indicator-applet crashed with SIGSEGV in gtk_range_get_value()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Sound Menu |
Fix Released
|
High
|
Conor Curran | ||
indicator-sound (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: indicator-sound
hi
I was just turning up the sound when it die .
my Ubuntu Is 10:10 a3 .
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-sound 0.3.9-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
Date: Mon Aug 9 10:21:47 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x889ac9 <gtk_range_
PC (0x00889ac9) ok
source "0x20(%eax)" (0x00000020) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-sound
StacktraceTop:
gtk_range_
?? () from /usr/lib/
g_cclosure_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
Title: indicator-applet crashed with SIGSEGV in gtk_range_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-
Related branches
- David Barth: Needs Fixing
-
Diff: 549 lines (+317/-45)5 files modifiedsrc/indicator-sound.c (+3/-0)
src/metadata-widget.c (+33/-26)
src/mpris2-controller.vala (+8/-4)
src/music-player-bridge.vala (+21/-3)
src/play-button.c (+252/-12)
Changed in indicator-sound (Ubuntu): | |
assignee: | nobody → Conor Curran (cjcurran) |
Changed in indicator-sound: | |
assignee: | nobody → Conor Curran (cjcurran) |
Changed in indicator-sound (Ubuntu): | |
assignee: | Conor Curran (cjcurran) → nobody |
Changed in indicator-sound: | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in indicator-sound: | |
milestone: | none → 0.4.4 |
Changed in indicator-sound: | |
status: | Fix Committed → Fix Released |
Changed in indicator-sound (Ubuntu): | |
status: | Invalid → Fix Committed |
importance: | Undecided → Low |
status: | Fix Committed → Fix Released |
Hi,
I have not been able to reproduce this. So for release 0.4.4 I have patched some defence code in place so as this should not happen again regardless. Was there anything particular when this occured, just after booting etc ?
Conor