Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
10-21-2004, 09:53 PM
|
#1
|
Senior Member
Registered: Apr 2003
Location: Minnesota, USA
Distribution: Slack 10.0 w/2.4.26
Posts: 1,032
Rep:
|
Open Office user install error: *** glibc detected *** double free or corruption: 0xb
I can successfully install OpenOffice for the root user, but for the normal users, I get the following error:
*** glibc detected *** double free or corruption: 0xbfffdabc ***
This happens either when I try to install a workstation batch after the network install for the system as well as when I try to issue the command directly from the directory I extracted the files to. I'm using essentially Slackware Current (as of 20 October 2004 or so), and I guess I'm using glibc version: 2.3.3
Any help/suggestions?
|
|
|
01-01-2005, 01:35 PM
|
#2
|
Member
Registered: Apr 2003
Location: Basel, Switzerland
Distribution: Ubuntu, OS X
Posts: 77
Rep:
|
me too
did you solve this?
I have the same problem :-(
I can start soffice as root but I get the error message when starting it as user
Stefan
|
|
|
01-15-2005, 03:41 PM
|
#3
|
LQ Newbie
Registered: Jan 2005
Posts: 3
Rep:
|
quite a solution
I used the MALLOC_CHECK_ variable to go through this problem, but it's a solution i don't like...
Do a "export MALLOC_CHECK_=1" and try again.
The value 1 still produces error messages but let OOo go on with the setup. This is the way i managed to install OOo on my computer. After this, I _have_ to lauch soffice from a console because it doesn't work at all from a gnome icon... It produces error messages but still launches OOo...
Hope it could help you guys.
I'd like a less durty solution if anybody's got one...
|
|
|
01-16-2005, 02:55 AM
|
#4
|
Member
Registered: Dec 2004
Distribution: Windows XP Home, Ubuntu Hoary
Posts: 584
Rep:
|
did you do a net install as root or a normal install as the user? if not, it wont work.
|
|
|
01-16-2005, 03:49 AM
|
#5
|
LQ Newbie
Registered: Jan 2005
Posts: 3
Rep:
|
i made a net install as root without any problem. then i wasn't able to make a local install for the users because of this error but doing the local install as root works well so i don't understand if the problem really comes from glibc or not...
|
|
|
01-16-2005, 06:28 AM
|
#6
|
Member
Registered: Dec 2004
Distribution: Windows XP Home, Ubuntu Hoary
Posts: 584
Rep:
|
Try doing a full local install as user into ur home folder instead. (Or is this a multi-user computer). Also, try grabbing OOo 1.1.3 if it is available. Maybe there is a bug in 1.1.4 or something. Which version is included with Fedora Core 1 by default?
|
|
|
01-16-2005, 07:08 AM
|
#7
|
LQ Newbie
Registered: Jan 2005
Posts: 3
Rep:
|
I use Slackware Linux 10 and I really had to make a net install. Getting back to glibc 2.3.2 solved the problem and I don't have error messages anymore, keeping OOo 1.1.4...
Thanks for your help
|
|
|
All times are GMT -5. The time now is 05:55 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
|
|