KDE 3.0.3. upgrade problems
After installing the KDE upgrade as per http://www.suse.com/us/private/download/linuks/i386/update_for_8_0/index.htm... certain apps crash. For example find files the Crash Handler dump says: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40f05099 in wait4 () from /lib/libc.so.6 #0 0x40f05099 in wait4 () from /lib/libc.so.6 #1 0x40f7fbd8 in __DTOR_END__ () from /lib/libc.so.6 #2 0x40d9a072 in waitpid () from /lib/libpthread.so.0 #3 0x405c1ade in KCrash::defaultCrashHandler () from /opt/kde3/lib/libkdecore.so.4 #4 0x40d97a74 in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x407fb851 in QWidget::checkChildrenDnd () from /usr/lib/libqt-mt.so.3 #7 0x407fb96d in QWidget::setAcceptDrops () from /usr/lib/libqt-mt.so.3 #8 0x4099416e in QTextEdit::init () from /usr/lib/libqt-mt.so.3 #9 0x40993dbd in QTextEdit::QTextEdit () from /usr/lib/libqt-mt.so.3 #10 0x40415a30 in KAboutContainerBase::addLicensePage () from /opt/kde3/lib/libkdeui.so.4 #11 0x40417e85 in KAboutDialog::addLicensePage () from /opt/kde3/lib/libkdeui.so.4 #12 0x404583a1 in KAboutApplication::buildDialog () from /opt/kde3/lib/libkdeui.so.4 #13 0x4045713a in KAboutApplication::KAboutApplication () from /opt/kde3/lib/libkdeui.so.4 #14 0x08055ff3 in QScrollView::mouseReleaseEvent () #15 0x0805698f in QScrollView::mouseReleaseEvent () #16 0x40e7a9ed in __libc_start_main () from /lib/libc.so.6 Similar output is given when some apps like package manager encounter a problem such as a zero result for a search. But the worst of the problem is that Yast2 will not start. The sand clock revolves for a while .......then nothing. I first noticed that Yast2 was sick when I was going to reinstall webcam apps which would not load. i.e. the KDE 303 upgrade did something to the webcam (video) apps. Since Qt3 looks to be involved I installed it again and the option Qt3 stuff , to be sure. But it has not helped. Main apps such as StarOffice, QCad, Mozilla 1.1, Digikam are OK After reading some of the threads in the KDE forum it seems that: Using Package Manager for the KDE upgrade is not safe. Using rpm command line strings is subject to habits (good or bad). It would be really helpful if SuSe had a text that one could cut and past line by line in the correct order to do the upgrade proceedure (gee that's almost a script or some kind of program to automate the process ... i.e. something that YasT should do.) Any suggestions please 1) to stop the crashes 2) procedure to regain "lost" apps like Yast2 3) to do it again but correctly ? thanks, -- John
But the worst of the problem is that Yast2 will not start. The sand clock revolves for a while .......then nothing.
I first noticed that Yast2 was sick when I was going to reinstall webcam apps which would not load. i.e. the KDE 303 upgrade did something to the webcam (video) apps.
Hi John! This is happening to me, too. It started while updating to kde 3.0.2, with yast2... There is an article on this problem at suse's site. http://sdb.suse.de/en/sdb/html/yast2_kde_controlcenter.html This doesn't work for me, however. In any case, you can open a console as root, and type yast2. Then yast is working though in text mode. Pere
Hi Pere, Thanks for the advice. I have recovered by using rpm from the command line. The KDE 303 packages had been downloaded. From a console do a cd to this directory. use the command rpm -Uvh <filename>.rpm --force then SuSEconfig and so on --force is necessary since rpm will report that the package is already installed. We can assume that the Package Manager did not install correctly or SuSEconfig should have been used. work your way through Qt arts kdelibs kdebase and the rest At some point Yast2 will start if you try it. So I have Yast2 back in working order. KDE 3.0.3 is reported by the KDE Control Centre. All is not quite right yet. I am still having trouble with the aRTs and getting RealPlayer to actually play. -- John Pere Constans wrote:
But the worst of the problem is that Yast2 will not start. The sand clock revolves for a while .......then nothing.
I first noticed that Yast2 was sick when I was going to reinstall webcam apps which would not load. i.e. the KDE 303 upgrade did something to the webcam (video) apps.
Hi John! This is happening to me, too. It started while updating to kde 3.0.2, with yast2... There is an article on this problem at suse's site. http://sdb.suse.de/en/sdb/html/yast2_kde_controlcenter.html This doesn't work for me, however. In any case, you can open a console as root, and type yast2. Then yast is working though in text mode.
Pere
participants (2)
-
John Sved -
Pere Constans