Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
WARNING: prelink and glibc-2.13 update
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
Naib
Advocate
Advocate


Joined: 21 May 2004
Posts: 4076
Location: Removed by Neddy

PostPosted: Tue Feb 08, 2011 1:14 am    Post subject: Reply with quote

WOW I am so glad I removed prelink last month... was causing issues with 64bit 3D applications. prelink would be linking in the 32bit libs from nvidia...
_________________
A free press is the unsleeping guardian of every other right that free men prize; it is the most dangerous foe of tyranny. Where men have the habit of liberty, the Press will continue to be the vigilant guardian of the rights of the ordinary citizen.
Back to top
View user's profile Send private message
HolgerH
n00b
n00b


Joined: 02 Mar 2008
Posts: 16

PostPosted: Tue Feb 08, 2011 1:20 am    Post subject: Reply with quote

SoLoR wrote:
glibc-2.13 also breaks postfix for me...
..
reverting glibc back to 2.12.2 and problem is gone.


Same here. May I ask how you downgraded? I read the various guides and just like the ebuild safety-check they all contain unhelpful panic warnings without actually saying what the problems are.
I haven't emerged anything since glibc, so is it just a matter of editing the 2.12.2 ebuild to disable the check, updating the manifest & emerging?

thanks.
Back to top
View user's profile Send private message
rhill
Developer
Developer


Joined: 22 Oct 2004
Posts: 1629
Location: sk.ca

PostPosted: Tue Feb 08, 2011 5:54 am    Post subject: Reply with quote

you can run
Code:
ROOT="/../" emerge -av1 =glibc-2.12.2

to get around the downgrade check.
_________________
by design, by neglect
for a fact or just for effect
Back to top
View user's profile Send private message
vdracula
n00b
n00b


Joined: 03 Aug 2004
Posts: 51
Location: NGC 5907

PostPosted: Tue Feb 08, 2011 6:00 am    Post subject: Reply with quote

After restoring my system back to normal, did a prelink -au.

Since then, everything o.k. here. No problems at all.

One have to be carefull with all kind of optimizations...
Back to top
View user's profile Send private message
yoshi314
l33t
l33t


Joined: 30 Dec 2004
Posts: 817
Location: PL

PostPosted: Tue Feb 08, 2011 7:08 am    Post subject: Reply with quote

NightMonkey wrote:
Welcome to unstable, everyone. :)
it's well beyond unstable, in that case.

i can understand an apps failing on unstable, but the whole system ? that stuff belongs to hard masked packages.

whoever is responsible for that critical system component really messed up.
_________________
~amd64, ~x86
shrink your /usr/portage with squashfs+aufs
Back to top
View user's profile Send private message
HolgerH
n00b
n00b


Joined: 02 Mar 2008
Posts: 16

PostPosted: Tue Feb 08, 2011 10:01 am    Post subject: Reply with quote

dirtyepic wrote:
you can run
Code:
ROOT="/../" emerge -av1 =glibc-2.12.2

to get around the downgrade check.


Nope, didn't work for me. Could be me using zsh though. Anyway just editing the ebuild and rebuilding worked fine, postfix is back up & running.
Back to top
View user's profile Send private message
FireBurn
Apprentice
Apprentice


Joined: 19 Sep 2004
Posts: 165
Location: Edinburgh, UK

PostPosted: Tue Feb 08, 2011 11:31 am    Post subject: Reply with quote

yoshi314 wrote:
NightMonkey wrote:
Welcome to unstable, everyone. :)
it's well beyond unstable, in that case.

i can understand an apps failing on unstable, but the whole system ? that stuff belongs to hard masked packages.

whoever is responsible for that critical system component really messed up.


Considering I gave a heads up to the committer within hours of the ebuild going live I'm angry at the length of time to took for something to be done

I got an email back with in an hour telling me that email wasn't the way to communicate bugs
Back to top
View user's profile Send private message
Xenoist
n00b
n00b


Joined: 21 Aug 2002
Posts: 23
Location: EU/DE/NRW/NEUSS

PostPosted: Tue Feb 08, 2011 3:55 pm    Post subject: to go back to glibc-2.12.2 use this Reply with quote

Sanity check is in /usr/portage/sys-libs/glibc/files/eblits/pkg_setup.eblit

So set # like here:

