Application that crashed: konqueror Version of the application: 4.3.2 (KDE 4.3.2) KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Running on older Dell Optiplex GX270 with 2 GB of RAM. Uname -a yields: Linux <hostname> 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux. From lshw: *-cpu description: CPU product: Intel(R) Pentium(R) 4 CPU 2.80GHz vendor: Intel Corp. physical id: 400 bus info: cpu@0 version: 15.2.9 slot: Microprocessor size: 2800MHz capacity: 3600MHz width: 32 bits clock: 533MHz capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr configuration: id=0 -- Backtrace: Application: Konqueror (kdeinit4), signal: Segmentation fault [KCrash Handler] #6 0x00c02f4d in KIO::Slave::deref() () from /usr/lib/libkio.so.5 #7 0x00c03af6 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #8 0x00c05ee3 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #9 0x00461263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #10 0x00461ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #11 0x00b0df97 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5 #12 0x00b0fd5e in ?? () from /usr/lib/libkio.so.5 #13 0x00b0fe8e in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #14 0x00459f0b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4 #15 0x0045b5fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #16 0x0437bf54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0x0438367c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #18 0x00ed4bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #19 0x0044b6cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #20 0x0044c2b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #21 0x0044c47d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #22 0x004763ff in ?? () from /usr/lib/libQtCore.so.4 #23 0x00577e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #24 0x0057b730 in ?? () from /lib/libglib-2.0.so.0 #25 0x0057b863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #26 0x0047602c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #27 0x0441cbe5 in ?? () from /usr/lib/libQtGui.so.4 #28 0x00449c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #29 0x0044a0ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #30 0x0044c53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #31 0x0437bdd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #32 0x0121559f in kdemain () from /usr/lib/libkdeinit4_konqueror.so #33 0x0804dde1 in _start () Reported using DrKonqi
Did you get "could not establish connection dialog"? see https://bugs.kde.org/show_bug.cgi?id=191589
Waiting for feedback
No, I had already made the connection and was copying along and I believe the Konqueoror window just closed. Sorry for the slow response. ---------- Original Message ---------- From: Tommi Tervo <tommi.tervo@gmail.com> To: johnisfound@netzero.com Subject: [Bug 221427] I was copying a folder from a Samba connection (Windows Server 2003) to my locate machine, Ubuntu 9.10 using Konqueror under Gnome. Date: Tue, 5 Jan 2010 19:41:29 +0100 (CET) https://bugs.kde.org/show_bug.cgi?id=221427 --- Comment #1 from Tommi Tervo <tommi tervo gmail com> 2010-01-05 19:41:26 --- Did you get "could not establish connection dialog"? see https://bugs.kde.org/show_bug.cgi?id=191589
No problem. In any case this should be fixed in KDE SC 4.4. Regards *** This bug has been marked as a duplicate of bug 191589 ***