Now tracking in:
https://errors.ubuntu.com/problem/7f251293da8ec10d19879691e89ba59543341b25
https://errors.ubuntu.com/problem/574b901b7cc110aa63cf17a216cbd35a81033d1b
** Description changed:
+ https://errors.ubuntu.com/problem/7f251293da8ec10d19879691e89ba59543341b25
+ https://errors.ubuntu.com
Annoyingly, around 50 reports of the crash on bionic is still not enough
for it to make it into the top 100 xorg-server crashes on bionic. So not
easy to find.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760104
Title:
** Summary changed:
- Xorg crashed with SIGSEGV
+ Xorg crashed with SIGSEGV in InputReady() from ospoll_wait() from
InputThreadDoWork()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760104
Title:
So, the pauses I am experiencing is likely due to simply the fact that
the keyboards and mice are being removed then added back, which is a
different issue than the crashes (which appear nvidia related). I will
likely create a PR to only trigger the input subsystem on an as-needed
base to reduce th
I had some luck with this not pausing/blinking gnome-shell:
$ sudo udevadm control --reload-rules
$ sudo udevadm trigger --subsystem-nomatch=input
$ sudo udevadm trigger --property-match=ID_INPUT_JOYSTICK=1
Alan, perhaps you can upgrade to core from edge (since it does some
things with ID_INPUT_J
I noticed I could prevent gnome-shell from blinking/pausing if instead
of 'sudo udevadm control --reload-rules && sudo udevadm trigger' I
instead did 'sudo udevadm control --reload-rules && sudo udevadm trigger
--subsystem-nomatch=input'. I'm not sure there is much that snapd can do
with that infor
I suspect this is because snapd will do 'sudo udevadm control --reload-
rules && sudo udevadm trigger' on interface connections. These
operations are supposed to be safe but I've seen with my Intel graphics
that gnome-shell/X11 will blink when this happens (due to the 'udevadm
trigger') but it does
Just had this again.
https://errors.ubuntu.com/oops/0c692c82-643d-11e8-b7b3-fa163e8d4bab
Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
Is the error I see in the xorg crash reports. I
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760
I've had this again. Here's the crash report links.
May 23rd: https://errors.ubuntu.com/oops/18a718fc-5e7e-11e8-a6ec-fa163ed44aae
May 10th: https://errors.ubuntu.com/oops/274be904-57ae-11e8-9ec0-fa163ef911dc
Feb 27th: https://errors.ubuntu.com/oops/1ce27eb4-1ba0-11e8-a91a-fa163e8d4bab
Error: [Err
I've just installed a snap and experienced this issue. The snap is a
game using the opengl interface and immediately after the install the
entire desktop UI locked up, Xorg crashed and I was returned to the
display manager. Here is the associated error report:
* https://errors.ubuntu.com/oops/97
I've added a task for snapd, because this only happens when I'm doing
"snap install" something. Usually at the point when it connects the
opengl interface.
** Information type changed from Private to Public
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this
13 matches
Mail list logo
