[Touch-packages] [Bug 2083526] Re: FTBFS s390x: gzip: stdin: invalid compressed data--format violated
I couldn't reproduce the rsyslog build-time test failure in a s390x vm, even one with 4 vcpus. The only difference between my test and the lp builders would have been the kernel, since the build in lp happens in a chroot with an older kernel as the base, not the oracular one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2083526 Title: FTBFS s390x: gzip: stdin: invalid compressed data--format violated Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Noble: New Status in rsyslog source package in Oracular: New Bug description: Multiple build-time gzip tests are failing[1] on s390x only: 14:31:21[0] Test: ./gzipwr_flushInterval.sh config rstb_615693_cea0d3b33SOB_.conf is: 1module(load="../plugins/imdiag/.libs/imdiag") 2global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4 default.action.queue.timeoutEnqueue="2") 5# use legacy-style for the following settings so that we can override if needed 6$MainmsgQueueTimeoutEnqueue 2 7$MainmsgQueueTimeoutShutdown 1 8$IMDiagListenPortFileName rstb_615693_cea0d3b33SOB.imdiag.port 9$IMDiagServerRun 0 10$IMDiagAbortTimeout 580 11 12:syslogtag, contains, "rsyslogd" ./rstb_615693_cea0d3b33SOB.started 13## end of testbench instrumentation part, test conf follows: 14 15module(load="../plugins/imtcp/.libs/imtcp") 16input(type="imtcp" port="0" listenPortFileName="rstb_615693_cea0d3b33SOB.tcpflood_port") 17 18template(name="outfmt" type="string" string="%msg:F,58:2%\n") 19:msg, contains, "msgnum:" action(type="omfile" template="outfmt" 20 zipLevel="6" ioBufferSize="256k" 21 flushOnTXEnd="off" flushInterval="1" 22 asyncWriting="on" 23 file="rstb_615693_cea0d3b33SOB.out.log.gz") rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated main Q:Reg: worker start requested, num workers currently 0 main Q:Reg: wrkr start initiated with state 0, num workers now 1 rsyslog debug: main Q:Reg: worker 0x2aa3d545730 started rsyslog debug: main Q:Reg: started with state 3, num workers now 1 14:31:21[0] rstb_615693_cea0d3b33SOB:.pid found, pid 158902 14:31:21[0] rsyslogd startup msg seen, pid 158902 waiting for file rstb_615693_cea0d3b33SOB.imdiag.port imdiag port: 35981 waiting for file rstb_615693_cea0d3b33SOB.tcpflood_port TCPFLOOD_PORT now: 37167 starting run 1 Sending 2500 messages. 2500 messages sent runtime: 0.001 End of tcpflood Run gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated scanf error in index i=0 gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated sequence error detected in rstb_615693_cea0d3b33SOB.out.log.gz number of lines in file: 0 rstb_615693_cea0d3b33SOB.out.log.gz sorted data has been placed in error.log, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 UNSORTED data, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 not reporting failure as RSYSLOG_STATSURL is not set rsyslog pid file still exists, trying to shutdown... rsyslogd debug: info: trying to cooperatively stop input ../plugins/imdiag/.libs/imdiag, timeout 6 ms rsyslogd debug: info: trying to cooperatively stop input imtcp, timeout 6 ms rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup rsyslog debug: 0x2aa3d5458b0: worker exiting rsyslog debug: main Q:Reg/w0: thread joined 14:31:26[5] FAIL: Test ./gzipwr_flushInterval.sh (took 5 seconds) FAIL gzipwr_flushInterval.sh (exit status: 1) So far I have seen this in noble, while preparing an SRU[2]. Don't know yet if oracular or others are also affected. 1. https://launchpadlibrarian.net/752369377/buildlog_ubuntu-noble-s390x.rsyslog_8.2312.0-3ubuntu9.1~ppa1_BUILDING.txt.gz 2. https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2083526/+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 2083700] Re: rsyslog FTBFS (s390x only) against zlib 1:1.3.dfsg+really1.3.1-1ubuntu1
I had filed https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2083526 previously, and I couldn't reproduce the build/test failures on a s390x vm, just in a ppa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2083700 Title: rsyslog FTBFS (s390x only) against zlib 1:1.3.dfsg+really1.3.1-1ubuntu1 Status in rsyslog package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: During an archive rebuild, rsyslog FTBFS on s390x only: https://launchpadlibrarian.net/751879056/buildlog_ubuntu- oracular-s390x.rsyslog_8.2406.0-1ubuntu2_BUILDING.txt.gz The build fails due to two tests: FAIL: gzipwr_flushInterval == testbench: TZ env var not set, setting it to UTC 08:47:04[0] Test: ./gzipwr_flushInterval.sh config rstb_216690_cea0d3b3Yo0x_.conf is: 1module(load="../plugins/imdiag/.libs/imdiag") 2global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4 default.action.queue.timeoutEnqueue="2") 5# use legacy-style for the following settings so that we can override if needed 6$MainmsgQueueTimeoutEnqueue 2 7$MainmsgQueueTimeoutShutdown 1 8$IMDiagListenPortFileName rstb_216690_cea0d3b3Yo0x.imdiag.port 9$IMDiagServerRun 0 10$IMDiagAbortTimeout 580 11 12:syslogtag, contains, "rsyslogd" ./rstb_216690_cea0d3b3Yo0x.started 13## end of testbench instrumentation part, test conf follows: 14 15module(load="../plugins/imtcp/.libs/imtcp") 16input(type="imtcp" port="0" listenPortFileName="rstb_216690_cea0d3b3Yo0x.tcpflood_port") 17 18template(name="outfmt" type="string" string="%msg:F,58:2%\n") 19:msg, contains, "msgnum:" action(type="omfile" template="outfmt" 20 zipLevel="6" ioBufferSize="256k" 21 flushOnTXEnd="off" flushInterval="1" 22 asyncWriting="on" 23 file="rstb_216690_cea0d3b3Yo0x.out.log.gz") rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated main Q:Reg: worker start requested, num workers currently 0 main Q:Reg: wrkr start initiated with state 0, num workers now 1 rsyslog debug: main Q:Reg: worker 0x2aa0873c810 started rsyslog debug: main Q:Reg: started with state 3, num workers now 1 08:47:04[0] rstb_216690_cea0d3b3Yo0x:.pid found, pid 158166 08:47:04[0] rsyslogd startup msg seen, pid 158166 waiting for file rstb_216690_cea0d3b3Yo0x.imdiag.port imdiag port: 35391 waiting for file rstb_216690_cea0d3b3Yo0x.tcpflood_port TCPFLOOD_PORT now: 32793 starting run 1 Sending 2500 messages. 2500 messages sent runtime: 0.005 End of tcpflood Run gzip: rstb_216690_cea0d3b3Yo0x.out.log.gz: invalid compressed data--format violated scanf error in index i=0 gzip: rstb_216690_cea0d3b3Yo0x.out.log.gz: invalid compressed data--format violated sequence error detected in rstb_216690_cea0d3b3Yo0x.out.log.gz number of lines in file: 0 rstb_216690_cea0d3b3Yo0x.out.log.gz sorted data has been placed in error.log, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 UNSORTED data, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 not reporting failure as RSYSLOG_STATSURL is not set rsyslog pid file still exists, trying to shutdown... rsyslogd debug: info: trying to cooperatively stop input ../plugins/imdiag/.libs/imdiag, timeout 6 ms rsyslogd debug: info: trying to cooperatively stop input imtcp, timeout 6 ms rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup rsyslog debug: 0x2aa0873c990: worker exiting rsyslog debug: main Q:Reg/w0: thread joined 08:47:09[5] FAIL: Test ./gzipwr_flushInterval.sh (took 5 seconds) FAIL gzipwr_flushInterval.sh (exit status: 1) FAIL: gzipwr_flushOnTXEnd = testbench: TZ env var not set, setting it to UTC 08:47:04[0] Test: ./gzipwr_flushOnTXEnd.sh config rstb_586738_b0a588ae30Do_.conf is: 1module(load="../plugins/imdiag/.libs/imdiag") 2global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4
[Touch-packages] [Bug 2077290] Re: [SRU] GLArea transparency broken
> Couldn't work out why they aren't updating automatically but manually > installing the .debs shows the > issue fixed, thanks! Thanks Robert for your verification, but could you please expand on what verification steps you actually performed, and with which package versions? The instructions request: > 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-noble to verification-done-noble. The test plan has very detailed steps that should have been followed. Regarding your issue with having apt recognize the packages from proposed, did you add the "-t noble-proposed" command-line parameter? In the meantime, I'm flipping the tags back to verification-needed. ** Tags removed: verification-done-noble ** Tags added: verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2077290 Title: [SRU] GLArea transparency broken Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Noble: Fix Committed Bug description: [Impact] In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42). [Test Case] Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). [Regression potential] Issues can be expected in GTK3 widgets with a transparent background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+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 2083489] Re: Upgrading dbus tear down network
> This I believe trigger a systemd-networkd restart Do you have logs showing the link between dbus being updated and systemd restarted? Does something similar happen when you just reinstall dbus? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2083489 Title: Upgrading dbus tear down network Status in dbus package in Ubuntu: New Bug description: While running a dist-ugprade on Jammy machines part of a Ceph cluster, dbus got updated ``` 2024-09-25 04:35:25 status triggers-pending dbus:amd64 1.12.20-2ubuntu4.1 2024-09-25 04:35:36 status triggers-pending dbus:amd64 1.12.20-2ubuntu4.1 2024-09-25 04:37:28 trigproc dbus:amd64 1.12.20-2ubuntu4.1 2024-09-25 04:37:28 status half-configured dbus:amd64 1.12.20-2ubuntu4.1 2024-09-25 04:37:28 status installed dbus:amd64 1.12.20-2ubuntu4.1 ``` This I believe trigger a systemd-networkd restart ``` Sep 25 04:36:35 * systemd[1]: Started Network Configuration. ``` Which causes interfaces to go down and up. ``` Sep 25 04:36:35 * systemd-networkd[605770]: bond0: netdev exists, using existing without changing its parameters Sep 25 04:36:35 * systemd-networkd[605770]: bond1: netdev exists, using existing without changing its parameters Sep 25 04:36:35 * systemd-networkd[605770]: br-bond0-3486: netdev exists, using existing without changing its parameters Sep 25 04:36:35 * systemd-networkd[605770]: br-bond1: netdev exists, using existing without changing its parameters Sep 25 04:36:35 * systemd-networkd[605770]: br-enp68s0f0: netdev exists, using existing without changing its parameters Sep 25 04:36:37 * systemd-networkd[605770]: enp129s0f1np1: Link DOWN Sep 25 04:36:37 * systemd-networkd[605770]: enp129s0f1np1: Lost carrier Sep 25 04:36:37 * systemd-networkd[605770]: enp129s0f0np0: Link DOWN Sep 25 04:36:37 * systemd-networkd[605770]: enp129s0f0np0: Lost carrier Sep 25 04:36:37 * systemd-networkd[605770]: bond1: Lost carrier Sep 25 04:36:37 * systemd-networkd[605770]: enp161s0f1np1: Link DOWN Sep 25 04:36:37 * systemd-networkd[605770]: enp161s0f1np1: Lost carrier Sep 25 04:36:37 * systemd-networkd[605770]: enp161s0f0np0: Link DOWN Sep 25 04:36:37 * systemd-networkd[605770]: enp161s0f0np0: Lost carrier Sep 25 04:36:37 * systemd-networkd[605770]: bond0: Lost carrier Sep 25 04:36:37 * systemd-networkd[605770]: bond0.3484: Lost carrier Sep 25 04:36:37 * systemd-networkd[605770]: bond0.3486: Lost carrier Sep 25 04:36:41 * systemd-networkd[605770]: enp129s0f1np1: Link UP Sep 25 04:36:42 * systemd-networkd[605770]: enp129s0f1np1: Gained carrier Sep 25 04:36:42 * systemd-networkd[605770]: enp129s0f0np0: Link UP Sep 25 04:36:42 * systemd-networkd[605770]: enp129s0f0np0: Gained carrier Sep 25 04:36:42 * systemd-networkd[605770]: enp161s0f1np1: Link UP Sep 25 04:36:42 * systemd-networkd[605770]: enp161s0f0np0: Link UP Sep 25 04:36:42 * systemd-networkd[605770]: enp161s0f1np1: Gained carrier Sep 25 04:36:42 * systemd-networkd[605770]: enp161s0f0np0: Gained carrier Sep 25 04:36:42 * systemd-networkd[605770]: bond0: Gained carrier Sep 25 04:36:42 * systemd-networkd[605770]: bond0.3484: Gained carrier Sep 25 04:36:42 * systemd-networkd[605770]: bond0.3486: Gained carrier Sep 25 04:36:42 * systemd-networkd[605770]: bond1: Gained carrier ``` ``` Sep 25 04:36:35 * kernel: [18085928.795785] bond1: (slave enp129s0f1np1): link status definitely down, disabling slave Sep 25 04:36:36 * kernel: [18085929.535826] bond1: (slave enp129s0f0np0): link status definitely down, disabling slave Sep 25 04:36:37 * kernel: [18085929.919702] bond0: (slave enp161s0f1np1): link status definitely down, disabling slave Sep 25 04:36:37 * kernel: [18085930.339709] bond0: (slave enp161s0f0np0): link status definitely down, disabling slave Sep 25 04:36:41 * kernel: [18085934.812301] bond0: (slave enp161s0f1np1): link status definitely up, 25000 Mbps full duplex Sep 25 04:36:41 * kernel: [18085934.812968] bond0: (slave enp161s0f0np0): link status definitely up, 25000 Mbps full duplex Sep 25 04:36:42 * kernel: [18085934.828048] bond1: (slave enp129s0f1np1): link status definitely up, 10 Mbps full duplex Sep 25 04:36:42 * kernel: [18085934.828491] bond1: (slave enp129s0f0np0): link status definitely up, 10 Mbps full duplex ``` This caused a big outage on the Ceph cluster where many placement groups went unavailable. It will be good if the dbus upgra
[Touch-packages] [Bug 2083526] Re: FTBFS s390x: gzip: stdin: invalid compressed data--format violated
I ran the gzip build-time tests on s390x, and nothing failed. Focusing on rsyslog again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2083526 Title: FTBFS s390x: gzip: stdin: invalid compressed data--format violated Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Noble: New Status in rsyslog source package in Oracular: New Bug description: Multiple build-time gzip tests are failing[1] on s390x only: 14:31:21[0] Test: ./gzipwr_flushInterval.sh config rstb_615693_cea0d3b33SOB_.conf is: 1module(load="../plugins/imdiag/.libs/imdiag") 2global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4 default.action.queue.timeoutEnqueue="2") 5# use legacy-style for the following settings so that we can override if needed 6$MainmsgQueueTimeoutEnqueue 2 7$MainmsgQueueTimeoutShutdown 1 8$IMDiagListenPortFileName rstb_615693_cea0d3b33SOB.imdiag.port 9$IMDiagServerRun 0 10$IMDiagAbortTimeout 580 11 12:syslogtag, contains, "rsyslogd" ./rstb_615693_cea0d3b33SOB.started 13## end of testbench instrumentation part, test conf follows: 14 15module(load="../plugins/imtcp/.libs/imtcp") 16input(type="imtcp" port="0" listenPortFileName="rstb_615693_cea0d3b33SOB.tcpflood_port") 17 18template(name="outfmt" type="string" string="%msg:F,58:2%\n") 19:msg, contains, "msgnum:" action(type="omfile" template="outfmt" 20 zipLevel="6" ioBufferSize="256k" 21 flushOnTXEnd="off" flushInterval="1" 22 asyncWriting="on" 23 file="rstb_615693_cea0d3b33SOB.out.log.gz") rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated main Q:Reg: worker start requested, num workers currently 0 main Q:Reg: wrkr start initiated with state 0, num workers now 1 rsyslog debug: main Q:Reg: worker 0x2aa3d545730 started rsyslog debug: main Q:Reg: started with state 3, num workers now 1 14:31:21[0] rstb_615693_cea0d3b33SOB:.pid found, pid 158902 14:31:21[0] rsyslogd startup msg seen, pid 158902 waiting for file rstb_615693_cea0d3b33SOB.imdiag.port imdiag port: 35981 waiting for file rstb_615693_cea0d3b33SOB.tcpflood_port TCPFLOOD_PORT now: 37167 starting run 1 Sending 2500 messages. 2500 messages sent runtime: 0.001 End of tcpflood Run gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated scanf error in index i=0 gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated sequence error detected in rstb_615693_cea0d3b33SOB.out.log.gz number of lines in file: 0 rstb_615693_cea0d3b33SOB.out.log.gz sorted data has been placed in error.log, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 UNSORTED data, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 not reporting failure as RSYSLOG_STATSURL is not set rsyslog pid file still exists, trying to shutdown... rsyslogd debug: info: trying to cooperatively stop input ../plugins/imdiag/.libs/imdiag, timeout 6 ms rsyslogd debug: info: trying to cooperatively stop input imtcp, timeout 6 ms rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup rsyslog debug: 0x2aa3d5458b0: worker exiting rsyslog debug: main Q:Reg/w0: thread joined 14:31:26[5] FAIL: Test ./gzipwr_flushInterval.sh (took 5 seconds) FAIL gzipwr_flushInterval.sh (exit status: 1) So far I have seen this in noble, while preparing an SRU[2]. Don't know yet if oracular or others are also affected. 1. https://launchpadlibrarian.net/752369377/buildlog_ubuntu-noble-s390x.rsyslog_8.2312.0-3ubuntu9.1~ppa1_BUILDING.txt.gz 2. https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2083526/+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 2083526] Re: FTBFS s390x: gzip: stdin: invalid compressed data--format violated
This is also affecting oracular: https://launchpadlibrarian.net/752391673/buildlog_ubuntu- oracular-s390x.rsyslog_8.2406.0-1ubuntu3~ppa1_BUILDING.txt.gz ** Also affects: rsyslog (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: rsyslog (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2083526 Title: FTBFS s390x: gzip: stdin: invalid compressed data--format violated Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Noble: New Status in rsyslog source package in Oracular: New Bug description: Multiple build-time gzip tests are failing[1] on s390x only: 14:31:21[0] Test: ./gzipwr_flushInterval.sh config rstb_615693_cea0d3b33SOB_.conf is: 1module(load="../plugins/imdiag/.libs/imdiag") 2global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4 default.action.queue.timeoutEnqueue="2") 5# use legacy-style for the following settings so that we can override if needed 6$MainmsgQueueTimeoutEnqueue 2 7$MainmsgQueueTimeoutShutdown 1 8$IMDiagListenPortFileName rstb_615693_cea0d3b33SOB.imdiag.port 9$IMDiagServerRun 0 10$IMDiagAbortTimeout 580 11 12:syslogtag, contains, "rsyslogd" ./rstb_615693_cea0d3b33SOB.started 13## end of testbench instrumentation part, test conf follows: 14 15module(load="../plugins/imtcp/.libs/imtcp") 16input(type="imtcp" port="0" listenPortFileName="rstb_615693_cea0d3b33SOB.tcpflood_port") 17 18template(name="outfmt" type="string" string="%msg:F,58:2%\n") 19:msg, contains, "msgnum:" action(type="omfile" template="outfmt" 20 zipLevel="6" ioBufferSize="256k" 21 flushOnTXEnd="off" flushInterval="1" 22 asyncWriting="on" 23 file="rstb_615693_cea0d3b33SOB.out.log.gz") rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated main Q:Reg: worker start requested, num workers currently 0 main Q:Reg: wrkr start initiated with state 0, num workers now 1 rsyslog debug: main Q:Reg: worker 0x2aa3d545730 started rsyslog debug: main Q:Reg: started with state 3, num workers now 1 14:31:21[0] rstb_615693_cea0d3b33SOB:.pid found, pid 158902 14:31:21[0] rsyslogd startup msg seen, pid 158902 waiting for file rstb_615693_cea0d3b33SOB.imdiag.port imdiag port: 35981 waiting for file rstb_615693_cea0d3b33SOB.tcpflood_port TCPFLOOD_PORT now: 37167 starting run 1 Sending 2500 messages. 2500 messages sent runtime: 0.001 End of tcpflood Run gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated scanf error in index i=0 gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated sequence error detected in rstb_615693_cea0d3b33SOB.out.log.gz number of lines in file: 0 rstb_615693_cea0d3b33SOB.out.log.gz sorted data has been placed in error.log, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 UNSORTED data, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 not reporting failure as RSYSLOG_STATSURL is not set rsyslog pid file still exists, trying to shutdown... rsyslogd debug: info: trying to cooperatively stop input ../plugins/imdiag/.libs/imdiag, timeout 6 ms rsyslogd debug: info: trying to cooperatively stop input imtcp, timeout 6 ms rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup rsyslog debug: 0x2aa3d5458b0: worker exiting rsyslog debug: main Q:Reg/w0: thread joined 14:31:26[5] FAIL: Test ./gzipwr_flushInterval.sh (took 5 seconds) FAIL gzipwr_flushInterval.sh (exit status: 1) So far I have seen this in noble, while preparing an SRU[2]. Don't know yet if oracular or others are also affected. 1. https://launchpadlibrarian.net/752369377/buildlog_ubuntu-noble-s390x.rsyslog_8.2312.0-3ubuntu9.1~ppa1_BUILDING.txt.gz 2. https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2083526/+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
[Touch-packages] [Bug 2072702] Re: AppArmor profile prevents use of TLS keys and certificates
> But perhaps /etc/ipa/ca.crt needs to be added to > /etc/apparmor.d/abstractions/ssl_certs which is in the > apparmor package. @jjohansen, @georgiag, what do you think about the above suggestion? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2072702 Title: AppArmor profile prevents use of TLS keys and certificates Status in rsyslog package in Ubuntu: New Bug description: I'm trying to use the following configuration: # certificate files $DefaultNetstreamDriverCAFile /etc/ipa/ca.crt $DefaultNetstreamDriverCertFile /etc/ssl/certs/FQDN.crt $DefaultNetstreamDriverKeyFile /etc/ssl/private/FQDN.key But AppArmor prevents the loading of /etc/ipa/ca.crt and the key file. I think rsyslog-gnutls should allow reading the key file. But perhaps /etc/ipa/ca.crt needs to be added to /etc/apparmor.d/abstractions/ssl_certs which is in the apparmor package. Version 8.2312.0-3ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2072702/+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 2083526] Re: FTBFS s390x: gzip: stdin: invalid compressed data--format violated
Perhaps related: https://bugs.launchpad.net/bugs/2076269 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2083526 Title: FTBFS s390x: gzip: stdin: invalid compressed data--format violated Status in rsyslog package in Ubuntu: New Bug description: Multiple build-time gzip tests are failing[1] on s390x only: 14:31:21[0] Test: ./gzipwr_flushInterval.sh config rstb_615693_cea0d3b33SOB_.conf is: 1module(load="../plugins/imdiag/.libs/imdiag") 2global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4 default.action.queue.timeoutEnqueue="2") 5# use legacy-style for the following settings so that we can override if needed 6$MainmsgQueueTimeoutEnqueue 2 7$MainmsgQueueTimeoutShutdown 1 8$IMDiagListenPortFileName rstb_615693_cea0d3b33SOB.imdiag.port 9$IMDiagServerRun 0 10$IMDiagAbortTimeout 580 11 12:syslogtag, contains, "rsyslogd" ./rstb_615693_cea0d3b33SOB.started 13## end of testbench instrumentation part, test conf follows: 14 15module(load="../plugins/imtcp/.libs/imtcp") 16input(type="imtcp" port="0" listenPortFileName="rstb_615693_cea0d3b33SOB.tcpflood_port") 17 18template(name="outfmt" type="string" string="%msg:F,58:2%\n") 19:msg, contains, "msgnum:" action(type="omfile" template="outfmt" 20 zipLevel="6" ioBufferSize="256k" 21 flushOnTXEnd="off" flushInterval="1" 22 asyncWriting="on" 23 file="rstb_615693_cea0d3b33SOB.out.log.gz") rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated main Q:Reg: worker start requested, num workers currently 0 main Q:Reg: wrkr start initiated with state 0, num workers now 1 rsyslog debug: main Q:Reg: worker 0x2aa3d545730 started rsyslog debug: main Q:Reg: started with state 3, num workers now 1 14:31:21[0] rstb_615693_cea0d3b33SOB:.pid found, pid 158902 14:31:21[0] rsyslogd startup msg seen, pid 158902 waiting for file rstb_615693_cea0d3b33SOB.imdiag.port imdiag port: 35981 waiting for file rstb_615693_cea0d3b33SOB.tcpflood_port TCPFLOOD_PORT now: 37167 starting run 1 Sending 2500 messages. 2500 messages sent runtime: 0.001 End of tcpflood Run gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated scanf error in index i=0 gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated sequence error detected in rstb_615693_cea0d3b33SOB.out.log.gz number of lines in file: 0 rstb_615693_cea0d3b33SOB.out.log.gz sorted data has been placed in error.log, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 UNSORTED data, first 10 lines are: 1scanf error in index i=0 ---last 10 lines are: 1scanf error in index i=0 not reporting failure as RSYSLOG_STATSURL is not set rsyslog pid file still exists, trying to shutdown... rsyslogd debug: info: trying to cooperatively stop input ../plugins/imdiag/.libs/imdiag, timeout 6 ms rsyslogd debug: info: trying to cooperatively stop input imtcp, timeout 6 ms rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup rsyslog debug: 0x2aa3d5458b0: worker exiting rsyslog debug: main Q:Reg/w0: thread joined 14:31:26[5] FAIL: Test ./gzipwr_flushInterval.sh (took 5 seconds) FAIL gzipwr_flushInterval.sh (exit status: 1) So far I have seen this in noble, while preparing an SRU[2]. Don't know yet if oracular or others are also affected. 1. https://launchpadlibrarian.net/752369377/buildlog_ubuntu-noble-s390x.rsyslog_8.2312.0-3ubuntu9.1~ppa1_BUILDING.txt.gz 2. https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2083526/+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 2056768] Re: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/"
While preparing the SRU for noble, I noticed the build is failing on s390x[1]. 1. https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2083526 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2056768 Title: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Noble: In Progress Bug description: There is an AppArmor regression in current noble. In cockpit we recently started to test on noble (to prevent the "major regressions after release" fiasco from 23.10 again). For some weird reason, rsyslog is installed *by default* [1] in the cloud images. That is a rather pointless waste of CPU and disk space, as it's an unnecessary running daemon and duplicates all the written logs. But more specifically, we noticed [2] an AppArmor rejection. Reproducer is simple: logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE this causes type=1400 audit(1710168739.345:108): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567 requested_mask="r" denied_mask="r" fsuid=102 ouid=0 Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does appear in the journal and also in /var/log/syslog. But it's some noise that triggers our (and presumbly other admin's) log detectors. rsyslog 8.2312.0-3ubuntu3 apparmor 4.0.0~alpha4-0ubuntu1 [1] https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest [2] https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768/+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 2073628] Re: imjournal module works with rsyslog package of ubuntu 22.04 but not with ubuntu 24.04
Can you please check if there are any apparmor errors in the `sudo dmesg -T` output with a timestamp that matches the rsyslog message where it says it will create the journal_state file? The current rules do allow creating files there, but maybe something is missing: /var/spool/rsyslog/ r, /var/spool/rsyslog/** rwk, ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2073628 Title: imjournal module works with rsyslog package of ubuntu 22.04 but not with ubuntu 24.04 Status in rsyslog package in Ubuntu: Incomplete Bug description: imjournal module fails to create /var/spool/rsyslog/journal-state file in ubuntu 24.04, rsyslog version(8.2312.0) x86 and s390x both, but works well in ubuntu 22.04 , rsyslog version(8.2112.0) x86 and s390x *** Ubuntu 24.04 s390x lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 # apt-cache policy rsyslog rsyslog: Installed: 8.2312.0-3ubuntu9 Candidate: 8.2312.0-3ubuntu9 Version table: *** 8.2312.0-3ubuntu9 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main s390x Packages 100 /var/lib/dpkg/status Have below line in /etc/rsyslog.conf module(load="imjournal" fileCreateMode="0666" PersistStateInterval="999" StateFile="/var/spool/rsyslog/journal_state") ul 19 18:39:35 latest-logs systemd[1]: Starting rsyslog.service - System Logging Service... Jul 19 18:39:35 latest-logs rsyslogd[8647]: rsyslogd's groupid changed to 102 Jul 19 18:39:35 latest-logs rsyslogd[8647]: rsyslogd's userid changed to 102 Jul 19 18:39:35 latest-logs systemd[1]: Started rsyslog.service - System Logging Service. Jul 19 18:39:35 latest-logs rsyslogd[8647]: [origin software="rsyslogd" swVersion="8.2312.0" x-pid="8647" x-info="https://www.rsyslog.com";] start Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: No statefile exists, /var/spool/rsyslog/journal_state will be created (ignore if this is first run): No such file or directory > Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: Journal indicates no msgs when positioned at head. [v8.2312.0 try https://www.rsyslog.com/e/0 ] Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: journal files changed, reloading... [v8.2312.0 try https://www.rsyslog.com/e/0 ] Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: No statefile exists, /var/spool/rsyslog/journal_state will be created (ignore if this is first run): No such file or directory > Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: Journal indicates no msgs when positioned at head. [v8.2312.0 try https://www.rsyslog.com/e/0 ] lines 1-25/25 (END) FIle /var/spool/rsyslog/journal_state should have created and logs should have redirected to rsyslog server ** In Ubuntu 22.04 all is working as expected # lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 #apt-cache policy rsyslog rsyslog: Installed: 8.2112.0-2ubuntu2.2 Candidate: 8.2112.0-2ubuntu2.2 Version table: *** 8.2112.0-2ubuntu2.2 100 100 /var/lib/dpkg/status Use the same line as above in /etc/rsyslog.conf restart service. it did gave error about fileCreateMode which got ignored and proceeded to create the journal-state file and continued without any error Jul 19 18:44:37 systemd[1]: Starting System Logging Service... Jul 19 18:44:37 rsyslogd[13664]: error during parsing file /etc/rsyslog.conf, on or before line 16: parameter 'fileCreateMode' not known -- typo in co> Jul 19 18:44:37 systemd[1]: Started System Logging Service. Jul 19 18:44:37 rsyslogd[13664]: rsyslogd's groupid changed to 111 Jul 19 18:44:37 rsyslogd[13664]: rsyslogd's userid changed to 104 Jul 19 18:44:37 rsyslogd[13664]: [origin software="rsyslogd" swVersion="8.2112.0" x-pid="13664" x-info="https://www.rsyslog.com";] start Jul 19 18:44:37 rsyslogd[13664]: imjournal: journal files changed, reloading... [v8.2112.0 try https://www.rsyslog.com/e/0 ] /var/spool/rsyslog# ls journal_state * please help with this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2073628/+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 2083526] [NEW] FTBFS s390x: gzip: stdin: invalid compressed data--format violated
Public bug reported: Multiple build-time gzip tests are failing[1] on s390x only: 14:31:21[0] Test: ./gzipwr_flushInterval.sh config rstb_615693_cea0d3b33SOB_.conf is: 1 module(load="../plugins/imdiag/.libs/imdiag") 2 global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4 default.action.queue.timeoutEnqueue="2") 5 # use legacy-style for the following settings so that we can override if needed 6 $MainmsgQueueTimeoutEnqueue 2 7 $MainmsgQueueTimeoutShutdown 1 8 $IMDiagListenPortFileName rstb_615693_cea0d3b33SOB.imdiag.port 9 $IMDiagServerRun 0 10 $IMDiagAbortTimeout 580 11 12 :syslogtag, contains, "rsyslogd" ./rstb_615693_cea0d3b33SOB.started 13 ## end of testbench instrumentation part, test conf follows: 14 15 module(load="../plugins/imtcp/.libs/imtcp") 16 input(type="imtcp" port="0" listenPortFileName="rstb_615693_cea0d3b33SOB.tcpflood_port") 17 18 template(name="outfmt" type="string" string="%msg:F,58:2%\n") 19 :msg, contains, "msgnum:" action(type="omfile" template="outfmt" 20 zipLevel="6" ioBufferSize="256k" 21 flushOnTXEnd="off" flushInterval="1" 22 asyncWriting="on" 23 file="rstb_615693_cea0d3b33SOB.out.log.gz") rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated main Q:Reg: worker start requested, num workers currently 0 main Q:Reg: wrkr start initiated with state 0, num workers now 1 rsyslog debug: main Q:Reg: worker 0x2aa3d545730 started rsyslog debug: main Q:Reg: started with state 3, num workers now 1 14:31:21[0] rstb_615693_cea0d3b33SOB:.pid found, pid 158902 14:31:21[0] rsyslogd startup msg seen, pid 158902 waiting for file rstb_615693_cea0d3b33SOB.imdiag.port imdiag port: 35981 waiting for file rstb_615693_cea0d3b33SOB.tcpflood_port TCPFLOOD_PORT now: 37167 starting run 1 Sending 2500 messages. 2500 messages sent runtime: 0.001 End of tcpflood Run gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated scanf error in index i=0 gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format violated sequence error detected in rstb_615693_cea0d3b33SOB.out.log.gz number of lines in file: 0 rstb_615693_cea0d3b33SOB.out.log.gz sorted data has been placed in error.log, first 10 lines are: 1 scanf error in index i=0 ---last 10 lines are: 1 scanf error in index i=0 UNSORTED data, first 10 lines are: 1 scanf error in index i=0 ---last 10 lines are: 1 scanf error in index i=0 not reporting failure as RSYSLOG_STATSURL is not set rsyslog pid file still exists, trying to shutdown... rsyslogd debug: info: trying to cooperatively stop input ../plugins/imdiag/.libs/imdiag, timeout 6 ms rsyslogd debug: info: trying to cooperatively stop input imtcp, timeout 6 ms rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup rsyslog debug: 0x2aa3d5458b0: worker exiting rsyslog debug: main Q:Reg/w0: thread joined 14:31:26[5] FAIL: Test ./gzipwr_flushInterval.sh (took 5 seconds) FAIL gzipwr_flushInterval.sh (exit status: 1) So far I have seen this in noble, while preparing an SRU[2]. Don't know yet if oracular or others are also affected. 1. https://launchpadlibrarian.net/752369377/buildlog_ubuntu-noble-s390x.rsyslog_8.2312.0-3ubuntu9.1~ppa1_BUILDING.txt.gz 2. https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2083526 Title: FTBFS s390x: gzip: stdin: invalid compressed data--format violated Status in rsyslog package in Ubuntu: New Bug description: Multiple build-time gzip tests are failing[1] on s390x only: 14:31:21[0] Test: ./gzipwr_flushInterval.sh config rstb_615693_cea0d3b33SOB_.conf is: 1module(load="../plugins/imdiag/.libs/imdiag") 2global(inputs.timeout.shutdown="6" 3 default.action.queue.timeoutshutdown="2" 4 default.action.queue.timeoutEnqueue="2") 5# use legacy-style for the following settings so that we can override if needed 6$MainmsgQueueTimeoutEnqueue 2 7$MainmsgQueueTimeoutShutdown 1 8$IMDiagListenPortFileName rstb_615693_cea0d3b33SOB.imdiag.port 9$IMDiagServerRun 0 10$IMDiagAbortTimeout 580 11 12:syslogtag, contains, "rsyslogd" ./rstb_615693_cea0d3b33SOB.started 13
[Touch-packages] [Bug 2056768] Re: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/"
** Changed in: rsyslog (Ubuntu Noble) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: rsyslog (Ubuntu Noble) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2056768 Title: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Noble: In Progress Bug description: There is an AppArmor regression in current noble. In cockpit we recently started to test on noble (to prevent the "major regressions after release" fiasco from 23.10 again). For some weird reason, rsyslog is installed *by default* [1] in the cloud images. That is a rather pointless waste of CPU and disk space, as it's an unnecessary running daemon and duplicates all the written logs. But more specifically, we noticed [2] an AppArmor rejection. Reproducer is simple: logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE this causes type=1400 audit(1710168739.345:108): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567 requested_mask="r" denied_mask="r" fsuid=102 ouid=0 Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does appear in the journal and also in /var/log/syslog. But it's some noise that triggers our (and presumbly other admin's) log detectors. rsyslog 8.2312.0-3ubuntu3 apparmor 4.0.0~alpha4-0ubuntu1 [1] https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest [2] https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768/+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 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
There is a dep8 test for saslauthd[1]. I didn't check if it caught this failure, or if it didn't, why. I'm guessing because the test command (testsaslauthd) is running as root in this test. 1. https://git.launchpad.net/ubuntu/+source/cyrus-sasl2/tree/debian/tests/saslauthd?h=applied/ubuntu/noble-devel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Noble: Incomplete Status in cyrus-sasl2 source package in Oracular: Fix Released Bug description: [Impact] Incorrect ownership of files in saslauthd's run directory can result in service issues (e.g. failure to authenticate, failure to restart, etc.) [Workaround] # systemctl edit saslauthd.service Then, put the following lines inside the file: [Service] Group=sasl Save the file, and restart the service. You should now see the right permissions/owner/group under /run/saslauthd. [Test Case] $ sudo apt-get install postfix sasl2-bin $ sudo systemctl enable saslauthd $ ls -ld /run/saslauthd/ drwx--x--- 2 root sasl 40 Sep 24 23:07 /run/saslauthd/ $ sudo systemctl start saslauthd $ ls -ld /run/saslauthd/ drwxr-xr-x 2 root root 140 Sep 24 23:09 /run/saslauthd [Where Problems Could Occur] Since the fix is only in packaging and deals only with permissions, regressions would be expected to be limited to permission issues relating to packaging files (configuration, daemons, logs, etc.) Notably, the fix corrects permissions on the *directory* itself, but not on its contents. Since the problem is that root ownership of the directory prevents non-root users from adding non-root owned files there, it is unlikely this situation would crop up in practice, and if it did should be reviewed and analyzed by the user. (We would not want to auto-fix unknown root-owned file permissions to non-root.) [Original Report] Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+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 2072452] Re: AppArmor denies crun sending signals to containers
No idea what the alsa-driver task is about here, looks like it was a mistake. Removing. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Invalid ** No longer affects: alsa-driver (Ubuntu) ** Tags added: server-todo -- 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/2072452 Title: AppArmor denies crun sending signals to containers Status in runc package in Ubuntu: Confirmed Bug description: Environment: k8s 1.30.2, containerd 1.7.12 (package in ubuntu repo) When I do a k8s deployment update, the old pods stay in 'Terminating' status. The /var/log/syslog has the following messages: 2024-07-05T15:52:07.892132+08:00 km kernel: audit: type=1400 audit(1720165927.890:2191): apparmor="DENIED" operation="signal" class="signal" profile="cri-containerd.apparmor.d" pid=134029 comm="runc" requested_mask="receive" denied_mask="receive" signal=kill peer="runc" Workaround: currently I disable the apparmor.service and reboot the system. Info from github: https://github.com/moby/moby/pull/47749/files#diff-4a7aa58be335398fb04f9f1634143e158146b57c6256a2d605f9eb3c3c53d840 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jul 8 09:26:20 2024 InstallationDate: Installed on 2024-07-03 (5 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 (20240423) SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2072452/+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 2080216] Re: sshd cannot bind to IPv4 interfaces
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/openssh/+git/openssh/+merge/474189 -- 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/2080216 Title: sshd cannot bind to IPv4 interfaces Status in openssh package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 24.04 I noticed that my sshd only listening on IPv6 interface (::), while previously it was listening both IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after restart sshd was still listening on IPv6 only. This problem affects other packages as well, for example, openvpn. Rebuilding applications from sources seems to fix the issue. Setting net.ipv6.bindv6only=0 also helps, but that's not a solution. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: openssh-server 1:9.6p1-3ubuntu13.5 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 10 16:45:54 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen.xterm-256color SourcePackage: openssh UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2080216/+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 2080358] Re: liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start
Adjusting bug tasks: fixed in Oracular, needs fixing in Noble. ** Also affects: lxc (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Oracular) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2080358 Title: liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Noble: New Status in lxc source package in Oracular: Fix Released Bug description: Hi, liblxc-common 1:5.0.3-2ubuntu7 provides an AppArmor-Profile for /usr/bin/lxc-copy, but the profile file contains the rule for /usr/bin/lxc-start instead of /usr/bin/lxc-copy. The mistake was introduced in [1], current Debian versions (1:5.0.2-1 and 1:6.0.1-1) are not affected, but Ubuntu 24.04 (noble) is. This wrong profile file prevents running lxc-copy on my companies Ubuntu 24.04 machines. Can you please replace the 'lxc-start' by 'lxc-copy' in /etc/apparmor/usr.bin.lxc-copy or update to Debian's 1:6.0.1-1 or above? Thanks and kind regards, Nicolas [1]: https://salsa.debian.org/lxc- team/lxc/-/merge_requests/19/diffs?commit_id=a2ad01ca2081c4dd925037253b01fff0499af17e#d7b13f871dc297c7aa81e98c974db1a24f1b016d_0_21 --- Description: Ubuntu 24.04.1 LTS Release: 24.04 liblxc-common: Installed: 1:5.0.3-2ubuntu7 Candidate: 1:5.0.3-2ubuntu7 Version table: *** 1:5.0.3-2ubuntu7 990 990 http://de.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: liblxc-common 1:5.0.3-2ubuntu7 Uname: Linux 6.10.6 x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Wed Sep 11 12:37:23 2024 InstallationDate: Installed on 2024-08-26 (16 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: lxc UpgradeStatus: Upgraded to noble on 2024-09-04 (7 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080358/+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 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+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 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
The patch looks fine from a feature freeze point of view, but we are
very close to final freeze, and I would feel better sponsoring this if
it had approval from the release team. I left a comment in the PR, and
also it needs fixing for the oracular version.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+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 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
** Merge proposal linked:
https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/472762
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+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 2076084] Re: Additional drivers tab cause uncancellable operation that prevents the program from closing
The target of the linked pr is not a packaging branch, and this is not yet merged into the upstream branch. I left a comment in the PR asking for it to be merged or abandoned (it has two approvals already). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2076084 Title: Additional drivers tab cause uncancellable operation that prevents the program from closing Status in software-properties package in Ubuntu: Triaged Bug description: Start software-properties-gtk, switch to additional drivers tab. The program will start consuming 100% CPU for quite some time (many seconds or minutes depending on the machine). There is however no way to cancel the operation other than killing software-properties. Trying to close the window or clicking Close button hangs. Test plans -- 1. Start software-properties-gtk 1.1. Go to additional drivers tab. 1.2. Click close at the south-east corner or close the window via your window manager. Expected. Window closes immediately. 4. Start software-properties-gtk 4.1. Go to additional drivers tab and wait. Expected: The viewport will at the end say that either no drivers are available or show a list of drivers such as in the drivers-list.png attachment. The cancel/retry buttons are gone in the latter case. 2. Start software-properties-gtk and 'top' in a terminal 2.1. Go to additional drivers tab. Expected: The 'python3' command starts consuming 100% CPU. 2.2. Click cancel. Expected: The aforementioned process is no longer hogging the CPU, indicating that the driver scan really stopped. The button is now retry, clickable. 2.3. Click retry. Expected: The 'python3' command starts consuming 100% CPU. The button is now cancel. 3. Start software-properties-gtk and 'top' in a terminal 3.1. Go to additional drivers tab. 3.2. Get the PID of the 'python3' process consuming 100% CPU and kill it with kill -29 PID Expected: The viewport reports the error. Retry is clickable. 5. Start software-properties-gtk 5.1. Introduce a unconditional exception in /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py:system_device_drivers, e.g.: ---> --- /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py +++ /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py @@ -866,4 +866,5 @@ def system_device_drivers(apt_cache=None, sys_path=None, freeonly=False): +print(fooo) '''Get by-device driver packages that are available for the system. <--- 5.2. Go to additional drivers tab. Expected: "An error occurred while searching for drivers."; In the terminal, the backtrace is shown: ---> Traceback (most recent call last): File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1456, in detect_drivers raise(self.p.exception) Exception: Traceback (most recent call last): File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 121, in run multiprocessing.Process.run(self) File "/usr/lib/python3.12/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1437, in wrapper_system_device_drivers devices = detect.system_device_drivers(cache) ^^^ File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 919, in system_device_drivers print(fo) ^^ NameError: name 'fo' is not defined <--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2076084/+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 2080358] Re: liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start
Thanks for the patch. I have some questions and comments below.
a)
The profile file is /etc/apparmor.d/usr.bin.lxc-copy, which contains:
abi ,
#include
/usr/bin/lxc-start flags=(attach_disconnected) {
#include
}
There is an obvious name mismatch, but the thing is, the name of the file
doesn't matter. An apparmor profile named "/usr/bin/lxc-start" will be created
by the above profile, and it will attach to the executable /usr/bin/lxc-start,
not to /usr/bin/lxc-copy.
So in reality, /usr/bin/lxc-copy is NOT confined. Can you please
elaborate on what is breaking for you?
Is it a matter of policy? Because there are many other unconfined
profiles there:
$ grep -E "\(unconfined\)" /etc/apparmor.d/lxc-*
/etc/apparmor.d/lxc-attach:profile lxc-attach /usr/bin/lxc-attach
flags=(unconfined) {
/etc/apparmor.d/lxc-create:profile lxc-create /usr/bin/lxc-create
flags=(unconfined) {
/etc/apparmor.d/lxc-destroy:profile lxc-destroy /usr/bin/lxc-destroy
flags=(unconfined) {
/etc/apparmor.d/lxc-execute:profile lxc-execute /usr/bin/lxc-execute
flags=(unconfined) {
/etc/apparmor.d/lxc-stop:profile lxc-stop /usr/bin/lxc-stop flags=(unconfined) {
/etc/apparmor.d/lxc-unshare:profile lxc-unshare /usr/bin/lxc-unshare
flags=(unconfined) {
/etc/apparmor.d/lxc-usernsexec:profile lxc-usernsexec /usr/bin/lxc-usernsexec
flags=(unconfined) {
b) d/changelog
+lxc (1:5.0.3-2ubuntu8) UNRELEASED; urgency=medium
For the version, please follow the version convention from "Update the
packaging" from https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation.
For this case, the version should be 1:5.0.3-2ubuntu7.1
Please replace "UNRELEASED" with "noble".
+
+ * apparmor: lxc-copy: Replace mistyped filename lxc-start by lxc-copy
It's customary to list the files you are changing. In this case, you are
changing a patch file, so I would expect the changelog above to say
something like:
* d/p/0014-cherry-pick-lxc-copy-apparmor.patch: replace mistyped
filename lxc-start by lxc-copy
(with appropriate word wrapping as needed)
+
+ -- Nicolas Schier Thu, 05 Sep 2024 10:14:51 +0200
c) Bug description
Since this is targeting a stable release of ubuntu (noble), the bug description
needs to be in the SRU format:
https://canonical-sru-docs.readthedocs-hosted.com/en/latest/reference/bug-template/
The general steps to follow are outlined in https://canonical-sru-
docs.readthedocs-hosted.com/en/latest/howto/standard/
I can help and guide you through these. I would suggest to start with
the template, and we can go from there. That is, if you still want to
proceed with this bug fix, depending on the answer to (a) above (which
translates to the "impact" section of the SRU template, and helps us
gauge if this bug is worth fixing or not).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2080358
Title:
liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule
for lxc-start
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Noble:
Incomplete
Status in lxc source package in Oracular:
Fix Released
Bug description:
Hi,
liblxc-common 1:5.0.3-2ubuntu7 provides an AppArmor-Profile for
/usr/bin/lxc-copy, but the profile file
contains the rule for /usr/bin/lxc-start instead of /usr/bin/lxc-copy. The
mistake was introduced in [1], current Debian versions (1:5.0.2-1 and
1:6.0.1-1) are not affected, but Ubuntu 24.04 (noble) is. This
wrong profile file prevents running lxc-copy on my companies Ubuntu 24.04
machines.
Can you please replace the 'lxc-start' by 'lxc-copy' in
/etc/apparmor/usr.bin.lxc-copy or update to Debian's 1:6.0.1-1 or
above?
Thanks and kind regards,
Nicolas
[1]: https://salsa.debian.org/lxc-
team/lxc/-/merge_requests/19/diffs?commit_id=a2ad01ca2081c4dd925037253b01fff0499af17e#d7b13f871dc297c7aa81e98c974db1a24f1b016d_0_21
---
Description: Ubuntu 24.04.1 LTS
Release: 24.04
liblxc-common:
Installed: 1:5.0.3-2ubuntu7
Candidate: 1:5.0.3-2ubuntu7
Version table:
*** 1:5.0.3-2ubuntu7 990
990 http://de.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: liblxc-common 1:5.0.3-2ubuntu7
Uname: Linux 6.10.6 x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Wed Sep 11 12:37:23 2024
InstallationDate: Installed on 2024-08-26 (16 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
(20240220)
SourcePackage: lxc
UpgradeStatus: Upgraded to noble on 2024-09-04 (7 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080358/+subscripti
[Touch-packages] [Bug 2080358] Re: liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start
I'll mark this bug as incomplete for now, pending answers to the previous comment. ** Changed in: lxc (Ubuntu Noble) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2080358 Title: liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Noble: Incomplete Status in lxc source package in Oracular: Fix Released Bug description: Hi, liblxc-common 1:5.0.3-2ubuntu7 provides an AppArmor-Profile for /usr/bin/lxc-copy, but the profile file contains the rule for /usr/bin/lxc-start instead of /usr/bin/lxc-copy. The mistake was introduced in [1], current Debian versions (1:5.0.2-1 and 1:6.0.1-1) are not affected, but Ubuntu 24.04 (noble) is. This wrong profile file prevents running lxc-copy on my companies Ubuntu 24.04 machines. Can you please replace the 'lxc-start' by 'lxc-copy' in /etc/apparmor/usr.bin.lxc-copy or update to Debian's 1:6.0.1-1 or above? Thanks and kind regards, Nicolas [1]: https://salsa.debian.org/lxc- team/lxc/-/merge_requests/19/diffs?commit_id=a2ad01ca2081c4dd925037253b01fff0499af17e#d7b13f871dc297c7aa81e98c974db1a24f1b016d_0_21 --- Description: Ubuntu 24.04.1 LTS Release: 24.04 liblxc-common: Installed: 1:5.0.3-2ubuntu7 Candidate: 1:5.0.3-2ubuntu7 Version table: *** 1:5.0.3-2ubuntu7 990 990 http://de.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: liblxc-common 1:5.0.3-2ubuntu7 Uname: Linux 6.10.6 x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Wed Sep 11 12:37:23 2024 InstallationDate: Installed on 2024-08-26 (16 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: lxc UpgradeStatus: Upgraded to noble on 2024-09-04 (7 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080358/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
I triggered a migration-reference/0 run for the focal failed tests, let's see the outcome in a few hours. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Committed Status in e2fsprogs source package in Jammy: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Released Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2077290] Re: [SRU] GLArea transparency broken
I retried many autopkgtests just now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2077290 Title: [SRU] GLArea transparency broken Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Noble: Fix Committed Bug description: [Impact] In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42). [Test Case] Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). [Regression potential] Issues can be expected in GTK3 widgets with a transparent background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+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 2069433] Re: Enabling new pockets does not enable deb-src for them, even if source code is enabled
This is the autopkgtest bug referred to by comment #11: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2066290 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2069433 Title: Enabling new pockets does not enable deb-src for them, even if source code is enabled Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Bug description: [Impact] If you have Source Code enabled, and you change the pockets configuration to "all pockets", it will add -backports without source code. The Source Code flag will still be set in the UI, but after a reload, you can see it is in a mixed state. This is more notable now, because this splits up the deb822 paragraph into two: One for the deb, and one for deb-src, whereas it should remain one. [Test plan] 1. Turn on source code, save and refresh sources, close app 2. Start again, observe the flag is on. 3. Turn "recommended updates" to "all updates", observe that -backports got added with deb-src, to the existing paragraph. 4. Restart the app and observe that the flag is still on. [Where problems could occur] This incurs a performance regression, as we need to check the state of the source code flag after reloading sources. That said, this is of course necessary for the source code flag to be correct after reloading modified sources (it gets reset to False when reloading). And since we run in a dbus service, we may just be reloading without having made the changes ourselves, so we can't just cache the old value and restore it. That said, software-properties already times out on my oracular system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2069433/+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 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
** Description changed: [Impact] Incorrect ownership of files in saslauthd's run directory can result in service issues (e.g. failure to authenticate, failure to restart, etc.) [Workaround] # systemctl edit saslauthd.service Then, put the following lines inside the file: - [Service] - Group=sasl + [Service] + Group=sasl Save the file, and restart the service. You should now see the right permissions/owner/group under /run/saslauthd. - [Test Case] $ sudo apt-get install postfix sasl2-bin $ sudo systemctl enable saslauthd $ ls -ld /run/saslauthd/ drwx--x--- 2 root sasl 40 Sep 24 23:07 /run/saslauthd/ $ sudo systemctl start saslauthd + $ ls -ld /run/saslauthd/ drwxr-xr-x 2 root root 140 Sep 24 23:09 /run/saslauthd - [Where Problems Could Occur] Since the fix is only in packaging and deals only with permissions, regressions would be expected to be limited to permission issues relating to packaging files (configuration, daemons, logs, etc.) Notably, the fix corrects permissions on the *directory* itself, but not on its contents. Since the problem is that root ownership of the directory prevents non-root users from adding non-root owned files there, it is unlikely this situation would crop up in practice, and if it did should be reviewed and analyzed by the user. (We would not want to auto-fix unknown root-owned file permissions to non-root.) - [Original Report] Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Noble: Triaged Status in cyrus-sasl2 source package in Oracular: Fix Released Bug description: [Impact] Incorrect ownership of files in saslauthd's run directory can result in service issues (e.g. failure to authenticate, failure to restart, etc.) [Workaround] # systemctl edit saslauthd.service Then, put the following lines inside the file: [Service] Group=sasl Save the file, and restart the service. You should now see the right permissions/owner/group under /run/saslauthd. [Test Case] $ sudo apt-get install postfix sasl2-bin $ sudo systemctl enable saslauthd $ ls -ld /run/saslauthd/ drwx--x--- 2 root sasl 40 Sep 24 23:07 /run/saslauthd/ $ sudo systemctl start saslauthd $ ls -ld /run/saslauthd/ drwxr-xr-x 2 root root 140 Sep 24 23:09 /run/saslauthd [Where Problems Could Occur] Since the fix is only in packaging and deals only with permissions, regressions would be expected to be limited to permission issues relating to packaging files (configuration, daemons, logs, etc.) Notably, the fix corrects permissions on the *directory* itself, but not on its contents. Since the problem is that root ownership of the directory prevents non-root users from adding non-root owned files there, it is unlikely this situation would crop up in practice, and if it did should be reviewed and analyzed by the user. (We would not want to auto-fix unknown root-owned file permissions to non-root.) [Original Report] Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notificatio
[Touch-packages] [Bug 2081334] Re: further performance improvement for dracut-install 060
Once troubleshooting finishes, please update the test case to cover what was found. Although I suspect that would be done in the new bug, that works too of course. -- 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/2081334 Title: further performance improvement for dracut-install 060 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Noble: Fix Committed Bug description: [ Impact ] This is a follow-up for bug #2065180 implementing the suggestion from comment #44 there. When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s [User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s 10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/comments/15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on 2024-07-01): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 248.054 s ± 5.569 s [User: 67.410 s, System: 169.412 s] Range (min … max): 238.909 s … 257.384 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on 2024-07-11): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s] Range (min … max): 222.120 s … 239.610 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1011.12 and all updates on 2024-09-19): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Time (mean ± σ): 219.439 s ± 4.869 s [User: 45.626 s, System: 163.172 s] Range (min … max): 213.340 s … 227.411 s 10 runs ``` [ Reduce manual_add_modules calls ] Besides making the dracut-install calls faster, group the dracut- install calls. Since the fix in oracular can cause regressions in custom hooks that rely on the current behavior, the SRU takes a safe approach which includes following packages (stating how many dracut- install calls are used): * cryptsetup: 2 -> 1 * lvm2: 8 -> 1 * thin-provisioning-tools: 3 -> 1 * open-iscsi: 9 -> 1 * cloud-initramfs-tools: 5 -> 1 dracut-install calls on a Raspberry Pi Zero 2W: | area | before | noble SRU | oracular | |--||---|--| | auto_add_modules + apply_add_modules | 8 | 5 | 5 | | calls by hooks + apply_add_modules | 4
[Touch-packages] [Bug 2081020] Re: initrd: Ubuntu 24.04 fails to boot on UFS storage
Hello Dirk, or anyone else affected, Accepted initramfs-tools into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.142ubuntu25.3 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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. ** Changed in: initramfs-tools (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- 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/2081020 Title: initrd: Ubuntu 24.04 fails to boot on UFS storage Status in OEM Priority Project: Confirmed Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Noble: Fix Committed Bug description: [Summary] Boot into initramfs after install 24.04 on UFS storage [Steps to reproduce] 1. install ubuntu 24.04 on device with UFS storage 2. reboot As additional SRU test: 1. Store the list of files in the initrd before the package update: 3cpio -t /boot/initrd.img > before 2. Upgrade initramfs-tools to the fixed version 3. Store the list of files in the initrd afterwards: 3cpio -t /boot/initrd.img > after 4. Compare the content of the initrd: diff -u before after 5. The diff should only show (six) new kernel modules from drivers/ufs/host [Expected result] Boot into ubuntu desktop [Actual result] Boot into initramfs [Failure rate] 100% [ Where problems could occur ] The initrd size will increase by 80 kB (see comment #6) and should not trigger people to run out of disk space. Generating the initrd during package upgrade could fail due to unrelated bugs, lack of disk space, or hardware failure. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2081020/+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 2081334] Re: further performance improvement for dracut-install 060
Hello Benjamin, or anyone else affected, Accepted initramfs-tools into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.142ubuntu25.3 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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. ** Changed in: initramfs-tools (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- 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/2081334 Title: further performance improvement for dracut-install 060 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Noble: Fix Committed Bug description: [ Impact ] This is a follow-up for bug #2065180 implementing the suggestion from comment #44 there. When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s [User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s 10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/comments/15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on 2024-07-01): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 248.054 s ± 5.569 s [User: 67.410 s, System: 169.412 s] Range (min … max): 238.909 s … 257.384 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on 2024-07-11): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-
[Touch-packages] [Bug 2081334] Re: further performance improvement for dracut-install 060
** Description changed: [ Impact ] This is a follow-up for bug #2065180 implementing the suggestion from comment #44 there. When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s [User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s 10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible - regressions (see comment #15). Only miniramfs needs to be adjusted to - also call `apply_add_modules`. But this change could break consumers of - the `manual_add_modules` function that are outside of the Ubuntu - archive. I googled for `apply_add_modules` but found no public outside - users. + regressions (see + https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/comments/15). + Only miniramfs needs to be adjusted to also call `apply_add_modules`. + But this change could break consumers of the `manual_add_modules` + function that are outside of the Ubuntu archive. I googled for + `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on 2024-07-01): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 248.054 s ± 5.569 s [User: 67.410 s, System: 169.412 s] Range (min … max): 238.909 s … 257.384 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on 2024-07-11): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s] Range (min … max): 222.120 s … 239.610 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1011.12 and all updates on 2024-09-19): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Time (mean ± σ): 219.439 s ± 4.869 s [User: 45.626 s, System: 163.172 s] Range (min … max): 213.340 s … 227.411 s 10 runs ``` [ Reduce manual_add_modules calls ] Besides making the dracut-install calls faster, group the dracut-install calls. Since the fix in oracular can cause regressions in custom hooks that rely on the current behavior, the SRU takes a safe approach which includes following packages (stating how many dracut-install calls are used): * cryptsetup: 2 -> 1 * lvm2: 8 -> 1 * thin-provisioning-tools: 3 -> 1 * open-iscsi: 9 -> 1 * cloud-initramfs-tools: 5 -> 1 dracut-install calls on a Raspberry Pi Zero 2W: | area | before | noble SRU | oracular | |--||---|--| | auto_add_modules + apply_add_modules | 8 | 5 | 5 | | calls by hooks + apply_add_modules | 42 | 20 | 2 | | hidden_dep_add_modules | 1 | 1 | 1 | | total | 51 | 26 | 8 | -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscr
[Touch-packages] [Bug 2065180] Re: performance regression in dracut-install 060
Thanks for the follow-up improvements. I think, though, that they should be applied under a new bug, instead of using this one here again. If we have to chase down future regressions, or even just understand the history of these changes, that is already becoming hard here, with over 70 comments and multiple tasks. -- 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/2065180 Title: performance regression in dracut-install 060 Status in Dracut: New Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in dracut package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in miniramfs package in Ubuntu: Fix Released Status in open-iscsi package in Ubuntu: Invalid Status in thin-provisioning-tools package in Ubuntu: Fix Released Status in cloud-initramfs-tools source package in Noble: Fix Released Status in cryptsetup source package in Noble: Fix Released Status in dracut source package in Noble: Fix Released Status in initramfs-tools source package in Noble: Fix Released Status in lvm2 source package in Noble: Fix Released Status in miniramfs source package in Noble: New Status in open-iscsi source package in Noble: Fix Released Status in thin-provisioning-tools source package in Noble: Fix Released Bug description: [ Impact ] When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s[User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see comment #15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on 2024-07-01): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 248.054 s ± 5.569 s[User: 67.410 s, System: 169.412 s] Range (min … max): 238.909 s … 257.384 s10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on 2024-07-11): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s] Range (min … max): 222.120 s … 239.610 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1011.12 and all updates on 2024-09-19): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Time (mean ± σ): 21
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
The current apparmor profile for digikam in oracular has these rules: /usr/lib/x86_64-linux-gnu/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, /usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, /usr/lib/arm-linux-gnueabihf/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, There is not even a qt6 path, which in oracular is indeed without the architecture path component: $ apt-file find QtWebEngineProcess apparmor: /etc/apparmor.d/QtWebEngineProcess libqt5webenginecore5: /usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess libqt6webenginecore6-bin: /usr/lib/qt6/libexec/QtWebEngineProcess nsight-compute: /usr/lib/nsight-compute/host/linux-desktop-t210-a64/libexec/QtWebEngineProcess nsight-systems: /usr/lib/nsight-systems/host-linux-armv8/libexec/QtWebEngineProcess -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in Wike: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Fix Committed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Triaged Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in foliate package in Ubuntu: Fix Committed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Fix Released Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Fix Released Status in guix package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Fix Released Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Fix Released Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Fix Released Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Fix Released Status in qutebrowser package in Ubuntu: Fix Released Status in rssguard package in Ubuntu: Fix Released Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Fix Released Status in tellico package in Ubuntu: Fix Released Status in tor package in Ubuntu: Confirmed Status in wike package in Ubuntu: Fix Committed Status in apparmor source package in Noble: Fix Committed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
I think this should be SRUed to noble, yes. ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Noble: Triaged Status in cyrus-sasl2 source package in Oracular: Fix Released Bug description: Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
** Description changed: # README first - If you are hit by this bug, please check if your root user's environment - has the "errors" variable set: + https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/62 + has the details. If you are hit by this bug, please check if your root + user's environment has the "errors" variable set: env | grep errors - sudo env | grep errors + And then unset the variable and run "apt -f install" (or repeat the apt + operation that failed and brought you here) [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Status in python3-defaults source package in Focal: Confirmed Status in python3-defaults source package in Jammy: Confirmed Status in python3-defaults source package in Noble: Confirmed Status in python3-defaults source package in Oracular: Confirmed Bug description: # README first https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/62 has the details. If you are hit by this bug, please check if your root user's environment has the "errors" variable set: env | grep errors And then unset the variable and run "apt -f install" (or repeat the apt operation that failed and brought you here) [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
Oracular also affected, obviously: Good case: root@o-py3-errors:~# apt install --reinstall python3 Summary: Upgrading: 0, Installing: 0, Reinstalling: 1, Removing: 0, Not Upgrading: 0 Download size: 0 B / 24.0 kB Space needed: 0 B / 98.5 GB available (Reading database ... 35925 files and directories currently installed.) Preparing to unpack .../python3_3.12.5-1_amd64.deb ... running python pre-rtupdate hooks for python3.12... Unpacking python3 (3.12.5-1) over (3.12.5-1) ... Setting up python3 (3.12.5-1) ... running python rtupdate hooks for python3.12... running python post-rtupdate hooks for python3.12... Processing triggers for man-db (2.12.1-3) ... The bug: root@o-py3-errors:~# errors=andreas-was-here apt install --reinstall python3 Summary: Upgrading: 0, Installing: 0, Reinstalling: 1, Removing: 0, Not Upgrading: 0 Download size: 0 B / 24.0 kB Space needed: 0 B / 98.5 GB available (Reading database ... 35925 files and directories currently installed.) Preparing to unpack .../python3_3.12.5-1_amd64.deb ... running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.5-1_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.5-1_amd64.deb Error: Sub-process /usr/bin/dpkg returned an error code (1) ** Also affects: python3-defaults (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Oracular) Importance: Undecided Status: Confirmed ** Description changed: # README first - If you are hit by this bug, please provide the information asked in the - comment #53 further down in this page, thanks + If you are hit by this bug, please check if your root user's environment + has the "errors" variable set: + + env | grep errors + + sudo env | grep errors + [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: python3-defaults (Ubuntu Focal) Status: New => Confirmed ** Changed in: python3-defaults (Ubuntu Jammy) Status: New => Confirmed ** Changed in: python3-defaults (Ubuntu Noble) Status: New => Confirmed ** Changed in: python3-defaults (Ubuntu Focal) Importance: Undecided => High ** Changed in: python3-defaults (Ubuntu Jammy) Importance: Undecided => High ** Changed in: python3-defaults (Ubuntu Noble) Importance: Undecided => High ** Changed in: python3-defaults (Ubuntu Oracular) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Status in python3-defaults source package in Focal: Confirmed Status in python3-defaults source package in Jammy: Confirmed Status in python3-defaults source package in Noble: Confirmed Status in python3-defaults source package in Oracular: Confirmed Bug description: # README first If you are hit by this bug, please check if your root user's environment has the "errors" variable set: env | grep errors sudo env | grep errors [ O
[Touch-packages] [Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
Amazing find @theofficialgman! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: # README first If you are hit by this bug, please provide the information asked in the comment #53 further down in this page, thanks [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2076542] Re: FTBFS with autoconf 2.72
This was fixed in https://launchpad.net/debian/+source/heimdal/7.8.git20221117.28daf24+dfsg-8, and we have 8ubuntu1 in oracular (with the fix too). ** Changed in: heimdal (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2076542 Title: FTBFS with autoconf 2.72 Status in heimdal package in Ubuntu: Fix Released Status in heimdal package in Debian: Fix Released Bug description: checking for gcc options needed to detect all undeclared functions... cannot detect configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal': configure: error: cannot make gcc report undeclared builtins See 'config.log' for more details and configure:19563: gcc -c -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1 -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= -D_FILE_OFFSET_BITS= conftest.c >&5 In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/limits.h:26, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210, from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34, from conftest.c:50: /usr/include/features.h:398:52: error: operator '&&' has no right operand 398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 |^~ conftest.c:41:16: error: duplicate 'unsigned' 41 | #define size_t unsigned int |^~~~ conftest.c:41:25: error: two or more data types in declaration specifiers 41 | #define size_t unsigned int | ^~~ Looks like _FILE_OFFSET_BITS is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2076542/+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 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~18.04 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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.
** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
Status: New => Fix Committed
** Tags added: verification-needed-xenial
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Packag
[Touch-packages] [Bug 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into xenial-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~16.04 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-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. 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.
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKer
[Touch-packages] [Bug 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~22.04 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.
** Changed in: ubuntu-advantage-tools (Ubuntu Focal)
Status: New => Fix Committed
** Tags added: verification-needed-focal
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubu
[Touch-packages] [Bug 2055239] Please test proposed package
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~20.04 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.
** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed-bionic
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: u
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Hello Nobuto, or anyone else affected,
Accepted ubuntu-advantage-tools into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/34~24.04 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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.
** Changed in: ubuntu-advantage-tools (Ubuntu Noble)
Status: In Progress => Fix Committed
** Tags removed: verification-done verification-done-noble
** Tags added: verification-needed verification-needed-noble
** Changed in: ubuntu-advantage-tools (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-needed-jammy
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
Fix Committed
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Fix Committed
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information relat
[Touch-packages] [Bug 2075332] Re: FTBFS with gcc-14
This migrated.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2075332
Title:
FTBFS with gcc-14
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
https://launchpadlibrarian.net/741628620/buildlog_ubuntu-oracular-
amd64.cyrus-sasl2_2.1.28+dfsg1-6_BUILDING.txt.gz
In file included from ../../include/hmac-md5.h:7,
from ../../include/saslplug.h:11,
from ../../lib/common.c:60:
/usr/include/openssl/md5.h:49:27: note: declared here
49 | OSSL_DEPRECATEDIN_3_0 int MD5_Init(MD5_CTX *c);
| ^~~~
../../lib/common.c:2034:19: error: assignment to ‘void (*)(MD5_CTX *)’ {aka
‘void (*)(struct MD5state_st *)’} from incompatible pointer type ‘int
(*)(MD5_CTX *)’ {aka ‘int (*)(struct MD5state_st *)’}
[-Wincompatible-pointer-types]
2034 | utils->MD5Init = &MD5_Init;
| ^
../../lib/common.c:2035:3: warning: ‘MD5_Update’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2035 | utils->MD5Update= &MD5_Update;
| ^
/usr/include/openssl/md5.h:50:27: note: declared here
50 | OSSL_DEPRECATEDIN_3_0 int MD5_Update(MD5_CTX *c, const void *data,
size_t len);
| ^~
../../lib/common.c:2035:19: error: assignment to ‘void (*)(MD5_CTX *, const
unsigned char *, unsigned int)’ {aka ‘void (*)(struct MD5state_st *, const
unsigned char *, unsigned int)’} from incompatible pointer type ‘int
(*)(MD5_CTX *, const void *, size_t)’ {aka ‘int (*)(struct MD5state_st *, const
void *, long unsigned int)’} [-Wincompatible-pointer-types]
2035 | utils->MD5Update= &MD5_Update;
| ^
../../lib/common.c:2036:3: warning: ‘MD5_Final’ is deprecated: Since OpenSSL
3.0 [-Wdeprecated-declarations]
2036 | utils->MD5Final = &MD5_Final;
| ^
/usr/include/openssl/md5.h:51:27: note: declared here
51 | OSSL_DEPRECATEDIN_3_0 int MD5_Final(unsigned char *md, MD5_CTX *c);
| ^
../../lib/common.c:2036:19: error: assignment to ‘void (*)(unsigned char *,
MD5_CTX *)’ {aka ‘void (*)(unsigned char *, struct MD5state_st *)’} from
incompatible pointer type ‘int (*)(unsigned char *, MD5_CTX *)’ {aka ‘int
(*)(unsigned char *, struct MD5state_st *)’} [-Wincompatible-pointer-types]
2036 | utils->MD5Final = &MD5_Final;
| ^
../../lib/common.c: In function ‘_sasl_find_verifyfile_callback’:
../../lib/common.c:2165:5: warning: cast between incompatible function types
from ‘int (*)(void *, char *, int)’ to ‘int (*)(void)’ [-Wcast-function-type]
2165 | (sasl_callback_ft)&_sasl_verifyfile,
| ^
make[5]: *** [Makefile:608: common.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2075332/+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 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
I just synced 2.1.28+dfsg1-8 from debian, which contains the fix. ** Changed in: cyrus-sasl2 (Ubuntu Oracular) Status: Triaged => Fix Committed ** Tags added: bite-size -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd Status in cyrus-sasl2 package in Ubuntu: Fix Committed Status in cyrus-sasl2 source package in Noble: Triaged Status in cyrus-sasl2 source package in Oracular: Fix Committed Bug description: Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+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 2078720] Please test proposed package
Hello Ankush, or anyone else affected, Accepted apt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.4.13 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. -- 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/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state Status in apt package in Ubuntu: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in apt source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: New Status in linux-gcp source package in Jammy: New Status in apt source package in Noble: New Status in linux-aws source package in Noble: New Status in linux-gcp source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: In Progress Bug description: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] ## Jammy APT verification To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm If using lxc shell or exec to connect to it, also perform the step b
[Touch-packages] [Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
I was able to reproduce this in jammy lxd VM, and tweaked the test plan a bit. I'm going to accept this into jammy-proposed in order to allow for testing to begin quickly, but we still need the noble and oracular uploads as well. The APT noble test plan could also use some refinement, there are still too many unknowns there, and not clear steps as to what should happen and what shouldn't. ** Description changed: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] ## Jammy APT verification To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm - $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets - To validate the apt change on jammy, + If using lxc shell or exec to connect to it, also perform the step + below: - Edit /etc/update-manager/release-upgrades and set Prompt to "normal" - (since release upgrades to noble via the lts prompt are temporarily - blocked due to this bug) + $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it + resets + + + On this jammy VM, edit /etc/update-manager/release-upgrades and set Prompt to "normal" (since release upgrades to noble via the lts prompt are temporarily blocked due to this bug) $ sudo do-release-upgrade After the reboot at the end, in the rebooted system, issue: $ sudo apt upgrade With the bug present, you will get an error like this: $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: - linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable + linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ## Noble APT verification To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU]
[Touch-packages] [Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Description changed: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] + ## Jammy APT verification + To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets To validate the apt change on jammy, - ubuntu@jammy-to-noble$ add-apt-repository -p proposed - ubuntu@jammy-to-noble$ apt install libapt-pkg6.0 # to upgrade libapt-pkg6.0 - ubuntu@jammy-to-noble$ do-release-upgrade + Edit /etc/update-manager/release-upgrades and set Prompt to "normal" + (since release upgrades to noble via the lts prompt are temporarily + blocked due to this bug) + + $ sudo do-release-upgrade + + After the reboot at the end, in the rebooted system, issue: + + $ sudo apt upgrade + + With the bug present, you will get an error like this: + $ sudo apt upgrade + Reading package lists... Done + Building dependency tree... Done + Reading state information... Done + You might want to run 'apt --fix-broken install' to correct these. + The following packages have unmet dependencies: + linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable + E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). + + + ## Noble APT verification To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU] For the APT change, the function in question is used in a small number of places: In APT library: - In the `upgrade` command and library function. Removals are already undone there before calling it so we never reach the new code path. - In the phased update implementation, during dist-upgrade. I expect a failure is lurking there that is fixed by this, but I haven't been able to write a reproducer to trigger it just yet. In aptitude: - The function is wrapped, but the wrapper never called In QApt: - QApt seems to rely on it for upgrading and doesn't seem to have any error checking of the return value. I expect it will read the er
[Touch-packages] [Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Description changed: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] To prepare the VMs, follow the following scheme: - $ lxc launch ubuntu:jammy jammy-to-noble + $ lxc launch ubuntu:jammy jammy-to-noble --vm $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets To validate the apt change on jammy, ubuntu@jammy-to-noble$ add-apt-repository -p proposed ubuntu@jammy-to-noble$ apt install libapt-pkg6.0 # to upgrade libapt-pkg6.0 ubuntu@jammy-to-noble$ do-release-upgrade To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU] For the APT change, the function in question is used in a small number of places: In APT library: - In the `upgrade` command and library function. Removals are already undone there before calling it so we never reach the new code path. - In the phased update implementation, during dist-upgrade. I expect a failure is lurking there that is fixed by this, but I haven't been able to write a reproducer to trigger it just yet. In aptitude: - The function is wrapped, but the wrapper never called In QApt: - QApt seems to rely on it for upgrading and doesn't seem to have any error checking of the return value. I expect it will read the error [Where problems could occur: u-r-u SRU] Upgrades will now result in a consistent state, but may spend hours searching for obsolete software again. -- 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/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state Status in apt package in Ubuntu: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in apt source package in Jammy: In Progress Status in linux-aws source package in Jammy: New Status in linux-gcp source package in Jammy: New Status in a
[Touch-packages] [Bug 1769297] Update Released
The verification of the Stable Release Update for initramfs-tools 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1769297
Title:
resume from hibernation broken when resume image is autodetected
(UUID= syntax used)
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Noble:
Fix Committed
Bug description:
[ Impact ]
I found a reason of non-functioning resume from hibernation when
resume partition/file is autodetected by intiramfs hook
/usr/share/initramfs-tools/hooks/resume.
Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable:
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
2) during boot init script sets 'resume' variable to 'RESUME' value
from conf/conf.d/zz-resume-auto, then it executes local-premount
scripts including local-premount/resume
3) resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor numbers by these lines:
DEV=$(readlink ${resume})
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read MAJMIN < "$DEV"
fi
4) next check fails and resume process silently aborts:
if [ -z "$MAJMIN" ]; then
exit 1
fi
Resuming script fails to get device major-minor because
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
into device path in init script.
Commonly mentioned workaround is to explicitly specify kernel
parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
this case init script resolves it to device path.
[ Test Plan ]
1. hibernate: `sudo systemctl hibernate`
2. resume from hibernate
3. `cat /sys/power/resume` should contain the major-minor of the swap
[ Other Info ]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
Uname: Linux 4.16.6-041606-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 5 11:32:31 2018
InstallationDate: Installed on 2018-03-27 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 2003027] Re: fq_codel qdisc compiled but not enabled on 22.10
This failed to build on arm64, whereas the previous version built, so it's a regression. Can somebody troubleshoot that failure please? Seems like a build-time test failure, so for now I triggered a new build attempt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2003027 Title: fq_codel qdisc compiled but not enabled on 22.10 Status in Ubuntu: Fix Released Status in procps package in Ubuntu: Fix Released Status in The Noble Numbat: Confirmed Status in procps source package in Noble: Fix Committed Status in The Oracular Oriole: Fix Released Status in procps source package in Oracular: Fix Released Bug description: [ Impact ] Starting with Ubuntu 22.10, the default qdisc regressed to pfifo_fast. This is due to a change we merged from Debian, removing systemd's /usr/lib/50-default.conf file. pfifo_fast does not prevent bufferbloat issues, severely degrading networking performance on Ubuntu systems. [ Test Plan ] On an Ubuntu VM, check that net.core.default_qdisc is set to 'fq_codel'. `tc qdisc show` should also confirm fq_codel is being used. halves@noble-vm:~$ sysctl net.core.default_qdisc net.core.default_qdisc = fq_codel halves@noble-vm:~$ tc qdisc show qdisc noqueue 0: dev lo root refcnt 2 qdisc mq 0: dev enp5s0 root qdisc fq_codel 0: dev enp5s0 parent :1 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64 [ Where Problems Could Occur ] Users relying on the default pfifo_fast qdisc could see different networking behavior. Although fq_codel should be an across-the-board improvement over pfifo_fast, we could monitor network latency stats and throughput to make sure no weird regressions arise from the qdisc scheduler. [ Other Info ] Instead of adding a sysctl.conf file, Debian has decided to change their default kernel configs to use fq_codel. This has the disadvantage of being "hidden" from end users, instead of being a queryable setting in e.g. /etc/sysctl.d/, and all kernel documentation still refers to pfifo_fast as being the default. Systemd's /usr/lib/50-default.conf file includes a lot of other settings that are either overruled elsewhere (e.g. from procps) or are entirely missing from our stable releases. Introducing a diff from Debian to ship this file only for the net.core.default_qdisc changes seems excessive, so having a dedicated place under procps where other similar toggles are already present seems like the more appropriate solution. -- [ Original Description ] fq_codel has been the default in ubuntu since #1436945 It is also now the default in debian. Somewhere between 22.04 and 22.10 though, it stopped being enabled by systemd? (it used to be enabled there via a sysctl), and thus 22.10 (I tried both ubuntu server and ubuntu studio) doesn't have it on. I rather *immediately* noticed this huge regression (I run my ethernet at 100Mbit, and thus immediately saw 400+ms latency) - and I hope it can be fixed in the next release? it can also be made the default via compiling it into the kernel as a kernel default. Aggh! death to fifos! root@localhost:~# sysctl -a | grep qdisc net.core.default_qdisc = pfifo_fast disc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 5250 bytes 53 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2003027/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
We tried multiple things to reproduce this bug, to no avail.
My last attempt was to inject an actual error in one of the
/usr/share/python3/runtime.d/*.rtupdate scripts to see how the upgrade (or
reinstall) would behave, and it does as expected:
Preparing to unpack .../python3_3.12.3-0ubuntu2_amd64.deb ...
running python pre-rtupdate hooks for python3.12...
stdout: andreas was here
stderr: andreas was here
error running python pre-rtupdate hook byobu
running python failed-pre-rtupdate hook byobu
stdout: andreas was here
stderr: andreas was here
dpkg: error processing archive
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack):
new python3 package pre-installation script subprocess returned error exit
status 1
Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ...
Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ...
Errors were encountered while processing:
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
We can see that:
a) pre-rtupdate hooks are run ("running python pre-rtupdate hooks for
python3.12...")
b) stdout and stderr of the failing rdupdate script are shown ("andreas was
here")
c) there is an error message saying exactly which hook failed ("error running
python pre-rtupdate hook byobu")
From the logs we have seen so far attached to this bug, we only get (a)
in them. Not (b) or (c).
I also tried release upgrades from jammy to noble, desktop and server,
and python upgrades in ubuntu desktop noble, and also couldn't reproduce
the error.
I'll mark this bug as incomplete reflecting the status that we have
tried many different ways to understand and reproduce this bug, but
haven't been successful yet.
** Changed in: python3-defaults (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2078356
Title:
python3 preinst failure to run pre-rtupdate hooks
Status in python3-defaults package in Ubuntu:
Incomplete
Bug description:
# README first
If you are hit by this bug, please provide the information asked in
the comment #53 further down in this page, thanks
[ Original Description ]
running python pre-rtupdate hooks for python3.12...
dpkg: error processing archive
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack):
new python3 package pre-installation script subprocess returned error exit
status 3
Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ...
Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ...
Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ...
Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ...
Errors were encountered while processing:
/var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: python3 3.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 29 10:52:19 2024
InstallationDate: Installed on 2024-07-13 (47 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078600] Re: package python3-dev 3.10.6-1~22.04.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置
Thanks for reporting this. Can you please run these commands and show the output: apt-cache policy asymptote python3 python3-minimal dpkg -L asymptote sudo apt -f install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078600 Title: package python3-dev 3.10.6-1~22.04.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置 Status in python3-defaults package in Ubuntu: New Bug description: when my pc start,the bug start ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3-dev 3.10.6-1~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Sep 1 08:59:13 2024 DpkgHistoryLog: Start-Date: 2024-09-01 08:58:07 Commandline: aptdaemon role='role-commit-packages' sender=':1.139' Upgrade: libext2fs2:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), libpython3-dev:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), python3-minimal:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), deepin-wine-helper:amd64 (5.3.16-1, 5.3.20-1), python3:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), libcom-err2:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), libcom-err2:i386 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), ubuntu-pro-client-l10n:amd64 (32.3.1~22.04, 33.2~22.04), python3-dev:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), libpython3-stdlib:amd64 (3.10.6-1~22.04, 3.10.6-1~22.04.1), logsave:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), ubuntu-advantage-tools:amd64 (32.3.1~22.04, 33.2~22.04), libss2:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), microsoft-edge-stable:amd64 (127.0.2651.105-1, 128.0.2739.54-1), e2fsprogs:amd64 (1.46.5-2ubuntu1.1, 1.46.5-2ubuntu1.2), ubuntu-pro-client:amd64 (32.3.1~22.04, 33.2~22.04) ErrorMessage: 依赖关系问题 - 仍未被配置 InstallationDate: Installed on 2024-04-09 (145 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: python3-defaults Title: package python3-dev 3.10.6-1~22.04.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078600/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
** Description changed: + # README first + + If you are hit by this bug, please provide the information asked in the + comment + https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/53 + further down in this page, thanks + + + [ Original Description ] + running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): - new python3 package pre-installation script subprocess returned error exit status 3 + new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: - /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb + /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: # README first If you are hit by this bug, please provide the information asked in the - comment - https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/53 - further down in this page, thanks - + comment comment #53 further down in this page, thanks [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: # README first If you are hit by this bug, please provide the information asked in the - comment comment #53 further down in this page, thanks + comment #53 further down in this page, thanks [ Original Description ] running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architec
[Touch-packages] [Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
> This bug has now affected (infected?) my third server which is running 22.04.4. Could you please get me the information from comment #53 about that system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2075337] Re: [SRU] py3clean fails when using alternate character set
Potential regression-update in https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tools dhcpy6d|dhcpy6d dkimpy-milter|dkimpy-milter fenrir|fenrir galileo|galileo glances|glances graphite-carbon|graphite-carbon grokmirror|grokmirror guerillabackup|guerillabackup ionit|ionit jupyterhub|jupyterhub liquidctl|liquidctl localslackirc|localslackirc logdata-anomaly-miner|logdata-anomaly-miner lomiri|lomiri mailman3|mailman3 mailman3-full|mailman3 matrix-sydent|matrix-sydent mom|mom mopidy|mopidy mpd-sima|mpd-sima nordugrid-arc-arex|nordugrid-arc notus-scanner|notus-scanner nrpe-ng|nrpe-ng onionprobe|onionprobe openscap-daemon|openscap-daemon ospd-openvas|ospd-openvas pagekite|pagekite pagure|pagure pagure-ev-server|pagure pagure-milters|pagure pglistener|pglistener policyd-rate-limit|policyd-rate-limit postfix-mta-sts-resolver|postfix-mta-sts-resolver powa-collector|powa-collector prelude-correlator|prelude-correlator prometheus-pgbouncer-exporter|prometheus-pgbouncer-exporter prometheus-xmpp-alerts|prometheus-xmpp-alerts pyroman|pyroman python3-autopilot|autopilot python3-btchip|btchip-python python3-pyro5|pyro5 qweborf|weborf razercfg|razercfg sgt-launcher|sgt-launcher sms4you|sms4you supervisor|supervisor syncplay-server|syncplay timekpr-next|timekpr
[Touch-packages] [Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
I'm gonna tag this with regression-update, even though it's not yet clear what is going on, but clearly it is affecting some users (bug heat is 28 at the moment). Potential regression-update of https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337 ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
I tried even an ubuntu desktop, I still cannot reproduce this. To those affected, please provide the output of these commands, if you haven't already: - apt-cache policy python3 libpython3-stdlib python3-gdbm python3-lib2to3 python3-minimal - locale - dpkg -S /usr/share/python3/runtime.d/* - cat /var/lib/dpkg/info/python3.preinst - dpkg -S $(which py3compile) $(which py3clean) - sudo apt install -f -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
** Summary changed: - python3 upgrade has unmet dependencies + python3 preinst failure to run pre-rtupdate hooks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078489] Re: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3
*** This bug is a duplicate of bug 2078356 *** https://bugs.launchpad.net/bugs/2078356 ** This bug has been marked a duplicate of bug 2078356 python3 upgrade has unmet dependencies -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078489 Title: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3 Status in python3-defaults package in Ubuntu: Confirmed Bug description: After system rquired reboot to install upgrades ProblemType: Package DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 AptOrdering: python3-minimal:amd64: Install python3-minimal:amd64: Configure python3:amd64: Install libpython3-stdlib:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 29 18:48:06 2024 DpkgTerminalLog: Preparing to unpack .../python3_3.12.3-0ubuntu2_amd64.deb ... running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 DuplicateSignature: package:python3:3.12.3-0ubuntu1 Preparing to unpack .../python3_3.12.3-0ubuntu2_amd64.deb ... running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 ErrorMessage: new python3 package pre-installation script subprocess returned error exit status 3 InstallationDate: Installed on 2024-07-13 (48 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: python3-defaults Title: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078489/+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 2078356] Re: python3 upgrade has unmet dependencies
It doesn't look like it's the update itself, because as can be seen in https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/33, reinstalling the non-update version also triggered it. I'm starting to think it could be one of the /usr/share/python3/runtime.d/*.rtupdate scripts that get executed, but I installed the same ones as listed in https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/comments/6 and still couldn't reproduce the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks Status in python3-defaults package in Ubuntu: Confirmed Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
You don't have /var/log/apt/history.log nor /var/log/apt/term.log? Just the rotated .1 versions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Oh, and /var/log/dpkg.log too please -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Ok, maybe the script is being called with redirection to a log file. That doesn't explain why you didn't have the script in place, but let's check some logs. Could you please attach the following to this bug: /var/log/apt/*.log /var/log/syslog output of "dmesg -T" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
It's just not being executed, because we are not seeing the "set -x" output (which would be very noisy). Did you do something different to this system that you can recall? Install python from source, or packages from debian instead of ubuntu, or anywhere else? That kind of thing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
And there is no /var/lib/dpkg/info/python3.preinst now? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
We should reinstall python3 to get things back to what they were, as much as possible. Run: sudo apt install --reinstall python3=3.12.3-0ubuntu1 And then, leave the system as is if there are no further errors. Maybe tomorrow someone has another idea to try. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
ok, well, that's good. Means there is this fallback that works. I still don't know why the upgrade failed for you. What does /var/lib/dpkg/info/python3.preinst look like now? ls -la /var/lib/dpkg/info/python3.preinst cat /var/lib/dpkg/info/python3.preinst -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
The "-s" was a simulation :) I wanted to check which packages would be downgraded, and the list looks correct. So let's try it without the -s: sudo apt install python3-minimal=3.12.3-0ubuntu1 libpython3-stdlib=3.12.3-0ubuntu1 python3=3.12.3-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
What's the output of this command: sudo apt install -s python3-minimal=3.12.3-0ubuntu1 libpython3-stdlib=3.12.3-0ubuntu1 python3=3.12.3-0ubuntu1 This would be a revert attempt to the previous version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
I'm baffled, you clearly have python3 installed, but no /var/lib/dpkg/info/python3.preinst and you had to create it by hand? What do you get with this: ls -la /var/lib/dpkg/info/python3*preinst And this: py3versions -i -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
> N: Unable to locate package python3-mininal Sorry, that was a typo on my part, it should have been python3-minimal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
> Okay, created the file /var/lib/dpkg/info/python3.preinst and executed it. No, you shouldn't have done that. If you had to create it, something else is very wrong on your system. That comes from the python3 debian package. Did you manage to check what I asked in comment #14 above? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
> That script does not exist on my system. (/var/lib/dpkg/info/python3.preinst) Huh, that's unexpected. Do you have the python3 package installed? dpkg -l python3 python3-minimal apt-cache policy python3 python3-mininal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Sorry, I should have been more clear. If you are willing to help debug this further, then please add "set -x" just below the existing "set -e" in /var/lib/dpkg/info/python3.preinst and then run "sudo apt -f install" again. It should output a lot more debugging information. After that, you can undo your change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
if you want, you could add a "set -x" to that script (/var/lib/dpkg/info/python3.preinst) and then run the apt -f install again -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
The preinst goes over those scripts in /usr/share/python3/runtime.d and executes them one by one. It's supposed to show the error if one of them fails, but I don't see that in your output... #! /bin/sh set -e # remove the python3 alternatives before installing our own python3 link update-alternatives --auto /usr/bin/python3 >/dev/null 2>&1 || true [ -L /usr/share/doc/python3/html ] || rm -rf /usr/share/doc/python3/html case "$1" in upgrade) oldv=$(echo $2 | sed 's/^\(...\).*/\1/') if [ "$DEBIAN_FRONTEND" != noninteractive ]; then echo "running python pre-rtupdate hooks for python3.12..." fi for hook in /usr/share/python3/runtime.d/*.rtupdate; do [ -x $hook ] || continue if ! $hook pre-rtupdate python$oldv python3.12; then hb=$(basename $hook .rtupdate) echo >&2 "error running python pre-rtupdate hook $hb" echo >&2 "running python failed-pre-rtupdate hook $hb" $hook failed-pre-rtupdate python$oldv python3.12 errors=yes break fi done [ -z "$errors" ] || exit 3 esac -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
I can't reproduce this, and I have the same files in /usr/share/python3/runtime.d. @waveform, any idea what's going on here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
What do you have in /usr/share/python3/runtime.d/? ls -la /usr/share/python3/runtime.d/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2078356] Re: python3 upgrade has unmet dependencies
Please show the full output of: sudo apt -f install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies Status in python3-defaults package in Ubuntu: New Bug description: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Preparing to unpack .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.3-0ubuntu2) over (3.12.3-0ubuntu1) ... Preparing to unpack .../libsmartcols1_2.39.3-9ubuntu6.1_amd64.deb ... Unpacking libsmartcols1:amd64 (2.39.3-9ubuntu6.1) over (2.39.3-9ubuntu6) ... Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3 3.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:52:19 2024 InstallationDate: Installed on 2024-07-13 (47 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+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 2075988] Re: Add comments to default config to explain Ubuntu deltas
This is fix released for oracular: https://git.launchpad.net/ubuntu/+source/openssh/tree/sshd_config?h=applied/ubuntu/oracular- devel#n15 ** Also affects: openssh (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Oracular) Importance: Low Status: Incomplete ** Changed in: openssh (Ubuntu Oracular) Status: Incomplete => Fix Released -- 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/2075988 Title: Add comments to default config to explain Ubuntu deltas Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Noble: New Status in openssh source package in Oracular: Fix Released Bug description: Hello, reading https://discourse.ubuntu.com/t/sshd-now-uses-socket- based-activation-ubuntu-22-10-and-later/30189/44 a great point is made here. Can we put some comments in the default config explaining the deltas we make? This would be the most visible place for end-users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2075988/+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 2075337] Re: [SRU] py3clean fails when using alternate character set
I verified ubuntu-pro-client from noble-proposed. First, reproducing the bug with old python3-minimal and current pro client (notice *** installed versions): root@n:~# apt-cache policy python3-minimal ubuntu-pro-client python3-minimal: Install�: 3.12.3-0ubuntu1 Candidat�: 3.12.3-0ubuntu2 Table de version�: 3.12.3-0ubuntu2 500 (phased 80%) 500 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages *** 3.12.3-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ubuntu-pro-client: Install�: 32.3.1~24.04 Candidat�: 32.3.1~24.04 Table de version�: 33.2~24.04.1 100 100 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages *** 32.3.1~24.04 500 500 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 31.2.3 500 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages root@n:~# apt install ubuntu-pro-client --reinstall Lecture des listes de paquets... Fait Construction de l'arbre des d�pendances... Fait Lecture des informations d'�tat... Fait 0 mis � jour, 0 nouvellement install�s, 1 r�install�s, 0 � enlever et 57 non mis � jour. Il est n�cessaire de prendre 229 ko dans les archives. Apr�s cette op�ration, 0 o d'espace disque suppl�mentaires seront utilis�s. R�ception de�:1 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 ubuntu-pro-client amd64 32.3.1~24.04 [229 kB] 229 ko r�ceptionn�s en 0s (2�031 ko/s) (Lecture de la base de donn�es... 34410 fichiers et r�pertoires d�j� install�s.) Pr�paration du d�paquetage de .../ubuntu-pro-client_32.3.1~24.04_amd64.deb ... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 584: invalid continuation byte Now I upgrade pro-client to the noble-proposed version. What I expect is that python3-minimal will be pulled in due to pro's Breaks, and no backtrace: root@n:~# apt install ubuntu-pro-client -t noble-proposed Lecture des listes de paquets... Fait Construction de l'arbre des d�pendances... Fait Lecture des informations d'�tat... Fait Les paquets suppl�mentaires suivants seront install�s�: libpython3-stdlib python3 python3-minimal ubuntu-pro-client-l10n Paquets sugg�r�s�: python3-doc python3-tk python3-venv Les paquets suivants seront mis � jour�: libpython3-stdlib python3 python3-minimal ubuntu-pro-client ubuntu-pro-client-l10n 5 mis � jour, 0 nouvellement install�s, 0 � enlever et 86 non mis � jour. Il est n�cessaire de prendre 311 ko dans les archives. Apr�s cette op�ration, 12,3 ko d'espace disque suppl�mentaires seront utilis�s. Souhaitez-vous continuer�? [O/n] R�ception de�:1 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 python3-minimal amd64 3.12.3-0ubuntu2 [27,4 kB] R�ception de�:2 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 python3 amd64 3.12.3-0ubuntu2 [23,0 kB] R�ception de�:3 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 libpython3-stdlib amd64 3.12.3-0ubuntu2 [10,0 kB] R�ception de�:4 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 ubuntu-pro-client-l10n amd64 33.2~24.04.1 [19,3 kB] R�ception de�:5 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 ubuntu-pro-client amd64 33.2~24.04.1 [231 kB] 311 ko r�ceptionn�s en 0s (2�900 ko/s) (Lecture de la base de donn�es... 34410 fichiers et r�pertoires d�j� install�s.) Pr�paration du d�paquetage de .../python3-minimal_3.12.3-0ubuntu2_amd64.deb ... D�paquetage de python3-minimal (3.12.3-0ubuntu2) sur (3.12.3-0ubuntu1) ... Param�trage de python3-minimal (3.12.3-0ubuntu2) ... (Lecture de la base de donn�es... 34410 fichiers et r�pertoires d�j� install�s.) Pr�paration du d�paquetage de .../python3_3.12.3-0ubuntu2_amd64.deb ... running python pre-rtupdate hooks for python3.12... D�paquetage de python3 (3.12.3-0ubuntu2) sur (3.12.3-0ubuntu1) ... Pr�paration du d�paquetage de .../libpython3-stdlib_3.12.3-0ubuntu2_amd64.deb ... D�paquetage de libpython3-stdlib:amd64 (3.12.3-0ubuntu2) sur (3.12.3-0ubuntu1) ... Pr�paration du d�paquetage de .../ubuntu-pro-client-l10n_33.2~24.04.1_amd64.deb ... D�paquetage de ubuntu-pro-client-l10n (33.2~24.04.1) sur (32.3.1~24.04) ... Pr�paration du d�paquetage de .../ubuntu-pro-client_33.2~24.04.1_amd64.deb ... D�paquetage de ubuntu-pro-client (33.2~24.04.1) sur (32.3.1~24.04) ... Param�trage de libpython3-stdlib:amd64 (3.12.3-0ubuntu2) ... Param�trage de python3 (3.12.3-0ubuntu2)
[Touch-packages] [Bug 2075337] Update Released
The verification of the Stable Release Update for python3-defaults 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 dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tools dhcpy6d|dhcpy6d dkimpy-milter|dkimpy-milter fenrir|fenrir galileo|galileo glances|glances graphite-carbon|graphite-carbon grokmirror|grokmirror guerillabackup|guerillabackup ionit|ionit jupyterhub|jupyterhub liquidctl|liquidctl localslackirc|localslackirc logdata-anomaly-miner|logdata-anomaly-miner lomiri|lomiri mailman3|mailman3 mailman3-full|mailman3 matrix-sydent|matrix-sydent mom|mom mopidy|mopidy mpd-sima|mpd-sima nordugrid-arc-arex|nordugrid-arc notus-scanner|notus-scanner nrpe-ng|nrpe-ng onionprobe|onionprobe openscap-daemon|openscap-daemon ospd-openvas|ospd-openvas pagekite|pagekite pagure|pagure pagure-ev-server|pagure pagure-milters|pagure pglistener|pglistener policyd-rate-limit|policyd-rate-limit postfix-mta-sts-resolver|postfix-mta-sts-resolver powa-collector|powa-collector prelude-correlator|prelude-corre
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted ubuntu-advantage-tools into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/33.2~24.04.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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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. ** Changed in: ubuntu-advantage-tools (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tool
[Touch-packages] [Bug 2060666] Update Released
The verification of the Stable Release Update for krb5 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 krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Released Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2060666] Re: [SRU] Memory leak in krb5 version 1.17
It passed now https://autopkgtest.ubuntu.com/packages/moonshot-gss- eap/focal/armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Committed Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2060666] Re: [SRU] Memory leak in krb5 version 1.17
https://autopkgtest.ubuntu.com/packages/postgresql-12/focal/s390x is green now, and https://autopkgtest.ubuntu.com/packages/moonshot-gss- eap/focal/armhf got another tmpfail. I retried that one one more time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Focal: Fix Committed Bug description: [ Impact ] Commit https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5 altered the memory management of krb5_gss_inquire_cred(), introducing defcred to act as an owner pointer when the function must acquire a default credential. The commit neglected to update the code to release the default cred along the successful path. The old code does not trigger because cred_handle is now reassigned, so the default credential is leaked. Resulting gradual increase in memory usage (memory leak) and eventual crash. [ Test Plan ] Setup 3 VMs: 1. Windows Server act as Domain controller (AD) 2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML utilities https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility) 3. SQL on Linux AD Joined ( configuration steps https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16) On the Machine with OStress create a file (name it disconnect.ini) with the following content under the same folder “C:\Program Files\Microsoft Corporation\RMLUtils” where OStress is installed. disconnect.ini == [Connection Options] LoginTimeout=30 QuotedIdentifier=Off AutocommitMode=On DisconnectPct=100.0 MaxThreadErrors=0 [Query Options] NoSQLBindCol=Off NoResultDisplay=Off PrepareExecute=Off ExecuteAsync=Off RollbackOnCancel=Off QueryTimeout=0 QueryDelay=0 MaxRetries=0 BatchDisconnectPct=0.0 CancelPct=0.00 CancelDelay=0 CancelDelayMin=0 CursorType= CursorConcurrency= RowFetchDelay=0 [Replay Options] Sequencing Options=global sequence ::Sequencing Options=global sequence, dtc replay DTC Timeout= DTC Machine=(local) Playback Coordinator=(local) StartSeqNum= StopSeqNum= TimeoutFactor=1.0 Run the following command to start the load using Ostress, change Server name (-S) accordingly and the number of threads (-n) as needed. Start 4 different CMD consoles and use the following different commands for each CMD window: 1. ostress.exe -E -S -Q"select * from sys.all_objects" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146 2. ostress.exe -E -S -Q"select * from sys.all_views" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146 3. ostress.exe -E -S -Q"select * from sys.all_columns" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146 4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q -cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146 After a run of about 5 hours, the memory usage for this is expected to be around 5G with the fix. Without the fix, it was observed that it reached around ~22G in 5 hours. Hence the increase in memory usage can be observed if the ostress.exe programs are let to run longer. [ Where problems could occur ] The fix may not fix the memory leak or could result in releasing the memory early in a different code path, and thus resulting in crashes. A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and they do not exhibit any issues. Likewise I've previously provided the fix in a PPA https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal to user who's been hit by this issue. They've tested and confirmed it fixes the memory leak. [ Other Info ] The commit https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 fixes the leak. The fix has been included in newer krb5 releases (Jammy, and Noble have the releases with the fix). Bionic doesn't have the commit the introduced the memory leak in the first place. So this will be a Focal-only backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2067240] Re: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS
Hi Atlas, thanks for your verification. Following the request in comment #12, though: > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the > package you tested, Could you please clarify the version of the package you tested? ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2067240 Title: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS Status in OEM Priority Project: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID information, and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo laptops. (lp: #2045276) [ Test Plan ] Under Jammy environment, with latest linux-oem kernel installed, check output of `mmcli -L` to see if the modems are properly recognized. Modems to check: - EM061K-GL - EM160 - EM160 [ Where problems could occur ] EM160R-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs EM061K-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs RM520N-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs All these changes are merged, and they only introduce new PIDs for initial supports, which do not affect existing ones. Noble contains these changes, so, only SRU jammy and mantic. [ Other Info ] These patches are proved work with the test version on my PPA: https://launchpad.net/~pseudoc/+archive/ubuntu/nate To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067240/+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 2036467] Update Released
The verification of the Stable Release Update for e2fsprogs 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 e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Committed Status in e2fsprogs source package in Jammy: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Released Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
The focal autopkgtests need work, lots of failed tests there: https://ubuntu-archive-team.ubuntu.com/proposed- migration/focal/update_excuses.html#e2fsprogs Looks like they all failed due to infrastructure problems (version="unknown" is the telltale). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Committed Status in e2fsprogs source package in Jammy: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Released Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2075337] Re: [SRU] py3clean fails when using alternate character set
Nice, is someone going to execute the test plan? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Committed Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Committed Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: New Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targetcli-fb ubiquity|ubiquity ubiquity-frontend-debconf|ubiquity ubiquity-frontend-gtk|ubiquity ubuntu-drivers-common|ubuntu-drivers-common ubuntu-pro-client|ubuntu-advantage-tools walinuxagent|walinuxagent noble restricted: noble universe: a2d|a2d apertium-apy|apertium-apy blueman|blueman borgmatic|borgmatic condor|condor cpupower-gui|cpupower-gui debomatic|debomatic dell-recovery|dell-recovery deluge-web|deluge depthcharge-tools|depthcharge-tools dhcpy6d|dhcpy6d dkimpy-milter|dkimpy-milter fenrir|fenrir galileo|galileo glances|glances graphite-carbon|graphite-carbon grokmirror|grokmirror guerillabackup|guerillabackup ionit|ionit jupyterhub|jupyterhub liquidctl|liquidctl localslackirc|localslackirc logdata-anomaly-miner|logdata-anomaly-miner lomiri|lomiri mailman3|mailman3 mailman3-full|mailman3 matrix-sydent|matrix-sydent mom|mom mopidy|mopidy mpd-sima|mpd-sima nordugrid-arc-arex|nordugrid-arc notus-scanner|notus-scanner nrpe-ng|nrpe-ng onionprobe|onionprobe openscap-daemon|openscap-daemon ospd-openvas|ospd-openvas pagekite|pagekite pagure|pagure pagure-ev-server|pagure pagure-milters|pagure pglistener|pglistener policyd-rate-limit|policyd-rate-limit postfix-mta-sts-resolver|postfix-mta-sts-resolver powa-collector|powa-collector prelude-correlator|prelude-correlator prometheus-pgbouncer-exporter|prometheus-pgbouncer-exporter prometheus-xmpp-alerts|prometheus-xmpp-alerts pyroman|pyroman python3-autopilot|autopilot python3-btchip|btchip-python python3-pyro5|pyro5 qweborf|weborf razercfg|razercfg sgt-launcher|sgt-launcher sms4you|sms4you supervisor|supervisor syncplay-server|syncplay timekpr-next|timekpr-next twms|twms ubiquity-frontend-kde|ubiquity vanguar
[Touch-packages] [Bug 2056768] Re: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/"
** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2056768 Title: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" Status in rsyslog package in Ubuntu: In Progress Status in rsyslog source package in Noble: Confirmed Bug description: There is an AppArmor regression in current noble. In cockpit we recently started to test on noble (to prevent the "major regressions after release" fiasco from 23.10 again). For some weird reason, rsyslog is installed *by default* [1] in the cloud images. That is a rather pointless waste of CPU and disk space, as it's an unnecessary running daemon and duplicates all the written logs. But more specifically, we noticed [2] an AppArmor rejection. Reproducer is simple: logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE this causes type=1400 audit(1710168739.345:108): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567 requested_mask="r" denied_mask="r" fsuid=102 ouid=0 Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does appear in the journal and also in /var/log/syslog. But it's some noise that triggers our (and presumbly other admin's) log detectors. rsyslog 8.2312.0-3ubuntu3 apparmor 4.0.0~alpha4-0ubuntu1 [1] https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest [2] https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768/+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 2056768] Re: apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/"
And once allowing reading the directory, the contents should also be
allowed:
[Sun Sep 1 16:00:46 2024] audit: type=1400 audit(1724157515.788:5238):
apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/2" pid=1873 comm=72733A6D61696E20513A526567
requested_mask="r" denied_mask="r" fsuid=102 ouid=0
So this is what I came up with:
--- a/debian/usr.sbin.rsyslogd
+++ b/debian/usr.sbin.rsyslogd
@@ -26,6 +26,11 @@ profile rsyslogd /usr/sbin/rsyslogd {
/etc/rsyslog.d/ r,
/etc/rsyslog.d/** r,
/{,var/}run/rsyslogd.pid{,.tmp} rwk,
+
+ # LP: #2056768
+ /{,var/}run/systemd/sessions/ r,
+ /{,var/}run/systemd/sessions/* r,
+
/var/spool/rsyslog/ r,
/var/spool/rsyslog/** rwk,
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2056768
Title:
apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/"
Status in rsyslog package in Ubuntu:
In Progress
Status in rsyslog source package in Noble:
Confirmed
Bug description:
There is an AppArmor regression in current noble. In cockpit we
recently started to test on noble (to prevent the "major regressions
after release" fiasco from 23.10 again).
For some weird reason, rsyslog is installed *by default* [1] in the
cloud images. That is a rather pointless waste of CPU and disk space,
as it's an unnecessary running daemon and duplicates all the written
logs.
But more specifically, we noticed [2] an AppArmor rejection.
Reproducer is simple:
logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE
this causes
type=1400 audit(1710168739.345:108): apparmor="DENIED"
operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567
requested_mask="r" denied_mask="r" fsuid=102 ouid=0
Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does
appear in the journal and also in /var/log/syslog. But it's some noise
that triggers our (and presumbly other admin's) log detectors.
rsyslog 8.2312.0-3ubuntu3
apparmor 4.0.0~alpha4-0ubuntu1
[1]
https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest
[2]
https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768/+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 2072574] Update Released
The verification of the Stable Release Update for ubuntu-settings 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 ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2072574 Title: Drop obsolete evolution-data-server notify-with-tray override Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Released Bug description: Impact -- Calendar notifications currently pop up a full app window instead of as a normal notification. The normal notifications respect the Do Not Disturb setting, but the full app window does not. Test Case 1 --- From Ubuntu Desktop… 1. Add your Google account to GNOME Settings > Online Accounts 2. Add a calendar event to Google Calendar with a notification in advance 3. When it is time for the notification, you should see a GNOME Shell notification. You can click on the notification to see the full Reminders window. Test Case 2 --- From Ubuntu Unity 24.04 LTS… 1. Open a terminal and run this command: sudo apt install gnome-online-accounts-gtk 2. Close the terminal 3. Add a calendar event to Google Calendar with a notification in advance 4. When it is time for the notification, you should see a notification pop-up. You can click OK on the notification to see the full Reminders window. What Could Go Wrong --- The ubuntu-settings package is shipped by default with Ubuntu Desktop, Ubuntu Unity, and Edubuntu. Edubuntu is practically the same as Ubuntu Desktop as far as the desktop experience goes with one additional GNOME Shell extension to sort the Show Apps view alphabetically. This is a small default change that can be easily changed (see Revert instructions below). I guess this could go bad if someone counts on getting event notifications even though they have turned on Do Not Disturb. I'm sorry but it is intended that Do Not Disturb not show notifications like this. Other Info -- I believe this override was originally added in 2011 for Unity's benefit LP: #757805 It was also helpful for GNOME in early GNOME 3 days with the unusual messaging tray that was later dropped. These days, GNOME Shell notifications work well, better than a separate popup window. Revert to Previous Behavior --- If you prefer the original Ubuntu 24.04 LTS behavior, do one of the following: 1. Run this in a terminal: gsettings set org.gnome.evolution-data-server.calendar notify-with-tray false 2. Or install Evolution. In ☰ > Edit > Preferences > Calendar and Tasks, turn on "Display Reminder window with notifications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2072574/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
I retried the remaining failing autopkgtests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Committed Status in e2fsprogs source package in Jammy: Fix Committed Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Committed Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2046486] Re: units with credentials fail in LXD containers
** Merge proposal unlinked: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/471168 -- 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/2046486 Title: units with credentials fail in LXD containers Status in cloud-images: Confirmed Status in lxd: New Status in lxd package in Ubuntu: Fix Committed Status in samba package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: Many units shipped by systemd use credentials in some way by default now (in v256). So this issue is now about much more than the original test case failure. For example, root@oracular:~# apt policy systemd systemd: Installed: 256-1ubuntu1 Candidate: 256-1ubuntu1 Version table: *** 256-1ubuntu1 100 100 http://archive.ubuntu.com/ubuntu oracular-proposed/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages root@oracular:~# for service in $(find /usr/lib/systemd/system -maxdepth 1 -name "systemd-*.service"); do grep -q "Credential.*=" "$service" && echo "$service"; done /usr/lib/systemd/system/systemd-sysusers.service /usr/lib/systemd/system/systemd-resolved.service /usr/lib/systemd/system/systemd-firstboot.service /usr/lib/systemd/system/systemd-network-generator.service /usr/lib/systemd/system/systemd-journald.service /usr/lib/systemd/system/systemd-sysctl.service /usr/lib/systemd/system/systemd-tmpfiles-setup-dev-early.service /usr/lib/systemd/system/systemd-tmpfiles-setup-dev.service /usr/lib/systemd/system/systemd-tmpfiles-setup.service /usr/lib/systemd/system/systemd-udev-load-credentials.service /usr/lib/systemd/system/systemd-tmpfiles-clean.service /usr/lib/systemd/system/systemd-networkd.service root@oracular:~# systemctl status systemd-sysusers.service systemd-resolved.service systemd-firstboot.service systemd-network-generator.service systemd-journald.service systemd-sysctl.service systemd-tmpfiles-setup-dev-early.service systemd-tmpfiles-setup-dev.service systemd-tmpfiles-setup.service systemd-udev-load-credentials.service systemd-tmpfiles-clean.service systemd-networkd.service ○ systemd-sysusers.service - Create System Users Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static) Active: inactive (dead) Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 1min 0s ago ├─ ConditionNeedsUpdate=|/etc was not met └─ ConditionCredential=|sysusers.extra was not met Docs: man:sysusers.d(5) man:systemd-sysusers.service(8) × systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:49 UTC; 59s ago Invocation: b1aaa662750f48868fe3388e4524c462 Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS https://systemd.io/WRITING_RESOLVER_CLIENTS Process: 258 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=243/CREDENTIALS) Main PID: 258 (code=exited, status=243/CREDENTIALS) ○ systemd-firstboot.service - First Boot Wizard Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static) Active: inactive (dead) Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 59s ago └─ ConditionFirstBoot=yes was not met Docs: man:systemd-firstboot(1) ○ systemd-network-generator.service - Generate network units from Kernel command line Loaded: loaded (/usr/lib/systemd/system/systemd-network-generator.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd-network-generator.service(8) × systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Drop-In: /usr/lib/systemd/system/systemd-journald.service.d └─nice.conf Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:48 UTC; 1min 0s ago Invocation: 7caace7a15c749f3a86fb15fcfb94dff TriggeredBy: × systemd-journald-dev-log.socket × systemd-journald.socket ○ systemd-journald-audit.socket Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 124 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=243/CREDENTIALS) Main PID: 124 (code=exited, status=243/CREDENTIALS) FD Store: 0 (limit: 4224) × systemd-sysctl.service - Apply Kernel Variables Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.
[Touch-packages] [Bug 1677863] Re: Missing dep8 tests
It migrated, closing bug. https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-8ubuntu1 ** Changed in: heimdal (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1677863 Title: Missing dep8 tests Status in heimdal package in Ubuntu: Fix Released Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source heimdal zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/heimdal status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3YANAAoJEIP8BxPaZgwlu24P/iJX01lyOO5vUdzYTOvjqNTF dGfAICBhOjkiHKMTa56e1VutrufBipgPZVdXAzou9fLb18SMBPH8SP5/iSk3GrCD 3IYIqY/+c+rQg/dVGWEpXOMpop8r+2d1IGarmy3PZuFvVJI34dskSkCBqW2OlHz+ unQ522qfDqfZ/8rq1xKspB/Vi7kbKV0uYenpgOhs5Vlb8nfWrHv1Zm+6lOnI42WJ r2+Hc1bb6snzKsYPgL6qigouHK4vsZjbWIugTaHalOQpm8R865Q8XSS+Skb2nGDp Ql2ULalPqERQRDOUtCpPaqZgB1iVlHApCRgH5baSh1a9WMraHoLlZLP/uRL6s4wC ThzeCGT2qJwSkESc/QE5iPtEx50+Kx8JVJgXxdjEArgVtHZERJ36U2FIzJE94uNG AiAOcvIjOTwHRqEQngPFtI+XskuKP2WeO5PbwgqgH51fi1LiNIovN1IALYZxsnhz 2qnorVpeJceVDXavgYiaWvPqiGh1EqXDIyqTdjT3r9cE+OjQMJV53SJk16wB6SyH 8E4GsWiazbSTvaAM5mWK7rFZh7vMcIDK8MpqVPxbgQrwV36DFXLyNVr/8eIvpO8G Gsk2UHxLdm4tPp7/Vkz9eBRhnP6fH6TTOpaKWPsn222m2LsnMS6gjXZMoIS4Pv0j KJoEHC3RRqOctkLd03Ck =mrOm -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1677863/+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 2074097] Re: DEP8 failing because of missing includedir support
It migrated, closing bug. https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-8ubuntu1 ** Changed in: heimdal (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of missing includedir support Status in heimdal package in Ubuntu: Fix Released Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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 1677863] Re: Missing dep8 tests
New tests passing. Just waiting for it to migrate, and then this bug can be marked as fix released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1677863 Title: Missing dep8 tests Status in heimdal package in Ubuntu: Fix Committed Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source heimdal zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/heimdal status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3YANAAoJEIP8BxPaZgwlu24P/iJX01lyOO5vUdzYTOvjqNTF dGfAICBhOjkiHKMTa56e1VutrufBipgPZVdXAzou9fLb18SMBPH8SP5/iSk3GrCD 3IYIqY/+c+rQg/dVGWEpXOMpop8r+2d1IGarmy3PZuFvVJI34dskSkCBqW2OlHz+ unQ522qfDqfZ/8rq1xKspB/Vi7kbKV0uYenpgOhs5Vlb8nfWrHv1Zm+6lOnI42WJ r2+Hc1bb6snzKsYPgL6qigouHK4vsZjbWIugTaHalOQpm8R865Q8XSS+Skb2nGDp Ql2ULalPqERQRDOUtCpPaqZgB1iVlHApCRgH5baSh1a9WMraHoLlZLP/uRL6s4wC ThzeCGT2qJwSkESc/QE5iPtEx50+Kx8JVJgXxdjEArgVtHZERJ36U2FIzJE94uNG AiAOcvIjOTwHRqEQngPFtI+XskuKP2WeO5PbwgqgH51fi1LiNIovN1IALYZxsnhz 2qnorVpeJceVDXavgYiaWvPqiGh1EqXDIyqTdjT3r9cE+OjQMJV53SJk16wB6SyH 8E4GsWiazbSTvaAM5mWK7rFZh7vMcIDK8MpqVPxbgQrwV36DFXLyNVr/8eIvpO8G Gsk2UHxLdm4tPp7/Vkz9eBRhnP6fH6TTOpaKWPsn222m2LsnMS6gjXZMoIS4Pv0j KJoEHC3RRqOctkLd03Ck =mrOm -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1677863/+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 2074097] Re: DEP8 failing because of missing includedir support
And the test is passing now. Marking as fix committed pending migration. ** Changed in: heimdal (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of missing includedir support Status in heimdal package in Ubuntu: Fix Committed Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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 2074097] Re: DEP8 failing because of missing includedir support
Fixed in https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-7ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2074097 Title: DEP8 failing because of missing includedir support Status in heimdal package in Ubuntu: Fix Committed Bug description: The new DEP8 test I added to heimdal is failing because of hostname issues: 117s autopkgtest [13:23:24]: test kinit: [--- 117s ## Adding includedir directive to /etc/krb5.conf 117s 117s ## Creating /etc/krb5.conf.d/autopkgtest.conf 117s 117s ## Stoping heimdal-kdc.service and cleaning up DB directory 117s 117s ## Stashing key 117s kstash: hdb_add_master_key: unable to find realm of host autopkgtest 117s autopkgtest [13:23:24]: test kinit: ---] 1. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/h/heimdal/20240725_132342_8fd69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2074097/+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
