- Package:
- light-locker
- Source:
- light-locker
- Description:
- simple screen locker for lightDM display manager
- Submitter:
- Francois Mescam
- Date:
- 2023-07-24 15:09:03 UTC
- Severity:
- normal
Dear Maintainer, In the logs I observe messages for coredump about light-locker : Jun 29 20:50:54 eiffel7 systemd-coredump[3646]: Process 3616 (light-locker) of user 1000 dumped core.#012#012Module libsystemd.so.0 from deb systemd-252.11-1.amd64#012Stack trace of thread 3616:#012#0 0x00007f7e30bf87d7 g_log_structured_array (libglib-2.0.so.0 + 0x5b7d7)#012#1 0x00007f7e30bf8bfe g_log_default_handler (libglib-2.0.so.0 + 0x5bbfe)#012#2 0x00007f7e30bf8e67 g_logv (libglib-2.0.so.0 + 0x5be67)#012#3 0x00007f7e30bf90ff g_log (libglib-2.0.so.0 + 0x5c0ff)#012#4 0x000055e5ed1d2085 n/a (light-locker + 0xb085)#012#5 0x00007f7e30d0cde9 g_type_create_instance (libgobject-2.0.so.0 + 0x37de9)#012#6 0x00007f7e30cf0d30 n/a (libgobject-2.0.so.0 + 0x1bd30)#012#7 0x00007f7e30cf23fc g_object_new_with_properties (libgobject-2.0.so.0 + 0x1d3fc)#012#8 0x00007f7e30cf3001 g_object_new (libgobject-2.0.so.0 + 0x1e001)#012#9 0x000055e5ed1d48e2 gs_listener_new (light-locker + 0xd8e2)#012#10 0x000055e5ed1d04c2 n/a (light-locker + 0x94c2)#012#11 0x00007f7e30d0cde9 g_type_create_instance (libgobject-2.0.so.0 + 0x37de9)#012#12 0x00007f7e30cf0d30 n/a (libgobject-2.0.so.0 + 0x1bd30)#012#13 0x00007f7e30cf23fc g_object_new_with_properties (libgobject-2.0.so.0 + 0x1d3fc)#012#14 0x00007f7e30cf3001 g_object_new (libgobject-2.0.so.0 + 0x1e001)#012#15 0x000055e5ed1d0b02 gs_monitor_new (light-locker + 0x9b02)#012#16 0x000055e5ed1cf3fa main (light-locker + 0x83fa)#012#17 0x00007f7e308fe18a n/a (libc.so.6 + 0x2718a)#012#18 0x00007f7e308fe245 __libc_start_main (libc.so.6 + 0x27245)#012#19 0x000055e5ed1cf54a _start (light-locker + 0x854a)#012#012Stack trace of thread 3630:#012#0 0x00007f7e309d2fff __poll (libc.so.6 + 0xfbfff)#012#1 0x00007f7e30bf19ae n/a (libglib-2.0.so.0 + 0x549ae)#012#2 0x00007f7e30bf1acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)#012#3 0x00007f7e30bf1b11 n/a (libglib-2.0.so.0 + 0x54b11)#012#4 0x00007f7e30c1bcfd n/a (libglib-2.0.so.0 + 0x7ecfd)#012#5 0x00007f7e3095ffd4 n/a (libc.so.6 + 0x88fd4)#012#6 0x00007f7e309e05bc n/a (libc.so.6 + 0x1095bc)#012#012Stack trace of thread 3633:#012#0 0x00007f7e309d2fff __poll (libc.so.6 + 0xfbfff)#012#1 0x00007f7e30bf19ae n/a (libglib-2.0.so.0 + 0x549ae)#012#2 0x00007f7e30bf1cef g_main_loop_run (libglib-2.0.so.0 + 0x54cef)#012#3 0x00007f7e30ea28f6 n/a (libgio-2.0.so.0 + 0x1188f6)#012#4 0x00007f7e30c1bcfd n/a (libglib-2.0.so.0 + 0x7ecfd)#012#5 0x00007f7e3095ffd4 n/a (libc.so.6 + 0x88fd4)#012#6 0x00007f7e309e05bc n/a (libc.so.6 + 0x1095bc)#012#012Stack trace of thread 3631:#012#0 0x00007f7e309d2fff __poll (libc.so.6 + 0xfbfff)#012#1 0x00007f7e30bf19ae n/a (libglib-2.0.so.0 + 0x549ae)#012#2 0x00007f7e30bf1acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)#012#3 0x00007f7e2fa064bd n/a (libdconfsettings.so + 0xb4bd)#012#4 0x00007f7e30c1bcfd n/a (libglib-2.0.so.0 + 0x7ecfd)#012#5 0x00007f7e3095ffd4 n/a (libc.so.6 + 0x88fd4)#012#6 0x00007f7e309e05bc n/a (libc.so.6 + 0x1095bc)#012ELF object binary architecture: AMD x86-64 Jun 29 20:50:54 eiffel7 drkonqi-coredump-launcher[3736]: Nothing handled the dump :O Jun 29 20:50:54 eiffel7 drkonqi-coredump-launcher[3736]: QFile::remove: Empty or null file name Jun 29 20:50:54 eiffel7 drkonqi-coredump-launcher[3736]: Unable to find file for pid 3616 expected at "kcrash-metadata/3616.ini" Jun 29 20:50:54 eiffel7 drkonqi-coredump-processor[3647]: "/usr/bin/light-locker" 3616 "/var/lib/systemd/coredump/core.light-locker.1000.a79dc46db0a3437aa8405f0168a2e653.3616.1688064653000000.zst" I have these messages since somme months for systemd-coredump and only since some weeks for drkonqi. I've not observe problem in relation with these messages. My laptop is updated every day. I work with kde. Regards
Hi,
I just found this coredump in my journal. Like the original reporter,
I'm a user of KDE (on trixie). I removed light-locker to see if I spotted any
change and I'm not seeing it yet.
Paul
Here's the dump:
jul 23 20:11:29 mulciber systemd-coredump[2250]: Process 2157 (light-locker) of user 1000 dumped core.
Module libsystemd.so.0 from deb systemd-253.5-1.amd64
Stack trace of thread 2157:
#0 0x00007f43ad4f6557 g_log_structured_array (libglib-2.0.so.0 + 0x61557)
#1 0x00007f43ad4f69ae g_log_default_handler (libglib-2.0.so.0 + 0x619ae)
#2 0x00007f43ad4f6c20 g_logv (libglib-2.0.so.0 + 0x61c20)
#3 0x00007f43ad4f6ecf g_log (libglib-2.0.so.0 + 0x61ecf)
#4 0x00005570baa14085 n/a (light-locker + 0xb085)
#5 0x00007f43ad61015b g_type_create_instance (libgobject-2.0.so.0 + 0x3815b)
#6 0x00007f43ad5f3e60 n/a (libgobject-2.0.so.0 + 0x1be60)
#7 0x00007f43ad5f5496 g_object_new_with_properties (libgobject-2.0.so.0 + 0x1d496)
#8 0x00007f43ad5f6311 g_object_new (libgobject-2.0.so.0 + 0x1e311)
#9 0x00005570baa168e2 gs_listener_new (light-locker + 0xd8e2)
#10 0x00005570baa124c2 n/a (light-locker + 0x94c2)
#11 0x00007f43ad61015b g_type_create_instance (libgobject-2.0.so.0 + 0x3815b)
#12 0x00007f43ad5f3e60 n/a (libgobject-2.0.so.0 + 0x1be60)
#13 0x00007f43ad5f5496 g_object_new_with_properties (libgobject-2.0.so.0 + 0x1d496)
#14 0x00007f43ad5f6311 g_object_new (libgobject-2.0.so.0 + 0x1e311)
#15 0x00005570baa12b02 gs_monitor_new (light-locker + 0x9b02)
#16 0x00005570baa113fa main (light-locker + 0x83fa)
#17 0x00007f43ad2056ca __libc_start_call_main (libc.so.6 + 0x276ca)
#18 0x00007f43ad205785 __libc_start_main_impl (libc.so.6 + 0x27785)
#19 0x00005570baa1154a _start (light-locker + 0x854a)
Stack trace of thread 2196:
#0 0x00007f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
#1 0x00007f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818)
#2 0x00007f439a50c059 n/a (iris_dri.so + 0x10c059)
#3 0x00007f439a4be17b n/a (iris_dri.so + 0xbe17b)
#4 0x00007f439a50bf97 n/a (iris_dri.so + 0x10bf97)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2199:
#0 0x00007f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
#1 0x00007f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818)
#2 0x00007f439a50c059 n/a (iris_dri.so + 0x10c059)
#3 0x00007f439a4be17b n/a (iris_dri.so + 0xbe17b)
#4 0x00007f439a50bf97 n/a (iris_dri.so + 0x10bf97)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2200:
#0 0x00007f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
#1 0x00007f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818)
#2 0x00007f439a50c059 n/a (iris_dri.so + 0x10c059)
#3 0x00007f439a4be17b n/a (iris_dri.so + 0xbe17b)
#4 0x00007f439a50bf97 n/a (iris_dri.so + 0x10bf97)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2201:
#0 0x00007f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
#1 0x00007f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818)
#2 0x00007f439a50c059 n/a (iris_dri.so + 0x10c059)
#3 0x00007f439a4be17b n/a (iris_dri.so + 0xbe17b)
#4 0x00007f439a50bf97 n/a (iris_dri.so + 0x10bf97)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2202:
#0 0x00007f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
#1 0x00007f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818)
#2 0x00007f439a50c059 n/a (iris_dri.so + 0x10c059)
#3 0x00007f439a4be17b n/a (iris_dri.so + 0xbe17b)
#4 0x00007f439a50bf97 n/a (iris_dri.so + 0x10bf97)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2172:
#0 0x00007f43ad2d99ef __GI___poll (libc.so.6 + 0xfb9ef)
#1 0x00007f43ad4ee85e n/a (libglib-2.0.so.0 + 0x5985e)
#2 0x00007f43ad4ee97c g_main_context_iteration (libglib-2.0.so.0 + 0x5997c)
#3 0x00007f43ad4ee9c1 n/a (libglib-2.0.so.0 + 0x599c1)
#4 0x00007f43ad51ae9d n/a (libglib-2.0.so.0 + 0x85e9d)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2197:
#0 0x00007f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
#1 0x00007f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818)
#2 0x00007f439a50c059 n/a (iris_dri.so + 0x10c059)
#3 0x00007f439a4be17b n/a (iris_dri.so + 0xbe17b)
#4 0x00007f439a50bf97 n/a (iris_dri.so + 0x10bf97)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2198:
#0 0x00007f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
#1 0x00007f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818)
#2 0x00007f439a50c059 n/a (iris_dri.so + 0x10c059)
#3 0x00007f439a4be17b n/a (iris_dri.so + 0xbe17b)
#4 0x00007f439a50bf97 n/a (iris_dri.so + 0x10bf97)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2174:
#0 0x00007f43ad2d99ef __GI___poll (libc.so.6 + 0xfb9ef)
#1 0x00007f43ad4ee85e n/a (libglib-2.0.so.0 + 0x5985e)
#2 0x00007f43ad4eeb9f g_main_loop_run (libglib-2.0.so.0 + 0x59b9f)
#3 0x00007f43ad7aa2c6 n/a (libgio-2.0.so.0 + 0x11c2c6)
#4 0x00007f43ad51ae9d n/a (libglib-2.0.so.0 + 0x85e9d)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2173:
#0 0x00007f43ad2d99ef __GI___poll (libc.so.6 + 0xfb9ef)
#1 0x00007f43ad4ee85e n/a (libglib-2.0.so.0 + 0x5985e)
#2 0x00007f43ad4ee97c g_main_context_iteration (libglib-2.0.so.0 + 0x5997c)
#3 0x00007f43ac2e94bd n/a (libdconfsettings.so + 0xb4bd)
#4 0x00007f43ad51ae9d n/a (libglib-2.0.so.0 + 0x85e9d)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
Stack trace of thread 2171:
#0 0x00007f43ad2deeb9 syscall (libc.so.6 + 0x100eb9)
#1 0x00007f43ad548260 g_cond_wait (libglib-2.0.so.0 + 0xb3260)
#2 0x00007f43ad4b8efb n/a (libglib-2.0.so.0 + 0x23efb)
#3 0x00007f43ad51b4e2 n/a (libglib-2.0.so.0 + 0x864e2)
#4 0x00007f43ad51ae9d n/a (libglib-2.0.so.0 + 0x85e9d)
#5 0x00007f43ad2663ec start_thread (libc.so.6 + 0x883ec)
#6 0x00007f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c)
ELF object binary architecture: AMD x86-64
jul 23 20:11:29 mulciber systemd[1]: systemd-coredump@0-2241-0.service: Deactivated successfully.
Hi Paul, so what you're saying is that you're a KDE user (not Xfce) but you're still using LightDM (not KDM), and light-locker is still started as part of your desktop session. light-locker is autostarted using the XDG/Freedesktop.org specifications so you should be able to prevent it to startup if you have a KDE screen locker (not sure how to do that on KDE though). Right now light-locker autostart ignores GNOME and Unity desktop environment, maybe it'd make sense to ignore KDE as well. In any case, if you don't use it on your box it's quite ok to remove it. Regards,
Hi, Indeed. I'm not aware that I ever did that actively. It seems that also nothing obvious changed for me since I deinstalled light-locker. So everything *looks* like before. I tried to say in my previous message that I already did that. Paul
Yeah I meant before removing it. Yes indeed, I was just saying that it was ok.