totem dumps core shortly after startup

Bug #181172 reported by Anders Steinlein
8
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: totem

This is a fairly fresh 7.10 64-bit install with a limited number of applications/packages installed thus far. I first tried opening a MPG movie and totem crashed. Same when simply trying to open the application. I can briefly see the application window before it disappears again. Trying to start totem from a terminal simply outputs "Bus error (core dumped)".

ProblemType: Crash
Architecture: amd64
Date: Tue Jan 8 06:21:00 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/totem
NonfreeKernelModules: nvidia
Package: totem-gstreamer 2.20.0-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: totem file:///data/Movies/The%20Insult%20Comic%20Dog/Hollywood%20Squares.mpg
ProcCwd: /home/anders
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 7
SourcePackage: totem
StacktraceTop:
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
Title: totem crashed with signal 7
Uname: Linux twilight 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Anders Steinlein (asteinlein) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in totem:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Anders Steinlein (asteinlein) wrote :

Thanks for the quick feedback, Pedro. I followed the instructions, but gdb provided little information (or I'm doing something wrong).

Running: gdb totem 2>&1 | tee gdb-totem.txt simply outputs the gdb copyright followed by:
Using host libthread_db library "/lib/libthread_db.so.1". and I'm left at a (gdb) prompt.

However, I tried Valgrind as well which gave a lot of output. Log file attached. Thanks again.

Revision history for this message
Anders Steinlein (asteinlein) wrote :

I don't know if this is related, but I'm commenting just in case. I tried mplayer to see if that would work, and at first it didn't. All but the ggi video output driver failed.

After searching around I found https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/159861, so I tried "killall gnome-screensaver" before launching mplayer, and voila, mplayer worked. However, this did nothing to help totem, which still crashes. Still, thought I'd just throw this out there.

Revision history for this message
Jonathan Thurn (jthurn) wrote :

Hi Anders,

I'm having the same totem error as you, though I'm running Xubuntu Gutsy, and though I have replaced totem-xine with totem-gstreamer as I had the same problem with xine.

As for the backtrace, see https://wiki.ubuntu.com/Backtrace again. Once you initiate the program with "gdb <program> 2>&1 | tee gdb-<program>.txt" you need to configure it with the next few lines. Don't ask me why everything cannot be sent on the same line as I'm new at this game also. I've attached my backtrace for your information as strace and my own valgrind output as it may differ from yours.

Best,
Jon

Revision history for this message
Jonathan Thurn (jthurn) wrote :
Revision history for this message
Jonathan Thurn (jthurn) wrote :
Revision history for this message
Jonathan Thurn (jthurn) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Revision history for this message
Jonathan Thurn (jthurn) wrote :

Dear Pedro,

I would be pleased to test out the most recent development release of hardy once bug no. 188660 has been fixed. Until then, I cannot get past the gdm login screen without going into safe graphics mode. I presume testing totem under the safe graphics mode would not provide you the best assurance that this bug has been fixed.

Best,
Jonathan

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in totem:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.