rhythmbox crashed with SIGSEGV in monitor_entry_file()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Rhythmbox |
Fix Released
|
Medium
|
||
| rhythmbox (Ubuntu) |
High
|
Michael Terry | ||
| Quantal |
High
|
Michael Terry |
Bug Description
...
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu2
ProcVersionSign
Uname: Linux 3.5.0-6-generic x86_64
ApportVersion: 2.4-0ubuntu5
Architecture: amd64
Date: Thu Jul 26 12:20:04 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: rhythmbox
SegvAnalysis:
Segfault happened at: 0x7f857e9d50e0: mov (%rax),%rsi
PC (0x7f857e9d50e0) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /lib/x86_
start_thread () from /lib/x86_
Title: rhythmbox crashed with SIGSEGV in start_thread()
UpgradeStatus: Upgraded to quantal on 2012-07-21 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
Alberts Muktupāvels (muktupavels) wrote : | #1 |
Apport retracing service (apport) wrote : | #2 |
Changed in rhythmbox (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- rhythmbox crashed with SIGSEGV in start_thread() + rhythmbox crashed with SIGSEGV in monitor_entry_file() |
tags: | removed: need-amd64-retrace |
Launchpad Janitor (janitor) wrote : | #6 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in rhythmbox (Ubuntu): | |
status: | New → Confirmed |
tags: | added: running-unity |
Omer Akram (om26er) wrote : | #7 |
rhythmbox is crashing like crazy, everytime I start it would first crash and on the next attempt will work fine.
visibility: | private → public |
Changed in rhythmbox (Ubuntu): | |
importance: | Medium → High |
Ursula Junque (ursinha) wrote : | #8 |
This happened to me today after dist-upgrading from precise to quantal. Once the machine returned from reboot, I logged in and hit this bug. I actually didn't run any commands for this to happen.
Changed in rhythmbox (Ubuntu Quantal): | |
assignee: | nobody → Michael Terry (mterry) |
Changed in rhythmbox: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in rhythmbox (Ubuntu Quantal): | |
status: | Confirmed → In Progress |
Changed in rhythmbox: | |
status: | New → Fix Released |
Launchpad Janitor (janitor) wrote : | #9 |
This bug was fixed in the package rhythmbox - 2.97-1ubuntu5
---------------
rhythmbox (2.97-1ubuntu5) quantal; urgency=low
[ Martin Pitt ]
* debian/
now.
[ Jeremy Bicha ]
* debian/
- Dropped, override moved to ubuntu-settings
[ Michael Terry ]
* debian/
- Backport git patches to guard against crashing due to monitoring
files outside library (by moving a g_strfreev and also just stopping
monitoring such files at all). LP: #1029333
-- Michael Terry <email address hidden> Wed, 19 Sep 2012 14:30:03 -0400
Changed in rhythmbox (Ubuntu Quantal): | |
status: | In Progress → Fix Released |
StacktraceTop: monitor. c:165 monitor. c:156 tree_entry_ foreach (rdb=<optimized out>, foreach_ func=0x7f857e9d 5080 <monitor_ entry_file> , user_data= 0x207a290) at rhythmdb- tree.c: 2422 entry_thread (db=0x207a290) at rhythmdb- monitor. c:251 buildd/ glib2.0- 2.33.6/ ./glib/ gthread. c:801
monitor_entry_file (db=0x207a290, entry=<optimized out>) at rhythmdb-
monitor_entry_file (entry=<optimized out>, db=0x207a290) at rhythmdb-
rhythmdb_
_monitor_
g_thread_proxy (data=0x2e9ab20) at /build/