Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44085 - [light-locker] core dumps when invoked

Attached to Project: Community Packages
Opened by John (graysky) - Saturday, 07 March 2015, 16:21 GMT
Last edited by Maxime Gauduin (Alucryd) - Sunday, 07 February 2016, 14:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I find light-locker core dumping when I try to use it on xfce4. Another user has confirmed this on an independent system[1].

1. https://bbs.archlinux.org/viewtopic.php?pid=1509029

Additional info:
* package version(s) 1.6.0-1

Steps to reproduce:
1) Log into xfce4 and install light-locker.
2) Run light-locker.

% light-locker
process 1737: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1340.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
[1] 1737 abort (core dumped) light-locker
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Sunday, 07 February 2016, 14:46 GMT
Reason for closing:  Not a bug
Comment by John (graysky) - Saturday, 07 March 2015, 16:22 GMT
Sorry about the blank title... that I pasted something in there. It should read: [light-locker] - core dumps when invoked.
Comment by Maxime Gauduin (Alucryd) - Sunday, 08 March 2015, 07:41 GMT
It would seem the same issue has been reported upstream already https://github.com/the-cavalry/light-locker/issues/36. I just left a message there, let's wait for an answer.
Comment by Trey Blancher (ectospasm) - Wednesday, 30 December 2015, 23:51 GMT
It seems this bug is in lightdm, it's not setting the XDG_SESSION_PATH environment variable, thus light-locker crashes. That would explain why my X session appears to completely hose when dm-tool lock is called on light-locker.
Comment by Maxime Gauduin (Alucryd) - Sunday, 07 February 2016, 10:04 GMT
lightdm sets XDG_SESSION_PATH fine here, do you still encounter this bug?
Comment by John (graysky) - Sunday, 07 February 2016, 12:09 GMT
@alucrdy - No, still does not run:

% light-locker
process 7897: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1340.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
[1] 7897 abort (core dumped) light-locker
Comment by Maxime Gauduin (Alucryd) - Sunday, 07 February 2016, 13:56 GMT
Which greeter are you using?
Comment by Trey Blancher (ectospasm) - Sunday, 07 February 2016, 14:11 GMT
I'm using the lightdm-gtk-greeter 1:2.0.1-2
Comment by Trey Blancher (ectospasm) - Sunday, 07 February 2016, 14:36 GMT
Yeah, I don't know how to get any handle on what's going on here. I issue "light-locker-command --lock", and lightdm appears to crash. It screws up my virtual terminals (vt1-vt7), such that I need to log in via SSH from another device and restart lightdm. Every time on this system I get a rapidly blinking cursor screen. As I switch to the various VTs, I see the login prompt only for a brief second, then the rapidly blinking cursor appears again.

I don't know how to troubleshoot this. This is one of only two Arch systems I have, and this one is the only one affected.
Comment by Maxime Gauduin (Alucryd) - Sunday, 07 February 2016, 14:37 GMT
Just tried launching an xfce4 session using the GTK greeter, light-locker doesn't core dump and works fine. What does XDG_SESSION_PATH contain, are you messing with it somewhere? Does light-locker --debug produce the same error as in the upstream issue above?
Comment by John (graysky) - Sunday, 07 February 2016, 14:37 GMT
I'm using lxdm.
Comment by Maxime Gauduin (Alucryd) - Sunday, 07 February 2016, 14:46 GMT
graysky: ... I didn't put lightdm in light-locker's depends array just for show. The upstream issue I posted above even mentions that light-locker only works with lightdm.

ectospasm: Your issue is probably unrelated to this, if your XDG_SESSION_PATH was borked, light-locker woudln't even run and light-locker-command would do nothing. I doubt this is a packaging issue, please ask if upstream has any idea and file another bug here if it's somehow our fault.

In any case, I'm closing this one.

Loading...