Welcome to the Xorg Hell: many crashes in too many occasions

Simone98RC · 2015-07-26 15:55:15

Hi guys,
after the 4.1.2 kernel update (which enable the Nouveau hardware acceleration for my GTX 750 Ti), I'm encountering a lot of Xorg crashes (so I'm returning to the login screen) in any app which make use of Xorg dipendences: games like Speed Dreams and SuperTuxKart, apps like Virtualbox, PiTiVi, FreeCAD etc.
My new Arch life is becoming an hell!

I'm using LightDM as login manager (started by the relative Plymouth service), Cinnamon as DE and Nouveau as graphic driver.
Here I've reported the repetitive errors logged in my syslog:

lug 26 17:32:36 S98RC-PC kernel: SUPR0GipMap: fGetGipCpu=0x3
lug 26 17:32:37 S98RC-PC cinnamon-session[1944]: Gdk-WARNING: cinnamon-session: Fatal IO error 11 (Risorsa temporaneamente non disponibile) on X server :0.
lug 26 17:32:37 S98RC-PC polkitd[754]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.40, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale it_IT.utf8) (disconnected from bus)
lug 26 17:32:37 S98RC-PC org.a11y.atspi.Registry[2901]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
lug 26 17:32:37 S98RC-PC org.a11y.atspi.Registry[2901]: after 29141 requests (29141 known processed) with 0 events remaining.
lug 26 17:32:37 S98RC-PC org.gnome.gedit[2515]: (gedit:14211): Gdk-WARNING **: gedit: Fatal IO error 11 (Risorsa temporaneamente non disponibile) on X server :0.
lug 26 17:32:37 S98RC-PC org.gtk.vfs.Daemon[2515]: A connection to the bus can't be made
lug 26 17:32:37 S98RC-PC org.gtk.vfs.Daemon[2515]: 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.
lug 26 17:32:37 S98RC-PC org.a11y.Bus[2515]: 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.
lug 26 17:32:37 S98RC-PC org.gtk.Private.UDisks2VolumeMonitor[2515]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). 
lug 26 17:32:37 S98RC-PC org.gtk.Private.MTPVolumeMonitor[2515]: 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.
lug 26 17:32:37 S98RC-PC org.gtk.Private.GPhoto2VolumeMonitor[2515]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). 
lug 26 17:32:37 S98RC-PC org.gtk.Private.GoaVolumeMonitor[2515]: 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.
lug 26 17:32:37 S98RC-PC org.gnome.OnlineAccounts[2515]: 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.
lug 26 17:32:37 S98RC-PC org.gtk.Private.AfcVolumeMonitor[2515]: g_dbus_connection_real_closed: Remote peer vanished with error: Errore nel ricevere il messaggio: Connessione interrotta dal corrispondente (g-io-error-quark, 44). Exiting.
lug 26 17:32:37 S98RC-PC ca.desrt.dconf[2515]: 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.
lug 26 17:32:37 S98RC-PC org.gtk.vfs.Daemon[2515]: 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.
lug 26 17:32:37 S98RC-PC org.gtk.vfs.Daemon[2515]: A connection to the bus can't be made
lug 26 17:32:37 S98RC-PC org.gtk.vfs.Daemon[2515]: 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.
lug 26 17:32:38 S98RC-PC systemd-coredump[14667]: Process 819 (Xorg) of user 0 dumped core.

Then... I've to say (hoping it's not misleading) that the hardware acceleration seems to be shitty: the "double v" are often omitted, when there are too many texts I see big artifacts (sometimes "very poligonal artworks" ).
Are you having my same troubles with both NVIDIA GM107 videocards and Nouveau driver installed?

Hope you'll be able to help me.

Last edited by Simone98RC (2015-07-26 16:04:27)

jasonwryan · 2015-07-26 19:37:34

