Re: gnome wont start: libesd.so.0
urgrue <[email protected]> Wed, 30 Oct 2002 11:30:39 +0200
| Newsgroups | gmane.linux.gentoo.newbies |
|---|---|
| Message-ID | <[email protected]> |
well, after "emerge -e gnome", nothing changed. that should reinstall=20 absolutely everything to do with gnome, right? well it didnt help, but, only now my ever-observant self noticed that=20 emerge doesnt update config files in /etc automatically, so after moving the ._cfgxxxx files into the correct places, the libesd=20 error has disappeared! go figure. replaced files were=20 hosts,profile,make.globals,fstab,make.conf,rc.conf, and fonts.conf. but now i get: ** ERROR **: Failed to match any font.... well, progress is progress... thanks, urgrue >=20 > > didnt help... > > qpkg -c esound returns: > > media-sound/esound-0.2.20 * > > 0/101 > > (what exactly does that mean?) > > i reinstalled esound, with only -02 -pipe -march=3Di686, even tried > > i586. but it didnt make any difference. same error... > > any ideas? > > > curioser and curioser.... >=20 > qpkg -c is "check", ie, it verifies that none of the files installed > by > the package is missing, has changed or is otherways tampered with. >=20 > Since you reinstalled esound its hardly an overoptimized setting > either, > so something else is seriously weird-out when it comes to how your > system handles modules and loading.. do other dynamically linked > programs break? >=20 >=20 > can you try running fex. "esdctl serverinfo" (esd control program, > output server information), since that program depends on > "libesd.so.0" > and if its a problem with the esd lib it will then break.. >=20 > if that works, we can probably assume that your esd installation is > functionning and its your "gnome-core" package that is broken (Gnome 2 > uses /usr/libexec/gnome_segv2 ) >=20 > can you also post the output of "ldd /usr/libexec/gnome_segv" or if > there are any broken library requirements there? >=20 >=20 > //Spider >=20 >=20 > -- > begin .signature > This is a .signature virus! Please copy me into your .signature! > See Microsoft KB Article Q265230 for more information. > end >=20