Changes between Version 1 and Version 2 of Ticket #73283, comment 7
- Timestamp:
- May 20, 2026, 9:54:04 PM (3 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #73283, comment 7
v1 v2 1 just to echo my experience: I am on Sequioa as well *BUT* on Apple Silicon, and was experiencing the same exact issue. Something like `echo ${HOME%/*}` would cause bash to segfault. And less you think this is a "niche" issue.. even something as insidious and dare I say common scenario like `ls -l ~/Downloads/*pdf` would kill bash as well. That's just unacceptable.1 just to echo my experience: I am on Sequioa as well *BUT* on Apple Silicon, and was experiencing the same exact issue. Something like `echo ${HOME%/*}` would cause bash to segfault. And less you think this is a "niche" issue... even something as insidious and dare I say as common as `ls -l ~/Downloads/*pdf` would kill bash as well. This was how I first experienced the bug... which I could live with and get around using grep (even if suboptimal). But now I see that this issue is breaking scripts too, which is just unacceptable. 2 2 3 3 And just like everybody else, `sudo port -ns upgrade --force bash` fixed it for me. For anybody who's wondering, I did NOT have the option to activate an old version since I had done a reclaim already. I was already on the latest version of bash (`5.3.9_0`), but you can still do `sudo port -ns upgrade --force bash`.