# eerror "Sanity check to keep you from breaking your system:"
# eerror " Downgrading glibc is not supported and a sure way to destruction"
# die "aborting to save your system"

ebuild /usr/portage/sys-libs/glibc/sys-libs/glibc-2.12.2.ebuild digest

echo "=sys-libs/glibc-2.13*" >> /etc/portage/package.mask

emerge -av1 =sys-libs/glibc-2.12.2

But i think that will be a bad option.

I will try it with complete rebuild on a 64bit environment in chroot.

Don't forget to enable the check again in /usr/portage/sys-libs/glibc/files/eblits/pkg_setup.eblit and do a ebuild /usr/portage/sys-libs/glibc/sys-libs/glibc-2.12.2.ebuild digest.
_________________
Once live is to short to learn all, but keep trying it.

"emerge the world" every day!

Linux Registered User #413022


Last edited by Xenoist on Tue Feb 08, 2011 10:11 pm; edited 1 time in total
Back to top
View user's profile Send private message
musv
Advocate
Advocate


Joined: 01 Dec 2002
Posts: 2541
Location: de

PostPosted: Tue Feb 08, 2011 7:36 pm    Post subject: Re: WARNING: updating to glibc-2.13 w/prelink hoses system Reply with quote

Yes, I can confirm this. It's working (the segfaults). :evil:

Odysseus wrote:
If you're running a ~ arch, DO NOT update to glibc-2.13 if you have prelink installed!!! It will completely hose your box!!! I just spent several hours trying to recover from this bug https://bugs.gentoo.org/show_bug.cgi?id=353814


---> afk for several hours. Downgrading glibc.
Back to top
View user's profile Send private message
rich0
Developer
Developer


Joined: 15 Sep 2002
Posts: 106

PostPosted: Tue Feb 08, 2011 7:39 pm    Post subject: Reply with quote

FireBurn wrote:


I got an email back with in an hour telling me that email wasn't the way to communicate bugs


Well, for a bug of this magnitude i'd probably suggest bugzilla plus email plus irc plus a process server... :)

Granted devs have day jobs too, but escalating this was not inappropriate...
Back to top
View user's profile Send private message
musv
Advocate
Advocate


Joined: 01 Dec 2002
Posts: 2541
Location: de

PostPosted: Tue Feb 08, 2011 9:02 pm    Post subject: Reply with quote

I didn't figure out how to downgrade glibc because of sanity check.

So I deinstalled prelink temporary. I hope there will be a patch soon.
Back to top
View user's profile Send private message
rhill
Developer
Developer


Joined: 22 Oct 2004
Posts: 1629
Location: sk.ca

PostPosted: Tue Feb 08, 2011 11:22 pm    Post subject: Reply with quote

HolgerH wrote:
dirtyepic wrote:
you can run
Code:
ROOT="/../" emerge -av1 =glibc-2.12.2

to get around the downgrade check.


Nope, didn't work for me. Could be me using zsh though. Anyway just editing the ebuild and rebuilding worked fine, postfix is back up & running.


Me neither actually. I guess portage is smart enough to rewrite it to "/".
_________________
by design, by neglect
for a fact or just for effect
Back to top
View user's profile Send private message
crculver
n00b
n00b


Joined: 02 Mar 2004
Posts: 17

PostPosted: Wed Feb 09, 2011 1:10 am    Post subject: Reply with quote

Is there any fix for postfix with this glibc? I've recompiled a fair bit of my system since the glibc upgrade and I'm afraid to revert to the previous version of glibc.

Incidentally, wouldn't finally updating the version of kernel-headers in Portage and then recompiling glibc make for a more reliable system for those running recent kernels?
Back to top
View user's profile Send private message
Odysseus
Apprentice
Apprentice


Joined: 23 Jun 2004
Posts: 248
Location: Miami, FL. I miss San Francisco!!!

PostPosted: Thu Feb 10, 2011 10:37 am    Post subject: Reply with quote

crculver wrote:
Is there any fix for postfix with this glibc? I've recompiled a fair bit of my system since the glibc upgrade and I'm afraid to revert to the previous version of glibc.

Incidentally, wouldn't finally updating the version of kernel-headers in Portage and then recompiling glibc make for a more reliable system for those running recent kernels?


