mate-power-manager crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

Bug #1551277 reported by Øystein Steffensen-Alværvik
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mate-power-manager (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I experimented with the Cupertino panel layout and Plank when this error suddenly popped up. Power manager seems to have crashed and did not restart.

Ubuntu 16.04 Daily release amd64 20160229

mate-power-manager:
  Installert: 1.12.1-1
  Kandidat: 1.12.1-1
  Versjonstabell:
 *** 1.12.1-1 500
        500 http://no.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: mate-power-manager 1.12.1-1
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Mon Feb 29 16:20:24 2016
ExecutablePath: /usr/bin/mate-power-manager
InstallationDate: Installed on 2016-02-29 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160229)
ProcCmdline: mate-power-manager
SegvAnalysis:
 Segfault happened at: 0x7fadf5140e69 <up_exported_daemon_get_lid_is_closed+9>: mov (%rbx),%rdi
 PC (0x7fadf5140e69) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mate-power-manager
StacktraceTop:
 up_exported_daemon_get_lid_is_closed () from /usr/lib/x86_64-linux-gnu/libupower-glib.so.3
 ?? ()
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mate-power-manager crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 mate-session[1023]: WARNING: Unable to find provider '' of required component 'dock'
 (nm-applet:1424): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
 (mate-power-manager:1402): libupower-glib-WARNING **: Couldn't connect to proxy: Feil ved kall til StartServiceByName for org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.UPower': timed out
 (mate-panel:1377): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion 'global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed

Revision history for this message
Øystein Steffensen-Alværvik (oystein-alver) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 up_exported_daemon_get_lid_is_closed (object=0x0) at up-daemon-generated.c:747
 gpm_button_init ()
 g_type_create_instance () from /tmp/apport_sandbox_gGw9vP/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_internal () from /tmp/apport_sandbox_gGw9vP/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /tmp/apport_sandbox_gGw9vP/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in mate-power-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mate-power-manager (Ubuntu):
status: New → Confirmed
information type: Private → Public
no longer affects: glib2.0 (Ubuntu)
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

mate-power-manager 1.12.1-1 (GTK2) is no longer supported.

Changed in mate-power-manager (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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