<![CDATA[Linux-Noob Forums - KDE]]> https://www.linux-noob.com/forums/ Fri, 12 Jun 2026 07:50:34 +0000 MyBB <![CDATA[KDE 4.0 Firefox 3 theme]]> https://www.linux-noob.com/forums/thread-883.html Mon, 04 Aug 2008 19:39:28 +0200 hybrid]]> https://www.linux-noob.com/forums/thread-883.html For those of us now running the KDE 4.0 series, there is a Firefox 3.0 theme being developed to foster better visual integration between KDE 4 and Firefox.

 

The theme uses the Oxygen icon set and also includes other visual tweaks to best match the visual style of KDE 4.

 

[Image: 2575739126_f15343af52.jpg]

 

It's at an early stage right now, so use with caution. The link you'll want is:

 

http://ramonantonio.net/kde-firefox/

]]> For those of us now running the KDE 4.0 series, there is a Firefox 3.0 theme being developed to foster better visual integration between KDE 4 and Firefox.

 

The theme uses the Oxygen icon set and also includes other visual tweaks to best match the visual style of KDE 4.

 

[Image: 2575739126_f15343af52.jpg]

 

It's at an early stage right now, so use with caution. The link you'll want is:

 

http://ramonantonio.net/kde-firefox/

]]> <![CDATA[xkill in terminal]]> https://www.linux-noob.com/forums/thread-1772.html Mon, 16 Oct 2006 12:25:41 +0200 Micah]]> https://www.linux-noob.com/forums/thread-1772.html Hey, I've used KDE for about three days and already tried experimenting to get used to it, as i've been a hopeless Windows user for my entire life... Shocking, I know Tongue

 

Now, anyway, my Firefox browser (like there is any other) crashed and I couldn't figure out how to kill it, so I used the "xkill" command, which worked great! However... I had Firefox minimized and thus clicked on the bottom "start-bar line" to remove it. Suddenly I was sitting there with only icons on my desktop and no startline! Firefox still running... well, sort of... ^^,

 

I got it back by restarting, but is there a way to "load" it again on the fly using the terminal?

 

Help will be very much appreciated!

 

On pre-hand; Thanks! (Not even sure pre-hand is a word... o.O)

]]> Hey, I've used KDE for about three days and already tried experimenting to get used to it, as i've been a hopeless Windows user for my entire life... Shocking, I know Tongue

 

Now, anyway, my Firefox browser (like there is any other) crashed and I couldn't figure out how to kill it, so I used the "xkill" command, which worked great! However... I had Firefox minimized and thus clicked on the bottom "start-bar line" to remove it. Suddenly I was sitting there with only icons on my desktop and no startline! Firefox still running... well, sort of... ^^,

 

I got it back by restarting, but is there a way to "load" it again on the fly using the terminal?

 

Help will be very much appreciated!

 

On pre-hand; Thanks! (Not even sure pre-hand is a word... o.O)

]]> <![CDATA[How To Get Xscreensaver Properly Running in KDE Environment]]> https://www.linux-noob.com/forums/thread-1782.html Mon, 09 Oct 2006 05:20:21 +0200 SendDerek]]> https://www.linux-noob.com/forums/thread-1782.html I've been having a lot of headaches with the screensaver in my Suse 10.1 installation using KDE. Sometimes the screensaver would work, other times it wouldn't. Sometimes it would fade in/out in a cool effect, sometimes it wouldn't (I'll show you that little trick as well).

 

For the most part, I think I got it covered, and I'd like to share how I managed to 'fix' it up a little by reading a FAQ from the xscreensaver site:

Quote:Instead of using the usual xscreensaver mechanisms, the KDE folks have chosen to roll their own screen saver wrapper that is inferior to the xscreensaver-demo way of doing things in any number of ways.  

The only sensible (and secure) way to use a screen saver under KDE is to turn off KDE's built-in screen saver, and use xscreensaver instead. How you go about this is explained in the "Using KDE" section of the xscreensaver manual.

 

The GNOME people used to have the same class of bugs as the KDE folks now have, but the GNOME crew finally came to their senses, and we worked together to come up with a solution that resulted in their being one and only one xscreensaver configurator, instead of two: mine and theirs.

 

Will the KDE people wise up and do the same? Only time will tell. I encourage you to encourage them.
 

Here are the steps that I took to resolve it. It's not very tricky, so this shouldn't take a lot of time at all.

 

