Totem crashes on startup

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.

What videocard and driver do you use?

The same thing happen to me. Totem really needs pygtk? Before install Jaunty i have no problem whit it.

Ps: sorry for my english

Here's the debug information. I hope this helps.

the issue seems due to the fact that pygtk is incorrectly installed

is pygtk installed?

The output I get when I try the command

sudo apt-get install python-gtk2

is

Reading package lists... Done
Building dependency tree
Reading state information... Done
python-gtk2 is already the newest version.
python-gtk2 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

can you use other pygtk softwares? pygtk-demo for example

I guess not because I get this

~/Desktop/pygtk-2.12.1/examples/pygtk-demo$ python pygtk-demo.py
Traceback (most recent call last):
  File "pygtk-demo.py", line 18, in <module>
    import gobject
ImportError: No module named gobject

I guess I need something like pyGnome?

python-gobject should be installed you have a weird installation issue

I have the same "weird installation issue" :P

How can I fix this? I tried installing python-gobject and I got

devo@devo-desktop:~/Desktop/pygtk-2.12.1/examples/pygtk-demo$ sudo apt-get install python-gobject
[sudo] password for devo:
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-gobject is already the newest version.
python-gobject set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

I have installed my own installation of python 3.0 but... I don't believe that would conflict with my other installations of python... I'm guessing this is not longer a Totem problem and is now a "weird installation" problem. Heh.

I agree with that, because i have the same problem with Rhythmbox and Screenlets.

Screenlets:
josecuervo86@josecuervo86-desktop:~$ screenlets
Traceback (most recent call last):
  File "/usr/share/screenlets-manager/screenlets-manager.py", line 25, in <module>
    import pygtk
ImportError: No module named pygtk

Rhythmbox:
josecuervo86@josecuervo86-desktop:~$ rhythmbox
(rhythmbox:12376): Rhythmbox-WARNING **: Could not import pygtk
ImportError: No module named pygtk
Fallo de segmentación

How can this be fixed if uninstalling the pygtk library and uninstalling the application and then reinstalling them doesn't work. This problem only started happening when I upgraded to Jaunty.

may be it can help... i solved similar problem by this.

http://community.livejournal.com/ubuntu_users/411194.html

p.s.: Sorry for my english

Thank you!! This just solve my problem!!! I remove all the files that started with python from /usr/local/bin

Pd: sorry for my english

Yeah. Deleting the python binary in /usr/local/bin fixed the problem.

I have no problems with /usr/local/bin - there is only my own scripts - but pygtk do work 'strange' on my machine to. It may be a compatibility issue, since my Totem and Rhythmbox work ootb, but my simple, elementar pygtk script (that us to work in 8.10) don't work anymore. And the error message is not very pythonic, or human readable, so, back to WX...

ovoid, a good command to help you troubleshoot would be in the terminal, 'which python'. This will, tell you which binary the command python refers to. The problem that the python binary in /usr/local/bin was that it wasn't referencing the proper paths to libraries such as PyGTK.

This is my firts comment :D
I speak sapnish so sorry for my future gramatical mistakes..

