[Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
For a while I stopped using Plover to avoid this issue, then I tried using it again and nothing crashed. After using it more times and Xorg still not crashing I think the bug seems to at least have stopped affecting me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
It happened again, this time on the Lubuntu desktop, and this time I'm pretty sure there was a crash file with "xorg" in the name, but running ubuntu-bug might just have renamed it without sending anything... Anyway, it seems it wasn't the only thing that crashed, so might as well give you the link to the error report that does appear to have got sent: https://errors.ubuntu.com/oops/2138bbc8-8b76-11ec-87d9-fa163e6cac46 That probably doesn't help a lot. But yeah, mentioning that something else seems to have crashed at the same time seems like the type of thing that probably doesn't matter but maybe it does. I've also heard from another person who got the crash today, not sure if that was on Ubuntu or something else (I do hope distributions have some coordination rather than fixing the bugs independently of each other, but I've started to wonder if they do). If it is getting annoying that I tell you every time I notice anything new, it's okay to tell me to stop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
I tried to use the Plasma (x11) desktop (installed the kubuntu-desktop package) and I got the crash there too, and I think I already mentioned it happen on GNOME (Ubuntu, manually installed the ubuntu-desktop package) and LXQt (Lubuntu). Well, someone else seems to have got a crash under similar circumstances but using KDE on Manjaro, and for them Xorg actually logged some error messages. And they reported it to Plover: https://github.com/openstenoproject/plover/issues/1479 I'm aware that Manjaro might have a slightly different version of Xorg, but I figured it was worth mentioning that this has happened to someone on another distro too, and that unlike me they got this in the Xorg logs: [ 14208.301] (EE) Segmentation fault at address 0x7ffd98866000 in case that helps with anything. ** Bug watch added: github.com/openstenoproject/plover/issues #1479 https://github.com/openstenoproject/plover/issues/1479 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
Today I got sent back to the login screen in the same way, same symptoms, same circumstances as last time (writing text into Firefox using Plover), and this is after upgrading to 21.10. However, I can't see a crash file from Xorg, only a _usr_bin_lxqt-panel.1000.crash. This time I was using the Lubuntu desktop rather than the (GNOME) Ubuntu one where I had been getting a different bug that made it look like I made a bunch of typos. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
Still less than twenty-four hours since the upgrade, still no crashes after it. But I found a workaround for the missing characters bug. Just switch to the Lubuntu desktop instead of the (GNOME) Ubuntu one. Might still want to report that bug to IBus or Xorg or whatever was causing the keypresses to get lost. So if you know how to figure out which package I should be reporting it about, that would be nice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
I upgraded to 21.10 yesterday, but haven't used it long enough to know for sure if the crash also happens here. And it switched to Wayland, which doesn't really solve the problem, since Plover isn't currently compatible with it. But I switched to Xorg and haven't got any Xorg crashes on 21.10 so far. However I did get another bug, which I'm not sure which package is in. Sometimes a word or phrase written with a single chord on the keyboard will come out with some characters missing, or backspacing gets messed up. This seems to be happening only with charcters that appear several times in the thing I'm writing, so if I write "teen princess", it might get turned into "ten princes" with the repeated e and s removed. Teen teen teen teen teen teen teen teen teen teen teen teen teen teen teen teen teen. Well, I guess it's not happening right now, at least on that word. There are there are there are ther are there are. Well, one of the there's got an e to little, so that's the type of issue. Where would I report that? It happens when I use Plover, but when I try to check what Plover is trying to outpt, it's sending the right keypresses, so it's something that processes them later tha's getting rid of some characters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
Possibly fixed after 20.04? I might try upgrading some day I have plenty of time then. If I then stop getting the crashes, I could mention that here. And if I still get them, I guess I could mention that. It's pretty random when it happens, but I guess it should happen at least once per month, especially if I type a lot or install certain Plover plugins (system switcher and VLC commands). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958444] Re: Xorg sometimes seems to crash when Plover is running
The crash took some time to happen again, but happened a moment ago. It does seem pretty inconsistent, and I was starting to think of unplugging the keyboard and plugging it in again to see if that would cause it, or reinstall those Plover plugins that seemed to make it happen much more often when they were installed than when they weren't. But now that it happened, I tried following the steps above. So I followed step 1, and it exits without telling me an ID. I followed step 2, and it shows several crashes, the most recent is in xserver-xorg-core, links to https://errors.ubuntu.com/oops/7990b650-763f-11ec-83e8-fa163e6cac46 and says it was received on 2022-01-15 20:01 UTC. I hope that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958444 Title: Xorg sometimes seems to crash when Plover is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958444] [NEW] Xorg sometimes seems to crash when Plover is running
Public bug reported: If I'm typing text into an application like gedit or Firefox using Plover, I occasionally get a screen freeze, then a black screen, and then I'm thrown back to the login screen, and all applications seem to get closed. I think I first noticed this in March 2021, but at that time, removing some Plover plugins that I had installed (system switcher and VLC controls) seemed to make it stop happen, at least for a while. There's also been some time in the middle where I rarely used Plover. It seems Plover isn't seeing anything going wrong. I'm using the version of Plover that's in Ubuntu's repositories. But now it seems to happen pretty often again. Symptoms: The crashes only happen when I'm typing text using Plover. At random but pretty frequent times (I think it's more than once every 2000 words), I will press a chord, release it, nothing will happen for a moment (I think I've tried moving the mouse and finding it didn't move), then I briefly get a black screen and then I'm back at the login screen. No sign of being logged in. I can type my password on qwerty, Plover isn't running. And when I'm logged in, all applications, including Plover and the one I was typing into, are closed. System: Ubuntu 20.04.3 LTS Xorg: 1:7.7+19ubuntu14 (if I understood correctly how to get the version number) Other: I got a software update today, and haven't had any crashes today so far, but I'm not sure Xorg was among the updated packages. And once I started typing this report and realized it could theoretically have been fixed today without me noticing, I decided to finish submitting the report so that I don't have to start over typing it. I'm typing it on qwerty so that I don't get any crashes while typing it. I looked through the last part of Xorg0.log right after logging back in after a crash: [ 13245.576] (II) config/udev: Adding input device Corsair Corsair K65 Gaming Keyboard (/dev/input/event14) [ 13245.576] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "libinput keyboard catchall" [ 13245.576] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "system-keyboard" [ 13245.576] (II) Using input driver 'libinput' for 'Corsair Corsair K65 Gaming Keyboard' [ 13245.578] (II) systemd-logind: got fd for /dev/input/event14 13:78 fd 25 paused 1 [ 13245.578] (II) systemd-logind: releasing fd for 13:78 [ 13245.607] (II) config/udev: Adding input device Corsair Corsair K65 Gaming Keyboard (/dev/input/event13) [ 13245.607] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "libinput keyboard catchall" [ 13245.607] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "system-keyboard" [ 13245.607] (II) Using input driver 'libinput' for 'Corsair Corsair K65 Gaming Keyboard' [ 13245.609] (II) systemd-logind: got fd for /dev/input/event13 13:77 fd 25 paused 1 [ 13245.609] (II) systemd-logind: releasing fd for 13:77 [ 13245.646] (II) config/udev: Adding input device Corsair Corsair K65 Gaming Keyboard (/dev/input/event12) [ 13245.646] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "libinput keyboard catchall" [ 13245.646] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "system-keyboard" [ 13245.646] (II) Using input driver 'libinput' for 'Corsair Corsair K65 Gaming Keyboard' [ 13245.648] (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 25 paused 1 [ 13245.648] (II) systemd-logind: releasing fd for 13:76 [ 27639.231] (II) UnloadModule: "libinput" [ 27639.231] (II) systemd-logind: releasing fd for 13:67 [ 27639.363] (II) UnloadModule: "libinput" [ 27639.363] (II) systemd-logind: releasing fd for 13:69 [ 27639.398] (II) UnloadModule: "libinput" [ 27639.398] (II) systemd-logind: releasing fd for 13:70 [ 27639.422] (II) UnloadModule: "libinput" [ 27639.422] (II) systemd-logind: releasing fd for 13:71 [ 27639.442] (II) UnloadModule: "libinput" [ 27639.442] (II) systemd-logind: releasing fd for 13:75 [ 27639.462] (II) UnloadModule: "libinput" [ 27639.462] (II) systemd-logind: releasing fd for 13:65 [ 27639.486] (II) UnloadModule: "libinput" [ 27639.486] (II) systemd-logind: releasing fd for 13:68 [ 27639.506] (II) UnloadModule: "libinput" [ 27639.691] (II) systemd-logind: releasing fd for 13:66 [ 27639.784] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [ 27639.784] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [ 27639.784] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [ 27639.785] (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 19:16:52 2022 DistUpgraded: Fresh install DistroCodename:
