View previous topic :: View next topic |
Author |
Message |
canis_lupus l33t
Joined: 22 Dec 2005 Posts: 773 Location: Kraków
|
Posted: Sun Jul 09, 2017 12:24 pm Post subject: Black screen after switch session. |
|
|
Hi! I have strange problem. I am using my computer with my wife, we have separate accounts on which we switch ctrl+alt+F7/8. But sometimes instead of the session on which I switch, I get a black screen with the cursor "_".
in .xsession-errors i get:
Code: | The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
kdeinit5: Fatal IO error: client killed
The X11 connection broke (error 1). Did the X11 server die?
kdeinit5: sending SIGHUP to children.
klauncher: Exiting on signal 1
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 11 (Zasoby chwilowo niedostępne) on X server ":1"
after 8357099 requests (8357099 known processed) with 0 events remaining.
QThread: Destroyed while thread is still running
[4365:4365:0207/225945.327885:ERROR:zygote_communication_linux.cc(292)] Failed to send GetTerminationStatus message to zygote
kdeinit5: sending SIGTERM to children.
kdeinit5: Exit.
Unexpected response from KInit (response = 0).
startkde: Could not start ksmserver. Check your installation.
QProcess: Destroyed while process ("kwin_x11") is still running.
[4365:4382:0207/225945.365436:ERROR:zygote_communication_linux.cc(292)] Failed to send GetTerminationStatus message to zygote
[4365:4371:0207/225945.445489:FATAL:bus.cc(1197)] D-Bus connection was disconnected. Aborting.
#0 0x565474dc1aae <unknown>
#1 0x565474dd8fc7 <unknown>
#2 0x565475a447f7 <unknown>
#3 0x565475a44823 <unknown>
#4 0x7f2b7a5ad109 dbus_connection_dispatch
#5 0x565475a43b89 <unknown>
#6 0x565474e4face <unknown>
#7 0x565474de30a8 <unknown>
#8 0x565474de4e88 <unknown>
#9 0x565474de5df2 <unknown>
#10 0x565474de6810 <unknown>
#11 0x565474de1f32 <unknown>
#12 0x565474e0515a <unknown>
#13 0x565474e238d7 <unknown>
#14 0x565474e1f532 <unknown>
#15 0x7f2b7ef765e6 start_thread
#16 0x7f2b765c0b4d clone
QProcess: Destroyed while process ("baloo_file") is still running.
autostart service "baloo_file" finished with exit code 1
QProcess: Destroyed while process ("krunner") is still running.
autostart service "krunner" finished with exit code 1
QProcess: Destroyed while process ("plasmashell") is still running.
autostart service "plasmashell" finished with exit code 1
QProcess: Destroyed while process ("/usr/lib64/libexec/polkit-kde-authentication-agent-1") is still running.
autostart service "/usr/lib64/libexec/polkit-kde-authentication-agent-1" finished with exit code 1
QProcess: Destroyed while process ("xembedsniproxy") is still running.
autostart service "xembedsniproxy" finished with exit code 1
KCrash: Application 'ksmserver' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
Warning: connect() failed: : Nie ma takiego pliku ani katalogu
KCrash: Attempting to start /usr/lib64/libexec/drkonqi directly
The X11 connection broke (error 1). Did the X11 server die?
QThread: Destroyed while thread is still running
Closing SQL connection: "kactivities_db_resources_140450577839936_readwrite"
Error: Can't open display: :1
QXcbConnection: Could not connect to display :1
Could not connect to D-Bus server: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
startkde: Shutting down...
kdeinit5_wrapper: Warning: connect(/var/run/user/1001/kdeinit5__1) failed: : No such file or directory
Error: Can not contact kdeinit5!
xprop: unable to open display ':1'
xprop: unable to open display ':1'
startkde: Done. |
_________________ "I love you cię" Różyczko... |
|
Back to top |
|
|
genterminl Guru
Joined: 12 Feb 2005 Posts: 523 Location: Connecticut, USA
|
Posted: Wed Jul 12, 2017 12:26 am Post subject: |
|
|
I suggest posting the previous few lines from .xsession-errors, and also at least the last bunch of lines from /var/log/Xorg.1.log (I'm guessing the 1 because of :1 in the lines you posted, but post the correct file for your session.) You might also say what happens then? If you go back to the console from which you started X (I'm assuming you manually started X) has it actually exited, and can you just restart it? You might also check for anything relevant in dmesg and /var/log/messages, although that seems less likely. Is the other X session still OK? And - as always, what has changed or been upgraded recently? |
|
Back to top |
|
|
canis_lupus l33t
Joined: 22 Dec 2005 Posts: 773 Location: Kraków
|
Posted: Wed Jul 12, 2017 7:15 am Post subject: |
|
|
Ok, I upload files as I go home.
Second X session is ok, I can open a new one. This has been happening for some time now, in the meantime several updates of xorg, kde, graphics driver, kernel, etc. _________________ "I love you cię" Różyczko... |
|
Back to top |
|
|
|
|
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
|
|