1.) I opened "Personal Settings" (AKA "Control Center" Located in "My System" in the KDE Launcher or Kicker).

 

2.) Then I clicked on "Appearance and Themes".

 

3.) Then I clicked on "Screensaver" and disabled the screensaver by unchecking "Start Automatically".

 

4.) I closed the "Personal Settings" window and opened up the "Run Command" by pressing ALT+F2.

 

5.) I typed in "xscreensaver-demo" to open up the true xscreensaver wrapper.

 

6.) I picked out my favorite screensaver (XAnalogTV) and then set the time to be "Blank After" 3 minutes and then exited the "xscreensaver-demo" program.

 

Ta-da! Finished. Now at least the screensaver should work a little better!

 

There has been some note to add a file called xscreensaver.desktop to your /home/[username]/.kde/Autostart directory with this as it's contents (I can't confirm or deny that this step is needed):



Code:
[Desktop Entry] Exec=xscreensaver Name=XScreensaver Type=Application X-KDE-StartupNotify=false




 

Now for the Fade in/out trick. It's a lot easier than you would imagine, but it sure adds a nice touch to the desktop.

 

1.) Open the "xscreensaver-demo" window again by using ALT+F2 and typing in "xscreensaver-demo".

 

2.) Click on the "Advanced" tab next to "Display Modes"

 

3.) In the "Fading and Color Maps" section of this tab, make sure that the proper options are checked. The rest is self explainatory I believe.

]]> I've been having a lot of headaches with the screensaver in my Suse 10.1 installation using KDE. Sometimes the screensaver would work, other times it wouldn't. Sometimes it would fade in/out in a cool effect, sometimes it wouldn't (I'll show you that little trick as well).

 

For the most part, I think I got it covered, and I'd like to share how I managed to 'fix' it up a little by reading a FAQ from the xscreensaver site:

Quote:Instead of using the usual xscreensaver mechanisms, the KDE folks have chosen to roll their own screen saver wrapper that is inferior to the xscreensaver-demo way of doing things in any number of ways.  

The only sensible (and secure) way to use a screen saver under KDE is to turn off KDE's built-in screen saver, and use xscreensaver instead. How you go about this is explained in the "Using KDE" section of the xscreensaver manual.

 

The GNOME people used to have the same class of bugs as the KDE folks now have, but the GNOME crew finally came to their senses, and we worked together to come up with a solution that resulted in their being one and only one xscreensaver configurator, instead of two: mine and theirs.

 

Will the KDE people wise up and do the same? Only time will tell. I encourage you to encourage them.
 

Here are the steps that I took to resolve it. It's not very tricky, so this shouldn't take a lot of time at all.

 

1.) I opened "Personal Settings" (AKA "Control Center" Located in "My System" in the KDE Launcher or Kicker).

 

2.) Then I clicked on "Appearance and Themes".

 

3.) Then I clicked on "Screensaver" and disabled the screensaver by unchecking "Start Automatically".

 

4.) I closed the "Personal Settings" window and opened up the "Run Command" by pressing ALT+F2.

 

5.) I typed in "xscreensaver-demo" to open up the true xscreensaver wrapper.

 

6.) I picked out my favorite screensaver (XAnalogTV) and then set the time to be "Blank After" 3 minutes and then exited the "xscreensaver-demo" program.

 

Ta-da! Finished. Now at least the screensaver should work a little better!

 

There has been some note to add a file called xscreensaver.desktop to your /home/[username]/.kde/Autostart directory with this as it's contents (I can't confirm or deny that this step is needed):



Code:
[Desktop Entry] Exec=xscreensaver Name=XScreensaver Type=Application X-KDE-StartupNotify=false




 

Now for the Fade in/out trick. It's a lot easier than you would imagine, but it sure adds a nice touch to the desktop.

 

1.) Open the "xscreensaver-demo" window again by using ALT+F2 and typing in "xscreensaver-demo".

 

2.) Click on the "Advanced" tab next to "Display Modes"

 

3.) In the "Fading and Color Maps" section of this tab, make sure that the proper options are checked. The rest is self explainatory I believe.

]]> <![CDATA[Very Frustrated with Installing Screensavers...]]> https://www.linux-noob.com/forums/thread-1797.html Fri, 29 Sep 2006 03:06:24 +0200 SendDerek]]> https://www.linux-noob.com/forums/thread-1797.html So, I've downloaded a couple sweet screensavers that I would love to get working. One is smoothslidesaver and the other is kcometen3.

 

