[Touch-packages] [Bug 806880] Re: make_bak_dir mkdir failed: File exists (17)
[Expired for rsync (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rsync (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/806880 Title: make_bak_dir mkdir failed: File exists (17) Status in rsync package in Ubuntu: Expired Bug description: I have an rsync-based backup routine. Today I had the following error: $ rsync -F -h -av --backup --delete --delete-excluded --force --backup-dir=/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33 --exclude=*.o --exclude=*~ --exclude=#* /media/hp320/Skannat /media/2TBBackup/backup/media/hp320 sending incremental file list Skannat/neg004c/im4114-2.tif.xmp Skannat/neg004c/im4115-2.tif.xmp Skannat/neg004c/im4116-2.tif.xmp Skannat/neg004c/im4123-2.tif.xmp Skannat/neg005c/im4044-2.tif.xmp [...] Skannat/neg023/2003bfl-0169-imh235.tif.xmp rsync: make_bak_dir mkdir "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33" failed: File exists (17) rsync: keep_backup failed: "/media/2TBBackup/backup/media/hp320/Skannat/neg004c/im4114-2.tif.xmp" -> "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33/Skannat/neg004c/im4114-2.tif.xmp": No such file or directory (2) rsync: stat "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33/Skannat/neg004c/im4114-2.tif.xmp" failed: No such file or directory (2) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: rsync 3.0.7-2ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Thu Jul 7 11:26:57 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928.1) SourcePackage: rsync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/806880/+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 2000868] Re: backport required for virtio_gpu_dri.so
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- 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/2000868 Title: backport required for virtio_gpu_dri.so Status in mesa package in Ubuntu: Expired Bug description: Hi, xorg crashing when using modsetting with virtio_gpu_dri as graphics driver in kvm guest. Kindly look into this conversation https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920 I think we need to backport https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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 2009603] Re: apt autoremove doesn´t catch all old kernels
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2009603 Title: apt autoremove doesn´t catch all old kernels Status in apt package in Ubuntu: Expired Bug description: I have an install with nominally 500MB as /boot. I'm regularly running beyond that limit at updates. Instead of manually picking out old files and apt --purge, I found that more recently apt autoremove would do that task. That brought me down by 11 MB only, from 100%: 445 401 11 98% apt update apt upgrade apt autoremove and reboot didn't improve the situation. A tad reluctantly I installed byobu and ran one session of purge-old-kernels. Result: 445 277 135 68% I can live with that; though I couldn't with the result above. Of course, I'd prefer apt autoremove to do everything in a single go. But what it does, does not actually warrant the deprecation of purge-old-kernels. I'm surely not the only person with a tight budget when using a separate /boot of an old installation. Or, as in my case, a fresh install into an old, formerly partitioned drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2009603/+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 2017926] Re: Unused content snaps not autoremoved
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-notifier (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017926 Title: Unused content snaps not autoremoved Status in snapd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: $ snap connections --all | grep gnome content - gnome-3-28-1804:gnome-3-28-1804 - content - gnome-3-34-1804:gnome-3-34-1804 - content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-42-2204]mattermost-desktop:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snap-store:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snapd-desktop-integration:gnome-42-2204 gnome-42-2204:gnome-42-2204 - my system has 4 gnome-* content snaps, that were pulled in as dependencies. The apps that used them, have moved on to newer versions. Something on my system must clean then up for me, for example apt autoremoves automatically installed packages & obsolete kernels, and so should also happen with snaps. It can be done by snapd itself, or by something else on the classic desktop - i.e. update-manager. Note it is easy to detect such snaps, as it provides no apps; has content interface only; which is not plugged by anything. If it is ever needed by any future or past revision of any other snap it would be autoinstalled back. On my system they take up 824M of disk space (2 revisions, of 2 unused content snaps = 4 snaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2017926/+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 2017926] Re: Unused content snaps not autoremoved
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017926 Title: Unused content snaps not autoremoved Status in snapd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: $ snap connections --all | grep gnome content - gnome-3-28-1804:gnome-3-28-1804 - content - gnome-3-34-1804:gnome-3-34-1804 - content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-42-2204]mattermost-desktop:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snap-store:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snapd-desktop-integration:gnome-42-2204 gnome-42-2204:gnome-42-2204 - my system has 4 gnome-* content snaps, that were pulled in as dependencies. The apps that used them, have moved on to newer versions. Something on my system must clean then up for me, for example apt autoremoves automatically installed packages & obsolete kernels, and so should also happen with snaps. It can be done by snapd itself, or by something else on the classic desktop - i.e. update-manager. Note it is easy to detect such snaps, as it provides no apps; has content interface only; which is not plugged by anything. If it is ever needed by any future or past revision of any other snap it would be autoinstalled back. On my system they take up 824M of disk space (2 revisions, of 2 unused content snaps = 4 snaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2017926/+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 2017926] Re: Unused content snaps not autoremoved
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017926 Title: Unused content snaps not autoremoved Status in snapd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: $ snap connections --all | grep gnome content - gnome-3-28-1804:gnome-3-28-1804 - content - gnome-3-34-1804:gnome-3-34-1804 - content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-42-2204]mattermost-desktop:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snap-store:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snapd-desktop-integration:gnome-42-2204 gnome-42-2204:gnome-42-2204 - my system has 4 gnome-* content snaps, that were pulled in as dependencies. The apps that used them, have moved on to newer versions. Something on my system must clean then up for me, for example apt autoremoves automatically installed packages & obsolete kernels, and so should also happen with snaps. It can be done by snapd itself, or by something else on the classic desktop - i.e. update-manager. Note it is easy to detect such snaps, as it provides no apps; has content interface only; which is not plugged by anything. If it is ever needed by any future or past revision of any other snap it would be autoinstalled back. On my system they take up 824M of disk space (2 revisions, of 2 unused content snaps = 4 snaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2017926/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I am aware of it, but because I lack a more appropriate link and it has to do with design, I suppose it is not my fault;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium & large form factors & point & click interactions E.g. Selection Menu Contextual Menu UX Spec here Contextual menu page 110: https://docs.google.com/document/edit?hgd=1&id=1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw#heading=h.8ru1zzx6wzpq Menus work is currently in progress (page 116): https://docs.google.com/document/edit?hgd=1&id=1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1428762/+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 2018661] [NEW] package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Attempting to install steam ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxxf86vm1 1:1.1.4-1build3 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None Date: Sat May 6 16:04:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:122d] InstallationDate: Installed on 2023-02-14 (81 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X750JA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: libxxf86vm Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X750JB.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X750JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX750JB.208:bd08/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnX750JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X750JA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: libxxf86vm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxxf86vm in Ubuntu. https://bugs.launchpad.net/bugs/2018661 Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg- deb --fsys-tarfile subprocess returned error exit status 2 Status in libxxf86vm package in Ubuntu: New Bug description: Attempting to install steam ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxxf86vm1 1:1.1.4-1build3 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None Date: Sat May 6 16:04:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:122d] InstallationDate: Installed on 2023-02-14 (81 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X750JA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: libxxf86vm Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X750JB.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X750JA
[Touch-packages] [Bug 2018656] [NEW] login process frozen in between username and password
Public bug reported: MY SYSTEM No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2018656 Title: login process frozen in between username and password Status in gnome-online-accounts package in Ubuntu: New Bug description: MY SYSTEM No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256c
[Touch-packages] [Bug 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Description changed: + [ Impact ] + + Recent updates have been using `PACKRATDATA=backzone` in order to add + all out-of-scope lower-quality pre-1970 data back that existed in + earlier tzadata releases (see bug #2003797). However it also leads to + time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, + and Pacific/Enderbury to change: + compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown + + [ Test Plan ] + + Add an autopkgtest test case for post-1970 symlink consistency: Check + that the timezones for today and in half a year (= to cover DST changes) + do not change compared to building them without `PACKRATDATA=backzone`. + + The mentioned timezones that differed can also be tested manually. + Running following commands should have the same output (the output + mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): + + ``` + $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" + Fri Apr 28 05:49:00 PST 2023 + $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" + Fri Apr 28 12:49:00 -01 2023 + $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" + Fri Apr 28 16:49:00 MSK 2023 + ``` + + [ Where problems could occur ] + + Timezone data could be wrong. Systems with incorrect timezone set may + observe unexpected time shift when updating the package. ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in tzdata package in Ubuntu: Confirmed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata source package in Lunar: New Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+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 2017898] Re: MESA 22.2 Regression Causes Kwin Crashes (Fix Available)
*** This bug is a duplicate of bug 2003339 *** https://bugs.launchpad.net/bugs/2003339 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/2017898 Title: MESA 22.2 Regression Causes Kwin Crashes (Fix Available) Status in mesa package in Ubuntu: Confirmed Bug description: MESA 22.2 contains a malfunction which causes kwin to exit regularly / frequently, leaving the system without window management. This is a regression compared to MESA 22.1 and fixed again in MESA 22.3. See following MESA bug: * https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 * just for reference, corresponding KDE Bugtracker entry: https://bugs.kde.org/show_bug.cgi?id=461316 Maybe the fix could be backported? It currently is something between inconvenient (for very technically savy users) and rendering the system unusable (for less technically savy users - suddenly, Window Management will be gone and switching windows, accessing panels, and controlling most applications even if they are in foreground at the time of a crash become impossible). ProblemType: Bug DistroRelease: KDE neon 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Apr 27 14:26:47 2023 DistUpgraded: 2020-10-11 12:05:38,766 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-40-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=/dev/mapper/ubuntu--vg--970-root ro resume=/dev/ubuntu-vg-970/swap fsck.mode=force rd.driver.blacklist=nouveau pcie_aspm=off RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2020-10-11 (928 days ago) dmi.bios.date: 11/10/2022 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-0xneon+22.04+jammy+release+build8 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017898/+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 2017898] Re: MESA 22.2 Regression Causes Kwin Crashes (Fix Available)
*** This bug is a duplicate of bug 2003339 *** https://bugs.launchpad.net/bugs/2003339 ** This bug has been marked a duplicate of bug 2003339 kwin_x11: The X11 connection broke: I/O error (code 1) -- 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/2017898 Title: MESA 22.2 Regression Causes Kwin Crashes (Fix Available) Status in mesa package in Ubuntu: New Bug description: MESA 22.2 contains a malfunction which causes kwin to exit regularly / frequently, leaving the system without window management. This is a regression compared to MESA 22.1 and fixed again in MESA 22.3. See following MESA bug: * https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 * just for reference, corresponding KDE Bugtracker entry: https://bugs.kde.org/show_bug.cgi?id=461316 Maybe the fix could be backported? It currently is something between inconvenient (for very technically savy users) and rendering the system unusable (for less technically savy users - suddenly, Window Management will be gone and switching windows, accessing panels, and controlling most applications even if they are in foreground at the time of a crash become impossible). ProblemType: Bug DistroRelease: KDE neon 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Apr 27 14:26:47 2023 DistUpgraded: 2020-10-11 12:05:38,766 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-40-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=/dev/mapper/ubuntu--vg--970-root ro resume=/dev/ubuntu-vg-970/swap fsck.mode=force rd.driver.blacklist=nouveau pcie_aspm=off RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2020-10-11 (928 days ago) dmi.bios.date: 11/10/2022 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-0xneon+22.04+jammy+release+build8 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017898/+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
