unity-music-daemon crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-lens-music (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This crash seem to happen after I started Update-Manager.
lsb_release-rd returned "Command not found". I've upgraded to 12.04 distribution.
Release 12.04 (precise) 64-bit
Kernel Linux 3.2.0-11-generic
GNOME 3.2.1
Prior to the distribution updates I put on yesterday, 12/01/27, I had to use the command line update
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-update
because the update-manager crashed when I tried to use it.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-music 5.0.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-11-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 28 09:09:42 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Alpha amd64 (20110530)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f75f76c6e38: mov 0x0(%rbp,
PC (0x7f75f76c6e38) ok
source "0x0(%rbp,%r14,8)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-lens-music
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: unity-music-daemon crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
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 #921426, 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.