Thanks for the response. Good to hear it's fixed but I hope running valgrind can be made a requirement for EVERY component of Kubuntu! It was created by great engineers for a good reason. It MUST be used. I have told my teams for YEARS that no changes would be allowed in our code without it. And, BTW, it doesn't change the fact that 26.04 is a total nightmare. I'll likely wait until the official release to decide whether to go back to 24.04 because it's such a pain to roll back, but I don't have much hope, considering it's alpha quality at best. Turning off the screen resulting in plasma core-dumping? Really? No one could catch that? Insane...
Chris ([email protected] or chris.bertin@proton <[email protected]>.me) On Sat, Sep 12, 2026 at 12:20 PM Sylvestre Ledru <[email protected]> wrote: > it has been fixed here: https://github.com/uutils/coreutils/pull/11781 > > it is "ls -l" with xattr, so, not that common > > > ** Changed in: rust-coreutils (Ubuntu) > Status: New => Fix Committed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2167147 > > Title: > ls -l > > Status in rust-coreutils package in Ubuntu: > Fix Committed > > Bug description: > I have used Unix for 50 years, starting with V6/PWB, and I have used > Linux for 25+ years, different distros, RH or Suse at work, [k]ubuntu > at home, mostly. I never thought 'ls -l' could ever be broken but it > is on kubuntu 26.04, the worst Linux release ever (even though it's > not officially out). So many things broken, worst of all plasma, which > crashes any time the screen is turned off, is totally messed up when > it comes to window sizes and positions, etc... An abominable failure, > so far. But, to get back to 'ls', it looks like the MOST basic tool of > all, for ANYONE developing any software on Linux, is Valgrind! The > 'ls' bug is not a catastrophic failure, like the entire release as a > hole, but it's symptomatic. The space between the mode strings and the > link count sometimes is ridiculously large, for some reason. For some > other insane reason, /bin/ls is now a link to some fargo > implementation of many BASIC CRITICAL tools. Really? Whose idea was > that??? Anyway, running valgrind shows some OBVIOUS out-of-bound or > otherwise invalid memory reads! And, sometimes, the command actually > works, when run with valgrind, sometimes it DOESN'T even work at all! > Use AI if you can't find any competent basic developers! > > $ valgrind /bin/ls -la > > ==312498== Memcheck, a memory error detector > > ==312498== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et > al. > ==312498== Using Valgrind-3.26.0 and LibVEX; rerun with -h for copyright > info > ==312498== Command: /bin/ls -la > > ==312498== > > ==312498== Invalid read of size 1 > ==312498== at 0x532A166: strlen (vg_replace_strmem.c:506) > ==312498== by 0x41C323C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E2C6: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E215: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4318F5C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E203: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x551E600: (below main) (libc_start_call_main.h:59) > ==312498== Address 0x7ffe45d15fcd is not stack'd, malloc'd or > (recently) free'd > ==312498== > ==312498== Invalid read of size 1 > ==312498== at 0x532A174: strlen (vg_replace_strmem.c:506) > ==312498== by 0x41C323C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E2C6: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E215: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4318F5C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E203: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x551E600: (below main) (libc_start_call_main.h:59) > ==312498== Address 0x7ffe45d15fce is not stack'd, malloc'd or > (recently) free'd > ==312498== > ==312498== Invalid read of size 1 > ==312498== at 0x41C329D: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E2C6: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E215: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4318F5C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E203: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x551E600: (below main) (libc_start_call_main.h:59) > ==312498== Address 0x7ffe45d15ff6 is not stack'd, malloc'd or > (recently) free'd > ==312498== > ==312498== Invalid read of size 1 > ==312498== at 0x532E12D: bcmp (vg_replace_strmem.c:1234) > ==312498== by 0x410814F: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x41C3325: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E2C6: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E215: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4318F5C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E203: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x551E600: (below main) (libc_start_call_main.h:59) > ==312498== Address 0x7ffe45d15fcd is not stack'd, malloc'd or > (recently) free'd > ==312498== > ==312498== Invalid read of size 1 > ==312498== at 0x532EBB0: memmove (vg_replace_strmem.c:1415) > ==312498== by 0x432558F: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4335255: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4311950: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x425C268: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x41C335D: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E2C6: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E215: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4318F5C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E203: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x551E600: (below main) (libc_start_call_main.h:59) > ==312498== Address 0x7ffe45d15fcd is not stack'd, malloc'd or > (recently) free'd > ==312498== > ==312498== Invalid read of size 1 > ==312498== at 0x532EBBD: memmove (vg_replace_strmem.c:1415) > ==312498== by 0x432558F: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4335255: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4311950: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x425C268: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x41C335D: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E2C6: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E215: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x4318F5C: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x417E203: ??? (in /usr/lib/cargo/bin/coreutils/ls) > ==312498== by 0x551E600: (below main) (libc_start_call_main.h:59) > ==312498== Address 0x7ffe45d15fcf is not stack'd, malloc'd or > (recently) free'd > ==312498== > > > .../... > > When the command "works", it shows: > > $ /bin/ls -l > .../... > ox/Private/chrisb/bin > lrwxrwxrwx+ 1 chrisb chrisb 18 May 26 2018 cr > -> Dropbox/Private/cr > drwxr-xr-x 9 chrisb chrisb 4096 May 26 2018 crm > drwxr-xr-x 15 chrisb chrisb 4096 Jul 6 2018 devel > lrwxrwxrwx+ 1 chrisb chrisb 21 Sep 2 2024 dps > -> Dropbox/Private/share > lrwxrwxrwx+ 1 chrisb chrisb 26 May 28 2020 fun > -> Dropbox/Private/chrisb/fun > drwxr-xr-x+ 4 chrisb chrisb 4096 Sep 9 13:46 > glance > drwxr-xr-x 5 chrisb chrisb 4096 Apr 25 15:52 > howdy-env > lrwxrwxrwx+ 1 chrisb chrisb 27 Oct 13 2019 java > -> Dropbox/Private/chrisb/java > drwxr-xr-x 2 chrisb chrisb 4096 May 27 2018 lbin > lrwxrwxrwx+ 1 chrisb chrisb 26 May 29 2020 lib > -> Dropbox/Private/chrisb/lib > -rw------- 1 chrisb chrisb 21916 May 18 15:27 mbox > drwxr-xr-x 2 chrisb chrisb 4096 Dec 24 2023 mnt > drwxr-xr-x 2 chrisb chrisb 4096 May 16 2025 > pcloud > lrwxrwxrwx+ 1 chrisb chrisb 27 Oct 8 2019 pers > -> Dropbox/Private/chrisb/pers > drwxr-xr-x 2 chrisb chrisb 4096 Aug 23 20:03 > proton > lrwxrwxrwx+ 1 chrisb chrisb 34 Oct 11 2019 > public_html -> Dropbox/Private/chrisb/public_html > drwxr-xr-x 2 chrisb chrisb 4096 Apr 28 02:41 > quarantine > -rw-r--r-- 1 chrisb root 2223 Aug 23 18:38 > signal-desktop-keyring.gpg > -rw-r--r-- 1 chrisb root 167 Aug 23 18:39 > signal-desktop.sources > drwx------ 10 chrisb chrisb 4096 Nov 9 2025 snap > lrwxrwxrwx+ 1 chrisb chrisb 26 Oct 7 2019 src > -> Dropbox/Private/chrisb/src > drwxr-xr-x 8 chrisb chrisb 4096 Sep 11 09:07 tmp > lrwxrwxrwx+ 1 chrisb chrisb 27 Oct 7 2019 work > -> Dropbox/Private/chrisb/work > > > What are all these spaces for??? As I said, the MOST BASIC testing could > reveal this issue! > > As much of a nightmare it is to go back to 24.04, I am doing this soon > because it's clear that [k]ubuntu has lost its way! > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2167147/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167147 Title: ls -l To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2167147/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