I've done this so far:

 



Code:
./configure make *change to root using su* make install make clean




 

I look in my Desktop properties under screensaver, but neither one of them is there. I have also tried to just goto

Code:
xscreensaver-demo


in the terminal, but it's not listed there either.

 

Help! This is so very frustrating to me. I just want a screensaver!

 

-Derek

]]> So, I've downloaded a couple sweet screensavers that I would love to get working. One is smoothslidesaver and the other is kcometen3.

 

I've done this so far:

 



Code:
./configure make *change to root using su* make install make clean




 

I look in my Desktop properties under screensaver, but neither one of them is there. I have also tried to just goto

Code:
xscreensaver-demo


in the terminal, but it's not listed there either.

 

Help! This is so very frustrating to me. I just want a screensaver!

 

-Derek

]]> <![CDATA[Trying to Install Kompose...]]> https://www.linux-noob.com/forums/thread-1811.html Thu, 21 Sep 2006 06:02:06 +0200 SendDerek]]> https://www.linux-noob.com/forums/thread-1811.html

Code:
checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix! hildretd@linux-kblp:~/Programs/kompile-0.3-beta2>




 

I'm just trying to install Kompose, but I can't seem to get past the "./configure" stage.

 

Any suggestions?

 

Thanks for any help in advance!

-Derek

]]>

Code:
checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix! hildretd@linux-kblp:~/Programs/kompile-0.3-beta2>




 

I'm just trying to install Kompose, but I can't seem to get past the "./configure" stage.

 

Any suggestions?

 

Thanks for any help in advance!

-Derek

]]> <![CDATA[KDE's new start menu]]> https://www.linux-noob.com/forums/thread-1841.html Tue, 22 Aug 2006 19:29:48 +0200 anyweb]]> https://www.linux-noob.com/forums/thread-1841.html check it out

 

[/url][url=http://home.kde.org/~binner/kickoff/sneak_preview.html]http://home.kde.org/~binner/kickoff/sneak_preview.html

 

running on OpenSuse 10.2

 

cheers

anyweb

]]> check it out

 

[/url][url=http://home.kde.org/~binner/kickoff/sneak_preview.html]http://home.kde.org/~binner/kickoff/sneak_preview.html

 

running on OpenSuse 10.2

 

cheers

anyweb

]]> <![CDATA[mepis kde problem [dcop]]]> https://www.linux-noob.com/forums/thread-2150.html Thu, 16 Feb 2006 23:04:36 +0100 rick]]> https://www.linux-noob.com/forums/thread-2150.html Hi ,

after trying Mandriva I think Mepis might be more suitable after using the Live CD for 2 days or so.

I have just done a full install off the CD ,which i thought went without a hitch

dual boots with XP with GRUB

after rebooting now when KDE starts loading, after the login window I get this message & cant get past it

 

"there was an error setting up inter-process communications for KDE the message returned for the system was could not read connection list /root/dcopserver_ricks p4_0 please check that the dcopsever process is running "

 

as said above I cannot get passed this window ,when OK is clicked the screen goes black for 1 second then back to the same message ,

 

have i missed something when setting up the install?

thanks for reading

 

edit google brings up this www.mepis.org/?q=node/897

being a newb , I dont know what to do I have reinstalled 3 times & still get it

if it was a bad burn [burnt at 2x on a DVD] surely the live CD would baulk also

 

Rick

]]> Hi ,

after trying Mandriva I think Mepis might be more suitable after using the Live CD for 2 days or so.

I have just done a full install off the CD ,which i thought went without a hitch

dual boots with XP with GRUB

after rebooting now when KDE starts loading, after the login window I get this message & cant get past it

 

"there was an error setting up inter-process communications for KDE the message returned for the system was could not read connection list /root/dcopserver_ricks p4_0 please check that the dcopsever process is running "

 

as said above I cannot get passed this window ,when OK is clicked the screen goes black for 1 second then back to the same message ,

 

have i missed something when setting up the install?

thanks for reading

 

edit google brings up this www.mepis.org/?q=node/897

being a newb , I dont know what to do I have reinstalled 3 times & still get it

if it was a bad burn [burnt at 2x on a DVD] surely the live CD would baulk also

 

