[Touch-packages] [Bug 2040019] [NEW] Bash environment gets corrupted
Public bug reported: bash 5.1-6ubuntu1 (jammy) After loading about 1000 aliases totaling 50kB Setting 200 vars totaling 20kB (half from default profile) And 1200 functions totaling 400kB (~100/72kB default completions) After running the occasional basic (but lengthy) scripts with no recursion, runtimes under 1 minute, all under 1 second CPU time in bash, 10-20 times a day for less than a month, bash starts losing functions and variables and aliases. Nothing in dmesg or syslog System is otherwise stable: -Memtest runs multiple passes ok -Several GB of apt updates all verify no errors -Checkrestart did not show any copies of bash needing restarts -no suspends, no remote shell -weekly apt updates run in this bash shell kernel 6.2.0-32 generic libc6 2.35-0ubuntu3.4 ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2040019 Title: Bash environment gets corrupted Status in bash package in Ubuntu: New Bug description: bash 5.1-6ubuntu1 (jammy) After loading about 1000 aliases totaling 50kB Setting 200 vars totaling 20kB (half from default profile) And 1200 functions totaling 400kB (~100/72kB default completions) After running the occasional basic (but lengthy) scripts with no recursion, runtimes under 1 minute, all under 1 second CPU time in bash, 10-20 times a day for less than a month, bash starts losing functions and variables and aliases. Nothing in dmesg or syslog System is otherwise stable: -Memtest runs multiple passes ok -Several GB of apt updates all verify no errors -Checkrestart did not show any copies of bash needing restarts -no suspends, no remote shell -weekly apt updates run in this bash shell kernel 6.2.0-32 generic libc6 2.35-0ubuntu3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2040019/+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 2038590] [NEW] Wget --rejected-log=file never logs anything
Public bug reported: Wget jammy 1.21.2-2ubuntu1 404 errors etc. are not written to log file File is never created. ** Affects: wget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/2038590 Title: Wget --rejected-log=file never logs anything Status in wget package in Ubuntu: New Bug description: Wget jammy 1.21.2-2ubuntu1 404 errors etc. are not written to log file File is never created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2038590/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
System time consistently falls behind, so hwclock -s is advancing the system clock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Expired Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
Hwclock -s is run on the system at least weekly as system time drifts. Adjtime is not installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Expired Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
With multiple bash scripts running for over a month, I now have random read fails at least once an hour PER SCRIPT. Restarting the script did not help. Restarting bash helps for a while. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Expired Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1817052] Re: bug with ls command, doesn't list only a single directory.
Did you mean ls -1? ls -l is long listing, does not start with filename, Example can't work as written -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1817052 Title: bug with ls command, doesn't list only a single directory. Status in bash package in Ubuntu: New Bug description: If is the only one which starts with an specified letter, won't show it with grep. Example: if there is only a directory starting with 'w', ls -l | grep ^[w] won't show it. With ls -l w* happens the same problem. I think you should check. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 12:37:04 2019 ExecutablePath: /bin/bash InstallationDate: Installed on 2019-01-13 (38 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANG=es_ES.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1817052/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
Also failing in Bash 5.0.6ubuntu1.2 In focal 20.04.5 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Expired Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
While date Do Read -t 60 x Done In another terminal, adjust the system clock by a few seconds Repeat hourly until the read hangs. Sometimes it hangs immediately after setting clock, Sometimes it runs for hours. I have seen hangs semi regularly for the last 5, maybe 10+ years. It often hangs with no apparent system clock changes, But more often when a cron job runs ntp No VM involved. Hangs on multiple AMD systems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Incomplete Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
Still fails randomly @ jammy bash 5.1-6ubuntu1 Read -t 60 failure can often be triggered by changing the system clock slightly. It often fails if waiting when ntp runs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Confirmed Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1988548] Re: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy
I manually installed the fixed zlib from kinetic. So far it is working. Could someone put it in proposed for focal and jammy so it will be on the livecd's? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1988548 Title: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy Status in zlib package in Ubuntu: Confirmed Bug description: There is a crictical security issue with zlib tracked here [1] The newest version in bionic [2] already has a security patch for it but the one in the focal [3] (and jammy) does not. As can be seen from their respective changelogs in the right hand side panel. Since zlib is loaded by lots of software, e.g. the apache weg server, this could be a problem. It seems that focal, jammy and bionic use the same base zlib version (1.2.11), so maybe the patch there could be recycled? I was asked to create a bug here after asking it as question here [4]. Thank you very much for your hard work! [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434 [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g [4] Original Question: https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1988548/+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 1806088] [NEW] disco livecd still has insecure version 15 days after 10.4 bugfix hit proposed
Public bug reported: This applies to disco only. Ref: symlink exploit fixed in 10.4 release Systemd restart is masked. Debian lists this update as high priority. Any easy get-root bug should be critical, not medium priority as listed in the usn. Updating while running the livecd is not securing anything. Please prioritize release of proposed security updates to disco, and all future current livecd versions. At least push out those updates that require substantial knowledge to activate (libc6, dbus, systemd, and their dependencies, etc ) and packages needed to do updates (apt, networkmanager, their dependencies, etc) Is there a way to override the mask and restart systemd? Can I use apparmor to prevent the symlink exploit? How? Should I file this elsewhere? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1806088 Title: disco livecd still has insecure version 15 days after 10.4 bugfix hit proposed Status in systemd package in Ubuntu: New Bug description: This applies to disco only. Ref: symlink exploit fixed in 10.4 release Systemd restart is masked. Debian lists this update as high priority. Any easy get-root bug should be critical, not medium priority as listed in the usn. Updating while running the livecd is not securing anything. Please prioritize release of proposed security updates to disco, and all future current livecd versions. At least push out those updates that require substantial knowledge to activate (libc6, dbus, systemd, and their dependencies, etc ) and packages needed to do updates (apt, networkmanager, their dependencies, etc) Is there a way to override the mask and restart systemd? Can I use apparmor to prevent the symlink exploit? How? Should I file this elsewhere? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806088/+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
