UNR Karmic launcher buttons not working

[jflaming]

The buttons in the launcher do not respond to mouse clicks in the UNR Karmic RC on my Inspiron 700m. I can click on the things in the taskbar, and they work fine. And I can hover over the left hand buttons and they highlight (although slowly).

After installing the desktop switcher and going to the gnome menus, I can use my trackpad or mouse normally. But still the launcher does not respond to any click events.

[markc (mark-shop)]

Exact same machine, same problem. 9.10 desktop works great, but the remix launcher won't let me click.

[J (jonathan-vola)]

Many people on ubuntuforums.org are experiencing this issue, suggest "Critical" Importance as it pretty much disables netbooks under karmic.

It took me a couple of hours and some commands to figure out how to access my stuff.

[Mahesh Asolkar (asolkar)]

Some folks on the forums have indicated that this may be related to Bug 521714 - Clutter picking broken on Intel 855GME (https://bugzilla.redhat.com/show_bug.cgi?id=521714).

Can the affected subscribers please confirm if they are using Intel 855GME? I have the same issue and my laptop does use Intel 855GME graphics.

[deChrLam (christopher-lambe)]

Same problem on an oldish Laptop with Intel 855GM graphics.

[kronos (henrik-ruul)]

Today I installed UNR 9.10 and experience exactly the same bug as you guys. I'm also using Intel 855GM graphics but I'm unsure what type of driver that is used.

Any news?

This should perhaps be raised to a critical bug...

[Aksel Mjeldheim (akselmjeldheim)]

I have same problem both on a Lenovo IdeaPad U350 and an Asus eee900. I have tried using the keyboard as well. I am able to move around using arrow keys, but sometimes it does not respond when selecting items using Enter key. Same behavior as using the mouse. Using Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07).

[Aksel Mjeldheim (akselmjeldheim)]

Sorry. I was in fact wrong about the Asus. Asus works fine, but Lenovo still acts up.

[Jamie (jamie-jamie-jones)]

I did a fresh install today. I too have this bug. My hardware is an aspire one 110

[Etienne (etienne-phillips-gmail)]

Also have this problem on a VIA Epia 15000NX with a CX700M2 chipset. Running the openchrome driver to get decent graphics performance.

Have the issue using a Logitech USB wireless mouse and an eGalax touch screen.

Is there a solution/workaround for this?

[Didier Roche-Tolomelli (didrocks)]

I think this issue should be more related to the kernel or other clutter related thing.

Can you try with the coming beta of lucid? You can also switch session on it to choose the gnome session in gdm and see if you have the same issue there.
Thanks a lot for testing this.

[Etienne (etienne-phillips-gmail)]

Unfortunately, I can confirm that this bug is still present in the Lucid live CD. The normal gnome session is fine. It's just the Clutter Launcher interface that's poked...

Thanks!

[Etienne (etienne-phillips-gmail)]

Just to add, I ran the live CD, installed the ubuntu-netbook-remix package, and logged out then back in to enable the NBR...

[Didier Roche-Tolomelli (didrocks)]

Right, it seems to be linked to that bug in the intel driver. I'm reassigning so the issue to xorg-x11-drv-intel package. I'll update next week the full clutter stack in lucid, but I don't think regarding the comment this will fix it and it's driver related and not clutter one.

You can still use the 2D launcher (see the session on gdm) which should work. Maybe we should fallback on it for this hardware? Not sure what's the right decision is.

PS: you should have installed ubuntu-netbook metapackage, as ubuntu-netbook-remix is just a dummy package in lucid which depends on the ubuntu-netbook one for the transition, but that's more a detail ;)

[Bryce Harrington (bryce)]

Hi jflaming,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Etienne (etienne-phillips-gmail)]

Ok, tested the 2D session on the openchrome-powered VIA system (using the ubuntu-netbook meta-package ;-) ), and it works fine, as long as you wait for about 30 seconds after login for the screen to finish redrawing itself, each time with a bit more (like task bar, then menu bar, then mouse cursor).

Since I'm not using the intel driver, are you sure it's an intel driver related bug? I'm pretty sure I've got 3D acceleration as I'm getting 1000+fps on a windowed glxgears...

Anyway, the 2D session is way better than a non-working 3D session, so at least I can continue happily!

Thanks again
Etienne

[Bryce Harrington (bryce)]

[Resetting to incomplete since we need a response from the original reporter on this].

[Jan-Erik Mai (in0de)]

bug still exists in latest UNR (lucid), Moblin, Ubuntu Unity, GnomeShell...
tested with 3 different laptops all with intel 855GM graphics.

clicking doesnt work, in moblin you sometimes have luck to see a icon hover color change but clicking still doesnt work. same with latest ubuntu unity (upcoming), latest gnomeshell and other apps.

i still guessing it is a intel driver related bug with clutter/mutter/3dcompositing...

hope it helps a bit

[Jan-Erik Mai (in0de)]

i am sorry i must correct, latest gnome-shell works.

[Bryce Harrington (bryce)]

@etienne-phillips-gmail - thanks for providing that info, but we would like to see it from the original reporter. We may want to send this bug report upstream, but upstream has a hard and fast rule that logs from someone other than the original reporter are not acceptable. The reason for that is that quite often with X.org bug reports, two people may *think* they have the same issue based on commonality of symptoms and/or hardware, but in truth they have separate issues and mixing the report and the files can cause the developers some confusion.

If this bug report seems not to be getting attention, I would encourage you to file a new bug report with this data, and simply reference this bug report in your bug description.