GNOME Bugzilla – Bug 326513
Crash (segfault) when adding to playlist for the 2nd time
Last modified: 2006-01-10 21:03:02 UTC
Steps to reproduce: 1. Open Totem, add item to play list. [Totem starts playing added item] 2. Click the 'add to playlist' again. [Totem window closes/dissappears and "Segmentation fault" is printed to console] Here is a full log of of console output (user interaction marked with [ ... ] ): [ User: Click 'add to playlist' button ] [ User: Select file in file dialog ] [ User: Click on Open button in file dialog ] ** Message: totem_playlist_add_one_mrl (): Nikkfurie de la Caution - The a la Menthe.mp3 file:///mnt/shared/Music/Misc/Nikkfurie%20de%20la%20Caution%20-%20The%20a%20la%20Menthe.mp3 (null) [ Totem: starts playing the added item ] [ User: Click 'add to playlist' button again ] (totem:23690): Gtk-CRITICAL **: gtk_object_sink: assertion `GTK_IS_OBJECT (object)' failed (totem:23690): Gtk-CRITICAL **: gtk_file_filter_get_name: assertion `GTK_IS_FILE_FILTER (filter)' failed (totem:23690): Gtk-CRITICAL **: gtk_object_sink: assertion `GTK_IS_OBJECT (object)' failed Segmentation fault [ Totem: *poof* ] The errors that show up in the console after hitting the 'Add...' button aren't always the same, it seems. But there are always a bunch of them. Stack trace: (gdb) thread apply all bt
+ Trace 65109
Thread 5 (Thread 49156 (LWP 23729))
Thread 4 (Thread 32771 (LWP 23728))
Thread 1 (Thread 16384 (LWP 23723))
Other information: System uname: 2.6.14-gentoo-r4 i686 AMD Athlon(tm) 64 Processor 3500+ Misc info: gcc-3.3.6, glibc-2.3.6-r2 I haven't always had this problem, but unfortunately do not recall what I changed (if anything) when it started happening. Might've been after a system (software) upgrade or something.
To be more precise, with the 'add to playlist' button, I mean the button with the + icon at the bottom of the playlist sidebar
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 324240 ***