Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] gdm/gnome 3.10 hang on start
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
triquetra
n00b
n00b


Joined: 09 Apr 2012
Posts: 46
Location: Kansas, USA

PostPosted: Fri Feb 21, 2014 11:35 pm    Post subject: [Solved] gdm/gnome 3.10 hang on start Reply with quote

Yesterday I upgraded from a working Gnome 3.8 install to Gnome 3.10. Now neither gdm nor gnome will start.

When gdm attempts to start, I get only a blank screen with a cursor in the upper left corner.

I stopped gdm with systemctl, and installed lxdm. After starting lxdm with systemctl, and lxdm worked. I selected gnome as my desktop, and after login, I get only a blue screen.

I rebooted and installed lxde. Stopped gdm and started lxdm through systemctl, then selected lxde as my desktop, and it worked. I'm now writing this post from my gentoo install in lxde.

With that background, I presume that my system is functional (since I'm using it), but there is something wrong with gnome/gdm 3.10.

Any ideas on how to get gnome 3.10 working?


Last edited by triquetra on Mon Apr 21, 2014 3:07 pm; edited 2 times in total
Back to top
View user's profile Send private message
TomWij
Developer
Developer


Joined: 04 Jul 2012
Posts: 1551

PostPosted: Sat Feb 22, 2014 3:11 pm    Post subject: Reply with quote

Check `journalctl -rb` in a TTY (newest messages at top) after you get that screen and see if there are any particular errors of interest; feel free to redirect it to a file and provide it to us, such that we can help take a look if needed.
Back to top
View user's profile Send private message
JohnY
Apprentice
Apprentice


Joined: 26 Jul 2002
Posts: 283

PostPosted: Sat Feb 22, 2014 8:52 pm    Post subject: Re: can not start gnome 3.10 Reply with quote

triquetra wrote:
Yesterday I upgraded from a working Gnome 3.8 install to Gnome 3.10. Now neither gdm nor gnome will start.

When gdm attempts to start, I get only a blank screen with a cursor in the upper left corner.

.....
Any ideas on how to get gnome 3.10 working?


Can't help with the 'getting gnome 3.10 working' part but I had exactly the same symptoms: no gdm and no gnome-shell or fallback. I spent about 4 days part time going back to gnome 3.8 - 111 packages and many dependents had to be rebuilt. Now gdm still won't start (it did before). Kdm will start gnome now, lightdm won't. I have enstalled e17 and xfce4 and they both work. I have a pretty good gnome 3.10 mask if you need it.

JohnY
Back to top
View user's profile Send private message
JohnY
Apprentice
Apprentice


Joined: 26 Jul 2002
Posts: 283

PostPosted: Sat Feb 22, 2014 9:09 pm    Post subject: Can't get gnome 3.10 to start Reply with quote

I also spent quite a bit of time trouble shooting the gnome 3.10 start without success. Besides e17 and later xfce4 I also had kde4 installed and working alongside gnome 3.8 before the attempt at gnome 3.10. I've removed a good chunk of kde4 while going back to gnome 3.8. I've nursed this 32bit ~x86 installation of gentoo since before gentoo 0.4 throught about 6 or 7 major hardware upgrade from a k6-2 300mhz thru:

Quote:
Linux zinger 3.13.1-gentoo #3 SMP PREEMPT Wed Feb 12 21:29:25 EST 2014 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD GNU/Linux


without any luck with gnome 3.10.


JohnY[/code]
Back to top
View user's profile Send private message
triquetra
n00b
n00b


Joined: 09 Apr 2012
Posts: 46
Location: Kansas, USA

PostPosted: Mon Feb 24, 2014 4:31 pm    Post subject: Reply with quote

I'm not seeing anything useful in the journal (it's my understanding that the dbus error is normal), TomWij, but since you asked for it, here it is:

