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!
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!
FS#57080 - XIO: fatal IO error 13 - The X11 connection broke
Attached to Project:
Arch Linux
Opened by Adrián (aribao) - Saturday, 13 January 2018, 08:36 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 29 March 2018, 14:10 GMT
Opened by Adrián (aribao) - Saturday, 13 January 2018, 08:36 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 29 March 2018, 14:10 GMT
|
DetailsDescription:
Plasma shell dies when searching something on klauncher menu or krunner. Usually the first time it dies it gets restarted but in the next times it doesn't and desktop can't be used anymore, forcing to restart from the tty. Additional info: * package version(s): * Plasma 5.11-1 * nvidia-340xx 340.104-21 Logs from .xsession-errors : The X11 connection broke: I/O error (code 1) XIO: fatal IO error 13 (Permiso denegado) on X server ":0" after 113253 requests (113238 known processed) with 0 events remaining. The X11 connection broke (error 1). Did the X11 server die? The X11 connection broke: I/O error (code 1) XIO: fatal IO error 13 (Permiso denegado) on X server ":0" after 113253 requests (113238 known processed) with 0 events remaining. I'm using nvidia Steps to reproduce: To reproduce open the menu and write something, or do the same with krunner (ALT + F2) and start typing. |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Sunday, 25 March 2018, 17:43 GMT
Is this still an issue?
Comment by Adrián (aribao) -
Thursday, 29 March 2018, 06:37 GMT
I couldn't reproduce it anymore, so it's fixed now.