Cannot log in after upgrade

pepedopolous · 2012-02-12 17:59:43

Hi I'm a newbie to Arch but used Ubuntu for many years. It appears that I've got a borked upgrade so if anyone can suggest how to solve this I would be most grateful!

I installed hunspell.en for use with libreoffice. For some reason appset-qt upgraded some other packages too

After closing libreoffice, it wouldn't start again.

I then found that I couldn't log in, even after a reboot. kdm crashed then leaving me at the slim login screen. Using slim, openbox failed to start too.

So I then tried using the maintenance mode. I tried the commands startx, kdm, xinit, all started but then failed.

I tried to start NetworkManager and do a system upgrade but NetworkManager also crashed.

The one persistent error message seems to be this: -

error while loading shared library libpcre.so.1 cannot open shared object

So I guess without a network connection I need to download a working version of the package which provides libpcre.so.1.

So, is this the right course of action? Many thanks, p.

karol · 2012-02-12 18:05:15

There was a pcre rebuild recently and it seems something went wrong on your system. Is the console working for the regular user? You don't need X to try to fix this.

I'm not sure if you only need to update pcre or some other packages too.

pepedopolous · 2012-02-12 18:24:29

Hi,

Thanks for the reply.

I've just downloaded and installed the last version of pcre (used my Ubuntu partition ;-) ) and I'm able to log-in again. Not sure if everything is right yet but fingers crossed

Many thanks,

P

n0stradamus · 2012-02-12 18:35:35

As karol said, you don't need X to fix the problem.
If you are confident enough with the commandline, you can try the following steps:

At system startup select the Arch Linux entry in Grub and press 'e'. Append a '1' to the kernel commandline (the line with '/vmlinuz'-stuff)
Your system will start up in single-user mode and ask you for the root password. Enter it and start up your network:
```
# rc.d start network
```
If you don't use the network scripts you'll need to start the network manager of your choice of course.
Having done that, start a system upgrade, reinstalling pcre in the process
```
# pacman -Syyu pcre
```
Wait for the update to complete and log out of the single-user mode. Your system will start up as it normally would and hopefully be usable again

Hopefully that fixes it!

EDIT: Looks like someone was faster

Last edited by n0stradamus (2012-02-12 18:36:07)

pepedopolous · 2012-02-12 18:43:22

Hi,

Thanks again. I did try to start NetworkManager but the problem is that it threw up the same error message (i'm ok with the command line but i'm used to using NM). I'm loving Arch but I'm learning quick that upgrades are dangerous!

senft · 2012-02-13 08:33:24

Reinstalling pcre (or lib32-pcre) didn't do the trick for me. I had to do a

ln -s /usr/lib/libpcre.so.1 /usr/lib/libpcre.so.0

karol · 2012-02-13 09:36:52

senft wrote:

Reinstalling pcre (or lib32-pcre) didn't do the trick for me. I had to do a
ln -s /usr/lib/libpcre.so.1 /usr/lib/libpcre.so.0

Why? Which packages required such move?

senft · 2012-02-13 10:56:35

Not sure if it was X itself or i3 (i3-git).

phunni · 2012-02-13 10:57:32

I have had a similar problem - in that I couldn't start Eterm because libpcre.so.1 wasn't found. Creating the link described above fixed the problem.

karol · 2012-02-13 11:13:43

You should rebuild i3-git for the new pcre library. symlinking is not advisable and shouldn't be necessary.

mr_comic · 2012-02-13 13:32:45

I came with the same solution, the symlinking, but I want to know which would be the best solution? I couldn't use any X app because of that error.

Mr.Elendig · 2012-02-13 13:51:31

Symlinking is _never_ the real solution. Updating/rebuilding the app/lib that links against the old .so is.
Or if you have an app/lib linking against the new .so, while you have the old one installed, then update the lib providing the .so.

Short story: partial updates are bad, don't do them.

Last edited by Mr.Elendig (2012-02-13 13:55:22)

jono · 2012-02-13 19:11:18

I can confirm I have the same problem. Both on my desktop and in a virtual machine. I made the symlink as a workaround. I would rather not do this but many apps depend on it.

Mr.Elendig · 2012-02-14 00:43:47

post output of pacman -Qs glib2

mr_comic · 2012-02-14 03:58:46

So glib IS the problem? Wow... I'm using the custom glib2 from Unity by chenxiaolong.

Mr.Elendig · 2012-02-14 06:40:01

You have to rebuild it against the new pcre. When you use non-official packages you have to keep track of them and rebuild when libs they link against gets updated.

jono · 2012-02-14 15:08:18

Mr.Elendig wrote:

post output of pacman -Qs glib2

$ pacman -Qs glib2
local/glib2 2.31.0-1
Common C routines used by GTK+ and other libs

then I did

$ pacman -S glib2
and it installed glib2 2.30

Realized I had upgraded glib2 and gtk3 to development branches a while back. So I just reinstalled those two and removed my symlink. Things are now working as they should. Thanks.

Arch Linux

#1 2012-02-12 17:59:43

Cannot log in after upgrade

#2 2012-02-12 18:05:15

Re: Cannot log in after upgrade

#3 2012-02-12 18:24:29

Re: Cannot log in after upgrade

#4 2012-02-12 18:35:35

Re: Cannot log in after upgrade

#5 2012-02-12 18:43:22

Re: Cannot log in after upgrade

#6 2012-02-13 08:33:24

Re: Cannot log in after upgrade

#7 2012-02-13 09:36:52

Re: Cannot log in after upgrade

#8 2012-02-13 10:56:35

Re: Cannot log in after upgrade

#9 2012-02-13 10:57:32

Re: Cannot log in after upgrade

#10 2012-02-13 11:13:43

Re: Cannot log in after upgrade

#11 2012-02-13 13:32:45

Re: Cannot log in after upgrade

#12 2012-02-13 13:51:31

Re: Cannot log in after upgrade

#13 2012-02-13 19:11:18

Re: Cannot log in after upgrade

#14 2012-02-14 00:43:47

Re: Cannot log in after upgrade

#15 2012-02-14 03:58:46

Re: Cannot log in after upgrade

#16 2012-02-14 06:40:01

Re: Cannot log in after upgrade

#17 2012-02-14 15:08:18

Re: Cannot log in after upgrade

Board footer