Bug 1772276 - gnome-shell xorg session freezes after login while pomodoro is active
Summary: gnome-shell xorg session freezes after login while pomodoro is active
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell-extension-pomodoro
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabian Affolter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-14 00:58 UTC by Basil Eric Rabi
Modified: 2020-09-05 01:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-05 01:50:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Basil Eric Rabi 2019-11-14 00:58:27 UTC
Description of problem:
While pomodoro is still active (counting down) and the machine is restarted, gnome shell xorg session freezes (1 cpu core is 100%) after logging in.

Version-Release number of selected component (if applicable):
gnome-shell-extension-pomodoro-1:0.15.2-0.1.gitcb1ad32.fc31.x86_64

How reproducible:
~50%

Steps to Reproduce:
1. Activate pomodoro
2. Restart machine
3. Login to xorg session

Actual results:
Gnome shell freezes

Expected results:
Gnome shell does not freeze

Additional info:
This does not happen in wayland. Gnome shell also freezes sometimes during pomodoro break.

Comment 1 Basil Eric Rabi 2019-11-14 14:27:46 UTC
Seems to be 100% reproducible.

Comment 2 Mat Booth 2020-09-04 12:37:51 UTC
Newest version of gnome-pomodoro in Fedora 31 is: gnome-shell-extension-pomodoro-0.16.0-1.fc31

Do you still see the problems with this latest version?

Comment 3 Basil Eric Rabi 2020-09-05 01:50:02 UTC
I can't say for sure in F31 but in F32, this issue is not present. Xorg session does not freeze during log-in when pomodoro is active. For anyone who are experiencing this issue in F31, the solution is just to upgrade to F32.


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