On 4 December 2011 23:55, Rob <robpill...@gmail.com> wrote: > On 4 December 2011 22:19, Arian Kuschki <arian.kusc...@googlemail.com> wrote: >> I get a segfault when running slock via my acpi handler script: >> >> Dec 4 23:15:00 localhost kernel: [26284.789539] slock[13389]: >> segfault at 0 ip 00007f12b8b57879 sp 00007fff74d6d810 error 4 in >> libnss_files-2.14.1.so[7f12b8b50000+b000] > > Can you get a coredump and give us a stack trace? > > In your script: > ulimit -c unlimited > Then when slock segfaults, hunt around for a file named "core". > Probably in $HOME > > Then: > $ gdb path/to/slock path/to/core > (gdb) bt > > > You might want to compile slock with debug flags too (replace -s with > -g in config.mk) > Rob
Thanks for the timely response Rob, but I think I found the reason: calling slock like so export DISPLAY=:0 && sudo -u $USER slock in my acpi handler script fixes the problem. So it seems it is not slocks fault, but rather some X-specific knowledge I guess I should have had. Cheers, Arian
