totem crashes when leaving fullscreen mode

Bug #216268 reported by MartinE
8
Affects Status Importance Assigned to Milestone
Totem
Invalid
Undecided
Unassigned
X.Org X server
Invalid
Undecided
Unassigned
nvidia-graphics-drivers-180 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: totem

On Ubuntu 8.04 (Hardy Heron) prerelease, totem consistently crashes X when I try to leave fullscreen mode. Fullscreen works perfectly, but leaving fullscreen mode breaks the X server. Not always, but about every third time. I'm using the proprietary nvidia-glx-new driver, and have compiz enabled. So far, I haven't noticed this bug with metacity. I'm not sure if this really is a bug in totem, or rather nvidia-glx-new, or compiz. I'm filing a bug against totem for now.

If you need further information, please tell me how to obtain it. I have to restart the entire system when the problem appears.

Package versions:

totem-2.22.1-0ubuntu2
nvidia-glx-new-169.12+2.6.24.12-16.34
compiz-1:0.7.4-0ubuntu4

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 instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

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.

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:
status: New → Invalid
Revision history for this message
MartinE (martin-engbers-gmx) wrote :

With all due respect, I protest the closing of this bug report. There is no ".crash" file that I could submit. Indeed, the /var/crash directory contains nothing but the ".lock" file.

If I should gather further information for you to deal with this bug, please tell me which and how to obtain it. Don't declare the bug report invalid because apport failed to create a ".crash" file.

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

Then please try to obtain a complete backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report, after you have done this re-open the report, thanks.

Revision history for this message
MartinE (martin-engbers-gmx) wrote :

The information at http://wiki.ubuntu.com/DebuggingProgramCrash , or more specifically at https://wiki.ubuntu.com/Backtrace , is not applicable, since gdm is killed when the crash occurs. Once X has restarted and i have logged in again, no gdm is running.

How do I obtain a backtrace under these circumstances? I will try to obtain valgrind and strace logs, if these are of any help to you. Any advice would be appreciated, thanks.

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

Whatever the application is doing xorg should not be crashing, that's likely a video driver issue, could you try using the opensource nvidia driver? Otherwise the Xorg.0.log might have informations about the crash

Revision history for this message
sc00ter (gosdenj) wrote :

Yep, I can confirm this. I'm getting exactly the same behaviour.

Totem (with grstreamer back-end and xine back-end) go into full-screen play-back and then exiting full-screen, the screen goes black and the GDM resets to the GDM Login.

NVidia drivers are 169.12: nvidia-glx-new 169.12+2.6.24.12-17.36

Running Ubuntu 8.04

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

do you get the issue using the nvidia opensource driver?

Revision history for this message
Claudiu Vlad (claudiu-vlad) wrote :

I am having the same issue here. when leaving fullscreen totem, its crashing the X server.
Xorg.0.log has no errors in it.

Changed in totem:
status: Invalid → Confirmed
Revision history for this message
Claudiu Vlad (claudiu-vlad) wrote :

Disabling Backingstore option in xorg.conf seems to fix it. I'll be reporting again if not.

Revision history for this message
MartinE (martin-engbers-gmx) wrote :

Thanks a lot, Claudiu!

That does indeed seem to work. I'll try this for 2-3 days, and report back unless I run into a crash again earlier.

I wonder though, was the BackingStore option enabled by default on Ubuntu Hardy? I'd nerver heard of it before, so I don't think I enabled it manually. Whatever.

Martin

Revision history for this message
MartinE (martin-engbers-gmx) wrote :

Sorry, totally forgot to report back as promised. Disabling the backingstore option definitely fixed this problem for me.

Martin

Revision history for this message
sc00ter (gosdenj) wrote :

Hi, I can also confirm that disabling BackingStore has resolved the problem.

Revision history for this message
Claudiu Vlad (claudiu-vlad) wrote :

Pedro Villavicencio , maybe this could lead to fixing some code in totem, could it ?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

seems fixed in intrepid, at least I can't reproduce it.

Changed in xorg:
status: Confirmed → Fix Released
Revision history for this message
smkururu (smkururu) wrote :

Hi, I'm running Ubuntu Jaunty with Totem Movie Player 2.26.1 . I don't have backingstore in xorg.conf and I think the problem is the same except that I use ATI, not nvidia.

Changed in xorg-server:
status: New → Fix Released
status: Fix Released → New
status: New → Invalid
Revision history for this message
jonnyb (tomas-pavlacky) wrote :

Hi, I have a same problem as smkururu. I'm running Ubuntu Jaunty and Totem 2.26.1. I'm using Ati 2600 pcie. When i turn of Compiz, everything OK without crash.

Revision history for this message
jonnyb (tomas-pavlacky) wrote :

i installed ati-driver-installer-9-6-x86.x86_64 this driver released 15.6.2009 and fix my problem.

Andrew (and471)
Changed in totem:
status: New → 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.