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:
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
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 Ubuntu
Touch seeded packages, which is subscribed to gcr in Ubuntu.
https://bugs.launchpad.net/bugs/1292183
Title:
Gmail password dialog box does not
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
On production machine which most probably using php5-fpm + event or worker
Apache2 MPM, this bug forcefully reinstall libapache2-mod-php5 after
(unattended = minor) PHP5 update.
The direct effect of this is reinstalling mpm_prefork !
Simply stated: unattended-upgrades breaks LAMP installation
I do have a radeon_bl0 symlink inside /sys/class/backlight/ pointing to a valid
path: /sys/devices/pci:00/:00:01.0/drm/card0/card0-eDP-1/radeon_bl0
I do not use systemd.
Handling of radeon_bl0 is probably an the issue for *another* subsystem,
most probably Xorg, udev or ACPI (= the same
** Changed in: systemd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1450044
Title:
On laptop on card AMD, screen brightness
This bug do exist
- with radeon driver(s) [radeonsi in my case]
- on some AMD hardware (Kaveri [Radeon R5 Graphics])
- is well known and explained:
* https://bbs.archlinux.org/viewtopic.php?id=193130
*
side note: I don't think this bug has anything to do with systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1450044
Title:
On laptop on card AMD, screen brightness
12 matches
Mail list logo
