[Bug 2063336] Re: All Chromium based applications fail to render on Wayland
Daniel, yes it's indeed an NVIDIA GPU as the primary one (both primary and secondary are NVIDIA, an RTX A6000 and a RTX3090). The issue shows up for both the Chromium snap and any other Chromium based app I could find. I did have some Wayland & NVIDIA issues (glitchy rendering after typing on the keyboard) also on Mantic and before on this same system, but this symptom is a lot more extreme now on Noble. Another observation as I messed around with reproducing this: I can see that on Noble hotplugging the display on Wayland doesn't really work (between these same NVIDIA GPUs), whereas on Mantic I didn't have the same problem. ** Description changed: - I am noticing two - - - Most of the time (3/4 desktop sessions attempted) all Chromium based + Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, - and when screenshotted, showing supposedly showing transparent pixels. + and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063336] [NEW] All Chromium based applications fail to render (dual NVIDIA GPU system)
Public bug reported: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug noble snap wayland-session ** Attachment added: "Screenshot showing the blank window that is supposed to be Chromium" https://bugs.launchpad.net/bugs/2063336/+attachment/5770045/+files/Screenshot%20from%202024-04-24%2016-21-59.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render (dual NVIDIA GPU system) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054928] Re: kernel UCSI fail
I have detected that the problem is triggered when power off the system, I can see that it says "spi -nor spi0.0: Error resetting software -524" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054928 Title: kernel UCSI fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2054928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054928] [NEW] kernel UCSI fail
Public bug reported: This only happens to me when I connect my USB-C docking station to my laptop. The laptop doesn't really turn off and goes crazy. To solve this I have seen that disconnecting the battery from the BIOS settings solves the problem. If I don't do this the laptop never really turns off and drains the battery. But when I start Ubuntu and restart it a couple of times it happens again. Dock: Thinkpad dock station Universal usb-c (upgraded the firmware to the last version for see this fix the problem) Laptop: Thinkpad E490 (bios upgraded to the last version) Run Ubuntu 22.04 (All upgraded !!!) kernel: 6.5.0-21-generic (with the kernel 6.5.0-18-generic same thing happens) On the same hardware configuration settings run Ubuntu 20.04 and i dont have problems. Regards!!! Belog my kernel logs ``` matias@matias-ThinkPad-E490:~$ cat /var/log/syslog | grep ucsi Feb 25 13:34:09 matias-ThinkPad-E490 kernel: [6.997101] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:05:56 matias-ThinkPad-E490 kernel: [7.077472] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:18:51 matias-ThinkPad-E490 kernel: [7.017315] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:21:56 matias-ThinkPad-E490 kernel: [7.253151] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:21:56 matias-ThinkPad-E490 kernel: [7.898290] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5) Feb 25 15:24:07 matias-ThinkPad-E490 kernel: [7.298691] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:07 matias-ThinkPad-E490 kernel: [7.298842] ucsi_acpi USBC000:00: con2: failed to get status Feb 25 15:24:08 matias-ThinkPad-E490 kernel: [8.789347] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:08 matias-ThinkPad-E490 kernel: [8.789519] ucsi_acpi USBC000:00: con3: failed to get status Feb 25 15:24:10 matias-ThinkPad-E490 kernel: [ 10.297429] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:10 matias-ThinkPad-E490 kernel: [ 10.297435] ucsi_acpi USBC000:00: con4: failed to get status Feb 25 15:24:10 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:005 Feb 25 15:24:11 matias-ThinkPad-E490 kernel: [ 11.765348] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:11 matias-ThinkPad-E490 kernel: [ 11.765353] ucsi_acpi USBC000:00: con5: failed to get status Feb 25 15:24:11 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:006 Feb 25 15:24:13 matias-ThinkPad-E490 kernel: [ 13.274527] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:13 matias-ThinkPad-E490 kernel: [ 13.274739] ucsi_acpi USBC000:00: con6: failed to get status Feb 25 15:24:13 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:007 Feb 25 15:24:14 matias-ThinkPad-E490 kernel: [ 14.798619] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:14 matias-ThinkPad-E490 kernel: [ 14.798637] ucsi_acpi USBC000:00: con7: failed to get status Feb 25 15:24:14 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:008 Feb 25 15:24:16 matias-ThinkPad-E490 kernel: [ 16.386801] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:16 matias-ThinkPad-E490 kernel: [ 16.386821] ucsi_acpi USBC000:00: con8: failed to get status Feb 25 15:24:16 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:009 Feb 25 15:24:17 matias-ThinkPad-E490 kernel: [ 18.018808] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:17 matias-ThinkPad-E490 kernel: [ 18.018827] ucsi_acpi USBC000:00: con9: failed to get status Feb 25 15:24:18 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:0010 Feb 25 15:24:19 matias-ThinkPad-E490 kernel: [ 19.621722] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:19 matias-ThinkPad-E490 kernel: [ 19.621729] ucsi_acpi USBC000:00: con10: failed to get status Feb 25 15:24:19 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:0011 Feb 25 15:24:20 matias-ThinkPad-E490 kernel: [ 21.147048] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:20 matias-ThinkPad-E490 kernel: [ 21.147071] ucsi_acpi USBC000:00: con11: failed to get status Feb 25 15:24:21 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy
[Bug 1971130] Re: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled
I left a terminal session tailing `/var/log/syslog` to track what's happening at the time when the notification shows up, and indeed managed to observe it happen again, with a fragment of system logs found below. Looks like NetworkManager fires off a `CONNECTED_SITE` state change, and the location is updated -> notification fires, even if timezone has not changed. I think the condition that triggers the unnecessary notification is the _location_ changing even if the timezone has not changed, and for whatever reason the location keeps flickering between either Denmark or Germany (both in CET). Here goes the log example: ``` May 2 15:19:41 iris NetworkManager[4609]: [1651493981.4907] manager: NetworkManager state is now CONNECTED_SITE May 2 15:19:41 iris dbus-daemon[4607]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=4609 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") May 2 15:19:41 iris systemd[1]: Starting Network Manager Script Dispatcher Service... May 2 15:19:41 iris dbus-daemon[4607]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' May 2 15:19:41 iris systemd[1]: Started Network Manager Script Dispatcher Service. May 2 15:19:41 iris NetworkManager[4609]: [1651493981.7719] manager: NetworkManager state is now CONNECTED_GLOBAL May 2 15:19:46 iris wpa_supplicant[4694]: TDLS: Invalid frame - payloadtype=1 category=240 action=26 May 2 15:19:51 iris systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. May 2 15:19:52 iris gsd-datetime[7371]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed May 2 15:19:52 iris gsd-datetime[7371]: message repeated 71 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52
[Bug 1971130] Re: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled
** Description changed: I am seeing repeated "time zone updated" notifications when "Automatic Time Zone" is enabled in Settings > Date & Time in gnome-control-center - on 22.04, whilst my gnome session continues to be active. The timezone - itself continues to be correct (and unchanged). + on 22.04, whilst my gnome session continues to be active (without me + taking any time related actions). The timezone itself continues to be + correct (and unchanged). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 2 10:26:46 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-26 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971130 Title: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971130] [NEW] Repeated "time zone updated" notifications when "Automatic Time Zone" enabled
Public bug reported: I am seeing repeated "time zone updated" notifications when "Automatic Time Zone" is enabled in Settings > Date & Time in gnome-control-center on 22.04, whilst my gnome session continues to be active. The timezone itself continues to be correct (and unchanged). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 2 10:26:46 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-26 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971130 Title: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970389] [NEW] [nvidia] Janky text entry in some applications in a GNOME / Wayland session
Public bug reported: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) ** Affects: xorg-server Importance: Unknown Status: Unknown ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy nvidia nvidia-wayland wayland wayland-session ** Attachment added: "A video showing the janky text entry" https://bugs.launchpad.net/bugs/1970389/+attachment/5583887/+files/IMG_8615.MOV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970389 Title: [nvidia] Janky text entry in some applications in a GNOME / Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
I can confirm that with the proposed update on a previously impacted system (where Wayland was not available as an option) with an NVIDIA only GPU (RTX3090), "Test Case 1" behaves after the proposed update as expected: the Wayland option is made available, but default is "Ubuntu" (not "Ubuntu on Wayland"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 1940112] Re: missing dependency of qemu-efi-aarch64 when testing arm platforms
** Tags added: cbox-51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940112 Title: missing dependency of qemu-efi-aarch64 when testing arm platforms To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1940112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] [NEW] 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
Public bug reported: After installing the proposed snapd update 2.54.2+21.10, I see the following when launching a new fish shell session on 21.10: ``` /usr/share/fish/vendor_conf.d/snapd.fish (line 3): fish_add_path -aP $snap_bin_path ^ from sourcing file /usr/share/fish/vendor_conf.d/snapd.fish called on line 294 of file /usr/share/fish/config.fish from sourcing file /usr/share/fish/config.fish called during startup ``` Said line of `/usr/share/fish/vendor_conf.d/snapd.fish` references the fish function `fish_add_path` which seems (*) to have only been made available in fish 3.2 (Ubuntu 21.10 packages 3.1.2 of fish presently). Upgrading fish by installing 3.2 or later via https://launchpad.net/~fish-shell/+archive/ubuntu/release-3 indeed works around (or modifying above script to `set -gx $PATH ...` (I guess this comes with the downside of duplicate entries that `fish_add_path` removes?) (*) PR adding `fish_add_path`: https://github.com/fish-shell/fish-shell/pull/7028 was part of the 3.2 milestone ** Affects: snapd (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/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948/+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 1937283] Re: ndiswrapper does not open, says "cannot execute command << gksu / usr / sbin / ndisgtk >>
** Changed in: ndisgtk (Ubuntu) Assignee: (unassigned) => Matias Guerrero (matiassnake) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937283 Title: ndiswrapper does not open, says "cannot execute command << gksu / usr / sbin / ndisgtk >> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndisgtk/+bug/1937283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937283] Re: ndiswrapper does not open, says "cannot execute command << gksu / usr / sbin / ndisgtk >>
Thanks. What card do we suggest? or where could I look? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937283 Title: ndiswrapper does not open, says "cannot execute command << gksu / usr / sbin / ndisgtk >> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndisgtk/+bug/1937283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937283] [NEW] ndiswrapper does not open, says "cannot execute command << gksu / usr / sbin / ndisgtk >>
Public bug reported: ndiswrapper does not open, says "cannot execute command << gksu / usr / sbin / ndisgtk >> I need to run ndiswrapper to install wireless network drivers. But I can't open it because I get the error "cannot execute command << gksu / usr / sbin / ndisgtk >>" I am new to this system, I need help ** Affects: ndiswrapper (Ubuntu) Importance: Undecided Status: New ** Tags: ndiswrapper ** Tags added: ndiswrapper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937283 Title: ndiswrapper does not open, says "cannot execute command << gksu / usr / sbin / ndisgtk >> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1937283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933344] [NEW] package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código
Public bug reported: Irror. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: socwatch2_13 vtsspp sep5 socperf3 pax zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 23 08:53:15 2021 ErrorMessage: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código de salida de error 1 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933344 Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1933344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922274] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: i have no idea ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: dkms:amd64: Install bcmwl-kernel-source:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CasperVersion: 1.445.1 Date: Thu Apr 1 14:12:50 2021 DpkgHistoryLog: Start-Date: 2021-04-01 14:11:59 Commandline: apt-get install -o DPkg::options::=--force-confnew -y bcmwl-kernel-source Install: dkms:amd64 (2.8.1-5ubuntu2, automatic), bcmwl-kernel-source:amd64 (6.30.223.271+bdcom-0ubuntu7~20.04.1) ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 LiveMediaBuild: Custom 20.04 - Release amd64 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922274 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1922274/+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 1881301] [NEW] q
Public bug reported: q ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_88_88_generic_67 wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri May 29 09:16:10 2020 DistUpgraded: 2019-01-04 17:00:34,973 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-88-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2017-02-06 (1207 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20156 ProcEnviron: LANGUAGE=es_PE:es PATH=(custom, no user) LANG=es_PE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=cef7f1ec-6114-4595-a4fc-e46a6813a2ca ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-04 (510 days ago) dmi.bios.date: 08/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN89WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G480 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G480 dmi.modalias: dmi:bvnLENOVO:bvr62CN89WW:bd08/16/2012:svnLENOVO:pn20156:pvrLenovoG480:rvnLENOVO:rnLenovoG480:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG480: dmi.product.family: ChiefRiver System dmi.product.name: 20156 dmi.product.version: Lenovo G480 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 4 13:11:34 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17740 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881301 Title: q To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881301/+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 271487] Re: terminator need to highlight search string
+1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/271487 Title: terminator need to highlight search string To manage notifications about this bug go to: https://bugs.launchpad.net/terminator/+bug/271487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877659] [NEW] package nvidia-dkms-440 440.82+really.440.64-0ubuntu6 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-440 script post-installation devolvió el código de sali
Public bug reported: graphic driver installing failure ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440 440.82+really.440.64-0ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 16:07:50 2020 ErrorMessage: el subproceso instalado paquete nvidia-dkms-440 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2018-10-21 (564 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-440 Title: package nvidia-dkms-440 440.82+really.440.64-0ubuntu6 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-440 script post-installation devolvió el código de salida de error 10 UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877659 Title: package nvidia-dkms-440 440.82+really.440.64-0ubuntu6 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-440 script post-installation devolvió el código de salida de error 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1877659/+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 1824816] [NEW] libconfig 1.5-0.2 arm64 packages randomly missing
Public bug reported: All Xenial libconfig arm64 packages (1.5-0.2) are randomly missing (load balancing server missing files?) from http://ports.ubuntu.com/ubuntu- ports/pool/universe/libc/libconfig/: E: Failed to fetch http://ports.ubuntu.com/ubuntu- ports/pool/universe/libc/libconfig/libconfig9_1.5-0.2_arm64.deb 403 Forbidden [IP: 91.189.88.151 80] E: Failed to fetch http://ports.ubuntu.com/ubuntu- ports/pool/universe/libc/libconfig/libconfig-dev_1.5-0.2_arm64.deb 403 Forbidden [IP: 91.189.88.151 80] We started noticing this with our CI server (Ubuntu 16.04.6 LTS, arm64) around April 12th. ** Affects: libconfig (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/1824816 Title: libconfig 1.5-0.2 arm64 packages randomly missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libconfig/+bug/1824816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Workaround: in ubuntu 18.4
Create an empty file /etc/NetworkManager/conf.d/10-globally-managed-devices.
Create an file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with
content:
network: {config: disabled}
Work for me,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manager does not manage ethernet and bluetooth interfaces when
Ubuntu 16.10 is installed using chroot/netboot method
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804276] [NEW] installation fails in lenovo u31-70
Public bug reported: during ubuntu 18.04 installation ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 18:14:41 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804276 Title: installation fails in lenovo u31-70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1804276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801375] [NEW] package ipmiutil (not installed) failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: Yes, and also failed "rpcbind" ProblemType: Package DistroRelease: Ubuntu 18.10 Package: ipmiutil (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: geary:amd64: Remove libgmime-2.6-0:amd64: Remove libmessaging-menu0:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Thu Nov 1 02:24:01 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2018-10-30 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: ipmiutil Title: package ipmiutil (not installed) failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.ipmiutil: [deleted] ** Affects: ipmiutil (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801375 Title: package ipmiutil (not installed) failed to install/upgrade: problemas de dependencias - se deja sin configurar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmiutil/+bug/1801375/+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 1786984] [NEW] package ca-certificates-java 20180516ubuntu1~18.04.1 failed to install/upgrade: instalado ca-certificates-java paquete post-installation guión el subproceso devolvió un error con e
Public bug reported: Error is shown everytime the system is started, the packages were reinstalled and the problem still appear. This started after an update around three weeks ago ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates-java 20180516ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: nodejs-doc:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 14 13:46:03 2018 ErrorMessage: instalado ca-certificates-java paquete post-installation guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2018-06-05 (69 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: ca-certificates-java Title: package ca-certificates-java 20180516ubuntu1~18.04.1 failed to install/upgrade: instalado ca-certificates-java paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786984 Title: package ca-certificates-java 20180516ubuntu1~18.04.1 failed to install/upgrade: instalado ca-certificates-java paquete post- installation guión el subproceso devolvió un error con estado de salida 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1786984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784235] [NEW] package pdfsam 3.3.5-1 failed to install/upgrade: intentando sobreescribir `/usr/bin/pdfsam', que está también en el paquete pdfsam 3.3.5-1
Public bug reported: I tried to install the package, and suddenly stopped. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: pdfsam 3.3.5-1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: pdfsam-basic:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jul 29 13:07:34 2018 DpkgTerminalLog: Preparando para desempaquetar .../pdfsam_3.3.6-1_all.deb ... Desempaquetando pdfsam-basic (3.3.6-1) ... dpkg: error al procesar el archivo /home/mgasperini/snap/firefox/common/Descargas/pdfsam_3.3.6-1_all.deb (--unpack): intentando sobreescribir `/usr/bin/pdfsam', que está también en el paquete pdfsam 3.3.5-1 ErrorMessage: intentando sobreescribir `/usr/bin/pdfsam', que está también en el paquete pdfsam 3.3.5-1 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: pdfsam Title: package pdfsam 3.3.5-1 failed to install/upgrade: intentando sobreescribir `/usr/bin/pdfsam', que está también en el paquete pdfsam 3.3.5-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pdfsam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784235 Title: package pdfsam 3.3.5-1 failed to install/upgrade: intentando sobreescribir `/usr/bin/pdfsam', que está también en el paquete pdfsam 3.3.5-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfsam/+bug/1784235/+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 1702187] Re: wrongly shipping /usr/locale/da/LC_MESSAGES/unity-lens-applications.mo
Still present in bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702187 Title: wrongly shipping /usr/locale/da/LC_MESSAGES/unity-lens-applications.mo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1702187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766606] [NEW] package libpaper1:amd64 1.1.24+nmu5ubuntu1 failed to install/upgrade: installed libpaper1:amd64 package post-installation script subprocess returned error exit status 1
Public bug reported: I don't know the problem. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpaper1:amd64 1.1.24+nmu5ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:33:26 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: installed libpaper1:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-05-30 (328 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libpaper Title: package libpaper1:amd64 1.1.24+nmu5ubuntu1 failed to install/upgrade: installed libpaper1:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) ** Affects: libpaper (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766606 Title: package libpaper1:amd64 1.1.24+nmu5ubuntu1 failed to install/upgrade: installed libpaper1:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpaper/+bug/1766606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714030] [NEW] package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: Im not technically able to detail the bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.11 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Aug 28 10:16:57 2017 Dependencies: ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2017-03-19 (164 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: linux-firmware Title: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714030 Title: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1714030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704803] [NEW] X11/XCB window resize is broken
Public bug reported: This is an upstream bug: https://bugreports.qt.io/browse/QTBUG-57608 ---[quote]--- As per the src; Qt assumes that all resize requests will succeed (and in turn, apparently, "proactively" resizes child windows for such requests; it's not clear if this is because of or even related to the noted issue; it may just be how Virtualbox commands Qt5 to behave in this case). This leads to very broken behavior and unusable applications where this assumption is invalid; for a library like Qt, it's never actually valid (as acknowledged by the FIXME: comment). This has most recently shown its face with the Virtualbox project, exposed by i3 and other window managers, though tiling window managers seem to make use of this protocol more than most. The Virtualbox bug report has some good details; the i3 report has good details on the compounding effects of such an issue. ---[end quote]--- The attached patch is a backport of the upstream fix. I'm also currently maintaining a PPA including this patch: https://launchpad.net/~paulo- matias/+archive/ubuntu/qt5-tiling It would be nice if the patch was included in the official Ubuntu package. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream ** Patch added: "Backport of upstream fix" https://bugs.launchpad.net/bugs/1704803/+attachment/4916192/+files/QTBUG-57608.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704803 Title: X11/XCB window resize is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1704803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697933] [NEW] package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de erro
Public bug reported: I don't know the problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] No existe el archivo o el directorio: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23' .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: Error: [Errno 2] No existe el archivo o el directorio: '/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c' ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootEFIContents: fw fwupx64.efi Date: Wed Jun 14 10:01:00 2017 EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system. ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: shim-signed Title: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697933 Title: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post- installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1697933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697281] [NEW] [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all
Public bug reported: . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 1629 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity Date: Sun Jun 11 11:37:01 2017 InstallationDate: Installed on 2015-10-24 (596 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 1629 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to xenial on 2017-05-20 (22 days ago) dmi.bios.date: 3/6/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd3/6/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: TOSHIBA NB515 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697281 Title: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1697281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694372] [NEW] partition install crashes on grub, Samsung laptop
Public bug reported: New to this installer. Booted from a USB live installer. Cant install the OS after a clean format of the HDD ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Tue May 30 01:47:14 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.3 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694372 Title: partition install crashes on grub, Samsung laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1694372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694262] [NEW] package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I don't know . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] No existe el archivo o el directorio: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23' .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: Error: [Errno 2] No existe el archivo o el directorio: '/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c' ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootEFIContents: fw fwupx64.efi Date: Mon May 29 08:31:32 2017 DuplicateSignature: package:shim-signed:1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 Setting up grub-efi-amd64-signed (1.66.9+2.02~beta2-36ubuntu3.9) ... grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory. dpkg: error processing package grub-efi-amd64-signed (--configure): subprocess installed post-installation script returned error exit status 1 EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system. ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: shim-signed Title: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694262 Title: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1694262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694259] [NEW] package grub-efi-amd64-signed 1.66.9+2.02~beta2-36ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I don't know. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-efi-amd64-signed 1.66.9+2.02~beta2-36ubuntu3.9 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Mon May 29 08:31:26 2017 DuplicateSignature: package:grub-efi-amd64-signed:1.66.9+2.02~beta2-36ubuntu3.9 Setting up grub-efi-amd64-signed (1.66.9+2.02~beta2-36ubuntu3.9) ... grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory. dpkg: error processing package grub-efi-amd64-signed (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.66.9+2.02~beta2-36ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694259 Title: package grub-efi-amd64-signed 1.66.9+2.02~beta2-36ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1694259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676963] [NEW] bug
Public bug reported: stop sound hd-intel no codec found ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-113.160-generic 3.13.11-ckt39 Uname: Linux 3.13.0-113-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 28 13:36:26 2017 DistUpgraded: 2017-03-15 19:31:45,926 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Core Processor Integrated Graphics Controller [1179:fd40] InstallationDate: Installed on 2016-03-08 (384 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite L735 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-113-generic root=UUID=1ab99c3a-74a6-46f9-ae73-d704cf89c1e3 ro vesafb.invalid=1 splash quiet nopat SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-15 (12 days ago) dmi.bios.date: 03/08/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.10:bd03/08/2011:svnTOSHIBA:pnSatelliteL735:pvrPSK73P-00QLM2:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L735 dmi.product.version: PSK73P-00QLM2 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Mar 28 13:35:20 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12884 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676963 Title: bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1676963/+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 1573959] Re: On-screen text disappears after suspend
I'm using Ubuntu 16.04 LTS $ lspci -nn | egrep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) $ uname -a Linux hostname 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux This is the first time it happens to me. I just logged out from X session and back again as @Alvaro Uría and it solves the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1573959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
Hi Andre, I also have upgraded to 16.10, hoping for the bug to be fixed, as everything seemed to go smooth until kernel 4.7. However, I still got kernel panics. In short, kernel 4.5 didn't have the bug: it was introduced by the backport Canonical made of amdgpu to 4.4. However the same bug, or a very similar one, was introduced as a regression in 4.8 (even vanilla 4.8). However I found some workaround which prevents amdgpu from loading and crashing the system. Since then I lost the interest to make a patch to fix this: it's too much work to get only the Intel GPU working (the AMD GPU would not work anyway with the open drivers). But it still would be nice if Ubuntu could ship with a kernel that doesn't crash on hardware that came with Ubuntu OEM (which, at least theoretically, should be tested by Canonical). If someone could go after this and fix the issue, it would be nice for the people who upgrade their Ubuntu OEM not to get an unusable system after reboot. The workaround I'm currently using is as follows: /etc/default/grub: Add amdgpu.runpm=0 to GRUB_CMDLINE_LINUX_DEFAULT /etc/rc.local: Add the following command: echo OFF > /sys/kernel/debug/vgaswitcheroo/switch /etc/X11/xorg.conf: Create the file if it doesn't exist, and add the following in order to get the backlight controls working (otherwise it would be misdetected): Section "Device" Identifier "Card0" Driver "intel" Option "Backlight" "intel_backlight" EndSection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643101] [NEW] installing ubuntu 16.04
Public bug reported: problem installing ubuntu 16.04 in thinkpad s230u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 Date: Fri Nov 18 21:31:16 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) ProcEnviron: LANGUAGE=es_AR.UTF-8 PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.2 ubuntu-gnome xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643101 Title: installing ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1643101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
I think they are the same. The bug manifests itself when using xorg, but the root cause is the kernel null pointer dereference. ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
Maybe we should mark it as confirmed now that Yuri bisected the kernel in the other bug? However I still think we should just put some test to check whether the pointer is NULL, we already have the stacktrace. Maybe I can try to patch it out when I get some spare time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587532] Re: Keyboard backlight turns on by itself
Hello, I´m having the same issue on my Thinkpad t460s. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587532 Title: Keyboard backlight turns on by itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1587532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
** Tags removed: kernel-fixed-upstream-4.6-rc7 ** Tags added: kernel-fixed-upstream-4.5.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
Will bisect work in this case? I had understood from the release notes that most of the 4.5-vanilla's amdgpu was backported to Ubuntu's 4.4 kernel. As I commented in the first message, 4.5.0 does not present the NULL ptr dereference, so it would not really be a bisect from 4.4 to 4.6-rc7, but from 4.4 to 4.5.0. However, would it make sense to carry this bisect since the amdgpu driver present in vanilla's 4.4 is completely different from the one shipped in Ubuntu's 4.4 kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587181] Re: snap login prompts for password but login fails
snap login expects an email as argument (not a username). So the output you get is the response from SSO complaining you didn't provide a valid email address. We need to improve that error message. If you try: $ snap login your_sso@email it should work (and request your 2FA if you have it enabled). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587181 Title: snap login prompts for password but login fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1587181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644780] Re: RTAI Patch doesn't apply over lucid's 2.6.32 kernel
No longer relevant since lucid reached EOL. I will mark this issue as Invalid. Feel free to change to Won't Fix. ** Changed in: rtai (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644780 Title: RTAI Patch doesn't apply over lucid's 2.6.32 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtai/+bug/644780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
Behavior with 4.6.0-040600rc7-generic appears to be even saner than with
4.5.0-050400, although the AMD GPU is still not usable ("DRI_PRIME=1
glxgears" opens a black window).
Only after reporting this bug, I found that 4.5.0-050400 presented
issues with sound output in the HDMI port (sound output at a lower
sampling rate, maybe half, than it was supposed to). These issues are
fixed in 4.6.0-040600rc7-generic.
Also, 4.6.0-040600rc7-generic does not present any errors in dmesg
output when trying to use the AMD GPU (again "DRI_PRIME=1 glxgears"):
---[cut]---
[ 251.019823] [drm] PCIE GART of 2048M enabled (table at 0x0004).
[ 251.258535] [drm] ring test on 0 succeeded in 15 usecs
[ 251.258748] [drm] ring test on 1 succeeded in 14 usecs
[ 251.258787] [drm] ring test on 2 succeeded in 13 usecs
[ 251.258797] [drm] ring test on 3 succeeded in 4 usecs
[ 251.258812] [drm] ring test on 4 succeeded in 2 usecs
[ 251.258818] [drm] ring test on 5 succeeded in 2 usecs
[ 251.258824] [drm] ring test on 6 succeeded in 2 usecs
[ 251.258830] [drm] ring test on 7 succeeded in 2 usecs
[ 251.258838] [drm] ring test on 8 succeeded in 3 usecs
[ 251.258865] [drm] ring test on 9 succeeded in 6 usecs
[ 251.258878] [drm] ring test on 10 succeeded in 6 usecs
---[cut]---
Whereas 4.5.0-050400 used to output the same kind of error message presented by
xenial's 4.4 kernel ("*ERROR* amdgpu: cp failed to lock ring N (-2)"), although
the NULL pointer dereference was already fixed in 4.5.0-050400.
In short, the NULL pointer dereference is fixed upstream. With upstream
kernel, the system appears to run pretty stably using the Intel GPU as
the renderer, whereas xenial's 4.4 kernel would constantly crash.
However, the AMD GPU is still not usable even with upstream kernel, as
it renders empty (black) output.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579374
Title:
amdgpu causes NULL pointer dereference when trying to use Topaz
(Radeon R7 M265) GPU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] [NEW] amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
snd_seq_device mei_me [ 131.202004] serio_raw snd_timer mei snd shpchp lpc_ich elan_i2c soundcore spi_pxa2xx_platform snd_soc_sst_acpi dw_dmac acpi_pad dw_dmac_core dell_rbtn i2c_designware_platform 8250_dw i2c_designware_core mac_hid parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_usb_sdmmc usbhid rtsx_usb amdkfd amd_iommu_v2 amdgpu crct10dif_pclmul crc32_pclmul i915 aesni_intel i2c_algo_bit ttm aes_x86_64 lrw gf128mul glue_helper ablk_helper drm_kms_helper cryptd syscopyarea r8169 sysfillrect mii psmouse sysimgblt fb_sys_fops ahci drm libahci wmi sdhci_acpi sdhci video i2c_hid hid fjes [ 131.202242] CPU: 3 PID: 189 Comm: gfx Tainted: G OE 4.4.0-22-generic #39-Ubuntu [ 131.202268] Hardware name: Dell Inc. Inspiron 5448/0YDTG3, BIOS A06 10/12/2015 [ 131.202291] task: 88024ee544c0 ti: 880035088000 task.ti: 880035088000 [ 131.202317] RIP: 0010:[] [] amdgpu_vm_grab_id+0x122/0x310 [amdgpu] [ 131.202389] RSP: 0018:88003508bce0 EFLAGS: 00010246 [ 131.202418] RAX: RBX: 88024f348000 RCX: 88024d472000 [ 131.202457] RDX: 03e803e8 RSI: 88024f34ad78 RDI: 88024b030240 [ 131.202498] RBP: 88003508bdb0 R08: 88024d472000 R09: [ 131.202533] R10: 5b25 R11: 1061 R12: 88024f34ad78 [ 131.202575] R13: 88024b030240 R14: 88024f348838 R15: 0001 [ 131.202617] FS: () GS:88025ecc() knlGS: [ 131.202664] CS: 0010 DS: ES: CR0: 80050033 [ 131.202698] CR2: 0248 CR3: 02e0a000 CR4: 003406e0 [ 131.202741] Stack: [ 131.202754] 8802506e8648 88024d472000 [ 131.202804] [ 131.202855] [ 131.202905] Call Trace: [ 131.202942] [] amdgpu_ib_schedule+0x90/0x390 [amdgpu] [ 131.203004] [] amdgpu_sched_run_job+0x36/0x140 [amdgpu] [ 131.203065] [] amd_sched_main+0x23f/0x400 [amdgpu] [ 131.203107] [] ? wake_atomic_t_function+0x60/0x60 [ 131.203163] [] ? amd_sched_entity_wakeup+0x70/0x70 [amdgpu] [ 131.203207] [] kthread+0xd8/0xf0 [ 131.203238] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 131.203278] [] ret_from_fork+0x3f/0x70 [ 131.203311] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 131.203350] Code: c0 44 89 bc 85 48 ff ff ff 41 83 c7 01 44 39 bb 1c 09 00 00 76 4f 49 83 c6 10 4d 8b 6e f0 4d 85 ed 74 66 4c 89 ef e8 fe 2e ff ff <8b> b8 48 02 00 00 48 8b b4 fd 50 ff ff ff 48 85 f6 74 b2 41 8b [ 131.203558] RIP [] amdgpu_vm_grab_id+0x122/0x310 [amdgpu] [ 131.203628] RSP [ 131.203645] CR2: 0248 [ 131.208801] ---[ end trace 8aa5d3e55e43b8c1 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matias 2141 F pulseaudio /dev/snd/controlC0: matias 2141 F pulseaudio CurrentDesktop: i3 Date: Sat May 7 10:56:56 2016 HibernationDevice: RESUME=UUID=60147c89-0820-48f0-9b56-033547cfbae8 InstallationDate: Installed on 2015-08-12 (268 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5448 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-26 (11 days ago) 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: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5448:pvrA06:rvnDellInc.:rn0YDTG3:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5448 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503589] [NEW] Unable to display Quick Energy Spectrum Plot (Graph is empty)
Public bug reported: While using DS9 to inspect X ray images, upon selecting a region to study and requiring to plot "Quick Energy Spectrum" for the region using Chandra-Ed analysis tools, the pop-up window plots an blank Graph. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: saods9 7.3.2+repack-1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Wed Oct 7 18:55:09 2015 InstallationDate: Installed on 2015-07-02 (97 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: saods9 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: saods9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503589 Title: Unable to display Quick Energy Spectrum Plot (Graph is empty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1503589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433411] Re: openafs-modules-dkms 1.6.7-1ubuntu1: openafs kernel module failed to build
Same here. Any news, workaround? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433411 Title: openafs-modules-dkms 1.6.7-1ubuntu1: openafs kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1433411/+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 1480495] Re: package shim-signed 1.9+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Yes, I have it. This file appeared when I tried to install a PSX emulator, specifically PCSX -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480495 Title: package shim-signed 1.9+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1480495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480495] Re: package shim-signed 1.9+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
/usr/sbin/grub-install (which grub-install) grub2-common: Installed: 2.02~beta2-9ubuntu1.3 Candidate: 2.02~beta2-9ubuntu1.3 Version table: *** 2.02~beta2-9ubuntu1.3 0 500 http://cl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.02~beta2-9 0 500 http://cl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages (apt-cache policy grub2-common) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480495 Title: package shim-signed 1.9+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1480495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480495] [NEW] package shim-signed 1.9+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Everytime I update Ubuntu, there's an error message. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: shim-signed 1.9+0.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Thu Jul 30 23:58:12 2015 DuplicateSignature: package:shim-signed:1.9+0.8-0ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-20 (72 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: shim-signed Title: package shim-signed 1.9+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480495 Title: package shim-signed 1.9+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1480495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
