totem crashes when opening any movie file after upgrading from 8.10 to 9.04

Bug #369372 reported by CVE
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: totem

I'm using 9.04 after upgrading from 8.10
Totem crashes whenever opening any kind of video file.
Mpg, wmv, flv all worked fine under 8.10.
Now the Totem window opens and the file name appears in the playlist, then Totem closes and that's it.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/totem-gstreamer
Package: totem-gstreamer 2.26.1-0ubuntu5
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
CVE (charles-edis) 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. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in totem (Ubuntu):
status: New → Invalid
Revision history for this message
CVE (charles-edis) wrote : Re: [Bug 369372] Re: totem crashes when opening any movie file after upgrading from 8.10 to 9.04

Thanks for this. There is nothing in /var/crash

I have tried enabling apport with "sudo force_start=1 /etc/init.d/apport
start" but it doesn't seem to work. I have also tried changing
"enabled=0" to "enabled=1" in /etc/default/apport but it won't let me
save the change. How do I enable it? Sorry to be a dunce, but I'm not a
techie.

Also; I have noticed that whenever I look at the system monitor
'Resources' tab the CPU usage flies up to 100% for as long as the graph
is on screen. If I switch to the 'Processes' tab nothing is using 100%
CPU but when I switch back to 'Resources' the CPU usage goes straight
back up from 23%, or whatever it's at, to 100%: Surely that can't be
right? Screenshot attached. It reads 100% CPU whenever the Resources
graph window is in the foreground and the CPU usage varies according to
how much of the graph is showing (i.e. if the system monitor window is
mostly covered by another window (such as this email) the CPU usage
drops to around 40%; if I make this window smaller and uncover more of
the graph in background the CPU usage goes up to, say 80%).

Methinks this and the movie problem could be something to do with my
graphics card? I am running 9.04 on my Fujitsu Siemens P7120 and it
worked great under 8.10.: Now I am wishing I hadn't upgraded..

By the way, youtube seems to work, so it's local files causing the
crashing problem.

On Wed, 2009-04-29 at 16:42 +0000, Pedro Villavicencio wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. However, your crash report is either missing or
> challenging to deal with as a ".crash" file. Please follow these
> instructions to have apport report a new bug about your crash that can
> be dealt with by the automatic retracer.
>
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart.
>
> If you are using Ubuntu with the Gnome desktop environment - launch
> nautilus and navigate to your /var/crash directory and double click on
> the crash report you wish to submit.
>
> If you are using Kubuntu or Xubuntu you can file the crash using
> /usr/share/apport/apport-qt --crash-
> file=/var/crash/_my_crash_report.crash in a terminal - where
> _my_crash_report.crash is the crash you would like to report.
>
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently. Thanks in advance for your cooperation and understanding.
>
> ** Changed in: totem (Ubuntu)
> Status: New => Invalid
>

Revision history for this message
networker (kussh-singh) wrote :

Totem crashes whenever any multimedia file is played --this happenned after upgrading to 9.04 from 8.10. Before this the ubuntu 8.10 system used to work fine.

I can play mp3 etc audio files in the rhythmbox player. When i am playing such files in rhythmbox, then totem can be opened to play any multimedia file. (audio or video). But as soon as file playing gets over in rhythmbox, totem crashes after playing the file to the end (ie. the file can't be replayed in totem after file playing is stopped in rhythmbox or rhythmbox is closed).

Therefore it seems that rhythmbox opens some multimedia socket file that is also used by totem which allows audio/video files to be played properly without crashing either application. But when totem tries to open any multimedia file on its own, the default channel used by totem crashes it.

This is what comes in xterminal when i try to open a multimedia file with totem without using rhythmbox --totem crashes and shows the output below in xterminal

/var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 82 error_code 11 request_code 132 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Revision history for this message
networker (kussh-singh) wrote :

/var/crash does not show anything. Maybe its because totem just closes OR it just aborts OR in other words exits with error code 11, request code 132, minor code 19. This same error comes even with vlc. Only the serial number of the error reported changes.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in totem (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: Invalid → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you use the desktop effects option?

Revision history for this message
Omer Akram (om26er) 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 (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
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.