@Jason_Dodd uh, sounds pretty bad. Is it 20180712 from https://ring.cx ? Could you open a bug report on https://git.ring.cx with the crash information from your syslog (/var/log/syslog) ? That would be really helpful 😉

@hle
It is 20180712. I'll see if I can manage to file a bug report

@Jason_Dodd Thanks ! Feel free to ping me if you find something unclear with the bug tracker.

@hle
Actually already reported here.
http://lists.gnu.org/archive/html/ring/2018-07/msg00002.html

@Jason_Dodd Well, Ring should not be able to crash xorg on a normal system. There is certainly an issue in Ring, but not only. Is there something interesting in your syslog ? If the bug is coming from xorg-nouveau, you should be able to find something in there :-)

@hle
Is xorg-nouveau for nvidia? The machine has a radeon card.

@Jason_Dodd I have opened a bug report on our bug tracker, see https://git.ring.cx/savoirfairelinux/ring-daemon/issues/23

It looks like your ring-dev message arrived empty, do you think you could re-send it (if possible in plain-text), cc-ing [email protected], together with the logs ? Thanks !

@hle
Sure. I don't have anything lse to add really. Subject said everything I wanted but I'll resend with /var/log/syslog attacched.

@Jason_Dodd we just had a look at your syslog and answered on the Gitlab issue https://git.ring.cx/savoirfairelinux/ring-daemon/issues/23

@hle
For some reason it's not letting me login with my gitlab account to update the bug so I'll send an email.

@Jason_Dodd what's the problem exactly ? cc @AmarOk

@hle @AmarOk
When I click on login to reply via gitlab i get a message, "
The change you requested was rejected.

Make sure you have access to the thing you tried to change.

Please contact your GitLab administrator if you think this is a mistake."

Let me know if you need more info.

@hle @AmarOk
mesa-va-drivers is already the newest version (13.0.6-1+b2).
mesa-va-drivers set to manually installed.

libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit

@Jason_Dodd @AmarOk just answered on the GL issue 👍

@hle @AmarOk
Thanks. I will be a day or two before I get back to this. But all none of those strings show in lsmod.

One question I have is if there was a change to ring because this happened right when I upgraded to the last version of ring.

@hle @AmarOk
Don't know if this is related but this is a new machine for me, and while don't run kde, I do use ksnapshot. I forgot to install it until just now.

Here's the reason I think it could be related. When I take a shapshot in kde, both monitors go soild white and the desktop is unresponsive except for the mouse.

I know I'm not the only one reporting this issue. But I'm going to reinstall the OS in the next day or two and let you know ring still has problems.

@Jason_Dodd @AmarOk Yep, your libva setup looks somewhat broken, so any app making use of it (potentially including ksnapshot) might very well crash your X11

@hle @AmarOk
I installed nonfree firmware and that seems to have resolved the issue.

I have another issues now. I've somehow lost the window borders and title bar and can't get them back. Is there a key combination to get them back. In firefox it's f11.

@Jason_Dodd @AmarOk So it was most likely an issue in your mesa/vaapi drivers setup.

Concerning the window issue: this is not normal, might be a bug somewhere between Ring, GTK and your WM. You can launch Ring from the command line using "gnome-ring -d", that will output the GTK logs and will let you know if something goes wrong in Ring/GTK.