No icon in Ubuntu 9.04 (just a dot)

Asked by Brendan

Hi,

I've installed gnomenu 1.8 on Ubuntu 9.04 (upgraded from 8.10 yesterday) with no problem. Adding it from the Add to Panels menu gives no error message, but the only thing that shows up on the panel is a one pixel dot. I can't click it to get a menu or anything. I see /usr/bin/GnoMen running, which seems to be a process associated with gnomenu.

I'd really love to have this menu working, it looks great!

Thanks,
Brendan

Question information

Language:
English Edit question
Status:
Expired
For:
GnoMenu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Its a known bug

https://bugs.launchpad.net/gnomenu/+bug/308272

Please monitor this for changes.

Thanks

Revision history for this message
Brendan (bleddy) said :
#2

Well, I tried all the suggestions in the other thread. Still no luck. A few others on the Ubuntu forums are having the problem with 9.04. I'll keep my eye on both threads for the solution.

Thanks for the super fast response.

Revision history for this message
technoshaun (shaun-marolf) said :
#3

technoshaun suggests this article as an answer to your question:
FAQ #283: “No Icons in GnoMenu Menu Panel”.

Revision history for this message
technoshaun (shaun-marolf) said :
#4

Revert back to Gnomenu. 1.8 has some serious bugs with Jaunty and are being fixed for the 1.9 release.

Revision history for this message
technoshaun (shaun-marolf) said :
#5

Meant to say revert back to GnoMenu 1.7

Revision history for this message
technoshaun (shaun-marolf) said :
#6

Known bugs with 1.8

Revision history for this message
Brendan (bleddy) said :
#7

Okay, I reverted to 1.6 last night, since it's known to work with Jaunty. I'll wait for 1.9 to come out. Thanks!

Revision history for this message
Brendan (bleddy) said :
#8

Thanks technoshaun, that solved my question.

Revision history for this message
technoshaun (shaun-marolf) said :
#9

GnoMenu 1.9 corrected issue