LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-19-2009, 09:08 AM   #1
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Rep: Reputation: 164Reputation: 164
-current, multilib, and KDE-4.3.4


I am running -current with multilib enabled. I know that I can't upgrade gcc or glibc, but I was wondering if upgrading KDE would break anything. TB-3x was a wash for me since I couldn't get it to open links in FF. I went back to TB-2x. But my real interest is in KDE, since its my DE of choice.
 
Old 12-19-2009, 09:24 AM   #2
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
Running -current, multilib with KDE4.3.4 here. Yet to discover any problems. One thing I had to manually fix was that perl upgrade to 5.10.1 broke something. But everything works great now. KDE 4.3.4 is fast and stable and feels lighter than it's predecessors.

Regards
 
Old 12-19-2009, 10:05 AM   #3
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
Quote:
KDE 4.3.4 is fast and stable and feels lighter than it's predecessors.
Agreed!

samac
 
Old 12-19-2009, 11:21 AM   #4
Laodiceans
Member
 
Registered: Jan 2006
Distribution: Slackware
Posts: 188

Rep: Reputation: 18
Quote:
Originally Posted by mlangdn View Post
I am running -current with multilib enabled. I know that I can't upgrade gcc or glibc, but I was wondering if upgrading KDE would break anything. TB-3x was a wash for me since I couldn't get it to open links in FF. I went back to TB-2x. But my real interest is in KDE, since its my DE of choice.
Do you read this?

http://www.linuxquestions.org/questi...bird-3-775851/
 
Old 12-19-2009, 11:33 AM   #5
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Original Poster
Rep: Reputation: 164Reputation: 164
Yes - I had read that. I may revisit your last post later. Right now, I have KDE running in init 3, but my default is init 4 with auto login. I just get a command prompt only here. I go back to init 3 and startx, and all is well. I may have to delete the old .kde and reconfigure. I tried to merge the common lines, but I don't think that will be sufficient.

Then I will tackle TB again. Now its time for a nap because I have a 12 hour shift coming up.
 
Old 12-19-2009, 11:51 AM   #6
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
Quote:
Originally Posted by ~sHyLoCk~ View Post
One thing I had to manually fix was that perl upgrade to 5.10.1 broke something.
So, what exactly was that "something"?

Eric
 
Old 12-19-2009, 07:28 PM   #7
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
Quote:
Originally Posted by Alien Bob View Post
So, what exactly was that "something"?

Eric
Hi,
It broke frozen-bubble which I had built from slackbuilds. When I tried launching it, it was looking for files [e.g.->locale-gettext] in perl5/5.10.1 which didn't exist, but they were present in 5.10.0, so I just copied them over to 5.10.1. I tried uninstall /re-install of frozen-bubble still it didn't work, then I did the copy operation. It seems like a dirty method but it worked.

Last edited by ~sHyLoCk~; 12-20-2009 at 06:24 AM.
 
Old 12-20-2009, 12:13 PM   #8
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Original Poster
Rep: Reputation: 164Reputation: 164
Well, I deleted .kde and .kderc, and I still get only a small box in the upper left corner for a shell. I am presently just using startx in init 3. Must be something else in the way.
 
Old 12-20-2009, 12:37 PM   #9
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
Quote:
Well, I deleted .kde and .kderc, and I still get only a small box in the upper left corner for a shell. I am presently just using startx in init 3. Must be something else in the way.
Try running xwmconfig this has worked for me in the past when I have broken my upgrade and only got a TWM desktop. KDE 4.3.4 works very well with multi-lib current.

samac
 
Old 12-20-2009, 01:36 PM   #10
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Original Poster
Rep: Reputation: 164Reputation: 164
I gave xwmconfig a whirl and that didn't work either. KDE runs fine in init 3. Its init 4 where the problem lies.............hmmmmmmmm - off to try something else in a bit.
 
Old 12-20-2009, 01:45 PM   #11
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Original Poster
Rep: Reputation: 164Reputation: 164
Ok - I stopped all the auto-login stuff and switched to init 4. Once there, I put in my username and password and selected the session type. I got the shell in the upper left corner again. So then I logout, start over and select XFCE 4. I got the same result. Can't run XFCE 4 in init 4 either. Something is broken in init 4. Not sure what, but I am going Christmas shopping with the wife for now. This one can wait.
 
Old 12-22-2009, 02:08 PM   #12
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Original Poster
Rep: Reputation: 164Reputation: 164
I ain't having much luck trying to figure out why KDE (or any DE) will not start in init 4. I've been searching for permission problems in my home folder, but have had no luck there either. I'm still looking.
 
Old 12-23-2009, 03:57 AM   #13
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Original Poster
Rep: Reputation: 164Reputation: 164
I finally got this figured out. The problem was in /etc/kde/kdm/kdmrc
What I did was to update another partition that Slackware64 was on to -current. I had no problems after the update getting KDE to work in init 4 with autologin and no password. After the upgrade was finished, I deleted the .kde folder, and simply selected O for all new config files. Basically, I was starting fresh.

Entering init 4 for the first time, I noticed that kdm was very different from what I was seeing on my main install. So I then ventured off to /etc/kde/kdm for a look around. It was there that I found the difference in the two files from each partition. All I did was to edit kdmrc to match the new one on my freshly updated old install. Now I am back in business.

Maybe tomorrow, I will tackle TB 3x and see if I can finally resolve the links opening in FF problem.

Merry Christmas to all!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware64-current multilib: Many improvements, few snags gargamel Slackware 7 11-15-2009 07:23 AM
KDE 4.3.3 in -Current slackd Slackware 45 11-11-2009 08:33 PM
I want to go back to KDE-3.5.10 the current KDE stinks and almost nothing about it is rob.rice Slackware 11 07-10-2009 02:50 AM
KDE 3.5 -> 4.2 Current Ginger Slackware 37 03-22-2009 01:18 PM
KDE 3.5.8 in -current Daedra Slackware 1 10-18-2007 07:10 AM


All times are GMT -5. The time now is 05:16 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration