You are not logged in.

#1 2026-05-19 07:39:06

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

LXQt error message

good morning,

everytime, when i start my pc, i have this error message ...

           PID: 3126 (light-locker)
           UID: 1000 (henni)
           GID: 984 (users)
        Signal: 6 (ABRT)
     Timestamp: Tue 2026-05-19 09:39:57 CEST (21s ago)
  Command Line: /usr/bin/light-locker
    Executable: /usr/bin/light-locker
 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: 48470831df3743d4be9fccc9b908c90c
    Machine ID: 69ad4b747e54426da021db74cc20801d
      Hostname: lo79pc
       Storage: /var/lib/systemd/coredump/core.light-locker.1000.48470831df3743d4be9fccc9b908c90c.3126.1779176397000000.zst (present)
  Size on Disk: 1M
       Message: Process 3126 (light-locker) of user 1000 dumped core.
                
                Stack trace of thread 3126:
                #0  0x00007fc94349a29c n/a (libc.so.6 + 0x9a29c)
                #1  0x00007fc94343e7d0 raise (libc.so.6 + 0x3e7d0)
                #2  0x00007fc943425681 abort (libc.so.6 + 0x25681)
                #3  0x00007fc9445900fc n/a (libglib-2.0.so.0 + 0x1e0fc)
                #4  0x00007fc9445da2a2 g_log_default_handler (libglib-2.0.so.0 + 0x682a2)
                #5  0x00007fc9445da5c6 g_logv (libglib-2.0.so.0 + 0x685c6)
                #6  0x00007fc9445da924 g_log (libglib-2.0.so.0 + 0x68924)
                #7  0x0000564f3d636836 n/a (/usr/bin/light-locker + 0xb836)
                #8  0x00007fc944714d21 g_type_create_instance (libgobject-2.0.so.0 + 0x3fd21)
                #9  0x00007fc9446f9905 n/a (libgobject-2.0.so.0 + 0x24905)
                #10 0x00007fc9446fb157 g_object_new_with_properties (libgobject-2.0.so.0 + 0x26157)
                #11 0x00007fc9446fc132 g_object_new (libgobject-2.0.so.0 + 0x27132)
                #12 0x0000564f3d638010 n/a (/usr/bin/light-locker + 0xd010)
                #13 0x00007fc944714d21 g_type_create_instance (libgobject-2.0.so.0 + 0x3fd21)
                #14 0x00007fc9446f9905 n/a (libgobject-2.0.so.0 + 0x24905)
                #15 0x00007fc9446fb157 g_object_new_with_properties (libgobject-2.0.so.0 + 0x26157)
                #16 0x00007fc9446fc132 g_object_new (libgobject-2.0.so.0 + 0x27132)
                #17 0x0000564f3d631372 n/a (/usr/bin/light-locker + 0x6372)
                #18 0x00007fc943427741 n/a (libc.so.6 + 0x27741)
                #19 0x00007fc943427879 __libc_start_main (libc.so.6 + 0x27879)
                #20 0x0000564f3d631be5 n/a (/usr/bin/light-locker + 0x6be5)
                
                Stack trace of thread 3189:
                #0  0x00007fc9434a0a52 n/a (libc.so.6 + 0xa0a52)
                #1  0x00007fc943494abc n/a (libc.so.6 + 0x94abc)
                #2  0x00007fc943494b04 n/a (libc.so.6 + 0x94b04)
                #3  0x00007fc94350fff6 ppoll (libc.so.6 + 0x10fff6)
                #4  0x00007fc9445d5edf n/a (libglib-2.0.so.0 + 0x63edf)
                #5  0x00007fc9445d5fe5 g_main_context_iteration (libglib-2.0.so.0 + 0x63fe5)
                #6  0x00007fc9445d6032 n/a (libglib-2.0.so.0 + 0x64032)
                #7  0x00007fc94460cad4 n/a (libglib-2.0.so.0 + 0x9aad4)
                #8  0x00007fc9434981b9 n/a (libc.so.6 + 0x981b9)
                #9  0x00007fc94351d21c n/a (libc.so.6 + 0x11d21c)
                
                Stack trace of thread 3190:
                #0  0x00007fc9434a0a52 n/a (libc.so.6 + 0xa0a52)
                #1  0x00007fc943494abc n/a (libc.so.6 + 0x94abc)
                #2  0x00007fc943494b04 n/a (libc.so.6 + 0x94b04)
                #3  0x00007fc94350fff6 ppoll (libc.so.6 + 0x10fff6)
                #4  0x00007fc9445d5edf n/a (libglib-2.0.so.0 + 0x63edf)
                #5  0x00007fc9445d5fe5 g_main_context_iteration (libglib-2.0.so.0 + 0x63fe5)
                #6  0x00007fc94223a7be n/a (libdconfsettings.so + 0x77be)
                #7  0x00007fc94460cad4 n/a (libglib-2.0.so.0 + 0x9aad4)
                #8  0x00007fc9434981b9 n/a (libc.so.6 + 0x981b9)
                #9  0x00007fc94351d21c n/a (libc.so.6 + 0x11d21c)
                
                Stack trace of thread 3192:
                #0  0x00007fc9434a0a52 n/a (libc.so.6 + 0xa0a52)
                #1  0x00007fc943494abc n/a (libc.so.6 + 0x94abc)
                #2  0x00007fc943494b04 n/a (libc.so.6 + 0x94b04)
                #3  0x00007fc94350fff6 ppoll (libc.so.6 + 0x10fff6)
                #4  0x00007fc9445d5edf n/a (libglib-2.0.so.0 + 0x63edf)
                #5  0x00007fc9445d61a7 g_main_loop_run (libglib-2.0.so.0 + 0x641a7)
                #6  0x00007fc943991974 n/a (libgio-2.0.so.0 + 0x127974)
                #7  0x00007fc94460cad4 n/a (libglib-2.0.so.0 + 0x9aad4)
                #8  0x00007fc9434981b9 n/a (libc.so.6 + 0x981b9)
                #9  0x00007fc94351d21c n/a (libc.so.6 + 0x11d21c)
                
                Stack trace of thread 3193:
                #0  0x00007fc94351af9d syscall (libc.so.6 + 0x11af9d)
                #1  0x00007fc944603f1c g_cond_wait_until (libglib-2.0.so.0 + 0x91f1c)
                #2  0x00007fc944598517 n/a (libglib-2.0.so.0 + 0x26517)
                #3  0x00007fc94459868f g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x2668f)
                #4  0x00007fc94460ddf1 n/a (libglib-2.0.so.0 + 0x9bdf1)
                #5  0x00007fc94460cad4 n/a (libglib-2.0.so.0 + 0x9aad4)
                #6  0x00007fc9434981b9 n/a (libc.so.6 + 0x981b9)
                #7  0x00007fc94351d21c n/a (libc.so.6 + 0x11d21c)
                
                Stack trace of thread 3191:
                #0  0x00007fc94351af9d syscall (libc.so.6 + 0x11af9d)
                #1  0x00007fc9446030de g_cond_wait (libglib-2.0.so.0 + 0x910de)
                #2  0x00007fc94459854d n/a (libglib-2.0.so.0 + 0x2654d)
                #3  0x00007fc9445985c6 g_async_queue_pop (libglib-2.0.so.0 + 0x265c6)
                #4  0x00007fc94365551c n/a (libpangoft2-1.0.so.0 + 0xc51c)
                #5  0x00007fc94460cad4 n/a (libglib-2.0.so.0 + 0x9aad4)
                #6  0x00007fc9434981b9 n/a (libc.so.6 + 0x981b9)
                #7  0x00007fc94351d21c n/a (libc.so.6 + 0x11d21c)
                
                Stack trace of thread 3188:
                #0  0x00007fc94351af9d syscall (libc.so.6 + 0x11af9d)
                #1  0x00007fc9446030de g_cond_wait (libglib-2.0.so.0 + 0x910de)
                #2  0x00007fc94459854d n/a (libglib-2.0.so.0 + 0x2654d)
                #3  0x00007fc94460cfd7 n/a (libglib-2.0.so.0 + 0x9afd7)
                #4  0x00007fc94460cad4 n/a (libglib-2.0.so.0 + 0x9aad4)
                #5  0x00007fc9434981b9 n/a (libc.so.6 + 0x981b9)
                #6  0x00007fc94351d21c n/a (libc.so.6 + 0x11d21c)
                ELF object binary architecture: AMD x86-64

do anyone here, what that is? and how i can correct it?

Offline

#2 2026-05-19 08:42:10

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,033

Re: LXQt error message

light-locker is not lxqt related, it is intended to be used together with the lightDM display manager .

Are you using lightDM and if so do you need the functionality light-locker offers ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2026-05-19 11:54:55

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

Re: LXQt error message

thanks for answer ... smile

i use gnome login manager ...

what should i do? which options do i have?

Offline

#4 2026-05-19 13:55:35

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

Re: LXQt error message

Switch to lightdm or remove light-locker?
Fwii, GDM can no longer launch X11 sessions, so you're most likely running some wayland session but lightdm/light-locker will require X11

Offline

#5 2026-05-20 10:33:41

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,033

Re: LXQt error message

lxqt has some support for wayland sessions[1] , so in theory it could be started from GDM.

[1] https://lxqt-project.org/wiki/Wayland-Session.html


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#6 2026-05-23 13:11:14

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

Re: LXQt error message

i have deinstalled light-locker, now error message is gone.

problem is gone.

Offline

#7 2026-05-24 10:00:02

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,033

Re: LXQt error message

In case you're ok with the outcome please prepend [Solved] to the thread title (edit first post).


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB