[power]: gnome-settings-daemon crashed with SIGSEGV in g_strsplit()

Bug #1056019 reported by Mario Vukelic
6
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just an hour ago I added info (valgrind log) to another g-s-d crash, bug #410534. Then I restarted g-s-d normally and it ran for an hour until the next apport report came up apparently out of the blue

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-settings-daemon 3.4.2-0ubuntu13
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 25 10:06:02 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
ProcCmdline: gnome-settings-daemon
SegvAnalysis:
 Segfault happened at: 0x7f6758972a08 <g_strsplit+312>: mov (%rdx),%rdi
 PC (0x7f6758972a08) ok
 source "(%rdx)" (0x747461622d6d7067) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_strsplit () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gpm_upower_get_device_icon () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
Title: [power]: gnome-settings-daemon crashed with SIGSEGV in g_strsplit()
UpgradeStatus: Upgraded to quantal on 2012-09-15 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Note that the valgrind log which I attached (maybe incorrectly) to bug #410534 also referred to problems in libpower

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #980328, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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