[Touch-packages] [Bug 1979850] Re: libudev-dev version 249.11-0ubuntu3.1 is missing in the repository
*** This bug is a duplicate of bug 1979244 *** https://bugs.launchpad.net/bugs/1979244 I also have this issue on 22.04: I am trying to install libudev-dev to compile logiops, but my up to date system has libudev1 (249.11-0ubuntu3.7). Error below. -- Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libudev-dev : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.7 is to be installed E: Unable to correct problems, you have held broken packages. -- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979850 Title: libudev-dev version 249.11-0ubuntu3.1 is missing in the repository Status in systemd package in Ubuntu: Confirmed Bug description: The mentioned version is missing, hence preventing an installation of the -dev package into an up-to-date system. If I would force version 249.11-0ubuntu3.3 of libudev1 and libudev- dev, it would remove essential parts of my system. ~$ sudo apt install libudev-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libudev-dev : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.1 is to be installed E: Unable to correct problems, you have held broken packages. ~$ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 ~$ apt-cache policy libudev-dev libudev-dev: Installed: (none) Candidate: 249.11-0ubuntu3 Version table: 249.11-0ubuntu3.3 1 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ~$ apt-cache policy libudev1 libudev1: Installed: 249.11-0ubuntu3.1 Candidate: 249.11-0ubuntu3.1 Version table: 249.11-0ubuntu3.3 1 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages *** 249.11-0ubuntu3.1 100 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libudev-dev (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 24 23:04:19 2022 InstallationDate: Installed on 2020-07-20 (704 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to jammy on 2022-05-03 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1979850/+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 1998267] Re: glib not aware of snap confinement
Correct, this fix is valuable for core22, so kinetic was skipped. There should be no issues for anyone updating from jammy to kinetic. Though this will affect core20, we expect most snaps to be using core22 so no plan to backport it to focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Released Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 1998267] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Released Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 1998267] Re: glib not aware of snap confinement
This bug was fixed in the package glib2.0 - 2.72.4-0ubuntu2 --- glib2.0 (2.72.4-0ubuntu2) jammy; urgency=medium * d/p/0001-gio-Make-portal-support-aware-of-snaps.patch: - Make portal support aware of snaps (LP: #1998267) -- Robert Ancell Wed, 22 Mar 2023 15:52:13 +1300 ** Changed in: glib2.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Released Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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] Re: ssh fails to rebind when it is killed with -HUP
I triggered a DEP8 run in the proper infrastructure[1], and the test failed as expected: autopkgtest [21:32:30]: test systemd-socket-activation: [--- Fail: ssh.socket: expected SubState=listening, but got SubState=running autopkgtest [21:32:31]: test systemd-socket-activation: ---] autopkgtest [21:32:31]: test systemd-socket-activation: - - - - - - - - - - results - - - - - - - - - - systemd-socket-activation FAIL non-zero exit status 1 autopkgtest [21:32:31]: summary regress PASS systemd-socket-activation FAIL non-zero exit status 1 I don't know why it didn't fail when I ran autopkgtest locally against a container, but hey, sanity half restored ;) 1. https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ahasenack- ssh-rexec-sru/lunar/amd64/o/openssh/20230427_213242_59dbf@/log.gz -- 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: In Progress Status in openssh source package in Kinetic: In Progress 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[116
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
I verified that the test was executed according to the [test plan]. I understand kinetic is not part of this SRU. The reason wasn't explained anywhere, but I'm assuming it's because it's a) ending support soon; and/or b) this glib update is more useful for core22 snap and core desktop deployments, which are 22.04 only (am I correct?). That being said, of course it will also be available to regular 22.04 desktops, so it must not break that scenario. And this was tested in comment #9. The package built correctly in all architectures and Ubuntu releases it was meant for. There are no DEP8 regressions, or they were fixed. There is no SRU freeze ongoing at the moment. There is no halted phasing on the previous update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Released Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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] Re: ssh fails to rebind when it is killed with -HUP
I grabbed this for my SRU shift, but quickly realized reviewing this patch is more complicated than I thought. I concentrated a bit more on the DEP8 test then. I confess I don't understand how this check is passing: # Check that ssh.service is currently inactive/dead. assert_unit_property ssh.service "ActiveState=inactive" assert_unit_property ssh.service "SubState=dead" Because autopkgtest just connected to the vm/container over ssh to run this test, so the ssh.service must be active at this point. When I run this test script in a local container, over ssh, the test fails on the above check, as I expected. But when I throw autopkgtest at it, locally, it passes the check (and I ran it with bash -x to confirm the state of ssh.service). How? On a review note about the test, if you happen to need to reupload this for whatever reason, I would suggest that you also add some output explaining what is being tested. The comments you have just before each assert are a great example. -- 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: In Progress Status in openssh source package in Kinetic: In Progress 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)
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
Yes, these specific steps performed in a core desktop VM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 2017927] Re: Failed to start SLAPD and B&R operation failed in ansible
** Package changed: update-manager (Ubuntu) => openldap (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2017927 Title: Failed to start SLAPD and B&R operation failed in ansible Status in openldap package in Ubuntu: New Bug description: Ldap conf is pointing to itself as the provider in sync-replication directive hence the restore is failing. Getting the below error while executing ansible playbook for restore. stdout: 'Starting SLAPD: Failed to start SLAPD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2017927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017926] [NEW] Unused content snaps not autoremoved
Public bug reported: $ snap connections --all | grep gnome content - gnome-3-28-1804:gnome-3-28-1804 - content - gnome-3-34-1804:gnome-3-34-1804 - content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-42-2204]mattermost-desktop:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snap-store:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snapd-desktop-integration:gnome-42-2204 gnome-42-2204:gnome-42-2204 - my system has 4 gnome-* content snaps, that were pulled in as dependencies. The apps that used them, have moved on to newer versions. Something on my system must clean then up for me, for example apt autoremoves automatically installed packages & obsolete kernels, and so should also happen with snaps. It can be done by snapd itself, or by something else on the classic desktop - i.e. update-manager. Note it is easy to detect such snaps, as it provides no apps; has content interface only; which is not plugged by anything. If it is ever needed by any future or past revision of any other snap it would be autoinstalled back. On my system they take up 824M of disk space (2 revisions, of 2 unused content snaps = 4 snaps) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Description changed: $ snap connections --all | grep gnome content - gnome-3-28-1804:gnome-3-28-1804 - content - gnome-3-34-1804:gnome-3-34-1804 - content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gnome-42-2204]mattermost-desktop:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snap-store:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gnome-42-2204]snapd-desktop-integration:gnome-42-2204 gnome-42-2204:gnome-42-2204 - - - my system has 4 gnome-* content snaps, that were pulled in as dependencies. The apps that used them, have moved on to newer versions. Something on my system must clean then up for me, for example apt autoremoves automatically installed packages & obsolete kernels, and so should also happen with snaps. + my system has 4 gnome-* content snaps, that were pulled in as + dependencies. The apps that used them, have moved on to newer versions. + Something on my system must clean then up for me, for example apt + autoremoves automatically installed packages & obsolete kernels, and so + should also happen with snaps. It can be done by snapd itself, or by something else on the classic desktop - i.e. update-manager. Note it is easy to detect such snaps, as it provides no apps; has content interface only; which is not plugged by anything. If it is ever needed by any future or past revision of any other snap it would be autoinstalled back. + + On my system they take up 824M of disk space (2 revisions, of 2 unused + content snaps = 4 snaps) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017926 Title: Unused content snaps not autoremoved Status in snapd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: $ snap connections --all | grep gnome content - gnome-3-28-1804:gnome-3-28-1804 - content - gnome-3-34-1804:gnome-3-34-1804 - content[gnome-3-38-2004] chromium:gnome-3-38
[Touch-packages] [Bug 2017924] [NEW] package libssl1.1 1.1.1f-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from oth
Public bug reported: cannot install unifi network controller due unspecified unmet dependencies ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libssl1.1 1.1.1f-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 AptOrdering: libssl1.1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 27 12:18:31 2023 DpkgTerminalLog: Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2.18_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1f-1ubuntu2.18) over (1.1.1f-1ubuntu2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2.18_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 InstallationDate: Installed on 2021-03-05 (782 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: openssl Title: package libssl1.1 1.1.1f-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/2017924 Title: package libssl1.1 1.1.1f-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 Status in openssl package in Ubuntu: New Bug description: cannot install unifi network controller due unspecified unmet dependencies ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libssl1.1 1.1.1f-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 AptOrdering: libssl1.1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 27 12:18:31 2023 DpkgTerminalLog: Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2.18_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1f-1ubuntu2.18) over (1.1.1f-1ubuntu2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2.18_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 InstallationDate: Installed on 2021-03-05 (782 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: openssl Title: package libssl1.1 1.1.1f-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2017924/+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 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
Tried with the oldest and newest kernels available in mainline (6.0.0 and 6.3.0). Same problem. Same ipc errors in dmesg. -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
Attempted a variety of things that I found on the internet for similar problems: Various options to alsa-base.conf (tried them individually): /etc/modprobe.d/alsa-base.conf options snd-hda-intel model=auto options snd-hda-intel model=generic options snd_sof sof_debug=128 options snd_sof sof_debug=1 (also tried the last 2 in /etc/modprobe.d/sof.conf) Tried these via grub and also via alsa-base.conf options GRUB_CMDLINE_LINUX_DEFAULT="quiet splash snd_hda_intel.dmic_detect=0" or GRUB_CMDLINE_LINUX_DEFAULT="quiet splash snd_intel_dspcfg.dsp_driver=1 (and/or with different values, 0-3) No improvement with any of these experiments. -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
I mean 22.04.2 LTS, not 22.03.2 LTS -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-gener
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
Here is the dmesg log from 22.03.2 LTS. The sound works great on that release. There are no tx/HW params/AsoC errors as seen in dmesg with 23.04. [3.608109] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [3.632029] sof-audio-pci-intel-tgl :00:1f.3: NHLT table not found [3.632076] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4 [3.633075] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:0:0-b678a [3.633080] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:21:0 [3.633085] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [3.727188] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:0:0-b678a [3.727194] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:21:0 [3.755011] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:20:0 Kernel ABI 3:21:0 [3.755271] sof_rt5682 tgl_mx98373_rt5682: ASoC: Parent card not yet available, widget card binding deferred [3.806335] snd_hda_codec_hdmi ehdaudio0D2: ASoC: sink widget AIF1TX overwritten [3.806345] snd_hda_codec_hdmi ehdaudio0D2: ASoC: source widget AIF1RX overwritten [3.818001] max98373 i2c-MX98373:00: Reset completed (retry:0) [3.832402] max98373 i2c-MX98373:01: Reset completed (retry:0) [3.859800] input: sof-rt5682 Headset Jack as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input9 [3.859880] input: sof-rt5682 HDMI/DP,pcm=2 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input10 [3.859946] input: sof-rt5682 HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input11 [3.860059] input: sof-rt5682 HDMI/DP,pcm=4 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input12 [3.860094] input: sof-rt5682 HDMI/DP,pcm=5 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input13 -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
Hello Robert, the [test plan] has very specific steps involving the calculator, gsettings, and an expected result. Did you perform those specifically? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Tim Andersson (andersson123) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: In Progress Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 2017846] Re: System kept waking up after pressing power button
Can you please attach logs from systemd-logind? $ journalctl -u systemd-logind.service -b 0 > systemd-logind-log.txt ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
May be worth mentioning that I previously was running 22.04 LTS, and the sound worked just fine on initial install, and through all the updates. -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-bas
[Touch-packages] [Bug 1992688] Re: firefox deb not installed
Brian promised to update the description with the required SRU information. On this note I have accepted the upload into jammy- proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1992688] Re: firefox deb not installed
Hello Brian, or anyone else affected, Accepted ubuntu-meta into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.481.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017898] [NEW] MESA 22.2 Regression Causes Kwin Crashes (Fix Available)
Public bug reported: MESA 22.2 contains a malfunction which causes kwin to exit regularly / frequently, leaving the system without window management. This is a regression compared to MESA 22.1 and fixed again in MESA 22.3. See following MESA bug: * https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 * just for reference, corresponding KDE Bugtracker entry: https://bugs.kde.org/show_bug.cgi?id=461316 Maybe the fix could be backported? It currently is something between inconvenient (for very technically savy users) and rendering the system unusable (for less technically savy users - suddenly, Window Management will be gone and switching windows, accessing panels, and controlling most applications even if they are in foreground at the time of a crash become impossible). ProblemType: Bug DistroRelease: KDE neon 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Apr 27 14:26:47 2023 DistUpgraded: 2020-10-11 12:05:38,766 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-40-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=/dev/mapper/ubuntu--vg--970-root ro resume=/dev/ubuntu-vg-970/swap fsck.mode=force rd.driver.blacklist=nouveau pcie_aspm=off RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2020-10-11 (928 days ago) dmi.bios.date: 11/10/2022 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-0xneon+22.04+jammy+release+build8 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017898 Title: MESA 22.2 Regression Causes Kwin Crashes (Fix Available) Status in mesa package in Ubuntu: New Bug description: MESA 22.2 contains a malfunction which causes kwin to exit regularly / frequently, leaving the system without window management. This is a regression compared to MESA 22.1 and fixed again in MESA 22.3. See following MESA bug: * https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 * just for reference, corresponding KDE Bugtracker entry: https://bugs.kde.org/show_bug.cgi?id=461316 Maybe the fix could be backported? It currently is something between inconvenient (for very technically savy users) and rendering the system unusable (for less technically savy users - suddenly, Window Management will be gone and switching windows, accessing panels, and controlling most applications even if they are in foreground at the time of a crash become impossible). ProblemType: Bug DistroRelease: KDE neon 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Apr 27 14:26:47 2023 DistUpgraded: 2020-10-11
[Touch-packages] [Bug 2017852] Re: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/2017852 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017852/+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 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
Hello,
On Ubuntu desktop 22.04 LTS, it seems that the hook is not executed. I'm
not sure how to verify that but sure thing is the DHCP is well
announcing the ntp server.
DHCP4.OPTION[8]:ntp_servers = X.X.X.X
DHCP4.OPTION[18]: requested_ntp_servers = 1
Could someone help ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1685484
Title:
DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
Status in network-manager package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Won't Fix
Status in systemd package in Debian:
Fix Released
Bug description:
I think it's regression for
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1578663 in
zesty.
1. NTP servers are send via DHCP and seen by NM:
$ nmcli con show connection1 | grep ntp
DHCP4.OPTION[30]: requested_ntp_servers = 1
DHCP4.OPTION[31]: ntp_servers = 80.50.231.226
217.96.29.26 212.160.106.226
2. timesyncd is using hardcoded default NTP server:
$ systemctl -n 200 status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
`-disable-with-time-daemon.conf
Active: active (running) since Sat 2017-04-22 13:12:23 CEST; 16min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 576 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
Memory: 1.5M
CPU: 20ms
CGroup: /system.slice/systemd-timesyncd.service
`-576 /lib/systemd/systemd-timesyncd
Apr 22 13:12:23 slodki systemd[1]: Starting Network Time Synchronization...
Apr 22 13:12:23 slodki systemd[1]: Started Network Time Synchronization.
Apr 22 13:12:53 slodki systemd-timesyncd[576]: Synchronized to time server
91.189.89.199:123 (ntp.ubuntu.com).
3. There are not other time sync deamons installed:
$ cat
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[Unit]
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService
$ ls -l /usr/sbin/{ntpd,openntpd,chronyd,VBoxService}
ls: cannot access '/usr/sbin/ntpd': No such file or directory
ls: cannot access '/usr/sbin/openntpd': No such file or directory
ls: cannot access '/usr/sbin/chronyd': No such file or directory
ls: cannot access '/usr/sbin/VBoxService': No such file or directory
4. There is only one default timesyncd.conf file with default values:
$ sudo find / -iname \*timesync\*
/etc/systemd/timesyncd.conf
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/dhcp/dhclient-exit-hooks.d/timesyncd
/usr/share/man/man5/timesyncd.conf.d.5.gz
/usr/share/man/man5/timesyncd.conf.5.gz
/usr/share/man/man8/systemd-timesyncd.8.gz
/usr/share/man/man8/systemd-timesyncd.service.8.gz
/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-6NwdRT
/lib/systemd/systemd-timesyncd
/lib/systemd/system/systemd-timesyncd.service
/lib/systemd/system/systemd-timesyncd.service.d
/var/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-jz0q47
$ cat /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.
[Time]
#NTP=
#FallbackNTP=ntp.ubuntu.com
5. DHCP hook installed as /etc/dhcp/dhclient-exit-hooks.d/timesyncd is
not working,
TIMESYNCD_CONF=/run/systemd/timesyncd.conf.d/01-dhclient.conf is not
created.
6. After manually executing steps from hook all works as expected:
$ sudo mkdir -p /run/systemd/timesyncd.conf.d/
$ sudo cat [Time]
> NTP=80.50.231.226 217.96.29.26 212.160.106.226
> EOF
$ sudo systemctl try-restart systemd-timesyncd.service
$ sudo systemctl status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/system
[Touch-packages] [Bug 2017743] Re: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev
It looks like that libdatetime-timezone-perl ships a copy of the timezone data. So versions in recent Ubuntu versions will contain the tzdata update. See https://manpages.ubuntu.com/manpages/kinetic/man3/DateTime::TimeZone::Catalog.3pm.html -- 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/2017743 Title: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev Status in tzdata package in Ubuntu: Invalid Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (240 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: tzdata 2023c-0ubuntu0.22.04.0 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
The debdiff is against 1.481 in jammy, please rebase against the latest version in the development release (currently 1.501 in lunar). You can use 'pull-lp-source ubuntu-meta' for this. Please also close this bug in the changelog e.g. (LP: #2017786). We should probably do the same for all the flavour meta packages as well, so this bug should be marked as affecting ubuntu-unity-meta, ubuntucinnamon-meta, etc. Unsubscribing sponsors for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 2017852] Re: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I could help myself like this: #check current linux version uname -a --> Linux p15 5.19.0-40-generic #41~22.04.1-Ubuntu # list installed linux images apt list --installed| grep linux-image --> there were some older ones with version 5.15 # remove the old ones apt remove linux-image-5.15.0-69-generic linux-image-5.15.0-70-generic apt autoremove # check states of /boot df -h --> /dev/nvme0n1p2 704M605M 48M 93% /boot ... hmm still not better. rm /boot/*-5.15* df -h /boot/ --> /dev/nvme0n1p2 704M288M 365M 45% /boot Looks better now. --- I can solve this on my own. But a normal human being (my mother, my sister) can't do this. -- 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/2017852 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017852/+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 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
I did not make any changes to the design when moving it from Update- Manager in apt, it's been this way for 10 years now, it's a proven concept. The initial implementation used and md5 but the math gets complex when dealing with 128 bit integers. You can easily override the machine-id for apt by setting the apt.conf option, /etc/machine-id is a default. It's general consensus that everything should be using the same machine id though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately Status in apt package in Ubuntu: Triaged Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 2017852] Re: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
The size of /boot was choosen by Ubuntu during the installation (not by me). I never touched a file in this directory by hand. -- 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/2017852 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017852/+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 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
To add a data point and save others from preventable headaches, I encountered a related bug and reported it here: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2017399 If anyone cares, here are my two cents regarding phased updates: https://github.com/xwcal/ubuntu-apt-bug#a-short-critique-of-phased-updates Or if lack of markdown formatting is not an issue, here is goes: # A Short Critique of Phased Updates Some thoughts after I stumbled on phased updates during a recent migration from Bionic to Jammy: ## Randomness and Repeatability Per [Debian repository specs](https://wiki.debian.org/DebianRepository/Format#Phased-Update- Percentage), randomization is achieved by the following means: ``` To determine whether an update is applicable to a given machine, a client shall seed a random number generator (APT uses std::minstd_rand) with the string: sourcePackage-version-machineID where sourcePackage is the name of the source package, version the version, and machineID the contents of /etc/machine-id. It shall then extract an integer from a uniform integer distribution between 0 and 100. ``` To the uninitiated: this is not how a random number generator is meant to be used. If you want a repeatable sequence of random numbers, you seed the RNG once and then draw the desired number of samples. You don't reseed the RNG for each new sample, since if your seeds are already random, then the RNG step is pointless, whereas if your seeds aren't random, say, in an extreme case, if you always seed with the same number, your "random" number is guaranteed to be the same each time. To achieve repeatable randomness with respect to both the package and machine, there is an obviously superior choice in terms of both randomness and portability: **just use a cryptographic hash like sha256**. This begs the question of how repeatable the design really is. To quote [https://wiki.debian.org/MachineId](https://wiki.debian.org/MachineId): ``` what is the machine id actually used for? a comprehensive list is probably not possible without grepping the code ``` That's to say, although for repeatable experiments it's foreseeably necessary to mess with the machine ID or share it publicly, the consequences of such tinkering or disclosure are hard to assess, since nobody knows for sure how and where the machine ID is and will be used. This leads to an easily conceivable alternative: since apt only uses the machine ID for the purpose of repeatable randomization, how about designating another user configurable value stored in, say `/etc/apt/phased-update-random-seed`, only for this particular purpose and by default initialized to the machine ID? ## User Choice >From [this response](https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2017399/comments/1) to my bug report (one question I forgot to ask is why phase security updates at all) and a comment on [askubuntu](https://askubuntu.com/questions/1431940/what-are-phased- updates-and-why-does-ubuntu-use-them) that doesn't cite any source, it does appear that consideration has been given regarding the need to treat different packages (at least different classes of packages) differently when it comes to phasing. It's conceivable that a user may have preferences over how each particular package is phased. For example, if a GUI component has a troubled history with my Nvidia graphics, I may prefer to be highly conservative and wait until the last minute, but this shouldn't prevent me from being adventurous when it comes to other phased packages. Unfortunately, it seems that a user currently has to decide between all or nothing, ie. between `APT::Get::Always-Include-Phased-Updates` or `APT::Get::Never-Include-Phased-Updates`. How about allowing per package user choice between Always and Never? Overall, I think for a such a prominent change to the cornerstone of probably half of today's Linux infrastructure, much remains to be desired. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately Status in apt package in Ubuntu: Triaged Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 U
[Touch-packages] [Bug 2017743] Re: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev
Another question, I've found another package `DateTime::TimeZone::Catalog.3pm.gz` https://manpages.ubuntu.com/manpages/xenial/man3/DateTime::TimeZone::Catalog.3pm.html Provided by: libdatetime-timezone-perl_1.95-1+2016a_all And there is some information with only `Kiev` Ukraine (UA) Europe/Kiev - most locations Europe/Uzhgorod - Ruthenia Europe/Zaporozhye - Zaporozh'ye, E Lugansk / Zaporizhia, E Luhansk Just want to be sure that it isn't related to this bug, am I right? -- 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/2017743 Title: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev Status in tzdata package in Ubuntu: Invalid Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (240 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: tzdata 2023c-0ubuntu0.22.04.0 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017743] Re: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev
Thanks! It works when set the environment option in the `teams` CMD. >> https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in-the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2?page=2 Dmytro Verbytskyi: I have Ubuntu 20.04. To make it all automated, we could add the environment variable for Teams with the necessary time zone. Just open /usr/share/applications/teams.desktop in your text editor, find section [Desktop Entry], and find a line in it Exec=teams Update this line to Exec=env TZ=Europe/Kiev /usr/bin/teams %U That's it, now it works for me without using CLI to start the application. The reason is really that Teams have no idea about Kyiv and its time zone. I hope MS will fix that. ** Changed in: tzdata (Ubuntu) Status: Incomplete => 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/2017743 Title: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev Status in tzdata package in Ubuntu: Invalid Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (240 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: tzdata 2023c-0ubuntu0.22.04.0 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017743] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2017743/+attachment/5669128/+files/ProcEnviron.txt -- 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/2017743 Title: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev Status in tzdata package in Ubuntu: Incomplete Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (240 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: tzdata 2023c-0ubuntu0.22.04.0 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017743] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2017743/+attachment/5669127/+files/ProcCpuinfoMinimal.txt -- 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/2017743 Title: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev Status in tzdata package in Ubuntu: Incomplete Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (240 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: tzdata 2023c-0ubuntu0.22.04.0 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017743] Re: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev
apport information ** Tags added: apport-collected jammy ** Description changed: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in-the- ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-08-29 (240 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + Package: tzdata 2023c-0ubuntu0.22.04.0 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 + Tags: jammy + Uname: Linux 5.19.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2017743/+attachment/5669126/+files/Dependencies.txt -- 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/2017743 Title: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev Status in tzdata package in Ubuntu: Incomplete Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (240 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: tzdata 2023c-0ubuntu0.22.04.0 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017840] Re: ifupdown resolved script has typo
** Description changed: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` - I'm thinking that the word `local` should appear before `mystatedir` on line 12. - The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. + I'm thinking that the word `local` used to appear before `mystatedir` on + line 12, but that was when it was a function. When it was converted + back from being a function, the 'local' keyword was removed, but the + variables remained. + + Either make it into a function again, or delete line 12. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+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 2017852] Re: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>From the logs: zstd: error 25 : Write error : No space left on device (cannot write compressed block) Not a bug in the software, but a local problem on your system. You have to clean up your system to create enough free space. -- 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/2017852 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017852/+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
