[SuSE Linux] Expert HELP! libncurses.so.3.0/4.0?
I had the kde up and running under libc2, qt4, compiled with egcs with two exceptions, I could not log on using KDM and I could not launch kvt. When I ldd /opt/kde/bin/kvt I saw that it was looking for libncurses.so.4.0. I looked and all I had on my system was 3.0 so I ran YAST to install the libncurses rpm and kvt started working. YAST gave me a warning that i4.0 conflicted with 3.0. Well now the system won't boot. Says it can't find libncurses.3.0. I mounted from the S.u.S.E. disk and did a find /usr -name libncurses* and found only libncurses.so.3.0 -> /lib/libncurses.so.4.0.1. I did not see libncurses.so.4.0.1 under /lib. I then tried to ln -s /lib/libncurses.so.3.0.980228 /usr/lib/libncurses.so.3.0 and rebooted. I still get an error that the system can open libncurses. I then went and looked at the /lib again and there is no libncurses.so.3.0.980228 in lib. The symlink is still there, so I know the file had to be there when I made the symlink. Even stranger there is a libncurses.so.4.0.1 in /lib now. I baffled. Does anyone have any suggestion? What I am most interested in is, will libncurses.so.3.0 cause the system not to boot? TIA, Steve - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Your ncurses needs to be in /lib. Your system needs it before /usr gets mounted. Mount your filesystems using the S.u.S.E. cd rescue method and move libncurses to /lib. If libncurses.so.4.0.1 is in /lib already, just symlink it "ln -s libncurses.so.4.0.1 libncurses.so.3.0" since the boot process will look for libncurses.so.3.0. Steven T. hatton wrote:
I had the kde up and running under libc2, qt4, compiled with egcs with two exceptions, I could not log on using KDM and I could not launch kvt. When I ldd /opt/kde/bin/kvt I saw that it was looking for libncurses.so.4.0. I looked and all I had on my system was 3.0 so I ran YAST to install the libncurses rpm and kvt started working. YAST gave me a warning that i4.0 conflicted with 3.0. Well now the system won't boot. Says it can't find libncurses.3.0. I mounted from the S.u.S.E. disk and did a find /usr -name libncurses* and found only libncurses.so.3.0 -> /lib/libncurses.so.4.0.1. I did not see libncurses.so.4.0.1 under /lib. I then tried to ln -s /lib/libncurses.so.3.0.980228 /usr/lib/libncurses.so.3.0 and rebooted. I still get an error that the system can open libncurses. I then went and looked at the /lib again and there is no libncurses.so.3.0.980228 in lib. The symlink is still there, so I know the file had to be there when I made the symlink. Even stranger there is a libncurses.so.4.0.1 in /lib now. I baffled.
Does anyone have any suggestion? What I am most interested in is, will libncurses.so.3.0 cause the system not to boot?
TIA,
Steve
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- .###. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html</A</A>> \# /## -==============================================- ###'---'#### - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Thanks Michael, That worked. I know you are a gonme so I won't ask you why I can't login through the KDM. :-) Steve Michael Lankton wrote:
Your ncurses needs to be in /lib. Your system needs it before /usr gets mounted. Mount your filesystems using the S.u.S.E. cd rescue method and move libncurses to /lib. If libncurses.so.4.0.1 is in /lib already, just symlink it "ln -s libncurses.so.4.0.1 libncurses.so.3.0" since the boot process will look for libncurses.so.3.0.
Steven T. hatton wrote:
I had the kde up and running under libc2, qt4, compiled with egcs with two exceptions, I could not log on using KDM and I could not launch kvt. When I ldd /opt/kde/bin/kvt I saw that it was looking for libncurses.so.4.0. I looked and all I had on my system was 3.0 so I ran YAST to install the libncurses rpm and kvt started working. YAST gave me a warning that i4.0 conflicted with 3.0. Well now the system won't boot. Says it can't find libncurses.3.0. I mounted from the S.u.S.E. disk and did a find /usr -name libncurses* and found only libncurses.so.3.0 -> /lib/libncurses.so.4.0.1. I did not see libncurses.so.4.0.1 under /lib. I then tried to ln -s /lib/libncurses.so.3.0.980228 /usr/lib/libncurses.so.3.0 and rebooted. I still get an error that the system can open libncurses. I then went and looked at the /lib again and there is no libncurses.so.3.0.980228 in lib. The symlink is still there, so I know the file had to be there when I made the symlink. Even stranger there is a libncurses.so.4.0.1 in /lib now. I baffled.
Does anyone have any suggestion? What I am most interested in is, will libncurses.so.3.0 cause the system not to boot?
TIA,
Steve
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- .###. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html</A</A>> \# /## -==============================================- ###'---'#### - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
You know, actually I don't like to use a desktop environment at all. I play with gnome when new versions come out, but I never run it. Likewise I always have kde installed to play with some of the apps, but I never use it as a windowmanager. I just configure WindowMaker so that all the apps I use are a click or two away and that's all the desktop environment I need. I think a 'standard' xdesktop is not necessarily a bad thing, just as long as alternatives exist for people who detest the status quo. Steven T. Hatton wrote:
Thanks Michael,
That worked. I know you are a gonme so I won't ask you why I can't login through the KDM. :-)
Steve
-- .###. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html</A</A>> \# /## -==============================================- ###'---'#### - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Problem solved! Perhaps I had linkded to the floppy's libncurses.3.0.so.980228. Anyhow, I just copied libncurses30.so.980228 from another system. Works great! One (known) problem left, still can't logon through KDM :-( Steve Steven T. hatton wrote:
I had the kde up and running under libc2, qt4, compiled with egcs with two exceptions, I could not log on using KDM and I could not launch kvt. When I ldd /opt/kde/bin/kvt I saw that it was looking for libncurses.so.4.0. I looked and all I had on my system was 3.0 so I ran YAST to install the libncurses rpm and kvt started working. YAST gave me a warning that i4.0 conflicted with 3.0. Well now the system won't boot. Says it can't find libncurses.3.0. I mounted from the S.u.S.E. disk and did a find /usr -name libncurses* and found only libncurses.so.3.0 -> /lib/libncurses.so.4.0.1. I did not see libncurses.so.4.0.1 under /lib. I then tried to ln -s /lib/libncurses.so.3.0.980228 /usr/lib/libncurses.so.3.0 and rebooted. I still get an error that the system can open libncurses. I then went and looked at the /lib again and there is no libncurses.so.3.0.980228 in lib. The symlink is still there, so I know the file had to be there when I made the symlink. Even stranger there is a libncurses.so.4.0.1 in /lib now. I baffled.
Does anyone have any suggestion? What I am most interested in is, will libncurses.so.3.0 cause the system not to boot?
TIA,
Steve
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (2)
-
hattons＠CPKWEBSER5.ncr.disa.mil -
mlankton＠home.com