bash issues with 4.2.005

Allan · 2011-03-01 11:12:53

As I pointed out, the OPs issue is not bash from [testing] given that bash package was not built when his issues started.... so start a new thread about the bash issue if necessary.

Edit: split into a new thread...

insanemal · 2011-03-01 12:02:20

i just remounted / in rw using
mount -n -o remount,rw /
then did a pacman -U
i did do more testing also
it seems the include of /etc/rc.d/functions is what causes the seg fault
i did a bash -x on it and it didnt even start executing
just got 10 or so lines into that after pulling in the rc.conf
hope this helps
also Alan is right these are unrelated i have started a thread in testing

broken pipe · 2011-03-01 13:15:30

ngoonee wrote:

Allan wrote:
4.2.005 was put in the repos 24 hours after the original post here... so there is probably two separate issues.
ML seems to indicate that bash or readline are causing non-bootable systems too, though. Possibly the OP simply didn't reboot immediately?
I've updated bash/readline but haven't rebooted yet....

it's caused by bash 4.2.005-1 i recently downgraded it because the system became unbootable.
after booting i got this error:"bash - cannot find /usr/bin/tty" and the system prompts to the login console

gimpel · 2011-03-01 14:07:23

Same problem for me on x86_64 / testing:

bash pkg version: 4.2.005-1-x86_64

segmentation faults on boot in rc.sysinit
hence / was mounted ro
...and a lot of aftereffects e.g. hostname unset, locale / keyboard layout not set up, "$ mount" not showing correct results...
runlevel 1 (default runlevel for my grub fallback kernel bootline) wasn't working at all

solution:
# remount -o remount,rw /dev/sda1
# pacman -U /var/cache/pacman/pkg/bash-4.2-1-x86_64.pkg.tar.xz
# reboot

now everything seems to work again

Last edited by gimpel (2011-03-01 14:26:46)

zyghom · 2011-03-01 14:44:51

