[kde] Plasma crash and can't log in anymore.
Hi there, First at all, I'm using KDE 4.7.0 under Ubuntu 11.04 with a 3.0.3 linux kernel. Today something very weird happened. I don't remember what I was doing exactly but suddenly KDE crashed and lxdm login showed up. I couldn't start KDE Plasma Desktop Session anymore and I get this .xsession-error[1]. However I can log in using some KDE Plasma Desktop Failsafe session kdm shows (after the crash I switched to kdm... lxdm doesn't show this special session). This failsafe session launch KDE Plasma using the --failsafe option. Any idea about what's going on and how can I fix it? Thanks in advance. [1] http://paste.kde.org/121033/ -- Luis Ángel Fernández Fernández ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Plasma crash and can't log in anymore.
Luis Ángel Fernández Fernández writes: Today something very weird happened. I don't remember what I was doing exactly but suddenly KDE crashed and lxdm login showed up. I couldn't start KDE Plasma Desktop Session anymore and I get this .xsession-error[1]. However I can log in using some KDE Plasma Desktop Failsafe session kdm shows (after the crash I switched to kdm... lxdm doesn't show this special session). This failsafe session launch KDE Plasma using the --failsafe option. Any idea about what's going on and how can I fix it? No. But I'd diff the output with the .xsession-errors you get when using the failsafe session. So you can separate the critical errors from harmless entries that happen every time. For example, I have no idea whether those dbus messages are normal in your setup, or if they are the root of the problem. Oh, and I think that attaching short logs is preferred to using pastebin, at least that seems how it is handles on most lists. Someone correct me please if this is wrong. Wonko ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Plasma crash and can't log in anymore.
On Martes, 13 de septiembre de 2011 17:00:38 Alex Schuster escribió: Any idea about what's going on and how can I fix it? No. But I'd diff the output with the .xsession-errors you get when using the failsafe session. So you can separate the critical errors from harmless entries that happen every time. For example, I have no idea whether those dbus messages are normal in your setup, or if they are the root of the problem. Ok. It seems that those dbus messages are normal since I have them in both modes. The differences start just after those messages. These are the differences: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 138 (NV-GLX) Minor opcode of failed request: 4 () Resource id in failed request: 0x1e3 Serial number of failed request: 33 Current serial number in output stream: 33 kwin(15671): fsrestore1 - conversion of 0,0,0,0 to QRect failed kwin(15671): fsrestore2 - conversion of 0,0,0,0 to QRect failed kwin(15671): fsrestore3 - conversion of 0,0,0,0 to QRect failed kwin(15671): Shaders are not supported kwin(15671): Shaders are not supported plasma-desktop: cannot connect to X server :0 plasma-desktop(15679): Communication problem with plasma-desktop , it probably crashed. Error message was: org.freedesktop.DBus.Error.NoReply : Message did not receive a reply (timeout by message bus) XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 after 58 requests (57 known processed) with 0 events remaining. kwalletd: Fatal IO error: client killed kdeinit4: Fatal IO error: client killed kdeinit4: sending SIGHUP to children. klauncher: Exiting on signal 1 kwin: Fatal IO error: client killed kglobalaccel: Fatal IO error: client killed kdeinit4: Fatal IO error: client killed kdeinit4: sending SIGHUP to children. KCrash: Application 'ksmserver' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit Warning: connect() failed: : No existe el fichero o el directorio KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly Qt-subapplication: Fatal IO error: client killed kdeinit4: sending SIGTERM to children. kdeinit4: Exit. kded4: Fatal IO error: client killed No protocol specified drkonqi: cannot connect to X server :0 kdeinit4: sending SIGTERM to children. kdeinit4: Exit. In failsafe mode I got many of those X Error but none of them say anything about NV-GLX. Anyway, it's very weird because everything was working until the crash and I think I didn't do any upgrade. The only thing I remember I've changed before the crash is that I changed something in akonadi configuration (something about working offline in one of my email accounts). Oh, and I think that attaching short logs is preferred to using pastebin, at least that seems how it is handles on most lists. Someone correct me please if this is wrong. No problem. I thought it could be too long and that's why I used pastebin. Thanks for your answer. Bye. -- Luis Ángel Fernández Fernández ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Plasma crash and can't log in anymore.
Le Mardi 13 de septembre 2011 17:47:28 Luis Ángel Fernández Fernández a écrit : On Martes, 13 de septiembre de 2011 17:00:38 Alex Schuster escribió: Any idea about what's going on and how can I fix it? No. But I'd diff the output with the .xsession-errors you get when using the failsafe session. So you can separate the critical errors from harmless entries that happen every time. For example, I have no idea whether those dbus messages are normal in your setup, or if they are the root of the problem. Ok. It seems that those dbus messages are normal since I have them in both modes. The differences start just after those messages. These are the differences: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 after 58 requests (57 known processed) with 0 events remaining. There, X doesn't work. try looking into /var/log/Xorg.0.log Search for lines with (EE) In failsafe mode I got many of those X Error but none of them say anything about NV-GLX. Anyway, it's very weird because everything was working until the crash and I think I didn't do any upgrade. The only thing I remember I've changed before the crash is that I changed something in akonadi configuration (something about working offline in one of my email accounts). In failsafe mode, try opening a console and running glxgears or glxinfo or nvidia-settings (and then go to the GLX page). This is to see if graphic acceleration is working. Check that you have free disk space in /tmp, and that /tmp isn't noexec (for some reason, nvidia needs execute permissions in /tmp, took me weeks to figure out) The shaders not supported part seems weird, what card do you have? Martin signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Plasma crash and can't log in anymore.
Luis Ángel Fernández Fernández writes: On Martes, 13 de septiembre de 2011 17:00:38 Alex Schuster escribió: Any idea about what's going on and how can I fix it? No. But I'd diff the output with the .xsession-errors you get when using the failsafe session. So you can separate the critical errors from harmless entries that happen every time. For example, I have no idea whether those dbus messages are normal in your setup, or if they are the root of the problem. Ok. It seems that those dbus messages are normal since I have them in both modes. One thing less to check for. The differences start just after those messages. These are the differences: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 138 (NV-GLX) Minor opcode of failed request: 4 () Resource id in failed request: 0x1e3 Serial number of failed request: 33 Current serial number in output stream: 33 kwin(15671): fsrestore1 - conversion of 0,0,0,0 to QRect failed kwin(15671): fsrestore2 - conversion of 0,0,0,0 to QRect failed kwin(15671): fsrestore3 - conversion of 0,0,0,0 to QRect failed kwin(15671): Shaders are not supported kwin(15671): Shaders are not supported plasma-desktop: cannot connect to X server :0 plasma-desktop(15679): Communication problem with plasma-desktop , it probably crashed. I have similar kwin messages, too. But the X stuff is weird. A shot in the dark: Can it be that compositing / desktop effects are making trouble, and are turned off in safe mode? You could disable them by setting Enabled to false in .kde/share/config/kwinrc, or better use the kwriteconfig --file kwinrc --group Compositing --key Enabled false command to do this. No more ideas, Wonko ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Plasma crash and can't log in anymore.
On Martes, 13 de septiembre de 2011 18:00:27 Martin Bednár escribió: First of all, thank you for yor help. Everything is working now. It seems that the driver became corrupted at some point and for some reason. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 after 58 requests (57 known processed) with 0 events remaining. There, X doesn't work. try looking into /var/log/Xorg.0.log Search for lines with (EE) I should have thought of this :(. Anyway. This is what I found there: [ 330.360] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X [ 330.360] (EE) NVIDIA(0): log file that the GLX module has been loaded in your X [ 330.360] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If [ 330.360] (EE) NVIDIA(0): you continue to encounter problems, Please try [ 330.360] (EE) NVIDIA(0): reinstalling the NVIDIA driver. So I did it but it wasn't too easy. I needed to move the nvidia.ko from modules folder because it was marked as permanent and I couldn't unload it using rmmod. But after that I've reinstalled the driver and everything is working again. In failsafe mode, try opening a console and running glxgears or glxinfo or nvidia-settings (and then go to the GLX page). This is to see if graphic acceleration is working. Those didn't run so I guess I didn't have acceletarion at all. There was a error message about not having GLX. The shaders not supported part seems weird, what card do you have? I have a NVidia GeForce 9400 GT but now I have shaders support. It was because the driver corruption, I guess. Bye. -- Luis Ángel Fernández Fernández ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
