Region around notifications became unclickable

Bug #1376382 reported by Cody Garver
256
This bug affects 52 people
Affects Status Importance Assigned to Milestone
Gala
Fix Released
High
Adam Bieńkowski

Bug Description

Until I restarted gala, the area below wingpanel was unclickable

The dimensions of the area were about 1 notification wide and 2 or 3 notifications tall

Related branches

Changed in gala:
status: New → Confirmed
milestone: none → loki-beta1
Revision history for this message
Max Bolotin (maks-bolotin) wrote :

is there a patch/workaround for this?

Revision history for this message
TDT (the-dirtchamber) wrote :

I would also like to know if there's any workaround. It's a very annoying issue...

xapantu (xapantu)
Changed in gala:
importance: Undecided → High
Revision history for this message
Gottano (jan-goes) wrote :

Maybe turning off the notification bubbles could be a temporary fix (seeing this bug is in part activated by the bubbles)

I have done just that and I will report back whether it has worked or not.

Changed in gala:
status: Confirmed → In Progress
assignee: nobody → Adam Bieńkowski (donadigo)
Revision history for this message
energy (donenergie) wrote :

Same issue... Reboot can fix it temporarily but not for ever. Turnig off the notification bubbles didnt't work...

Revision history for this message
Fabio Gomes (fabioxgn) wrote :

This happens to me on Freya too, will it be fixed just on Loki?

Revision history for this message
Mike Lacey (michael-j-lacey) wrote :

Happens to me on Freya, really inconvenient, would be good to see the Loki fix applied to Freya as well.

Revision history for this message
Stiffler (stefan-binder17) wrote :

is there a fix/workaround for freya? it is really annoying.

Revision history for this message
Selwyn Orren (selwyn) wrote :

Hi, I have upgraded to 0.3.2 and I still am getting this bug, has anyone manage to find a workaround yet?

Revision history for this message
Robin Nabel (rnabel) wrote :

Hi all, I found a workaround for this:
kill your gnome-session on startup. I have achieved this by adding a cron task, run:
crontab -e

and then add
@reboot killall gnome-session

Changed in gala:
status: In Progress → Confirmed
assignee: Adam Bieńkowski (donadigo) → nobody
Changed in gala:
milestone: loki-beta1 → loki-rc1
tags: added: notifications
Revision history for this message
jay (a-jay-3) wrote :

I see this bug in Freya. After cold boot everything is OK. If an "Automatic Suspend" notification activates in the upper right screen, the notification will stay active even if the user begins work again. The user cannot click anything behind the "Automatic Suspend" banner and the banner will not go away. If the user lets the computer suspend and then re-awakens, the banner will be gone but the user still cannot click anything in the region that the banner occupied--as if the notification were still in the way. This is extremely annoying because I can't click any links in the menu bar of my browser in that region.

Revision history for this message
Gottano (jan-goes) wrote : Re: [Bug 1376382] Re: Region around notifications became unclickable

It's been about a year this major problem has been identified....any news
regarding possible fixes?

On Tue, 12 Jul 2016 00:01 jay, <email address hidden> wrote:

> I see this bug in Freya. After cold boot everything is OK. If an
> "Automatic Suspend" notification activates in the upper right screen,
> the notification will stay active even if the user begins work again.
> The user cannot click anything behind the "Automatic Suspend" banner and
> the banner will not go away. If the user lets the computer suspend and
> then re-awakens, the banner will be gone but the user still cannot click
> anything in the region that the banner occupied--as if the notification
> were still in the way. This is extremely annoying because I can't click
> any links in the menu bar of my browser in that region.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1376382
>
> Title:
> Region around notifications became unclickable
>
> Status in Gala:
> Confirmed
>
> Bug description:
> Until I restarted gala, the area below wingpanel was unclickable
>
> The dimensions of the area were about 1 notification wide and 2 or 3
> notifications tall
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gala/+bug/1376382/+subscriptions
>

Revision history for this message
Cody Garver (codygarver) wrote :

Haven't seen this recently.

Changed in gala:
status: Confirmed → Incomplete
Revision history for this message
Eric Karnes (eric-karnes1) wrote :

Using Loki beta 2 and experienced this yesterday, still not fixed.

Revision history for this message
Cody Garver (codygarver) wrote :

Eric, there was an update to the window manager that addressed another
notifications issue, it went live earlier today. Would you mind taking note
of whether the bug happens or not after your next system reboot?

On Sun, Jul 31, 2016 at 6:27 PM, Eric Karnes <email address hidden> wrote:

> Using Loki beta 2 and experienced this yesterday, still not fixed.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1376382
>
> Title:
> Region around notifications became unclickable
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gala/+bug/1376382/+subscriptions
>

--
Cody Garver

Revision history for this message
Eric Karnes (eric-karnes1) wrote :

Have yet to experience this bug again after updating gala, fingers crossed.

Revision history for this message
Cody Garver (codygarver) wrote :

Thanks for following up, glad to hear this issue may finally be resolved.

Changed in gala:
status: Incomplete → Fix Committed
assignee: nobody → Adam Bieńkowski (donadigo)
Changed in gala:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.