Same behavior with an Entroware laptop on 5.15.0-52-generic (both
touchpad and internal keyboard, function keys work)
Hard to tell who's the culprit among the kernel, libusb, udev and gdm
One weird thing in the context of resuming : The Xorg.log generated by
gdm shows:
(II) UnloadModule:
Dears,
GTK 4.6.7 was released three weeks ago
(https://gitlab.gnome.org/GNOME/gtk/-/tags/4.6.7)
Could we hope for a package update release anytime soon?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
Forgot:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734908
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748729
** Bug watch added: Debian Bug tracker #734908
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734908
** Bug watch added: Debian Bug tracker #748729
Retrospective:
-
https://askubuntu.com/questions/867/how-can-i-stop-being-prompted-to-unlock-the-default-keyring-on-boot
(Viewed 439k times, 309 votes)
-
https://askubuntu.com/questions/495957/how-to-disable-the-unlock-your-keyring-popup
(Viewed 403k times, 138 votes)
-
Several problems about bug triage itself:
- Since 2012, no corresponding bug has been opened upstream
(https://gitlab.gnome.org/GNOME/gcr/-/issues) : ping pkg-gnome-maintainers?
- upstream isn't subscribed to this bug either (@NielsDG?)
- The code about the gcr-prompter itself does not seem to
Duplicate of https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549
?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/415320
Title:
unlock keyring "steals" focus (no cursor
This 8-years problem still exists on 20.04 (!)
As commented in #4 back in 2012, the particular focus-mode triggers crazy
situations.
Ex: autologin + autostart app's and/or auto-move windows (dedicated desktop per
window)
After GDM (auto)login, the "gcr-prompter" can not be focused or even
Duplicate of https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549
?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gcr in Ubuntu.
https://bugs.launchpad.net/bugs/1292183
Title:
Gmail password dialog box does not work and also
I can confirm the exact same behavior.
Google docs "Voice typing" constantly opens and closes the access to the
microphone while other websites (like `https://www.onlinemictest.com/`)
work normally.
When looking at the sound settings while activating voice typing, I can see
that the entry which
I'm seeing the same message `st_widget_get_theme_node called on the
widget [0x559c32c8cc50 StWidget] which is not in the stage.` even
updating individual gnome-shell / *gjs packages to eoan (gnome-shell
3.32.1) although it does not seem to actually crash gnome-shell but
rather "reload" it (It
Intel on Entroware laptop for me so hardly a driver problem (but maybe not even
the same bug)
efficient diagnosis procedure welcomed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
E555, same chip, same problem.
This guy too:
https://askubuntu.com/questions/585709/headphones-not-recognized/674501
This one too, but got it fixed using the right "model":
http://www.linuxquestions.org/questions/slackware-14/slackware64-on-lenovo-g50-70-no-sound-4175514003/
and here too (but
12 matches
Mail list logo
