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 632370 - rhythmbox crashes when a .m3u file is opened
rhythmbox crashes when a .m3u file is opened
Status: RESOLVED DUPLICATE of bug 591841
Product: rhythmbox
Classification: Other
Component: general
0.13.x
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-10-17 16:29 UTC by Omer Akram
Modified: 2010-10-18 02:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
logs (2.67 KB, text/plain)
2010-10-17 16:30 UTC, Omer Akram 		Details

Description Omer Akram 2010-10-17 16:29:38 UTC 
click on music>import file and select a .m3u file and click open and rhythmbox crashes.

originally reported at: https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/662251
Comment 1 Omer Akram 2010-10-17 16:30:09 UTC 
Created attachment 172552 [details]
logs
Comment 2 Fabio Durán Verdugo 2010-10-18 01:56:25 UTC 
paste here the backtrace.


(rhythmbox:2656): Gtk-WARNING **: Attempting to read the recently used resources file at `/home/kholdi/.recently-used.xbel', but the parser failed: Error reading file '/home/kholdi/.recently-used.xbel': Is a directory.
[New Thread 0xb28b3b70 (LWP 2666)]
[Thread 0xb3addb70 (LWP 2662) exited]

(rhythmbox:2656): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

Program received signal SIGSEGV, Segmentation fault.
0x00167a45 in rb_shell_guess_source_for_uri () from /usr/lib/librhythmbox-core.so.1
(gdb) bt

+ Trace 224194

  • #0 rb_shell_guess_source_for_uri
    from /usr/lib/librhythmbox-core.so.1
  • #1 ??
    from /usr/lib/librhythmbox-core.so.1
  • #2 ??
    from /usr/lib/libtotem-plparser.so.17
  • #3 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #4 ??
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #7 ??
    from /usr/lib/libtotem-plparser.so.17
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main 
A debugging session is active.
Comment 3 Fabio Durán Verdugo 2010-10-18 01:56:56 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 4 Jonathan Matthew 2010-10-18 02:52:10 UTC 

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