[Touch-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
Yes, it still happens with mesa 23.2.1-1ubuntu2. Additionally, it is not only with video fullscreen. Same happens if I start synaptic for example. Sometimes it hangs for 10 seconds too. Seems to affect multiple applications and is triggered by multiple ways. https://gitlab.freedesktop.org/mesa/mesa/-/issues/9905 ** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed
Hello. Is there somebody looking into this problem? No comment from ubuntu-devs so far and I wonder if this report is even noticed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1766325 Title: sudo: pam_unix(sudo:auth): conversation failed Status in sudo package in Ubuntu: Confirmed Bug description: Hello. I experience a bug after upgrading from Ubuntu 17.10 to 18.04. The bug seems to be a regression because what I am trying to do was working with Ubuntu 17.10 and stopped working after the upgrade. Here is the problem: I have 2 users on my system. One is the user that is created during installation, named zzz. The other user I added later, named abc. Both users have passwords set. According to passwd the password for user abc is a locked password (L) (whatever that means). Now I am logged into user zzz and want to execute a program as user abc without entering the password of user abc. Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java -version". To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: /usr/bin/java" Now this seems to be ignored. Instead the terminal is asking for the password of user abc. I see this in /var/log/auth.log: "sudo: pam_unix(sudo:auth): conversation failed". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1766325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767299] [NEW] Ubuntu 18.04 Installer creates swap partition too small
Public bug reported: Installed Ubuntu 18.04 final release. The disk is 512 Gigabyte, the RAM is 8 Gigabyte. The installer just gave me 979 Megabyte of space. I chose LVM to have an encrypted drive. Here are some details: free -h totalusedfree shared buff/cache available Mem: 7,7G4,0G152M399M3,6G3,0G Swap: 979M 0B979M swapon --show NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/ubuntu--vg-root / ext4errors=remount-ro 0 1 # /boot was on /dev/sda2 during installation UUID=removed-id /boot ext4defaults0 2 # /boot/efi was on /dev/sda1 during installation UUID=removed-id /boot/efi vfatumask=0077 0 1 /dev/mapper/ubuntu--vg-swap_1 noneswapsw 0 0 ** Affects: partman-auto (Ubuntu) Importance: Undecided Status: New ** Package changed: sudo (Ubuntu) => partman (Ubuntu) ** Package changed: partman (Ubuntu) => partman-auto (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1767299 Title: Ubuntu 18.04 Installer creates swap partition too small Status in partman-auto package in Ubuntu: New Bug description: Installed Ubuntu 18.04 final release. The disk is 512 Gigabyte, the RAM is 8 Gigabyte. The installer just gave me 979 Megabyte of space. I chose LVM to have an encrypted drive. Here are some details: free -h totalusedfree shared buff/cache available Mem: 7,7G4,0G152M399M3,6G 3,0G Swap: 979M 0B979M swapon --show NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/ubuntu--vg-root / ext4errors=remount-ro 0 1 # /boot was on /dev/sda2 during installation UUID=removed-id /boot ext4defaults0 2 # /boot/efi was on /dev/sda1 during installation UUID=removed-id /boot/efi vfatumask=0077 0 1 /dev/mapper/ubuntu--vg-swap_1 noneswapsw 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed
This happens with the final release 18.04 as well. Is there a temporary solution or some progress in fixing that regression? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1766325 Title: sudo: pam_unix(sudo:auth): conversation failed Status in sudo package in Ubuntu: Confirmed Bug description: Hello. I experience a bug after upgrading from Ubuntu 17.10 to 18.04. The bug seems to be a regression because what I am trying to do was working with Ubuntu 17.10 and stopped working after the upgrade. Here is the problem: I have 2 users on my system. One is the user that is created during installation, named zzz. The other user I added later, named abc. Both users have passwords set. According to passwd the password for user abc is a locked password (L) (whatever that means). Now I am logged into user zzz and want to execute a program as user abc without entering the password of user abc. Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java -version". To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: /usr/bin/java" Now this seems to be ignored. Instead the terminal is asking for the password of user abc. I see this in /var/log/auth.log: "sudo: pam_unix(sudo:auth): conversation failed". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1766325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
