Re: [Bug 2076308] [NEW] Allow requesting not running update-ca-certificates during install
From a correctness point of view it feels like a job for equivs to install a stub package instead - after all the data is provided externally. But I can see how we don't have good tooling for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076308 Title: Allow requesting not running update-ca-certificates during install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2076308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
I can confirm #52: Works fine for me on DisplayPort, broken on HDMI. My system is described in #21. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068834] [NEW] package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1
Public bug reported: ugprade from 23.10 to 24.04 on raspberry pi 5 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: plymouth 24.004.60-1ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-1018.21-raspi 6.5.13 Uname: Linux 6.5.0-1018-raspi aarch64 ApportVersion: 2.28.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: CloudSubPlatform: config-disk (/dev/sda1) Date: Sun Jun 9 13:33:22 2024 ErrorMessage: installed plymouth package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20230807.2 Lspci-vt: -[:00]---00.0-[01]00.0 Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/2p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/2p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ProcCmdLine: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=D8:3A:DD:C8:20:56 vc_mem.mem_base=0x3fc0 vc_mem.mem_size=0x4000 console=ttyAMA10,115200 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mapper/rootfs rootfstype=ext4 rootwait fixrtc quiet splash cryptdevice=/dev/sda2 ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=D8:3A:DD:C8:20:56 vc_mem.mem_base=0x3fc0 vc_mem.mem_size=0x4000 console=ttyAMA10,115200 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mapper/rootfs rootfstype=ext4 rootwait fixrtc quiet splash cryptdevice=/dev/sda2 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-06-09 (0 days ago) acpidump: ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image cloud-image noble raspi-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068834 Title: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2068834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067712] Re: NETDEV WATCHDOG: eno12399np0 (bnxt_en): transmit queue 4 timed out
Also affects jammy with HWE Kernel version 6.5.0-35-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067712 Title: NETDEV WATCHDOG: eno12399np0 (bnxt_en): transmit queue 4 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064791] [NEW] apparmor prevents kea launch
Public bug reported:
Dear Sir or Madam,
during installation of kea-2.4 (kea-dhcp4, kea-dhcp6 and kea-ctrl-agent)
some profiles for apparmor are installed/created as well.
Unfortunately these profiles prevent kea services to start when for example
MySQL as backend is configured.
Config snippet from kea-dhcp4.conf:
"hosts-database": {
"type": "mysql",
"name": "kea",
"user": "kea",
"password": "password",
"host": "",
"port": 3306
},
Error message from kea-dhcp4-server:
ERROR [kea-dhcp4.dhcp4.125444634970560] DHCP4_CONFIG_LOAD_FAIL configuration
error using file: /etc/kea/kea-dhcp4.conf, reason: Unable to open database:
Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (13)
ERROR [kea-dhcp4.dhcp4.125444634970560] DHCP4_INIT_FAIL failed to initialize
Kea server: configuration error using file '/etc/kea/kea-dhcp4.conf': Unable to
open database: Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (13)
Message from dmesg:
[ 685.201719] audit: type=1400 audit(1714811351.219:113): apparmor="DENIED"
operation="connect" class="file" info="Failed name lookup - disconnected path"
error=-13 profile="kea-dhcp4" name="run/mysqld/mysqld.sock" pid=2887
comm="kea-dhcp4" requested_mask="wr" denied_mask="wr" fsuid=111 ouid=110
As you can see, kea can't connect to mysql through the socket, since
apparmor is preventing it.
There is a similar issue with using the kea-ctrl-agent with the other
services.
In your installed apparmor profiles you specifically allow the socket
/run/kea/kea4-ctrl-socket
profile snippet:
# Control sockets
# Before LP: #1863100, these were in /tmp. For compatibility, let's keep both
# locations
owner /{tmp,run/kea}/kea4-ctrl-socket w,
owner /{tmp,run/kea}/kea4-ctrl-socket.lock rwk,
Naming it anything else prevents the server to start as well.
It's really time-consuming and nerve racking to debug this, since the
issue with apparmor is not directly apparently.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: kea-dhcp4-server 2.4.1-3build3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat May 4 10:33:20 2024
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: isc-kea
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.kea.kea-dhcp4.conf: [modified]
mtime.conffile..etc.kea.kea-dhcp4.conf: 2024-05-04T10:28:43.848349
** Affects: isc-kea (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064791
Title:
apparmor prevents kea launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/2064791/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
Tested with 22.02.0-2ubuntu0.4 and working fine. Thanks! ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059739] Re: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs
Thanks you for the quick response. Update-initramfs works without errors or warnings and dropbear correctly starts in the initial ramdisk environment created after applying 0001-Copy-only-dhcpcd-user-into-initramfs-etc-passwd.patch. I can not really say anything about the dhcpd functionality though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059739 Title: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059739] [NEW] initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs
Public bug reported: Recent changes to the dhcpd hook shipped with dhcpdinitramfs-tools 0.142ubuntu23 (noble-dev) copy the host /etc/passwd into the initramfs-image: https://git.launchpad.net/ubuntu/+source/initramfs-tools/commit/hooks/dhcpcd?h=applied/ubuntu/noble&id=73c865b9d234087d977d7baa20852639746567fd This has multiple problems: * The passwd file is copied without checking if the dhcpcd user actually exists (which is created by dhcpcd package, but only dhcpcd-base is installed via dependencies) * The change breaks dropbear-initramfs because the passwd file contains a root user with a non existing home directory * leaking user information into initramfs (which may or may not be a problem on fully encrypted systems) ** Affects: initramfs-tools (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/2059739 Title: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers
Done, thank you! https://lists.ubuntu.com/archives/ubuntu- doc/2024-March/020906.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056591 Title: [UIFe] Noble Flavor Wallpapers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/2056591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056591] [NEW] [UIFe] Noble Flavor Wallpapers
Public bug reported: I am requesting a blanket UI Freeze exception for all flavor wallpaper packages in advance of the upcoming UI Freeze for a period of 5 days after it starts. The Noble wallpapers for vanilla Ubuntu will be available on March 18th, which only gives flavors 2 days to create their customized wallpapers. This is a very tight deadline, and we'd like to avoid putting the burden on flavors to request individual UIFe's or forcing them to rush update their wallpaper to make the deadline. I'd appreciate your support on granting this exception. ** Affects: ubuntu-wallpapers (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/2056591 Title: [UIFe] Noble Flavor Wallpapers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/2056591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971093] Re: collectd missing in 22.04/jammy
I have tried out the packages from Jammy proposed, and they work fine here (Ubuntu 22.04, many collectd plugins active, forwarding to a Graphite server). Debian sid also has collectd 5.12.0-9 with the exact same changelog as the Ubuntu package (https://metadata.ftp- master.debian.org/changelogs//main/c/collectd/collectd_5.12.0-9_changelog) with no recent bugs in their tracker. So there does not seem to be a reason why Ubuntu should not ship that package. Anway, if a package is shipped and later removed from the package repository for whatever reason, I would expect to be able to find the reason for this somewhere, e.g., here in the bug tracker. But I could not find any mention of this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971093 Title: collectd missing in 22.04/jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972051] Re: After upgrade to 22.04, screenshot shortcuts are re-enabled and cannot be disabled
** Description changed: I’ve upgraded from Ubuntu 21.10 to 22.04 using do-release-upgrade. After the upgrade, I found that the screenshot shortcuts in Settings > Keyboard > View and Customize Shortcuts > Screenshots were all enabled even though I had previously disabled them. I don’t expect an OS upgrade to undo settings I explicitly made. It also doesn’t seem possible to disable these shortcuts. I’ve disabled all of them, yet pressing “Print” (for example) still invokes the new screenshot utility that was introduced in 22.04. This is especially problematic because I have set-up custom screenshot shortcuts to use Flameshot. These shortcuts don’t work anymore even though they’re still shown in the Custom Shortcuts section. Specifically, Print, Alt+Print, and Ctrl+Print are all hijacked by the new screenshot utility with no way to prevent that. + Now, what actually happens is that no matter what’s set-up for these + shortcuts, pressing Print (for example) always shows the new screenshot + utility. After that, one can press Share which then seems to pass the + screenshotted area onto Flameshot? This is a superbly weird interaction + and I don’t want it. + (Note that it was not possible for me to identify the package responsible for this because "ubuntu-bug -w" doesn’t seem to work on my system because of something related to Wayland.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972051 Title: After upgrade to 22.04, screenshot shortcuts are re-enabled and cannot be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972051] Re: After upgrade to 22.04, screenshot shortcuts are re-enabled and cannot be disabled
** Also affects: gnome-control-center (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/1972051 Title: After upgrade to 22.04, screenshot shortcuts are re-enabled and cannot be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972051] [NEW] After upgrade to 22.04, screenshot shortcuts are re-enabled and cannot be disabled
Public bug reported: I’ve upgraded from Ubuntu 21.10 to 22.04 using do-release-upgrade. After the upgrade, I found that the screenshot shortcuts in Settings > Keyboard > View and Customize Shortcuts > Screenshots were all enabled even though I had previously disabled them. I don’t expect an OS upgrade to undo settings I explicitly made. It also doesn’t seem possible to disable these shortcuts. I’ve disabled all of them, yet pressing “Print” (for example) still invokes the new screenshot utility that was introduced in 22.04. This is especially problematic because I have set-up custom screenshot shortcuts to use Flameshot. These shortcuts don’t work anymore even though they’re still shown in the Custom Shortcuts section. Specifically, Print, Alt+Print, and Ctrl+Print are all hijacked by the new screenshot utility with no way to prevent that. (Note that it was not possible for me to identify the package responsible for this because "ubuntu-bug -w" doesn’t seem to work on my system because of something related to Wayland.) ** Affects: 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/1972051 Title: After upgrade to 22.04, screenshot shortcuts are re-enabled and cannot be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572074]
Comment on attachment 8642998 middlemouse on new tab button creates a new tab related to current Sounds like a sensible shortcut if I understand this correctly: So with this patch, middle-clicking the new tab button in the tab strip will create a new tab next to the currently selected tab instead of at the end of the tab strip, correct? If so, go for it! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572074 Title: New tabs open to the right of all existing tabs instead of opening next to the current tab To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/572074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
I have now tested whether the issue is still resolved and it luckily is. So both after installing a version of amdgpu-pro and also after uninstalling this proprietary driver again, unlocking the system works again. Once the stable version of Ubuntu 22.04 is published, I will upgrade and try again. At this point, I don’t want to try a pre-release version to avoid having my only personal computer become inoperable. Also, I have yet to find a way to restore the resolution during the boot process. Specifically, the default resolution is used during the cryptsetup decryption stage and before (when only the mainboard manufacturer logo is shown). The BIOS configuration seems to be in order and is set to use the primary PCIe slot to which my monitor is connected. It’s not terrible that this is so, but I’d like to fix it. My internet searches have been unsuccessful though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
Yes, I believe having installed a proprietary driver could’ve caused this. I didn’t realize this at the time of installing the driver, but I think the file name "amdgpu-pro-21.20-1271047-ubuntu-20.04" clearly indicates that this is in fact AMD’s proprietary driver. Curiously, the issue didn’t happen immediately after installing this driver and rebooting. I used the computer for at least two sessions after this and everything was seemingly fine. In any case, things are mostly in order now. I have yet to test if my initially reported issue of locking the computer crashing the driver is still resolved. I will get back with an updated report on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
After the things I did in https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.13/+bug/1964711/comments/7, I am now facing a worse problem. My computer no longer recognizes my display correctly. Since the boot screen, the resolution is the minimum available (1024x768). I think my system no longer selects the correct driver for my graphics card. Running "sudo lshw -c video" yields the following: ``` *-display UNCLAIMED description: VGA compatible controller product: Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:03:00.0 version: ca width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:4000-4fff memory:5000-501f ioport:3000(size=256) memory:5030-5037 memory:c-d ``` Running "lsmod | grep amd" prints nothing (it used to before) and "dkms status amdgpu" also prints nothing. I tried uninstalling the drivers I installed and also tried installing drivers from different source. I tried to look for issues in my BIOS settings. All to no avail. If I don’t find a solution to this, I will resort to completely re-installing Ubuntu 20.04. I have luckily completed a full backup before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
I’ve done the following things now: Unsuccessful: Upgrade from Ubuntu 20.04 to 21.04. This did not solve the issue. Successful: Manually uninstall and install the latest amdgpu package from https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified- linux-21-20. Specifically, I downloaded amdgpu- pro-21.20-1271047-ubuntu-20.04.tar.xz and installed it via the amdgpu- install binary. This seems to have solved the issue. I reckon there is a good chance that it was rather uninstalling and reinstalling the driver than installing a specific version of it, but that I can’t tell with certainty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964711] Re: Locked Ubuntu is frozen and cannot be unlocked
Around 8 this morning (that’s an hour ago from me writing this), I started my computer and logged in. I then locked the computer without starting any programs manually. After returning now (an hour later), the same issue can be observed. I shut down the computer manually (by pressing down the power button), started the computer again and produced the prevboot.txt file as instructed. The /var/crash directory has no files for this time frame. ** Attachment added: "Result of “journalctl -b-1”" https://bugs.launchpad.net/ubuntu/+bug/1964711/+attachment/5569949/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: Locked Ubuntu is frozen and cannot be unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1964711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964711] [NEW] Locked Ubuntu is frozen and cannot be unlocked
Public bug reported: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description:Ubuntu 20.04.4 LTS Release:20.04 ** Affects: 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/1964711 Title: Locked Ubuntu is frozen and cannot be unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1964711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
This is a kernel regression and now almost three months old. Could somebody please have a look? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
I'm having a very similar issue. With 21.10 I noticed that the issue goes away, when I change the scale to 100% (instead of 200%) on the secondary screen. Main Screen (USB-C): 3440x1440, 100% Secondary Screen (Built-In): 3840x2160: 200% I'm having the issue with or without extensions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253205] Re: logging of error in opening file
** Changed in: apt-cacher-ng (Ubuntu) Status: Incomplete => 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/1253205 Title: logging of error in opening file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1253205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567565] Re: Permission error saving a file
This problem persists with recent versions of Ubuntu and Evince when editing files on CIFS/SMB shares, even after disabling AppArmor. The reason for this is that Evince attempts to move the temporary file over the original PDF while it still has the latter file open, and overwriting open files is not supported by SMB: https://lists.samba.org/archive/samba/2021-November/238366.html https://lists.samba.org/archive/samba/2021-November/238367.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567565 Title: Permission error saving a file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1567565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949299] Re: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy)
There is also a bug report in debian for this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994944 ** Bug watch added: Debian Bug tracker #994944 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994944 ** Also affects: gtk4 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994944 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/1949299 Title: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1949299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949299] [NEW] gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy)
Public bug reported: The binary (gtk4-broadwayd) and also the devel files for gtk4 broadway are missing in the 4.4 packages for impish and jammy. They are in the hirsute package (4.0) though. For example this would be needed for Cambalache: WARNING:cambalache.cmb_view gtk4-broadwayd not found, Gtk 4 workspace wont work. ** Affects: gtk4 (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/1949299 Title: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1949299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
Status set to "Confirmed" as requested by the bot after uploading logs (although I did upload them when creating the issue as well...). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534266/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534267/+files/WifiSyslog.txt ** 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534265/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534264/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534263/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534262/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534261/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534260/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534259/+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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
apport information ** Tags added: apport-collected ** Description changed: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 19 04:42 seq + crw-rw 1 root audio 116, 33 Oct 19 04:42 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' + CasperMD5CheckResult: skip
[Bug 1947718] [NEW] overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
Public bug reported: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU ** Affects: linux (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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909087] Re: My USB UPS works incorrectly. it appears and disappears in system
** Changed in: libusb-1.0 (Ubuntu) Status: New => Confirmed ** Changed in: libusb-1.0 (Ubuntu) Assignee: (unassigned) => Philipp (philipp1981) ** Changed in: libusb-1.0 (Ubuntu) Status: Confirmed => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/libusb-1.0/+question/698862 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909087 Title: My USB UPS works incorrectly. it appears and disappears in system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1909087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903995] Re: upower report wrong battery percentage for Logitech Unify devices
> I believe that this should be fixed by this upstream commit, which will be in the 5.12 kernel Has anyone been able to verify that? If it indeed fixes this annoying issue (I get notifications about low mouse battery all the time even though it's almost full), then it might be worth back-porting to older kernels (?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903995 Title: upower report wrong battery percentage for Logitech Unify devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1903995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930594] [NEW] Nautilus needs very long to open (1+ minute)
Public bug reported: 1.) lsb_release -rd: Description:Ubuntu 20.04.2 LTS Release:20.04 2.) apt-cache policy nautilus: nautilus: Installiert: 1:3.36.3-0ubuntu1 Installationskandidat: 1:3.36.3-0ubuntu1 Versionstabelle: *** 1:3.36.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3.) What you expected to happen: I expected that when I press "Files" or type in "nautilus" in the terminal, that Nautilus shows up within a few seconds. 4.) What happend instead: It took about 1 minute until nautilus showed up. If i close it, it takes another minute to show up again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 2 16:07:05 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1072, 550)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-05-10 (23 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (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/1930594 Title: Nautilus needs very long to open (1+ minute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1930594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930090] [NEW] Sometimes doubleclick to open folders is not working
Public bug reported: I'm using Ubuntu 20.04 (64 bit, Desktop) and sometimes the doubleclick to open folders is not working correctly. Its not the mouse, cause I use the same mouse on a windows pc and it works without any problems. Its also not the doubleclick speed, I'm very sure about that, even if i can't prove. But I'm using a PC for over 20 years and never got that problem in the past 10 years, only with Ubuntu. So I think there's something wrong, cause its very annyoing if you have to work and go through many different folders and then every 5. - 10. folder that problem occurs. I posted this question in a ubuntu users forum and others said that they have that problem, too. ** Affects: nautilus (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/1930090 Title: Sometimes doubleclick to open folders is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1930090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910521] Re: libappindicator breaks left-mouse actions for most applications
> doesn't happen on xubuntu with the indicator But it does happen on Ubuntu. > The priority is low for Ubuntu since there is no report of such problems on Ubuntu Here comes that report. To reproduce: 1. Download the latest Ubuntu (21.04, live stick is enough). 2. Download and open Joplin (https://github.com/laurent22/joplin/releases/download/v1.7.11/Joplin-1.7.11.AppImage), which is an app that uses Electron and therefore libappindicator. 3. In the Options under Application enable "Show tray icon", which should show up at the top right of the screen. 4. Left-click on the icon. Observe how the context menu opens, just like with a right click, even though the application should open the main window instead (https://github.com/laurent22/joplin/blob/80b16dd17e227e3f538aa221d7b6cc2d81688e72/packages/app-desktop/ElectronAppWrapper.ts#L297-L299), and indeed it does so under Windows for example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910521 Title: libappindicator breaks left-mouse actions for most applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1910521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924846] Re: [550-254ng, Nvidia GPU 60 HDMI/DP, Digital Out, DisplayPort] Crackling sound during quiet parts of video, with DisplayPort only
On a different machine (no Nvidia) but with the same monitor, I can also reproduce this over DisplayPort but not over HDMI. So I don't think that the Nvidia graphics card/driver is to blame. Instead, it seems like there's a general DisplayPort-related issue either in Linux/Alsa or in my cable/monitor (but if so, then Windows has a workaround for that issue, which could hopefully be implemented in Linux/Alsa too). Either way, it seems like this is something for the Alsa team to debug, and I'm happy to provide more information or run more experiments/tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924846 Title: [550-254ng, Nvidia GPU 60 HDMI/DP, Digital Out, DisplayPort] Crackling sound during quiet parts of video, with DisplayPort only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1924846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890406] Re: tmux sessions don't show up with who, users, ...
Thank you very much! I downloaded and installed https://launchpad.net/ubuntu/+source/tmux/3 .0a-2ubuntu0.3/+build/21444364/+files/tmux_3.0a-2ubuntu0.3_amd64.deb and it works fine. Tmux sessions get shown by `who` as before with `(tmux(3431814).%0)`. `users` also works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890406 Title: tmux sessions don't show up with who, users, ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1890406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924846] [NEW] [550-254ng, Nvidia GPU 60 HDMI/DP, Digital Out, DisplayPort] Crackling sound during quiet parts of video, with DisplayPort only
Public bug reported: When I play YouTube videos, then in the quiet parts of the video (i.e. in pauses between sentences, even if they are very brief), I hear a popping/crackling sound on my headphones connected through my DisplayPort monitor and my Nvidia GeForce GTX 745 card (I have this PC: https://www.notebooksbilliger.de/hp+pavilion+550+254ng+intel+core+i5+6400 and an Asus PB248Q monitor). Depending on the video and how many pauses the speakers make, this is very annoying. I've run a long series of experiments, see https://forums.linuxmint.com/viewtopic.php?f=48&t=347176 for details. In summary, I can reproduce this: - With any installed Linux OSes (Ubuntu or Mint) or with live sticks (tried Ubuntu, Mint, PopOS and Manjaro). - With the open-source driver (Nouveau) or with various versions of the Nvidia driver. - With Chrome or Firefox or even an Audacity recording (from the DisplayPort output's audio monitor in PulseAudio) of the same audio stream. - Even when I try the usual fixes like tsched=0, disabling module-suspend-on-idle, disabling /sys/module/snd_hda_intel/parameters/power_save or position_fix=1 or =2. - Even when I don't use PulseAudio, but use `apulse ffplay ...` to play a file directly to ALSA. - NOT on Windows. Any browser and any video/sound file works fine on Windows with exactly the same hardware. - NOT with HDMI. The same card/monitor/headphones connected over HDMI (aka. "HDMI / DisplayPort 3" aka. "hdmi-stereo-extra2" aka. device number 8 aka. "HDMI 2") works fine. Only over DisplayPort (aka. "HDMI / DisplayPort 4" aka. "hdmi-stereo-extra3" aka. device number 9 aka. "HDMI 3") it crackles. - NOT when I save the problematic Audacity recording as a wav/mp3 file (and play it in any media player or with `apulse aplay ...`) or when I convert it to 16-Bit PCM in Audacity (and back to 32-bit float). My suspicion is that this somehow gets rid of the pauses / quiet parts by writing sth like zeros in there. - NOT when I have some other continuous audio running at the same time, e.g. if I turn on some radio in Rhythmbox and play the problematic video at the same time, there's no crackles. Again my suspicion is that this gets rid of the quiet parts -- not in the video, but in the mixed stream sent to the audio device. This bug report is produced from `ubuntu-bug audio` on a freshly created Ubuntu LTS live USB stick with all default values, where I've just reconfirmed that DisplayPort is broken and HDMI works. Thanks for your help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 5070 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 5070 F...m pulseaudio /dev/snd/controlC1: ubuntu 5070 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 17 11:25:05 2021 LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia successful Symptom_Card: GM107 High Definition Audio Controller [GeForce 940MX] - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [550-254ng, Nvidia GPU 60 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2018 dmi.bios.release: 5.11 dmi.bios.vendor: AMI dmi.bios.version: A0.20 dmi.board.asset.tag: CZC6057CYQ dmi.board.name: 2B47 dmi.board.vendor: HP dmi.board.version: 1.04 dmi.chassis.asset.tag: CZC6057CYQ dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrA0.20:bd01/18/2018:br5.11:svnHP:pn550-254ng:pvr1.04:rvnHP:rn2B47:rvr1.04:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 550-254ng dmi.product.sku: V2F29EA#ABD dmi.product.version: 1.04 dmi.sys.vendor: HP ** Affects: alsa-driver (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/1924846 Title: [550-254ng, Nvidia GPU 60 HDMI/DP, Digital Out, DisplayPort] Crackling sound during quiet parts of video, with DisplayPort only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1924846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.
[Bug 1890406] Re: tmux sessions don't show up with who, users, ...
We also experience this bug on Focal. It is a real issue for us because unattended-upgrades relies on the `users` command to determine logged-in users. This means that on Focal, unattended-upgrades reboots forcefully and kills running tmux sessions even if instructed not to with `Unattended-Upgrade::Automatic-Reboot-WithUsers "false";` in the apt config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890406 Title: tmux sessions don't show up with who, users, ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1890406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Thanks! >> I noticed that in the list of affected packages in the bug metadata >> Bionic is not mentioned. Will the fix also be backported there? > > It depends on which kernel you are talking about. The bionic GA kernel > (4.15) was not affected based on my testing. If you are seeing problems > with it, please let me know. 4.15 was not affected indeed. > The bionic HWE kernel is derived from the kernel source in focal, so > that kernel does not need to be fixed separately from the focal kernel. Ok, just wanted to make sure this is the case. Everything is fine for me now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Thanks! I tested it on a Focal machine and the -proposed kernel works. However, I don't have a Groovy machine here, is it necessary for me to test this? I noticed that in the list of affected packages in the bug metadata Bionic is not mentioned. Will the fix also be backported there? ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909087] [NEW] My USB UPS works incorrectly. it appears and disappears in system
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 [ 2951.843390] usb 1-1.2: new low-speed USB device number 78 using ehci-pci [ 2951.960420] usb 1-1.2: New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02 [ 2951.960427] usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 2951.960430] usb 1-1.2: Product: HID UPS Battery [ 2951.960433] usb 1-1.2: Manufacturer: POWERCOM Co.,LTD [ 2951.960436] usb 1-1.2: SerialNumber: 004-0D9F-000 [ 2952.006860] hid-generic 0003:0D9F:0004.01C7: hiddev0,hidraw2: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-:00:1a.0-1.2/input0 [ 2955.716788] usb 1-1.2: USB disconnect, device number 78 [ 2958.499506] usb 1-1.2: new low-speed USB device number 79 using ehci-pci [ 2958.616917] usb 1-1.2: New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02 [ 2958.616924] usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 2958.616927] usb 1-1.2: Product: HID UPS Battery [ 2958.616930] usb 1-1.2: Manufacturer: POWERCOM Co.,LTD [ 2958.616933] usb 1-1.2: SerialNumber: 004-0D9F-000 [ 2958.666897] hid-generic 0003:0D9F:0004.01C8: hiddev0,hidraw2: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-:00:1a.0-1.2/input0 [ 2962.372449] usb 1-1.2: USB disconnect, device number 79 . . . . repeats continuously On older ubuntu this UPS works fine This problem is repeated on a purely installed ubuntu 20.04 desktop or server on another computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libusb-1.0-0 2:1.0.23-2build1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 23 12:53:48 2020 InstallationDate: Installed on 2013-11-27 (2583 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: libusb-1.0 UpgradeStatus: Upgraded to focal on 2020-11-19 (33 days ago) ** Affects: libusb-1.0 (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/1909087 Title: My USB UPS works incorrectly. it appears and disappears in system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1909087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906985] [NEW] onioncircuits crahes on start due to "NameError: name 'pkg_resources' is not defined"
Public bug reported: The complete console output: ``` > onioncircuits Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pycountry/__init__.py", line 10, in import pkg_resources File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3257, in def _initialize_master_working_set(): File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3240, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3269, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573, in _build_master ws = cls() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 566, in __init__ self.add_entry(entry) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 622, in add_entry for dist in find_distributions(entry, True): File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2075, in find_on_path for dist in factory(fullpath): File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2140, in distributions_from_metadata if len(os.listdir(path)) == 0: PermissionError: [Errno 13] Permission denied: '/usr/local/lib/python3.8/dist-packages/wrapt-1.12.1.dist-info' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/onioncircuits", line 25, in import pycountry File "/usr/lib/python3/dist-packages/pycountry/__init__.py", line 13, in except (ImportError, pkg_resources.DistributionNotFound): NameError: name 'pkg_resources' is not defined Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 72, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 32, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 26, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 36, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table Original exception was: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pycountry/__init__.py", line 10, in import pkg_resources File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3257, in def _initialize_master_working_set(): File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3240, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3269, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573, in _build_master ws = cls() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 566, in __init__ self.add_entry(entry) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 622, in add_entry for dist in find_distributions(entry, True): File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2075, in find_on_path for dist in factory(fullpath): File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2140, in distributions_from_metadata if len(os.listdir(path)) == 0: PermissionError: [Errno 13] Permission denied: '/usr/local/lib/python3.8/dist-packages/wrapt-1.12.1.dist-info' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/onioncircuits", line 25, in import pycountry File "/usr/lib/python3/dist-packages/pycountry/__init__.py", line 13, in except (ImportError, pkg_resources.DistributionNotFound): NameError: name 'pkg_resources' is not defined ``` Starting with `sudo` doesn't help. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: onioncircuits 0.6-3 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 17:36:24 2020 InstallationDate: Installed on 2020-10-02 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: onioncircuits UpgradeStatus: Upgraded to groovy on 2020-11-22 (13 days ago) ** Affects: onioncircuits (Ubuntu)
[Bug 1906112] [NEW] rtl8812au causes kernel error when connecting TP-Link T4UH
Public bug reported: After connecting the WiFi USB adapter `sudo dmesg` shows ``` [ 1521.747860] usb 1-1.1: USB disconnect, device number 3 [ 1523.968354] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 1524.047189] usb 1-1.1: New USB device found, idVendor=2357, idProduct=0101, bcdDevice= 0.00 [ 1524.047194] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1524.047197] usb 1-1.1: Product: 802.11n NIC [ 1524.047199] usb 1-1.1: Manufacturer: Realtek [ 1524.047200] usb 1-1.1: SerialNumber: 123456 [ 1524.047711] [ cut here ] [ 1524.047766] WARNING: CPU: 1 PID: 11611 at net/wireless/core.c:890 wiphy_register+0x587/0x7f0 [cfg80211] [ 1524.047767] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink br_netfilter bridge stp llc rfcomm ccm algif_aead des_generic libdes arc4 md4 aufs cmac algif_hash algif_skcipher af_alg bnep overlay cachefiles fscache bbswitch(OE) binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio zfs(PO) zunicode(PO) zavl(PO) icp(PO) intel_rapl_msr nls_iso8859_1 mei_hdcp zcommon(PO) znvpair(PO) spl(O) zlua(PO) snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core intel_rapl_common x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul ghash_clmulni_intel snd_pcm aesni_intel crypto_simd cryptd glue_helper rapl snd_seq_midi intel_cstate snd_seq_midi_event input_leds uvcvideo 8812au(OE) snd_rawmidi btusb iwldvm videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 serio_raw [ 1524.047851] mac80211 rtsx_usb_ms videobuf2_common btrtl at24 efi_pstore snd_seq videodev memstick btbcm libarc4 btintel mc joydev snd_seq_device snd_timer bluetooth i915 iwlwifi snd ecdh_generic cfg80211 ecc hid_multitouch drm_kms_helper cec rc_core i2c_algo_bit soundcore fb_sys_fops mei_me syscopyarea sysfillrect mei sysimgblt ideapad_laptop sparse_keymap wmi mac_hid sch_fq_codel pkcs8_key_parser parport_pc ppdev lp parport drm ip_tables x_tables autofs4 rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid crc32_pclmul i2c_i801 psmouse ahci r8169 xhci_pci lpc_ich libahci i2c_smbus realtek xhci_pci_renesas video [last unloaded: nvidia] [ 1524.047941] CPU: 1 PID: 11611 Comm: kworker/1:3 Tainted: PW OE 5.8.0-29-lowlatency #31-Ubuntu [ 1524.047943] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21) 07/12/2013 [ 1524.047953] Workqueue: usb_hub_wq hub_event [ 1524.047993] RIP: 0010:wiphy_register+0x587/0x7f0 [cfg80211] [ 1524.047998] Code: 0b 66 41 89 54 24 30 e9 a7 fd ff ff 80 7a 1e 00 74 30 0f 0b b8 ea ff ff ff e9 0f fd ff ff 0f 0b b8 ea ff ff ff e9 03 fd ff ff <0f> 0b b8 ea ff ff ff e9 f7 fc ff ff 0f 0b b8 ea ff ff ff e9 eb fc [ 1524.048001] RSP: 0018:be8e25c47710 EFLAGS: 00010246 [ 1524.048004] RAX: c0b6a0f0 RBX: 9cda0ea0bae0 RCX: c0b6a0e0 [ 1524.048007] RDX: c0b6a180 RSI: 0025 RDI: 001e [ 1524.048009] RBP: be8e25c47780 R08: 0004 R09: 0003 [ 1524.048011] R10: R11: R12: 9cda0ea0bae0 [ 1524.048013] R13: 9cd9b9f83000 R14: 9cda0ee7f830 R15: 9cda0ee7f830 [ 1524.048017] FS: () GS:9cdaaf24() knlGS: [ 1524.048019] CS: 0010 DS: ES: CR0: 80050033 [ 1524.048022] CR2: 2789d76eef40 CR3: 00017020a003 CR4: 001606e0 [ 1524.048024] Call Trace: [ 1524.048086] ? _rtw_malloc+0x2d/0x2f [8812au] [ 1524.048137] ? _rtw_memcpy+0x10/0x12 [8812au] [ 1524.048194] ? rtw_5g_rates_init+0x1a/0x1c [8812au] [ 1524.048251] ? rtw_spt_band_alloc+0xb0/0xb2 [8812au] [ 1524.048306] rtw_wdev_alloc+0xf6/0x29c [8812au] [ 1524.048364] rtw_usb_if1_init+0xf0/0x20c [8812au] [ 1524.048446] rtw_drv_init+0x24b/0x2d7 [8812au] [ 1524.048461] usb_probe_interface+0xf1/0x2b0 [ 1524.048473] really_probe+0x2f4/0x430 [ 1524.048482] driver_probe_device+0xe9/0x160 [ 1524.048492] __device_attach_driver+0x71/0xd0 [ 1524.048500] ? driver_allows_async_probing+0x50/0x50 [ 1524.048510] bus_for_each_drv+0x84/0xd0 [ 1524.048518] __device_attach+0xde/0x1e0 [ 1524.048526] device_initial_probe+0x13/0x20 [ 1524.048532] bus_probe_device+0x8f/0xa0 [ 1524.048538] device_add+0x3ad/0x6a0 [ 1524.048544] usb_set_configuration+0x48e/0x850 [ 1524.048554] usb_generic_driver_probe+0x53/0x70 [ 1524.048559] usb_probe_device+0x3e/0x100 [ 1524.048564] really_probe+0x2f4/0x430 [ 1524.048569] driver_probe_device+0xe9/0x160 [ 1524.048574] __device_attach_driver+0x71/0xd0 [ 1524.048579] ? driver_allows_async_probing+0x50/0x50 [ 1524.048584] bus_for_each_drv+0x84/0xd0 [ 1524.048590] __device_attach+0xde/0x1e0 [ 1524.048594] device_initial_probe+0x13/0x20 [ 1524.048598] bus_probe_device+0x8f/0xa0 [ 1524.048604] device_add+0x3ad/0x6a0 [ 1524.04
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
I noticed that the changelog of the kernel package 5.4.0-50.55~18.04.1 for Bionic now also includes the two additional patches, and indeed I can confirm that on Bionic with kernel 5.4.0-54-generic the regression was now also introduced. Is there an update whether it will be possible to solve this regression? It breaks our container runtime unfortunately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894334] Re: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel
Updated my BIOS to V2.13 It didn't resolve this bug. I'm still stuck on Kernel 5.4.0-42 If you need additional Information, please get in touch with me. Because I don't know what you need or how to gather that info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894334 Title: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] [NEW] overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Public bug reported:
We use unprivileged user namespaces with overlay mounts for containers.
After recently upgrading our Focal kernels to 5.4.0-51.56 this breaks,
one cannot access files through the overlay mount in the container
anymore. This is very likely caused by some of the patches that were
added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay of
/usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52 but
is broken on kernel 5.4.0-51.56, no matter whether on Bionic or Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches that
according to the changelogs were applied in the same revision but only
to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: User Name 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 14 04:48 seq
crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CasperMD5CheckResult: skip
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
Date: Fri Oct 16 13:02:32 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic
root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.4.0-51-generic N/A
linux-backports-modules-5.4.0-51-generic N/A
linux-firmware1.187.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-5.0
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.0:cvnQEMU:ct1:cvrpc-i440fx-5.0:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-5.0
dmi.sys.vendor: QEMU
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** 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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020-16120
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions
--
ubuntu-bu
[Bug 1898189] [NEW] ubiquity doesn't offer fallback to unsigned grub-efi if signed installation fails
Public bug reported: ubiquity doesn't offer fallback to unsigned grub-efi if signed installation fails ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Fri Oct 2 14:09:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898189 Title: ubiquity doesn't offer fallback to unsigned grub-efi if signed installation fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1898189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894334] [NEW] GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel
Public bug reported: When migrating from the Kernel 5.4.0-42-lowlatency to 5.4.0-45-lowlatency my Graphic card stopped working properly. My second Monitor went dark. even little things like moving the mouse was just a slide show. When using Grub to load with the previus Kernel (5.4.0-42-lowlatency) my Graphics card worked just fine again. My Bios version is "heavily outdated" as I was told. I'll try to update it to V2.13 soon, maybe that helps run newer Kernel in the future. My Hardware: Mainboard: Z77A-G43 the command "sudo dmidecode -s bios-version" returned: "V2.5" Graphic card: Geforce GTX 760 GTK Driver package: NVIDIA driver metapackage nvidia-driver-435 UbuntuStudio 20.04.1 LTS Kernel 5.4.0-45-lowlatency PS: Thanks for your awesome Work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Sep 4 20:51:16 2020 InstallationDate: Installed on 2020-01-26 (222 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=58aefce8-42fe-4333-81ae-31d2c867846e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-21 (75 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-28T17:00:58.663417 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1894334 Title: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892245] Re: Extension breaks when accessing Overview or applications list
I tried the groovy package, works fine on focal with several machines. Maybe backporting it to focal would be the best the easiest way to fix this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892245 Title: Extension breaks when accessing Overview or applications list To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-dash-to-panel/+bug/1892245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891378] [NEW] gnome-shell 3.36.4+ unusable after show applications is triggered
Public bug reported: dash-to-panel makes gnome-shell 3.36.4 unusable after show applications is triggered. This bug is fixed in dash-to-panel 38, which is already part of groovy. I have tested the groovy package on multiple machines and it works fine. Any chance that it will be backported to focal? It is definitely better than an unusable gnome-shell if you happen to use the dash-to-panel focal package and update to the new gnome-shell 3.36.4. https://github.com/home-sweet-gnome/dash-to-panel/issues/1129 https://github.com/home-sweet-gnome/dash-to-panel/releases/tag/v38 ** Affects: gnome-shell-extension-dash-to-panel (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/1891378 Title: gnome-shell 3.36.4+ unusable after show applications is triggered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1891378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890794] [NEW] gufw fails to start due to "ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file or directory"
Public bug reported: Invoking `gufw` in a terminal causes the program to crash immediately after authorization of firewall change due to ``` > gufw /usr/bin/gufw: line 2: [: too many arguments ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file or directory Traceback (most recent call last): File "/usr/share/gufw/gufw/gufw.py", line 30, in gufw = Gufw(controler.get_frontend()) File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 80, in __init__ self._set_initial_values() File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 283, in _set_initial_values self.listening = ListeningReport(self) File "/usr/share/gufw/gufw/gufw/view/listening.py", line 35, in __init__ self._show_report() File "/usr/share/gufw/gufw/gufw/view/listening.py", line 48, in _show_report self._view_report(report, self.previous_report) File "/usr/share/gufw/gufw/gufw/view/listening.py", line 83, in _view_report self.gufw.listening_model.set_value(iter_row, 1, int(line_split[1].strip())) # port ValueError: invalid literal for int() with base 10: 'WARN:' ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gufw 20.04.1-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Aug 7 11:21:25 2020 InstallationDate: Installed on 2015-04-20 (1935 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) PackageArchitecture: all SourcePackage: gui-ufw UpgradeStatus: Upgraded to focal on 2020-04-24 (104 days ago) ** Affects: gui-ufw (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/1890794 Title: gufw fails to start due to "ls: cannot access '/usr/lib/python*/site- packages/gufw/gufw.py': No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1890794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Daniel, the shell itself is still usable in my scenario. You can open the calendar, options menu on the top right and even new windows from the panel. But the windows itself and desktop (including right click menu) are frozen. I just tested it with the latest gnome 3.36.3 updates and it still happens, still easily reproducible with many right clicks on the desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883239] Re: Kernel modules missing in 5.4.0-37
Same for me. I was also missing linux-generic. That explains it, thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883239 Title: Kernel modules missing in 5.4.0-37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883239] Re: Kernel modules missing in 5.4.0-37
I believe I was hit by the same bug. I'm using Ubuntu 20.04 on a ThinkPad X1 Carbon 4th. Manually installing the missing linux-modules- extra for 5.4.0-37 brings networking back, but I still had problems getting the system to detect external monitors. That is why I stay on 5.4.0-33 for the moment. However, even on 5.4.0-33, the detection of external monitors sometimes fails. That means that aspect could be a false alarm (on my system). What I can confirm is that for me networking is definitely broken because of the missing linux-modules-extra, which were automatically installed for 5.4.0.33 but were missing in 5.4.0.37. After manually installing the package, networking works as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883239 Title: Kernel modules missing in 5.4.0-37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882890] Re: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot
Same problem with Ubuntu 20.04 on a ThinkPad X1 Carbon 4th. "apt-get upgrade" froze at the installing the intel-ucode update. Then it also refused to start. As a workaround, I followed similar steps Paulo: * Booting into recovery mode * Step 1: dpkg --configure -a * Step 2: apt --purge remove intel-microcode (first, I had to restore networking, but continuing boot in normal mode) I also realized that the /boot partition was out of space. So, I also had to run "apt-get auto-remove" first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882890 Title: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
** Description changed: - I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: + I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272G5DYEB. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
I just checked back with my Nvidia machine and instead of "amdgpu" it saying that "modeset" is doing the EDID'ing (both with open source and proprietary driver) and no 1080p 144 Hz: [18.782] (II) modeset(G0): EDID for output DP-1-1 [18.782] (II) modeset(G0): Printing probed modes for output DP-1-1 [18.782] (II) modeset(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [18.782] (II) modeset(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [18.782] (II) modeset(G0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [18.782] (II) modeset(G0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e) [18.782] (II) modeset(G0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Where do I have to file the bug report in this case? I saw that there is a thing called modesetting that is part of the kernel. Do I have to file a report for the kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
The drm-tip kernel didn't help the case. Did I understand this correctly that you have identified the driver to be the problem? If so I have to delegate this two 3 different drivers with which I have this problem: the already linked amd driver, but also the proprietary and open source nvidia drivers that I both tested with unsuccessfully. Can you point me to the right places here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
Doesn't seem to be that there is much EDID communication going on. ** Attachment added: "sys-edid.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1879402/+attachment/5374122/+files/sys-edid.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
I just went into Windows using a cmd-tool called DumbEDID which gave me information I upload here (note that there are two monitors present and the MSI is working fine in Ubuntu, I'm referring to the philips at the bottom of the log). There is some information that is actually transported like the native resolution, physical size, monitor model and some frequencies. I'm wondering if I can use this information now to create a modeline in Ubuntu. ** Attachment added: "The information for the concerning monitor is at the bottom. The top shows information about another monitor that is working fine." https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1879402/+attachment/5373993/+files/edid.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
I tried 3 different Displayport cables without success. In Ubuntu get- edid tells me that there is no EDID information provided. As the monitor is working properly in Windows I think that Windows is just doing a better job at coming up with a 1080p modeline on its own. So in my mind the thing to do now is trying out different modelines until one with the proper resolution is actually working but I have no idea how to come up with more modelines other than using cvt 1920 1080. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879402] [NEW] Proper monitor resolution/refresh rate not available
Public bug reported: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution third-party-packages ubuntu ** Description changed: - I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I tried to get a proper solution: + I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode
[Bug 1871963] Re: dpkg fails to install grub-efi-amd64 signed and shim-signed
Just had the same issue as Deepak. Same error after upgrading from 18.04 to 20.04, but I checked and apparently also had the fix of the semicolon in /var/lib/dpkg/info/grub-efi-amd64-signed.postinst. So, there might be another issue that is causing the same problem. Running it with "set -x", I could see that the "/usr/lib/grub-multi- install --target=$target" call was failing (with target=x86_64-efi). Why it failed, I could not find out. I was able to fix the installation problem by running the commands from https://stackoverflow.com/a/53284186/783510: # sudo apt-get purge grub\* # sudo apt-get install grub-efi # sudo apt-get autoremove # sudo update-grub After that, the apt-get errors were gone, and the installation could be completed. (Another issue, which I will mention as there is a tiny chance that it is related, although I doubt it: After rebooting, I was not able to boot (not even reaching the question for the passphrase). To solve it, I had to disable Secure Boot, then I reached the state where I could enter my passphrase to unlock the encrypted partition.) My notebook: Lenovo ThinkPad X1 Carbon 4th -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871963 Title: dpkg fails to install grub-efi-amd64 signed and shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1871963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Here is my journal -f output when the bug happens. The moment it freezes: JS ERROR: Error: incorrect grab helper pop Every (no longer working) click after the freeze will result in this message: JS ERROR: TypeError: this._grabStack[i] is undefined ** Attachment added: "journal -f" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666/+attachment/5368203/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I can easily reproduce this bug on Ubuntu 20.04 with right and left clicking on the desktop to open the context menu alot. On many different machines and virtual machines. This does NOT happen for me when gnome-shell-extension-desktop-icons is deactivated. On some machines I have to explicitly do the desktop context menu thing to force it (otherwise it will not happen) on some machines it randomly happens even if I do not click on the desktop. The latter is pretty annoying. ** Attachment added: "An easy way to reproduce this, works every time on many machines. Sometimes takes a bit longer but it will happen." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666/+attachment/5368201/+files/gnome-freeze.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877451] Re: window input no longer possible when right clicking on desktop
*** This bug is a duplicate of bug 1181666 *** https://bugs.launchpad.net/bugs/1181666 ** This bug has been marked a duplicate of bug 1181666 gnome-shell randomly blocks mouse clicks from working in app windows -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877451 Title: window input no longer possible when right clicking on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877451] Re: window input no longer possible when right clicking on desktop
** Also affects: gnome-shell-extension-desktop-icons (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/1877451 Title: window input no longer possible when right clicking on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877451] Re: window input no longer possible when right clicking on desktop
** Attachment added: "journal -f" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+attachment/5368000/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877451 Title: window input no longer possible when right clicking on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877451] Re: window input no longer possible when right clicking on desktop
** Attachment added: "Video of the bug in a fresh Ubuntu 20.04 installation in a virtual machine" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+attachment/5367999/+files/gnome-freeze.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877451 Title: window input no longer possible when right clicking on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877451] [NEW] window input no longer possible when right clicking on desktop
Public bug reported:
Sometimes when right clicking on desktop all windows no longer respond
to input.
This is easily reproducable, just do many alternating right and left
clicks directly on the desktop. The context menu will open and close and
at some point the context menu will stay open and will no longer
respond. Also all other windows will no longer react on input.
The top bar can be used though, it is possible to log out and log in
again. This will reset the problem. Sometimes Alt + F2 -> R is also
possible, which resets the problem.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu2
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
CurrentDesktop: ubuntu:GNOME
Date: Thu May 7 22:30:46 2020
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'de')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children'
b"['update-manager']"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2020-05-07 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (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/1877451
Title:
window input no longer possible when right clicking on desktop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
I can reproduce this bug on a fresh install of Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877451] Re: window input no longer possible when right clicking on desktop
I can reproduce this bug on many different machines and virtual machines. I was not able to reproduce it with gnome-shell-extension- desktop-icons disabled (yet?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877451 Title: window input no longer possible when right clicking on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875504] Re: apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" name="/dev/net/tun" pid=490601 comm="swanctl" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
# grep -R kernel-libipsec /etc/strongswan.* /etc/swanctl/
/etc/strongswan.d/charon/kernel-libipsec.conf:kernel-libipsec {
The whole file /etc/strongswan.d/charon/kernel-libipsec.conf:
kernel-libipsec {
load = no
}
Anything else that I could check?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875504
Title:
apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl"
name="/dev/net/tun" pid=490601 comm="swanctl" requested_mask="wr"
denied_mask="wr" fsuid=0 ouid=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1875504/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875504] Re: apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" name="/dev/net/tun" pid=490601 comm="swanctl" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
No, I'm not running kernel-libipsec. My configured ipsec connections work despite the apparmor deny action. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875504 Title: apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" name="/dev/net/tun" pid=490601 comm="swanctl" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1875504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875504] [NEW] apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" name="/dev/net/tun" pid=490601 comm="swanctl" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Public bug reported: The swanctl apparmor profile leads to the following deny: apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" name="/dev/net/tun" pid=490601 comm="swanctl" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 I'm using charon-systemd instead of strongswan-starter. $ dpkg -l|grep "strongswan\|charon" ii charon-systemd 5.8.2-1ubuntu3 amd64strongSwan IPsec client, systemd support ii libcharon-extauth-plugins5.8.2-1ubuntu3 amd64strongSwan charon library (extended authentication plugins) ii libcharon-extra-plugins 5.8.2-1ubuntu3 amd64strongSwan charon library (extra plugins) ii libcharon-standard-plugins 5.8.2-1ubuntu3all transitional package ii libstrongswan5.8.2-1ubuntu3 amd64strongSwan utility and crypto library ii libstrongswan-extra-plugins 5.8.2-1ubuntu3 amd64strongSwan utility and crypto library (extra plugins) ii strongswan 5.8.2-1ubuntu3all IPsec VPN solution metapackage ii strongswan-charon5.8.2-1ubuntu3 amd64strongSwan Internet Key Exchange daemon ii strongswan-libcharon 5.8.2-1ubuntu3 amd64strongSwan charon library ii strongswan-pki 5.8.2-1ubuntu3 amd64strongSwan IPsec client, pki command ii strongswan-starter 5.8.2-1ubuntu3 amd64strongSwan daemon starter and configuration file parser ii strongswan-swanctl 5.8.2-1ubuntu3 amd64strongSwan IPsec client, swanctl command ** Affects: strongswan (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/1875504 Title: apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" name="/dev/net/tun" pid=490601 comm="swanctl" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1875504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875503] [NEW] apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" pid=xxxxx comm="swanctl" family="packet" sock_type="dgram" protocol=0 requested_mask="send receive" denied_ma
Public bug reported: The swanctl apparmor profile leads to a denied: AVC apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" pid=490601 comm="swanctl" family="packet" sock_type="dgram" protocol=0 requested_mask="send receive" denied_mask="send receive" I'm using charon-systemd instead of strongswan-starter. $ dpkg -l|grep "strongswan\|charon" ii charon-systemd 5.8.2-1ubuntu3 amd64strongSwan IPsec client, systemd support ii libcharon-extauth-plugins5.8.2-1ubuntu3 amd64strongSwan charon library (extended authentication plugins) ii libcharon-extra-plugins 5.8.2-1ubuntu3 amd64strongSwan charon library (extra plugins) ii libcharon-standard-plugins 5.8.2-1ubuntu3all transitional package ii libstrongswan5.8.2-1ubuntu3 amd64strongSwan utility and crypto library ii libstrongswan-extra-plugins 5.8.2-1ubuntu3 amd64strongSwan utility and crypto library (extra plugins) ii strongswan 5.8.2-1ubuntu3all IPsec VPN solution metapackage ii strongswan-charon5.8.2-1ubuntu3 amd64strongSwan Internet Key Exchange daemon ii strongswan-libcharon 5.8.2-1ubuntu3 amd64strongSwan charon library ii strongswan-pki 5.8.2-1ubuntu3 amd64strongSwan IPsec client, pki command ii strongswan-starter 5.8.2-1ubuntu3 amd64strongSwan daemon starter and configuration file parser ii strongswan-swanctl 5.8.2-1ubuntu3 amd64strongSwan IPsec client, swanctl command ** Affects: strongswan (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/1875503 Title: apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/swanctl" pid=x comm="swanctl" family="packet" sock_type="dgram" protocol=0 requested_mask="send receive" denied_mask="send receive" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1875503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875502] [NEW] error: module 'acme. challenges' has no attribute 'TLSSNI01'
Public bug reported: After upgrading to ubuntu 20.04 certbot fails to create new certificates: $ certbot renew --dry-run Traceback (most recent call last): File "/usr/lib/python3/dist-packages/certbot/renewal.py", line 449, in handle_renewal_request main.renew_cert(lineage_config, plugins, renewal_candidate) File "/usr/lib/python3/dist-packages/certbot/main.py", line 1208, in renew_cert renewed_lineage = _get_and_save_cert(le_client, config, lineage=lineage) File "/usr/lib/python3/dist-packages/certbot/main.py", line 116, in _get_and_save_cert renewal.renew_cert(config, domains, le_client, lineage) File "/usr/lib/python3/dist-packages/certbot/renewal.py", line 307, in renew_cert new_cert, new_chain, new_key, _ = le_client.obtain_certificate(domains, new_key) File "/usr/lib/python3/dist-packages/certbot/client.py", line 348, in obtain_certificate orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names) File "/usr/lib/python3/dist-packages/certbot/client.py", line 396, in _get_order_and_authorizations authzr = self.auth_handler.handle_authorizations(orderr, best_effort) File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 62, in handle_authorizations achalls = self._choose_challenges(authzrs) File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 206, in _choose_challenges self._get_chall_pref(authzr.body.identifier.value), File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 221, in _get_chall_pref plugin_pref = self.auth.get_chall_pref(domain) File "/usr/lib/python3/dist-packages/certbot_nginx/configurator.py", line 1110, in get_chall_pref return [challenges.HTTP01, challenges.TLSSNI01] AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' /etc/letsencrypt/renewal/host.conf: # renew_before_expiry = 30 days version = 0.36.0 archive_dir = /etc/letsencrypt/archive/host cert = /etc/letsencrypt/live/host/cert.pem privkey = /etc/letsencrypt/live/host/privkey.pem chain = /etc/letsencrypt/live/host/chain.pem fullchain = /etc/letsencrypt/live/host/fullchain.pem # Options used in the renewal process [renewalparams] account = abcdef1234567890 authenticator = nginx installer = nginx server = https://acme-v02.api.letsencrypt.org/directory $ dpkg -l|grep certbot ii certbot 0.40.0-1 all automatically configure HTTPS using Let's Encrypt ii python3-certbot 0.40.0-1 all main library for certbot ii python3-certbot-nginx0.39.0-1 all Nginx plugin for Certbot ** Affects: python-certbot (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/1875502 Title: error: module 'acme. challenges' has no attribute 'TLSSNI01' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1875502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874318] [NEW] package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.142+2.04-1ubuntu26 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 17:09:37 2020 DuplicateSignature: package:grub-efi-amd64-signed:1.142+2.04-1ubuntu26 Setting up grub-efi-amd64-signed (1.142+2.04-1ubuntu26) ... dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2015-07-26 (1732 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2020-04-22 (0 days ago) ** Affects: grub2-signed (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/1874318 Title: package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1874318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874317] [NEW] package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 1874318 *** https://bugs.launchpad.net/bugs/1874318 Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.142+2.04-1ubuntu26 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 17:09:37 2020 DuplicateSignature: package:grub-efi-amd64-signed:1.142+2.04-1ubuntu26 Setting up grub-efi-amd64-signed (1.142+2.04-1ubuntu26) ... dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2015-07-26 (1732 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2020-04-22 (0 days ago) ** Affects: grub2-signed (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/1874317 Title: package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1874317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871308] [NEW] Failed to start Notification regarding a crash report
Public bug reported: journalctl has these nasty messages when the whoopsie service is disabled: systemd[3290]: Starting Notification regarding a crash report... update-notifier-crash[38295]: /usr/bin/whoopsie systemd[3290]: update-notifier-crash.service: Main process exited, code=exited, status=1/FAILURE systemd[3290]: update-notifier-crash.service: Failed with result 'exit-code'. systemd[3290]: Failed to start Notification regarding a crash report. It is caused by /usr/lib/update-notifier/update-notifier-crash having `set -e` at the top but then doing checks like `systemctl -q is-enabled whoopsie` outside of an `if`. A simple fix that also silences the line with "/usr/bin/whoopsie" is attached. ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Patch added: "update-notifier-crash.patch" https://bugs.launchpad.net/bugs/1871308/+attachment/5348450/+files/update-notifier-crash.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871308 Title: Failed to start Notification regarding a crash report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1871308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870386] [NEW] GIMP crash on changing themes
Public bug reported: GIMP 2.10.8 crashes for me when selecting any theme, or reloading the current theme. Steps to reproduce: (1) Open The GIMP. (2) Open Preferences. (3) Open theme selection in preferences. (4) Select any theme, OR click "reload current theme". (5) Crash. See bug information below! ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) using GEGL version 0.4.14 (compiled against version 0.4.12) using GLib version 2.62.4 (compiled against version 2.58.1) using GdkPixbuf version 2.40.0 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.0) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Speicherzugriffsfehler Stack trace: ``` # Stack traces obtained from PID 7329 - Thread 7329 # [New LWP 7330] [New LWP 7331] [New LWP 7332] [New LWP 7333] [New LWP 7334] [New LWP 7335] [New LWP 7336] [New LWP 7344] [New LWP 7345] [New LWP 7354] [New LWP 7355] [New LWP 7356] [New LWP 7357] [New LWP 7358] [New LWP 7359] [New LWP 7360] [New LWP 7361] [New LWP 7362] [New LWP 7363] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __libc_read (nbytes=256, buf=0x7ffe8d898d50, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7f607f7dbe00 (LWP 7329) "gimp" __libc_read (nbytes=256, buf=0x7ffe8d898d50, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7f607f01e700 (LWP 7330) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f607e81d700 (LWP 7331) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f607e01c700 (LWP 7332) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f607d81b700 (LWP 7333) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7f607d01a700 (LWP 7334) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7f607c819700 (LWP 7335) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7f606700 (LWP 7336) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f605c97f700 (LWP 7344) "gmain"0x7f608077dc2f in __GI___poll (fds=0x56345723e0c0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7f605d180700 (LWP 7345) "gdbus"0x7f608077dc2f in __GI___poll (fds=0x563457252940, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7f6038346700 (LWP 7354) "async"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7f6037b45700 (LWP 7355) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7f6037344700 (LWP 7356) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 14 Thread 0x7f6036b43700 (LWP 7357) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 15 Thread 0x7f6036342700 (LWP 7358) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7f6035b41700 (LWP 7359) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 17 Thread 0x7f6035340700 (LWP 7360) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_6
[Bug 1867503] [NEW] package gcc-avr (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package gcc-arm-embedded 7-2018q2-1~trusty1
Public bug reported: See error message in summary. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: gcc-avr (not installed) ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 AptOrdering: binutils-avr:amd64: Install gcc-avr:amd64: Install avr-libc:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Mar 15 10:26:23 2020 ErrorMessage: trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package gcc-arm-embedded 7-2018q2-1~trusty1 InstallationDate: Installed on 2016-04-26 (1418 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: gcc-avr Title: package gcc-avr (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package gcc-arm-embedded 7-2018q2-1~trusty1 UpgradeStatus: Upgraded to eoan on 2020-01-03 (72 days ago) ** Affects: gcc-avr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan ** Attachment removed: "Df.txt" https://bugs.launchpad.net/ubuntu/+source/gcc-avr/+bug/1867503/+attachment/5337137/+files/Df.txt ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gcc-avr/+bug/1867503/+attachment/5337138/+files/Dmesg.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/gcc-avr/+bug/1867503/+attachment/5337141/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "DpkgHistoryLog.txt" https://bugs.launchpad.net/ubuntu/+source/gcc-avr/+bug/1867503/+attachment/5337139/+files/DpkgHistoryLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867503 Title: package gcc-avr (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package gcc- arm-embedded 7-2018q2-1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-avr/+bug/1867503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862018] [NEW] Auto-refresh does not work
Public bug reported: PDFs are not automatically refreshed when they change, e.g. when working on a latex document. ** Affects: evince (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/1862018 Title: Auto-refresh does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1862018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172937] Re: SQUASHFS error while booting from live cd
Update regarding my previous comment:
After resetting the VM (in the Hyper-V connection -> "Action" ->
"Reset") the VM rebooted, showed the login screen for the first time and
I could login. But right after the login the screen was stuck again -
there was no menu bar with the program launch icons on the left (a.k.a.
"dock"), the bar on the top was empty except for the three indicators in
the top right corner (network, sound, power), right click on the
background didn't do anything and there was just the time being
displayed in the center. Nothing happened for at least 15 minutes.
Then after resetting *again* and logging in a second time, finally the
typical welcome screen of Ubuntu appeared ("What's new in Ubuntu", the
program launch bar on the left etc.) and I could properly use 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/172937
Title:
SQUASHFS error while booting from live cd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172937] Re: SQUASHFS error while booting from live cd
I just installed Ubuntu 18.04 in a new Hyper-V VM (host is Windows 10 Pro). Fresh virtual disk (25 GB), 2 virtual CPUs, 4 GB RAM. I used the ISO file to boot and install. The installation went fine until the forced reboot at the end of the installation. After the reboot a lot of these "SQUASHFS error: ..." messages appear: - SQUASHFS error: Unable to read metadata cache entry [...] - SQUASHFS error: read_indexes: reading block [...:...] And at the end the screen is stuck as can be seen in the attached screenshot. ** Attachment added: "2020-01-15 ubuntu vm.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+attachment/5320576/+files/2020-01-15%20ubuntu%20vm.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/172937 Title: SQUASHFS error while booting from live cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484157] Re: AltGr key acts like "Select All"
Same bug here after updating the system from 16.04 LTS to 19.04. German keyboard layout, so it is pretty annoying, especially when entering passwords in Firefox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484157 Title: AltGr key acts like "Select All" To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1484157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484157] Re: AltGr key acts like "Select All"
Addendum to comment #16: Switching the "keyboard input method system" to either "XIM" or "none" does NOT help on my system. Moving the focus between several input fields sometimes restores the correct behaviour and suddenly changes back to the faulty one, usually when pressing Alt Gr after typing some characters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484157 Title: AltGr key acts like "Select All" To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1484157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857955] Re: 'unicode' is not defined
This indicates you are using a broken version of the titlecase plugin. It shouldn't even be marked as compatible with Picard 2, but maybe it was edited manually. Please remove /home/danialbehzadi/.config/MusicBrainz/Picard/plugins/titlecase.zip and install the latest version in Options > Plugins. ** Changed in: picard (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857955 Title: 'unicode' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/picard/+bug/1857955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857758] [NEW] package libapache2-mod-php7.0 7.0.33-0ubuntu0.16.04.7 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: It could not be installed with tasksel ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libapache2-mod-php7.0 7.0.33-0ubuntu0.16.04.7 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-72-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Sat Dec 28 13:34:35 2019 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-05-04 (967 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: php7.0 Title: package libapache2-mod-php7.0 7.0.33-0ubuntu0.16.04.7 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apache2.mods-available.php7.0.conf: [deleted] modified.conffile..etc.apache2.mods-available.php7.0.load: [deleted] ** Affects: php7.0 (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/1857758 Title: package libapache2-mod-php7.0 7.0.33-0ubuntu0.16.04.7 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1857758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854866] [NEW] openarena-server crashes due to segmentation fault after start of game
Public bug reported: openarena crashes immediately after start of singleplayer game due to a segmentation fault. The output of the command is ``` > openarena ioq3 1.36+u20190529.350b8f9~dfsg-2/Ubuntu linux-x86_64 Jul 9 2019 SSE instruction set enabled - FS_Startup - We are looking in the current search path: /home/richter/.openarena/baseoa /usr/lib/openarena/baseoa /usr/lib/openarena/baseoa/z_oacmp-volume1-v3.pk3 (370 files) /usr/lib/openarena/baseoa/pak6-patch088.pk3 (711 files) /usr/lib/openarena/baseoa/pak6-patch085.pk3 (559 files) /usr/lib/openarena/baseoa/pak6-misc.pk3 (229 files) /usr/lib/openarena/baseoa/pak5-TA.pk3 (139 files) /usr/lib/openarena/baseoa/pak4-textures.pk3 (1753 files) /usr/lib/openarena/baseoa/pak2-players.pk3 (669 files) /usr/lib/openarena/baseoa/pak2-players-mature.pk3 (231 files) /usr/lib/openarena/baseoa/pak1-maps.pk3 (100 files) /usr/lib/openarena/baseoa/pak0.pk3 (1042 files) -- 5803 files in pk3 files execing default.cfg execing q3config.cfg couldn't exec autoexec.cfg Hunk_Clear: reset the hunk ok - Client Initialization - Couldn't read q3history. - Initializing Renderer Trying to load "renderer_opengl2_x86_64.so" from "/usr/lib/ioquake3"... --- QKEY found. - Client Initialization Complete - - R_Init - SDL using driver "x11" Initializing OpenGL display Display aspect: 1.600 ...setting mode -1: 1680 1050 Trying to get an OpenGL 3.2 core context SDL_GL_CreateContext succeeded. Using 24 color bits, 24 depth, 8 stencil display. Available modes: '1440x900 1680x1050 1280x720 720x400 640x480 800x600 832x624 1024x768 1152x864 1280x960 1600x1200 1280x1024' GL_RENDERER: Mesa DRI Intel(R) Ivybridge Mobile Initializing OpenGL extensions ...GL_EXT_texture_compression_s3tc not found ...ignoring GL_S3_s3tc ...ignoring GL_EXT_texture_filter_anisotropic ...using GL_SGIS_texture_edge_clamp ...using GL_ARB_framebuffer_object ...using GL_ARB_vertex_array_object ...using GL_ARB_texture_float ...using GL_ARB_depth_clamp ...ignoring GL_ARB_seamless_cube_map ...using GLSL version 4.20 ...GL_NVX_gpu_memory_info not found ...GL_ATI_meminfo not found ...ignoring GL_ARB_texture_compression_rgtc ...ignoring GL_ARB_texture_compression_bptc ...GL_EXT_direct_state_access not found --- FBO_Init --- --- GLSL_InitGPUShaders --- loaded 114 GLSL shaders (48 gen 42 light 24 etc) in 1.36 seconds --- R_InitVaos --- Initializing Shaders GL_VENDOR: Intel Open Source Technology Center GL_RENDERER: Mesa DRI Intel(R) Ivybridge Mobile GL_VERSION: 4.2 (Core Profile) Mesa 19.2.1 GL_EXTENSIONS: GL_3DFX_texture_compression_FXT1 GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_trinary_minmax GL_AMD_texture_texture4 GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_APPLE_object_purgeable GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_compressed_texture_pixel_storage GL_ARB_compute_shader GL_ARB_conditional_render_inverted GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_sha
