Hi, I have been following the recent posts about upgrading to KDE 3.3. Most of them have been about upgrading SUSE 9.x. I am running SUSE 8.2 and I am very happy with it, but I would like to upgrade to KDE 3.3. Before I do I was just wondering if anyone here has upgraded to KDE 3.3 on their SUSE 8.2 system, and if so did you encounter any problems or difficulties? Many thanks, Ben. _____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Tuesday 07 September 2004 07:48, Ben Hills wrote:
do I was just wondering if anyone here has upgraded to KDE 3.3 on their SUSE 8.2 system, and if so did you encounter any problems or difficulties?
Worked a treat using yast. Lots of obsoletes to take care of. Sadly I haven't kept a record....lots were about pim and the base SUSE extentions. Backup first! Berni
El Mar 07 Sep 2004 01:48, Ben Hills escribió:
Hi,
I have been following the recent posts about upgrading to KDE 3.3. Most of them have been about upgrading SUSE 9.x. I am running SUSE 8.2 and I am very happy with it, but I would like to upgrade to KDE 3.3. Before I do I was just wondering if anyone here has upgraded to KDE 3.3 on their SUSE 8.2 system, and if so did you encounter any problems or difficulties?
Ben, I am running SuSE 8.2 and I am just as happy as you are. I recently updated to KDE 3.3, using the rpm packages provided by SuSE on their website. All in all it was painless, I just encountered two problems: I am running a jabber server and noticed that after the update Kopete wouldn't support anymore the Jabber protocol. The plugin was missing from kdenetwork3-InstantMessenger.rpm, bus has in the meantime been updated by SuSE. The other problem I have experienced has to do with an apparently mispackaged rpm file as well; after the update I wasn't able anymore to connect from within Konqueror to Samba shares of Windows machines on our network. The culprit this time is kdebase3-samba, which misses the kio_smb library. This package has not been updated yet by SuSE. Other than that, all is fine and I love the many new features. -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia
Andreas Philipp a écrit :
El Mar 07 Sep 2004 01:48, Ben Hills escribió:
Hi,
I have been following the recent posts about upgrading to KDE 3.3. Most of them have been about upgrading SUSE 9.x. I am running SUSE 8.2 and I am very happy with it, but I would like to upgrade to KDE 3.3. Before I do I was just wondering if anyone here has upgraded to KDE 3.3 on their SUSE 8.2 system, and if so did you encounter any problems or difficulties?
I find everything nice, except that the screensavers don't work anymore. Robert
http://lists.suse.com/archive/suse-kde/2004-Aug/0136.html This should help you. Have fun! Daniel Am Donnerstag, 9. September 2004 21:14 schrieb Bob:
Andreas Philipp a écrit :
El Mar 07 Sep 2004 01:48, Ben Hills escribió:
Hi,
I have been following the recent posts about upgrading to KDE 3.3. Most of them have been about upgrading SUSE 9.x. I am running SUSE 8.2 and I am very happy with it, but I would like to upgrade to KDE 3.3. Before I do I was just wondering if anyone here has upgraded to KDE 3.3 on their SUSE 8.2 system, and if so did you encounter any problems or difficulties?
I find everything nice, except that the screensavers don't work anymore.
Robert
Daniel Eckl a écrit :
http://lists.suse.com/archive/suse-kde/2004-Aug/0136.html
This should help you.
Have fun! Excellent. Many thanks. Robert
Bob, On Thursday 09 September 2004 12:14, Bob wrote:
Andreas Philipp a écrit :
El Mar 07 Sep 2004 01:48, Ben Hills escribió:
Hi,
... and if so did you encounter any problems or difficulties?
I find everything nice, except that the screensavers don't work anymore.
Look in the SuSE-KDE mailing list archives for August (
Robert
Randall Schulz
On Thursday 09 Sep 2004 18:33, Andreas Philipp wrote:
I am running a jabber server and noticed that after the update Kopete wouldn't support anymore the Jabber protocol. The plugin was missing from kdenetwork3-InstantMessenger.rpm, bus has in the meantime been updated by SuSE.
So you have Jabber back in kopete? I updated to the latest supplementary packages today but still do not have the Jabber plugin for kopete. I am using SuSE 9.0 however. -- Colin Pinkney http://www.cpinkney.org.uk
El Jue 09 Sep 2004 15:36, Colin Pinkney escribió:
So you have Jabber back in kopete? I updated to the latest supplementary packages today but still do not have the Jabber plugin for kopete. I am using SuSE 9.0 however.
Yes, Kopete connects now happily to my Jabber server. I first compiled the kdenetwork-3.3.0 tarball from kde.org whih resolved the problem. When SuSE updated around September 2 (?) the rpm, I updated the previously installed package to the new version 3.3.0-12. -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia
On Thursday 09 Sep 2004 22:50, Andreas Philipp wrote:
El Jue 09 Sep 2004 15:36, Colin Pinkney escribió:
So you have Jabber back in kopete? I updated to the latest supplementary packages today but still do not have the Jabber plugin for kopete. I am using SuSE 9.0 however.
Yes, Kopete connects now happily to my Jabber server. I first compiled the kdenetwork-3.3.0 tarball from kde.org whih resolved the problem. When SuSE updated around September 2 (?) the rpm, I updated the previously installed package to the new version 3.3.0-12.
Strange. I looked at the SuSE 8.2 kdenetwork3-InstantMessenger rpm and the latest version is now 3.3.0-15, but that doesn't have the jabber plugin in it (neither does the latest 9.0 rpm). So I looked at the SuSE 9.1 rpm, which is at version 3.3.0-16 and that had it in. I extracted and manually installed all the jabber stuff using cpio and found out it also requires the SuSE 9.1 version of libidn, so I downloaded that and installed as normal. Now Jabber seems to work with my SuSE 9.0 system and kopete, yay :) -- Colin Pinkney http://www.cpinkney.org.uk
El Vie 10 Sep 2004 17:06, Colin Pinkney escribió:
Strange. I looked at the SuSE 8.2 kdenetwork3-InstantMessenger rpm and the latest version is now 3.3.0-15, but that doesn't have the jabber plugin in it (neither does the latest 9.0 rpm). So I looked at the SuSE 9.1 rpm, which is at version 3.3.0-16 and that had it in. I extracted and manually installed all the jabber stuff using cpio and found out it also requires the SuSE 9.1 version of libidn, so I downloaded that and installed as normal. Now Jabber seems to work with my SuSE 9.0 system and kopete, yay :)
You are right, neither the latest version of the kdenetwork3-InstantMessenger rpm nor the one I used for my update contain the jabber plugin. So that I am able to connect with Kopete to my jabber server is because I have compiled the kdenetwork-3.3.0 tarball and installed it from there. SuSE apparently still has not fixed this issue. -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia
Another observation.....The support for device icons is not installed by the recent suse 8.2 kde 3.3 rpms through yast. The problem is immediately apparent at login which ioslave crashing out not recognising "devices"...installing kdebase3-extra seems to resolve. Berni
Hi, Thanks for all the replies about upgrading to KDE 3.3 on SUSE 8.2. I have downloaded all of the packages and burnt them on to CD and I have managed to resolve all the dependency problems - except one. YaST says that there is a conflict with kdebase3-SuSE. From what I have managed to find out most people simply remove this package to resolve the conflict. This seems to ben the easiest solution but what functionality does the kdebase3-SuSE package provide? Am I going to lose anything useful? Many thanks, Ben. _____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
Suse window manager and icons and most importantly YOU (you will have to remember to check for updates periodically yourself. There may be other things but these are the things I noticed. You could extract some of the files from the rpm and install yourself. Andrew On Thursday 16 September 2004 08:09, Ben Hills wrote:
Hi,
Thanks for all the replies about upgrading to KDE 3.3 on SUSE 8.2. I have downloaded all of the packages and burnt them on to CD and I have managed to resolve all the dependency problems - except one. YaST says that there is a conflict with kdebase3-SuSE. From what I have managed to find out most people simply remove this package to resolve the conflict. This seems to ben the easiest solution but what functionality does the kdebase3-SuSE package provide? Am I going to lose anything useful?
Many thanks,
Ben.
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
-- Andrew Colvin apc@abcj.demon.co.uk ICQ: 44775817 Jabber: acolvin@jabber.com MSN: apc@abcj.demon.co.uk -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) mQGiBD8FKdkRBADo7ANPdaMNYIlihjYh5oBld3ShWLTVqfQVjz5+twZgo7T5FlCy OSscQaC12NiYixanlZqZrXJs7/fQGAKAZ/CFZvZCTufHLuO5IXVOyRZAWNu7QbcN kWc8m0UilZDSKSb+AxXCnMpW/iEyQ0l8Zv6PKKRrC9Ok/zX9dszCSYakdwCgpKHY MI10jbBAD8cGMWIHGGj4egUD/0f2AWy8Ko02nW3zYLjV6qFkYGLc524qX/XhLhBo m4mhba5SWZl3P7CWs91ZkBTjgdz/XHUA5nCoFCQWTxuTL1UUx9dSHnCkPn4JQRTe /jWO1aOD+HBJYWV1w1r2EfDJE/Fmnukb+tgc3D2ZBROFvQSN9fCYt29aINkVyz0A BXj3A/4xwIAT+PfyiSkn6wheSUdhvXusQ4pZuETu+dbCNpvKWvR7p45KdJQ6DsRV mgWnVQZSxxPBBJIpXl/2JGI9F37VLnA4ATx8qauntHfDL11wjLCAIVab6x+0+ZeM s69xywtWOTiaTU0Rjh8IeNDDvb3hv/3EWCmfyQXvbDlLgRcS8LQkQW5kcmV3IENv bHZpbiA8YXBjQGFiY2ouZGVtb24uY28udWs+iFkEExECABkFAj8FKdkECwcDAgMV AgMDFgIBAh4BAheAAAoJEP9j3GM12XCdoWMAn1byxQyJH+Rxtcjd6ZEyS1gCAHWC AJ9GI9ZtwL/m703mg9T4hh+CajwZirkCDQQ/BSnsEAgAuBM0PxJdK1vKrHg1inEJ 83+e0oQPWLhTnvV3wT34OGkj/Krzexo9cOUHM5BteidQY6ovhH3AKjmkF0aNXaay xpsVrtXYpqEWgqeZagRvuLw5+mj/X9+S0LS458bFmwpkkqZ+5QOhoLjNGeYutHqJ orINQsU/74NLfgKbGd94uP82t1kPTgF+oAuVUCidqVN0eubQ4OdxZ+ySxxCRU4GU vbUVxo/CfnG0PazXeWOIqBrq+WkuHF/C6OoBGyi67UXq5FjhR8hrmr4OuDBXuU0Z mb08CuLi0nTxXrbwrmH0G9SzXBMxMBRep9qnGdILVWeACeIz9sVBj+dwJHyTpgM2 7wAEDQf/QXSyLsrX9pufdGSJqKS6+sMouMeJo+fnkX2VXUFLLDX7KdwmHO4liISb BleT3m69w/WwVwN286kW7wlMVXD7cLFCLC3SVXLHaVVkArGt/9uY6g3gZ53FaqNv NvumuYLpqH6iAicP9rIVrA69ztTwtmbqcHA+P6juoO3tJohJEiQhlrmH0Tmp+BSq XMyBUb5SJJOeRArPb1FNF9Q96iOk45EIRPp4riiaBptOFe95jJBiWBBfLIuQDMQ8 PA6gVw+u9kMUbKjA30yj4vL43lFyQPUwSiT0okgq0/TXMzyO568UFhYTeT/DV8Lq 5evvNwRmRpjfJHwekUyD4MHVkEr5BohGBBgRAgAGBQI/BSnsAAoJEP9j3GM12XCd KWAAoJIN9wx51sDaCHdY49MnNNFxZ7imAJsEi4G5d9LOIBne++TrHCFMjWzcwA== =AFMd -----END PGP PUBLIC KEY BLOCK-----
* Andrew Colvin
Suse window manager and icons and most importantly YOU (you will have to remember to check for updates periodically yourself.
There may be other things but these are the things I noticed. You could extract some of the files from the rpm and install yourself.
Just reinstall kdebase3-SuSE with '--force' after you have finished the upgrade to 3.3. No ill effects are apparent or have been reported. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Hi,
Just reinstall kdebase3-SuSE with '--force' after you have finished the upgrade to 3.3. No ill effects are apparent or have been reported.
Thanks very much. I will do just that. Ben. _____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
Hello all,
Can anyone give me an idea what files and subdirectories found in /tmp are
necessary? Maybe even an idea what some are for?
For example:
/tmp/gpg-
On Thursday 16 September 2004 03:26 pm, cms wrote:
Hello all,
Can anyone give me an idea what files and subdirectories found in /tmp are necessary? Maybe even an idea what some are for? For example: /tmp/gpg-
I have six of these gpg subdirectories within /tmp . Each contains a single file called S.gpg-agent, identified as a socket, zero bytes. Are these necessary? What are they for? I have six subdirectories that each begins with ssh, such as ssh-dDwubb4505 and ssh-gqo1014839. Are these necessary? What are they for?
I also have a variety of other files, each zero bytes, that begin with ssh, such as such as gs_IGTUs1 and gs_9UgcT5. What are these files for?
If it matters I'm running SuSE 9.1 pro.
TIA
Chris/CMS
They are exactly as they sound Chris, temp files stored in the /tmp directory for the system. Even those directories located there are temporary used at some time by the system. It is a good idea every once in a while to clean out the /tmp directory to keep problems from showing, especially when one updates all of their KDE files to newer versions. Don't remove the /tmp directory as it has special settings, but anything within is fair game! :o) Be sure to restart KDE if you should remove everything while in KDE because you will suddenly find things not working! Programs will not work because it's temp files were deleted. It's usually best to drop down to "init 1" , remove the files then log back to "init 5". Your command would be: rm -rf /tmp/* (do not forget the asterick!!!) Regards, Lee -- --- KMail v1.7 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 Those Who Dance Are Considered Insane, by Those Who Cannot Hear the Music!
* cms
Can anyone give me an idea what files and subdirectories found in /tmp are necessary? Maybe even an idea what some are for? For example: /tmp/gpg-
I have six of these gpg subdirectories within /tmp . Each contains a single file called S.gpg-agent, identified as a socket, zero bytes. Are these necessary? What are they for?
Hi Chris, If it is space that concerns you, there is a cron setting available in yast2 that will clean the contents of /tmp on system boot. yast2 -> Editor for /etc/sysconfig files -> System -> Cron -> CLEAR_TMP_DIRS_AT_BOOTUP I have, usually when updating kde system files, dropped to runlevel 1 and deleted the entire contents of /tmp before returning to runlevel 5. Everything in /tmp necessary for the system will be recreated. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Thursday 16 September 2004 16:42, Patrick Shanahan wrote:
Hi Chris,
If it is space that concerns you, there is a cron setting available in yast2 that will clean the contents of /tmp on system boot.
yast2 -> Editor for /etc/sysconfig files -> System -> Cron -> CLEAR_TMP_DIRS_AT_BOOTUP
I have, usually when updating kde system files, dropped to runlevel 1 and deleted the entire contents of /tmp before returning to runlevel 5.
Everything in /tmp necessary for the system will be recreated. ---snip---
Actually, that was going to be my next question; whether or not the temp files necessary for the system to function properly, such as the kde temp files, would be recreated if I cleaned the /tmp directory. Thank you. BandiPat--Thank you as well, for your explanation. Chris/CMS
On Thursday September 16 2004 7:07 pm, cms wrote:
On Thursday 16 September 2004 16:42, Patrick Shanahan wrote:
Hi Chris,
If it is space that concerns you, there is a cron setting available in yast2 that will clean the contents of /tmp on system boot.
yast2 -> Editor for /etc/sysconfig files -> System -> Cron -> CLEAR_TMP_DIRS_AT_BOOTUP
I have, usually when updating kde system files, dropped to runlevel 1 and deleted the entire contents of /tmp before returning to runlevel 5.
Everything in /tmp necessary for the system will be recreated.
---snip---
Actually, that was going to be my next question; whether or not the temp files necessary for the system to function properly, such as the kde temp files, would be recreated if I cleaned the /tmp directory.
'Works great! Fred -- "Running Windows on a Pentium is like getting a Porsche but only being able to drive it in reverse with the handbrake on."
On Friday 17 September 2004 01:07, cms wrote:
On Thursday 16 September 2004 16:42, Patrick Shanahan wrote:
Hi Chris,
If it is space that concerns you, there is a cron setting available in yast2 that will clean the contents of /tmp on system boot.
yast2 -> Editor for /etc/sysconfig files -> System -> Cron -> CLEAR_TMP_DIRS_AT_BOOTUP
I have, usually when updating kde system files, dropped to runlevel 1 and deleted the entire contents of /tmp before returning to runlevel 5.
Everything in /tmp necessary for the system will be recreated.
---snip---
Actually, that was going to be my next question; whether or not the temp files necessary for the system to function properly, such as the kde temp files, would be recreated if I cleaned the /tmp directory.
Dive into the FSH (File System Hierarchy) if you really want to know. IIAIC, /tmp is for temporary files that do not have to survive a reboot /var/tmp is for temporary files that do have to survive a reboot Cheers, Leen
HI! Patrick Shanahan wrote:
Suse window manager and icons and most importantly YOU (you will have to remember to check for updates periodically yourself.
There may be other things but these are the things I noticed. You could extract some of the files from the rpm and install yourself.
Just reinstall kdebase3-SuSE with '--force' after you have finished the upgrade to 3.3. No ill effects are apparent or have been reported.
Unfortunately, there is one issue with displaying HTML pages in Konqueror. When I use the original kdebase3-SuSE with Suse 9.0/KDE 3.3, this crashes Konqueror, because of the krpmview plugin. There is a special kdebase3-SuSE RPM, that does not have dependency issues (you don't need --force) and that does not contain the offending krpmview plugin: ftp://packman.iu-bremen.de/testing/SuSE_8.2_kde_3.3_missing/rpm/ ftp://packman.iu-bremen.de/testing/SuSE_9.0_kde_3.3_missing/rpm/ Thomas
On Friday 17 September 2004 07:34, Thomas Börkel wrote: snip
There is a special kdebase3-SuSE RPM, that does not have dependency issues (you don't need --force) and that does not contain the offending krpmview plugin:
ftp://packman.iu-bremen.de/testing/SuSE_8.2_kde_3.3_missing/rpm/ ftp://packman.iu-bremen.de/testing/SuSE_9.0_kde_3.3_missing/rpm/
Thomas
What is the background to these rpm's please. The 8.2s seem to be named for 9.0. I chose to remove kbebase3-SUSE (along with other obsoletes) to install Suse's update 8.2 KDE3.3 cleanly. Once tested, then I installed the kdebase3-SUSE from the original 8.2 using yast ignore inconsistencies. I did have to acknowlege once of errors which winged about devices and had to clear /tmp. Rmp viewing seems ok. I have YOU working too. One has to wonder what testing Suse did before releasing the kde 3.3 updates...ho hum. Berni
One has to wonder what testing Suse did before releasing the kde 3.3 updates...ho hum.
YOU has just delivered a new kdebase-SUSE to my 8.2 system... Maybe the answere is to just run YOU after upgrading KDE and forcing kdebase3? It would be nice to know for sure. Berni
*** Reply to message from Bernard Elbourn
Maybe the answere is to just run YOU after upgrading KDE and forcing kdebase3?
My understanding is to run your Online update to make sure it installs updates to qt and about a dozen other items... needed to be done BEFORE you attempt to install the new KDE kdebase3 Whomever is working on YAST, especially the online update section, DOWNLEVELING shouldn't be the only choice when there is a list of things, which often will include the missing whatever at the end of the collection of files to be installed via rpm. There was a time when one downloaded the whole pile of rpms to a directory and then ran the rpm - uhvF foo.rpm and the rpms sorted themselves and the correct order in which they needed to be installed. You guys are doing such a great job, I hate to complain about something so silly, but generally that commandline install via rpm worked out very well. It was how I managed to get my first Nvidia updates installed, and later my first "all by myself" upgrade of KDE. (I'm still trying to get krecipies to work.. but I keep messing up something) AND just now, it will have to wait while important things happen. Important things for the company anyway <VBG> -- j -- nemo me impune lacessit
On Saturday 18 September 2004 10:59, jfweber@bellsouth.net wrote:
My understanding is to run your Online update to make sure it installs updates to qt and about a dozen other items... needed to be done BEFORE you attempt to install the new KDE kdebase3
Sound sensible. Actually, I started with an up to date system via YOU. Then installed kde3.3 for suse 8.2 update cleanly with kdebase3-SUSE removed. Then forced kdebase3-SUSE. Then just by chance I did my normal YOU this week which updated the kdebase3-SUSE. I suspect the lack of the right kdebase3-SUSE in the update was a simple oversight? But sadly it is such an obvious dependancy one would indicate that Suse are not testing their prior version upgrades at all. While I do not wish to critisize one of the best euro suppliers too much .... thing kind of thing (which is easily prevented) will loose them market share. Hopefully our feedback will help it to be fixed on the mirrors so others can enjoy a smoother upgrade. Berni
HI! Bernard Elbourn wrote:
There is a special kdebase3-SuSE RPM, that does not have dependency issues (you don't need --force) and that does not contain the offending krpmview plugin:
ftp://packman.iu-bremen.de/testing/SuSE_8.2_kde_3.3_missing/rpm/ ftp://packman.iu-bremen.de/testing/SuSE_9.0_kde_3.3_missing/rpm/
Thomas
What is the background to these rpm's please. The 8.2s seem to be named for 9.0.
No, don't be confused by the name.
One has to wonder what testing Suse did before releasing the kde 3.3 updates...ho hum.
These updates are unsupported by Suse AFAIK. Thomas
participants (15)
-
Andreas Philipp -
Andrew Colvin -
BandiPat -
Ben Hills -
Bernard Elbourn -
Bob -
cms -
Colin Pinkney -
Daniel Eckl -
Fred Miller -
jfweber＠bellsouth.net -
Leendert Meyer -
Patrick Shanahan -
Randall R Schulz -
Thomas Börkel