No module named cluttergst

chinco, you are probably missing the correct version of clutter. How did you install Entertainer? Did you happen to refer to http://wiki.entertainer-project.com/wiki/StartUpGuide? There are good instructions about installation there.

Hi Matt. It still does not work:-( I tried full uninstallation of Entertainer and also all clutter-related packages in Synaptic. Then I followed the guide in wiki. It seem now to be python-clutter that is missing. Is this not supported in Synaptic for Ubuntu 8.10? Might this be the case? How can I get python-clutter? chinco

chinco, pyclutter did not make it into Ubuntu 8.10 for various reasons. However, the entertainer-releases PPA has a packaged version of pyclutter. If you install Entertainer from the PPA (`sudo apt-get install entertainer` after you've added the PPA to your software sources), then it should pull in pyclutter and all its dependencies automatically for you. Is this not how you installed Entertainer?

Matt, I finally managed to install Entertainer after changing from Norwegian to English language and using the command `sudo apt-get install entertainer` in Terminal.
I use the deb lines and keys in the software source list from these locations:
1. https://launchpad.net/~entertainer-releases/+archive/ppa (tried many times, but stopped because Python-clutter could not be found)
2. https://launchpad.net/~rockstar/+archive/ppa (added today, maybe that got me further)

Now Entertainer starts but gives this fault code:
odd@Multitainer:~$ entertainer

Entertainer backend starting...
**
Clutter:ERROR:clutter-stage.c:131:clutter_stage_get_preferred_width: assertion failed: (priv->impl != NULL)
Aborted

chinco,

Basically, I think you have a problem with your clutter installation. I'm going to ask a couple of questions for you to try and resolve this.

Can you check what version of clutter you are running? Do this by typing `python` in a Terminal, followed by `import clutter`, followed by `clutter.__version__` (note that it is two underscores before and after the word "version," so four total). Anything less than 0.8.0 is bad.

To be honest, I'm really surprised that installing from the package didn't work for you. I know for a fact that it can work because I've done it many times with a fresh installation in a virtual machine. Could you walk me through the exact process that you tried to install from the PPA? If we can figure out where that went wrong, maybe we can get you set up quickly by fixing the problem there.

chinco,

Did you add the Jaunty deb line instead of the Intrepid one? I tried to install the Jaunty package on my test box and I got a failure about python-clutter and python-imdbpy, so maybe you just installed from the wrong version repository. I had no problem when I tried from the Intrepid version.

I'll talk to Paul about fixing the Jaunty version, but since you're running 8.10, you'll definitely want the Intrepid version.

Matt,
I have version 0.8.0 of python.
I tried the jaunty deb line first and got the missing python-clutter message that you also mention. Then I tried with both the jaunty and intrepid lines active in software sources and got where I am now. What do you suggest as my next step?

chinco,

I would suggest you try it, but remove the Jaunty repository. If you have both the Jaunty and Intrepid PPA, then it might try to default to Jaunty. So try getting rid of the Jaunty one, just install with Intrepid (so that you're sure it's the Intrepid package) and see how that goes.

Matt,
Do you mean this one: deb http://ppa.launchpad.net/entertainer-releases/ppa/ubuntu intrepid main ?

chinco,

Yep, that is the one you should try to install from.

You should remove deb http://ppa.launchpad.net/entertainer-releases/ppa/ubuntu jaunty main.

Matt,
I tried again and got a starting picture in Entertainer, but also got the following error message:
odd@Multitainer:~$ entertainer
Entertainer backend starting...
Error occured. Please see /home/odd/.config/entertainer/entertainer.log for more information. This is probably not a fatal error. Just wait one minute and try again.
Execution aborted!
odd@Multitainer:~$

The log file of today states:
2009-03-08 11:26:04,443 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.utils.configuration.Configuration object at 0xa26724c>' registered to the message bus.
2009-03-08 11:26:04,452 backend.BackendServer DEBUG Configuration intialized successfully
2009-03-08 11:26:04,452 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.feeds.feed_manager.FeedManager object at 0xa267acc>' registered to the message bus.
2009-03-08 11:26:04,452 backend.BackendServer DEBUG Feed Manager intialized successfully
2009-03-08 11:26:04,453 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.mediacache.media_cache_manager.MediaCacheManager object at 0xa267c6c>' registered to the message bus.
2009-03-08 11:26:04,453 backend.BackendServer DEBUG Media Manager intialized successfully
2009-03-08 11:26:04,453 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.tvguide.guide_updater.GuideUpdater object at 0xa26b26c>' registered to the message bus.
2009-03-08 11:26:04,454 backend.BackendServer DEBUG Guide Updater intialized successfully
2009-03-08 11:26:04,454 backend.core.ConnectionServer DEBUG ConnectionServer waiting incoming connections
2009-03-08 11:26:04,454 backend.BackendServer DEBUG Message scheduler intialized successfully
2009-03-08 11:26:04,457 backend.core.ConnectionServer DEBUG Incoming connection accepted
2009-03-08 11:26:04,458 backend.core.MessageBus DEBUG Message bus locked. Message of type '2' is on the bus.
2009-03-08 11:26:04,458 frontend.FrontendClient DEBUG Connected to the Entertainer backend server.
2009-03-08 11:26:04,471 backend.components.mediacache.VideoCache DEBUG Adding a directory to the video cache. Path is: '/home/odd/Videoer'
2009-03-08 11:26:04,594 frontend.gui.UserInterface DEBUG Frontend GUI initialized succesfully
2009-03-08 11:26:12,253 backend.components.feed.FeedFetcher INFO Feed cache has been updated
2009-03-08 11:26:12,253 backend.core.MessageBus DEBUG Message bus locked. Message of type '4' is on the bus.
2009-03-08 11:27:46,220 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.utils.configuration.Configuration object at 0x966f34c>' registered to the message bus.
2009-03-08 11:27:46,220 backend.BackendServer DEBUG Configuration intialized successfully
2009-03-08 11:27:46,220 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.feeds.feed_manager.FeedManager object at 0x966fbcc>' registered to the message bus.
2009-03-08 11:27:46,220 backend.BackendServer DEBUG Feed Manager intialized successfully
2009-03-08 11:27:46,224 backend.components.mediacache.VideoCache DEBUG Adding a directory to the video cache. Path is: '/home/odd/Videoer'
2009-03-08 11:27:46,226 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.mediacache.media_cache_manager.MediaCacheManager object at 0x966fd6c>' registered to the message bus.
2009-03-08 11:27:46,226 backend.BackendServer DEBUG Media Manager intialized successfully
2009-03-08 11:27:46,226 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.tvguide.guide_updater.GuideUpdater object at 0x9676eec>' registered to the message bus.
2009-03-08 11:27:46,226 backend.BackendServer DEBUG Guide Updater intialized successfully
2009-03-08 11:27:46,226 backend.core.ConnectionServer ERROR Socket failed to bind. Address already in use
2009-03-08 11:27:46,226 backend.BackendServer ERROR ConnectionServer initialization failed!
2009-03-08 11:31:24,781 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.utils.configuration.Configuration object at 0xaafb4cc>' registered to the message bus.
2009-03-08 11:31:24,781 backend.BackendServer DEBUG Configuration intialized successfully
2009-03-08 11:31:24,781 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.feeds.feed_manager.FeedManager object at 0xaafb88c>' registered to the message bus.
2009-03-08 11:31:24,781 backend.BackendServer DEBUG Feed Manager intialized successfully
2009-03-08 11:31:24,784 backend.components.mediacache.VideoCache DEBUG Adding a directory to the video cache. Path is: '/home/odd/Videoer'
2009-03-08 11:31:24,788 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.mediacache.media_cache_manager.MediaCacheManager object at 0xaafba2c>' registered to the message bus.
2009-03-08 11:31:24,788 backend.BackendServer DEBUG Media Manager intialized successfully
2009-03-08 11:31:24,789 backend.core.MessageBus DEBUG MessageHandler '<entertainerlib.backend.components.tvguide.guide_updater.GuideUpdater object at 0xab0ac8c>' registered to the message bus.
2009-03-08 11:31:24,789 backend.BackendServer DEBUG Guide Updater intialized successfully
2009-03-08 11:31:24,790 backend.core.ConnectionServer DEBUG ConnectionServer waiting incoming connections
2009-03-08 11:31:24,790 backend.BackendServer DEBUG Message scheduler intialized successfully
2009-03-08 11:31:24,790 backend.core.ConnectionServer DEBUG Incoming connection accepted
2009-03-08 11:31:24,791 backend.core.MessageBus DEBUG Message bus locked. Message of type '2' is on the bus.
2009-03-08 11:31:24,791 frontend.FrontendClient DEBUG Connected to the Entertainer backend server.
2009-03-08 11:31:24,857 frontend.gui.UserInterface DEBUG Frontend GUI initialized succesfully
2009-03-08 11:31:30,174 backend.components.feed.FeedFetcher INFO Feed cache has been updated
2009-03-08 11:31:30,175 backend.core.MessageBus DEBUG Message bus locked. Message of type '4' is on the bus.

chinco,

Does your problem happen one hundred percent of the time? I would guess that if you try it again, you might have different results. Sometimes Entertainer complains about starting up if it is launched too quickly from the last time it was closed. I would suggest giving it a minute or two between when you opened the application, closed it, then opened it again.

If this problem is repeatable every time, and the interface is never launching, please let me know.

Matt,
This made Entertainer start, but only the backend is loading:
odd@Multitainer:~$ entertainer
Entertainer backend starting...

chinco,

I think that the next thing to test would be if your clutter installation works (clutter is what provides the nice user interface features for Entertainer). You can test it by going to /usr/share/doc/python-clutter/examples and running each test by running `python <insert test filename here>.py`. I'm hoping you get failures at this step because it would help us continue to isolate the issue.

odd@Multitainer:/usr/share/doc/python-clutter/examples$ python behave.pySegmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python behave.py
Segmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python bubbles.py
Segmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python cairo-texture.pySegmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python clock.py
Segmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python custom-actor.py
Clicked!
Segmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python entry.py
key_cb called
key_cb called
key_cb called
key_cb called
key_cb called
key_cb called
Segmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python gtk-clutter.py
Segmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python hello.py
mouse button 1 pressed at (486, 322)
mouse button 3 pressed at (667, 267)

New session:
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python rects.py
0.8.0
stage color: <ClutterColor at 0x8b14648>
Adding element: <clutter.Rectangle object at 0xb7dfc7ac (ClutterRectangle at 0x8e75800)>
Adding element: <clutter.Rectangle object at 0xb7dfc9dc (ClutterRectangle at 0x8e758c8)>
Adding element: <clutter.Rectangle object at 0xb7dfc7ac (ClutterRectangle at 0x8e75990)>
Adding element: <clutter.Rectangle object at 0xb7dfc9dc (ClutterRectangle at 0x8e75a58)>
Adding element: <clutter.Rectangle object at 0xb7dfc7ac (ClutterRectangle at 0x8e75b20)>
Adding element: <clutter.Rectangle object at 0xb7dfc9dc (ClutterRectangle at 0x8e75be8)>
Adding element: <clutter.Rectangle object at 0xb7dfc7ac (ClutterRectangle at 0x8e75cb0)>
Adding element: <clutter.Rectangle object at 0xb7dfc9dc (ClutterRectangle at 0x8e75d78)>
Adding element: <clutter.Rectangle object at 0xb7dfc7ac (ClutterRectangle at 0x8e75e40)>

New session:
odd@Multitainer:/usr/share/doc/python-clutter/examples$ python script.py
Timeline: move-timeline
Timeline: scale-timeline
Timeline: fade-timeline
running the score
timeline started: move-timeline
timeline started: scale-timeline
timeline started: fade-timeline
quitting
Segmentation fault
odd@Multitainer:/usr/share/doc/python-clutter/examples$

I did not know how to stop each session so I used Close on the bottom line. Each session made frames of various size on the right side of the screen. I saw a moving square, rising bubbles, a moving clock and so on. I hope you can see what might be wrong from the text above. Is there something else I should look for?

chinco,

I think I'm running out of ideas. Nothing in your log indicates any real show stopping problems. You've indicated that you installed from the Intrepid PPA. You've proven that you can successfully runAre you running Entertainer from the Applications menu, or are you launching it from the Are you running Entertainer from the Applications menu, or are you launching it from the clutter. And, from what you've told me, you aren't getting any significant errors.

I'm not exactly sure what to tell you. I think one thing that you could try is to run Entertainer from the current trunk. The PPA should have installed all the correct dependencies so I would suggest running `bzr branch lp:entertainer` (you'll have to install bzr). Once you have a branch of the trunk, cd into the entertainer directory, then type `./entertainer`. This will cause you to run Entertainer from that branch. If it's not working from there, you could attempt to poke around in the source code and add print statements at various points to see if/where the code is dying.

Any advise I could offer beyond that starts to get *really* technical and would involve using the Python debugger. Sorry I can't be more helpful. I wish I could help you determine what your problem is, but I think you've stumped me. If you have any more information that you think might be helpful, I could try to interpret it, but I don't know how much more I could do.

If you can do something a little more real time, I'm typically logged into IRC in #entertainer on the Freenode network. If I can't help you or am not available, maybe someone else in the channel can't assist you.