Totem starts maximized and without window borders

[Christoph Langner]

Binary package hint: totem

Sometimes it happens, that when i open a video file (.avi) totem starts maximized and without window borders. Closing and restarting totem doesn't help. Usually i can fix that problem by closing down x and logging back in. I don't have logs yet, but i found other people who have the same problem. That's why i report this as a bug. Running gutsy gibbon with compiz here.

totem 2.20.0-0ubuntu3
compiz 1:0.6.0+git20071008-0ubuntu1

[illpig z. (illpig)]

Same problem here. Trying it by getting into the "window menu" with ALT+Space kills totem. I have no conclusion where it came from, just happend from one to another movie without installing any updates or rebooting.
Gutsy /Gnome with Compiz here too.

[Christoph Langner (chrissss)]

A backtrace shows this

----
Starting program: /usr/bin/totem
[Thread debugging using libthread_db enabled]
[New Thread -1228818768 (LWP 4846)]

** (totem:4846): CRITICAL **: bacon_video_widget_set_fullscreen: assertion `bvw != NULL' failed

** (totem:4846): CRITICAL **: bacon_video_widget_set_show_cursor: assertion `bvw != NULL' failed
[New Thread -1242936432 (LWP 4857)]
[Thread -1242936432 (LWP 4857) exited]
----

[Pedro Villavicencio (pedro)]

Thanks for the report, which architecture do you have? which video card do you have? Does it works with a new user? I cannot reproduce your problem here with compiz.

[Christoph Langner (chrissss)]

I could reproduce this on my system under gutsy 32-bit as well as with a 64-bit installation

---
# lspci | grep VGA
07:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS] (rev a1)

# cat /etc/X11/xorg.conf | grep Driver
...
    Driver "nvidia"
---

The next time th error occurs i will try to repdroduce it with a new user.

[illpig z. (illpig)]

Working on an 32-bit gutsy too.
___
# lspci | grep VGA
04:00.0 VGA compatible controller: nVidia Corporation G71 [GeForce 7300 GS] (rev a1)

# cat /etc/X11/xorg.conf | grep Driver
...
    Driver "nvidia"
___

Just having the totem-fullscreen all the time now. But will try with a new user soon.

[andrjas (andrjas)]

Same problem here on a 64 bit Gutsy and ATI graphic card with the default fglrx driver.
My workaround is to delete $HOME/.gnome2/Totem/state.ini . I hope it won't come back again.

[Pedro Villavicencio (pedro)]

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.

[Pedro Villavicencio (pedro)]

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

[Christoph Langner (chrissss)]

I've got the problem again with my up to date installation of hardy. It's pretty impossible to recreate the problem with a hardy live cd, because the problem occours now and then, without any reason. The workaround andrjas posted worked here too. After deleting ~/.config/totem/state.ini, totem started like usual. Here's the content of my state.ini before i deleted the file

---
[State]
window_w=1280
window_h=1024
show_sidebar=false
maximised=false
sidebar_w=998
sidebar_page=properties
---

and here the file after i restarted totem

---
[State]
window_w=873
window_h=476
show_sidebar=true
maximised=false
sidebar_w=247
sidebar_page=playlist
---

[Dommo (u-carlot-u)]

the system is up to date. i've gotten this error for months now.

This is a bug that happens sporadically. it seems to be caused by compiz. the temporary way to fix it is to turn off compiz, then turn it back on if you want to keep on using compiz.

when you open a video or audio file, totem runs with the following argument: totem %U

The work around I've found is to run totem in the terminal as just totem

when i get the error, i run totem %U in terminal and i get the following output:

e@e-desktop:~$ totem %U
** Message: Error: Resource not found.
gstfilesrc.c(977): gst_file_src_start (): /play/source:
No such file "/home/e/%U"

I also get small window with the error message

An error occurred

Location not found

[Sohail Mirza (mirzmaster)]

Is there an upstream bug for this issue? Is there anything that can be done to expedite its resolution?

This bug has bitten me a number of times, and I can only imagine the horror of a new user realizing that their videos are stuck in fullscreen mode for some inexplicable reason.

[umer (umer-farooq)]

I am having the exact same problem as described here. I am running an upto date install of Ubuntu 8.10 x86_64. I have an nVidia 9200M GS, and the drivers I am using are the latest nVidia beta drivers. The "workaround" I have found for this is to alt+f2 > metacity --replace, open up totem, un-maximize it, then alt+f2 > compiz --replace, and it is fine for a while, and then the problem comes back. I had this problem with Gutsy, Hardy, and now Intrepid. I hope this can be resolved soon.

[Walter (walter-verbruggen)]

I had the same problem, but none of the previous solutions worked out.

In a terminal I've started totem with the --replace option

:~$ totem --replace

this has solved my problem

[Sohail Mirza (mirzmaster)]

Is anyone still seeing this issue? Since I've migrated to Jaunty, I am no longer experiencing this issue. Instead, I occasionally find totem starts with the window maximized, but restoring it works just fine.

[Sohail Mirza (mirzmaster)]

By the way, I'm using the following versions:

totem: 2.26.1-0ubuntu5
compiz: 1:0.8.2-0ubuntu8.1

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.