When i open totem
whit GDB
$ gdb totem
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/totem
(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]
(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)
---Type <return> to continue, or q <return> to quit---ryn
(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)
---Type <return> to continue, or q <return> to quit---run
(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)
---Type <return> to continue, or q <return> to quit---run
(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)
(n...

I think that this bug have a relation (sotty english) whit the themes..
because it was wokring fine..

Fix :D

no no fix

With gdb you have to install the debugger symbols from Synaptic in or for it to work. Did you read the previous comments?

Nop sorry

2009/6/20 devo <email address hidden>

> With gdb you have to install the debugger symbols from Synaptic in or
> for it to work. Did you read the previous comments?
>
> --
> Totem crashes on startup
> https://bugs.launchpad.net/bugs/367573
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “python-support” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: totem
>
> Description: Ubuntu 9.04
> Release: 9.04
>
> totem:
> Installed: 2.26.1-0ubuntu5
> Candidate: 2.26.1-0ubuntu5
> Version table:
> *** 2.26.1-0ubuntu5 0
> 500 http://archive.ubuntu.com jaunty/main Packages
> 100 /var/lib/dpkg/status
>
> Well, I expect it to work and open up.
>
> What happened instead is it crashes and the output it gives me in the
> console is this...
>
> ** (totem:21700): WARNING **: Could not import pygtk
> ImportError: No module named pygtk
> Segmentation fault
>
> I have pygtk installed though according to Synaptic so I don't see what the
> problem is. I've tried reinstalling it and reinstalling totem and nothing
> changes...
>

I had the same problem after upgrading to Jaunty and solved it by deleting my self-installed /usr/local/bin/python.

Maybe totem should explicitly use /usr/bin/python instead of the one first found on the path?

This is certainly not a python-support problem.

totem uses libpython to test-load pygtk. People reported here that removing /usr/local/bin/python helped with this situation, but totem doesn't run that. Could it be that you removed /usr/loca/lib/python* instead? That would be a more plausible explanation.

This bug is so old. And Totem doesn't use Python? Totem isn't written in Python? Also, Totem would use the /usr/local/bin/python because that would be the Python that every program using Python in that environment would be using... So removing that one would make sense... Anyways, whatever. This is such an old bug.

i got this bug after a kernel upgrade in Karmic. I solved the issue by reinstalling python-gtk2.

While totem isn't written in Python, many of its plugins are, and totem has a module written to handle python plugins. So if a python coded plugin is enabled when totem is closed, a custom python installed in /usr/local/bin/, and totem restarted, when it reloads its python based plugins import errors occur because the custom python can't find required modules (as described in the link provided by anonyMouse on 2009-05-10).

An alternative to deleting the python binaries from /usr/local/bin is to go to /usr/lib/totem/plugins and prevent access to any folder (using chmod 700 <folder> or tarballing for example) that is a python based plugin (the folder will contain .py/.pyc files). While this is still a band-aid solution, it is an option for those who wish to keep their custom python install in preference to totem's plugins.

I figured out why deleting /usr/local/bin/python solves the problem: As Loïc said, this is surprising because totem uses libpython and not the python executable. However, libpython tries to be clever and looks for the executable itself. That's why deleting the executable steers it towards the system default python in /usr, where pygtk can be found and everything is fine.

A very simple workaround and possibly a fix for the bug is to set PYTHONHOME to "/usr", i.e. call Totem with "PYTHONHOME=/usr totem".

I still think that Totem shouldn't segfault on a missing pygtk, though. The problem with this is in totem-python-module.c: If pygtk can't be found, "totem_python_module_init_python" simply prints a warning and returns. "init_pygobject" is never called, but "totem_python_module_load" later calls "pyg_gil_state_ensure", which leads to the segfault.

I filed an upstream bug with patch for the segfault issue:

https://bugzilla.gnome.org/show_bug.cgi?id=615437

The segfault was fixed in upstream, so totem shouldn't become unusable any more, but rather show errors and then disable the Python plugins.

The workaround (set PYTHONHOME) stays valid.

Very nice workaround Hagen, can confirm it works in Intrepid and Karmic.

Fixed upstream.

SRU team members: Debdiff for 2.30.1 update (which has a fix for this) is attached to bug 535426.

Accepted totem into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Verified: OK
uninstalled and reinstalled, everythings ok.

I've tested the proposed package, the crash is not there anymore, instead a warning is presented to the user, the bug is fixed, thanks for the work.

This bug was fixed in the package totem - 2.30.1-0ubuntu1

---------------
totem (2.30.1-0ubuntu1) lucid-proposed; urgency=low

  [ Martin Pitt ]
  * New upstream bug fix release. Changes since our last git snapshot:
    - Fix crashes on exit.
    - Fix possible crasher when PyGTK isn't available. (LP: #367573)
    - Require gstreamer 0.10.28.1 for queue2 fixes.
    - Fix Youtube search lasting forever while playing Video. (LP: #559862)
    - Fix artifacts or black screen when paused. (LP: #535426)
    - Translation updates.
  * 90_autotools.patch: Refresh for new upstream version.
  * 90_autotools.patch: Revert upstream change of bumping gstreamer
    dependency to 0.10.28.1; set it back to 0.10.28. There are no queue2
    related changes in totem since our previous git snapshot, so this can't
    make a difference.

  [ Loïc Minier ]
  * totem.preinst: Actually remove alternatives by checking for action
    "upgrade" instead of "configure" which isn't used with preinsts; bump
    version to 2.30.0git20100413-0ubuntu2 for that to be effective.
 -- Martin Pitt <email address hidden> Wed, 28 Apr 2010 15:58:47 +0200

Copied lucid-proposed to maverick.