Finish recompiling against the new glibc, but make sure that prelink is either disabled or removed from your system. It's far safer to just finish recompiling than downgrading to the previous version (unless you're willing to risk breaking your box). I know I wouldn't risk it myself, despite some of the posts here to the contrary.

Fixing the bugs with this new glibc release is probably one of the highest priorities for the maintainers at the moment. I noticed on bugzilla that they've setup a tracker to focus on eliminating them. So I'm sure that before long we'll either see an update to glibc or to the packages affected by it. Unless you can write code and are willing to contribute the only thing to do is wait and have patience.

Updating the kernel headers only matters if there is a new feature, driver or supported processor in the newer kernel that you need that isn't included in what you have installed. I've gone for well over a year before without updating kernel headers, while updating my kernel sources with each new release, with no negative effects. Where you really run into problems is if you update your headers to a newer version then your kernel sources. I did that once and found I couldn't compile a kernel until I updated my sources.

Most of the time when I see a new kernel header package in portage, I'll mask it until there is a gcc or glibc update, then unmask and recompile my world against both. This way I kill two birds with one stone. Who wants to be constantly recompiling their entire system? Not me.

I hope this helps

Ciao
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2352
Location: Austria

PostPosted: Thu Feb 10, 2011 6:06 pm    Post subject: Reply with quote

So far I haven't noticed any problems on my 1250sth packages system, so it seems to be rather safe with the known exceptions.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Odysseus
Apprentice
Apprentice


Joined: 23 Jun 2004
Posts: 248
Location: Miami, FL. I miss San Francisco!!!

PostPosted: Mon Feb 14, 2011 10:51 pm    Post subject: Reply with quote

Prelink is fixed now in glibc-2.13-r1 as per this bug report https://bugs.gentoo.org/show_bug.cgi?id=353814

I just resynced, updated to the new glibc version, reinstalled and enabled prelink, ran prelink -amR, and all worked as expected. I rebooted my system and it was noticeably faster as was starting KDE on my five year old ~x86 single-core Centrino notebook.

So it appears this has been resolved and I can confirm that things are back to normal now.

The issue appears to have been caused by the omission of this patch that RedHat had included in their build of glibc, that wasn't included in the officially released version. http://sourceware.org/git/?p=glibc.git;a=commit;h=25b3aada

You can read more about it here on the Arch Linux forums https://bugs.archlinux.org/task/22656

So the OP can now mark this thread as "solved" and we can all go back to using prelink as before.

I hope this helps,

Ciao
Back to top
View user's profile Send private message
Hwoarang
Developer
Developer


Joined: 24 Feb 2007
Posts: 701
Location: Leeds, UK

PostPosted: Mon Feb 14, 2011 11:18 pm    Post subject: Reply with quote

Sadly skype is still broken so I had to dowgrade glibc everywhere :(
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Tue Feb 15, 2011 6:48 am    Post subject: Reply with quote

FYI: The issue with postfix (fatal: unable to determine open file limit) seems to be a kernel issue:

https://bugs.gentoo.org/354041 and http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=aa5bd67dcfdf9af34c7fa36ebc87d4e1f7e91873

Strange, though, that the bug concides with an upgrade of glibc to 2.13. I will stay with <glibc-2.13 until the kernel patch arrives in portage.

Christopher

(Hugh, my first post since several years here...)
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
duderonomy
Guru
Guru


Joined: 20 Mar 2004
Posts: 325
Location: SF Bay Area

PostPosted: Fri Feb 18, 2011 12:02 pm    Post subject: Reply with quote

oh man. and I thought this was "just me". lol!
thank you, for this thread...
:D
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Sat Feb 26, 2011 9:10 am    Post subject: Reply with quote

Kernel 2.6.37-gentoo-r1 now contains the Patch which should fix the issue wie Postfix. Will now upgrade to the new kernel and glibc... Hope it works...

Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
iaindb
n00b
n00b


Joined: 30 Jun 2004
Posts: 19

PostPosted: Thu Mar 03, 2011 2:22 am    Post subject: Reply with quote

SoLoR wrote:

im trying to recompile whole system with new glibc to see if it fixed my postfix issue, but it will take a while...


any luck SoLoR? same issue here!
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Thu Mar 03, 2011 6:40 am    Post subject: Reply with quote

With 2.6.37-gentoo-r1 and glibc-2.13-r1 postfix now works for me.

Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum