gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification()

Bug #1082723 reported by Sasa Paporovic
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Confirmed
High
Unassigned

Bug Description

This crasher happends during a system run of several hours with not specific doing on the system.

Steps to reproduce:

Unfortunally it is not possible to give a reliable reproducing procedure.
Run the sytem for several hours.

Additional:

clamtk was running called by gksu a recursive search for malware through the filesystem.
No other GUI- or user started program was running.

Additional2:

This is propably a regression of a already fixed bug in Ubuntu11.10 Oneiric.
The affected report can be found here:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/832603

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-settings-daemon 3.6.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
Uname: Linux 3.7.0-3-generic x86_64
ApportVersion: 2.6.2-0ubuntu5
Architecture: amd64
Date: Sat Nov 24 18:46:05 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2012-07-22 (125 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6624cf2046: cmpq $0x0,(%rdi)
 PC (0x7f6624cf2046) ok
 source "$0x0" ok
 destination "(%rdi)" (0x00000101) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to raring on 2012-11-15 (8 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
information type: Private → Public
tags: added: regression-release
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ubuntu_osd_do_notification (notification=notification@entry=0x101, hint=hint@entry=0x7f6624d01383 "brightness", value=value@entry=80, muted=muted@entry=0, icon_names=icon_names@entry=0x7f6624f0ac00) at gsd-media-keys-manager.c:274
 ubuntu_osd_notification_show_brightness (value=80, manager=0xed2100) at gsd-media-keys-manager.c:300
 update_screen_cb (source_object=<optimized out>, res=<optimized out>, user_data=0xed2100) at gsd-media-keys-manager.c:1845
 g_simple_async_result_complete (simple=0x11346a0) at /build/buildd/glib2.0-2.34.2/./gio/gsimpleasyncresult.c:775
 reply_cb (connection=<optimized out>, res=<optimized out>, user_data=0x11346a0) at /build/buildd/glib2.0-2.34.2/./gio/gdbusproxy.c:2632

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 gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
summary: gnome-settings-daemon crashed with SIGSEGV in
- g_simple_async_result_complete()
+ ubuntu_osd_do_notification()
tags: removed: need-amd64-retrace
Changed in gnome-settings-daemon (Ubuntu):
importance: Medium → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
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.