true - bash from testing caused the problem ;-(

Allan · 2011-03-01 14:45:09

Again... the bash issue is separate to the issue the original poster has...

karabaja4 · 2011-03-01 20:23:09

So... I had a problem with recent bash update (segmentation fault during sysinit) which I had to solve by booting to live cd (because keyboard wouldn't work after booting to read-only), then mounting root to folder, and doing pacman -U <old_bash_package_from_root_folder_cache> --root <mounted_root_folder>

Maybe this would be nice as a news on main site for people that updated to latest bash this morning...

karol · 2011-03-01 20:26:02

karabaja4 wrote:

So... I had a problem with recent bash update (segmentation fault during sysinit) which I had to solve by booting to live cd (because keyboard wouldn't work after booting to read-only), then mounting root to folder, and doing pacman -U <old_bash_package_from_root_folder_cache> --root <mounted_root_folder>
Maybe this would be nice as a news on main site for people that updated to latest bash this morning...

Are you talking about a package from [testing]? People running [testing] should know damn well how to deal with breakage and should be subscribed to Arch MLs.

Last edited by karol (2011-03-01 20:27:58)

loafer · 2011-03-01 21:02:34

karol wrote:

karabaja4 wrote:
So... I had a problem with recent bash update (segmentation fault during sysinit) which I had to solve by booting to live cd (because keyboard wouldn't work after booting to read-only), then mounting root to folder, and doing pacman -U <old_bash_package_from_root_folder_cache> --root <mounted_root_folder>
Maybe this would be nice as a news on main site for people that updated to latest bash this morning...
Are you talking about a package from [testing]? People running [testing] should know damn well how to deal with breakage and should be subscribed to Arch MLs.

Fair enough. But as Allan points out this is the wrong thread for all this. Also, those of us who updated earlier today did so before it got on the ML. That's why it was discussed on the forums.

Inxsible · 2011-03-01 21:35:02

Thread split and moved to testing. Allan mentioned thrice that the bash in testing has nothing to do with the op's problem. Please do not hijack threads. Start your own in the appropriate forum if you see an issue.

Sean-Der · 2011-03-02 00:02:45

Probably does not help but I would like to confirm this bug on x64

nikor · 2011-03-02 06:43:18

The problem is that bash segfaults on "unset TZ" in /etc/rc.d/functions.

Allan · 2011-03-02 06:52:55

bash-4.2.004-1 has been in [testing] for a while now... use that.

hbekel · 2011-03-02 07:35:44

Seems to be solved with bash-4.2.006, boots fine and unset TZ works.

http://ftp.gnu.org/gnu/bash/bash-4.2-patches/bash42-006

Flylow · 2011-03-02 21:21:20

Tried to downgrade but have trouble doing so:

Screen_Shot

Remounted fs writeable using mount -n -o remount,rw /
Changed into pkg cache and searched earlier bash version
tried to downgrade using the command which you see on the bottom of the screen

What am I doing wrong?

loafer · 2011-03-02 21:30:25

Try logging in as root rather than a non privileged user.

Then mount.

Then install from the cache.

Flylow · 2011-03-02 21:48:30

Tried it quickly. The only thing that changes is, that now there stands "killed" below note: pacman......

jdarnold · 2011-03-02 22:27:55

I installed a version of bash (I believe it was bash-4.2.005-1-x86_64) yesterday that broke things horribly. Bash was segfaulting, so parsing the rc.conf wasn't even working. I downgraded to bash-4.2-1-x86_64.pkg.tar.xz and all was better. Of course, the version numbers have me confused, but pacman -Qu tells methat bash-4.2-1 needs upgrading, so I guess that means bash-4.2-1 is an older version than 4.2.00501.

I believe I did this after the boot failed, leavin me at a TTY prompt.

# mount -o remount,rw /dev/sda3
# cd /var/cache/pacman/pkg
# pacman -U bash-4.2-1-x86_64.pkg.tar.xz

Last edited by jdarnold (2011-03-02 22:30:30)

Flylow · 2011-03-03 07:43:23

Still have the same problem. Tried 4.2-1 too -> no change. Another thing is, that when I get the message on the screenshot, the laptop hangs up if I run the command again.

Cadynum · 2011-03-03 17:25:18

If anything this though me to include usbinput in mkinitcpio HOOKS.

Flylow · 2011-03-05 09:58:43

Finally solved my problem.

Boot from Live-USB
fsck -f /dev/sda1
mkdir /mnt/arch
mount /dev/sda1 /mnt/arch
chroot /mnt/arch
cd /var/cache/pacman/pkg
pacman -U bash.....

Arch Linux

#1 2011-03-01 11:12:53

bash issues with 4.2.005

#2 2011-03-01 12:02:20

Re: bash issues with 4.2.005

#3 2011-03-01 13:15:30

Re: bash issues with 4.2.005

#4 2011-03-01 14:07:23

Re: bash issues with 4.2.005

#5 2011-03-01 14:44:51

Re: bash issues with 4.2.005

#6 2011-03-01 14:45:09

Re: bash issues with 4.2.005

#7 2011-03-01 20:23:09

Re: bash issues with 4.2.005

#8 2011-03-01 20:26:02

Re: bash issues with 4.2.005

#9 2011-03-01 21:02:34

Re: bash issues with 4.2.005

#10 2011-03-01 21:35:02

Re: bash issues with 4.2.005

#11 2011-03-02 00:02:45

Re: bash issues with 4.2.005

#12 2011-03-02 06:43:18

Re: bash issues with 4.2.005

#13 2011-03-02 06:52:55

Re: bash issues with 4.2.005

#14 2011-03-02 07:35:44

Re: bash issues with 4.2.005

#15 2011-03-02 21:21:20

Re: bash issues with 4.2.005

#16 2011-03-02 21:30:25

Re: bash issues with 4.2.005

#17 2011-03-02 21:48:30

Re: bash issues with 4.2.005

#18 2011-03-02 22:27:55

Re: bash issues with 4.2.005

#19 2011-03-03 07:43:23

Re: bash issues with 4.2.005

#20 2011-03-03 17:25:18

Re: bash issues with 4.2.005

#21 2011-03-05 09:58:43

Re: bash issues with 4.2.005

Board footer