On Monday 27 May 2002 11:20 pm, Travis Owens wrote:

On Mon, 2002-05-27 at 22:06, Andy Stewart wrote:

...

Hi everybody,

After upgrading to KDE 3.0.1 with the packages in the supplementary directories, YaST2 no longer works properly in every case.

When I attempt to use the online update from YaST2 with KDE running, after typing my root password, a portion of the YaST2 window eventually turns grey (instead of showing the online update). I see the following error messages back at my console window (the one from which I originally started X):

Undefined symbol init_libkcm_yast2 in /opt/kde3/lib/libkdecore.so.4 The library libkcm_yast2 does not offer an init_libkcm_yast2 function

Ok, it sounds like you d/l-ed the packages from the ftp server and manually installed the updates?

Yes, that's precisely what I did.

If so, did you run SuSEconfig and ldconfig after to sync the libraries?

Yes. I also double checked that /opt/kde3/lib was listed in /etc/ld.so.conf.

Just a thought.

Good try - thanks!

Travis.

Here is more detailed info: kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/libkdecore.so.4: undefined symbol: init_libkcm_yast2 kdecore (KLibLoader): WARNING: KLibrary: The library libkcm_yast2 does not offer an init_libkcm_yast2 function ASSERT: "!name.isEmpty()" in kinstance.cpp (55) -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

On Tuesday 28 May 2002 02:45, Fergus Wilde wrote:

On Tuesday 28 May 2002 04:20, you wrote:

...

On Mon, 2002-05-27 at 22:06, Andy Stewart wrote:

...

Hi everybody,

After upgrading to KDE 3.0.1 with the packages in the supplementary directories, YaST2 no longer works properly in every case.

<snip>

...

Ok, it sounds like you d/l-ed the packages from the ftp server and manually installed the updates?

If so, did you run SuSEconfig and ldconfig after to sync the libraries?

YaST2 has stopped working in graphical mode altogether on my system since the 3.0.1 upgrade, made the way you describe. I did indeed run SuSEconfig - but when you say here 'run ldconfig', is ldconfig not called by SuSEconfig in any event? I understood that it was, but would be grateful to be put right if that's not the case.

I'd also be grateful for advice on how to get graphical YaST2 back, though the upgrade to 3.0.1 was well worth the sacrifice anyway ...

Best Fergus

I have the same problem as well, no yast2 after update to 3.0.1. Very annoying.

On Tue, 2002-05-28 at 03:45, Fergus Wilde wrote:

YaST2 has stopped working in graphical mode altogether on my system since the 3.0.1 upgrade, made the way you describe. I did indeed run SuSEconfig - but when you say here 'run ldconfig', is ldconfig not called by SuSEconfig in any event? I understood that it was, but would be grateful to be put right if that's not the case.

Ok, I looked through SuSEconfig in /sbin and there is no reference to ldconfig ! Also, I ran it from the CLI in verbose mode and there was no reference to ldconfig ! :^/ So, maybe it doesn't ??! (This was very preliminary searching) :)

I'd also be grateful for advice on how to get graphical YaST2 back, though the upgrade to 3.0.1 was well worth the sacrifice anyway ...

I have heard several people mention cleaning out the /tmp directory of all things YaST before running it when problems arise. :) cheers! -- Travis. For Laptop issuses, check out: http://www.linux-laptop.net For Wireless LAN issues, check out: http://www.linux-wlan.com Don't forget to document your experiences, tricks, and advice while using Linux. Post it somewhere so we'll all benefit from it. You never know who will be asking the same question next time.

Le Mercredi 29 Mai 2002 10:55, Fergus Wilde a écrit / wrote:

...

is ldconfig not called

...

by SuSEconfig in any event? I understood that it was, but would be grateful to be put right if that's not the case.

Ok, I looked through SuSEconfig in /sbin and there is no reference to ldconfig ! Also, I ran it from the CLI in verbose mode and there was no reference to ldconfig ! :^/

So, maybe it doesn't ??! (This was very preliminary searching) :)

OK - interesting. It certainly lives in sbin on 7.3, but I will check on my 8 installation later and look for it. It never occured to me that it would have left town ...

The SuSEconfig call to 'ldconfig' lives in : /sbin/conf.d/SuSEconfig.aaa_at_first (at least on my 8.0 system...) Francis

On Tuesday 28 May 2002 2:10 pm, Ben Rosenberg wrote:

* Fergus Wilde (fwilde@chethams.org.uk) [020528 01:55]: ::YaST2 has stopped working in graphical mode altogether on my system since :: the 3.0.1 upgrade, made the way you describe. I did indeed run :: SuSEconfig - but when you say here 'run ldconfig', is ldconfig not :: called by SuSEconfig in any event? I understood that it was, but would :: be grateful to be put right if that's not the case.

If you use sux and su to root then type yast2 it comes up. It's a problem with the .desktop files in ~/.kde/share/applnk. Some how they got very broken between 2.2.2 -> 3.0 and 3.0.1.

I tried to fire up yast2 from the Kmenu and it never displayed but was running and sucking up CPU like there was no tomorrow. I killed it then did an sux and fired up yast2. I then went to the Online update and it worked fine. It's something bizarre with the .desktop entries.

-=Ben

HI Ben, I tried what you suggested and it did not help. The failure mode is the same. BTW, I have neither man nor info pages for sux...what is it? Thanks, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org