Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: After stopping/terminating the pomodoro extension using its 'Quit' menu option, it is not possible to get the pomodoro extension to start again. This applies across logoff/logon and across restart/reboot of Fedora. Version-Release number of selected component (if applicable): $ /usr/bin/gnome-pomodoro --version Pomodoro 0.20.0 $ rpm -q gnome-pomodoro gnome-pomodoro-0.20.0-1.fc35.x86_64 How reproducible: Once the 'Quit' menu item (right-click on the Pomodoro "circle", and select 'Quit') has been selected and Pomodoro extension has stopped, it is not possible to get the extension to start again. It is possible from the shell to get the Pomodoro application to display its "egg" window, but once the start button has been clicked on, the application runs for two seconds only (from 25:00 to 24:58) and then freezes. Using the Gnome Settings application, it is possible to turn on and turn off the notifications for Pomodoro, but this setting has no effect on whether the Pomodoro extension appears on the status line (it does not appear). Steps to Reproduce: 1. Install the gnome-pomodoro package. 2. Turn on the notifications for the Pomodoro extension via the Gnome Settings application 3. An open-circle icon for the Pomodoro extension should appear on the status line. Right-click on the circle and start the extension via its menu. 4. After the extension is running, right-click on the the open-circle icon again and select 'Quit' from its menu. Actual results: At this point, no attempts to restart the Pomodoro extension (such as via the Gnome Settings application) will work. Expected results: It should be possible via the Gnome Settings application to stop and then restart notifications for Pomodoro, and its icon (an open circle) should appear on the Gnome status line. Or, the icon should appear after logging off and logging on. Or, the icon should appear after rebooting and logging on. Also, if /usr/bin/gnome-pomodoro is run from a shell prompt, then the Pomodoro application timer should appear and should not freeze after running for two seconds. Additional info: Deleting the data files that are generated by gnome-pomodoro has no effect; the application still fails to run correctly after: $ cd ~/.local/share/gnome-pomodoro $ rm -f * Also, uninstalling and re-installing the gnome-pomodoro package had no effect. And '$ rpm -V gnome-pomodoro' shows no errors in the installed package.
Restarting the "Pomodoro" application from the Gnome launcher works fine for me. Do you get any errors if you start it from the command line, e.g. with this command? $ gnome-pomodoro
(In reply to Mat Booth from comment #1) > Restarting the "Pomodoro" application from the Gnome launcher works fine for > me. Do you get any errors if you start it from the command line, e.g. with > this command? > > $ gnome-pomodoro Here are the results: $ /usr/bin/gnome-pomodoro The Pomodoro application window is displayed with the Timer, Stats, and menu buttons, along with the large Play/right-arrow button that should be able to click to start the timer. The application is now frozen before clicking on any buttons. Even if nothing is clicked on, then after two to three seconds, a window is displayed with the text: "Pomodoro" is not responding. You may choose to wait a short while for it to continue or force the application to quit entirely. The window then includes two buttons with the text: Force Quit | Wait Note that before clicking on "Force Quit", three new files have been created in ~/.local/share/gnome-pomodoro: 1) database.sqlite, 2) database.sqlite-shm, and 3) database.sqlite-wal. Starting Pomodoro from the Gnome launcher yields similar results. The Pomodoro timer application window is displayed, but it is not responsive to any mouse clicks and eventually displays the "Pomodoro" is not responding window.
(In reply to Mat Booth from comment #1) > Restarting the "Pomodoro" application from the Gnome launcher works fine for > me. Do you get any errors if you start it from the command line, e.g. with > this command? > > $ gnome-pomodoro Note also that this might be related to how Pomodoro is started initially. Instead of starting Pomodoro from the Gnome launcher, start it via the Gnome Settings / Notification, turning on the notification for Pomodoro. When Pomodoro is started by this method, the Pomodoro application window is not displayed. Instead, a Pomodoro icon (a hollow circle) is added to the Gnome status area. The Pomodoro application can then be controlled by right-clicking on the Pomodoro icon, including an option to quit the Pomodoro application. It is this method that appears to cause the problem that prevents Pomodoro from being restarted -- some interaction between the application and some other Gnome controller, perhaps. Also, I have reproduced this problem on a second computer. Once I quit Pomodoro via the Pomodoro icon on the status line, it cannot be restarted.
Messages reported in /var/log/messages when Pomodoro is started via the Gnome launcher: systemd[26969]: Started dbus-:1.2-org.gnome.Pomodoro. dleyna-renderer-service[36868]: Client :1.409 lost dleyna-renderer-service[36868]: dLeyna: Exit systemd[26969]: dbus-:1.2-org.gnome.clocks: Consumed 1.088s CPU time. At this point, the Pomodoro application window is displayed. Click on the large "play" button in the Pomodoro application. Within 2 minutes, the '"Pomodoro" is not responding' window is displayed. Click on the "Force Quit" button in this new window. Then the following messages are generated in /var/log/messages: dbus-:1.2-org.gnome.Pomodoro: Main process exited, code=killed, status=9/KILL dbus-:1.2-org.gnome.Pomodoro: Failed with result 'signal'.
This problem persists in Fedora 36. After upgrading one of the two computers on which I have this problem, the Gnome Settings application is not able to enable the Pomodoro notification in the status area.
Can you try with version 0.21.1 when it hits the testing repo? https://bodhi.fedoraproject.org/updates/FEDORA-2022-bfb43e54c3
(In reply to Mat Booth from comment #6) > Can you try with version 0.21.1 when it hits the testing repo? > > https://bodhi.fedoraproject.org/updates/FEDORA-2022-bfb43e54c3 Yes. Two questions: 1. Can you provide a detailed list of commands (at a terminal shell) to issue to carry this out? (Presumably, this would be a "dnf" command(s) with some option to specify the testing repo.) 2. Can you provide details to determine when gnome-pomodoro version 0.21.1 has been added to the testing repo?
Sure, the link I posted has all the details. Quoting from that page the command to install the test update is this: sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-bfb43e54c3 And the update details contains the link to the upstream change notes: Update to latest upstream release: https://github.com/gnome-pomodoro/gnome-pomodoro/blob/0.21.1/NEWS
Also if you follow the link it will show when the update is available in the repo (it will show "testing" instead of "pending->testing")
(In reply to Mat Booth from comment #9) > Also if you follow the link it will show when the update is available in the > repo (it will show "testing" instead of "pending->testing") 1. OK. According to https://bodhi.fedoraproject.org/updates/FEDORA-2022-bfb43e54c3 "This update has been pushed to testing." 2. Attempting to update, but without success: $ sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-bfb43e54c3 Last metadata expiration check: 0:40:49 ago on Sun 15 May 2022 10:36:32 AM EDT. No security updates needed, but 109 updates available Dependencies resolved. Nothing to do. Complete! 3. Repeating the "dnf upgrade" command, but with "gnome-pomodoro" argument added: $ sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-bfb43e54c3 gnome-pomodoro Last metadata expiration check: 0:43:50 ago on Sun 15 May 2022 10:36:32 AM EDT. No security updates needed for "gnome-pomodoro", but 1 update available Dependencies resolved. Nothing to do. Complete! Please let me know if there is some error in the above commands.
It does say "No security updates needed, ....." -- is your machine configured for security updates only? Or maybe it's not synched to your local mirror yet (in which case, wait longer) or maybe your metadata cache is out of date (try "sudo dnf clean all" first) FWIW the command works fine here.
(In reply to Mat Booth from comment #11) > It does say "No security updates needed, ....." -- is your machine > configured for security updates only? > As far as I know, neither of two computers (one with Fedora Workstation 35, one with Fedora Workstation 36) has this restriction, unless that is the default for a Fedora Workstation. The "dnf upgrade" command works when the option "--advisory=FEDORA-2022-bfb43e54c3" is omitted and "gnome-pomodoro" is added. $ sudo dnf upgrade --enablerepo=updates-testing gnome-pomodoro After the dnf upgrade completes: $ rpm -q gnome-pomodoro gnome-pomodoro-0.21.1-1.fc35.x86_64 Pomodoro can then be started (without logging off or rebooting) from the Gnome Launcher. This then puts the Pomodoro notification icon (an open circle) in the Gnome status area. Logging off and logging on keeps the Pomodoro icon in the status area. Rebooting and logging on keeps the Pomodoro status area. Also, quitting Pomodoro from the Pomodoro icon (right-click on the icon and select "Quit" from the menu) and restarting Pomodoro from the Gnome Launcher still works. So, it appears that the problem has been fixed. Finally, the same sequence of commands above works on Fedora 36, too.
> Or maybe it's not synched to your local mirror yet (in which case, wait > longer) or maybe your metadata cache is out of date (try "sudo dnf clean > all" first) Trying this after the solution, above (Comment #12): $ sudo dnf clean all 119 files removed $ sudo dnf remove gnome-pomodoro sudo dnf install gnome-pomodoro Fedora 35 - x86_64 2.0 MB/s | 79 MB 00:39 Fedora 35 openh264 (From Cisco) - x86_64 4.1 kB/s | 2.5 kB 00:00 Fedora Modular 35 - x86_64 1.6 MB/s | 3.3 MB 00:02 Fedora 35 - x86_64 - Updates 2.7 MB/s | 30 MB 00:11 Fedora Modular 35 - x86_64 - Updates 1.3 MB/s | 3.1 MB 00:02 Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: gnome-pomodoro x86_64 1:0.20.0-1.fc35 fedora 6.0 M Transaction Summary ================================================================================ Install 1 Package Total download size: 6.0 M Installed size: 6.8 M Is this ok [y/N]: y ... Installed: gnome-pomodoro-1:0.20.0-1.fc35.x86_64 Complete! $ sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-bfb43e54c3 Fedora 35 - x86_64 - Test Updates 2.5 MB/s | 7.5 MB 00:02 Last metadata expiration check: 0:00:04 ago on Mon 16 May 2022 01:30:26 PM EDT. No security updates needed, but 109 updates available Dependencies resolved. Nothing to do. Complete! $ sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-bfb43e54c3 gnome-pomodoro Last metadata expiration check: 0:00:51 ago on Mon 16 May 2022 01:30:26 PM EDT. No security updates needed for "gnome-pomodoro", but 1 update available Dependencies resolved. Nothing to do. Complete! So, the "dnf clean all" did NOT change the result (no upgrade). Finally, repeating the last "dnf upgrade" command, above, but with the "--advisory" option deleted works again for the second time: $ sudo dnf upgrade --enablerepo=updates-testing gnome-pomodoro Last metadata expiration check: 0:02:27 ago on Mon 16 May 2022 01:30:26 PM EDT. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Upgrading: gnome-pomodoro x86_64 1:0.21.1-1.fc35 updates-testing 6.0 M Transaction Summary ================================================================================ Upgrade 1 Package Total download size: 6.0 M Is this ok [y/N]: y Downloading Packages: gnome-pomodoro-0.21.1-1.fc35.x86_64.rpm 3.2 MB/s | 6.0 MB 00:01 -------------------------------------------------------------------------------- Total 2.9 MB/s | 6.0 MB 00:02 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Upgrading : gnome-pomodoro-1:0.21.1-1.fc35.x86_64 1/2 Cleanup : gnome-pomodoro-1:0.20.0-1.fc35.x86_64 2/2 Running scriptlet: gnome-pomodoro-1:0.20.0-1.fc35.x86_64 2/2 Verifying : gnome-pomodoro-1:0.21.1-1.fc35.x86_64 1/2 Verifying : gnome-pomodoro-1:0.20.0-1.fc35.x86_64 2/2 Upgraded: gnome-pomodoro-1:0.21.1-1.fc35.x86_64 Complete! Please let me know if there is some additional step or configuration that might make the "--advisory" option work successfully.
FEDORA-2022-bfb43e54c3 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bfb43e54c3
FEDORA-2022-879f2c493b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-879f2c493b
(In reply to Mark Harig from comment #12) > So, it appears that the > problem has been fixed. Great, thanks for testing.
FEDORA-2022-bfb43e54c3 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-879f2c493b has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.