Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1017909: gnome-shell-pomodoro: Package unusable in Bullseye
22 views
Skip to first unread message
Imre Jonk
Aug 22, 2022, 6:10:03 AM8/22/22
to
Package: gnome-shell-pomodoro
Version: 0.18.0-0.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The gnome-shell-pomodoro version 0.18.0-0.1, present in Debian
Bullseye, is completely unusable as it freezes almost immediately after
starting. The window then has to be quit forcibly. Upgrading the
package (and its data package) to version 0.21.1-1 (currently present
in Bookworm and unstable) solved the problem for me.
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-17-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-shell-pomodoro depends on:
ii gnome-shell 3.38.6-1~deb11u1
ii gnome-shell-pomodoro-data 0.21.1-1
ii libc6 2.31-13+deb11u3
ii libcairo2 1.16.0-5
ii libcanberra0 0.30-7
ii libglib2.0-0 2.66.8-1
ii libgom-1.0-0 0.4-1
ii libgstreamer1.0-0 1.18.4-2.1
ii libgtk-3-0 3.24.24-4+deb11u2
ii libpeas-1.0-0 1.28.0-2+b1
gnome-shell-pomodoro recommends no packages.
gnome-shell-pomodoro suggests no packages.
-- no debconf information
Version: 0.18.0-0.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The gnome-shell-pomodoro version 0.18.0-0.1, present in Debian
Bullseye, is completely unusable as it freezes almost immediately after
starting. The window then has to be quit forcibly. Upgrading the
package (and its data package) to version 0.21.1-1 (currently present
in Bookworm and unstable) solved the problem for me.
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-17-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-shell-pomodoro depends on:
ii gnome-shell 3.38.6-1~deb11u1
ii gnome-shell-pomodoro-data 0.21.1-1
ii libc6 2.31-13+deb11u3
ii libcairo2 1.16.0-5
ii libcanberra0 0.30-7
ii libglib2.0-0 2.66.8-1
ii libgom-1.0-0 0.4-1
ii libgstreamer1.0-0 1.18.4-2.1
ii libgtk-3-0 3.24.24-4+deb11u2
ii libpeas-1.0-0 1.28.0-2+b1
gnome-shell-pomodoro recommends no packages.
gnome-shell-pomodoro suggests no packages.
-- no debconf information
Tobias Frost
Aug 22, 2022, 10:20:03 AM8/22/22
to
Control: tags -1 unreproducible
Hi Imre,
> Dear Maintainer,
>
> The gnome-shell-pomodoro version 0.18.0-0.1, present in Debian
> Bullseye, is completely unusable as it freezes almost immediately after
> starting. The window then has to be quit forcibly. Upgrading the
> package (and its data package) to version 0.21.1-1 (currently present
> in Bookworm and unstable) solved the problem for me.
I've just test installed a fresh Debian bullseye to see if I can reproduce
the behaviour you are experiencing. Unfortunatly I couldn't…
Do you have other extensions enabled? Is there something else special on your
system? Does journalctl --user give any hints?
Do you have other packages not originating from Debian/bullseye installed?
Are you on Wayland or X11?
--
Cheers,
tobi
Hi Imre,
> Dear Maintainer,
>
> The gnome-shell-pomodoro version 0.18.0-0.1, present in Debian
> Bullseye, is completely unusable as it freezes almost immediately after
> starting. The window then has to be quit forcibly. Upgrading the
> package (and its data package) to version 0.21.1-1 (currently present
> in Bookworm and unstable) solved the problem for me.
the behaviour you are experiencing. Unfortunatly I couldn't…
Do you have other extensions enabled? Is there something else special on your
system? Does journalctl --user give any hints?
Do you have other packages not originating from Debian/bullseye installed?
Are you on Wayland or X11?
--
Cheers,
tobi
Imre Jonk
Aug 22, 2022, 10:40:07 AM8/22/22
to
Hi Tobias, thanks for the quick reply.
On Mon, 2022-08-22 at 16:09 +0200, Tobias Frost wrote:
> I've just test installed a fresh Debian bullseye to see if I can
> reproduce the behaviour you are experiencing. Unfortunatly I
> couldn't…
Crap, now I can't either... I've downgraded to 0.18.0-0.1 again but
everything works fine.
There are some bug reports upstream that describe the same freezing
behavior that I was seeing:
https://github.com/gnome-pomodoro/gnome-pomodoro/issues?q=is%3Aissue+freeze
People there report that reloading the GNOME session (e.g. by logging
out and back in) works. Or that the Pomodoro GNOME extension has to be
explicitly enabled. I don't think I reloaded my GNOME session in the
meantime, but I could have.
> Do you have other extensions enabled?
No.
> Is there something else special on your system?
Most desktop systems are special snowflakes, but I don't have any
obscure GNOME tweaks or options enabled that I know of.
> Does journalctl --user give any hints?
Only this:
aug 22 11:37:56 silicon dbus-daemon[1762]: [session uid=1000 pid=1762]
Activating service name='org.gnome.Pomodoro' requested by ':1.33'
(uid=1000 pid=1901 comm="/usr/bin/gnome-shell ")
aug 22 11:37:56 silicon dbus-daemon[1762]: [session uid=1000 pid=1762]
Successfully activated service 'org.gnome.Pomodoro'
aug 22 11:37:57 silicon gnome-shell[1901]: Couldn't find child
[0x5564b642ed70 Gjs_ui_windowPreview_WindowPreview:last-child
("Pomodoro")] in window slots
aug 22 11:37:57 silicon gnome-shell[1901]: Couldn't find child
[0x5564b642ed70 Gjs_ui_windowPreview_WindowPreview:first-child
("Pomodoro")] in window slots
> Do you have other packages not originating from Debian/bullseye
> installed?
A few, but nothing related to desktop environments / GUI stuff.
> Are you on Wayland or X11?
Wayland.
I'll try reproducing the issue in a clean Bullseye VM later today.
On Mon, 2022-08-22 at 16:09 +0200, Tobias Frost wrote:
> I've just test installed a fresh Debian bullseye to see if I can
> reproduce the behaviour you are experiencing. Unfortunatly I
> couldn't…
everything works fine.
There are some bug reports upstream that describe the same freezing
behavior that I was seeing:
https://github.com/gnome-pomodoro/gnome-pomodoro/issues?q=is%3Aissue+freeze
People there report that reloading the GNOME session (e.g. by logging
out and back in) works. Or that the Pomodoro GNOME extension has to be
explicitly enabled. I don't think I reloaded my GNOME session in the
meantime, but I could have.
> Do you have other extensions enabled?
> Is there something else special on your system?
obscure GNOME tweaks or options enabled that I know of.
> Does journalctl --user give any hints?
aug 22 11:37:56 silicon dbus-daemon[1762]: [session uid=1000 pid=1762]
Activating service name='org.gnome.Pomodoro' requested by ':1.33'
(uid=1000 pid=1901 comm="/usr/bin/gnome-shell ")
aug 22 11:37:56 silicon dbus-daemon[1762]: [session uid=1000 pid=1762]
Successfully activated service 'org.gnome.Pomodoro'
aug 22 11:37:57 silicon gnome-shell[1901]: Couldn't find child
[0x5564b642ed70 Gjs_ui_windowPreview_WindowPreview:last-child
("Pomodoro")] in window slots
aug 22 11:37:57 silicon gnome-shell[1901]: Couldn't find child
[0x5564b642ed70 Gjs_ui_windowPreview_WindowPreview:first-child
("Pomodoro")] in window slots
> Do you have other packages not originating from Debian/bullseye
> installed?
> Are you on Wayland or X11?
I'll try reproducing the issue in a clean Bullseye VM later today.
Imre Jonk
Aug 22, 2022, 11:50:04 AM8/22/22
to
severity -1 normal
thanks
On Mon, 2022-08-22 at 16:27 +0200, Imre Jonk wrote:
> People there report that reloading the GNOME session (e.g. by logging
> out and back in) works. Or that the Pomodoro GNOME extension has to
> be explicitly enabled. I don't think I reloaded my GNOME session in
> the meantime, but I could have.
Yeah this is it. I just installed a clean Bullseye VM with GNOME on
Wayland. The application freezes when opening right after installation,
but doesn't if you log out and back in before opening it. You can also
open it first, let it freeze, then force-quit the application and log
out and back in again.
I think this hints to the underlying problem:
https://github.com/gnome-pomodoro/gnome-pomodoro/issues/522#issuecomment-735459614
Right after installation, I cannot find the Pomodoro extension in GNOME
Tweaks. When I log out and back in again, the Pomodoro extension is
listed, but disabled. When I start the Pomodoro application, the
extension gets enabled.
Hope this helps!
thanks
On Mon, 2022-08-22 at 16:27 +0200, Imre Jonk wrote:
> People there report that reloading the GNOME session (e.g. by logging
> out and back in) works. Or that the Pomodoro GNOME extension has to
> be explicitly enabled. I don't think I reloaded my GNOME session in
> the meantime, but I could have.
Wayland. The application freezes when opening right after installation,
but doesn't if you log out and back in before opening it. You can also
open it first, let it freeze, then force-quit the application and log
out and back in again.
I think this hints to the underlying problem:
https://github.com/gnome-pomodoro/gnome-pomodoro/issues/522#issuecomment-735459614
Right after installation, I cannot find the Pomodoro extension in GNOME
Tweaks. When I log out and back in again, the Pomodoro extension is
listed, but disabled. When I start the Pomodoro application, the
extension gets enabled.
Hope this helps!
0 new messages