On Sun, 7 Sep, 2014 at 3:38 AM, Tom Beckmann <email address hidden>
wrote:
> Could you please re-test this with the newest gala updates installed?
> (Revision 413 that is, you can check if you have that version via
> "apt-
> cache show gala | grep Version" and look for the "r413")
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1357054).
> https://bugs.launchpad.net/bugs/1356785
>
> Title:
> Notifications cannot be dismissed when anything is behind it
>
> Status in Gala Window Manager:
> Confirmed
>
> Bug description:
> As long as there is a window behind the notification it cannot be
> dismissed or interacted with in anyway. I have uploaded a video to
> the google plus community which I will link below. Running Freya
> Beta
> 1 system up to date as of Aug 14, 0220
>
> Video:
> https://plus.google.com/117763153598905243679/posts/jgerCpSQhhr
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gala/+bug/1356785/+subscriptions
Looks like it's fixed. Good work!
On Sun, 7 Sep, 2014 at 3:38 AM, Tom Beckmann <email address hidden> /bugs.launchpad .net/bugs/ 1356785 /plus.google. com/11776315359 8905243679/ posts/jgerCpSQh hr /bugs.launchpad .net/gala/ +bug/1356785/ +subscriptions
wrote:
> Could you please re-test this with the newest gala updates installed?
> (Revision 413 that is, you can check if you have that version via
> "apt-
> cache show gala | grep Version" and look for the "r413")
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1357054).
> https:/
>
> Title:
> Notifications cannot be dismissed when anything is behind it
>
> Status in Gala Window Manager:
> Confirmed
>
> Bug description:
> As long as there is a window behind the notification it cannot be
> dismissed or interacted with in anyway. I have uploaded a video to
> the google plus community which I will link below. Running Freya
> Beta
> 1 system up to date as of Aug 14, 0220
>
> Video:
> https:/
>
> To manage notifications about this bug go to:
> https:/