[Desktop-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.
# cat ~/.gnupg/scdaemon.conf
card-timeout 5
disable-ccid
To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.
** Bug watch added:
gitlab.archlinux.org/archlinux/packaging/packages/gnupg/-/issues #4
https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg/-/issues/4
** Also affects: archlinux-lp via
https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg/-/issues/4
Importance: Unknown
Status: Unknown
** Changed in: pcsc-lite (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
Yubikey stopped working after noble upgrade
Status in Arch Linux on Launchpad:
Unknown
Status in gnupg2 package in Ubuntu:
New
Status in pcsc-lite package in Ubuntu:
Invalid
Bug description:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it works:
$ sudo gpg --card-status
Reader ...: 1050:0407:X:0
Application ID ...: D27600012401000609082616
Application type .: OpenPGP
Version ..: 2.1
Manufacturer .: Yubico
Serial number :
Name of cardholder: [not set]
Language prefs ...: [not set]
Salutation ...:
URL of public key : [not set]
Login data ...: [not set]
Signature PIN : not forced
Key attributes ...: rsa4096 rsa4096 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 10 0 10
Signature counter : 1172
UIF setting ..: Sign=off Decrypt=off Auth=off
Signature key :
created :
Encryption key:
created :
Authentication key: [none]
General key info..: [none]
If I manually run pcscd.service then it stops working both as root and
a user.
$ sudo pkill -9 scdaemon
$ sudo systemctl start pcscd.service
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
$ sudo gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
It might be worth mentioning I'm accessing the machine over SSH, so I
also did experiment with a polkit rule like this:
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_card" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
polkit.service in case this was a polkit issue, but this didn't do
anything.
Versions in noble:
pcscd: 2.0.3-1build1
libpcslite1: 2.0.3-1build1
gnupg: 2.4.4-2ubuntu17
scdaemon: 2.4.4-2ubuntu17
To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:
https://dev.gnupg.org/T6871
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
Yubikey stopped working after noble upgrade
Status in Arch Linux on Launchpad:
Unknown
Status in gnupg2 package in Ubuntu:
New
Status in pcsc-lite package in Ubuntu:
Invalid
Bug description:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it works:
$ sudo gpg --card-status
Reader ...: 1050:0407:X:0
Application ID ...: D27600012401000609082616
Application type .: OpenPGP
Version ..: 2.1
Manufacturer .: Yubico
Serial number :
Name of cardholder: [not set]
Language prefs ...: [not set]
Salutation ...:
URL of public key : [not set]
Login data ...: [not set]
Signature PIN : not forced
Key attributes ...: rsa4096 rsa4096 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 10 0 10
Signature counter : 1172
UIF setting ..: Sign=off Decrypt=off Auth=off
Signature key :
created :
Encryption key:
created :
Authentication key: [none]
General key info..: [none]
If I manually run pcscd.service then it stops working both as root and
a user.
$ sudo pkill -9 scdaemon
$ sudo systemctl start pcscd.service
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
$ sudo gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
It might be worth mentioning I'm accessing the machine over SSH, so I
also did experiment with a polkit rule like this:
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_card" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
polkit.service in case this was a polkit issue, but this didn't do
anything.
Versions in noble:
pcscd: 2.0.3-1build1
libpcslite1: 2.0.3-1build1
gnupg: 2.4.4-2ubuntu17
scdaemon: 2.4.4-2ubuntu17
To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061708] [NEW] Yubikey stopped working after noble upgrade
Public bug reported:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it works:
$ sudo gpg --card-status
Reader ...: 1050:0407:X:0
Application ID ...: D27600012401000609082616
Application type .: OpenPGP
Version ..: 2.1
Manufacturer .: Yubico
Serial number :
Name of cardholder: [not set]
Language prefs ...: [not set]
Salutation ...:
URL of public key : [not set]
Login data ...: [not set]
Signature PIN : not forced
Key attributes ...: rsa4096 rsa4096 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 10 0 10
Signature counter : 1172
UIF setting ..: Sign=off Decrypt=off Auth=off
Signature key :
created :
Encryption key:
created :
Authentication key: [none]
General key info..: [none]
If I manually run pcscd.service then it stops working both as root and a
user.
$ sudo pkill -9 scdaemon
$ sudo systemctl start pcscd.service
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
$ sudo gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
It might be worth mentioning I'm accessing the machine over SSH, so I
also did experiment with a polkit rule like this:
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_card" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
polkit.service in case this was a polkit issue, but this didn't do
anything.
Versions in noble:
pcscd: 2.0.3-1build1
libpcslite1: 2.0.3-1build1
gnupg: 2.4.4-2ubuntu17
scdaemon: 2.4.4-2ubuntu17
** Affects: archlinux-lp
Importance: Unknown
Status: Unknown
** Affects: gnupg2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: pcsc-lite (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnupg (Ubuntu)
Importance: Undecided
Status: New
** Package changed: gnupg (Ubuntu) => gnupg2 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
Yubikey stopped working after noble upgrade
Status in Arch Linux on Launchpad:
Unknown
Status in gnupg2 package in Ubuntu:
New
Status in pcsc-lite package in Ubuntu:
New
Bug description:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it works:
$ sudo gpg --card-status
Reader ...: 1050:0407:X:0
Application ID ...: D27600012401000609082616
Application type .: OpenPGP
Version ..: 2.1
Manufacturer .: Yubico
Serial number :
Name of cardholder: [not set]
Language prefs ...: [not set]
Salutation ...:
URL of public key : [not set]
Login data ...: [not set]
Signature PIN : not forced
Key attributes ...: rsa4096 rsa4096 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 10 0 10
Signature counter : 1172
UIF setting ..: Sign=off Decrypt=off Auth=off
Signature key :
created :
Encryption key:
created :
Authentication key: [none]
General key info..: [none]
If I manually run pcscd.service then it stops working both as root and
a user.
$ sudo pkill -9 scdaemon
$ sudo systemctl start pcscd.service
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
$ sudo gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
It might be worth mentioning I'm accessing the machine over SSH, so I
also did experiment with a polkit rule like this:
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_card" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
polkit.service in case this was a polkit issue, but this didn't do
anything.
Versions
[Desktop-packages] [Bug 2008958] Re: please backport 0.21 to jammy
I've updated the description to the SRU template. I do feel that this meets the "other safe cases" section. ** Description changed: + [ Impact ] + + power-profiles-daemon has the ability to make drastic improvements to + the power consumption of machines. This increases the likelihood of + them passing energy certifications such as Energy Star. + + On AMD laptops the following improvements are made: + * Tune the platform cTDP using the ACPI platform profile drivers. + * Tune the CPU using the amd-pstate EPP driver (kernel 6.5 or newer) + * Tune the backlight using AMD ABM (kernel 6.8 or newer) + * Tune the EPP dynamically based on AC vs battery + On Intel laptops the following improvements are made: + * Tune the CPU using the intel-pstate EPP/EPB driver + * Tune the EPP dynamically based on AC vs battery + + As Ubuntu 22.04 has kernel 6.5 and will later get kernel 6.8, many of + the improvements specifically for AMD laptops can apply. + + [ Test Plan ] + + Check for visual "performance issues" on battery using a web browser. + Verify correct EPP targets are selected (balance_power on battery balance_performance on AC). + Verify that changing to power-saver and performance profiles work properly. + The below significant bugfixes are implemented, which would enable more power & energy efficient modes on our supported laptops, as well as enable for the kernel default to change. + + [ Where problems could occur ] + + There is a very thorough integration test suite distributed with power- + profiles-daemon. This covers combinations of kernels and hardware that + are seen in Ubuntu. + + It is reported upstream that some Intel systems don't handle + balance_power effectively and can cause skipped frames. This should be + looked for explicitly when testing. + + It is possible that some users would prefer the increased performance + instead of efficiency that will be available on a laptop in battery + mode. They will need to manually change to performance mode to get that + performance. + + [ Other info ] + + Frame.work has been suggesting to their AMD laptop users to use a + backported release on this PPA + https://launchpad.net/~superm1/+archive/ubuntu/ppd since Framework 13 + AMD and Framework 16 AMD launched. There have been no reports of bugs + on the release on this PPA. + + Full upstream changelog is below. 0.21 Since this release power-profiles-daemon is battery-state aware and some drivers use a more power efficient state when using the balanced profile on battery. In particular both the AMD and Intel P-State drivers will use the balance_power EPP profile, while for Intel one we also set the energy performance bias to 8 (instead of 6). This release also contains various fixes for the powerprofilesctl command line tool when using the launch or version commands. The tool is now better documented as we generate a manual page for it (if python3-argparse is installed) and bash completions. We're even generating the ZSH completions, but the install path must be provided. The daemon command line interface has been improved for debugging, so use --help-debug for further information. The systemd service lockdown settings have been restricted even more. Various code optimizations. - 0.20 This release adds support for multiple power-profiles-daemon drivers to load simultaneously. This notably allows both CPU based control with amd-pstate or intel-pstate as well as ACPI platform profile based control. This release also adds support for the amdgpu panel power savings which uses dedicated hardware in systems with integrated Radeon graphics to decrease panel power consumption when the system is on battery. 0.13 This release adds support for the AMD P-State driver that's been added to the 6.3 Linux kernel. This release also fixes mismatched profiles on some HP laptops and some miscellaneous bug fixes. 0.12 This release adds support for the Intel "Energy Performance Bias" feature, which can be used on hardware that doesn't have a platform_profile or doesn't support HWP. It will also be used to eke out a bit more performance, or power, on systems which already supported HWP. More information is available in the README. 0.11.1 -- This release stops power-profiles-daemon from modifying the cpufreq driver when driver when the user/administrator has chosen to disable the Intel P-State scaling governor (eg. forcing a passive operation mode). More information is available in the README. 0.11 This release fixes problems on Intel machines when the CPUs didn't support turbo at all, or the performance scaling governor was built as default in the kernel. It also adds better end-user documentation, fixes in the command-line tool to not cause bug report tools to popup on not-uncommon errors, and a bug fix for running
[Desktop-packages] [Bug 1942616] Re: Settings Power says high hardware temperature
That's great to hear! I'll close this issue then since we have the newer version in Noble and a wishlist bug to backport it to Jammy: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958 If anyone else encounters this again, please ensure you're on 0.21 and if you are please capture these at the time of the failure: /sys/devices/system/cpu/intel_pstate/no_turbo /sys/devices/system/cpu/intel_pstate/turbo_pct ** Changed in: power-profiles-daemon (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1942616 Title: Settings Power says high hardware temperature Status in power-profiles-daemon package in Ubuntu: Fix Released Status in power-profiles-daemon package in Debian: New Bug description: Settings Power says 'high hardware temperature: performance mode unavailable' while temperature is normal. corrado@corrado-x5-ii-0901:~$ sensors coretemp-isa- Adapter: ISA adapter Package id 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 0:+35.0°C (high = +80.0°C, crit = +100.0°C) Core 1:+34.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0200 Adapter: PCI adapter Composite:+31.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) pch_skylake-virtual-0 Adapter: Virtual device temp1:+49.5°C See also attached screenshot ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 16:36:11 2021 InstallationDate: Installed on 2021-09-01 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210901) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942616] Re: Settings Power says high hardware temperature
Anyone still affected by this, can I please ask you to check the 0.21 release? It's been uploaded to Noble. I've also got it backported on a PPA that can be used on Jammy or Mantic: https://launchpad.net/~superm1/+archive/ubuntu/ppd After upgrading if you're seeing this message still, can you please gather the value of "/sys/devices/system/cpu/intel_pstate/no_turbo" at the same time as the problem? If that is set then this isn't the "fault" of power-profiles-daemon but rather the hardware, kernel, or other software. However the "reason" string emitted by power-profiles-daemon might need some improvements. ** Changed in: power-profiles-daemon (Ubuntu) Status: Confirmed => Incomplete ** Bug watch added: Debian Bug tracker #1063757 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063757 ** Also affects: power-profiles-daemon (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063757 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1942616 Title: Settings Power says high hardware temperature Status in power-profiles-daemon package in Ubuntu: Incomplete Status in power-profiles-daemon package in Debian: Unknown Bug description: Settings Power says 'high hardware temperature: performance mode unavailable' while temperature is normal. corrado@corrado-x5-ii-0901:~$ sensors coretemp-isa- Adapter: ISA adapter Package id 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 0:+35.0°C (high = +80.0°C, crit = +100.0°C) Core 1:+34.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0200 Adapter: PCI adapter Composite:+31.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) pch_skylake-virtual-0 Adapter: Virtual device temp1:+49.5°C See also attached screenshot ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 16:36:11 2021 InstallationDate: Installed on 2021-09-01 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210901) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058604] [NEW] Framework 16 disable touchpad when typing doesn't work
Public bug reported: Due to the "input deck" the Framework 16 has a "USB" internal keyboard. This throws off heuristics for detection of keyboards to turn off when you select disable touchpad when typing. This is fixed in upstream libinput with the following change: https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0 As that's not yet part of a release yet and it's a trivial change, could it be cherry picked for Ubuntu to give a better experience to Framework 16 users? ** Affects: libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2058604 Title: Framework 16 disable touchpad when typing doesn't work Status in libinput package in Ubuntu: New Bug description: Due to the "input deck" the Framework 16 has a "USB" internal keyboard. This throws off heuristics for detection of keyboards to turn off when you select disable touchpad when typing. This is fixed in upstream libinput with the following change: https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0 As that's not yet part of a release yet and it's a trivial change, could it be cherry picked for Ubuntu to give a better experience to Framework 16 users? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2058604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977660] Re: Power settings have no effect and offer nonexisting options
This should be fixed in Noble in power-profiles-daemon 0.20. ** Changed in: power-profiles-daemon (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1977660 Title: Power settings have no effect and offer nonexisting options Status in power-profiles-daemon package in Ubuntu: Fix Released Bug description: The "power" area of the settings offer three options: powersave, balanced, and performance. As per cpufreq-info "balanced" is not a valid option. Also changing to any of the two really existing options does not change cpu frequency in a visible way. Maybe there is a connection between this and the bug i reported about the matching indicator: https://bugs.launchpad.net/ubuntu/+source/indicator- cpufreq/+bug/1977659 I *can* actually switch between the values using the studio-controls application. changing values there leads to visible changes in cpufreq-info output and /proc/cpuinfo data shown. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35 Uname: Linux 5.15.0-35-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 20:36:14 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-12 (782 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-28 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1977660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
It's marked failed to upload on all architectures right now: INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 I guess that means an epoch is needed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 Status in glib2.0 package in Ubuntu: Fix Committed Bug description: glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate out of noble-proposed before or at the same as glib2.0. I'm filing this bug to explain why glib2.0 isn't migrating despite the excuses page saying "Will attempt migration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046853] Re: Power Profiles daemon should change multiple drivers
https://launchpad.net/ubuntu/+source/power-profiles-daemon/0.20-1 ** Changed in: power-profiles-daemon (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2046853 Title: Power Profiles daemon should change multiple drivers Status in power-profiles-daemon package in Ubuntu: Fix Released Bug description: The current version of power-profiles-daemon (0.13) has support both for amd/intel pstate drivers as well as the ACPI platform profile drivers. If the system supports both types of drivers then only the ACPI platform profile driver gets used. This doesn't do a great job as a result on x86 systems that could really benefit from changing the pstate drivers too. Ideally power-profiles-daemon should change both drivers at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2046853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046992] Re: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch)
Do you have something in /usr/local perhaps? Or did you have a snap installed for fwupd? ** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu) ** Changed in: fwupd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2046992 Title: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch) Status in fwupd package in Ubuntu: Incomplete Bug description: On Ubuntu 22.04.03, the fwupd package fails to perform a clean apt install. The error given upon service startup is the following: Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 fwupd[9985]: Failed to load engine: libfwupd version 1.9.4 does not match daemon 1.7.9 More info below: System version: root@jwlandon-ThinkPad-E14-Gen-2:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy No fwupd related packages installed: root@jwlandon-ThinkPad-E14-Gen-2:~# apt list --installed 2> /dev/null |grep fwupd Now I install fwupd: root@jwlandon-ThinkPad-E14-Gen-2:~# apt install fwupd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: fwupd-signed libfwupd2 libfwupdplugin5 Suggested packages: gir1.2-fwupd-2.0 The following NEW packages will be installed: fwupd fwupd-signed libfwupd2 libfwupdplugin5 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/2,889 kB of archives. After this operation, 7,989 kB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package libfwupd2:amd64. (Reading database ... 329400 files and directories currently installed.) Preparing to unpack .../libfwupd2_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupd2:amd64 (1.7.9-1~22.04.3) ... Selecting previously unselected package libfwupdplugin5:amd64. Preparing to unpack .../libfwupdplugin5_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupdplugin5:amd64 (1.7.9-1~22.04.3) ... Selecting previously unselected package fwupd. Preparing to unpack .../fwupd_1.7.9-1~22.04.3_amd64.deb ... Unpacking fwupd (1.7.9-1~22.04.3) ... Selecting previously unselected package fwupd-signed. Preparing to unpack .../fwupd-signed_1.51.1~22.04.1+1.4-0ubuntu0.1_amd64.deb ... Unpacking fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up libfwupd2:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up libfwupdplugin5:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd (1.7.9-1~22.04.3) ... fwupd-offline-update.service is a disabled or a static unit, not starting it. fwupd-refresh.service is a disabled or a static unit, not starting it. fwupd-refresh.timer is a disabled or a static unit, not starting it. fwupd.service is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.35-0ubuntu3.5) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... fwupd packages are now installed: root@jwlandon-ThinkPad-E14-Gen-2:~# apt list --installed 2> /dev/null |grep fwupd fwupd-signed/jammy-updates,now 1.51.1~22.04.1+1.4-0ubuntu0.1 amd64 [installed,automatic] fwupd/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed] libfwupd2/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed,automatic] libfwupdplugin5/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed,automatic] Service is unable to start: root@jwlandon-ThinkPad-E14-Gen-2:~# systemctl start fwupd Job for fwupd.service failed because the control process exited with error code. See "systemctl status fwupd.service" and "journalctl -xeu fwupd.service" for details. Service complains about a library to daemon sw version mismatch: root@jwlandon-ThinkPad-E14-Gen-2:~# systemctl status fwupd × fwupd.service - Firmware update daemon Loaded: loaded (/lib/systemd/system/fwupd.service; static) Active: failed (Result: exit-code) since Tue 2023-12-19 21:36:46 PST; 20s ago Docs: https://fwupd.org/ Process: 9985 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) Main PID: 9985 (code=exited, status=1/FAILURE) CPU: 59ms Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: Starting Firmware update daemon... Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 fwupd[9985]: Failed to load engine: libfwupd version 1.9.4 does not match daemon 1.7.9 Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: fwupd.service: Failed with result
[Desktop-packages] [Bug 2046853] [NEW] Power Profiles daemon should change multiple drivers
Public bug reported: The current version of power-profiles-daemon (0.13) has support both for amd/intel pstate drivers as well as the ACPI platform profile drivers. If the system supports both types of drivers then only the ACPI platform profile driver gets used. This doesn't do a great job as a result on x86 systems that could really benefit from changing the pstate drivers too. Ideally power-profiles-daemon should change both drivers at the same time. ** Affects: power-profiles-daemon (Ubuntu) Importance: Wishlist Status: Triaged ** Bug watch added: gitlab.freedesktop.org/upower/power-profiles-daemon/-/issues #107 https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/issues/107 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2046853 Title: Power Profiles daemon should change multiple drivers Status in power-profiles-daemon package in Ubuntu: Triaged Bug description: The current version of power-profiles-daemon (0.13) has support both for amd/intel pstate drivers as well as the ACPI platform profile drivers. If the system supports both types of drivers then only the ACPI platform profile driver gets used. This doesn't do a great job as a result on x86 systems that could really benefit from changing the pstate drivers too. Ideally power-profiles-daemon should change both drivers at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2046853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028674] Re: Automatically switch profiles based on plugged-in status
Something I want to mention is that some drivers in the kernel and some implementations of vendor's EC firmware internally handle AC vs battery differently within a given platform profile. So you "automatically" get a better power savings just going to battery compared to AC. Thus I don't think this is a high priority item. In any case if you feel it's important you should raise it upstream. It's not a behavior that would be changed specifically in Ubuntu's package. ** Changed in: power-profiles-daemon (Ubuntu) Importance: Undecided => Wishlist ** Changed in: power-profiles-daemon (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2028674 Title: Automatically switch profiles based on plugged-in status Status in power-profiles-daemon package in Ubuntu: Opinion Bug description: As of now there is no option to switch power profiles automatically, based on the status (plugged-in or not) of the device. It would be a very useful feature, and would work around the requirement to create user scripts and download gnome-extensions. E.g: https://extensions.gnome.org/extension/5575/power-profile-switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2028674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034678] Re: Power profile constantly resets to Balanced
This is a firmware or kernel bug, not a power profiles daemon bug. Please report it to Lenovo to investigate the details. ** Changed in: power-profiles-daemon (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2034678 Title: Power profile constantly resets to Balanced Status in power-profiles-daemon package in Ubuntu: Invalid Bug description: Setting power profile from GNOME into power saver automatically sets it to balanced after a while. Let battery drain down to critical and have automatic power saver on. Power saver profile is on for a while. Expected: Power profile stays on power saver. Actual: In about 15 minutes the power profile is seemingly set to balanced when opening the power management window, although there is a text saying that the power profile is set to saver due to the aforementioned configuration. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 powerprofilesctl --version 0.12 neofetch .-/+oooo+/-. `:+ss+:` -- -+ssyy+- OS: Ubuntu 23.04 x86_64 .ossdMMMNyo. Host: 20N3S2NJ00 ThinkPad T490 /ssshdmmNNmmyNhss/ Kernel: 6.2.0-32-generic +shmydMMMNy+ Uptime: 2 hours, 46 mins /hNMMMyhhhmNMMMNh/Packages: 2058 (dpkg), 9 (flatpak) .dMMMNhsshNMMMd. Shell: bash 5.2.15 +hhhyNMMNyyNMMMysss+ Resolution: 1920x1080 ossyNMMMNyMMhsshmmmhssso DE: GNOME 44.3 ossyNMMMNyMMhsshmmmhssso WM: Mutter +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Yaru [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel i5-8265U (8) @ 3.900GHz .ossdMMMNyo. GPU: Intel WhiskeyLake-U GT2 [UHD Gr -+syyy+- Memory: 7718MiB / 15640MiB `:+ss+:` .-/+oooo+/-. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2034678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043318] Re: Screen keeps dimming, power mode switches to 'power saver' by itself
Closing it here as this is a firmware bug not a software bug. ** Changed in: power-profiles-daemon (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2043318 Title: Screen keeps dimming, power mode switches to 'power saver' by itself Status in power-profiles-daemon package in Ubuntu: Invalid Bug description: Fresh installed Lenovo Thinkpad L13 Gen2 Ubuntu 23, kernel 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Firmware updates done In Settings -> Power, screen dimming is turned off but the screen keeps dimming. This is probably caused by the Power Mode being in 'Power Saver'. After switching to 'Balanced' or 'Performance', the Power Mode switches back to 'Power Saver' by itself, typically in 10 seconds to about a minute. This slows down the computer and constantly dims the screen if the keyboard or mouse is not being operated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2043318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046491] [NEW] Finger Print Sensor is not working on goodixmoc device
Public bug reported: AMD testing of some Goodix MOC devices shows that this device fails to work properly: [ 208.586084] usb 1-2: New USB device found, idVendor=27c6, idProduct=6496, bcdDevice= 1.00 The issue is specifically that there is a problem with the 'enroll create' state. It has been fixed by the following commit that is part of fprintd 1.94.6: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/86566e8d0b7b36ebaa5588af75b46e2c93a12918 Please consider bringing either that commit or the whole 1.94.6 version into Ubuntu (1.94.6 also adds compatibilities with a bunch of other devices). ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/2046491 Title: Finger Print Sensor is not working on goodixmoc device Status in fprintd package in Ubuntu: New Bug description: AMD testing of some Goodix MOC devices shows that this device fails to work properly: [ 208.586084] usb 1-2: New USB device found, idVendor=27c6, idProduct=6496, bcdDevice= 1.00 The issue is specifically that there is a problem with the 'enroll create' state. It has been fixed by the following commit that is part of fprintd 1.94.6: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/86566e8d0b7b36ebaa5588af75b46e2c93a12918 Please consider bringing either that commit or the whole 1.94.6 version into Ubuntu (1.94.6 also adds compatibilities with a bunch of other devices). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/2046491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f6
** Changed in: linux (Ubuntu)
Status: Won't Fix => Confirmed
** Changed in: linux (Ubuntu Jammy)
Status: Won't Fix => Confirmed
** Changed in: linux (Ubuntu Lunar)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Confirmed
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043264] Re: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE)
Can you please try to reproduce using a mainline upstream build? https://kernel.ubuntu.com/mainline/v6.7-rc2/ If you can reproduce please share a new kernel log from a boot it occurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2043264 Title: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: --- en Always, almost every time I turn on my notebook, my LG external monitor keeps blinking and it takes a while to actually connect to the notebook and the external monitor screen to turn on. For the external monitor to work I change the video settings using Ctrl + P and turn the monitor off/on several times. In Kubuntu it is recognized but when it blinks the system thinks the monitor is off. I'm using Kubuntu 23.04, I've used other distributions on the same hardware and this problem hasn't happened. I believe it's something with KDE. --- pt-br Sempre, quase toda vez que ligo meu notebook, meu monitor externo LG fica piscando e demora para realmente conectar ao notebook e a tela do monitor externo ligar. Para o monitor externo funcionar eu mudo as configurações de vídeo usando Ctrl + P e desligo/ligo o monitor várias vezes. No Kubuntu ele é reconhecido mas quando fica piscando o sistema acha que o monitor está desligado. Estou usando o Kubuntu 23.04, já usei outras distribuições no mesmo hardware e esse problema não aconteceu. Eu acredito que seja algo com o KDE. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 11 07:52:24 2023 DistUpgraded: 2023-11-02 07:28:00,578 DEBUG /openCache(), new cache size 78921 DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3804] InstallationDate: Installed on 2022-10-23 (383 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 81V7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=d72b8a6b-953f-4b38-8b0a-d1e9b6899ad2 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-11-02 (9 days ago) dmi.bios.date: 05/19/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: BUCN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15API dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrBUCN25WW:bd05/19/2020:br1.25:efr1.25:svnLENOVO:pn81V7:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81V7_BU_idea_FM_IdeaPadS145-15API: dmi.product.family: IdeaPad S145-15API dmi.product.name: 81V7 dmi.product.sku: LENOVO_MT_81V7_BU_idea_FM_IdeaPad S145-15API dmi.product.version: Lenovo IdeaPad S145-15API dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt upgrade
# sudo reboot
If they don't, you can remove the PPA using ppa-purge like this:
# sudo ppa-purge ppa:superm1/gitlab2971
# sudo reboot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Unknown
Status in linux package in Ubuntu:
Won't Fix
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Won't Fix
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Lunar)
Status: New => Won't Fix
** Also affects: mesa via
https://gitlab.freedesktop.org/drm/amd/-/issues/2971
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Unknown
Status in linux package in Ubuntu:
Won't Fix
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Won't Fix
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This should be a different issue than the mutter issue; please open it up separately for investigation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
From the upstream bug this is caused by PSR, so it's not a mesa issue. ** No longer affects: mesa (Ubuntu) ** No longer affects: mesa (Ubuntu Jammy) ** No longer affects: mesa (Ubuntu Lunar) ** No longer affects: mesa (Ubuntu Mantic) ** No longer affects: mesa (Ubuntu Noble) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2042054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
It's unclear if this is a BIOS, mesa or kernel bug at this time, but it's certainly not an Xorg bug as it was reproduced in Wayland. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954 https://gitlab.freedesktop.org/drm/amd/-/issues/2954 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2954 Importance: Unknown Status: Unknown ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: Unknown Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in mesa source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.5 source package in Lunar: Invalid Status in mesa source package in Lunar: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in mesa source package in Mantic: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in mesa source package in Noble: New Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM
[Desktop-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
** Package changed: xorg (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in mesa package in Ubuntu: New Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2042054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Please also take this fix at the same time for this same laptop. It will fix s2idle for it. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/commit/?h=fixes=3bde7ec13c971445faade32172cb0b4370b841d9 ** Changed in: libinput (Ubuntu) Status: Confirmed => Invalid ** Package changed: linux-signed-hwe-6.2 (Ubuntu) => linux (Ubuntu) ** No longer affects: linux-signed-oem-6.5 (Ubuntu) ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: libinput (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** No longer affects: libinput (Ubuntu) ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** No longer affects: linux-oem-6.1 (Ubuntu Lunar) ** No longer affects: linux-oem-6.1 (Ubuntu Mantic) ** No longer affects: linux-oem-6.1 (Ubuntu Noble) ** No longer affects: linux-oem-6.5 (Ubuntu Lunar) ** No longer affects: libinput (Ubuntu Jammy) ** No longer affects: libinput (Ubuntu Lunar) ** No longer affects: libinput (Ubuntu Mantic) ** No longer affects: libinput (Ubuntu Noble) ** No longer affects: linux-hwe-6.2 (Ubuntu Lunar) ** No longer affects: linux-hwe-6.2 (Ubuntu Mantic) ** No longer affects: linux-hwe-6.2 (Ubuntu Noble) ** No longer affects: linux-oem-6.5 (Ubuntu Mantic) ** No longer affects: linux-oem-6.5 (Ubuntu Noble) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-hwe-6.2 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command
[Desktop-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Here is the upstream patch for this issue: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=218003 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
#75 You can turn on proposed and then use ppa-purge command to remove my PPA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Sure. It wasn't opened yet when I uploaded to mantic a few days ago. Since it's open now I've: 1. uploaded a *ubuntu4 version to noble (after a local test build with noble archive worked). 2. uploaded a *ubuntu3.1 version to mantic to make sure the version string doesn't conflict since they will be different binaries. Please reject the *ubuntu4 version from the mantic-proposed queue and accept the *ubuntu3.1 version (if it looks good). ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Mario Limonciello (superm1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
The fixes are identified, I don't think this should wait until GNOME 45.1 release. This issue is totally breaking suspend on several of my test systems. I've backported the fixes from the GNOME 45 branch onto this PPA build: https://launchpad.net/~superm1/+archive/ubuntu/lp2034619/+packages I've also uploaded the mutter package into the proposed queue for SRU team to look at. ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => In Progress ** Changed in: mutter (Ubuntu Mantic) Assignee: (unassigned) => Mario Limonciello (superm1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039958] Re: gnome-shell session dies when locking laptop screen
*** This bug is a duplicate of bug 2034619 *** https://bugs.launchpad.net/bugs/2034619 ** This bug has been marked a duplicate of bug 2034619 [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039958 Title: gnome-shell session dies when locking laptop screen Status in gnome-shell package in Ubuntu: New Bug description: Started after migrating to 23.10 STR: - Boot laptop - Login - Start GNOME Terminal - Lock screen Expected: - Screen is locked, I can unlock and recover my session Actual: - Screen gets locked, does not unlock, and ends up starting a new gnome session This only reproduces in the simple case of laptop with its integrated screen being used. When I connect to my docking station, with two external monitors and the internal screen disabled, I can properly perform the locking/unlocking. journalctl does not show anything useful besides: oct. 20 11:40:13 portable-alex kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 oct. 20 11:40:18 portable-alex gnome-shell[27866]: (EE) failed to read Wayland events: Broken pipe oct. 20 11:40:18 portable-alex update-notifier[28393]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta.desktop[27371]: The Wayland connection broke. Did the Wayland compositor die? oct. 20 11:40:18 portable-alex xdg-desktop-por[26680]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex snapd-desktop-i[26606]: Error reading events from display: Broken pipe oct. 20 11:40:18 portable-alex solaar[26327]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex evolution-alarm[26356]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex xdg-desktop-por[26746]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta[27371]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-wacom[26213]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-color[26168]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-power[26183]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-keyboard[26178]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gnome-terminal-[27151]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-media-keys[26180]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit UNIT has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct. 20 11:40:18 portable-alex sudo[28424]: pam_unix(sudo:session): session closed for user root oct. 20 11:40:18 portable-alex io.github.Hexchat.desktop[27864]: hexchat: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0. oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:03:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (473 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox
6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
New
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This is the upstream fix for this issue: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I've split up the GDM for Jammy change into https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757 ** No longer affects: gdm3 (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039757] [NEW] Fix race condition in gdm with simpledrm and real drm drivers
Public bug reported: [ Impact ] When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a series of events can occur that cause simpledrm to race with GDM. When GDM loses the race then a user is left with a black screen. This series of events doesn't currently happen in Jammy kernels, but can happen from a mainline kernel or HWE kernel that enables it. To protect users from this circumstance it is better to fix the race condition. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * GDM can take longer to start up while settling [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 * the changes needed to enable this in the kernel are tracked in bug 1965303 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2039757 Title: Fix race condition in gdm with simpledrm and real drm drivers Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: New Bug description: [ Impact ] When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a series of events can occur that cause simpledrm to race with GDM. When GDM loses the race then a user is left with a black screen. This series of events doesn't currently happen in Jammy kernels, but can happen from a mainline kernel or HWE kernel that enables it. To protect users from this circumstance it is better to fix the race condition. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * GDM can take longer to start up while settling [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 * the changes needed to enable this in the kernel are tracked in bug 1965303 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The issue won't occur in Lunar. It's only specifically a problem with gdm when a kernel has been configured this way. It's not a problem in Jammy yet, but will be a problem when such a kernel gets backported as HWE. ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Lunar) Status: New => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: gdm3 (Ubuntu Lunar) Status: New => Invalid ** Changed in: gdm3 (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Ok in this case can you please open an upstream mesa bug? ** Changed in: mesa (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0
[Desktop-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed right after you reported this issue. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Incomplete Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
I'd say that's very likely. That mesa upgrade just landed in the archive a few days ago and the trace you reported looks more like how a mesa bug manifests. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu:
[Desktop-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Are you up to date on the current version of mesa in 23.10? 23.2.1-1ubuntu2? ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW:
[Desktop-packages] [Bug 2016435] Re: amdgpu driver randomly resets
Random resets are "typically" triggered by mesa or application bugs. Can you still trigger them in the latest mantic (which has a more up to date mesa and kernel)? ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2016435 Title: amdgpu driver randomly resets Status in mesa package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: amdgpu tends to randomly reset. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xserver-xorg-video-amdgpu 23.0.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sun Apr 16 18:04:34 2023 DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1849:5212] NVIDIA Corporation GA104 [GeForce RTX 3060 Ti] [10de:2486] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GA104 [GeForce RTX 3060 Ti] [3842:3663] InstallationDate: Installed on 2022-01-14 (457 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to lunar on 2023-04-01 (14 days ago) dmi.bios.date: 10/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F3c dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF3c:bd10/01/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroRelease: Ubuntu 23.04 DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard:
[Desktop-packages] [Bug 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1987792 Title: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers Status in mesa package in Ubuntu: Incomplete Bug description: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is 0x39.
[Desktop-packages] [Bug 1094959] Re: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade
> NonfreeKernelModules: fglrx Nothing that will be done in mesa for an issue with fglrx anyway these days. ** Changed in: mesa (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1094959 Title: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade Status in mesa package in Ubuntu: Won't Fix Bug description: I was trying to (re)install Steam, and I got this error. One weird thing that happened before is that Steam (and all it's files) wiped themselves out of my system for no reason... ProblemType: PackageDistroRelease: Ubuntu 12.04 Package: libgl1-mesa-dri 8.0.4-0ubuntu0.2 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17 AptOrdering: libgl1-mesa-dri: Install libgl1-mesa-dri: Configure Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Mon Dec 31 16:48:23 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.2.0-34-generic, x86_64: installed fglrx-updates, 9.000, 3.2.0-35-generic, x86_64: installed DpkgTerminalLog: Unpacking libgl1-mesa-dri:i386 (from .../libgl1-mesa-dri_8.0.4-0ubuntu0.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libgl1-mesa-dri_8.0.4-0ubuntu0.2_i386.deb (--unpack): './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system ErrorMessage: './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI Device [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:2556] InstallationMedia: This MachineType: HP-Pavilion FQ601AA-A2L m9505f MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic root=UUID=4fd95ed0-53b7-4da0-9a18-989348244233 ro quiet splashSourcePackage: mesa Title: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.43 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnFQ601AA-A2Lm9505f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: FQ601AA-A2L m9505f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1094959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
In this case the kernel is the "messenger" for the page fault. This is more likely to be a mesa or application issue than a kernel issue. Can you please raise a ticket to the upstream mesa bug tracker? https://gitlab.freedesktop.org/mesa/mesa/ ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Description changed: - The fbdev subsystem has been deprecated for a long time. We should drop - it in favour of using simpledrm with fbdev emulation layer. + [ Impact ] + The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. - This requires config changes: + This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer - fedora bug: - https://bugzilla.redhat.com/show_bug.cgi?id=2022385 + When this stack is enabled, it changes boot timing such that some + drivers may take a longer time to boot and GDM may hang in a black + screen. + + [ Test Plan ] + * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) + + [ Where Problems could occur ] + * Race conditions could be exposed to DE environments + * Software that expects to find DRM device at /dev/dri/card0 may have a problem. + * Some older versions of NVIDIA driver might not work properly. + + [ Other Info ] + * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2909 https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #2022385 https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2022385 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Unknown Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Triaged Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Unknown Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is still open. ** Changed in: gdm3 (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Triaged Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Bug description: The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036190] Re: fwupd running in WSL 2 in Ubuntu-22.04 fails to start
I think that this should be changed in gnome software not to try to start fwupd then when in WSL2. ** Package changed: fwupd (Ubuntu) => gnome-software (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2036190 Title: fwupd running in WSL 2 in Ubuntu-22.04 fails to start Status in gnome-software package in Ubuntu: New Bug description: The fwupd systemd service file contains "ConditionVirtualization=!container". This blocks fwupd from starting in WSL 2 Ubuntu-22.04 instance. Modifying the fwupd systemd service file to contain: # /etc/systemd/system/fwupd.service.d/override.conf [Unit] ConditionVirtualization= fixes this issue. WSL 2 is a light-weight utility VM, not a container. I noticed this issue when starting gnome-software. gnome-software output this error to the terminal: 09:48:20:0857 Gs plugin fwupd took 25.0 seconds to do setup 09:48:21:0461 PK failed to set proxy: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:21:0462 GsPluginPackageKit failed to set proxies: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:46:0298 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) 09:48:46:0299 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action get-updates-historical: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fwupd 1.7.9-1~22.04.3 Uname: Linux 5.10.16.3-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Xpra Date: Fri Sep 15 13:01:49 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2036190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-hwe-6.2 (Ubuntu Jammy) Status: New => Invalid ** Changed in: mesa (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-hwe-6.2 source package in Jammy: Invalid Status in mesa source package in Jammy: New Status in linux-hwe-6.2 source package in Lunar: Invalid Status in mesa source package in Lunar: New Status in linux-hwe-6.2 source package in Mantic: Invalid Status in mesa source package in Mantic: Fix Released Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu
[Desktop-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
I believe this likely needs the VCN fixes from https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Unknown Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4 i2c_hid
[Desktop-packages] [Bug 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
** Also affects: xserver-xorg-video-amdgpu (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Assignee: Kai-Chuan Hsieh (kchsieh) => (unassigned) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019116] Re: Performance mode not available
This is fixed in mantic which just upgraded to the 0.13 release, but you will also need to add amd_pstate=active to your kernel command line. ** Changed in: power-profiles-daemon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2019116 Title: Performance mode not available Status in power-profiles-daemon package in Ubuntu: Fix Released Bug description: Performance mode not available as a profile. Only Power Saver and Balanced are there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2019116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022945] [NEW] Update power profiles daemon to 0.13 release
Public bug reported: 0.13 This release adds support for the AMD P-State driver that's been added to the 6.3 Linux kernel. This release also fixes mismatched profiles on some HP laptops and some miscellaneous bug fixes. ** Affects: power-profiles-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2022945 Title: Update power profiles daemon to 0.13 release Status in power-profiles-daemon package in Ubuntu: New Bug description: 0.13 This release adds support for the AMD P-State driver that's been added to the 6.3 Linux kernel. This release also fixes mismatched profiles on some HP laptops and some miscellaneous bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2022945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics
I believe the same thing can likely happen if llvm updates but mesa stays the same. Can you embed both into the string? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: New Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: New Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in xserver-xorg-video-amdgpu source package in Xenial: Invalid Bug description: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Ctrl-Alt-F[1-6] (switch TTY/terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faulty component. The attached file "amdgpu-bug.txt" is the reason why I'm pretty convinced that the problem is being caused by the amdgpu driver (although it seems to be related to how it interacts with the kernel, thus maybe the problem is kernel-related). WORKAROUND: Boot from GRUB with the nomodeset parameter. The graphics performance becomes terribly slow. - Apport output: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0643] Subsystem: Dell Topaz XT [Radeon R7 M260/M265] [1028:0643] InstallationDate: Installed on 2016-07-29 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5548 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=24cb3fff-5c01-4674-9c59-58d7d776fd70 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Renderer: Software Tags: xenial ubuntu Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape users video _MarkForUpload: True dmi.bios.date: 10/12/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YDTG3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn0YDTG3:rvrA02:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5548 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 2017142] [NEW] [jammy] VA-API doesn't work on DCN 3.1.4
Public bug reported: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: originate-from-2016915 ** Tags added: originate-from-2016915 ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
At least from AMD's tests, backported mesa stack is working properly with RDNA3. Adjusting tag accordingly. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: Fix Committed Status in llvm-toolchain-15 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: Fix Committed Status in spirv-llvm-translator-15 source package in Jammy: Fix Committed Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.5
I tested 42.5-0ubuntu1 on a Z13 (which prompted the heuristics change) and can confirm it's working with Wayland and the non-functional resolutions are no longer offered. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985856 Title: Update Mutter to 42.5 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
> A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". It's not a function of the OS, it's a function of the underlying hardware, firmware, and firmware configuration for your given system. The "!" in the HSI string is controlled by OS behavior (such as encrypted swap, taint, etc). At least on a pre-production Lenovo Z13 I can get HSI-2, depending on whether Lenovo has SPI replay protection in the production hardware I might be able to get all the way to HSI 4. Host Security ID: HSI:2! (v1.8.4) HSI-1 ✔ Fused platform:Locked ✔ Rollback protection: Enabled ✔ Supported CPU: Valid ✔ TPM empty PCRs:Valid ✔ TPM v2.0: Found ✔ UEFI platform key: Valid HSI-2 ✔ IOMMU: Enabled ✔ Platform Debugging:Locked ✔ SPI write protection: Enabled ✔ TPM PCR0 reconstruction: Valid HSI-3 ✔ Pre-boot DMA protection: Enabled ✔ Suspend-to-idle: Enabled ✔ Suspend-to-ram:Disabled ✘ SPI replay protection: Disabled HSI-4 ✔ Encrypted RAM: Encrypted -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
FYI - 1.8.4 synced from Debian to Ubuntu kinetic now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
One possible solution is to split the fwupd package along it's possible plugins into multiple packages. However I tend to agree that it has no use in a cloud or container seed. I also agree libmm-glib0 shouldn't recommend modem manager. ** Changed in: fwupd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Changed in: linux-oem-5.17 (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Just to correct a few of the targets on this issue. * The reverts mentioned in #30 need to be pulled into linux-firmware for focal. * They're already included in jammy. ** Changed in: amd Status: New => Fix Released ** No longer affects: mesa (Ubuntu) ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-firmware (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: Won't Fix Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) > $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf > [Service] > DynamicUser=no The whole point of using DynamicUser in this case was so that fwupdmgr didn't run as root when it reached out to the web to get data. Yes, certainly turning off DynamicUser in fwupd-refresh.service will solve the problem, but that is then a different threat vector. I think if turning off DynamicUser=1, then we probably need to also create a new service account for that systemd service to use. I'll open a new bug to move this discussion to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969976 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug,
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 This appears to have caused a regression in fwupd in Ubuntu 20.04 with details at https://github.com/fwupd/fwupd/issues/3037 fwupd-refresh.service uses DynamicUser and now hits this upstream bug: https://github.com/systemd/systemd/issues/22737 ** Bug watch added: github.com/fwupd/fwupd/issues #3037 https://github.com/fwupd/fwupd/issues/3037 ** Bug watch added: github.com/systemd/systemd/issues #22737 https://github.com/systemd/systemd/issues/22737 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped
[Desktop-packages] [Bug 656478] Re: Init script for saned is spammy on default install needlessly
** Changed in: sane-backends (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/656478 Title: Init script for saned is spammy on default install needlessly Status in sane-backends package in Ubuntu: Won't Fix Bug description: The default install of Maverick installs sane-utils which provides an init script for saned. It's disabled by default, but on every boot spams the VT with echo "$NAME disabled; edit /etc/default/saned" Looking at how simple the init script and /etc/default/saned are, I would contend that this should either: 1) Be converted to an upstart script that's not enabled by default or 2) Remove the line that tells the user that saned is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/656478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962277] Re: To support Synaptics fp device
** Also affects: libfprint (Ubuntu Jammy) Importance: Medium Status: New ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device Status in OEM Priority Project: Confirmed Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: New Status in libfprint source package in Impish: New Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/4d5e2775b23a65b6b7b41eb98fa5b2c68a805f33 https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/128d809227bbef1d3bd8e7c7e1f9b68a335db252 https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3fb8860dc487568518d69e9074135041296d1e75 This ID is included in upstream. [Impact] * Devices have synaptics fingerprint component will get supported. * Supported list. [06cb:0100] [06cb:00f0] [06cb:0103] [06cb:0123] [06cb:0126] [06cb:0129] [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be more synaptics devices get supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962349] [NEW] Bolt doesn't work with native USB4 hosts
Public bug reported: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. ** Affects: bolt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: bolt (Ubuntu Focal) Importance: Undecided Status: New ** Affects: bolt (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Affects: bolt (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: bolt (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: bolt (Ubuntu Jammy) Status: New => Fix Released ** Description changed: [Impact] - * AMD Yellow Carp provides integrated USB4 host controllers - * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" + * AMD Yellow Carp provides integrated USB4 host controllers + * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] - * Plug in USB4 device or TBT3 to AMD Yellow Carp host - * Ensure that PCI topology has populated - * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" - * Try to run `boltctl enroll $UUID` + * Plug in USB4 device or TBT3 to AMD Yellow Carp host + * Ensure that PCI topology has populated + * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" + * Try to run `boltctl enroll $UUID` [Where problems could occur] - * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. - * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. + * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. + * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. [Other Info] - * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. - * It is fixed in bolt 0.9.1 or later release. - * To solve the SRU, will backport 0.9.2 release from Jammy. + * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. + * It is fixed in bolt 0.9.1 or later release. + * To solve the SRU, will backport 0.9.1 release from Impish. ** Changed in: bolt (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in bolt package in Ubuntu: Fix Released Status in bolt source package in Focal: New Status in bolt source package in Impish: Fix Released Status in bolt source package in Jammy: Fix Released Bug description: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
> If fwupd is being backported to previous releases of Ubuntu it seems like libgusb would also need to be backported. Actually the bug was introduced in libgusb 0.3.8, fixed in libgusb 0.3.9. If older releases have older than 0.3.8 they shouldn't need libgusb backport. See comment #3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
** Changed in: fwupd (Ubuntu) Status: Confirmed => Invalid ** Changed in: libusb (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Confirmed Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
Ah probably was caused by https://github.com/hughsie/libgusb/commit/4b52b0cd27fdadcb29b4518cff293c1c76b872a9 in 0.3.8 and fixed by https://github.com/hughsie/libgusb/commit/24934619a2ad3467b98142dfab2039985afc970d in that case. ** Also affects: libgusb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Confirmed Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp
Verified on YC with the following combination all from -proposed: # dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0." ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor library ii libgbm1:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64generic buffer management API -- runtime ii libgl1-mesa-dri:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- GLX vendor library ii linux-firmware 1.187.19 all Firmware for Linux kernel drivers ii linux-image-5.14.0-1005-oem5.14.0-1005.5 amd64Signed kernel image oem ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp
With manually placing firmware in /lib/firmware (since SRU not started for that) and using 5.14 kernel confirmed that mesa looks good. Since we don't have linux-firmware SRU package yet and they are combined on this bug report I will not add "verification-done-focal". # glxinfo | grep "OpenGL render" -i OpenGL renderer string: AMD YELLOW_CARP (DRM 3.42.0, 5.14.0, LLVM 12.0.0) # dpkg -l | grep 21.0.3-0ubuntu0.3 ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor library ii libgbm1:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64generic buffer management API -- runtime ii libgl1-mesa-dri:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- GLX vendor library -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute/impish (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Here's a PPA build with the mesa fix Alex mentioned backported: https://launchpad.net/~superm1/+archive/ubuntu/lp1928393 If you can follow the directions to add that PPA and upgrade to that mesa package you can see if that indeed fixes it. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865206] [NEW] package libxvmc-dev 2:1.0.12-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-d
Public bug reported: Received during focal apt dist-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxvmc-dev 2:1.0.12-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 28 12:26:12 2020 DistUpgraded: 2019-11-21 10:34:45,404 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-05 (328 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190405) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=338eb039-e741-415d-bc9a-1d7c83c55c55 ro quiet splash i915.fastboot=1 vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: libxvmc Title: package libxvmc-dev 2:1.0.12-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 UpgradeStatus: Upgraded to focal on 2019-11-21 (99 days ago) dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd12/03/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: libxvmc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal has-workaround single-occurrence ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxvmc in Ubuntu. https://bugs.launchpad.net/bugs/1865206 Title: package libxvmc-dev 2:1.0.12-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 Status in libxvmc package in Ubuntu: New Bug description: Received during focal apt dist-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxvmc-dev 2:1.0.12-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 28 12:26:12 2020 DistUpgraded: 2019-11-21 10:34:45,404 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-05 (328 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190405) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=338eb039-e741-415d-bc9a-1d7c83c55c55 ro quiet splash i915.fastboot=1 vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: libxvmc Title: package libxvmc-dev 2:1.0.12-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 UpgradeStatus: Upgraded to focal on 2019-11-21 (99 days ago) dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
I reported this upstream here: https://github.com/hughsie/lvfs- website/issues/335 It looks like it's related to the metadata being too big. ** No longer affects: appstream-glib (Ubuntu) ** Bug watch added: github.com/hughsie/lvfs-website/issues #335 https://github.com/hughsie/lvfs-website/issues/335 ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Triaged ** Changed in: fwupd (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Triaged Bug description: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic (Xenial): #apt install fwupd #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc The `fwupd` classic confined snap also works. === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
That message is coming from appstream-glib, somewhere around here: https://github.com/hughsie/appstream- glib/blob/843caabdeca6ae15f400f38536bc666340c30465/libappstream-glib/as- store.c#L2329 I would recommend to start out with trying a newer appstream-glib to see if that helps. ** Also affects: appstream-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu Status in appstream-glib package in Ubuntu: New Status in fwupd package in Ubuntu: New Bug description: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic (Xenial): #apt install fwupd #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc The `fwupd` classic confined snap also works. === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1829813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
FWIW a few other messages pop up to me in the above logs as suspicious to the described symptoms, especially with keyboard working in cryptsetup. Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client bug: timer event25 debounce: offset negative (-111ms) Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client bug: timer event25 debounce: offset negative (-44ms) Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client bug: timer event25 debounce short: offset negative (-57ms) When libinput initialized if it failed to configure those input devices, that /might/ explain the behavior. Flipping the hinge will cause them to come on/off the bus and let libinput try again. ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty
** Changed in: libxmlb (Ubuntu) Status: Triaged => Fix Released ** Changed in: libxmlb (Ubuntu Disco) Status: Won't Fix => Fix Released ** Changed in: libxmlb (Ubuntu) Assignee: Robert Ancell (robert-ancell) => Mario Limonciello (superm1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1817223 Title: [disco-proposed] The list of applications in Ubuntu Software is empty Status in gnome-software package in Ubuntu: Triaged Status in libxmlb package in Ubuntu: Fix Released Status in gnome-software source package in Disco: Won't Fix Status in libxmlb source package in Disco: Fix Released Bug description: Hi The COMPLETE LIST of applications in Ubuntu Software is not showing up See attached image Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.31.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 19:11:23 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.31.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1817223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811169] Re: Device firmware update does not detect AC power
To me this sounds like it's probably Gnome Software not fwupd. ** Changed in: fwupd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1811169 Title: Device firmware update does not detect AC power Status in fwupd package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Incomplete Bug description: On a freshly installed Ubuntu 18.10 on a Lenovo T580, the Gnome Software center after awhile proposes to install a couple of firmware related updates. At first the AC wasn't connected, and upon trying to install either of the updates, a popup appears saying that the update cannot continue without the AC being plugged in. This is so far expected behavior. But even after connecting the laptop to the AC power supply, the message persists, making it not possible to continue with the firmware updates. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 10 00:59:20 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-01-09 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1811169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798470] Re: gnome-software can't handle composite CAB files
Yes, confirmed this is still fixed in 3.18.1-0ubuntu4.18.04.8. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719797] Re: Firmware update seemingly not working
I just downgraded an XPS 9370 and then upgraded it again using gnome- software 3.28.1-0ubuntu4.18.04.8 and it works like I expected. ** Tags removed: artful verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working Status in fwupd package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in fwupd source package in Bionic: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software package in Fedora: Confirmed Bug description: The fix for this particular issue is tracked in SRU bug https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 Regression potential: Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. Test case: 1) Run a UEFI firmware update from Gnome software. 2) Make sure that the update disappears from the listing after pressing the update button. Original bug: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798470] Re: gnome-software can't handle composite CAB files
I've upgraded on a bionic machine to 3.28.1-0ubuntu4.18.04.5. xdg-open FirmwareUpdateLinux_00.00.07.cab opens a composite CAB file in gnome-software now. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719797] Re: Firmware update seemingly not working
I've tested the fwupd half of this SRU (couldn't test the gnome-software as it's not yet in place). The fwupd half works properly. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working Status in fwupd package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in fwupd source package in Bionic: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software package in Fedora: Unknown Bug description: The fix for this particular issue is tracked in SRU bug https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 Regression potential: Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. Test case: 1) Run a UEFI firmware update from Gnome software. 2) Make sure that the update disappears from the listing after pressing the update button. Original bug: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798470] Re: gnome-software can't handle composite CAB files
$ gnome-software --version gnome-software 3.30.2 $ xdg-open DellUsbCDockFirmwareUpdateLinux_00.00.07.cab Now does the right thing ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Bug description: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798470] [NEW] gnome-software can't handle composite CAB files
Public bug reported: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f ** Affects: gnome-software (Ubuntu) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: gnome-software (Ubuntu Bionic) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: gnome-software (Ubuntu Dd-series) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Also affects: gnome-software (Ubuntu Dd-series) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Dd-series) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Status in gnome-software source package in DD-Series: New Bug description: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798014] [NEW] [sru] backport 0.5 release to bionic
Public bug reported: [Impact] * The bolt 0.4 release introduced support for Thunderbolt force power, but it has been reported that this conflicts with the fwupd force power support. This is a regression as a result of 0.4 being backported to bionic. * Bolt 0.5 will work together with other applications that support the bolt force power API (such as fwupd 1.0.9) to make sure that one doesn't stomp on the other's toes. [Test Case] * Open up Thunderbolt GUI in gnome control center and ensure Thunderbolt devices are listed when plugged in. [Regression Potential] * Regressions if manifested would cause thunderbolt security levels to not function proplery. [Other Info] An SRU is filed for fwupd 1.0.9 which also support bolt and fwupd coordinating force power. ** Affects: bolt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1798014 Title: [sru] backport 0.5 release to bionic Status in bolt package in Ubuntu: New Bug description: [Impact] * The bolt 0.4 release introduced support for Thunderbolt force power, but it has been reported that this conflicts with the fwupd force power support. This is a regression as a result of 0.4 being backported to bionic. * Bolt 0.5 will work together with other applications that support the bolt force power API (such as fwupd 1.0.9) to make sure that one doesn't stomp on the other's toes. [Test Case] * Open up Thunderbolt GUI in gnome control center and ensure Thunderbolt devices are listed when plugged in. [Regression Potential] * Regressions if manifested would cause thunderbolt security levels to not function proplery. [Other Info] An SRU is filed for fwupd 1.0.9 which also support bolt and fwupd coordinating force power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1798014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719797] Re: Firmware update seemingly not working
fwupd -- This has been fixed upstream in the 1.1.3 release, so marking the development release task complete. The 1.0.9 SRU bug for bionic is here: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 gnome-software There is an SRU in progress for 3.28.1-0ubuntu4.18.04.4 that I don't want to de-rail by uploading a new patch for this bug. Once that one is in https://gitlab.gnome.org/GNOME/gnome-software/commit/057eea7cc03d647544b5819ff37951f7bfffb77e should be added to this SRU bug. ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working Status in fwupd package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in fwupd source package in Bionic: In Progress Status in gnome-software source package in Bionic: New Status in gnome-software package in Fedora: Unknown Bug description: The fix for this particular issue is tracked in SRU bug https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 Regression potential: Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. Test case: 1) Run a UEFI firmware update from Gnome software. 2) Make sure that the update disappears from the listing after pressing the update button. Original bug: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614105] Re: /usr/lib/x86_64-linux-gnu/fwupd/fwupd:11:as_store_load_yaml_file:as_store_from_file_internal:as_store_load_app_info_file:as_store_load_app_info:as_store_search_app
This particular issue hasn't received reports in anything newer than Ubuntu 16.04. The fwupd version in 16.04 is in deep maintenance mode and issues on the branches contained there (0.7.x and 0.8.x) will not be fixed. ** Changed in: appstream-glib (Ubuntu) Status: Triaged => Invalid ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released ** Also affects: appstream-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1614105 Title: /usr/lib/x86_64-linux- gnu/fwupd/fwupd:11:as_store_load_yaml_file:as_store_from_file_internal:as_store_load_app_info_file:as_store_load_app_info:as_store_search_app_info Status in appstream-glib package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in appstream-glib source package in Xenial: New Status in fwupd source package in Xenial: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding fwupd. This problem was most recently seen with version 0.7.0-0ubuntu4.2, the problem page at https://errors.ubuntu.com/problem/383fc92e3f070ac2836bf575ac0ddc40814a5427 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1614105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631002] Re: fwupd crashed with SIGSEGV in malloc_consolidate()
** Changed in: fwupd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1631002 Title: fwupd crashed with SIGSEGV in malloc_consolidate() Status in fwupd package in Ubuntu: Invalid Status in libusb package in Ubuntu: Confirmed Bug description: fwupd crashed with SIGSEGV in malloc_consolidate() ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: fwupd 0.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Oct 6 19:48:13 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/fwupd/fwupd InstallationDate: Installed on 2016-08-20 (47 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/fwupd/fwupd ProcEnviron: Signal: 11 SourcePackage: fwupd StacktraceTop: malloc_consolidate (av=av@entry=0x7f8d3420) at malloc.c:4202 _int_free (av=0x7f8d3420, p=0x7f8d34003b20, have_lock=0) at malloc.c:4110 __GI___libc_free (mem=) at malloc.c:2982 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: fwupd crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (32 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1631002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756695] Re: gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 I'll mark it as such, if we have evidence it's not at some point we can re-visit. ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1756695 Title: gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc Status in fwupd package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I need to get out more. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10 Uname: Linux 4.15.0-13-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Sun Mar 18 08:08:22 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-03-17 (0 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu4 ProcCmdline: gnome-software ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 in g_main_context_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout fax lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1756695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761061] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 ** This bug is no longer a duplicate of bug 1756695 gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1761061 Title: gnome-software crashed with signal 5 Status in gnome-software package in Ubuntu: New Bug description: This crash appears for no reason after updating using the updater app, not gnome-software ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 4 06:45:56 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2014-06-13 (1390 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1761061/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761010] Re: gnome-software crashed with signal 5 in g_main_context_new → g_dbus_connection_send_message_with_reply_sync → g_dbus_connection_call_sync_internal → g_dbus_connect
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 ** This bug is no longer a duplicate of bug 1756695 gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1761010 Title: gnome-software crashed with signal 5 in g_main_context_new → g_dbus_connection_send_message_with_reply_sync → g_dbus_connection_call_sync_internal → g_dbus_connection_call_with_unix_fd_list_sync → g_dbus_proxy_call_sync_internal → g_dbus_proxy_call_sync → fwupd_client_get_devices → gs_plugin_fwupd_add_updates Status in gnome-software package in Ubuntu: Confirmed Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 4 00:16:32 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-03-03 (31 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 in g_main_context_new() UpgradeStatus: Upgraded to bionic on 2018-03-03 (31 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1761010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763390] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 ** This bug is no longer a duplicate of bug 1756695 gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1763390 Title: gnome-software crashed with signal 5 Status in gnome-software package in Ubuntu: New Bug description: This crashed after rebooting my system, no idea why ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Apr 12 10:14:50 2018 DuplicateOf: https://bugs.launchpad.net/bugs/1756695 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-04-03 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu7 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719797] Re: Firmware update seemingly not working
** Description changed: + The fix for this particular issue is tracked in SRU bug + https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 + + Regression potential: + Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. + + Test case: + 1) Run a UEFI firmware update from Gnome software. + 2) Make sure that the update disappears from the listing after pressing the update button. + + Original bug: + Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working Status in fwupd package in Ubuntu: Triaged Status in gnome-software package in Ubuntu: Triaged Status in fwupd source package in Bionic: In Progress Status in gnome-software source package in Bionic: New Status in gnome-software package in Fedora: Unknown Bug description: The fix for this particular issue is tracked in SRU bug https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 Regression potential: Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. Test case: 1) Run a UEFI firmware update from Gnome software. 2) Make sure that the update disappears from the listing after pressing the update button. Original bug: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate
Try d-feet as root. I think I recalled seeing this too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate
When I did those PR upstream I did it with a swapfile actually on Ubuntu. The key comes down to how initramfs-tools hands off the offsets. It's kinda a jumbled mess though. I started a discussion here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950 but it got stalled and I got busy with other stuff and didn't resume it. ** Bug watch added: Debian Bug tracker #890950 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719797] Re: Firmware update seemingly not working
** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu Bionic) Assignee: (unassigned) => Mario Limonciello (superm1) ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu) Assignee: (unassigned) => Mario Limonciello (superm1) ** No longer affects: gnome-software -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working Status in fwupd package in Ubuntu: Triaged Status in gnome-software package in Ubuntu: Triaged Status in fwupd source package in Bionic: In Progress Status in gnome-software source package in Bionic: New Status in gnome-software package in Fedora: Unknown Bug description: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719797] Re: Firmware update seemingly not working
** Changed in: fwupd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working Status in GNOME Software: New Status in fwupd package in Ubuntu: Triaged Status in gnome-software package in Ubuntu: Triaged Status in gnome-software package in Fedora: Unknown Bug description: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
