Ubuntu
gnome-settings-daemon package

/usr/libexec/gsd-power:11:up_client_get_devices2:engine_coldplug:gsd_power_manager_start:main

Bug #2083202 reported by errors.ubuntu.com bug bridge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
High
Unassigned

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4871bf360fcc371310fbdec244b42a054e3858e3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Journalctl warnings from one of the errors report

sep 29 19:57:36 NUC gsd-power[731063]: invalid (NULL) pointer instance
sep 29 19:57:36 NUC gsd-power[731063]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sep 29 19:57:36 NUC gsd-power[731063]: up_client_get_devices_full: assertion 'UP_IS_CLIENT (client)' failed

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → High
tags: added: rls-oo-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

The errors started in Oracular, maybe a upower regression?

Revision history for this message
Alessandro Astone (aleasto) wrote :

Currently upower is a required dependency of:
    gnome-applets
    gnome-session-bin
    gnome-power-manager

It is also a Recommends for gnome-settings-daemon, through gnome-settings-daemon → libupower-glib3 → upower.

The logic did not take into account that connecting to UPower might fail, so eventually gsd-power crashes.

However, I don’t believe these crashes originate from upower being not installed. Instead, @paride found that his libimobiledevice6 package was corrupted so that upower couldn’t find the library and failed to start.

That shouldn’t happen, but we should make gsd-power exit gracefully rather than crash when failing to connect to UPower.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.