journalctl -rb:
-- Logs begin at Sun 2013-08-25 06:12:34 CDT, end at Mon 2014-02-24 10:16:58 CST. --
Feb 24 10:16:58 dpc-np9170-gentoo systemd[3199]: Time has been changed
Feb 24 10:16:44 dpc-np9170-gentoo systemd[3199]: Startup finished in 42ms.
Feb 24 10:16:44 dpc-np9170-gentoo systemd[3199]: Reached target Default.
Feb 24 10:16:44 dpc-np9170-gentoo systemd[3199]: Starting Default.
Feb 24 10:16:44 dpc-np9170-gentoo systemd[3199]: Stopped target Bluetooth.
Feb 24 10:16:44 dpc-np9170-gentoo systemd[3199]: Stopped target Sound Card.
Feb 24 10:16:44 dpc-np9170-gentoo systemd[3199]: Mounted /sys/fs/fuse/connections.
Feb 24 10:16:44 dpc-np9170-gentoo systemd[3199]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory


@JohnY, please post your gnome 3.10 mask. I may wind up using that if I can't get this figured out soon. Thanks.
Back to top
View user's profile Send private message
TomWij
Developer
Developer


Joined: 04 Jul 2012
Posts: 1551

PostPosted: Mon Feb 24, 2014 6:36 pm    Post subject: Reply with quote

See https://wiki.gentoo.org/wiki/Systemd#systemd-logind_.26_pam_systemd
Back to top
View user's profile Send private message
triquetra
n00b
n00b


Joined: 09 Apr 2012
Posts: 46
Location: Kansas, USA

PostPosted: Tue Feb 25, 2014 3:51 pm    Post subject: Reply with quote

TomWij wrote:
See https://wiki.gentoo.org/wiki/Systemd#systemd-logind_.26_pam_systemd


That section seems to deal with authorization through PAM and NetworkManager not working properly. Neither of those seem to be a problem for me. I have no problem logging in through the console while systemd is running (and I can log into lxde or enlightenment through lxdm) and NetworkManager seems to be functioning properly.

Anyway, my system-auth seems to already have the proper line:

/etc/pam.d/system-auth:
auth      required   pam_env.so
auth      required   pam_unix.so try_first_pass likeauth nullok
auth      optional   pam_permit.so
 
account      required   pam_unix.so
account      optional   pam_permit.so
 
password   required   pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
password   required   pam_unix.so try_first_pass use_authtok nullok sha512 shadow
password   optional   pam_permit.so
 
session      required   pam_limits.so
session      required   pam_env.so
session      required   pam_unix.so
session      optional   pam_permit.so
-session        optional        pam_systemd.so
Back to top
View user's profile Send private message
TomWij
Developer
Developer


Joined: 04 Jul 2012
Posts: 1551

PostPosted: Tue Feb 25, 2014 6:15 pm    Post subject: Reply with quote

Hmm, then there's something else going on; because something prevents the socket from being made, I haven't read up on the details of how that all works yet. But the way forward I think is to see which process is responsible for creating that socket and what could prevent that socket from being made; I am thinking PAM could be it, but it could just as well be something else.
Back to top
View user's profile Send private message
triquetra
n00b
n00b


Joined: 09 Apr 2012
Posts: 46
Location: Kansas, USA

PostPosted: Tue Feb 25, 2014 8:48 pm    Post subject: Reply with quote

I tried the systemd dbus config suggested here, but after reboot, there was no difference.
Back to top
View user's profile Send private message
triquetra
n00b
n00b


Joined: 09 Apr 2012
Posts: 46
Location: Kansas, USA

PostPosted: Wed Mar 05, 2014 4:31 pm    Post subject: Reply with quote

I discovered that "journalctrl -rb" yields different results depending on the user. Here's the results of "sudo journalctrl -rb" after a boot and frozen Gnome/GCM 3.10

Besides some Javascript warnings, the only thing I see is the dbus error. I'm not sure how to fix this.
Back to top
View user's profile Send private message
TomWij
Developer
Developer


Joined: 04 Jul 2012
Posts: 1551

PostPosted: Wed Mar 05, 2014 5:41 pm    Post subject: Reply with quote

Right, I'll keep the different user on mind next time I ask. There are a few gjs backtraces in that from gnome-session and/or gnome-shell, which I think point out that there may be something wrong in the code (as it should rather give a proper error); I suggest you to file a bug at https://bugzilla.gnome.org/ to make upstream aware of this, as they'll want to hear about this.

Quote:
Mar 04 10:20:00 dpc-np9170-gentoo gnome-session[2723]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 04 10:20:00 dpc-np9170-gentoo gnome-session[2723]: DateMenuButton<._updateClockAndDate@/usr/share/gnome-shell/js/ui/dateMenu.js:198
Mar 04 10:20:00 dpc-np9170-gentoo gnome-session[2723]: (gnome-shell:2776): Gjs-WARNING **: JS ERROR: Error: Argument 'text' (type utf8) may not be null
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: _convertToNativeSignal@/usr/share/gjs-1.0/overrides/Gio.js:130
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: _emit@/usr/share/gjs-1.0/signals.js:124
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: ScreenShield<._init/<@/usr/share/gnome-shell/js/ui/screenShield.js:537
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: wrapper@/usr/share/gjs-1.0/lang.js:213
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: ScreenShield<._onStatusChanged@/usr/share/gnome-shell/js/ui/screenShield.js:840
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: notifyError@/usr/share/gnome-shell/js/ui/main.js:313
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: notify@/usr/share/gnome-shell/js/ui/main.js:293
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: (gnome-shell:2776): Gjs-WARNING **: JS ERROR: Exception in callback for signal: StatusChanged: TypeError: messageTray is null
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: Gjs-Message: JS LOG: error: Unable to lock: Lock was blocked by an application
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: Gjs-Message: JS LOG: pushModal: invocation of begin_modal failed
Mar 04 10:19:56 dpc-np9170-gentoo gnome-session[2723]: Gjs-Message: JS LOG: pushModal: invocation of begin_modal failed


Last edited by TomWij on Mon Mar 17, 2014 11:14 pm; edited 1 time in total
Back to top
View user's profile Send private message
lucky_rooster
n00b
n00b


Joined: 24 Aug 2004
Posts: 28

PostPosted: Wed Mar 12, 2014 7:57 pm    Post subject: Same issue here Reply with quote

