You are not logged in.

#1 2026-07-03 13:07:37

lo7777799
Member
Registered: 2023-07-25
Posts: 88

permanently repeating error message

good afternoon,

i use lxqt with wayland. i have that error message ...

           PID: 44546 (glycin-image-rs)
           TID: 44546 (glycin-image-rs)
           UID: 1000 (henni)
           GID: 984 (users)
        Signal: 31 (SYS)
     Timestamp: Fri 2026-07-03 15:07:31 CEST (14s ago)
  Command Line: /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 155
    Executable: /usr/lib/glycin-loaders/2+/glycin-image-rs
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (henni)
       Boot ID: 89fff9bfe94346debb7d1dbb8bd7e804
    Machine ID: 69ad4b747e54426da021db74cc20801d
      Hostname: lo79pc
       Storage: /var/lib/systemd/coredump/core.glycin-image-rs.1000.89fff9bfe94346debb7d1dbb8bd7e804.44546.1783084051000000.zst (present)
  Size on Disk: 50K
       Message: Process 44546 (glycin-image-rs) of user 1000 dumped core.
                
                Stack trace of thread 2:
                #0  0x00005629ddc425bb n/a (glycin-image-rs + 0x28d5bb)
                #1  0x00005629ddb6fe9a n/a (glycin-image-rs + 0x1bae9a)
                #2  0x00005629ddbb660e n/a (glycin-image-rs + 0x20160e)
                #3  0x00005629ddbfe2a6 n/a (glycin-image-rs + 0x2492a6)
                #4  0x00005629ddcecc19 n/a (glycin-image-rs + 0x337c19)
                #5  0x00007f8fb6627741 n/a (libc.so.6 + 0x27741)
                #6  0x00007f8fb6627879 __libc_start_main (libc.so.6 + 0x27879)
                #7  0x00005629ddae5fe5 n/a (glycin-image-rs + 0x130fe5)
                ELF object binary architecture: AMD x86-64

my computer is very slow, when i got this message. i often get that error message.

Offline

#2 2026-07-03 13:17:00

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,836

Re: permanently repeating error message

That's not an error message but a coredump - if there's actually an error message about what's wrong that might help.
Otherwise see https://wiki.archlinux.org/title/Core_d … _core_dump and make sure to use https://wiki.archlinux.org/title/Debuginfod

SIGSYS implies the invocation of some protected system call, do you harden the system (hardened kernel, apparmor, selinux, firejail, …)?

Offline

Board footer

Powered by FluxBB