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 330730 - Totem crashes while trying to open the file dialog!
Totem crashes while trying to open the file dialog!
Status: RESOLVED DUPLICATE of bug 324240
Product: totem
Classification: Core
Component: xine-lib backend
1.2.x
Other All
: Normal critical
: ---
Assigned To: Maintainer alias for xine-lib component of Totem
Maintainer alias for xine-lib component of Totem
Depends on:
Blocks:
 
 
Reported: 2006-02-10 22:51 UTC by Kay Marks
Modified: 2006-02-10 23:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Kay Marks 2006-02-10 22:51:12 UTC
Steps to reproduce:
Distribution: Ubuntu 5.10 (breezy)
Package: totem
Severity: Normal
Version: GNOME2.12.1 1.2.1
Gnome-Distributor: Ubuntu
Bugzilla-Product: totem
Bugzilla-Component: general
Bugzilla-Version: 1.2.1
BugBuddy-GnomeVersion: 2.0 (2.12.0)


Description of the crash:
The totem-xine music player crashes when I try to open the file browser to load
a multimedia file.

Steps to reproduce the crash:
There are different versions of this bug. I found out that when I use
the ATI driver from the ubuntu repository that the "normal" totem player
works just fine. But very often, when I tried to open the open --> file
menu after playing a song with totem already, the program simply quit
itself without any error messages!
 
But after I installed the newest driver from the ATI page totem didn't
even start anymore! Well, it gave me an error that the video port is
blocked by another application. I couldn't figure out how this would be
the case and installed totem-xine instead. I got that running fine, but
it pretty much had the same bug with the file dialog like descripted
above, but quits with an error message. 

Under the same circumstances it happened both with totem & totem-xine
sometimes that it opened the file dialog, but you could only see
folders. All files were faded out. When you looked at the bottom right
of the dialog, where the filter setting is located, you saw "Untitled
Filter" standing there. If you clicked on this drop-down-box you would
see the same option offered a second time. But clicking on the other
didn't turn the files visible again either. 
 
 
How often does this happen?
The crashing happens more regularly then the "untitled filter" bug, I
guess 2:1. And such a bug happens in 2 out of 3 cases after or while you
are playing a song or another media file with the player.

Stack trace:
Debugging Information:

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225345344 (LWP 10937)]
[New Thread -1307546704 (LWP 10947)]
[New Thread -1298048080 (LWP 10945)]
[New Thread -1289655376 (LWP 10944)]
[New Thread -1279374416 (LWP 10943)]
[New Thread -1266881616 (LWP 10942)]
[New Thread -1258218576 (LWP 10941)]
[New Thread -1249789008 (LWP 10940)]
[New Thread -1233785936 (LWP 10939)]
[New Thread -1227949136 (LWP 10938)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()




Other information:
Using ATI Radeon 9800 Pro
Comment 1 Bastien Nocera 2006-02-10 23:05:02 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 324240 ***