[Bug 1968743] [NEW] Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in Xubuntu
Public bug reported: Very simple to repro. Starting Xubuntu 20.04 (bug still present in 22.04): 1. Open rhythmbox 2. Hit Ctrl+Q (Quit) or Ctrl+W (Close window) 3. Nothing happens This was working fine in Xubuntu 18.04 This bug can be reproduced in the Live USB version (i.e. "Try Xubuntu") Upstream claims it should be working and it works under GNOME: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1961 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 Uname: Linux 5.13.7+ x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Apr 12 11:39:22 2022 InstallationDate: Installed on 2017-12-22 (1572 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: rhythmbox UpgradeStatus: Upgraded to focal on 2022-04-07 (4 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968743 Title: Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1968743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968238] [NEW] apt-cacher-ng is completely broken and corrupts data
Public bug reported: After upgrading to Ubuntu 20.04 apt-cacher-ng started to behave erratically. Trying to do `apt update` would randomly throw errors such as: Err:20 https://repo.skype.com/deb stable InRelease Reading from proxy failed - select (115: Operation now in progress) [IP: 192.168.1.13 4687] But before the error appears, the connection would stay frozen for a minute or so. But please note that it is NOT related to HTTPS protocol, and this would be *random*. Trying to execute the command again could succeed for this website but fail for another, regardless of http/https protocol. Sometimes 6 URLs would fail, other times it would be only 1 or 2. But that's not the only broken thing. Going to the web interface (via http://192.168.1.13:4687/acng- report.html) I could go to the maintenance sections and I would see the same errors: - The cleanup section would stall forever - The cleanup section would throw random "500 internal error, SELECT returned bad file descriptor. Aborting" Purging the package and installing again did not fix it. The only solution was to install version 3.6.4-1_amd from http://ftp.debian.org/debian/pool/main/a/apt-cacher-ng/apt-cacher- ng_3.6.4-1_amd64.deb which works with Ubuntu 20.04. That fixed all the problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt-cacher-ng 3.3.1-2build1 Uname: Linux 5.13.7+ x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 7 20:47:45 2022 InstallationDate: Installed on 2017-12-22 (1567 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: apt-cacher-ng UpgradeStatus: Upgraded to focal on 2022-04-07 (0 days ago) modified.conffile..etc.apt-cacher-ng.security.conf: [inaccessible: [Errno 13] Permission denied: '/etc/apt-cacher-ng/security.conf'] mtime.conffile..etc.apt-cacher-ng.acng.conf: 2022-04-07T20:47:42.966343 ** Affects: apt-cacher-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968238 Title: apt-cacher-ng is completely broken and corrupts data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1968238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
This bug is related to https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1928244 https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811 Kernel 5.13 can be compiled in one of the two ways: 1. Use dwarves 1.21, which needs Ubuntu 21.04 and breaks installation for older systems 2. Disable CONFIG_DEBUG_INFO_BTF, thus allowing it to be compiled with older toolchains and thus, for older Ubuntu releases. I believe the sensible approach would be to temporarily follow the second option until a better solution is found as proposed in 1912811. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916919] Re: after upgrade to 5.4.0-66 monitor remains black after off/on cycle
As a workaround you can try booting with "amdgpu.dc=0" Although I don't know if Vega supports disabling DC. With DC disabled, the GPU cannot know if your monitor has been turned off. Another possible solution is to use an SSH session to try to restore your monitor, typing: DISPLAY=:0.0 xrandr --auto -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916919 Title: after upgrade to 5.4.0-66 monitor remains black after off/on cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)
This bug should be marked as CRITICAL and be fixed ASAP. It's preventing automatic security upgrades. Hopefully this was a mistake by a packager, but investigation should be made in order to check this isn't a Supply Chain Attack More info on apt output: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-66-generic linux-hwe-5.4-headers-5.4.0-66 linux-image-5.4.0-66-generic linux-modules-5.4.0-66-generic linux-modules-extra-5.4.0-66-generic The following packages have been kept back: mesa-va-drivers mesa-va-drivers:i386 mesa-vulkan-drivers:i386 The following packages will be upgraded: dirmngr dnsmasq-base gnupg gnupg-agent gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv idle-python2.7 idle-python3.6 libpython2.7 libpython2.7-dev libpython2.7-minimal libpython2.7-stdlib libpython3.6 libpython3.6-dev libpython3.6-minimal libpython3.6-stdlib linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-libc-dev python-httplib2 python2.7 python2.7-dev python2.7-minimal python3-httplib2 python3.6 python3.6-dev python3.6-minimal retroarch xterm 37 upgraded, 5 newly installed, 0 to remove and 3 not upgraded. Need to get 33,4 MB/166 MB of archives. After this operation, 349 MB of additional disk space will be used. Do you want to continue? [Y/n] Ign:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7-dev amd64 2.7.17-1~18.04ubuntu1.3 Ign:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-dev amd64 2.7.17-1~18.04ubuntu1.3 Ign:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7 amd64 2.7.17-1~18.04ubuntu1.3 Ign:4 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7 amd64 2.7.17-1~18.04ubuntu1.3 Ign:5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-stdlib amd64 2.7.17-1~18.04ubuntu1.3 Ign:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3 Ign:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3 Err:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7-dev amd64 2.7.17-1~18.04ubuntu1.3 404 Not Found [IP: 91.189.91.39 80] Err:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-dev amd64 2.7.17-1~18.04ubuntu1.3 404 Not Found [IP: 91.189.91.39 80] Err:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7 amd64 2.7.17-1~18.04ubuntu1.3 404 Not Found [IP: 91.189.91.39 80] Err:4 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7 amd64 2.7.17-1~18.04ubuntu1.3 404 Not Found [IP: 91.189.91.39 80] Err:5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-stdlib amd64 2.7.17-1~18.04ubuntu1.3 404 Not Found [IP: 91.189.91.39 80] Err:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3 404 Not Found [IP: 91.189.91.39 80] Err:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-dev_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7-dev_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7-stdlib_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.91.39 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916915 Title: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale) To manage notifications about this bug go to:
[Bug 1900062] [NEW] AMDGPU resume fail with RX 560
Public bug reported: Description:Ubuntu 18.04.5 LTS In kernel 5.4.0-51 (known good: 5.4.0-48), resuming from suspend results in the monitors not turning up and the keyboard locked up. However the system still responds to SSH sessions. - The bug sometimes also triggers when plugging or unplugging an HDMI TV. - 'sudo shutdown now' will never finish. The kernel is stuck - 'sudo service lightdm restart' will never finish. - In my case dmesg nor xorg.log notice at all something went wrong - Trying to kill X reveals the following: [ 1571.941734] Call Trace: [ 1571.941747] __schedule+0x293/0x720 [ 1571.941752] ? __queue_work+0x14c/0x400 [ 1571.941758] schedule+0x33/0xa0 [ 1571.941765] rpm_resume+0x108/0x780 [ 1571.941769] ? __switch_to_asm+0x40/0x70 [ 1571.941776] ? wait_woken+0x80/0x80 [ 1571.941782] __pm_runtime_resume+0x4e/0x80 [ 1571.941939] amdgpu_drm_ioctl+0x39/0x80 [amdgpu] [ 1571.941944] do_vfs_ioctl+0xa9/0x640 [ 1571.941950] ? __schedule+0x29b/0x720 [ 1571.941954] ksys_ioctl+0x75/0x80 [ 1571.941957] __x64_sys_ioctl+0x1a/0x20 [ 1571.941964] do_syscall_64+0x57/0x190 [ 1571.941968] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 1571.941973] RIP: 0033:0x7f746d5a96d7 [ 1571.941982] Code: Bad RIP value. [ 1571.941985] RSP: 002b:7fff1ec6a7a8 EFLAGS: 3246 ORIG_RAX: 0010 [ 1571.941990] RAX: ffda RBX: 7fff1ec6a7e0 RCX: 7f746d5a96d7 [ 1571.941992] RDX: 7fff1ec6a7e0 RSI: c06864a2 RDI: 000d [ 1571.941994] RBP: 7fff1ec6a7e0 R08: R09: [ 1571.941996] R10: R11: 3246 R12: c06864a2 [ 1571.941998] R13: 000d R14: 55f52f391780 R15: 55f52f2176a0 [ 1571.942021] INFO: task chrome:shlo0:2563 blocked for more than 120 seconds. [ 1571.942026] Tainted: G OE 5.4.0-51-generic #56~18.04.1-Ubuntu [ 1571.942029] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.774402] python3:disk$2 D0 6187 1 0x80004002 [ 1692.774404] Call Trace: [ 1692.774410] __schedule+0x293/0x720 [ 1692.774414] ? __switch_to_asm+0x40/0x70 [ 1692.774419] schedule+0x33/0xa0 [ 1692.774424] schedule_preempt_disabled+0xe/0x10 [ 1692.774429] __mutex_lock.isra.9+0x26d/0x4e0 [ 1692.774436] __mutex_lock_slowpath+0x13/0x20 [ 1692.774441] ? __mutex_lock_slowpath+0x13/0x20 [ 1692.774446] mutex_lock+0x2f/0x40 [ 1692.774472] drm_release+0x2e/0xd0 [drm] [ 1692.774476] __fput+0xc6/0x260 [ 1692.774481] fput+0xe/0x10 [ 1692.774485] task_work_run+0x9d/0xc0 [ 1692.774491] do_exit+0x382/0xb80 [ 1692.774496] ? mem_cgroup_try_charge+0x75/0x190 [ 1692.774503] do_group_exit+0x43/0xa0 [ 1692.774506] get_signal+0x14f/0x860 [ 1692.774512] do_signal+0x34/0x6d0 [ 1692.774515] ? strlcpy+0x32/0x50 [ 1692.774519] ? __x64_sys_futex+0x13f/0x190 [ 1692.774525] exit_to_usermode_loop+0x90/0x130 [ 1692.774530] do_syscall_64+0x170/0x190 [ 1692.774534] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 1692.774536] RIP: 0033:0x7f7f31d789f3 [ 1692.774541] Code: Bad RIP value. [ 1692.774543] RSP: 002b:7f7ef49abd10 EFLAGS: 0246 ORIG_RAX: 00ca [ 1692.774546] RAX: fe00 RBX: 02041e80 RCX: 7f7f31d789f3 [ 1692.774548] RDX: RSI: 0080 RDI: 02041ea8 [ 1692.774549] RBP: 02041ea4 R08: R09: [ 1692.774551] R10: R11: 0246 R12: 02041ea8 [ 1692.774553] R13: R14: 02041e58 R15: 0002 [ 1692.774558] INFO: task kworker/4:1:6532 blocked for more than 241 seconds. [ 1692.774561] Tainted: G OE 5.4.0-51-generic #56~18.04.1-Ubuntu [ 1692.774563] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.774566] kworker/4:1 D0 6532 2 0x80004000 This bug seems to be reported in upstream: https://bugzilla.kernel.org/show_bug.cgi?id=204241 https://bugzilla.kernel.org/show_bug.cgi?id=209457 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-51-generic 5.4.0-51.56~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 15 20:04:48 2020 InstallationDate: Installed on 2017-12-22 (1028 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2018-05-26 (873 days ago) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900062 Title: AMDGPU resume fail with RX 560 To manage notifications about this bug go to:
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
I can also confirm 5.3.0-59 fixed the bug on my HW as well. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-meta-hwe (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Hi, I'm just passing by. Regarding amdgpu issues related with Ryzen / Vega iGPU, there are a couple steps you can try: 1. Try a newer firmware blob. Download e.g. 1a. Download the latest firmware and unpack it https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz 1b. Backup your /lib/firmware folder 1c. sudo make install A newer firmware could fix the issue (it did for me on Ubuntu 18.04). If this fixes your problem, remember to freeze the linux-firmware package otherwise the next update will overwrite your changes and instability will come back. 2. Try a newer libdrm. Kernel updates for amdgpu go hand in hand with libdrm, but sometimes backports get these out of sync, or you try a mainline kernel but without a mainline libdrm. Download latest libdrm from https://gitlab.freedesktop.org/mesa/drm compile it and replace your Ubuntu's installation with your custom build one -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879997] Re: HP-255-G7-Notebook-PC 5.3.0-51-generic
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879997 Title: HP-255-G7-Notebook-PC 5.3.0-51-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879807 Title: 5.3.0-53 Kernel system falis to reboot after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881253] Re: PC fails to power off at end of shutdown
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881253 Title: PC fails to power off at end of shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880005] Re: Shutdown/Poweroff Failed with Kernel 5.0.3-53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880005 Title: Shutdown/Poweroff Failed with Kernel 5.0.3-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
** Also affects: dri via https://gitlab.freedesktop.org/drm/amd/-/issues/1094 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881516] Re: PC fails to power-off on kernel 5.3.0.53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881516 Title: PC fails to power-off on kernel 5.3.0.53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1881516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874325] Re: Eoan update: upstream stable patchset 2020-04-22
This series of patches broke: https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe/+bug/1880041/comments/19 Commit drm/amdgpu: fix gfx hang during suspend with video playback (v2) https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/?id=6ad2b975986441870a9a67051f9571b5c09c2569 has a known issue and already has a fix in upstream: https://gitlab.freedesktop.org/drm/amd/-/issues/1094 However this fix has not been backported to 18.04 LTS HWE, thus leaving Ryzen systems with integrated GPUs unable to shutdown or reboot. ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1094 https://gitlab.freedesktop.org/drm/amd/-/issues/1094 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874325 Title: Eoan update: upstream stable patchset 2020-04-22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
[BISECTED], FOUND After bisecting, I found the troublesome commit: drm/amdgpu: fix gfx hang during suspend with video playback (v2) https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/?id=6ad2b975986441870a9a67051f9571b5c09c2569 This problem is known and already has a bugfix in upstream: https://gitlab.freedesktop.org/drm/amd/-/issues/1094 Now that the problem has been identified and it affects normal operation of hardware I ask the ticket be raised to CRITICAL and either fixes in DRM upstream be backported to 18.04 LTS HWE, or the patch undone. Thanks Log: git bisect start git bisect bad a70cc238a0294ad63dbeb73c69450e8156cf31d8 git bisect good 6791ee82bfa161e17a9f94952c84b2b0aa0829ed git bisect good d7b1d9a450581a59eeec1f07b1899735063f7b54 git bisect good dd4cf9beceff77431ef18568be7b04357d391052 git bisect good f1c670058149fc6bc7fe59e462abeeefbc3176df git bisect skip 76d6c1bf805637505abb65b2964565e43f59dc63 git bisect skip 74b95fb8681aebab7b652dd9d6b5f8f30fa5792d git bisect skip 519d5c524073ab2bc51fc81a1dce4ca45017029a git bisect bad 548b3e311d63d6bc87e3fbb70adc9fcb5fce4083 git bisect bad addad368a3a0d07f1fee652589750a9d51c26d5b git bisect bad 1a3962a990cdc9be7b039c843de8e7f028b3cc68 git bisect bad 6ad2b975986441870a9a67051f9571b5c09c2569 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1094 https://gitlab.freedesktop.org/drm/amd/-/issues/1094 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865913] Re: amdgpu drivers crashe is very often
Try installing the latest firmware from git: 1. Make a backup of /lib/firmware 2. Download the latest firmware package e.g. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz 3. Unzip it 4. sudo make install 5. Reboot your system If you're lucky like me and it makes your system stable, then remember to freeze the package 'linux-firmware' to prevent an update from overwriting your changes and making your system unstable again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865913 Title: amdgpu drivers crashe is very often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1865913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880178] Re: Regression: Cannot shutdown or reboot with 5.3.0-53-generic kernel (18.04) Lenovo ThinkCentre M75s
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880178 Title: Regression: Cannot shutdown or reboot with 5.3.0-53-generic kernel (18.04) Lenovo ThinkCentre M75s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880381] Re: No full shutdown 5.3.0-53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880381 Title: No full shutdown 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880695] Re: system hangs at shutdown or restart
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880695 Title: system hangs at shutdown or restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880695] Re: system hangs at shutdown or restart
Duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe/+bug/1880041 Please pass there by and select that you're affected too so it gets more attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880695 Title: system hangs at shutdown or restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
But is still present as of package linux-meta-hwe (5.3.0.53.110) bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install
Duplicate tickets: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1880425 https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 Possibly duplicate (unsure): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879807 Title: 5.3.0-53 Kernel system falis to reboot after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
Duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe/+bug/1880041 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
Same. I reported it as https://bugs.launchpad.net/ubuntu/+source/linux- signed-hwe/+bug/1880425 and I just noticed this bug report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880425] Re: REGRESSION Linux kernel 5.3.0-53 freeze on shutdown/restart
Please marks this as duplicate of: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 I only just found it after reporting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880425 Title: REGRESSION Linux kernel 5.3.0-53 freeze on shutdown/restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1880425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880425] [NEW] REGRESSION Linux kernel 5.3.0-53 freeze on shutdown/restart
Public bug reported: Last known good: 5.3.0-51 Last known bad: 5.3.0-53 System: Laptop Ryzen 2500U 8GB RAM Lenovo ideapad 330-15 ARR Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-image-5.3.0-53 linux-image-5.3.0-53-generic: Installed: 5.3.0-53.47~18.04.1 Candidate: 5.3.0-53.47~18.04.1 Version table: *** 5.3.0-53.47~18.04.1 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status linux-image-5.3.0-53-lowlatency: Installed: (none) Candidate: 5.3.0-53.47~18.04.1 Version table: 5.3.0-53.47~18.04.1 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages Symptoms: The system will lock right when it should shutdown or restart. The screen goes blank (but monitor doesn't turn off) and keyboard becomes locked up (i.e. numpad LED still lit, but will not respond). Only solution is to keep holding Power down for 10 seconds. Attached core dump from lightdm which seems to be generated with the crash. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-53-generic 5.3.0-53.47~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 24 14:26:40 2020 InstallationDate: Installed on 2019-05-21 (368 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "_usr_sbin_lightdm.0.crash" https://bugs.launchpad.net/bugs/1880425/+attachment/5376274/+files/_usr_sbin_lightdm.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880425 Title: REGRESSION Linux kernel 5.3.0-53 freeze on shutdown/restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1880425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
You mean bisecting the git commits from mainline linux-firmware; compare it against https://kernel.ubuntu.com/git/ubuntu/linux- firmware.git/log/?h=bionic until I isolate the culprit(s)? Yes I can do that. It will take a while though (laptop needs to reboot with every attempt, it may take a while to crash, etc) Does anyone know if: service lightdm stop rmmod amdgpu modprobe amdgpu service lightdm start will reupload the firmware blob? That would speed up the testing process tremendously. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
** Attachment added: "uname.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+attachment/5305900/+files/uname.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852857] [NEW] Use more modern Raven Ridge firmware in linux-firmware package
Public bug reported: I own a: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) Description:Ubuntu 18.04.3 LTS Release:18.04 linux-firmware: Installed: 1.173.12 Candidate: 1.173.12 Version table: *** 1.173.12 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin 4d7651ab7fc4dba1abcfaf4a88f40686 raven2_pfp.bin 4ac07f88b9c4aa4fe026be87cb16ceda raven2_rlc.bin ac3a488f651921bc5a21b5a443ee7c23 raven2_sdma.bin 2372175130589c169afc4bc0e0435705 raven2_vcn.bin fe5ec673b44d95c686a240a8d138f499 raven_asd.bin 3e4aeb199a9e1c56a398d5b4ff6a7166 raven_ce.bin b5387b400b0ee4b04565a5179aebb9cd raven_dmcu.bin 052cdc264b228656dff12b95def55c54 raven_gpu_info.bin b16a081785f2f75a6f326ca5ca92113d raven_me.bin 4390c8485f4d4583ae878aa227968a48 raven_mec2.bin 4390c8485f4d4583ae878aa227968a48 raven_mec.bin f69ef2e297e66eb68eecb02540780f4c raven_pfp.bin 0e5fff019103b4cdc5a0366e29411fdd raven_rlc.bin df5f1ef96feade475a9c83451d840bb3 raven_sdma.bin 7e22527c2ef5e9b6e4e871d6ec546848 raven_vcn.bin There's the possibility that I'm wrong and the actually firmware file is not related to Raven Ridge (I doubt it, my usage when it freezes points to being a GPU problem) More specifically I'm using these https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tag/?h=20190815 I have been working with these new firmware files for months and no crashes. Yesterday linux-firmware was updated reverting my changes, and it started locking up again. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1852857/+attachment/5305899/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827302] Re: 18.10 → 19.04 Alt-Tab cycling no longer includes Slack window
This bug started in Slack 3.4.0 and affects Xubuntu 18.04.2 LTS too.
The problem happens because xfwm4 looks for any of the following:
"_NET_WM_WINDOW_TYPE_DESKTOP",
"_NET_WM_WINDOW_TYPE_DIALOG",
"_NET_WM_WINDOW_TYPE_DOCK",
"_NET_WM_WINDOW_TYPE_MENU",
"_NET_WM_WINDOW_TYPE_NORMAL",
"_NET_WM_WINDOW_TYPE_SPLASH",
"_NET_WM_WINDOW_TYPE_TOOLBAR",
"_NET_WM_WINDOW_TYPE_UTILITY",
But Slack doesn't set them.
I compiled xfwm4 from source, debugged remotely (it is nearly impossible
to halt the window manager in the host machine...) and the problem boils
down to:
1. clientCycleCreateList in cycle.c calls:
if (!clientSelectMask (c2, NULL, search_range, WINDOW_REGULAR_FOCUSABLE))
{
TRACE ("%s not in select mask", c2->name);
continue;
}
2. Inside clientSelectMask in focus.c, c2->type = 0; thus "return
c2->type & mask" returns 0 regardless of the mask and thinks the window
should not be alt-tabbed
3. I believe (not 100% sure) this happens because in clientWindowType in
netwm.c, c->type_atom == None. I don't know whether this should be
treated as a client bug or a window manager bug. I'm not an X11 expert
so I don't know if it is possible to know if a window is the root one,
but root windows should definitely be alt-tabbeable.
If I change the line to:
if (!clientSelectMask (c2, NULL, search_range,
WINDOW_REGULAR_FOCUSABLE) && c2->type != UNSET)
Then Slack works with alt+tab and my computer hasn't blown up yet. I
don't know if it's the proper fix though, but it may be
I fixed this problem by rebuilding xfwm4 with the attached patch:
mkdir tmp
cd tmp
sudo apt install devscripts build-essential fakeroot dpkg-dev
sudo apt-get build-dep xfwm4
apt-get source xfwm4
cd xfwm4-4.12.5
patch -i xfwm4_slack_fix.diff #Point it where the patch is located!!!
debuild -b -uc -us
sudo dpkg -i ../xfwm4_4.12.5-1ubuntu0.18.04.1_amd64.deb
** Patch added: "Alt + Tab fix for xfwm4 and Slack"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/+attachment/5261320/+files/xfwm4_slack_fix.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827302
Title:
18.10 → 19.04 Alt-Tab cycling no longer includes Slack window
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827302] Re: 18.10 → 19.04 Alt-Tab cycling no longer includes Slack window
I'm attaching .deb and .ddeb (debug symbols) files I built myself if someone's too lazy or too busy to rebuild the patched xfwm4 him/herself. It has been working fine for me so far. USE THEM AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR WHAT HAPPENS IF YOU TRY THEM. ** Attachment added: "Built deb & .ddeb versions of the patched xfwm4 (USE THEM AT YOUR OWN RISK)" https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/+attachment/5261322/+files/xfwm4_4.12.5-1ubuntu0.18.04.1_amd64.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827302 Title: 18.10 → 19.04 Alt-Tab cycling no longer includes Slack window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827302] Re: 18.10 → 19.04 Alt-Tab cycling no longer includes Slack window
Sorry my bad, the diff is reversed. Use the following commands instead: mkdir tmp cd tmp sudo apt install devscripts build-essential fakeroot dpkg-dev sudo apt-get build-dep xfwm4 apt-get source xfwm4 cd xfwm4-4.12.5 patch -R -p1 -i xfwm4_slack_fix.diff # !!! Point it where the patch is located!!! debuild -b -uc -us sudo dpkg -i ../xfwm4_4.12.5-1ubuntu0.18.04.1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827302 Title: 18.10 → 19.04 Alt-Tab cycling no longer includes Slack window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
Found upstream discussion: https://forum.xfce.org/viewtopic.php?id=12138 Apparently the problem is caused because xfce4-power-manager migrated to upower, which has only empty, caution, low, good, and full icon themes. That's 3 states + a caution + empty. IMO that's too few. And yes, the icon themes are misleading. In /usr/share/icons/elementary- xfce/status/symbolic, battery-good-symbolic takes over at 30-59%, however the icon displayed looks more like 70% full or so. Relevant files: battery-caution-charging-symbolic.svg battery-caution-symbolic.svg battery-empty-charging-symbolic.svg battery-empty-symbolic.svg battery-full-charged-symbolic.svg battery-full-charging-symbolic.svg battery-full-symbolic.svg battery-good-charging-symbolic.svg battery-good-symbolic.svg battery-low-charging-symbolic.svg battery-low-symbolic.svg GNOME icons are consistent with this scheme (it shows 3 bars). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767560 Title: Battery graph in tray icon is inaccurate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
More related discussion: https://bbs.archlinux.org/viewtopic.php?pid=1651514#p1651514 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767560 Title: Battery graph in tray icon is inaccurate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
I'm not fully certain. It appears like a theme specific bug, but it doesn't seem like the new xfce4-power-manager icon is using the theme's icons, but rather its own internal, or perhaps I'm looking at the wrong place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767560 Title: Battery graph in tray icon is inaccurate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791452] Re: screen tearing in some games (fullscreen and windowed)
Try the following: xrandr --output DVI-D-0 --set TearFree 1 You may need a different output e.g. HDMI-A-0 You can list your outputs by just running "xrandr" Apply the TearFree option to all of your monitors and try again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791452 Title: screen tearing in some games (fullscreen and windowed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
This bug affects Xubuntu 18.04 but not 17.xx or earlier
It can be easily be reproduced on any desktop machine using
https://github.com/hoelzro/linux-fake-battery-module (patch to compile
on Xubuntu 18.04 is at the end)
I can see that:
In the range [60; 100] the full battery icon is displayed
In the range [30; 59] an icon that indicates around 60% battery level is
displayed.
In the range [10; 30] an icon that indicates around 30-40% battery level is
displayed
In the range [0; 9] an orange bar is displayed
Judging from the themes in 17.xx at /usr/share/icons/elementary-
xfce/status/48 there's a lot more battery icon variety than what is
being displayed (there's icons for 6 ranges!).
As for the fake module, apply this patch:
diff --git a/fake_battery.c b/fake_battery.c
index 2e3c04c..48da386 100644
--- a/fake_battery.c
+++ b/fake_battery.c
@@ -23,6 +23,7 @@
#include
#include
+#include
static int
fake_battery_get_property1(struct power_supply *psy,
@@ -63,7 +64,6 @@ static int ac_status = 1;
static char *fake_ac_supplies[] = {
"BAT0",
-"BAT1",
};
static enum power_supply_property fake_battery_properties[] = {
@@ -99,14 +99,6 @@ static struct power_supply_desc descriptions[] = {
.get_property = fake_battery_get_property1,
},
-{
-.name = "BAT1",
-.type = POWER_SUPPLY_TYPE_BATTERY,
-.properties = fake_battery_properties,
-.num_properties = ARRAY_SIZE(fake_battery_properties),
-.get_property = fake_battery_get_property2,
-},
-
{
.name = "AC0",
.type = POWER_SUPPLY_TYPE_MAINS,
@@ -220,7 +212,7 @@ handle_charge_changes(int ac_status, struct battery_status
*battery)
static ssize_t
control_device_write(struct file *file, const char *buffer, size_t count,
loff_t *ppos)
{
-char kbuffer[1024]; /* limited by kernel frame size, 1K should be enough */
+char kbuffer[512]; /* limited by kernel frame size, 1K should be enough */
char *buffer_cursor;
char *newline;
size_t bytes_left = count;
@@ -232,8 +224,8 @@ control_device_write(struct file *file, const char *buffer,
size_t count, loff_t
return -EINVAL;
}
-if(count > 1024) {
-printk(KERN_ERR "Too much data provided to /dev/fake_battery (limit
1024 bytes)\n");
+if(count > 512) {
+printk(KERN_ERR "Too much data provided to /dev/fake_battery (limit
512 bytes)\n");
return -EINVAL;
}
@@ -264,7 +256,7 @@ control_device_write(struct file *file, const char *buffer,
size_t count, loff_t
power_supply_changed(supplies[0]);
power_supply_changed(supplies[1]);
-power_supply_changed(supplies[2]);
+//power_supply_changed(supplies[2]);
return count;
}
This patch fixes a compilation error, a gcc warning, and disables the 2nd fake
battery (by default the git repo creates 2 fake batteries)
And then run:
make
sudo insmod ./fake_battery.ko
echo 'charging = 0' | sudo tee /dev/fake_battery
echo 'capacity0 = 50' | sudo tee /dev/fake_battery
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767560
Title:
Battery graph in tray icon is inaccurate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766217] Re: software updater presents an empty panel for updating
I forgot. If after executing those commands now update-manager gets permanently stuck on "waiting for other software managers to quit" (which is kept stuck even after removing the locks in all apt places and closing all software managers), then run: sudo apt install --reinstall update-manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766217 Title: software updater presents an empty panel for updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766217] Re: software updater presents an empty panel for updating
I was having this same bug and I managed to "fix" it by deleting everything under /var/lib/apt i.e. sudo apt rm -rf /var/lib/apt/ Then run "sudo apt update" and reboot the system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766217 Title: software updater presents an empty panel for updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661842] Re: gstreamer 1.8.3 incorrectly removes some decoders and encoders when built against ffmpeg 2.8.10
This bug affects yakkety yak but I don't see an update for that platform. Am I wrong or this was missed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661842 Title: gstreamer 1.8.3 incorrectly removes some decoders and encoders when built against ffmpeg 2.8.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1661842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
I can confirm this bug still persists in latest package 304.134 on XUbuntu 16.04 LTS. The card is nForce 6150SE OpenGL does not work, but I can login to xfce because it does not need a compositor. Version 304.131 works OK. It was listed in aptitude for some reason, so I could just downgrade. I cannot use nouveau on this card because it hard-crashes (entire screen becomes filled with lots of lines in a slightly diagonal screen gray & blue pattern, stops responding, only solution is to do a hard reset) when doing "intensive" graphics usage (intensive = opening a web browser and browser one or two pages). I didn't try PPA nouveau with latest drivers, just the ones provided by stock Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
+1 to ask for a backport to 14.04. It's getting pretty annoying.
It happens every time I plug my iPad Mini 3 to the USB; it gets worst if
the system boots with the iPad already plugged ("System problem
detected" will show up as soon as I'm logged in, my screen resolution
will be wrong, then goes right, and the text is rendered differently, as
if missing antialias or using a different font)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305699
Title:
upowerd crashed with SIGSEGV in service_client_free()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327193] Re: acpi-cpufreq reports No Such Device (Jaunty)
Same problem here. Intel Quad Core QX9650 @3Ghz Motherboard ASUS P5Q-E 4GB RAM CPU Scaling works in Windows. Tried acpi-cpufreq powernow-k8 speedstep-centrino all of them just in case, with same result uname -r 2.6.26-2-amd64 lsmod: Module Size Used by nvidia 10262056 36 ppdev 11656 0 parport_pc 31016 0 lp 14724 0 parport41776 3 ppdev,parport_pc,lp ipv6 288328 20 cpufreq_powersave 6400 0 cpufreq_stats 9120 0 cpufreq_userspace 8452 0 cpufreq_ondemand 11792 0 freq_table 9344 2 cpufreq_stats,cpufreq_ondemand cpufreq_conservative11784 0 fuse 53184 4 sbp2 25356 0 loop 19468 0 snd_hda_intel 436440 2 snd_pcm_oss41760 0 snd_mixer_oss 18816 1 snd_pcm_oss snd_pcm81672 2 snd_hda_intel,snd_pcm_oss snd_seq_dummy 7428 0 snd_seq_oss33280 0 snd_seq_midi 11072 0 snd_rawmidi26784 1 snd_seq_midi snd_seq_midi_event 11904 2 snd_seq_oss,snd_seq_midi snd_seq54304 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 25744 2 snd_pcm,snd_seq snd_seq_device 11668 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq psmouse42268 0 i2c_i801 13596 0 pcspkr 7040 0 serio_raw 9860 0 i2c_core 27936 2 nvidia,i2c_i801 snd63688 13 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 12064 1 snd button 11680 0 snd_page_alloc 13072 2 snd_hda_intel,snd_pcm intel_agp 31856 0 evdev 14208 4 ext3 124944 2 jbd51240 1 ext3 mbcache12804 1 ext3 sg 36576 0 usbhid 45920 0 hid41664 1 usbhid ff_memless 9224 1 usbhid sr_mod 19652 0 cdrom 37928 1 sr_mod sd_mod 29376 6 pata_marvell8832 0 usb_storage95680 0 ata_generic10116 0 ata_piix 22660 5 ahci 33036 0 libata165600 4 pata_marvell,ata_generic,ata_piix,ahci scsi_mod 160760 6 sbp2,sg,sr_mod,sd_mod,usb_storage,libata dock 14112 1 libata floppy 61672 0 ohci1394 32692 0 skge 41744 0 ieee1394 93816 2 sbp2,ohci1394 sky2 48004 0 ide_pci_generic 9220 0 [permanent] ide_core 128284 1 ide_pci_generic ehci_hcd 35980 0 uhci_hcd 25760 0 thermal22816 0 processor 42304 1 thermal fan 9352 0 thermal_sys17728 3 thermal,processor,fan cat /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz stepping: 7 cpu MHz : 2999.673 cache size : 6144 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm bogomips: 6003.35 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz stepping: 7 cpu MHz : 2999.673 cache size : 6144 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm bogomips: 5999.37 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz stepping
[Bug 327193] Re: acpi-cpufreq reports No Such Device (Jaunty)
Ooops. I'm a bit ashamed. I'm still wondering how it works in Windows though. After more researching I had C1E (Enhanced Halt State) enabled BUT Intel SpeedStep disabled in the BIOS. After enabling it, cpu freq scaling started working and the modprobe was done automatically on boot (using acpi-cpufreq now). My apologies. -- acpi-cpufreq reports No Such Device (Jaunty) https://bugs.launchpad.net/bugs/327193 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
