KDE4 Upgrade problem

[sfdtux]

OK - Trying to go with KDE4 - I went through the procedure as outlined by Texstar for the proper way to upgrade from KDE 3.5 to 4

I marked all the upgrades and applied them - that seemed to go OK - no errors and about 99 upgrades were installed - I reloaded Synaptic with kde4 added. I then went to task-kde4 and marked that  ( after a reboot just in case). I took only the KDE4 task and left the Extra stuff for later. I just wanted to get the basic system up and running. I got no errors after the task was applied but when I rebooted the system - I got dropped to a command prompt. OK so I tried running StartX - and got a window asking if I want 3D Desktop or not - I said no - tried to login and still only command prompt. So, I siad yes to 3D - no change - Either choice - the systems tries to load -0 I see the "Nvidia" logo flash by - the "Watch" icon diplays on screen then - I get this....

dlopen: /usr/lib/xorg/modules/fonts//libtype1.so: undefined symbol: Type1RegisterFontFileFunction
(EE) Failed to load /usr/lib/xorg/modules/fonts//libtype1.so
(EE) Failed to load module "type1" (loader failed, 7)

I tried to comment out "Type1"  in the modules to see if I could get past that - no go!!
I searched through this forum - only ref to an issue like this was someone using a VM environment - I am not.
I had 2009.2 KDE3.5 running on this machine without any problems - it's a decent system  AMD Proc 3200+ 2 gigs RAM and a MSI video ( NVIDIA - GeForce Chipset ) video card 256 RAM

Can anyone tell me how to get back my Desktop and what possibly happened? I'd like to continue on KDE4 and all its glory.

Thank you.

[MCP]

From a command prompt, navagate to /etc/X11/xorg.conf  Now open with your favorite file editor, and change from 'nvidia' to 'nv'.
This is the default nvidia driver.  It should now startup on reboot.  I had to do this since I had used the nvidia driver from nvidia instead of synaptic.

Hope this helps,
MCP

[sfdtux]

Hello MCP - thank you for response - but sorry to say - it didn't fix the issue.

Along with the error I posted, there is an additional line that now reads...

Failed to initialize GLX extension ( Compatible NVIDIA X driver not found )
xinit: connection to X server lost.

Now that I only get a command prompt - is there a way to apt-get (maybe) drivers I need to get the system to a a GUI ??
I also remember something about using "vesa" as a driver instead - to at least - get the system to diplay desktop gui - I changed the "nv" to "vesa" but that didn't work either !

Now I am a bit lost.

[MCP]

Hello MCP - thank you for response - but sorry to say - it didn't fix the issue.

Along with the error I posted, there is an additional line that now reads...

Failed to initialize GLX extension ( Compatible NVIDIA X driver not found )
xinit: connection to X server lost.

Now that I only get a command prompt - is there a way to apt-get (maybe) drivers I need to get the system to a a GUI ??
I also remember something about using "vesa" as a driver instead - to at least - get the system to diplay desktop gui - I changed the "nv" to "vesa" but that didn't work either !

Now I am a bit lost.

When rebooting switch to safe mode when you get to grub and see what you get.  If you get in with kde you can then use synaptic.

MCP

[Ertain]

From the look of that nVidia issue (with GLX) it's trying to find the files that work with nVidia drivers.  Meaning that you're using the "nv" driver, not the one put out by nVidia.  I have a hunch about this.  Go to /usr/lib and see what libGL.so links to.  (For example, does /usr/lib/libGL.so link to /usr/lib/libGL.so.1?  Or is it linked to a file to a different directory, such as /etc/alternative/foo/libGL.so?)

As for that FreeType file I have no clue what's going on.  It could be an older version of X Server or an older version of FreeType.  Something's old.

[kjpetrie]

Those errors you got first are normal and not fatal. You can comment out the two modules in xorg.conf to get rid of them.

There is a problem with symbolic links pointing to the wrong directory as Ertain suggests with some nvidia drivers, so that hunch is a good one.

You can't run synaptic from the command line but you can run lynx or ncftp if it's installed. You can also use less to view /etc/apt/sources.list to find the URL for your repo, so you can view the repo to see what packages are installed. If you use ctrl+alt+F1...6 to switch terminals you can have lynx in one, man apt-get (if it's not minime) in another(both logged on as your normal user), and run apt-get in a third (logged on as root) - almost as good as having a gui!

Alternatively, use a livecd to run synaptic (don't forget to reload) and make a note of what's available.

[sfdtux]

Both Ertain and KJP suggestions are very good and make sense - unfortunately - I didn't have lynx installed - all I could do was to pull up shell command and poke around - I am not a keyboard CLI ninja sorry to say. I could not find the file libGL.so in any directory ! I did have liGL.so.1.2 though - I don't really understand the Linux file system yet nor how symbolic links work exactly.
The repo I was using was heanet one. 

When I set out to upgrade to KDE4 - I did mark all updates and apply them - I did reboot - and then I installed task-kde4. I did not see any errors but when I rebooted again - I got the "normal" splash screen - that showed some  choices - PCLOS - PCLOS Safe Mode etc - but I could never toggle down to Safe Mode or any other choice - I did see the progress wheel turn - very slowly on only PCLOS to boot the system.

What I did last night - was to pull the nvidia 5300 LE card in the system and installed an older nvidia card I had GeForce 2 I believe. That did get the system up - I finally got into KDE4 - BUT - the system is very slow - I am having a hard time navigating around - the bottom panel where the "Start" icon and Program icons should be is totally unreadable - it is acting very weird - especially when I mouse over it - I am thinking this system is borked and a recovery will be too painful right now - I need it up and running.

I do have all my files etc on a second HD in this computer so it's not a very big deal to re-install 2009.2  which I think I am going to have to do now. I was really looking forward to KDE4 too - wondering when the PCLOS will be released as bug free as possible.

Thank you guys again.

[Ertain]

Aw nuts, and I was about to help you further with symbolic links and installing lynx.

[sfdtux]

oooooppps - now I am disappointed too!   I would really like and welcome the help - at least knowing how the sym. links work. I'm old school computer network engineer and tech - ( mostly Windows - yea yeah I know )

I have 2 machines I use - one is a basic Shuttle PC that I actually got PCLOS and KDE4 running on and it seems to work ok - although I don't much like or understand how to "tweak" it yet, like customize the Panels - Desktop tweaks, and how to work the "Run" command which I am not liking. This Shuttle  has hardly any video power - onBoard VIA chipset at 128 mb Vid ram -   The machine I am really concerned with is my workhorse PC - I had that running just the way I liked it - it saw all our network shares and mapped Windows drives - printers - etc etc. But since KDE3.5 is being phased out and updates in Synaptic were getting limited - I figured time to move on to KDE4. Then all went south with it!!

As I type this - that machine has been reloaded with 2009.2 KDE 3.5 and is right now being updated by Marking All and applying  updates - all 767 packages !! I'd like to give it another try ( not today - I'm toast !)

So - if I can - I'd like to keep this thread open for a day or two before we close it -- I hate giving up.

[kjpetrie]

What a pity, lynx would have been so easy to install; "apt-get install lynx" was all you needed.

Then you could have explored the repo and even visited the forum for help.

Never mind. If it happens again you'll be better prepared.

[sfdtux]

Yes - I know - I really wanted to fix the issue - it would have given me a bit more in my PCLOS "education".

I have to tell you  that I have tried to re-install 2009.2 on that PC again  - I get a great KDE3.5 install but - again - when I do get the KDE4 up on it - it just refuses to play nice. OK - what I have done now - was to pull the HD out and install a new 500 gig SATA - and I am now installing a clean - fresh copy of 2009.2 ( I'll pull my data off the other drive later ).

I am contemplating 2 things   1) with a clean install - try the process again. Do the Upgrades - etc and the KDE4 upgrade or 2) wait til PCLOS releases with the KDE4 ready to go and see if that works out.

I am leaning towards the later ( number 2). WHY ? because I now believe that the PC I am trying to upgrade has underlying issues. With a clean install and all the upgrades marked and installed from heanet repo, I can't seem to get the resolution higher than 1024x768. The OS detects the card correctly but that's all. Something to look into Monday.

It's Friday late afternoon here - I am going to pick this up on Monday - I am not giving up.

Thank you

[g2sws]

I am not very good on linux yet but have you tried just to run XFDrake from the command line as root

[Sleepy]

I am not very good on linux yet but have you tried just to run XFDrake from the command line as root

I agree.
Had a similar problem to the OP and Fixed it by running XFDrake.

[YouCanToo]

Yes - I know - I really wanted to fix the issue - it would have given me a bit more in my PCLOS "education".

I have to tell you  that I have tried to re-install 2009.2 on that PC again  - I get a great KDE3.5 install but - again - when I do get the KDE4 up on it - it just refuses to play nice. OK - what I have done now - was to pull the HD out and install a new 500 gig SATA - and I am now installing a clean - fresh copy of 2009.2 ( I'll pull my data off the other drive later ).

I am contemplating 2 things   1) with a clean install - try the process again. Do the Upgrades - etc and the KDE4 upgrade or 2) wait til PCLOS releases with the KDE4 ready to go and see if that works out.

I am leaning towards the later ( number 2). WHY ? because I now believe that the PC I am trying to upgrade has underlying issues. With a clean install and all the upgrades marked and installed from heanet repo, I can't seem to get the resolution higher than 1024x768. The OS detects the card correctly but that's all. Something to look into Monday.

It's Friday late afternoon here - I am going to pick this up on Monday - I am not giving up.

Thank you

I just installed a fresh copy of 2009.2 updated it using the kde3.pclosusers.com repo, and than using the same repo installed KDE4.3 without any issues.

I updated kde3  using the following repository
Use this line in your /etc/apt/sources.list
rpm http://kde3.pclosusers.com/pclosfiles/ pclinuxos/2007 main extra nonfree kde

DO NOT select any other Repository

After I updated 2009.2 (KDE3.5) I edited the above line to read rpm http://kde3.pclosusers.com/pclosfiles/ pclinuxos/2007 main extra nonfree kde4

Than in synaptic I clicked "RELOAD" and than selected and installed "task-kde4-minimal" I than rebooted and went back into synaptic and installed "task-kde4" and "task-kde4-extra" I rebooted once more and went back into synaptic and clicked on UPDATES and marked them and installed them. Couldn't ask for an easier update.

[sfdtux]

OK - I did install a fresh copy of 2009.2 KDE3.5 on a clean HD. I will use the upgrade procedure outlined by YouCanToo  and watch closely how it goes. By the way - I did do the upgrade previously  per your outline except that I used the heanet.ie/pub/pclinuxos/apt  repo instead - that's the only difference - but if it worked for you - then that's what I'll try this time around.

Sleepy and G2sws - yes - I did run XFDrake - also the "video" command  at the command line - I could set different resolutions and test OK - but on reboot - I would still not get a GUI - always dropped to command line and running the startx command would not get me into a GUI.

FYI - guys - I had NO trouble getting a Shuttle PC ( my second desktop I use ) to upgrade to KDE4. That machine has everything on-board - video - LAN - Sound - and only 512 mb RAM. Same Seagate 500 gig SATA Hard Drives were used in all machines. 

Let's see what happens now - I should have it all set up very soon.