I am encountering the same issue on one of my 2 systems that were upgraded to Gnome/GDM 3.10.0.1. The working system (a laptop Core i3 w/ Intel HD graphic) had no issues. My desktop (AMD FX-8320 w/ nvidia) first had the issue of:
Code:
GLib-GObject: g_object_ref: assertion `object->ref_count > 0' failed

per this thread

As suggested there, I rebuilt the entire gdm tree hoping for the best. Now I am hitting this issue and installed lxdm since the desktop is used by the family and the younger of the kids like the graphical login.

Most users on the box that has the issue are using XCFE4 which is running fine. One user was using a Gnome session and after logging in (via lxdm) would get a screen and cursor similar to what gdm was giving - I haven't looked into it yet - just switched her to XFCE4.

I would be interested in hearing from anyone else that may be encountering this and/or anyone that has found a way around it (less reverting to the Gnome 3.8 stuff). I've started looking through packages and versions comparing the working and non-working but haven't gotten too far into it yet.

Also, just wondering: did a bug ever get filed upstream?
Back to top
View user's profile Send private message
raynsan
n00b
n00b


Joined: 16 Mar 2014
Posts: 1

PostPosted: Sun Mar 16, 2014 11:50 am    Post subject: Reply with quote

Hello there :)

after my update from gnome 3.8.x to 3.10.x i encountered problems with gdm, too.


  • Could not log in
  • Screen was somewhat frozen / did not react
  • etc...


Funny fact though, my system was booting in openrc! I told my system to use systemd again by setting GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd" in "/etc/default/grub" (As stated here). After a reboot, everything worked just fine.

I hope this will help someone.

Bye
Back to top
View user's profile Send private message
lucky_rooster
n00b
n00b


Joined: 24 Aug 2004
Posts: 28

PostPosted: Mon Mar 17, 2014 3:56 pm    Post subject: Reply with quote

This morning portage indicated that among the available updates were: nvidia-drivers, libav, and gnome-shell so I was a bit hopeful something might get fixed. After updating the world, setting gdm to be used and rebooting I am still seeing the same issue.

Also, I am already using systemd (on both systems).
Back to top
View user's profile Send private message
Progman3K
Guru
Guru


Joined: 03 Jan 2004
Posts: 535

PostPosted: Mon Mar 17, 2014 10:38 pm    Post subject: Reply with quote

lucky_rooster wrote:
This morning portage indicated that among the available updates were: nvidia-drivers, libav, and gnome-shell so I was a bit hopeful something might get fixed. After updating the world, setting gdm to be used and rebooting I am still seeing the same issue.

Also, I am already using systemd (on both systems).


I'm having a nearly-identical problem (only I am using nouveau, not nvidia):
http://forums.gentoo.org/viewtopic-p-7518756.html

The problem is inside either gdm or gnome.
Back to top
View user's profile Send private message
dengel
n00b
n00b


Joined: 22 Dec 2004
Posts: 23

PostPosted: Sat Mar 22, 2014 5:11 am    Post subject: Any movement on this? Reply with quote

Has anyone found any way to resolve this? I'm having the same issue since updating to gnome-3.10.
Back to top
View user's profile Send private message
triquetra
n00b
n00b


Joined: 09 Apr 2012
Posts: 46
Location: Kansas, USA

PostPosted: Tue Apr 01, 2014 3:27 pm    Post subject: Reply with quote

No resolution yet. I have been doing world updates almost daily in hopes that something might clean up this mess, but no luck yet. Unlike raynsan, I know that I am using systemd (I use rEFInd, not GRUB), so that is not my issue. Anyone else have success sorting this out?
Back to top
View user's profile Send private message
sedorox
Apprentice
Apprentice


Joined: 13 Feb 2004
Posts: 202

PostPosted: Sat Apr 19, 2014 2:49 pm    Post subject: Reply with quote

I found a fix (for me at least), and documented it here: http://forums.gentoo.org/viewtopic-p-7538254.html#7538254
The short of it is, that the system locale needed to be in the utf8 format. For me, this was en_US.utf8. this can be set with "localectl set-locale LANG=en_US.utf8" (available ones are given with localectl list)
Don't forget to adjust LC_ALL and LANGUAGE in make.conf as well.
_________________
Home Desktop: Intel i5-2400 3.10ghz | 16G Ram | 1x 60G SSD, 1x 1TB HDD
Home Server: Intel E6750 2.66Ghz| 8G Ram | 1x 500G, 2x 750G (RAID1), 1x 1T, 1x 640G
Back to top
View user's profile Send private message
triquetra
n00b
n00b


Joined: 09 Apr 2012
Posts: 46
Location: Kansas, USA

PostPosted: Mon Apr 21, 2014 3:06 pm    Post subject: [Solved] gdm/gnome 3.10 hang on start Reply with quote

Thank you sedorox! This seems to have worked for me as well. My LC_ALL and LANGUAGE variables were not set in make.conf, so I did nothing with them, but changing to UTF8 using localectl resolved the black screen hang I had been experiencing. Marked solved.
Back to top
View user's profile Send private message
lucky_rooster
n00b
n00b


Joined: 24 Aug 2004
Posts: 28

PostPosted: Fri May 02, 2014 2:00 pm    Post subject: LOCALE is the fix Reply with quote

Thanks, this, indeed, solved my issue!

One note worth mentioning from the localization wiki:

Quote:
Warning
Using LC_ALL is strongly discouraged as it can't be overridden later on. Please use it only when testing and never set it in a startup file.
Back to top
View user's profile Send private message
difficultcho
n00b
n00b


Joined: 15 Mar 2013
Posts: 14

PostPosted: Thu May 29, 2014 4:09 am    Post subject: Reply with quote

Thanks, sedorox!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum