Subject: Re: KDE 3.3 upgrade - msg#00161

Previous Message by Date: click to view message preview

Re: KDE 3.3 upgrade

*** Reply to message from Bernard Elbourn <berni@xxxxxxxxxxxxxxxxx> on Fri, 17 Sep 2004 08:57:00 +0100 One more candle and a trip around the Sun*** > 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 -- To unsubscribe, email: suse-kde-unsubscribe@xxxxxxxx For additional commands, email: suse-kde-help@xxxxxxxx Please do not cross-post to suse-linux-e

Next Message by Date: click to view message preview

kontact crashes

Since some time (I think it started around kdelibs-3.3.0 release 8 or so) kontact crashes for me during startup (this is on suse 9.1). I have removed the kontactrc file, but that does not help. No new kontactrc is created. Kontact crashed with the following backtrace Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 4464)] [KCrash handler] #5 0x081a8321 in ?? () #6 0x41820010 in __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__ () from /lib/libc.so.6 #7 0x081773d8 in ?? () #8 0x00000001 in ?? () #9 0x08136550 in ?? () #10 0x081610b0 in ?? () #11 0x41820a00 in __libc_tsd_MALLOC_data () from /lib/libc.so.6 #12 0x081610c0 in ?? () #13 0x416dd450 in __JCR_LIST__ () from /usr/lib/libstdc++.so.5 #14 0x081a5d20 in ?? () #15 0x08171548 in ?? () #16 0xbfffe658 in ?? () #17 0x416bac91 in operator delete () from /usr/lib/libstdc++.so.5 I set all plugin definitions in the (old) kontactrc file to false. It's still crashing. BTW, the mainwindow pops up, but when it is about to fill it, kontact crashes. The seperate apps (knotes, kmail, knode, korganizer) run okay. gdb kontact does not reveal much. What can be wrong?? -- Richard Bos Without a home the journey is endless -- To unsubscribe, email: suse-kde-unsubscribe@xxxxxxxx For additional commands, email: suse-kde-help@xxxxxxxx Please do not cross-post to suse-linux-e

Previous Message by Thread: click to view message preview

Re: KDE 3.3 upgrade

*** Reply to message from Bernard Elbourn <berni@xxxxxxxxxxxxxxxxx> on Fri, 17 Sep 2004 08:57:00 +0100 One more candle and a trip around the Sun*** > 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 -- To unsubscribe, email: suse-kde-unsubscribe@xxxxxxxx For additional commands, email: suse-kde-help@xxxxxxxx Please do not cross-post to suse-linux-e

Next Message by Thread: click to view message preview

Re: KDE 3.3 upgrade

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 -- To unsubscribe, email: suse-kde-unsubscribe@xxxxxxxx For additional commands, email: suse-kde-help@xxxxxxxx Please do not cross-post to suse-linux-e