Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.
up vote 0 down vote favorite

I installed the Android Developer Tools (ADT) bundle, which includes the Eclipse platform, using the official instructions. When I run the program from the command line I see this message 8 times:

LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed

When I exit I get:

>(ADT:5170): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion 'GTK_IS_MENU_SHELL(menu)' failed

>(ADT:5170): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion 'GTK_IS_MENU_SHELL(menu)' failed

>(ADT:5170): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertionGTK_IS_MENU_SHELL(menu)' failed`

>(ADT:5170): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion 'GTK_IS_MENU_SHELL(menu)' failed

>(ADT:5170): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion 'GTK_IS_MENU_SHELL(menu)' failed

>(ADT:5170): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

>(ADT:5170): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion 'GTK_IS_MENU_SHELL(menu)' failed

>(ADT:5170): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion 'GTK_IS_MENU_SHELL(menu)' failed

What is going wrong?
and
Should I expect ADT to work normally, or with some errors, or with reduced functionality?

UPDATE

When running as sudo:

sudo adt-bundle-linux-x86_64/eclipse/eclipse

there are no GTK errors. How can I run ADT/Eclipse without sudo and without running into the GTK errors?

share|improve this question
Have you tried running it as sudo? Also is your OS 32-bit or 64-bit? – lordqwerty Feb 1 at 12:31
@lordqwerty 64 bit Ubuntu 12.10 – chobok Feb 4 at 5:41
@lordqwerty running it as sudo give me no GTK errors. Any ideas on how to avoid the errors without sudo? – chobok Feb 4 at 6:02
not sure entirely. I'll post an answer below :) – lordqwerty Feb 5 at 20:26

3 Answers

up vote 0 down vote

Go to this link and download the ADT zip and use it for installation. If you face any problem then let me know.

share|improve this answer
I used that file to install already. – chobok Feb 4 at 5:41
up vote 0 down vote

I think the reason for this is because you're running 64-bit architecture. This can hopefully be fixed quite easy. When running android on 64-bit Ubuntu you need 32-bit libs. This can be easily installed by running the following in a terminal:

sudo apt-get install ia32-libs

Give that a go. If it works without using sudo and your above edit, then happy days! If not I'll take a look around. This fixed issues I had on my 64-bit ubuntu.

share|improve this answer
up vote 0 down vote

Someone having the same issue found that it was related to some PPAs they'd added for access to some GNOME Shell extensions.

Unless it was a standard installation, check if any additional PPAs were added and test for the while using a different desktop environment.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.