elementary/triage

Onboard segfaults on hover

Opened this issue · 7 comments

madonuko commented

What Happened?

Onboard (on-screen keyboard) proceeds to segfault when the mouse pointer is above the Window.

Downstream issue: Ultramarine-Linux/triage#25

Steps to Reproduce

  1. Execute the onboard program.
  2. Put your mouse pointer over it. No clicking is needed.
  3. After around 2 seconds, the program segfaults.

Expected Behavior

I guess no segfaults?

OS Version

  • Ultramarine Linux 39 KDE Edition, on Pantheon DE (debug infos provided by me) (Wayland)
  • Ultramarine Linux 39 Pantheon Edition (original issue reporter / tester on immutable OSTree) (uncertain if it's wayland or not)

Software Version

Latest release (I have run all updates)

Log Output

$ onboard
15:07:00.679 WARNING Config: mousetweaks GSettings schema not found, mousetweaks integration disabled.
15:07:00.829 WARNING Indicator: Failed to setup D-Bus match rule, no left-click Activate() for AppIndicator: org.freedesktop.DBus.Error.MatchRuleInvalid: Invalid match rule
zsh: segmentation fault (core dumped)  onboard

Under -d all, there are no related logs as far as I'm concerned.

Note that the 2 warnings are shown on startup, not when I hover my mouse. No logs are shown (not even DEBUG logs under -d all) when I hover my mouse.

The following is the output of coredumpctl debug /usr/bin/python3.12:

          PID: 14166 (onboard)
          UID: 1000 (mado)
          GID: 1000 (mado)
       Signal: 11 (SEGV)
    Timestamp: Sun 2023-12-03 15:30:39 HKT (27s ago)
 Command Line: /usr/bin/python3 -sP /usr/bin/onboard
   Executable: /usr/bin/python3.12
Control Group: /user.slice/user-1000.slice/session-4.scope
         Unit: session-4.scope
        Slice: user-1000.slice
      Session: 4
    Owner UID: 1000 (mado)
      Boot ID: ff9edb65d2434727947e37ca2e1f9699
   Machine ID: 32d77afe9e734b5e93ff06863ac8d371
     Hostname: boibook
      Storage: /var/lib/systemd/coredump/core.onboard.1000.ff9edb65d2434727947e37ca2e1f9699.14166.1701588639000000.zst (present)
 Size on Disk: 5.7M
      Package: python3.12/3.12.0-1.fc39
     build-id: 07023eb4f297ae1d4591ec808ab20b2788c542be
      Message: Process 14166 (onboard) of user 1000 dumped core.

Modules: https://pastebin.com/uhDeUDak

Backtrace: https://pastebin.com/mFfvPXk7

Hardware Info

The above debug information has been provided by me on Linux 6.6.2-201.fc39.x86_64, mutable Pantheon DE (see comps.xml in Terra, @pantheon-desktop group)

The issue has been first reported by another immutable Pantheon DE user on Ultramarine, meaning it has been reproduced on 2 different machines. Furthermore, this has been only reproducable on Pantheon DE, not KDE Plasma (Wayland).

lenemter commented

onboard is an on-screen keyboard Pantheon uses, but it's not developed by elementary. There are plans to replace it later because I think it doesn't work on Wayland.

madonuko commented

it doesn't work on Wayland

Probably not the issue since it works fine on KDE Plasma Wayland on my machine.

  • 👀1
madonuko commented

Oh wait yeah I mixed up onboarding with onboard. My bad. Oops.

lenemter commented

I'll move the issue to triage repo, since elementary OS 8 may also be affected by this.

michimussato commented

Same issue here. Once the keyboard is visible on screen, a mouse hover causes:

$ onboard
23:12:54.071 WARNING Indicator: Failed to setup D-Bus match rule, no left-click Activate() for AppIndicator: org.freedesktop.DBus.Error.MatchRuleInvalid: Invalid match rule
Segmentation fault (core dumped)

OS:

$ neofetch
██████████████████  ████████   michael@pocket3.lan 
██████████████████  ████████   ------------------- 
██████████████████  ████████   OS: Manjaro Linux x86_64 
██████████████████  ████████   Host: G1621-02 
████████            ████████   Kernel: 6.8.12-3-MANJARO 
████████  ████████  ████████   Uptime: 10 mins 
████████  ████████  ████████   Packages: 2319 (pacman), 8 (flatpak) 
████████  ████████  ████████   Shell: bash 5.2.26 
████████  ████████  ████████   Resolution: 2560x1440 
████████  ████████  ████████   DE: Plasma 6.0.5 
████████  ████████  ████████   WM: KWin 
████████  ████████  ████████   Theme: [Plasma], Adwaita [GTK2/3] 
████████  ████████  ████████   Icons: [Plasma], breeze-dark [GTK2/3] 
████████  ████████  ████████   Terminal: konsole 
                               CPU: 11th Gen Intel i7-1195G7 (8) @ 5.000GHz 
                               GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] 
                               Memory: 2869MiB / 15772MiB
MichaelMacha commented

I'm having the same issue on KUbuntu 24.04; it's been temporarily mitigated by going into Onboard options and switching from XInput (the default) to GTK. It now works as intended.

  • 👍1
michimussato commented

Can confirm @MichaelMacha 's workaround. GTK seems fine whereas Xinput crashes.