rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
After I started Rhythmbox, it started reindexing my music library (first time after I upgrade from 11.10 to 12.04b2), I went into Settings... window and then the system throw this error message. However, after that I could play my music.
System informations:
#uname -a
Linux bernard 3.2.0-22-generic #35-Ubuntu SMP Tue Apr 3 18:33:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
#lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
#apt-cache policy rhythmbox
rhythmbox:
Installed: 2.96-0ubuntu4
Marked: 2.96-0ubuntu4
Version table:
*** 2.96-0ubuntu4 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CheckboxSubmission: 4be66cfce97e83c
CheckboxSystem: b8f3ec504801f13
Date: Sat Apr 7 11:23:57 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
ProcCmdline: /usr/lib/
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
Title: rhythmbox-metadata crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to precise on 2012-04-01 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
| loserock (loserock) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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.