Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38018 - [gnome-shell] 3.10.2 crashed at logon

Attached to Project: Arch Linux
Opened by Bernard Michaud (polaris6262) - Thursday, 05 December 2013, 01:27 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 05 December 2013, 23:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Upgraded from gnome-shell-3.10.1-1 to gnome-shell-3.10.2-1 on Nov 14, and after trying to log in got the infamous "Something has gone wrong" screen. Downgrading gnome-shell back to 3.10.1-1 immediately fixed the problem. On the next day (Nov 15) upgraded to the newly-released gnome-shell-3.10.2.1-1 and the same thing happened, again fixed by downgrading. Today Dec 4 another upgrade, this time to gnome-shell-3.10.2.1-2, and still the same thing.

The fact that reverting back to gnome-shell-3.10.1 immediately fixes the issue tends to indicate that the problem is related to gnome-shell-3.10.2 itself or a conflict with another gnome component.

I'm using lightdm-1.8.5. Not being very proficient with diagnosing system-level issues I am at a loss at finding out what is wrong with gnome-shell-3.10.2 but I'll gladly assist by providing whatever might be needed to find out the root cause.


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:

Upgrade to gnome-shell-3.10.2(-1)-(1/2)
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 05 December 2013, 23:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  libgdm 3.10.0.1-2
Comment by Jan Alexander Steffens (heftig) - Thursday, 05 December 2013, 18:56 GMT
Journal output of a login attempt?
Comment by Bernard Michaud (polaris6262) - Thursday, 05 December 2013, 21:42 GMT
That's not the system log accessible through dmesg is it?

If not, could you tell me how to access the required journal? I've managed Solaris and AIX systems before but I'm fairly new to Linux.

As well, as I no longer have a DE environment when gnome-shell fails, I'll have to capture the journal output to a USB key from a VT, the only access left.
Comment by Jan Alexander Steffens (heftig) - Thursday, 05 December 2013, 21:49 GMT
GDM sends all stderr output from the session to the journal. You can get the journal content since boot via "journalctl -b 0" or for the last five minutes via "journalctl --since='-5 minutes'", both as root.

I don't know whether LightDM does the same or saves the logs somewhere else, perhaps as ~/.xsession-errors. You should be using GDM for GNOME anyway.
Comment by Bernard Michaud (polaris6262) - Thursday, 05 December 2013, 22:55 GMT
I originally did use gdm when I first installed Arch with the Gnome DE. I truly disliked it for its lack of configurability (that's really a Gnome problem throughout, but that's a different issue) but I was especially irked however when it displayed a list of available users on the system, something which is in my opinion a breach of the most basic security, which is to not give away user names and accounts. I did manage through changing settings to get gdm to not display users, but then I found myself looking at a mostly empty screen and having to click on the "Not listed?" field just to get a Username entry. I found this too frustrating and did some research on alternative DMs and eventually picked lightdm for its simplicity and elegant configuration. It's worked perfectly well for me until gnome-shell-3.10.2.

I'm attaching the journal as requested. I did not find anything significant in the ~/.xsession-errors file except for a dbus timeout message.
   arch_journal.txt (425.5 KiB)
Comment by Jan Alexander Steffens (heftig) - Thursday, 05 December 2013, 22:59 GMT
Dec 05 17:37:46 tovilyis.excom.com gnome-session[2169]: (gnome-shell:2240): GLib-GIO-ERROR **: Settings schema 'org.gnome.login-screen' is not installed

Does it work if gdm is installed, even if it's not run?
Comment by Bernard Michaud (polaris6262) - Thursday, 05 December 2013, 23:23 GMT
To be perfectly honest I'd rather not have to install gdm if I'm not going to use it. As well, would there be a significant enough difference between version 3.10.1 and 3.10.2 of gnome-shell that would require the latter to have gdm on the system when the former does not?

If necessary I'll take a full system image of Arch and then install gdm, re-install gnome-shell-3.10.2.1-2 and try again to log on.

Loading...