Rick

]]> <![CDATA[redhat 9 -> kde3.2]]> https://www.linux-noob.com/forums/thread-3228.html Tue, 20 Jul 2004 01:30:09 +0200 dallas]]> https://www.linux-noob.com/forums/thread-3228.html Hi all...

 

Just want to write down my experience in upgrading my redhat 9 machine into a pretty kde3.2 machine Smile

 

First of all my redhat 9 box is a standard rpm installation with no (significant) tarballs installed. It apt-gets it's rpms from freshrpms and the dag wieers collection. It's pretty much up2date.

 

The kde3.2 rpms I used were from [/url][url=ftp://apt.kde-redhat.org/apt/kde-redhat/9/RPMS.stable/]ftp://apt.kde-redhat.org/apt/kde-redhat/9/RPMS.stable/

 

I am going to do this at home soon too, probably with the unstable ones.. just to push my luck Wink

 

 

redhat 9 needs a lot more rpms than is provided by kde-redhat.org. so off i went using rpm.pbone.net to upgrade and/or install other things. here's a list of pre-installation rpms I used.

 

hicolor-icon-theme-0.3-0.fdr.0.noarch.rpm libasound2-1.0.5-0_14.rh9.at.i386.rpm mathml-fonts-1.0-0.fdr.14.noarch.rpm jasper-1.701.0-0.fdr.2.rh90.i386.rpm libgsf-1.8.2-0.fdr.0.rh90.i386.rpm samba-2.2.8-1.i386.rpm lcms-1.12-0.fdr.0.rh90.i386.rpm libgsf-devel-1.8.2-0.fdr.0.rh90.i386.rpm themer-1.50-0.fdr.0.noarch.rpm

 

These are all kde-redhat.org except libasound, provided by atrpms.net; samba by samba.org and the mathml are straight from fedora.

 

Next install QT.

 

gtk-qt-engine-0.3-0.fdr.0.rh90.i386.rpm qt2-designer-2.3.2-0.fdr.0.rh90.i386.rpm qt2-static-2.3.2-0.fdr.0.rh90.i386.rpm qt2-2.3.2-0.fdr.0.rh90.i386.rpm qt2-devel-2.3.2-0.fdr.0.rh90.i386.rpm qt2-Xt-2.3.2-0.fdr.0.rh90.i386.rpm

 

(all of these were from kde-redhat.org)

 

Next libxml and libxslt

libxml2-2.6.9-0.99_10.rh9.at.i386.rpm libxml2-python-2.6.9-0.99_10.rh9.at.i386.rpm

libxml2-devel-2.6.9-0.99_10.rh9.at.i386.rpm

 

libxslt1-1.1.7-2_5.rh9.at.i386.rpm libxslt-devel-1.1.7-2_5.rh9.at.i386.rpm

libxslt-1.1.7-2_5.rh9.at.i386.rpm libxslt-python-1.1.7-2_5.rh9.at.i386.rpm

 

(these by atrpms.net)

 

 

Now onto kdecore. this is a lot :/

 

arts-1.2.3-1.0.rh90.kde.i386.rpm kdenetwork-devel-3.2.3-1.0.rh90.kde.i386.rpm

arts-devel-1.2.3-1.0.rh90.kde.i386.rpm kdesdk-3.2.3-1.1.rh90.kde.i386.rpm

aspell-0.50.3-0.fdr.2.rh90.i386.rpm kdesdk-devel-3.2.3-1.1.rh90.kde.i386.rpm

aspell-compat-0.33.7.1-0.ximian.2.i386.rpm kdevelop-3.0.3-1.0.rh90.kde.i386.rpm

aspell-devel-0.50.3-0.fdr.2.rh90.i386.rpm koffice-1.3.2-1.0.rh90.kde.i386.rpm

aspell-en-0.51-6.i386.rpm pspell-compat-0.12.2-0.ximian.4.i386.rpm

ghostscript-7.07-25.fdr.2.rh90.i386.rpm PyKDE-3.11.1-0.fdr.0.rh90.i386.rpm

ghostscript-devel-7.07-25.fdr.2.rh90.i386.rpm PyKDE-devel-3.11.1-0.fdr.0.rh90.i386.rpm

graphviz-1.12-0.fdr.2.rh90.i386.rpm PyQt-3.12-0.fdr.1.rh90.i386.rpm

gtk+-1.2.10-30.fdr.3.rh90.i386.rpm PyQt-devel-3.12-0.fdr.1.rh90.i386.rpm

gtk2-2.2.4-6.fdr.2.rh90.i386.rpm PyQt-examples-3.12-0.fdr.1.rh90.i386.rpm

gtk2-devel-2.2.4-6.fdr.2.rh90.i386.rpm PyQt-qscintilla-3.12-0.fdr.1.rh90.i386.rpm

gtk+-devel-1.2.10-30.fdr.3.rh90.i386.rpm qscintilla-1.3-0.fdr.0.rh90.i386.rpm

ImageMagick-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-c++-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-designer-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-c++-devel-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-devel-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-devel-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-MySQL-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-perl-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-ODBC-3.3.2-10.1.rh90.kde.i386.rpm

kdeadmin-3.2.3-1.0.rh90.kde.i386.rpm qt-PostgreSQL-3.3.2-10.1.rh90.kde.i386.rpm

kdeartwork-3.2.3-1.1.rh90.kde.i386.rpm quanta-3.2.3-1.0.rh90.kde.i386.rpm

kdeartwork-icons-3.2.3-1.1.rh90.kde.i386.rpm redhat-artwork-0.96-1.1.rh90.kde.i386.rpm

kdebase-3.2.3-1.0.rh90.kde.i386.rpm redhat-menus-1.4.1-1.noarch.rpm

kdebase-devel-3.2.3-1.0.rh90.kde.i386.rpm sip-3.10.2-0.fdr.0.rh90.i386.rpm

kdelibs-3.2.3-1.0.rh90.kde.i386.rpm sip-devel-3.10.2-0.fdr.0.rh90.i386.rpm

kdelibs-devel-3.2.3-1.0.rh90.kde.i386.rpm superkaramba-0.33-0.fdr.1.rh90.i386.rpm

kdenetwork-3.2.3-1.0.rh90.kde.i386.rpm wv2-0.2.1-0.fdr.2.rh90.i386.rpm

 

If you were to drop koffice, you could also skip upgrading ghostscript, imagemagick, aspell, pspell and wv2. keeping koffice proved to be a real bitch :/

 

All these rpms by kde-redhat.org except aspell/pspell by ximian, redhat-* come from fedora afaik.

 

Then your installation should break. ld.so.conf does not get told there are new qt libraries, so add in /usr/lib/qt-3.3/lib and your apps (kdeinit) should find that. after that things are all fine.

a quick reboot will make kdm DoS your cpu. I have no idea why but it does not like new qt libraries.

Jul 14 15:19:17 sa kdm: :0[2692]: Abnormal termination of greeter for display :0, code 127, signal 0

 

weird shit.

 

Post installation rpms:

 

fribidi-0.10.4-0.fdr.0.rh90.i386.rpm kdepim-3.2.3-1.0.rh90.kde.i386.rpm

k3b-0.11.12-0.fdr.0.rh90.i386.rpm kdepim-devel-3.2.3-1.0.rh90.kde.i386.rpm

k3b-mp3-0.11.12-0.fdr.0.rh90.i386.rpm kdeutils-3.2.3-1.0.rh90.kde.i386.rpm

kdeaddons-3.2.3-1.0.rh90.kde.i386.rpm libmal-0.31-0.fdr.1.rh90.i386.rpm

kdegames-3.2.3-1.0.rh90.kde.i386.rpm musicman-0.11-0.fdr.0.rh90.i386.rpm

kdegames-devel-3.2.3-1.0.rh90.kde.i386.rpm scribus-1.1.7-0.fdr.0.rh90.i386.rpm

kdegraphics-3.2.3-1.0.rh90.kde.i386.rpm scribus-devel-1.1.7-0.fdr.0.rh90.i386.rpm

kdegraphics-devel-3.2.3-1.0.rh90.kde.i386.rpm thinkeramik-3.2.1-0.fdr.1.rh90.i386.rpm

 

(all by kde-redhat.org)

 

you should install these as it makes things all pretty. don't forget nuvola icons!!!! a must for kde3.2!!! things to watch out for are kdepim/kmail being buggy pieces of shit (im staying with evolution for now) and all gtk apps look so weird. I haven't upgraded this box to the new mozilla 1.6/galeon that apt has on offer. i like the old galeon 1.2.13

 

I have yet to install kdemultimedia and openoffice.org

they`re conflicting with so much shit and I'm lazy.

 

All in all this effort was a big pain in the ass but it's worth it, because now i can edit python in kdevelop3 !!!!! Smile

anybody else who wants kde3.2 should upgrade to fedora2.

da!!as

]]> Hi all...

 

Just want to write down my experience in upgrading my redhat 9 machine into a pretty kde3.2 machine Smile

 

First of all my redhat 9 box is a standard rpm installation with no (significant) tarballs installed. It apt-gets it's rpms from freshrpms and the dag wieers collection. It's pretty much up2date.

 

The kde3.2 rpms I used were from [/url][url=ftp://apt.kde-redhat.org/apt/kde-redhat/9/RPMS.stable/]ftp://apt.kde-redhat.org/apt/kde-redhat/9/RPMS.stable/

 

I am going to do this at home soon too, probably with the unstable ones.. just to push my luck Wink

 

 

redhat 9 needs a lot more rpms than is provided by kde-redhat.org. so off i went using rpm.pbone.net to upgrade and/or install other things. here's a list of pre-installation rpms I used.

 

hicolor-icon-theme-0.3-0.fdr.0.noarch.rpm libasound2-1.0.5-0_14.rh9.at.i386.rpm mathml-fonts-1.0-0.fdr.14.noarch.rpm jasper-1.701.0-0.fdr.2.rh90.i386.rpm libgsf-1.8.2-0.fdr.0.rh90.i386.rpm samba-2.2.8-1.i386.rpm lcms-1.12-0.fdr.0.rh90.i386.rpm libgsf-devel-1.8.2-0.fdr.0.rh90.i386.rpm themer-1.50-0.fdr.0.noarch.rpm

 

These are all kde-redhat.org except libasound, provided by atrpms.net; samba by samba.org and the mathml are straight from fedora.

 

Next install QT.

 

gtk-qt-engine-0.3-0.fdr.0.rh90.i386.rpm qt2-designer-2.3.2-0.fdr.0.rh90.i386.rpm qt2-static-2.3.2-0.fdr.0.rh90.i386.rpm qt2-2.3.2-0.fdr.0.rh90.i386.rpm qt2-devel-2.3.2-0.fdr.0.rh90.i386.rpm qt2-Xt-2.3.2-0.fdr.0.rh90.i386.rpm

 

(all of these were from kde-redhat.org)

 

Next libxml and libxslt

libxml2-2.6.9-0.99_10.rh9.at.i386.rpm libxml2-python-2.6.9-0.99_10.rh9.at.i386.rpm

libxml2-devel-2.6.9-0.99_10.rh9.at.i386.rpm

 

libxslt1-1.1.7-2_5.rh9.at.i386.rpm libxslt-devel-1.1.7-2_5.rh9.at.i386.rpm

libxslt-1.1.7-2_5.rh9.at.i386.rpm libxslt-python-1.1.7-2_5.rh9.at.i386.rpm

 

(these by atrpms.net)

 

 

Now onto kdecore. this is a lot :/

 

arts-1.2.3-1.0.rh90.kde.i386.rpm kdenetwork-devel-3.2.3-1.0.rh90.kde.i386.rpm

arts-devel-1.2.3-1.0.rh90.kde.i386.rpm kdesdk-3.2.3-1.1.rh90.kde.i386.rpm

aspell-0.50.3-0.fdr.2.rh90.i386.rpm kdesdk-devel-3.2.3-1.1.rh90.kde.i386.rpm

aspell-compat-0.33.7.1-0.ximian.2.i386.rpm kdevelop-3.0.3-1.0.rh90.kde.i386.rpm

aspell-devel-0.50.3-0.fdr.2.rh90.i386.rpm koffice-1.3.2-1.0.rh90.kde.i386.rpm

aspell-en-0.51-6.i386.rpm pspell-compat-0.12.2-0.ximian.4.i386.rpm

ghostscript-7.07-25.fdr.2.rh90.i386.rpm PyKDE-3.11.1-0.fdr.0.rh90.i386.rpm

ghostscript-devel-7.07-25.fdr.2.rh90.i386.rpm PyKDE-devel-3.11.1-0.fdr.0.rh90.i386.rpm

graphviz-1.12-0.fdr.2.rh90.i386.rpm PyQt-3.12-0.fdr.1.rh90.i386.rpm

gtk+-1.2.10-30.fdr.3.rh90.i386.rpm PyQt-devel-3.12-0.fdr.1.rh90.i386.rpm

gtk2-2.2.4-6.fdr.2.rh90.i386.rpm PyQt-examples-3.12-0.fdr.1.rh90.i386.rpm

gtk2-devel-2.2.4-6.fdr.2.rh90.i386.rpm PyQt-qscintilla-3.12-0.fdr.1.rh90.i386.rpm

gtk+-devel-1.2.10-30.fdr.3.rh90.i386.rpm qscintilla-1.3-0.fdr.0.rh90.i386.rpm

ImageMagick-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-c++-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-designer-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-c++-devel-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-devel-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-devel-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-MySQL-3.3.2-10.1.rh90.kde.i386.rpm

ImageMagick-perl-5.5.7.15-0.fdr.2.rh90.i386.rpm qt-ODBC-3.3.2-10.1.rh90.kde.i386.rpm

kdeadmin-3.2.3-1.0.rh90.kde.i386.rpm qt-PostgreSQL-3.3.2-10.1.rh90.kde.i386.rpm

kdeartwork-3.2.3-1.1.rh90.kde.i386.rpm quanta-3.2.3-1.0.rh90.kde.i386.rpm

kdeartwork-icons-3.2.3-1.1.rh90.kde.i386.rpm redhat-artwork-0.96-1.1.rh90.kde.i386.rpm

kdebase-3.2.3-1.0.rh90.kde.i386.rpm redhat-menus-1.4.1-1.noarch.rpm

kdebase-devel-3.2.3-1.0.rh90.kde.i386.rpm sip-3.10.2-0.fdr.0.rh90.i386.rpm

kdelibs-3.2.3-1.0.rh90.kde.i386.rpm sip-devel-3.10.2-0.fdr.0.rh90.i386.rpm

kdelibs-devel-3.2.3-1.0.rh90.kde.i386.rpm superkaramba-0.33-0.fdr.1.rh90.i386.rpm

kdenetwork-3.2.3-1.0.rh90.kde.i386.rpm wv2-0.2.1-0.fdr.2.rh90.i386.rpm

 

If you were to drop koffice, you could also skip upgrading ghostscript, imagemagick, aspell, pspell and wv2. keeping koffice proved to be a real bitch :/

 

All these rpms by kde-redhat.org except aspell/pspell by ximian, redhat-* come from fedora afaik.

 

Then your installation should break. ld.so.conf does not get told there are new qt libraries, so add in /usr/lib/qt-3.3/lib and your apps (kdeinit) should find that. after that things are all fine.

a quick reboot will make kdm DoS your cpu. I have no idea why but it does not like new qt libraries.

Jul 14 15:19:17 sa kdm: :0[2692]: Abnormal termination of greeter for display :0, code 127, signal 0

 

weird shit.

 

Post installation rpms:

 

fribidi-0.10.4-0.fdr.0.rh90.i386.rpm kdepim-3.2.3-1.0.rh90.kde.i386.rpm

k3b-0.11.12-0.fdr.0.rh90.i386.rpm kdepim-devel-3.2.3-1.0.rh90.kde.i386.rpm

k3b-mp3-0.11.12-0.fdr.0.rh90.i386.rpm kdeutils-3.2.3-1.0.rh90.kde.i386.rpm

kdeaddons-3.2.3-1.0.rh90.kde.i386.rpm libmal-0.31-0.fdr.1.rh90.i386.rpm

kdegames-3.2.3-1.0.rh90.kde.i386.rpm musicman-0.11-0.fdr.0.rh90.i386.rpm

kdegames-devel-3.2.3-1.0.rh90.kde.i386.rpm scribus-1.1.7-0.fdr.0.rh90.i386.rpm

kdegraphics-3.2.3-1.0.rh90.kde.i386.rpm scribus-devel-1.1.7-0.fdr.0.rh90.i386.rpm

kdegraphics-devel-3.2.3-1.0.rh90.kde.i386.rpm thinkeramik-3.2.1-0.fdr.1.rh90.i386.rpm

 

(all by kde-redhat.org)

 

you should install these as it makes things all pretty. don't forget nuvola icons!!!! a must for kde3.2!!! things to watch out for are kdepim/kmail being buggy pieces of shit (im staying with evolution for now) and all gtk apps look so weird. I haven't upgraded this box to the new mozilla 1.6/galeon that apt has on offer. i like the old galeon 1.2.13

 

I have yet to install kdemultimedia and openoffice.org

they`re conflicting with so much shit and I'm lazy.

 

All in all this effort was a big pain in the ass but it's worth it, because now i can edit python in kdevelop3 !!!!! Smile

anybody else who wants kde3.2 should upgrade to fedora2.

da!!as

]]> <![CDATA[Change KDE Menu Icon]]> https://www.linux-noob.com/forums/thread-3327.html Tue, 08 Jun 2004 15:54:13 +0200 joobie]]> https://www.linux-noob.com/forums/thread-3327.html Hi Guys.

 

How do I go about changing the KDE icon of the Redhat that is on the desktop, which is used to bring up the menu when clicked?

 

I have installed Fedora core 2.. Thanks!

]]> Hi Guys.

 

How do I go about changing the KDE icon of the Redhat that is on the desktop, which is used to bring up the menu when clicked?

 

I have installed Fedora core 2.. Thanks!

]]> <![CDATA[KDE 3.2]]> https://www.linux-noob.com/forums/thread-3552.html Mon, 15 Mar 2004 12:44:33 +0100 theshinydemon]]> https://www.linux-noob.com/forums/thread-3552.html Has anyone tried the new KDE interface yet??

 

what are your thoughts on this??

 

Gnome vs. KDE??

 

Let me know!!!

 

[img]<___base_url___>/uploads/emoticons/default_dry.png[/img]

]]> Has anyone tried the new KDE interface yet??

 

what are your thoughts on this??

 

Gnome vs. KDE??

 

Let me know!!!

 

[img]<___base_url___>/uploads/emoticons/default_dry.png[/img]

]]> <![CDATA[How Do I Upgrade KDE to 3.1]]> https://www.linux-noob.com/forums/thread-3573.html Fri, 05 Mar 2004 23:22:07 +0100 LinuxNewb]]> https://www.linux-noob.com/forums/thread-3573.html Please I am using FedoraCOre 1 and I'd like to update KDE to 3.1

What rpm's to download, how o install them.

Thnx.

Also I Have problems on installing alsa, but when i Upgrade kernel I cant use NVIDIA drivers.

how to sove this ?

]]> Please I am using FedoraCOre 1 and I'd like to update KDE to 3.1

What rpm's to download, how o install them.

Thnx.

Also I Have problems on installing alsa, but when i Upgrade kernel I cant use NVIDIA drivers.

how to sove this ?

]]> <![CDATA[How do I change KDE's startup background color?]]> https://www.linux-noob.com/forums/thread-4054.html Thu, 11 Dec 2003 19:22:24 +0100 P38]]> https://www.linux-noob.com/forums/thread-4054.html When starting kde on my system, (I use startx from the command line), I did not like the way that KDE would startup with a baby blue background and then transition to my configured background color. I wanted a way to make the color consistant from the start of the X server until my default desktop was up.

 

KDE starts with the command "exec startkde" usually found in ~/.Xclients-default or ~/.Xclients. "startkde" is a script that, on my system, is in /usr/kde/3.1/bin/ (your system may be different).

 

Within that script are the following lines:

 

test "$XDM_MANAGED" || bkg="-solid #000000"

xsetroot -cursor_name left_ptr $bkg

 

As you can see, the startkde script uses "xsetroot" to set its initial color. I have mine set to "#000000" which

is black but you can set the color to anything you like. You can use a utility like "gcolor" to pick a color code that you like or you can use the utility here to experiment. [/url][url=http://www.imagitek.com/bcs.html]http://www.imagitek.com/bcs.html

]]> When starting kde on my system, (I use startx from the command line), I did not like the way that KDE would startup with a baby blue background and then transition to my configured background color. I wanted a way to make the color consistant from the start of the X server until my default desktop was up.

 

KDE starts with the command "exec startkde" usually found in ~/.Xclients-default or ~/.Xclients. "startkde" is a script that, on my system, is in /usr/kde/3.1/bin/ (your system may be different).

 

Within that script are the following lines:

 

test "$XDM_MANAGED" || bkg="-solid #000000"

xsetroot -cursor_name left_ptr $bkg

 

As you can see, the startkde script uses "xsetroot" to set its initial color. I have mine set to "#000000" which

is black but you can set the color to anything you like. You can use a utility like "gcolor" to pick a color code that you like or you can use the utility here to experiment. [/url][url=http://www.imagitek.com/bcs.html]http://www.imagitek.com/bcs.html

]]>