Bug 312578 - interaction with some topbar widgets not possible
Summary: interaction with some topbar widgets not possible
Status: RESOLVED FIXED
Alias: None
Product: Active
Classification: Unmaintained
Component: Top Bar (show other bugs)
Version: PA 3
Platform: Other Linux
: NOR normal
Target Milestone: unscheduled
Assignee: active
URL:
Keywords:
: 319587 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-01-04 00:45 UTC by Michael Bohlender
Modified: 2013-12-02 16:17 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Bohlender 2013-01-04 00:45:17 UTC
I can't interact with the following things from the top bar:

# device notifier
# power
# location
# slc

steps to reproduce: 

1. klick on any of the listed things.
-> dropdown menu appears

2. try to interact with that menu
-> nothing happens

reproduceable: most of the time

i managed to trigger the star rating and the send by mail once by wildly klicking at it at high rate.
no luck with the rest though.

what works sometimes:

# interaction with notification 
(every 5th time or so)

what works:
# kmix
# networkmanger
# home


Device: Nexus 7,  Mer
Comment 1 Shmerl 2013-01-04 00:48:00 UTC
I confirm, I noticed this with notification widget. Only tapping multiple times with high frequency actually deletes entries from there.
Comment 2 Marco Martin 2013-01-21 16:03:12 UTC
this seems an issue related to ARM: on the intel image this problem doesn't seem to happen and i already heard of people having this problem on the archos adaptation.

is the top panel correctly interagible?
Comment 3 Michael Bohlender 2013-01-22 10:53:35 UTC
I don't understand your question. What do you mean by "interagible" ?
Comment 4 Aaron J. Seigo 2013-01-23 14:19:56 UTC
I assume it was a typo and should have been "interactible" (which also isn't really a proper word ;) .. or: "is the panel as a whole interactive" or "can you interact with the panel" ... e.g. can you pull the panel down to show the peak/launch areas.
Comment 5 Marco Martin 2013-01-23 14:33:29 UTC
interagible is just a bad literal translation :p
means: is possible to interact with the panel?
several things may happen, like
* it all works,
* is possible to pull it down but not possible to interact with anything in it
* stuff in the panel like the menu can be interacted with, but the window strip not
* window strip can be interacted with, not the rest
* ...
Comment 6 Michael Bohlender 2013-01-23 17:44:48 UTC
yes i can interact with:
# kmix
# networkmanger
# home 
on the bar. 

also pull it down and:
# switch windows
# start applications
Comment 7 Michael Bohlender 2013-04-07 12:24:23 UTC
I installed the latest image today. Now networkmanager has the same problem.
Comment 8 Michael Bohlender 2013-04-10 00:20:25 UTC
rcg confirmed the bug on irc.
Comment 9 Michael Bohlender 2013-04-13 19:29:03 UTC
Interestingly the notifications and power works now.

works: 

# home
# kmix
# notifications
# power

does not work:
# network manager
# slc
# device notifier 
 # location
Comment 10 Ryan McCann 2013-05-09 20:47:57 UTC
*** Bug 319587 has been marked as a duplicate of this bug. ***
Comment 11 Jan Grulich 2013-06-14 13:02:06 UTC
I can confirm the same problem, I'm running PA 4 (RC1) on my Nexus 7 with fully updated system and all applets in the top bar are unusable. When I try to click on something then works 1 of 20 clicks or none.
Comment 12 Rex Dieter 2013-11-21 19:12:02 UTC
may be related to bug #282975 "Plasmoid's buttons/checkboxes unclicable on arm builds"
Comment 13 Rex Dieter 2013-12-02 16:11:03 UTC
See http://mail.kde.org/pipermail/active/2013-November/007228.html
and quick-n-dirty workaround:
http://goo.gl/ph8OqQ
Comment 14 Michael Bohlender 2013-12-02 16:14:16 UTC
Fixed by workaround. See above.
Comment 15 Rex Dieter 2013-12-02 16:16:34 UTC
1.  It's not fixed upstream
2.  its an arch-specific hack, not a fix
Comment 16 Rex Dieter 2013-12-02 16:17:23 UTC
that said, I guess we can reclose this, and I'd be happy to continue tracking the issue in the older bug #282975