You are not logged in.
Hello!
Since today when I rebooted my system gdm treis to start 10 times, then I get the written message that the graphical UI started (but it is not) and changing the tty results in a blinking back and forth beetween the boot messages on tty1 and the login on the chosen tty...
By the way: Starting the whole system with the LTS kernel works fine.
Journalctl shows me these lines booting Arch latest:
Feb 17 15:30:33 arch gdm[601]: Unable to kill session worker process
Feb 17 15:30:34 arch gdm[601]: Child process -1809 was already dead.
Feb 17 15:30:34 arch gdm[601]: Child process 1793 was already dead.
Feb 17 15:30:34 arch gdm[601]: Unable to kill session worker process
Feb 17 15:30:34 arch systemd[1]: Stopping GNOME Display Manager...
Feb 17 15:30:34 arch gdm-launch-environment][1818]: pam_systemd(gdm-launch-environment:session): Failed to create session: Message recipient disconnected from message bus without replying
Feb 17 15:30:34 arch gdm[601]: GdmLocalDisplayFactory: Failed to issue method call: GDBus.Error:org.freedesktop.DBus.Error.NoReply issue method call: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Feb 17 15:30:34 arch gdm[601]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Feb 17 15:30:35 arch systemd[1]: Stopped GNOME Display Manager.It works fine booting Arch LTS kernel:
Feb 17 15:31:32 arch systemd[1]: Starting GNOME Display Manager...
Feb 17 15:31:32 arch systemd[1]: Started GNOME Display Manager.So is this a dbus problem?
How can I solve it?
thx for help,
p.
Last edited by piedro (2017-02-19 20:37:15)
Offline
I have the same problem too. I'll try and downgrade gdm and see how it goes.
update: I installed 3.22.0-1 package and still it crashes.
Here's my system config:
x86_64
cpu i7 6700k
gpu nvidia 8800gtx with nouveau driver
update 2:
and here's my journal:
Φεβ 18 14:31:49 nekhomeworkstation /usr/lib/gdm/gdm-x-session[962]: resize called 2560 1600
Φεβ 18 14:31:49 nekhomeworkstation systemd[955]: Starting Sound Service...
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation rtkit-daemon[795]: Supervising 0 threads of 0 processes of 1 users.
Φεβ 18 14:31:49 nekhomeworkstation dbus-daemon[967]: Activating service name='org.gnome.GConf'
Φεβ 18 14:31:49 nekhomeworkstation dbus-daemon[967]: Successfully activated service 'org.gnome.GConf'
Φεβ 18 14:31:49 nekhomeworkstation systemd[955]: Started Sound Service.
Φεβ 18 14:31:49 nekhomeworkstation gnome-shell[988]: JS ERROR: Error: No property 'gi' in importer (or its value was undefined)
@<main>:1
Φεβ 18 14:31:49 nekhomeworkstation kernel: gnome-shell[988]: segfault at 8 ip 00007ff870524f10 sp 00007fff9927cc68 error 4 in libmozjs-24.so[7ff870395000+529000]
Φεβ 18 14:31:50 nekhomeworkstation gnome-session[969]: gnome-session-binary[969]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11As it turns out, my issue seems to be related to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1365967
Last edited by Nektarios (2017-02-18 12:40:18)
Offline
Me, I am using Nvidia proprietary driver, so it's probable not related to the graphics driver...
I looked at the bug report but frankly I do not understand entirely. I have changed some directory locations like for "Documents" - so there are entries in this XDG file. But all my directories are accessible (and no network drives) so I do not understand what I can do to avoid this error... use default locations?
Any work around?
p.
Offline
Hi, I had also a problem. After I disabled gdm and enabled lxdm, he told me something like my gpu driver mismatch. I installed nvidia-dkms instead of nvidia driver. Then he builded the kernel module fine. Hope this helps. Greets
Offline
Thanks for your hint.
But I already have nvidia-dkms installed and I do not see how a graphics driver problem could relate to these message lines from journalctl as posted above:
Feb 17 15:30:34 arch gdm-launch-environment][1818]: pam_systemd(gdm-launch-environment:session): Failed to create session: Message recipient disconnected from message bus without replying
Feb 17 15:30:34 arch gdm[601]: GdmLocalDisplayFactory: Failed to issue method call: GDBus.Error:org.freedesktop.DBus.Error.NoReply issue method call: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Feb 17 15:30:34 arch gdm[601]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failedAnyone?
But I still will try to change the display manager... (I already tried sddm with a resulting black screen, :-( )...
Reporting back then...
Last edited by piedro (2017-02-18 23:14:34)
Offline
THanks everybody.
Problem went away with today's arch kernel update.
So I guess this was just a strange regression caused by the kernel packaging team.
So it works again, amking this thread obsolete...
Cheeeerrrs, p.
Offline
OK I solved mine too. In my case the cause was the I had small customization of the gnome-shell JS and I had the env GNOME_SHELL_JS exported at /etc/environment to point to my customized files but those files where from the previous version and they were incompatible. removing the env var now it works again.
Offline