[Touch-packages] [Bug 2020030] [NEW] System 76 Lemur Pro - Light Display Manager failed on boot
Public bug reported: I have executed a ubuntu-bug lightdm as requested here: https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709 In my case I did nano /etc/systemd/system/display-manager.service and double checked Restart=Always was on (it was) and added RestartSec=0.5. So far it’s booting every single time without issue. It might be better to include that in the config by default so less people run into this issue. Most of the people who were addressing this ended up reinstalling Ubuntu Budgie and this fix can avoid that issue entirely. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 [modified: lib/systemd/system/lightdm.service] Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed May 17 21:50:52 2023 InstallationDate: Installed on 2022-09-21 (239 days ago) InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) LightdmConfig: [Seat:*] greeter-session=slick-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/2020030 Title: System 76 Lemur Pro - Light Display Manager failed on boot Status in lightdm package in Ubuntu: New Bug description: I have executed a ubuntu-bug lightdm as requested here: https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709 In my case I did nano /etc/systemd/system/display-manager.service and double checked Restart=Always was on (it was) and added RestartSec=0.5. So far it’s booting every single time without issue. It might be better to include that in the config by default so less people run into this issue. Most of the people who were addressing this ended up reinstalling Ubuntu Budgie and this fix can avoid that issue entirely. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 [modified: lib/systemd/system/lightdm.service] Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed May 17 21:50:52 2023 InstallationDate: Installed on 2022-09-21 (239 days ago) InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) LightdmConfig: [Seat:*] greeter-session=slick-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2020030/+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 2018935] Re: Amazon and Google+ icons exist in suru-icons and ubuntu-mobile packages.
** Changed in: ubuntu-themes Status: New => In Progress ** Changed in: ubuntu-themes Assignee: (unassigned) => wontfix (wontfix) ** Changed in: ubuntu-themes Importance: Undecided => Low ** Changed in: ubuntu-themes (Ubuntu) Assignee: wontfix (wontfix) => (unassigned) ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/2018935 Title: Amazon and Google+ icons exist in suru-icons and ubuntu-mobile packages. Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: Triaged Bug description: This may be holdover from Ubuntu Touch or related desktop Amazon Unity scope integration around that time. /ubuntu-mobile/apps/scalable/amazon.svg /ubuntu-mobile/apps/240/amazon.png /ubuntu-mobile/apps/144/amazon.png /suru-icons/apps/scalable/amazon-symbolic.svg Google+ was sunset in 2018. https://www.blog.google/technology/safety-security/project-strobe/ /ubuntu-mobile/apps/symbolic/googleplus-symbolic.svg /suru-icons/apps/scalable/googleplus-symbolic.svg /suru-icons/apps/scalable/google-plus-symbolic.svg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/2018935/+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 2018940] Re: ubuntu-mono icon theme contains Ubuntu One client icons.
** Changed in: ubuntu-themes Assignee: (unassigned) => wontfix (wontfix) ** Changed in: ubuntu-themes Importance: Undecided => Medium ** Changed in: ubuntu-themes Status: New => In Progress ** Changed in: ubuntu-themes (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/2018940 Title: ubuntu-mono icon theme contains Ubuntu One client icons. Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Ubuntu One file client services were shut down nine years ago. https://ubuntu.com/blog/shutting-down-ubuntu-one-file-services /ubuntu-mono-dark/status/24/ubuntuone-client-offline.svg /ubuntu-mono-dark/status/24/ubuntuone-client-idle.svg /ubuntu-mono-dark/status/24/ubuntuone-client-error.svg /ubuntu-mono-dark/status/24/ubuntuone-client-paused.svg /ubuntu-mono-dark/status/24/ubuntuone-client-updating.svg /ubuntu-mono-dark/status/22/ubuntuone-client-offline.svg /ubuntu-mono-dark/status/22/ubuntuone-client-idle.svg /ubuntu-mono-dark/status/22/ubuntuone-client-error.svg /ubuntu-mono-dark/status/22/ubuntuone-client-paused.svg /ubuntu-mono-dark/status/22/ubuntuone-client-updating.svg /ubuntu-mono-dark/status/16/ubuntuone-client-offline.svg /ubuntu-mono-dark/status/16/ubuntuone-client-idle.svg /ubuntu-mono-dark/status/16/ubuntuone-client-error.svg /ubuntu-mono-dark/status/16/ubuntuone-client-paused.svg /ubuntu-mono-dark/status/16/ubuntuone-client-updating.svg /ubuntu-mono-light/status/24/ubuntuone-client-offline.svg /ubuntu-mono-light/status/24/ubuntuone-client-idle.svg /ubuntu-mono-light/status/24/ubuntuone-client-error.svg /ubuntu-mono-light/status/24/ubuntuone-client-paused.svg /ubuntu-mono-light/status/24/ubuntuone-client-updating.svg /ubuntu-mono-light/status/22/ubuntuone-client-offline.svg /ubuntu-mono-light/status/22/ubuntuone-client-idle.svg /ubuntu-mono-light/status/22/ubuntuone-client-error.svg /ubuntu-mono-light/status/22/ubuntuone-client-paused.svg /ubuntu-mono-light/status/22/ubuntuone-client-updating.svg /ubuntu-mono-light/status/16/ubuntuone-client-offline.svg /ubuntu-mono-light/status/16/ubuntuone-client-idle.svg /ubuntu-mono-light/status/16/ubuntuone-client-error.svg /ubuntu-mono-light/status/16/ubuntuone-client-paused.svg /ubuntu-mono-light/status/16/ubuntuone-client-updating.svg I didn't remove these from my branch because I'm not sure if they are needed for something or if they were fully replaced by gnome-online- accounts' /usr/share/icons/hicolor/scalable/apps/goa-account- ubuntusso.svg and similar packages. /ubuntu-mobile/apps/scalable/ubuntuone.svg /ubuntu-mobile/apps/240/ubuntuone.png /ubuntu-mobile/apps/144/ubuntuone.png /suru-icons/apps/scalable/ubuntuone-symbolic.svg /suru-icons/apps/512/online-accounts-ubuntuones.png /suru-icons/apps/512/ubuntuone.png /suru-icons/apps/128/online-accounts-ubuntuones.png /suru-icons/apps/128/ubuntuone.png /suru-icons/apps/sources/ubuntuone.svg /suru-icons/apps/256/online-accounts-ubuntuones.png /suru-icons/apps/256/ubuntuone.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/2018940/+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 2018954] Re: 600+ duplicate icons exist in the ubuntu-themes packages including ubuntu-mono .
** Changed in: ubuntu-themes Assignee: (unassigned) => wontfix (wontfix) ** Changed in: ubuntu-themes Importance: Undecided => Medium ** Changed in: ubuntu-themes Status: New => In Progress ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/2018954 Title: 600+ duplicate icons exist in the ubuntu-themes packages including ubuntu-mono . Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Using find for duplicates shows 1099 duplicate or related to duplicate files between the packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/2018954/+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 2018945] Re: ubuntu-mono and ubuntu-mobile have 115 broken symlinks and 12 empty directories.
** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => wontfix (wontfix) ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-themes Status: New => In Progress ** Changed in: ubuntu-themes Assignee: (unassigned) => wontfix (wontfix) ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Triaged ** Changed in: ubuntu-themes Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/2018945 Title: ubuntu-mono and ubuntu-mobile have 115 broken symlinks and 12 empty directories. Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: Triaged Bug description: The 115 broken symlinks are in- /ubuntu-mono-dark/status/22/ /ubuntu-mono-dark/status/24/ /ubuntu-mobile/status/scalable/ Empty directories- /ubuntu-mono-dark/apps/48 /ubuntu-mono-dark/stock/32 /ubuntu-mono-dark/stock/128 /ubuntu-mono-dark/stock/24 /ubuntu-mono-dark/stock/16 /ubuntu-mono-dark/stock/48 /ubuntu-mono-light/apps/48 /ubuntu-mono-light/stock/32 /ubuntu-mono-light/stock/128 /ubuntu-mono-light/stock/24 /ubuntu-mono-light/stock/16 /ubuntu-mono-light/stock/48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/2018945/+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 2018935] Re: Amazon and Google+ icons exist in suru-icons and ubuntu-mobile packages.
** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => wontfix (wontfix) ** Changed in: ubuntu-themes (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/2018935 Title: Amazon and Google+ icons exist in suru-icons and ubuntu-mobile packages. Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: In Progress Bug description: This may be holdover from Ubuntu Touch or related desktop Amazon Unity scope integration around that time. /ubuntu-mobile/apps/scalable/amazon.svg /ubuntu-mobile/apps/240/amazon.png /ubuntu-mobile/apps/144/amazon.png /suru-icons/apps/scalable/amazon-symbolic.svg Google+ was sunset in 2018. https://www.blog.google/technology/safety-security/project-strobe/ /ubuntu-mobile/apps/symbolic/googleplus-symbolic.svg /suru-icons/apps/scalable/googleplus-symbolic.svg /suru-icons/apps/scalable/google-plus-symbolic.svg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/2018935/+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 480516] Re: software sources not appear
There has to be a fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/480516 Title: software sources not appear Status in Launchpad itself: Invalid Status in gconf package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Fix Released Bug description: for futher information see http://img20.imageshack.us/img20/7530/screenshot1zx.png the problem is "software sources" not appear even i run "gksu /usr/bin/software-properties-gtk".. root@se7en-laptop:/home/se7en# gksu /usr/bin/software-properties-gtk GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) (gksu:3681): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 110, in app = SoftwarePropertiesGtk(datadir=data_dir, options=options, file=file) File "/usr/lib/python2.6/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 122, in __init__ self.show_keys() File "/usr/lib/python2.6/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 716, in show_keys for key in self.apt_key.list(): File "/usr/lib/python2.6/dist-packages/softwareproperties/AptAuth.py", line 54, in list p = subprocess.Popen(self.list_opt,stdout=PIPE).stdout File "/usr/lib/python2.6/subprocess.py", line 621, in __init__ errread, errwrite) File "/usr/lib/python2.6/subprocess.py", line 1126, in _execute_child raise child_exception OSError: [Errno 8] Exec format error root@se7en-laptop:/home/se7en# To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/480516/+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 480516] Re: software sources not appear
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/480516 Title: software sources not appear Status in Launchpad itself: Invalid Status in gconf package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Fix Released Bug description: for futher information see http://img20.imageshack.us/img20/7530/screenshot1zx.png the problem is "software sources" not appear even i run "gksu /usr/bin/software-properties-gtk".. root@se7en-laptop:/home/se7en# gksu /usr/bin/software-properties-gtk GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) (gksu:3681): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 110, in app = SoftwarePropertiesGtk(datadir=data_dir, options=options, file=file) File "/usr/lib/python2.6/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 122, in __init__ self.show_keys() File "/usr/lib/python2.6/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 716, in show_keys for key in self.apt_key.list(): File "/usr/lib/python2.6/dist-packages/softwareproperties/AptAuth.py", line 54, in list p = subprocess.Popen(self.list_opt,stdout=PIPE).stdout File "/usr/lib/python2.6/subprocess.py", line 621, in __init__ errread, errwrite) File "/usr/lib/python2.6/subprocess.py", line 1126, in _execute_child raise child_exception OSError: [Errno 8] Exec format error root@se7en-laptop:/home/se7en# To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/480516/+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 2019496] Re: Security implications of SUDO_ASKPASS
Hello Heinrich, I suspect once you can set aliases in shells used by people with sudo privileges, the game is already over regardless of environment variables used. Is there something I'm missing where setting aliases in someone else's shell is fine except for this variable? Thanks -- 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/2019496 Title: Security implications of SUDO_ASKPASS Status in sudo package in Ubuntu: New Bug description: All that is needed to subvert sudo is adding this line to ~/.bashrc alias sudo="SUDO_ASKPASS=/home/$USER/.config/git/doevil sudo -A" and a program that reads the password from the command line and makes use of it. Ignoring the SUDO_ASKPASS environment variable would be an option to stop this. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2019496/+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 1457020] Re: x86_64-specific crash with one-word modulus
Lets set this to WONTFIX then; this isn't exactly a promise we won't get to it, but ideally any 14.04 LTS users affected by this would re-open or file a support request etc. ** Changed in: openssl (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1457020 Title: x86_64-specific crash with one-word modulus Status in openssl package in Ubuntu: Won't Fix Bug description: Hello, I'm trying to build nodejs 0.10.38 on Precise using the shared openssl but the tests fails[0]. An upstream patch[1] exists to fix this issue. Is it possible to provide it to precise? Regards. [0] https://github.com/joyent/node/issues/8050 [1] https://github.com/openssl/openssl/commit/eca441b2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1457020/+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 2019496] Re: Security implications of SUDO_ASKPASS
** Information type changed from Private Security to Public Security -- 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/2019496 Title: Security implications of SUDO_ASKPASS Status in sudo package in Ubuntu: New Bug description: All that is needed to subvert sudo is adding this line to ~/.bashrc alias sudo="SUDO_ASKPASS=/home/$USER/.config/git/doevil sudo -A" and a program that reads the password from the command line and makes use of it. Ignoring the SUDO_ASKPASS environment variable would be an option to stop this. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2019496/+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 2011458] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu8.1)
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu8.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: ganeti/3.0.2-3 (amd64, arm64, armhf, ppc64el) nova/3:27.0.0-0ubuntu1.1 (armhf) piuparts/1.1.7 (amd64, arm64, ppc64el, s390x) sbuild/0.85.0ubuntu2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#openssh [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Kinetic: Fix Committed Status in openssh source package in Lunar: Fix Committed Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running
[Touch-packages] [Bug 2017984] Re: Browser "Save as" dialog is not in dark mode
*** This bug is a duplicate of bug 2013126 *** https://bugs.launchpad.net/bugs/2013126 I'm having this issue with firefox and google chrome ** Attachment added: "Pasted image.png" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+attachment/5673673/+files/Pasted%20image.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017984 Title: Browser "Save as" dialog is not in dark mode Status in gtk+3.0 package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/gtk+3.0/+bug/2017984/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
jammy, lunary, and mantic: for distro in jammy lunar mantic ; do for component in main universe multiverse restricted ; do for-archive /srv/mirror/ubuntu/dists/$distro/$component/source/Sources.gz /srv/mirror/ubuntu/ ~/bin/for-archive-tools/unpack-search '/system- connections' ; done ; done | tee ~/system-connections-$(date +%d-%H:%M:%S) ** Attachment added: "system-connections-17-10:41:24" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2019940/+attachment/5673652/+files/system-connections-17-10%3A41%3A24 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: New Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Changed in: tzdata (Ubuntu Lunar) Status: New => Incomplete -- 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 python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Incomplete 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/python-tz/+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 2019022] Re: Bionic dep8 tests are failing
The bionic amd64 dep8 test run for 1.6.1-2ubuntu2.1: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/amd64/i/iptables/20230512_170407_f7c64@/log.gz Has all tests passing now: autopkgtest [17:04:01]: summary command1 PASS command2 PASS command3 PASS command4 PASS command5 PASS command6 PASS command7 PASS command8 PASS command9 PASS command10PASS command11PASS command12PASS command13PASS command14PASS command15PASS command16PASS command17PASS command18PASS command19PASS Bionic verification succeeded. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2019022 Title: Bionic dep8 tests are failing Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Committed Bug description: [ Impact ] This bug does not affect users directly, but it's a problem everytime iptables is SRUed to Bionic. We could hint the DEP8 tests, in which case they would all be ignored (uncluding the ones that actually work), or fix it. By itself, fixing DEP8 is not worth an SRU, but since we are fixing a segfault (in #1992454), we can ship the DEP8 fixes with it and make future SRUs easier and of better quality (since the tests now run correctly). The actual fixes are two: - since many iptables commands exit non-zero when the help parameter is given (-h/--help), instead of relying on that, we grep the output. Since bash's pipefail option is not set, it's the grep exit status that will be checked. - the iptables-compat-save is now being called with the -d (dump) option, which works for what the test wants, and doesn't exit 1 for no reason. Later versions of iptables have either flipped the exit status of the -h option (but not for all commands, annoyingly), so this fix is not needed after bionic. In other cases, the problematic test was just removed from d/t/control. [ Test Plan ] Verify in the autopkgtest report that the DEP8 tests ran and are all green. [ Where problems could occur ] This is fixing the existing DEP8 tests, which have been red for bionic since ever. If the fix fails, the tests will remain red, so no change. I'm assuming that the test goal of the multiple calls to iptables binaries with just the "-h/--help" option is to see if they run and don't crash. This is now being wrapped by a grep filter. If the iptables binary crashes, but still produces the expected help output, then it will be considered a green run, even though there was a problem. [ Other Info ] This fix is being included in the same upload as bug #1992454. [ Original Description] The Bionic DEP8 tests for iptables are in bad shape[1], even in the migration-reference/0 run. There are two types of failures: a) some commands have an exit status of 1 when called with the -h (for help) option, which is what some tests do b) iptables-compat-save (and its IPv6 counterpart) also exit with status 1, even when there are chains/tables to save I'll propose: a) grep the help output instead of relying on the exit status b) call the command with the -d (dump) option. That doesn't exit 0 in the success case, and actually dumps data when there are tables to do so 1. https://autopkgtest.ubuntu.com/packages/i/iptables/bionic/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019022/+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 2019023] Re: Fix shell test suite
Focal amd64 dep8 run: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/amd64/i/iptables/20230516_045413_de974@/log.gz It now contains a new dep8 test, labeled command17, which runs run- tests.sh: autopkgtest [04:53:52]: test command17: chmod +x ./iptables/tests/shell/testcases/chain/0006rename-segfault_0; cd iptables/tests/shell; ./run-tests.sh --host Which runs the shell test suite, including the test for bug #1992454: autopkgtest [04:53:52]: test command17: chmod +x ./iptables/tests/shell/testcases/chain/0006rename-segfault_0; cd iptables/tests/shell; ./run-tests.sh --host autopkgtest [04:53:52]: test command17: [--- I: [EXECUTING] ././testcases/arptables/0001-arptables-save-restore_0 [1A[KI: [OK] ././testcases/arptables/0001-arptables-save-restore_0 (...) I: [EXECUTING] ././testcases/chain/0006rename-segfault_0 [1A[KI: [OK] ././testcases/chain/0006rename-segfault_0 (...) And this suite passes: (...) I: [EXECUTING] ././testcases/nft-only/0003delete-with-comment_0 [1A[KI: [OK] ././testcases/nft-only/0003delete-with-comment_0 I: nft results: [OK] 41 [FAILED] 0 [TOTAL] 41 I: combined results: [OK] 82 [FAILED] 0 [TOTAL] 82 autopkgtest [04:54:00]: test command17: ---] autopkgtest [04:54:00]: test command17: - - - - - - - - - - results - - - - - - - - - - command17PASS Focal verification succeeded. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2019023 Title: Fix shell test suite Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Focal: Fix Committed Bug description: [ Impact ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests in focal only: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) The upstream fix includes other similar changes in other tests, but in the case of focal, the above is the minimal fix needed. Note that this shell test suite is not being run in focal, just in later ubuntu releases. But since the fix for #1992454 is adding such a test, I decided to fix the shell test run and add it to the existing DEP8 tests for focal via this bug, so we have test parity between focal and later ubuntu releases. 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 [ Test Plan ] Verify that the DEP8 tests now include a run-tests.sh test suite, and that it passes. [ Where problems could occur ] If the fix is incorrect, it would affect only the already-failing firewalld test. But in addition to fixing that test, we are now also including a full test run of all shell tests, something which wasn't being done for focal until now. While these tests are passing now, they could fail in a future iptables SRU, or turn out to be flaky. They are being run in ubuntu releases after focal, though, so that is a good sign. [ Other Info ] This fix is being included in the same upload as bug #1992454. [ Original Description ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
This upload proposes to remove some of the options in debian/tzdata.templates. So what happens if a user has configured deployment automation to use particular debconf options that will now disappear? The changelog says "It removes following time zones from debconf and updates them on upgrades again" but what about the reproducibility of previous behaviour on redeployments? This would apply to: America/ Argentina/ComodRivadavia Rosario Asia/ Hanoi Europe/ Uzhgorod Zaporozhye Pacific/ Enderbury -- 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 python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed 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/python-tz/+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 1992454] Autopkgtest regression report (iptables/1.8.7-1ubuntu5.1)
All autopkgtests for the newly accepted iptables (1.8.7-1ubuntu5.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nova/3:25.1.0-0ubuntu2.1 (armhf) systemd/249.11-0ubuntu3.9 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#iptables [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Committed Status in iptables source package in Focal: Fix Committed Status in iptables source package in Jammy: Fix Committed Status in iptables source package in Kinetic: Fix Committed Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy - Kinetic: iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 Alternatively, this test has been added to the DEP8 list of tests, and will be executed automatically once the package is accepted into proposed. The DEP8 logs can be inspected for its run. Look for a test named "0006rename-segfault". [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] The patch is also applied to lunar and mantic, but is fixed in upstream's 1.8.9 release which so far is only in debian testing/unstable. This is being uploaded together with test fixes from bug #1992454 (bionic-specific) and bug #2019023 (focal-specific), which were found and fixed while trying out the DEP8 runs for this package. To manage notifications about this bug go to:
[Touch-packages] [Bug 2017229] Re: Update evolution-data-server to 3.48.1
I have had evolution-data-server 3.48.1-0ubuntu1 installed on my Ubuntu 23.04 for a couple weeks. Evolution 3.48.1 and GNOME Calendar 44.0 work normally. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Lunar: Fix Committed Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
creating testing ppa https://launchpad.net/~hypothetical- lemon/+archive/ubuntu/lp2019856-util-linux ** Changed in: util-linux (Ubuntu Jammy) Assignee: (unassigned) => Heather Lemon (hypothetical-lemon) ** Changed in: util-linux (Ubuntu Lunar) Assignee: (unassigned) => Heather Lemon (hypothetical-lemon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: New Status in util-linux source package in Lunar: New Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same issue on LG Gram 17Z90R - no audio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1750051] Re: cron doesn't support MAILFROM
Hi what is the status of this bug? It says " Fix Released " does that mean it is fixed, is so what version? I am using Ubuntu 22.04.1 LTS and I cannot get cron to accept the MAILFROM directive. No matter what I do it always defaults to root. Unfortunately I can't get any notification from cron without properly filling out this field. The man page says it should work. I have spend many hours trying to get this to work and looking for work around. Please confirm the status of this bug, if it has indeed been fixed and if so what version. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1750051 Title: cron doesn't support MAILFROM Status in cron package in Ubuntu: Triaged Status in cron package in Debian: Fix Released Bug description: Ubuntu's cron version doesn't support setting MAILFROM to set the "From:" header of cron generated emails. This feature would be nice to have and bring parity with RHEL/CentOS which has it since RHEL 6: $ cat /etc/redhat-release CentOS release 6.6 (Final) $ man 5 crontab | grep -1 FROM doesn´t do aliasing, and UUCP usually doesn´t read its mail. If MAIL- FROM is defined (and non-empty), it will be used as the envelope sender address, otherwise, ‘‘root’’ will be used. $ apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 16 15:52:54 2018 InstallationDate: Installed on 2016-12-06 (436 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+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 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS
Hi, Thank you for taking the time to report this issue and providing a reproducer. Unfortunately I have not succeeded in reproducing the issue. In a fresh jammy container, using "OPENSSL_BRANCH=openssl-3.0.3 scripts/fullbuild.sh", I then ran "ln -s oqsprovider.so _build/lib/oqsprovider2.so" which gave me the layout below: root@jammy:~/oqs-provider# ls -l _build/lib/ total 6472 lrwxrwxrwx 1 root root 14 May 17 15:39 oqsprovider2.so -> oqsprovider.so lrwxrwxrwx 1 root root 16 May 17 15:32 oqsprovider.so -> oqsprovider.so.1 -rwxr-xr-x 1 root root 6625696 May 17 15:32 oqsprovider.so.0.5.0-dev lrwxrwxrwx 1 root root 24 May 17 15:32 oqsprovider.so.1 -> oqsprovider.so.0.5.0-dev and then root@jammy:~/oqs-provider# OPENSSL_MODULES=_build/lib/ OPENSSL_CONF=scripts/o-ca.cnf ./.local/bin/openssl version OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) which didn't crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2019970 Title: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS Status in openssl package in Ubuntu: New Bug description: Full bug report at https://github.com/openssl/openssl/issues/20981 No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2019970/+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 2015562] Re: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream)
** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/442007 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2015562 Title: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream) Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: In Progress Bug description: Hi folks, I've been using dnsmasq for my home DNS needs, which includes returning null entries for certain domain queries. The specific case in which I found this segfault was returning null records for Netflix (to ensure Netflix does not try to use my IPv6 tunnel to egress traffic through). I've been using very simple configuration snippet to achieve this, this is attached as netflix-nov6.conf (the full file contains more entries). Ever since I've upgraded from Ubuntu 20.04 to 22.04, dnsmasq kept segfaulting at random occasions. I also attempted do an apt update&, but there are no newer versions of this package available. Further research into this issue showed that a surefire way to trigger this segfault was to go to a website blocked via this method (for testing purposes, a dig query works quite well). The segfault can be reproduced reliably, and always occurs after one or a few queries towards the "blocked" domain entries. I found a commit in the upstream dnsmasq git repo which seems to fix this issue, the fix made it into 2.87: https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=de372d6914ae20a1f9997815f258efbf3b14c39b Would it be possible to backport this into the version used in the current LTS Ubuntu release? Thanks! -- $ lsb_release -d Description: Ubuntu 22.04.2 LTS $ apt-cache policy dnsmasq dnsmasq: Installed: 2.86-1.1ubuntu0.2 Candidate: 2.86-1.1ubuntu0.2 Version table: *** 2.86-1.1ubuntu0.2 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 100 /var/lib/dpkg/status 2.86-1.1ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 2.86-1.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages -- Excerpt from the dnsmasq logs, with debugging enabled, after I loaded fast.com: Apr 07 13:47:41 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Apr 07 13:47:42 budgie dnsmasq[109976]: query[type=65] fast.dradis.netflix.com from 192.168.10.82 Apr 07 13:47:42 budgie dnsmasq[109976]: config error is REFUSED (EDE: network error) Apr 07 13:47:43 budgie dnsmasq[109976]: query[type=65] ichnaea-web.netflix.com from 192.168.10.82 Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Failed with result 'core-dump'. Core dump is also attached. Reproduction steps: - 1. Install dnsmasq on Ubuntu 22.04 (or any Ubuntu release using dnsmasq 2.86) - 1.5. Configure one or multiple DNS servers for dnsmasq - 2. Copy netflix-nov6.conf into /etc/dnsmasq.d/ - 3. Restart/reload dnsmasq - 3.5 Verify that dnsmasq resolves domains correctly: root@budgie:~# dig +short -tA ubuntu.com @127.0.0.1 185.125.190.21 185.125.190.20 185.125.190.29 root@budgie:~# dig +short -t ubuntu.com @127.0.0.1 2620:2d:4000:1::28 2620:2d:4000:1::26 2620:2d:4000:1::27 - 4. Perform a type65 / HTTPS recordtype query for netflix.com towards the dnsmasq server once or twice: root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1 root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1 ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached - 5. Check logs to verify segfault: Apr 07 14:03:28 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Apr 07 14:03:32 budgie dnsmasq[111585]: query[type=65] netflix.com from 127.0.0.1 Apr 07 14:03:32 budgie dnsmasq[111585]: config error is REFUSED (EDE: network error) Apr 07 14:03:33 budgie dnsmasq[111585]: query[type=65] netflix.com from 127.0.0.1 Apr 07 14:03:33 budgie systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Apr 07 14:03:33 budgie systemd[1]: dnsmasq.service: Failed with result 'core-dump'. -- netflix-nov6.conf: # Null response on these domains server=/netflix.com/# address=/netflix.com/:: server=/netflix.net/# address=/netflix.net/:: server=/nflxext.com/# address=/nflxext.com/:: To manage notifications about this bug go to:
[Touch-packages] [Bug 2018342] Re: Undefined symbol nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2018342 Title: Undefined symbol nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation Status in curl package in Ubuntu: Confirmed Bug description: I updated Ubuntu from 22.10 to 23.04 this morning and have this issue when NetworkManager starts : > NetworkManager: symbol lookup error: /lib/x86_64-linux-gnu/libcurl- gnutls.so.4: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation I tried to remove/reinstall libcurl and network-manager and all dependencies. I created this ticket on the Curl repo : https://github.com/curl/curl/tree/d8df0d6db7441b6e14920a7e16a10e32bdc9c7ae It was close because : > This is not a curl bug. This is libcurl having been built with an nghttp2 version >= 1.50.0 (which has that function) and then at run- time it uses an older nghttp2 library that doesn't have the function. Versions : libcurl4 : 7.88.1-8ubuntu1 libcurl3-gnu-tls : 7.88.1-8ubuntu1 libnghttp2-dev : 1.52.0-1 libnghttp2-14 : 1.52.0-1 network-manager : 1.42.4 operating system : Linux ubuntu 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2018342/+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 2019970] [NEW] OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS
Public bug reported: Full bug report at https://github.com/openssl/openssl/issues/20981 No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any more. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2019970 Title: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS Status in openssl package in Ubuntu: New Bug description: Full bug report at https://github.com/openssl/openssl/issues/20981 No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2019970/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Changed in: python-tz (Ubuntu Kinetic) Status: New => Invalid ** Changed in: python-tz (Ubuntu Jammy) Status: New => Invalid ** Changed in: python-tz (Ubuntu Focal) Status: New => Invalid -- 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 python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed 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/python-tz/+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 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
Both the Apparmor MR on GitLab to support 'nostrictatime', 'lazytime', and 'nolazytime' (https://gitlab.com/apparmor/apparmor/-/merge_requests/1005), and the snapd PR to support 'nofail' and other userspace and fs-specific mount options (https://github.com/snapcore/snapd/pull/12712) have been merged into their respective master branches. The snapd changes will be backported into the 2.59 release as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: Fix Committed Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created
** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2010561 Title: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created Status in netplan: Invalid Status in network-manager package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a WiFi adapter. (I used Lubuntu Lunar.) 2. Connect to WiFi and install all updates. 3. Enable the Netplan Everywhere PPA and install the updated NetworkManager from it (further details at https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3) 4. When the installation finishes, run "sudo netplan get". Expected result: Networking information related to the WiFi connection should appear in the "sudo netplan get" output. Actual result: "sudo netplan get" returns the following: ** (process:4088): WARNING **: 12:41:41.394; Permissions for /etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration should NOT be accessible by others. network: version: 2 renderer: NetworkManager End of output. Additionally, the /etc/netplan folder does not contain files that I would expect to be there that would contain the networking info. Additional information: If I disconnect from WiFi, then delete my WiFi connection entirely in nmtui, and *then* reconnect to the same WiFi network, "sudo netplan get" returns the expected networking information. /etc/netplan is also properly populated after doing this. This bug seems like it will probably cause unintended behavior after an upgrade from 23.04 (which uses normal NetworkManager) to 23.10 (which is supposed to be using the Netplan Everywhere NetworkManager). People probably won't know to entirely delete the WiFi and other connections and then reconnect them in order for the netplan output to be usable. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2010561/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
We should run the same query on the Ubuntu archive, too. The security team (sespiros / sarnold) might be able to help with this in the future. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: New Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2018731] Re: Graphics memory (VRAM) leak in mutter-x11-frames
Upstream thinks this should be fixed in mutter 44.1, but we're yet to confirm. ** No longer affects: xorg (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2816 https://gitlab.gnome.org/GNOME/mutter/-/issues/2816 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2816 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Tags added: nvidia ** Tags added: gnome-shell-leak -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2018731 Title: Graphics memory (VRAM) leak in mutter-x11-frames Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: I'm seeing degraded performance with NVIDIA Geforce 3008 Mobile and two screens. After launching nvidia-smi, I can clearly see that there's a memory leak in mutter-x11-frames, which uses around 10-12 GB of VRAM. nvidia-drivers-525 Ubuntu 23.04 X11 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 8 14:28:13 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (87 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (18 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/mutter/+bug/2018731/+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 2018706] Re: Second Monitor not detected
> I just use nvidia Graphics. It appears the opposite is true. Only the built-in Intel GPU is active so any secondary monitor connected to the Nvidia GPU won't work... Please open the 'Additional Drivers' app and use it to reinstall the Nvidia driver. Try choosing one that's not the "Open" Nvidia driver. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Second Monitor not detected + Nvidia Xorg driver not installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2018706 Title: Nvidia Xorg driver not installed Status in Ubuntu: Incomplete Bug description: I just use nvidia Graphics. Before i changed it from xorg i can use my second monitor but after i change it, update it.I can't use my second monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX Open Kernel Module for x86_64 530.41.03 Release Build (dvs-builder@U16-T02-35-3) Thu Mar 16 19:33:35 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 8 06:58:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] [1d05:1099] NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited TU117M [GeForce GTX 1650 Ti Mobile] [1d05:1099] InstallationDate: Installed on 2022-12-05 (153 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: MONSTER ABRA A5 V15.10 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=49c05d00-8d9a-4953-9075-be6351ac7576 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07 dmi.board.asset.tag: Standard dmi.board.name: ABRA A5 V15.10 dmi.board.vendor: MONSTER dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: MONSTER dmi.chassis.version: Standard dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07:bd09/08/2020:br5.17:efr1.19:svnMONSTER:pnABRAA5V15.10:pvrStandard:rvnMONSTER:rnABRAA5V15.10:rvrStandard:cvnMONSTER:ct10:cvrStandard:sku0001: dmi.product.family: CML dmi.product.name: ABRA A5 V15.10 dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: MONSTER nvidia-settings: ERROR: A query to find an object was unsuccessful 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/+bug/2018706/+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 2018363] Re: Sony LE_WH-1000XM5 Connection button is disabled in Bluetooth settings
** Summary changed: - Connection button is disabled in Bluetooth settings + Sony LE_WH-1000XM5 Connection button is disabled in Bluetooth settings ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => New ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2018363 Title: Sony LE_WH-1000XM5 Connection button is disabled in Bluetooth settings Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Device appears as paired but the Connection button is disabled. I can't click the button to connect the device. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-09-28 (222 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 21D8CTO1WW Package: gnome-control-center PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=20c02ac6-394b-416e-8c15-f3f909240844 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (17 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev root sambashare sudo _MarkForUpload: True dmi.bios.date: 03/09/2023 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: N3EET29W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrN3EET29W(1.15):bd03/09/2023:br1.15:efr1.12:svnLENOVO:pn21D8CTO1WW:pvrThinkPadP15vGen3:rvnLENOVO:rn21D8CTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D8_BU_Think_FM_ThinkPadP15vGen3: dmi.product.family: ThinkPad P15v Gen 3 dmi.product.name: 21D8CTO1WW dmi.product.sku: LENOVO_MT_21D8_BU_Think_FM_ThinkPad P15v Gen 3 dmi.product.version: ThinkPad P15v Gen 3 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:E9:F7:5A:31:C3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:20013 acl:0 sco:0 events:3219 errors:0 TX bytes:790999 acl:0 sco:0 commands:3217 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2018363/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
** Changed in: ltsp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: New Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2019939] Re: Outdated documentation about NetworkManager keyfiles
** Tags added: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019939 Title: Outdated documentation about NetworkManager keyfiles Status in debian-handbook package in Ubuntu: New Status in dhcpcanon package in Ubuntu: New Status in fai package in Ubuntu: New Status in gnome-user-docs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in wifi-qr package in Ubuntu: New Bug description: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
netcfg is not part of Ubuntu anymore (got dropped post Focal) ** Changed in: netcfg (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: New Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: New Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
Netplan deals with keyfiles in /run/NetworkManager/system-connections not /etc/... ** Changed in: netplan.io (Ubuntu) Status: New => Won't Fix ** Tags added: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: New Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: New Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2019940] [NEW] Directly manipulating NetworkManager keyfiles
Public bug reported: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 ** Affects: augeas (Ubuntu) Importance: Undecided Status: New ** Affects: calamares (Ubuntu) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: cruft-ng (Ubuntu) Importance: Undecided Status: New ** Affects: dracut (Ubuntu) Importance: Undecided Status: New ** Affects: forensic-artifacts (Ubuntu) Importance: Undecided Status: New ** Affects: guestfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: guix (Ubuntu) Importance: Undecided Status: New ** Affects: ltsp (Ubuntu) Importance: Undecided Status: New ** Affects: netcfg (Ubuntu) Importance: Undecided Status: Won't Fix ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: Won't Fix ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: refpolicy (Ubuntu) Importance: Undecided Status: New ** Affects: sosreport (Ubuntu) Importance: Undecided Status: New ** Affects: uhd (Ubuntu) Importance: Undecided Status: New ** Affects: vagrant (Ubuntu) Importance: Undecided Status: New ** Tags: netplan-everywhere rls-mm-incoming ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: netcfg (Ubuntu) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu) Importance: Undecided Status: New ** Also affects: calamares (Ubuntu) Importance: Undecided Status: New ** Also affects: guestfs-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: cruft-ng (Ubuntu) Importance: Undecided Status: New ** Also affects: guix (Ubuntu) Importance: Undecided Status: New ** Also affects: refpolicy (Ubuntu) Importance: Undecided Status: New ** Also affects: augeas (Ubuntu) Importance: Undecided Status: New ** Also affects: ltsp (Ubuntu) Importance: Undecided Status: New ** Also affects: forensic-artifacts (Ubuntu) Importance: Undecided Status: New ** Also affects: dracut (Ubuntu) Importance: Undecided Status: New ** Also affects: uhd (Ubuntu) Importance: Undecided Status: New ** Also affects: vagrant (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: New Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: New Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2019927] Re: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error e
zstd: error 70 : Write error : cannot write block : No space left on device bpool/BOOT/ubuntu_bpduzc 663296 655744 7552 99% /boot Your boot partition is far too small. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2019927 Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This bug report showed up after rebooting first time to 23.04. I have not yet noticed anything actually broken in the system, but uptime is only 6 minutes. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 16 23:41:05 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-21 (786 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bpduzc@/vmlinuz-6.2.0-20-generic root=ZFS=rpool/ROOT/ubuntu_bpduzc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-17 (0 days ago) dmi.bios.date: 09/16/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA 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.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.307:bd09/16/2020:br5.16:efr3.7:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2019927/+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 2019939] [NEW] Outdated documentation about NetworkManager keyfiles
Public bug reported: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 ** Affects: debian-handbook (Ubuntu) Importance: Undecided Status: New ** Affects: dhcpcanon (Ubuntu) Importance: Undecided Status: New ** Affects: fai (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-l2tp (Ubuntu) Importance: Undecided Status: New ** Affects: wifi-qr (Ubuntu) Importance: Undecided Status: New ** Tags: netplan-everywhere rls-mm-incoming ** Also affects: debian-handbook (Ubuntu) Importance: Undecided Status: New ** Description changed: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ + + PS: Packages were queried using: + https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 ** Also affects: wifi-qr (Ubuntu) Importance: Undecided Status: New ** Also affects: fai (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Also affects: dhcpcanon (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-l2tp (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Netplan Everywhere: Outdated documentation about NetworkManager keyfiles + Outdated documentation about NetworkManager keyfiles -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019939 Title: Outdated documentation about NetworkManager keyfiles Status in debian-handbook package in Ubuntu: New Status in dhcpcanon package in Ubuntu: New Status in fai package in Ubuntu: New Status in gnome-user-docs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in wifi-qr package in Ubuntu: New Bug description: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
** Changed in: ayatana-indicator-messages (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: ayatana-indicator-messages (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 1990089] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.33-1ubuntu2 (i386) mir/2.7.0-0ubuntu3 (armhf) mutter/42.5-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode Status in Linux: New Status in Mutter: Fix Released Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Status in mesa source package in Kinetic: Won't Fix Status in mesa source package in Lunar: Fix Released Bug description: [Impact] Running stress-ng freezes the screen under wayland on intel iris. Upstream has fixed it in 5aae8a05264c354aa93017d323ce238858f68227 iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM 646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if kernel can't allocate memory" which need to be backported for 22.2.5 [Test case] Install the update, then 1. stress-ng --stack 0 --timeout 300 2. check the screen and note that it shouldn't freeze anymore. [Where things could go wrong] This moves checking ENOMEM to the right place, so it's hard to see how it might cause issues. -- [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from
[Touch-packages] [Bug 2003339] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.33-1ubuntu2 (i386) mir/2.7.0-0ubuntu3 (armhf) mutter/42.5-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2017142] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.33-1ubuntu2 (i386) mir/2.7.0-0ubuntu3 (armhf) mutter/42.5-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 2015962] Proposed package upload rejected
An upload of ayatana-indicator-messages to lunar-proposed has been rejected from the upload queue for the following reason: "Rejecting from the queue as this is still missing SRU information, and that should notify someone who cares :). The diff itself looks fine, although the it now also needs fixing in mantic and the lunar upload needs a non- conflicting version number. Please feel free to reupload with those fixed.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
This bug is about the open source nouveau driver only. The issue in comment #38 is covered in bug 938751. -- 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/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.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: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 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/linux/+bug/1969959/+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 2019929] Re: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
As already said, this was due to configuration of my machine ** Changed in: pam (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/pam/+question/706672 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2019929 Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: Invalid Bug description: Upgrade from Ubuntu 20.04 to 22.04 which created and error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 17 09:02:11 2023 Ec2AMI: ami-00026187 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: b2-30 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2023-05-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2019929/+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 2019929] Re: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Well the problem was because of usage of pam_tally on the configuration, so it was correctly stopping the upgrade process. But this could have been dynamically by disabling this as well. But I resolve the problem manually by disabling the module -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2019929 Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: Invalid Bug description: Upgrade from Ubuntu 20.04 to 22.04 which created and error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 17 09:02:11 2023 Ec2AMI: ami-00026187 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: b2-30 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2023-05-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2019929/+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 2019929] Re: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2019929 Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: New Bug description: Upgrade from Ubuntu 20.04 to 22.04 which created and error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 17 09:02:11 2023 Ec2AMI: ami-00026187 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: b2-30 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2023-05-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2019929/+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 2019929] [NEW] package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Public bug reported: Upgrade from Ubuntu 20.04 to 22.04 which created and error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 17 09:02:11 2023 Ec2AMI: ami-00026187 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: b2-30 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2023-05-17 (0 days ago) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2019929 Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: New Bug description: Upgrade from Ubuntu 20.04 to 22.04 which created and error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 17 09:02:11 2023 Ec2AMI: ami-00026187 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: b2-30 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2023-05-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2019929/+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 2019927] Re: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error e
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2019927 Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This bug report showed up after rebooting first time to 23.04. I have not yet noticed anything actually broken in the system, but uptime is only 6 minutes. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 16 23:41:05 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-21 (786 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bpduzc@/vmlinuz-6.2.0-20-generic root=ZFS=rpool/ROOT/ubuntu_bpduzc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-17 (0 days ago) dmi.bios.date: 09/16/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA 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.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.307:bd09/16/2020:br5.16:efr3.7:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2019927/+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 2019927] [NEW] package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error
Public bug reported: This bug report showed up after rebooting first time to 23.04. I have not yet noticed anything actually broken in the system, but uptime is only 6 minutes. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 16 23:41:05 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-21 (786 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bpduzc@/vmlinuz-6.2.0-20-generic root=ZFS=rpool/ROOT/ubuntu_bpduzc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-17 (0 days ago) dmi.bios.date: 09/16/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA 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.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.307:bd09/16/2020:br5.16:efr3.7:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2019927 Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This bug report showed up after rebooting first time to 23.04. I have not yet noticed anything actually broken in the system, but uptime is only 6 minutes. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 16 23:41:05 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-21 (786 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bpduzc@/vmlinuz-6.2.0-20-generic root=ZFS=rpool/ROOT/ubuntu_bpduzc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-17 (0 days ago) dmi.bios.date: 09/16/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA 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
