HelloSuSE people Recently upgraded to KDE 3.1.3 K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received. I cannot nake any sense of it. Maybe some kind soul on this list can? and tell me what to do? (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 3985)] 0x416eccf7 in waitpid () from /lib/libpthread.so.0 #0 0x416eccf7 in waitpid () from /lib/libpthread.so.0 #1 0x40c4fad9 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x416eb895 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x40ff0135 in QPtrList<QBoxLayoutItem>::deleteItem(void*) () from /usr/lib/libqt-mt.so.3 #5 0x413124de in QGList::clear() () from /usr/lib/libqt-mt.so.3 #6 0x40feca17 in QBoxLayout::~QBoxLayout() () from /usr/lib/libqt-mt.so.3 #7 0x40fef4cb in QVBoxLayout::~QVBoxLayout() () from /usr/lib/libqt-mt.so.3 #8 0x410d9bfa in QGroupBox::setColumnLayout(int, Qt::Orientation) () from /usr/lib/libqt-mt.so.3 #9 0x410d9b14 in QGroupBox::setInsideMargin(int) () from /usr/lib/libqt-mt.so.3 #10 0x08099fc4 in K3bProjectBurnDialog::prepareGui() () #11 0x080ee100 in K3bDataBurnDialog::K3bDataBurnDialog(K3bDataDoc*, QWidget*, char const*, bool) () #12 0x080cec55 in K3bDataView::burnDialog(bool) () #13 0x080a75ca in K3bMainWindow::slotFileBurn() () #14 0x080a87ce in K3bMainWindow::qt_invoke(int, QUObject*) () #15 0x4100acec in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #16 0x4100aa8c in QObject::activate_signal(int) () from /usr/lib/libqt-mt.so.3 #17 0x409fba99 in KAction::activated() () from /opt/kde3/lib/libkdeui.so.4 #18 0x409ec58d in KAction::slotActivated() () from /opt/kde3/lib/libkdeui.so.4 #19 0x409fbb51 in KAction::qt_invoke(int, QUObject*) () from /opt/kde3/lib/libkdeui.so.4 #20 0x4100ac3b in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #21 0x4100aa8c in QObject::activate_signal(int) () from /usr/lib/libqt-mt.so.3 #22 0x413a6b2c in QButton::clicked() () from /usr/lib/libqt-mt.so.3 #23 0x410b5e22 in QButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libqt-mt.so.3 #24 0x41048ad4 in QWidget::event(QEvent*) () from /usr/lib/libqt-mt.so.3 #25 0x40fa329f in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #26 0x40fa273d in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #27 0x40bdac19 in KApplication::notify(QObject*, QEvent*) () from /opt/kde3/lib/libkdecore.so.4 #28 0x40f2f0f0 in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/lib/libqt-mt.so.3 #29 0x40f2c5d5 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libqt-mt.so.3 #30 0x40f43b0c in QEventLoop::processEvents(unsigned) () from /usr/lib/libqt-mt.so.3 #31 0x40fb9ab3 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3 #32 0x40fb99a6 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3 #33 0x40fa351f in QApplication::exec() () from /usr/lib/libqt-mt.so.3 #34 0x080a90d7 in main () #35 0x4184f8ae in __libc_start_main () from /lib/libc.so.6 Thanks in advance Bob S.
Do you have nautilus 2.0 installed? CWSIV On Fri, 19 Sep 2003 03:30:03 -0400 "Bob S." <usr@sanctum.com> writes:
HelloSuSE people
Recently upgraded to KDE 3.1.3
K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received. I cannot nake any sense of it. Maybe some kind soul on this list can? and tell me what to do?
(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 3985)] 0x416eccf7 in waitpid () from /lib/libpthread.so.0 #0 0x416eccf7 in waitpid () from /lib/libpthread.so.0
________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
On Saturday 20 September 2003 00:46, Carl William Spitzer IV wrote:
Do you have nautilus 2.0 installed?
Hello Carl, thanks for responding. No, I do not have Nautilus installed
On Fri, 19 Sep 2003 03:30:03 -0400 "Bob S." <usr@sanctum.com> writes:
HelloSuSE people
Recently upgraded to KDE 3.1.3
K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received. I cannot nake any sense of it. Maybe some kind soul on this list can? and tell me what to do?
(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 3985)] 0x416eccf7 in waitpid () from /lib/libpthread.so.0 #0 0x416eccf7 in waitpid () from /lib/libpthread.so.0
Bob S.
On Friday 19 September 2003 03:30 am, Bob S. wrote:
HelloSuSE people
Recently upgraded to KDE 3.1.3
K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received. I cannot nake any sense of it. Maybe some kind soul on this list can? and tell me what to do?
Have you tried running the setup program again? You also might want to try to nuke/rename two k3b config files (k3brc & k3bsetuprc) in ~/.kde/share/config/ and see what happens. hth -- I always lie. In fact, I'm lying to you right now! ---------------------------------------------------------------- SuSE 8.2 - KDE 3.1.3
On Sunday 21 September 2003 00:40, columbo wrote:
On Friday 19 September 2003 03:30 am, Bob S. wrote:
HelloSuSE people
Recently upgraded to KDE 3.1.3
K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received. I cannot nake any sense of it. Maybe some kind soul on this list can? and tell me what to do?
Have you tried running the setup program again? You also might want to try to nuke/rename two k3b config files (k3brc & k3bsetuprc) in ~/.kde/share/config/ and see what happens.
Thanks for replying/trying to help. Yes, I have probably run the setup program a dozen times. Tried your tip about deleting the two files. Nothing, no change. If I try to copy a CD or try to write files from the HD, it immediately crashes. I can do it from the command line OK So I just removed k3b, downloaded and installed it again. Same crap. A little rant please because I am getting so frustrated. Seems as though everytime you try to do something with KDE you break something else. I am really getting tired of this. It's not only this K3b thing, it is lots and lots of little annoying things, like teeny teeny fonts in the Mozilla dialogs, like right clinking on a file in Konqueror and being immediately bumped up to the parent directory, and why sometimes a terminal will open a program and sometimes not by announcing no such file or directory, and on and on. Thanks for letting me vent. I don't suppose anyone else has any ideas why this stupidness is happening. Bob S.
What version of qt do you have installed? rpm -qa | grep qt I am using qt3-3.1.1-62 and I have no problems I had to downgrade my version of qt3 in order to solve just such a problem.
Recently upgraded to KDE 3.1.3
K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received. I cannot nake
On Tuesday 23 September 2003 16:39, James PEARSON wrote:
What version of qt do you have installed?
rpm -qa | grep qt
I am using qt3-3.1.1-62 and I have no problems
I had to downgrade my version of qt3 in order to solve just such a problem.
Hello James, qt3-non-mt-3.2.0b1-6 qt3-3.2.0b1-6 yast2-qt-2.7.18-41 qt3-devel-3.2.0b1-6
Recently upgraded to KDE 3.1.3
K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received.
Ummmmmm......James, I hope not. What a pain that will be. JS Tried that. Blew away my version and completely reinstalled the new one. No change. Thanks for replying. CWSIV .... Do all of my updates with apt-get since I don't have a T1 line. Download everything for several nights running. Then when it is all together I update everything. Probably my system is as up-to-date as any system out here. Appreciate your words of advice though. OK SuSE people, any other ideas ??? As stated I can burn from the command line. Why is this stupid thing crash when I click on "Burn" of "Copy CD" ? Please don't tell me I have to downgrade QT. Here is the output of the trace after the sigserv: Just in case somebody new picks this up and reads it. I cannot make heads or tails of it. Wish I could :-( (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 3985)] 0x416eccf7 in waitpid () from /lib/libpthread.so.0 #0 0x416eccf7 in waitpid () from /lib/libpthread.so.0 #1 0x40c4fad9 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x416eb895 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x40ff0135 in QPtrList<QBoxLayoutItem>::deleteItem(void*) () from /usr/lib/libqt-mt.so.3 #5 0x413124de in QGList::clear() () from /usr/lib/libqt-mt.so.3 #6 0x40feca17 in QBoxLayout::~QBoxLayout() () from /usr/lib/libqt-mt.so.3 #7 0x40fef4cb in QVBoxLayout::~QVBoxLayout() () from /usr/lib/libqt-mt.so.3 #8 0x410d9bfa in QGroupBox::setColumnLayout(int, Qt::Orientation) () from /usr/lib/libqt-mt.so.3 #9 0x410d9b14 in QGroupBox::setInsideMargin(int) () from /usr/lib/libqt-mt.so.3 #10 0x08099fc4 in K3bProjectBurnDialog::prepareGui() () #11 0x080ee100 in K3bDataBurnDialog::K3bDataBurnDialog(K3bDataDoc*, QWidget*, char const*, bool) () #12 0x080cec55 in K3bDataView::burnDialog(bool) () #13 0x080a75ca in K3bMainWindow::slotFileBurn() () #14 0x080a87ce in K3bMainWindow::qt_invoke(int, QUObject*) () #15 0x4100acec in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #16 0x4100aa8c in QObject::activate_signal(int) () from /usr/lib/libqt-mt.so.3 #17 0x409fba99 in KAction::activated() () from /opt/kde3/lib/libkdeui.so.4 #18 0x409ec58d in KAction::slotActivated() () from /opt/kde3/lib/libkdeui.so.4 #19 0x409fbb51 in KAction::qt_invoke(int, QUObject*) () from /opt/kde3/lib/libkdeui.so.4 #20 0x4100ac3b in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #21 0x4100aa8c in QObject::activate_signal(int) () from /usr/lib/libqt-mt.so.3 #22 0x413a6b2c in QButton::clicked() () from /usr/lib/libqt-mt.so.3 #23 0x410b5e22 in QButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libqt-mt.so.3 #24 0x41048ad4 in QWidget::event(QEvent*) () from /usr/lib/libqt-mt.so.3 #25 0x40fa329f in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #26 0x40fa273d in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #27 0x40bdac19 in KApplication::notify(QObject*, QEvent*) () from /opt/kde3/lib/libkdecore.so.4 #28 0x40f2f0f0 in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/lib/libqt-mt.so.3 #29 0x40f2c5d5 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libqt-mt.so.3 #30 0x40f43b0c in QEventLoop::processEvents(unsigned) () from /usr/lib/libqt-mt.so.3 #31 0x40fb9ab3 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3 #32 0x40fb99a6 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3 #33 0x40fa351f in QApplication::exec() () from /usr/lib/libqt-mt.so.3 #34 0x080a90d7 in main () #35 0x4184f8ae in __libc_start_main () from /lib/libc.so.6 Bob S.
On Wed, 2003-09-24 at 07:26, Bob S. wrote:
On Tuesday 23 September 2003 16:39, James PEARSON wrote:>
I am using qt3-3.1.1-62 and I have no problems
I had to downgrade my version of qt3 in order to solve just such a problem.
Hello James,
qt3-non-mt-3.2.0b1-6 qt3-3.2.0b1-6 yast2-qt-2.7.18-41 qt3-devel-3.2.0b1-6
I maintain that if you downgrade qt3-non-mt-3.2.0b1-6 qt3-3.2.0b1-6 qt3-devel-3.2.0b1-6 to the versions that you have on your SuSE cd roms that k3b will work. K3b v10 works with qt3.2 the versions previous 8.? and 9 don't. I solved a similar problem by downgrading. The choice is yours. @+ James
On Wednesday 24 September 2003 02:22, you wrote:
On Wed, 2003-09-24 at 07:26, Bob S. wrote:
On Tuesday 23 September 2003 16:39, James PEARSON wrote:>
I am using qt3-3.1.1-62 and I have no problems
I had to downgrade my version of qt3 in order to solve just such a problem.
Hello James,
qt3-non-mt-3.2.0b1-6 qt3-3.2.0b1-6 yast2-qt-2.7.18-41 qt3-devel-3.2.0b1-6
I maintain that if you downgrade qt3-non-mt-3.2.0b1-6 qt3-3.2.0b1-6 qt3-devel-3.2.0b1-6 to the versions that you have on your SuSE cd roms that k3b will work.
James, I have absolutely no doubt that you are correct. I am kind of anal about downgrading after all of the time and trouble of upgrading. I solved the problem by upgrading again, to KDE 3.1.4 and qt3-3.2.1-35 k3b works just fine now. ( I was just hoping that somewhere along the way someone caught that problem and got lucky I guess) Thanks for you and all others who responded. Your interest.is appreciated. Bob S.
Bob S. wrote:
On Sunday 21 September 2003 00:40, columbo wrote:
On Friday 19 September 2003 03:30 am, Bob S. wrote:
HelloSuSE people
Recently upgraded to KDE 3.1.3
K3b crashes (KDE sigserve) now when I try to burn a data CD. Used to work OK. Following is the error that I received. I cannot nake any sense of it. Maybe some kind soul on this list can? and tell me what to do?
Have you tried running the setup program again? You also might want to try to nuke/rename two k3b config files (k3brc & k3bsetuprc) in ~/.kde/share/config/ and see what happens.
Thanks for replying/trying to help. Yes, I have probably run the setup program a dozen times. Tried your tip about deleting the two files. Nothing, no change. If I try to copy a CD or try to write files from the HD, it immediately crashes. I can do it from the command line OK
Bob S.
You might try deleting the program directory or settings files. Then you can try a newer version which you can download at: http://packman.links2linux.org/?action=219 John S.
participants (5)
-
Bob S. -
Carl William Spitzer IV -
columbo -
James PEARSON -
js