Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
03-30-2006, 09:17 PM
|
#1
|
|
Guru
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,817
|
Problems with glibc on Slackware current?
I upgraded to glibc -2.3.6-i486-3 a few days ago, and since then the machine has crashed twice.
Once last night, where X crashed and just went to a black screen, changing back to tty1, I could see it said something about a glibc critical error.
Today, when I went to some evening classes, I returned to see my computer apparently restarted, and "last" showed "crashed" about an hour after I left.
Anyone else noticing any problems with this glibc version?
Also, something I thought very odd, when X crashed to the black screen, the only thing that showed up was ">_0" in the top left corner. WTF is up with that...
|
|
|
|
03-30-2006, 09:24 PM
|
#2
|
|
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 13.37
Posts: 4,084
Rep: 
|
What steps did you use to upgrade? The info in upgrade.txt has stuff like; change to single user mode, update glibc-solibs, update pkgtools then update the other packages. After I do this I usually recompile my kernel and nvidia drivers, but only because I've had problems with the nvidia stuff before and I can't recompile it properly without recompiling the kernel (after updating glibc).
|
|
|
|
03-30-2006, 09:57 PM
|
#3
|
|
Guru
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,817
Original Poster
|
I did drop into single user mode and go through the normal routine for updating glibc and the base libraries. But even if I hadn't, isn't going to single user mode just to minimalize the amount of programs running to reduce the risk of programs acting up at the time of upgrade? I have restarted the machine a few times since then.
I didn't recompile the kernel after the upgrade though, and I am using the Nvidia drivers, so that might be something for me to look into.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 03:01 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|