Please edit your post to change the title to something descriptive, rather than ranty. Mentioning your graphics card might be a good start, rather than burying it at the bottom of your thread:
https://wiki.archlinux.org/index.php/Fo … ow_to_post

V1del · 2015-07-27 08:47:41

The card is relatively new and nouveau is the least maintained of the free drivers (lack of official documentation, not a high priority because ethics aside the nvidia driver just works) which directly leads to my next suggestion: Why are you not using the propietary nvidia drivers? If you don't want to because you would like to stay with the free drivers because of ethics/belief/whatever, then do so, but you have to live with the consequences, it will get better with time, but if this is the first release which contains hardware accel you can't expect to have everything working immediately (The nouveau devs are working with basically zero documentation and have to reverse engineer everything, which for hardware as complex as a modern graphics adapter, will take time).

If you want to be productive, you could identify issues and report bugs for them to be fixed in future releases.

Simone98RC · 2015-07-28 09:48:47

jasonwryan wrote:

Please edit your post to change the title to something descriptive, rather than ranty. Mentioning your graphics card might be a good start, rather than burying it at the bottom of your thread:
https://wiki.archlinux.org/index.php/Fo … ow_to_post

I've specified the videocard name just in the first part of my post (where I speak about the kernel update).

V1del wrote:

The card is relatively new and nouveau is the least maintained of the free drivers (lack of official documentation, not a high priority because ethics aside the nvidia driver just works) which directly leads to my next suggestion: Why are you not using the propietary nvidia drivers? If you don't want to because you would like to stay with the free drivers because of ethics/belief/whatever, then do so, but you have to live with the consequences, it will get better with time, but if this is the first release which contains hardware accel you can't expect to have everything working immediately (The nouveau devs are working with basically zero documentation and have to reverse engineer everything, which for hardware as complex as a modern graphics adapter, will take time).
If you want to be productive, you could identify issues and report bugs for them to be fixed in future releases.

I hope you're right, Arch is an evolving distro and I use to constantly attend updates.
Find that I've a bad Xorg configuration or some unknown sw which have conflicts would be a terrible discovering.

To diagnose the issue what can I do, given that I won't to install NVIDIA drivers? I've few experience in the Arch world, in these cases the only useful source I know is the syslog (accessible via journalctl command).

jasonwryan · 2015-07-28 09:52:30

jasonwryan wrote:

Please edit your post to change the title to something descriptive, rather than ranty.

I asked nicely.

Trilby · 2015-07-28 10:48:09

Simone, very few people are going to read that top part of your post to see the video driver and other information. Many users scan titles first. If you put relevant information in the title, you will get the right people to read your thread.

As is, I suspect the majority of people who bother to read this thread will either be curious about how big of a train wreck it will be, or they will be forum moderators checking whether it should be binned. I must admit, I fall into both categories. Your title is your first impression. My role here dissuades me from elaborating exactly what first impression this title gives, but I can say it is not a positive one.

clfarron4 · 2015-07-28 10:55:46

You've associated it with the 4.1.2 kernel update.

Have you tried downgrading that (along with the necessary packages) to confirm it's actually the kernel and not something else?

Last edited by clfarron4 (2015-07-28 10:56:00)

Arch Linux

#1 2015-07-26 15:55:15

Welcome to the Xorg Hell: many crashes in too many occasions

#2 2015-07-26 19:37:34

Re: Welcome to the Xorg Hell: many crashes in too many occasions

#3 2015-07-27 08:47:41

Re: Welcome to the Xorg Hell: many crashes in too many occasions

#4 2015-07-28 09:48:47

Re: Welcome to the Xorg Hell: many crashes in too many occasions

#5 2015-07-28 09:52:30

Re: Welcome to the Xorg Hell: many crashes in too many occasions

#6 2015-07-28 10:48:09

Re: Welcome to the Xorg Hell: many crashes in too many occasions

#7 2015-07-28 10:55:46

Re: Welcome to the Xorg Hell: many crashes in too many occasions

Board footer