After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 648649 - Crash starting Rhythmbox if there are Missing files. Segmentation fault.
Crash starting Rhythmbox if there are Missing files. Segmentation fault.
Status: RESOLVED DUPLICATE of bug 647032
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-04-25 22:49 UTC by Matteo Drera
Modified: 2011-04-26 21:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Rhythmbox log (99.01 KB, application/x-gzip)
2011-04-25 22:52 UTC, Matteo Drera 		Details
Rhythmbox trace (854 bytes, application/octet-stream)
2011-04-25 23:30 UTC, Matteo Drera 		Details
Rhythmbox trace (13.50 KB, text/plain)
2011-04-26 11:23 UTC, Matteo Drera 		Details

Description Matteo Drera 2011-04-25 22:49:14 UTC 
Rhythmbox crashes shortly after startup if there are "Missing files" in the library.

After Rhythmbox UI is shown, the library is loaded and all the plugins are activated, then Rhythmbox suddenly closes. Segmentation fault.


* Preliminary steps to reproduce bug:
- Start Rhythmbox normally (with no "Missing files")
- Delete a file using the "Move to Trash"
- "Missing files" appears in the sidebar [1]
- Normally close Rhythmbox

* Step to reproduce:
- Re-open Rhythmbox


[1] If "Missing files" is clicked during preliminary, Rhythmbox crashes as described in bug #647032 or #641884, but on next start THIS bug DOES NOT happen.
Comment 1 Matteo Drera 2011-04-25 22:52:37 UTC 
Created attachment 186625 [details]
Rhythmbox log

$ rhythmbox -d &> rhythbox.log
Comment 2 Jonathan Matthew 2011-04-25 22:56:43 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 3 Matteo Drera 2011-04-25 23:30:30 UTC 
Created attachment 186629 [details]
Rhythmbox trace

Hope this could help.
Comment 4 Jonathan Matthew 2011-04-25 23:36:18 UTC 
That's not a stack trace.  Please read the instructions on http://live.gnome.org/GettingTraces for more information.
Comment 5 Ionut Biru 2011-04-26 07:26:05 UTC 
in arch like in fedora, we have gnome 3. until now, a compatible rhythmbox version wasn't released and we used a git snapshot. I tried to generate a newer snpashot couples of days ago but the stability wasn't that good.

i don't recommend any arch users to report bugs now. wait until 3.0.0 is released
Comment 6 Jonathan Matthew 2011-04-26 07:35:16 UTC 
I'd appreciate it if users did report bugs.  I can't fix problems I don't know about.
Comment 7 Matteo Drera 2011-04-26 11:23:09 UTC 
Created attachment 186647 [details]
Rhythmbox trace

Here's the trace of Rhythmbox obtained running gdb according to: https://live.gnome.org/GettingTraces/Details#gdb-not-yet-running

Rhythmbox 0.13.3, GLib and Gtk3 recompiled to enable debug.

Unfortunately we are still missing debug symbols on some libs, so trace will still probably not so good.
Comment 8 Jonathan Matthew 2011-04-26 21:39:46 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 647032 ***