Bug 1385465 - Gnome desktop becomes unstable when mouse is moved or clicked near top panel notification area/date
Summary: Gnome desktop becomes unstable when mouse is moved or clicked near top panel ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 24
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 06:19 UTC by Ajith
Modified: 2017-08-08 19:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 19:27:39 UTC
Type: Bug


Attachments (Terms of Use)
Corrupt desktop view, large number of notifications can be seen (216.32 KB, image/jpeg)
2016-10-17 06:19 UTC, Ajith
no flags Details

Description Ajith 2016-10-17 06:19:17 UTC
Created attachment 1211231 [details]
Corrupt desktop view, large number of notifications can be seen

Description of problem: 
Temporary freeze of desktop is experienced on first login and subsequent screen unlocks. There is no clear errors in the logs. After 40 to 60 seconds, desktop responds. But If I clicked on the date to see pending notifications (or even move the mouse near there), entire desktop freezes and becomes unstable. In this case, it will not come back automatically. I switch to VT, come back again, try Alt+F2 and do shell restart using "r". Desktop may come back. 

Version-Release number of selected component (if applicable): GNOME Shell 3.20.4

How reproducible:

Steps to Reproduce:
1. Create many all day calendar entries/events in evolution for the day or longer period.
2. Set notification for them, so that all comes up together
3. All these notifications will come up in notification area
4. Move the mouse near date, or click on it.

Actual results:
Desktop freezes and/or becomes unstable/unusable.

Expected results:
I should be able to see the pending notifications/scroll through it and clear it

Additional info:
I am using nvidia-367.44 from rpmfusion-nonfree-updates
X11 and gdm login is used.
This observation could be due to too many notifications pending there. 
After deleting the culprit events from Evolution, issue did not recur.

Comment 1 Ajith 2016-10-17 07:49:24 UTC
I am not able to reproduce the original evolution calendar entry/entries that caused this issue. I tried creating few all day events, pasted it multiple times. Desktop is slowing down, but not freexing now.

I also tried this loop, apart from slowness, desktop is not freezing now.
for f in `seq 1 500`; do notify-send "test msg $f"; done

Comment 2 Fedora End Of Life 2017-07-25 23:30:47 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 19:27:39 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.