[Bug 956068] New: Gnome does not start
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 Bug ID: 956068 Summary: Gnome does not start Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: wodenhof@daad-alumni.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I installed primarily the KDE version. When it was up and running, I installed Gnome via YAST2 / software install or delete / patterns / gnome basic system and gnome desktop environment. No errors. When I (the user created during install) chose Gnome at the login screen entering user and password the screen turns black and I get an "x" as mouse pointer. <alt><F2> and login as root then "init 3" and "init 5" brings me back to the login screen. If a different user tries to login with gnome, same happens as described above, but some 10 or 15 seconds later one will be back to the login screen automatically. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c1 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org, | |wodenhof@daad-alumni.de Flags| |needinfo?(wodenhof@daad-alu | |mni.de) --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> --- As you installed KDE/Plasma first, I assume you're using sddm as your display manager (the login manager) Which means, this should be a duplicate of bug 931314; but that bug is marked fixed with a corresponding fix released; Can you please verify/confirm these things: * are you using sddm as your display manager? (check /etc/sysconfig/displaymanager) * do you have the patch for gnome-session installed? openSUSE-RU-2015:2018-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 931314 CVE References: Sources used: openSUSE Leap 42.1 (src): gnome-session-3.16.0-5.2 * if this is all correct, please poste the output of the systemd journal in order to be able to further diagnose this issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c2 --- Comment #2 from Matthias Schünemann <wodenhof@daad-alumni.de> --- sddm is the login manager. I installed the patch. I (the first user created during installation besides root) can now log in to Gnome and to KDE. All others can not. Gnome kicks them back to the login screen after some seconds, KDE hangs as described for Gnome in my initial report. Journal follows. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c3 --- Comment #3 from Matthias Schünemann <wodenhof@daad-alumni.de> --- Created attachment 656865 --> http://bugzilla.opensuse.org/attachment.cgi?id=656865&action=edit Output of <journalctl | grep "Nov 21"> copied from Konsole If you need any particular piece of the journal, please tell me the exact command sequence, I'm not really an expert here... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 Raul Malea <raulmalea@yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |raulmalea@yahoo.co.uk -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c4 Bjørn Lie <zaitor@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zaitor@opensuse.org --- Comment #4 from Bjørn Lie <zaitor@opensuse.org> --- (In reply to Matthias Schünemann from comment #2)
sddm is the login manager.
I installed the patch. I (the first user created during installation besides root) can now log in to Gnome and to KDE. All others can not. Gnome kicks them back to the login screen after some seconds, KDE hangs as described for Gnome in my initial report.
Journal follows.
Are you saying that you can NOT log into KDE/Plasma with the newly added users either? If so - the issue is not in GNOME any more, but in SDDM or somewhere else. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c5 --- Comment #5 from Matthias Schünemann <wodenhof@daad-alumni.de> --- (In reply to Bjørn Lie from comment #4)
(In reply to Matthias Schünemann from comment #2)
sddm is the login manager.
I installed the patch. I (the first user created during installation besides root) can now log in to Gnome and to KDE. All others can not. Gnome kicks them back to the login screen after some seconds, KDE hangs as described for Gnome in my initial report.
Journal follows.
Are you saying that you can NOT log into KDE/Plasma with the newly added users either?
Yes. Login is not possible neither to plasma nor to Gnome by users other than the first user created during installation (i.e. I can log in, my children cannot).
If so - the issue is not in GNOME any more, but in SDDM or somewhere else.
If you say so. What more information do you need? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c6 Azazel Gad <azazel_2011@yahoo.com.mx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |azazel_2011@yahoo.com.mx --- Comment #6 from Azazel Gad <azazel_2011@yahoo.com.mx> --- Hi all, I'm having a similar issue. I originally installed KDE with a fresh openSUSE Leap install. Then I decided to try out GNOMEand installed it from YaST software install or delete / patterns / gnome basic system and gnome desktop environment. After installation had finished I decided to reboot the computer and chose GNOME from SDDM login screen. I got a something went wrong Logout screen which sent me back to SDDM login screen. I thought the issue may be related to sddm so I installed and changed my display manager to lightdm and got same result as sddm after rebooting computer. Finally I changed my display manager to GDM. After rebooting the computer I only got a black screen and no login at all. I used a virtual console (ctrl + alt + F1) to change my display manager back to sddm so I could start KDE at least. I'm using a AMD Radeon GPU with proprietary driver installed from repos. this is what I got from journalctl: dic 12 21:36:51 jarvis gnome-session[2028]: ** (gnome-session-failed:2282): WARNING **: Could not open X display dic 12 21:36:51 jarvis gnome-session[2028]: Unable to init server: No se pudo conectar: Conexión rehusada dic 12 21:36:51 jarvis gnome-session[2028]: ** (gnome-session-failed:2282): WARNING **: No se puede abrir el visor: dic 12 21:36:55 jarvis gnome-session[2317]: X Error of failed request: BadValue (integer parameter out of range for operation) dic 12 21:36:55 jarvis gnome-session[2317]: Major opcode of failed request: 141 (RANDR) dic 12 21:36:55 jarvis gnome-session[2317]: Minor opcode of failed request: 13 (RRChangeOutputProperty) dic 12 21:36:55 jarvis gnome-session[2317]: Value in failed request: 0x75 dic 12 21:36:55 jarvis gnome-session[2317]: Serial number of failed request: 320 dic 12 21:36:55 jarvis gnome-session[2317]: Current serial number in output stream: 322 dic 12 21:37:02 jarvis gnome-session[2317]: gnome-session[2317]: WARNING: Lost name on bus: org.gnome.SessionManager dic 12 21:37:02 jarvis gnome-session[2317]: WARNING: Lost name on bus: org.gnome.SessionManager dic 12 21:37:02 jarvis gnome-session[2317]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. dic 12 21:37:03 jarvis gnome-session[2317]: ** (gnome-session-failed:2376): WARNING **: Could not open X display dic 12 21:37:03 jarvis gnome-session[2317]: Unable to init server: No se pudo conectar: Conexión rehusada dic 12 21:37:03 jarvis gnome-session[2317]: ** (gnome-session-failed:2376): WARNING **: No se puede abrir el visor: dic 12 21:37:07 jarvis gnome-session[2411]: X Error of failed request: BadValue (integer parameter out of range for operation) dic 12 21:37:07 jarvis gnome-session[2411]: Major opcode of failed request: 141 (RANDR) dic 12 21:37:07 jarvis gnome-session[2411]: Minor opcode of failed request: 13 (RRChangeOutputProperty) dic 12 21:37:07 jarvis gnome-session[2411]: Value in failed request: 0x75 dic 12 21:37:07 jarvis gnome-session[2411]: Serial number of failed request: 320 dic 12 21:37:07 jarvis gnome-session[2411]: Current serial number in output stream: 322 dic 12 21:39:28 jarvis gnome-session[2411]: WARNING: Lost name on bus: org.gnome.SessionManager dic 12 21:39:28 jarvis gnome-session[2411]: gnome-session[2411]: WARNING: Lost name on bus: org.gnome.SessionManager dic 12 21:40:42 jarvis gnome-session[1152]: X Error of failed request: BadValue (integer parameter out of range for operation) dic 12 21:40:42 jarvis gnome-session[1152]: Major opcode of failed request: 141 (RANDR) dic 12 21:40:42 jarvis gnome-session[1152]: Minor opcode of failed request: 13 (RRChangeOutputProperty) dic 12 21:40:42 jarvis gnome-session[1152]: Value in failed request: 0x75 dic 12 21:40:42 jarvis gnome-session[1152]: Serial number of failed request: 320 dic 12 21:40:42 jarvis gnome-session[1152]: Current serial number in output stream: 322 Hope you can help me. Thank you -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c7 Bjørn Lie <zaitor@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-gnome@forge.provo. |opensuse-kde-bugs@opensuse. |novell.com |org Flags|needinfo?(wodenhof@daad-alu | |mni.de) | --- Comment #7 from Bjørn Lie <zaitor@opensuse.org> --- (In reply to Azazel Gad from comment #6)
Hi all,
I'm having a similar issue.
snip
I'm using a AMD Radeon GPU with proprietary driver installed from repos.
We had a bug with gdm and radeon prop driver - this one was fixed a long time ago, so I assume you are ok at least. Matthias: I'll just reassign to kde team, and they will have to look into it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c8 Bjørn Lie <zaitor@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |KDE Workspace (Plasma) --- Comment #8 from Bjørn Lie <zaitor@opensuse.org> --- Also change component. ---- Sidenote to Azazel Gad: Should you still have the same problem, please file a new bug with ref to this one. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c9 Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tittiatcoke@gmail.com Flags| |needinfo?(wodenhof@daad-alu | |mni.de) --- Comment #9 from Raymond Wooninck <tittiatcoke@gmail.com> --- Matthias, Can you check if there are any errors in the .xsession-errors-:* files that are in the home directory of the users ? Normally Plasma will log all errors during the startup in the file and not really in the systemd journal. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c10 --- Comment #10 from Matthias Schünemann <wodenhof@daad-alumni.de> --- Created attachment 673249 --> http://bugzilla.opensuse.org/attachment.cgi?id=673249&action=edit Xsession-errors file File from around the time the error occurred. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c11 --- Comment #11 from Matthias Schünemann <wodenhof@daad-alumni.de> --- Sorry, people, this is nearly half a year in the past. I re-installed long since with no gnome. I added xsession-errors-:1 from about that time -- which somehow survived. I hope you can glean some meaning from it. Leap 42.1 is giving me a terrible time. I wish I'd stayed with 13.2 which was truly and really nice and good ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c12 --- Comment #12 from Raymond Wooninck <tittiatcoke@gmail.com> --- As expected I guess, this xsession-errors file doesn't deliver any indication of the reported problem. It would have been great if we could have gotten the .xsession-errors file for those users where login is no longer possible. As I understood from your message, you have reinstalled Leap 42.1 with just a single desktop and no longer face the issue. Is this correct ? If so, then there is little we can do until someone else has the same issue and is capable of providing the error files for us. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c13 --- Comment #13 from Matthias Schünemann <wodenhof@daad-alumni.de> --- (In reply to Raymond Wooninck from comment #12)
As expected I guess, this xsession-errors file doesn't deliver any indication of the reported problem.
Sorry it is the only one left over from that time.
It would have been great if we could have gotten the .xsession-errors file for those users where login is no longer possible.
I checked, but they have no .xsession-errors files of that time conserved.
As I understood from your message, you have reinstalled Leap 42.1 with just a single desktop and no longer face the issue.
Correct.
Is this correct ? If so, then there is little we can do until someone else has the same issue and is capable of providing the error files for us.
Well, sorry but this is a machine for working (and my only PC). I _had_ to get it up and running. Thanks for your efforts anyway. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=956068 http://bugzilla.opensuse.org/show_bug.cgi?id=956068#c14 Karl Cheng <qantas94heavy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |qantas94heavy@gmail.com Resolution|--- |NORESPONSE --- Comment #14 from Karl Cheng <qantas94heavy@gmail.com> --- Hi, unfortunately it seems this hasn't been able to be reproduced. Given that openSUSE has had significant updates in newer versions, this bug may have been fixed already. If you can still reproduce the problem with a current version of openSUSE, please file a new bug or reopen this one. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com