Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 786963 - >=gnome-base/gnome-settings-daemon-40.0 prevents gdm/gnome-shell to start
Summary: >=gnome-base/gnome-settings-daemon-40.0 prevents gdm/gnome-shell to start
Status: RESOLVED DUPLICATE of bug 786573
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-29 19:14 UTC by grixfosforito
Modified: 2021-04-29 19:40 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description grixfosforito 2021-04-29 19:14:47 UTC
After installing gnome-base/gnome-settings-daemon-40.0 or gnome-base/gnome-settings-daemon-40.0.1, gnome would not start, it would show the "Oh no! Something has gone wrong." gray screen before even showing gdm's login screen. 

journalctl shows the following errors:

systemd-coredump[8306]: Process 8292 (gnome-shell) of user 994 dumped core.
gnome-session-binary[8265]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
kernel: traps: gnome-shell[8370] trap int3 ip:7f9a7e379e57 sp:7ffeec38c0d0 error:0 in libglib-2.0.so.0.6800.1[7f9a7e33c000+8d000]
gnome-session[8265]: gnome-session-binary[8265]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
systemd[1]: systemd-coredump@1-8305-0.service: Succeeded.
gnome-shell[8370]: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'hinting'

Reinstalling gnome-base/gnome-settings-daemon-3.38.1 allows a normal boot.

Reproducible: Always
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-04-29 19:17:00 UTC
Dupe of 786573, I think?

*** This bug has been marked as a duplicate of bug 786573 ***
Comment 2 grixfosforito 2021-04-29 19:40:47 UTC
(In reply to Sam James from comment #1)
> Dupe of 786573, I think?
> 
> *** This bug has been marked as a duplicate of bug 786573 ***

It is indeed. Thanks.