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 634203 - Crash when open playlist.pls
Crash when open playlist.pls
Status: RESOLVED DUPLICATE of bug 591841
Product: rhythmbox
Classification: Other
Component: general
0.12.x
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-07 01:15 UTC by Fabio Durán Verdugo
Modified: 2010-11-07 01:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Fabio Durán Verdugo 2010-11-07 01:15:08 UTC 
Steps:
1-) select the attach file (playlist.pls)
2.-) right click and select open with rhythmbox
3.-) crash

Core was generated by `rhythmbox'.
Program terminated with signal 11, Segmentation fault.

+ Trace 224535

Thread 1 (Thread 13362)

  • #0 rb_shell_guess_source_for_uri
    from /usr/lib/librhythmbox-core.so.1
  • #1 ??
    from /usr/lib/librhythmbox-core.so.1
  • #2 totemplparser_marshal_VOID__STRING_BOXED
    at totemplparser-marshal.c line 138
  • #3 g_closure_invoke
    at gclosure.c line 766
  • #4 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #5 g_signal_emit_valist
    at gsignal.c line 2983
  • #6 g_signal_emit
    at gsignal.c line 3040
  • #7 emit_entry_parsed_signal
    at totem-pl-parser.c line 1300
  • #8 g_idle_dispatch
    at gmain.c line 4254
  • #9 g_main_dispatch
    at gmain.c line 2149
  • #10 g_main_context_dispatch
    at gmain.c line 2702
  • #11 g_main_context_iterate
    at gmain.c line 2780
  • #12 g_main_loop_run
    at gmain.c line 2988
  • #13 IA__gtk_main
    at gtkmain.c line 1237
  • #14 main 






Comment 1


Jonathan Matthew





          2010-11-07 01:18:18 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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