http://bugzilla.opensuse.org/show_bug.cgi?id=975653 http://bugzilla.opensuse.org/show_bug.cgi?id=975653#c1 --- Comment #1 from Atri Bhattacharya --- Created attachment 673048 --> http://bugzilla.opensuse.org/attachment.cgi?id=673048&action=edit Full journallog from previous boot Note the several upowerd core dump messages: Apr 14 22:46:43 tp-yoga260 systemd-coredump[9893]: Process 9869 (upowerd) of user 0 dumped core. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=975653 http://bugzilla.opensuse.org/show_bug.cgi?id=975653#c3 --- Comment #3 from Atri Bhattacharya --- the gdb output follows: ==================================================== Starting program: /usr/bin/gnome-power-statistics [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffead82700 (LWP 12558)] [New Thread 0x7fffea581700 (LWP 12559)] [New Thread 0x7fffe9afa700 (LWP 12560)] (gnome-power-statistics:12557): libupower-glib-WARNING **: up_client_get_devices failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.273 was not provided by any .service files Program received signal SIGSEGV, Segmentation fault. gpm_stats_startup_cb (application=<optimized out>, user_data=<optimized out>) at gpm-statistics.c:2008 2008 in gpm-statistics.c (gdb) bt #0 gpm_stats_startup_cb (application=<optimized out>, user_data=<optimized out>) at gpm-statistics.c:2008 #1 0x00007ffff68b3795 in g_closure_invoke (closure=0x7e8350, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0x7fffffffda20, invocation_hint=invocation_hint@entry=0x7fffffffd9c0) at gclosure.c:804 #2 0x00007ffff68c5081 in signal_emit_unlocked_R (node=node@entry=0x6ed000, detail=detail@entry=0, instance=instance@entry=0x659240, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffffffda20) at gsignal.c:3629 #3 0x00007ffff68cdcca in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffdbb8) at gsignal.c:3385 #4 0x00007ffff68ce0a2 in g_signal_emit (instance=instance@entry=0x659240, signal_id=<optimized out>, detail=detail@entry=0) at gsignal.c:3441 #5 0x00007ffff6ffd132 in g_application_register (application=application@entry=0x659240, cancellable=cancellable@entry=0x0, error=error@entry=0x7fffffffdce8) at gapplication.c:2049 #6 0x00007ffff6ffd91f in g_application_real_local_command_line (application=0x659240, arguments=0x7fffffffddb0, exit_status=0x7fffffffddac) at gapplication.c:1012 #7 0x00007ffff6ffdc82 in g_application_run (application=0x659240, argc=argc@entry=1, argv=argv@entry=0x7fffffffdf18) at gapplication.c:2350 #8 0x0000000000405186 in main (argc=1, argv=0x7fffffffdf18) at gpm-statistics.c:2081 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=975653 http://bugzilla.opensuse.org/show_bug.cgi?id=975653#c5 Bjørn Lie changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zaitor@opensuse.org See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=94262 --- Comment #5 from Bjørn Lie --- https://bugs.freedesktop.org/show_bug.cgi?id=94262 Fix on it's way to Tw. Note that this is a fix from upstream, but I'd like some testing, cause when I tried it my laptop shut down instead of hybrid sleeping like it used to do. I wonder if the fix upstream is not quite correct, or if this current release of upower is even more borked. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=975653 http://bugzilla.opensuse.org/show_bug.cgi?id=975653#c7 Bjørn Lie changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Bjørn Lie --- Closing as resolved fixed, even if it has yet to land in TW -- You are receiving this mail because: You are on the CC list for the bug.