Description of problem: At startup of Pantheon environment on recently upgraded Fedora 26 (from 25) Version-Release number of selected component: light-locker-1.7.0-4.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: light-locker crash_function: _dbus_warn_check_failed executable: /usr/bin/light-locker journald_cursor: s=834b3544f6784cfbbc598cbf0a247e14;i=71cb8;b=932056af1c6247daa852a5844131c9a2;m=59d99901e;t=555f7e68be2c6;x=4af39b5fa014eb30 kernel: 4.11.11-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1309246 [details] File: backtrace
Created attachment 1309247 [details] File: cgroup
Created attachment 1309248 [details] File: core_backtrace
Created attachment 1309249 [details] File: cpuinfo
Created attachment 1309250 [details] File: dso_list
Created attachment 1309251 [details] File: environ
Created attachment 1309252 [details] File: limits
Created attachment 1309253 [details] File: maps
Created attachment 1309254 [details] File: open_fds
Created attachment 1309255 [details] File: proc_pid_status
Created attachment 1309256 [details] File: var_log_messages
As I don't use Pantheon, reassigning to maintainer of pantheon packages. Maybe some help possible from there.
I assume you are using LightDM as your DM?
(In reply to Fabio Valentini from comment #13) > I assume you are using LightDM as your DM? Yes. Light-locker can work with LightDM only.
light-locker-1.8.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b0520a55ff
light-locker-1.8.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b0520a55ff
light-locker-1.8.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.