Created attachment 847994 [details] emerge --info after recent gnome 43.2 update launching standard gnome applications (evolution,totem, gnome-photos, gnome-maps, gedit, gnome-terminal, sometimes nautilus) and some other gtk apps (like Liferea) from gnome shell fails after 30-60 minutes of active gnome session evolution gives this error: Cannot start Evolution. Another Evolution instance may be unresponsive. System error: Could not connect: No such file or directory Other apps simply don't start initially after fresh reboot stating apps works fine this is true for x.org and wayland session can launch applications from terminal though even if launching from gnome shell does not work issue appeared after updating to 43.2 from gnome 42 tried downgrading to gnome 42, although gnome-shell versions older than 43.2 were cleared from tree, and partial downgrade of other packages did not resolve the issue tried removing gnome and all related packages, and re-emerged from scratch gnome still without success emerge --info is in attached files not sure if helpful, but /var/log/messages has this: Jan 8 18:24:59 pc gdm: Gdm: Child process -5857 was already dead. Jan 8 18:29:50 pc shutdown[8204]: shutting down for system reboot Jan 8 18:29:52 pc gdm: Gdm: GdmDisplay: Session never registered, failing Jan 8 18:29:52 pc syslogd[5659]: exiting on signal 15 Jan 8 18:30:55 pc syslogd[5726]: syslogd v2.4.4: restart. Jan 8 18:32:41 pc shutdown[7055]: shutting down for system halt Jan 8 18:32:42 pc gdm: Gdm: GdmDisplay: Session never registered, failing Jan 8 18:32:43 pc syslogd[5726]: exiting on signal 15 Jan 8 18:35:47 pc syslogd[5656]: syslogd v2.4.4: restart. Jan 8 18:36:08 pc gdm: Gdm: Child process -5855 was already dead. Jan 8 19:50:53 pc gdm: Gdm: Child process -14059 was already dead. Jan 8 22:31:13 pc gdm: Gdm: Child process -20636 was already dead. Jan 8 22:42:51 pc shutdown[21804]: shutting down for system reboot Jan 8 22:42:54 pc syslogd[5656]: exiting on signal 15 Jan 8 22:44:18 pc syslogd[5719]: syslogd v2.4.4: restart. Jan 8 22:44:33 pc gdm: Gdm: Child process -5917 was already dead. Jan 8 22:44:59 pc gdm: Gdm: Child process -7997 was already dead. /var/log/gdm/greeter: (gsd-rfkill:6496): GLib-GIO-WARNING **: 22:44:33.715: Error releasing name org.gnome.SettingsDaemon.Rfkill: The connection is closed (gsd-a11y-settings:6491): GLib-GIO-WARNING **: 22:44:33.715: Error releasing name org.gnome.SettingsDaemon.A11ySettings: The connection is closed (gnome-shell:6020): libmutter-WARNING **: 22:44:33.715: Connection to xwayland lost (gsd-screensaver-proxy:6509): GLib-GIO-WARNING **: 22:44:33.717: Error releasing name org.gnome.SettingsDaemon.ScreensaverProxy: The connection is closed (gsd-housekeeping:6502): GLib-GIO-WARNING **: 22:44:33.717: Error releasing name org.gnome.SettingsDaemon.Housekeeping: The connection is closed (gsd-datetime:6506): GLib-GIO-WARNING **: 22:44:33.717: Error releasing name org.gnome.SettingsDaemon.Datetime: The connection is closed (gsd-sharing:6518): GLib-GIO-WARNING **: 22:44:33.717: Error releasing name org.gnome.SettingsDaemon.Sharing: The connection is closed gnome-session-binary[5941]: WARNING: Lost name on bus: org.gnome.SessionManager
any ideas? this issue persists through 2 months already driving gentoo+gnome combo unusable sad to see such deterioration of quality
It is hard as I cannot reproduce... but I only have access to systemd setups... for the case it is a problem happening with openRC. Regarding the logs... if it is a more important/general problem, maybe dmesg output after gnome starts to malfunction could be interesting
Created attachment 854878 [details] dmesg from computer start till freezes appear
I don't see anything special :S And if the messages in /var/log/messages are only those reported in the first comment ... :/ Does it happen in a newly created user account? Also... it seems to be a hardened system... I don't know if maybe that could cause some issues
Also please retry with Gnome 45 Thanks
(In reply to Pacho Ramos from comment #5) > Also please retry with Gnome 45 > > Thanks Previous attempt to resolve issue with new user on gnome 44 did not help But gnome 45 works well! Unfortunate it was 1 year for this bug to get resolved. But it works now
Unfortunately issue is still present It takes 2 days of computer running without reboot for the issue to appear instead of 60 min, but it is still present
And you are still using openRC instead of systemd, right? Are you using any overlay or something?
(In reply to Pacho Ramos from comment #8) > And you are still using openRC instead of systemd, right? Are you using any > overlay or something? Yes, I still use openrc though I switched from hardened profile to standard gnome profile - unfortunately same issue persists I only have 1 overlay guru with these packages installed for waydroid: app-containers/waydroid-1.4.0::guru dev-libs/gbinder-1.1.32::guru dev-libs/libglibutil-1.0.68::guru dev-python/gbinder-1.1.1-r10::guru dev-python/pyclip-0.7.0::guru But this does not touch system files so I doubt it is a reason My bet this 1 year bug arise from openrc + gnome combination, gnome is specifically designed for systemd reason to use gnome is its superior support of wayland enhancing security of system. KDE was not close when I tried 6 months ago main reason to use gentoo was openrc, now if switching to systemd I might as well consider other distro, unfortunately
