On Sat, Apr 04, 2015 at 14:43:23 +0100, Ian Campbell wrote: > On Sat, 2015-04-04 at 14:48 +0200, reportbug wrote: > [...] > > Apr 02 12:08:28 hostname qcontrol[617]: qcontrol 0.5.4 daemon starting. > > Apr 02 12:08:28 hostname qcontrold[480]: Starting qcontrol daemon: qcontrol. > > Apr 02 12:08:28 hostname qcontrol[617]: evdev: Error opening > > /dev/input/by-path/platform-gpio-keys-event: No such file or directory > > Apr 02 12:08:28 hostname qcontrol[617]: register() - Error loading module > > I think this is probably the root cause, this path doesn't exist for > some reason, so qcontrold doesn't start. > > Do you have that device path now? I suppose you must since a later > manual start of qcontrold worked. If not then do you have anything > similar (i.e. "tr - _" perhaps)?
I do, it is a symlink to "../event0": 0 lrwxrwxrwx 1 root root 9 2015-04-02 12:08 /dev/input/by-path/platform-gpio-keys-event -> ../event0 When I do a stat on this "/dev/input/event0" file, it curiously displays a filestamp being one second later than the qcontrol journalctl error entries: % stat /dev/input/event0 File: '/dev/input/event0' Size: 0 Blocks: 0 IO Block: 4096 character special file Device: 5h/5d Inode: 5272 Links: 1 Device type: d,40 Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 113/ input) Access: 2015-04-02 12:08:29.728000000 +0200 Modify: 2015-04-02 12:08:29.728000000 +0200 Change: 2015-04-02 12:08:29.728000000 +0200 Birth: - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
