After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 636716 - MeeGo interface crashes Banshee
MeeGo interface crashes Banshee
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: User Interface
1.9.0
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-07 18:26 UTC by Bennett Kanuka
Modified: 2010-12-07 18:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
banshee --debug output (3.74 KB, text/plain)
2010-12-07 18:26 UTC, Bennett Kanuka 		Details

Description Bennett Kanuka 2010-12-07 18:26:30 UTC 
Created attachment 176020 [details]
banshee --debug output

With banshee-meego extension installed on Ubuntu, pressing the "Show the Netbook interface" button crashes Banshee.

Attached is banshee --debug output from just after startup when the button is pressed until crash.

I am not using MeeGo but Ubuntu 10.10 - I still have an interest in the netbook interface because my screen is kinda small.
Comment 1 Aaron Bockover 2010-12-07 18:32:48 UTC 
Does touching/creating the file /etc/meego-release fix the crash?

$ sudo touch /etc/meego-release

The main UI takes some different code paths if this file exists (as a hint that it's running in a MeeGo desktop).

This file will cause the main UI to look/behave a little differently (more suitable for smaller screen).

You do *not* need to --enable-meego for this to happen though. Passing --enable-meego builds the panel extension, which does absolutely require MeeGo (libmutter-meego) to be useful. Running this panel extension on Ubuntu will just be confusing as you'll have two main windows competing for each other.
Comment 2 Aaron Bockover 2010-12-07 18:33:35 UTC 
Actually looking at the crash - I think this was already fixed in master and stable-1.9 branches in git.

Please try building from one of those branches in git.
Comment 3 Bennett Kanuka 2010-12-07 18:43:51 UTC 
Oops. Thanks. It was fixed in git.