rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Started Rhythmbox after doing a clean install of Ubuntu 12.04 LTS daily build (4/11/12). Started importing music into the library by selecting the music folder on my Windows partition (which mounts on boot). It started importing, then popped up the metadata error. I let it finish importing, then started playing music. It worked just fine, and the program seems to be functioning normally.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 11 15:26:26 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120411.1)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f00fbb85414 <g_type_
PC (0x7f00fbb85414) ok
source "$0x8" ok
destination "0x16(%rbx)" (0x4000000016) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
g_type_check_value () from /usr/lib/
gst_value_
gst_structure_copy () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: rhythmbox-metadata crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #838812, 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.