glibc update refusing to proceed. File ownership problem

Jindur · 2012-07-16 23:50:23

I don't really read news on the website everytime before I use pacman. And pacman messages looked pretty straightforward, making it look easy to solve, not like something you'd start browsing the web for. Actually I didn't expect pacman to be able to cause this much trouble just from forcing to install a package that did nothing bad except complaining that a folder is already in place which obviously should be in place, but now I know better.

Last edited by Jindur (2012-07-16 23:52:22)

jasonwryan · 2012-07-16 23:52:52

Merging with the stickied glibc thread...

Trilby · 2012-07-16 23:56:25

Jindur wrote:

I don't really read news on the website everytime before I use pacman.

Neither do I. I think the suggestion that one should be expected to do so is highly unrealistic. But, that said, if any error pops up, I'd think taking a peak at the news would be plain common sense.

Jindur wrote:

Actually I didn't expect pacman to be able to cause this much trouble just from forcing to install a package...

Erm ... Don't listen to Obi-wan, using the -force is almost always bad.

nomorewindows · 2012-07-17 00:08:23

Trilby wrote:

Erm ... Don't listen to Obi-wan, using the -force is almost always bad.

May the force be with you, but not when you're using the pacman package manager.
I think here, they'll have to use the LiveCD to get out of this one, Jedi Master.

Jindur · 2012-07-17 00:12:42

Is there any way to get a su shell on this system? Sudo/su commands don't work if I just enter them. I still have a midnight commander instance and some terminals open, is it somehow still possible to get root access in one of those in any way?

I just want to try to copy the /lib contents to /usr/lib and then removing /lib and symlinking it from /usr/lib.

Last edited by Jindur (2012-07-17 00:13:19)

cfr · 2012-07-17 00:14:35

Trilby wrote:

Jindur wrote:
I don't really read news on the website everytime before I use pacman.
Neither do I. I think the suggestion that one should be expected to do so is highly unrealistic. But, that said, if any error pops up, I'd think taking a peak at the news would be plain common sense.

