Bug 62724 - print and open lead to crash
Summary: print and open lead to crash
Status: CLOSED DUPLICATE of bug 51628
Alias: None
Product: kdeprint
Classification: Applications
Component: general (show other bugs)
Version: 3.1.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Goffioul
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-15 17:15 UTC by hughjonesd
Modified: 2008-12-31 13:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hughjonesd 2003-08-15 17:15:31 UTC
Version:           2.1 (using KDE 3.1.3)
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:          Linux (i686) release 2.4.18-4GB

To crash Kate:

1. hit Ctrl+P to open the print dialog
2. hit Ctrl+O to open the open file dialog
3. open a file from the dialog
4. hit "cancel" on the print dialog

Backtrace:
(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)...(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)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP 1025)]

(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)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x40f15099 in wait4 () from /lib/libc.so.6
#0  0x40f15099 in wait4 () from /lib/libc.so.6
#1  0x40f8fbd8 in __DTOR_END__ () from /lib/libc.so.6
#2  0x40dc9072 in waitpid () from /lib/libpthread.so.0
#3  0x40577f8b in KCrash::defaultCrashHandler ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x40dc6a74 in pthread_sighandler () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x408c5029 in QObject::disconnect () from /usr/lib/libqt-mt.so.3
#7  0x40572291 in KAccelPrivate::eventFilter ()
   from /opt/kde3/lib/libkdecore.so.4
#8  0x408c3548 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
#9  0x408c3401 in QObject::event () from /usr/lib/libqt-mt.so.3
#10 0x408efac5 in QWidget::event () from /usr/lib/libqt-mt.so.3
#11 0x4097a3c1 in QMainWindow::event () from /usr/lib/libqt-mt.so.3
#12 0x40879d37 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#13 0x408792a8 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#14 0x4051408b in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#15 0x405714f0 in KAccelEventHandler::x11Event ()
   from /opt/kde3/lib/libkdecore.so.4
#16 0x40517e95 in KApplication::x11EventFilter ()
   from /opt/kde3/lib/libkdecore.so.4
#17 0x408253d9 in qt_set_x11_event_filter () from /usr/lib/libqt-mt.so.3
#18 0x4082ea6c in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#19 0x4083f632 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#20 0x4088a2a0 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#21 0x4088a1e7 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#22 0x40879ea6 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#23 0x4064ad8a in main () from /opt/kde3/lib/kate.so
#24 0x0804d036 in launch ()
#25 0x0804df08 in handle_launcher_request ()
#26 0x0804e425 in handle_requests ()
#27 0x0804f2e7 in main ()
#28 0x40e8a9ed in __libc_start_main () from /lib/libc.so.6

Dave
Comment 1 Christoph Cullmann 2003-08-16 13:50:34 UTC
if that really crashs, can not reproduce, that is a kdeprint problem 
Comment 2 Michael Goffioul 2003-08-18 08:29:20 UTC
Subject: Re:  print and open lead to crash

> ------- Additional Comments From cullmann@kde.org  2003-08-16 13:50 -------
> if that really crashs, can not reproduce, that is a kdeprint problem

Looks more like a accel mess up. I doubt this has something to do
with kdeprint.

Comment 3 Waldo Bastian 2004-02-07 18:52:10 UTC

*** This bug has been marked as a duplicate of 51628 ***
Comment 4 John Layt 2008-12-31 13:15:26 UTC
Closing old Resolved status bug.