Ditto. I also have pacmatic installed and aliased for root and me. (Doesn't work with sudo but I try to remember to substitute pacmatic in that case.) This is most useful if there's something it would be good to know before you start. It doesn't prevent the need for turning to the wiki/news/forums in case of trouble.

Jindur wrote:

Actually I didn't expect pacman to be able to cause this much trouble just from forcing to install a package...

It was not just "a package". It was *glibc*! If that doesn't mean anything to you, it should.

Trilby · 2012-07-17 00:17:47

Jindur, I see you think pacman is to blame and would prefer something more like aptitude. It always seemed essentially unanimous that pacman was the biggest strength of archlinux. Given that, and the fact that the package management system is (to my knowledge) one of the main things that differentiates distros, why do you use arch at all? If you want archlinux - pacman + aptitude ... isn't that just called debian?

Last edited by Trilby (2012-07-17 00:18:09)

Jindur · 2012-07-17 00:26:20

Trilby wrote:

Jindur, I see you think pacman is to blame and would prefer something more like aptitude. It always seemed essentially unanimous that pacman was the biggest strength of archlinux. Given that, and the fact that the package management system is (to my knowledge) one of the main things that differentiates distros, why do you use arch at all? If you want archlinux - pacman + aptitude ... isn't that just called debian?

I don't know what that would be, and I don't know about whether pacman differentiates or not, I just like my system and I would like it even more if the package manager wouldn't fail this often/badly. If someone says ok let's use a package manager that just works (tm) it'd seem to me the system just got improved further. If you say "it isn't the package manager's fault" then I'll believe you though. I don't know that much about package managers, I can only tell you that my experience so far has been that aptitude always works and pacman for system upgrades often "doesn't" in the sense of not requiring the user to fix/hack stuff. But maybe it wasn't pacman's fault but just everytime some revolutionary change in the architecture that absolutely made manual fixing necessary.

Last edited by Jindur (2012-07-17 00:28:12)

jasonwryan · 2012-07-17 00:27:45

Jindur wrote:

I would like it even more if I wouldn't fail this often/badly

Fixed that for you...

Pacman does what you tell it to. That's the whole point of Arch: being responsible for your system.

Jindur · 2012-07-17 00:28:49

asshole wrote:

Jindur wrote:
I would like it even more if I wouldn't fail this often/badly
Fixed that for you...

Fixed it too.

jasonwryan · 2012-07-17 00:30:29

Jindur wrote:

asshole wrote:
Jindur wrote:
I would like it even more if I wouldn't fail this often/badly
Fixed that for you...
Fixed it too.

A ban isn't going to help you get your system fixed: you might want to rethink your approach...
https://wiki.archlinux.org/index.php/Fo … ther_Users
https://wiki.archlinux.org/index.php/Fo … _The_Staff

Jindur · 2012-07-17 00:32:01

jasonwryan wrote:

A ban isn't going to help you get your system fixed: you might want to rethink your approach...
https://wiki.archlinux.org/index.php/Fo … ther_Users
https://wiki.archlinux.org/index.php/Fo … _The_Staff

I'm sorry, I only returned the ball. So how about we both rethink our approaches? I don't like this either, you know.
Also, the only reason I'm writing a lot of stuff here is obviously that I like my system, otherwise I'd just ignore it and go somewhere else. So I don't mean to do any harm.

Last edited by Jindur (2012-07-17 00:33:44)

jasonwryan · 2012-07-17 00:34:51

Jindur wrote:

jasonwryan wrote:
A ban isn't going to help you get your system fixed: you might want to rethink your approach...
https://wiki.archlinux.org/index.php/Fo … ther_Users
https://wiki.archlinux.org/index.php/Fo … _The_Staff
I'm sorry, I only returned the ball. So how about we both rethink our approaches? I don't like this either, you know.

The difference is I wasn't insulting you: I was pointing out that blaming your tools is disrespectful to the people who create them.

I accept your apology, but you might want to reflect on the fact that everything about your system has been built by volunteers and the help you are seeking now is provided by the same...

Jindur · 2012-07-17 00:42:57

Yes I know about that, it's the same reason why I try to post stuff here whenever I collect some experience on the platform, in order to share it. I'm just annoyed that after the last time I used pacman -Syu and had to find out and fix some stuff manually, now right again something nasty happens. I wish it'd just work (tm), but I guess it was just bad luck and timing, well and I didn't read the news. And maybe pacman could just fix the /lib folder on the fly (it's probably relatively easy if you know what to do?) instead of risking people bricking their systems. But I'll certainly keep reading news from now on.

Last edited by Jindur (2012-07-17 00:44:08)

Trilby · 2012-07-17 00:49:32

Whoa,

Jindur, I can see why you might have felt a bit insulted, though it wasn't a groundless attack, rather just holding you to the responsibility that is expected of archers to maintain their system. To follow up on your point on if I think your problem is pacman's fault, I do not. I had no problems with recent updates at all, neither did many other users.

From recent activity on the forums, one might argue that many users have had problems with the glibc /lib/ change, or the previous filesystem,mtab,etc changes - but in a majority of those cases do seem to be from a failure to read the news or to execute the instructions therein properly.

That is no insult to those with the problems: I'm the king of screwing up simple instructions - but when I do so I (reluctantly) accept that I botched it up or failed to get the information I should have. When running archlinux there is an expectation that you will keep up with the news and continue learning. This is made clear in all the documentation.

If that's what you want, take a "mulligan" and keep on going. If it's now what you want, don't expect pacman, or the arch community, to change to suit your tastes.

Jindur · 2012-07-17 01:27:48

Reading the news is no problem once you know when you better read them (before updating your system), so I'll be better prepared from now on.

About changing pacman, what the community is for or against is probably not determined by fixed rules but can change depending on what actually happens. I'm an arch user too after all, saying that in my particular opinion it'd be nice if pacman just fixed the /lib folder on the fly (after asking the user). So if someone asks you if the arch community has an opinion regarding a possible pacman modification for this particular issue you can tell him "part of it has".

Btw any idea how to get a root shell now if that's even possible anymore? I've got firefox, terminals, thunars and mc open, to try stuff. No sshd. Just typing 'su' or 'sudo' results in the usual command not found error.

jasonwryan · 2012-07-17 01:32:36

Jindur wrote:

Btw any idea how to get a root shell now if that's even possible anymore? I've got firefox, terminals, thunars and mc open, to try stuff. No sshd. Just typing 'su' or 'sudo' results in the usual command not found error.

There are a couple of good suggestions here: https://bbs.archlinux.org/viewtopic.php?pid=1130458

Jindur · 2012-07-17 01:49:31

Thanks, those seem to be for when you still have a root shell open or when you reboot anyway.
I was thinking of getting a root shell without rebooting, then trying to fix the /lib folder.
However, I cannot run 'su' or 'sudo' or anything. My only idea atm is, I still have midnight commander open which has a hex editor and can set file permissions. Anyone know of an x86 machine code sequence I could put into a new file, mark it executable, and it attains root access via some buffer overflow or something? :-p or is that too far fetched..

I'll take other suggestions too.

Last edited by Jindur (2012-07-17 01:50:00)

jasonwryan · 2012-07-17 01:53:06

Can't you just use the same approach that progandy recommended for nautilus, using mc?

Jindur · 2012-07-17 02:01:04

He still had a root shell running in that approach, from which he was able to call busybox. I don't have any open root shells, only user shells.
I actually downloaded busybox too and set it executable in mc, but it's no help since it isn't root.

jasonwryan · 2012-07-17 02:08:24

OK: it looks like plan B: reboot and append the linked bash line to your bootloader entry...

snoxu · 2012-07-17 03:09:21

Hey guys just biked in to say most painful update ever! Had me going mad for the last 2 days.

I

pacman -Syu --ignore glibc

but got nothing from

pacman -Su

I rebooted and managed to bork my system and couldn't run a DE and no network. Then I further borked my system beyond use by installing a kernel from cache. Rebooted and got the dreaded

Unable to find root device

Systemrescued my system but

find /lib -exec pacman -Qo -- {} +

yielded and endless number of pages of bullshit. Maybe crap from installing a kernel from cache.

I got impatient and went for the quick and dirty amsri method on page 5 and got my system working again.

amsri on page 5 you're the man!

I wonder if there's is any cleanup I should do?

Last edited by snoxu (2012-07-17 03:11:47)

geekinthesticks · 2012-07-17 07:43:28

I have worked my way through the Wiki to the point where I do:

grep '^lib/' /var/lib/pacman/local/*/files

the output from this is:

var/lib/pacman/local/gcc-4.7.0-6/files:lib/
/var/lib/pacman/local/gcc-4.7.0-6/files:lib/cpp
/var/lib/pacman/local/glibc-2.15-11/files:lib/
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-linux-x86-64.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil.so.1

The wiki suggests removing packages shown by this command. However, all these look as they are part of gcc, which the upgrade itself is supposed to deal with. I have done several rounds of:

pacman -Syu --ignore glibc
pacman -Su

So how to proceed from here?

swanson · 2012-07-17 07:47:44

Uninstall gcc , gcc-objc and possibly libtool. Upgrade glibc and then reinstall them. Worked really well on my netbook just now.

geekinthesticks · 2012-07-17 08:01:51

swanson wrote:

Uninstall gcc , gcc-objc and possibly libtool. Upgrade glibc and then reinstall them. Worked really well on my netbook just now.

Thank you, that worked perfectly.

Arch Linux

#126 2012-07-16 23:50:23

Re: glibc update refusing to proceed. File ownership problem

#127 2012-07-16 23:52:52

Re: glibc update refusing to proceed. File ownership problem

#128 2012-07-16 23:56:25

Re: glibc update refusing to proceed. File ownership problem

#129 2012-07-17 00:08:23

Re: glibc update refusing to proceed. File ownership problem

#130 2012-07-17 00:12:42

Re: glibc update refusing to proceed. File ownership problem

#131 2012-07-17 00:14:35

Re: glibc update refusing to proceed. File ownership problem

#132 2012-07-17 00:17:47

Re: glibc update refusing to proceed. File ownership problem

#133 2012-07-17 00:26:20

Re: glibc update refusing to proceed. File ownership problem

#134 2012-07-17 00:27:45

Re: glibc update refusing to proceed. File ownership problem

#135 2012-07-17 00:28:49

Re: glibc update refusing to proceed. File ownership problem

#136 2012-07-17 00:30:29

Re: glibc update refusing to proceed. File ownership problem

#137 2012-07-17 00:32:01

Re: glibc update refusing to proceed. File ownership problem

#138 2012-07-17 00:34:51

Re: glibc update refusing to proceed. File ownership problem

#139 2012-07-17 00:42:57

Re: glibc update refusing to proceed. File ownership problem

#140 2012-07-17 00:49:32

Re: glibc update refusing to proceed. File ownership problem

#141 2012-07-17 01:27:48

Re: glibc update refusing to proceed. File ownership problem

#142 2012-07-17 01:32:36

Re: glibc update refusing to proceed. File ownership problem

#143 2012-07-17 01:49:31

Re: glibc update refusing to proceed. File ownership problem

#144 2012-07-17 01:53:06

Re: glibc update refusing to proceed. File ownership problem

#145 2012-07-17 02:01:04

Re: glibc update refusing to proceed. File ownership problem

#146 2012-07-17 02:08:24

Re: glibc update refusing to proceed. File ownership problem

#147 2012-07-17 03:09:21

Re: glibc update refusing to proceed. File ownership problem

#148 2012-07-17 07:43:28

Re: glibc update refusing to proceed. File ownership problem

#149 2012-07-17 07:47:44

Re: glibc update refusing to proceed. File ownership problem

#150 2012-07-17 08:01:51

Re: glibc update refusing to proceed. File ownership problem

Board footer