Bug 182516 - Open terminal here crash konqueror
Summary: Open terminal here crash konqueror
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.2.0
Platform: Gentoo Packages Unspecified
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 195237 197182 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-31 00:18 UTC by BRULE Herman
Modified: 2011-06-05 16:07 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BRULE Herman 2009-01-31 00:18:35 UTC
Version:            (using KDE 4.2.0)
Installed from:    Gentoo Packages

When I go to ~ with konqueror, I do Actions -> Open terminal here, that's crash konqueror.
Comment 1 David Faure 2009-01-31 00:19:59 UTC
Can you provide a backtrace of the crash?
Comment 2 A. Spehr 2009-01-31 00:30:31 UTC
Can't confirm on ~4.2.61, can you check your install? Otherwise, add 
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports


Comment 3 BRULE Herman 2009-01-31 11:54:43 UTC
For konqueror:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
...
(no debugging symbols found)
0x00007fd8a7bacaa1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 32025)]

For plasma:
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
...
(no debugging symbols found)
(no debugging symbols found)
0x00007f30bb239aa1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 3767)]

I recompil kde for have backtrace.
Comment 4 BRULE Herman 2009-02-01 14:13:25 UTC
Application: Konqueror (konqueror), signal SIGABRT
0x00007fcf63ac18a1 in nanosleep () from /lib/libc.so.6
Current language:  auto; currently c
[Current thread is 0 (LWP 12479)]

Thread 2 (Thread 0x7fcf5a0b1950 (LWP 12485)):
#0  0x00007fcf63aeb552 in select () from /lib/libc.so.6
#1  0x00007fcf6652ea65 in QProcessManager::run (this=0x16a8930) at io/qprocess_unix.cpp:307
#2  0x00007fcf6645eb92 in QThreadPrivate::start (arg=0x16a8930) at thread/qthread_unix.cpp:191
#3  0x00007fcf661eb007 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#4  0x00007fcf63af1e4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fcf68ed8750 (LWP 12479)):
[KCrash Handler]
#5  0x00007fcf63a541e5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007fcf63a55703 in *__GI_abort () at abort.c:88
#7  0x00007fcf664560fd in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>) at global/qglobal.cpp:2108
#8  0x00007fcf66456237 in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2309
#9  0x00007fcf67d96571 in KDirModelPrivate::_k_slotNewItems (this=0x1c17500, directoryUrl=<value optimized out>, items=@0x1a31610)
    at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs-4.2.0/kio/kio/kdirmodel.cpp:367
#10 0x00007fcf67d9666a in KDirModel::qt_metacall (this=0x1d61430, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff70f0c130)
    at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs_build/kio/kdirmodel.moc:77
#11 0x00007fcf66566d3c in QMetaObject::activate (sender=0x1d06ae0, from_signal_index=<value optimized out>, to_signal_index=14, argv=0xffffffffffffffff) at kernel/qobject.cpp:3028
#12 0x00007fcf67d7feea in KDirLister::itemsAdded (this=0x30bf, _t1=<value optimized out>, _t2=<value optimized out>)
    at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs_build/kio/kdirlister.moc:266
#13 0x00007fcf67d80f9a in KDirLister::Private::emitItems (this=0x1a5b220) at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs-4.2.0/kio/kio/kdirlister.cpp:2232
#14 0x00007fcf67d84f82 in KDirListerCache::emitRefreshItem (this=<value optimized out>, oldItem=@0x7fff70f0c450, fileitem=@0x1a524e8)
    at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs-4.2.0/kio/kio/kdirlister.cpp:935
#15 0x00007fcf67d8aec4 in KDirListerCache::slotFilesChanged (this=0x1b0f080, fileList=@0x1b0ed50) at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs-4.2.0/kio/kio/kdirlister.cpp:818
#16 0x00007fcf67d8b73c in KDirListerCache::qt_metacall (this=0x1b0f080, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff70f0c620)
    at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs_build/kio/kdirlister_p.moc:92
#17 0x00007fcf66566d3c in QMetaObject::activate (sender=0x1b11100, from_signal_index=<value optimized out>, to_signal_index=8, argv=0xffffffffffffffff) at kernel/qobject.cpp:3028
#18 0x00007fcf67d99bc5 in OrgKdeKDirNotifyInterface::FilesChanged (this=0x30bf, _t1=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs_build/kio/kdirnotify.moc:116
#19 0x00007fcf67d99d24 in OrgKdeKDirNotifyInterface::qt_metacall (this=0x1b11100, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff70f0c720)
    at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs_build/kio/kdirnotify.moc:81
#20 0x00007fcf66861403 in QDBusConnectionPrivate::deliverCall (this=0x17192c0, object=0x1b11100, msg=@0x1d24eb8, metaTypes=@0x1d24ec0, slotIdx=8) at qdbusintegrator.cpp:855
#21 0x00007fcf66868dff in QDBusCallDeliveryEvent::placeMetaCall (this=0x0, object=0x30bf) at qdbusintegrator_p.h:136
#22 0x00007fcf6656092d in QObject::event (this=0x1b11100, e=0x1d24e70) at kernel/qobject.cpp:1152
#23 0x00007fcf6582115d in QApplicationPrivate::notify_helper (this=0x16aa4c0, receiver=0x1b11100, e=0x1d24e70) at kernel/qapplication.cpp:3809
#24 0x00007fcf65827f9e in QApplication::notify (this=0x7fff70f0d730, receiver=0x1b11100, e=0x1d24e70) at kernel/qapplication.cpp:3774
#25 0x00007fcf67341c11 in KApplication::notify (this=0x7fff70f0d730, receiver=0x1b11100, event=0x1d24e70)
    at /var/tmp/portage/kde-base/kdelibs-4.2.0/work/kdelibs-4.2.0/kdeui/kernel/kapplication.cpp:307
#26 0x00007fcf66550810 in QCoreApplication::notifyInternal (this=0x7fff70f0d730, receiver=0x1b11100, event=0x1d24e70) at kernel/qcoreapplication.cpp:593
#27 0x00007fcf6655170b in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1693a60) at kernel/qcoreapplication.h:215
#28 0x00007fcf658b604a in QEventDispatcherX11::processEvents (this=0x16a9b50, flags={i = 1894831184}) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#29 0x00007fcf6654f412 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1894831232}) at kernel/qeventloop.cpp:149
#30 0x00007fcf6654f59d in QEventLoop::exec (this=0x7fff70f0d4c0, flags={i = 1894831312}) at kernel/qeventloop.cpp:200
#31 0x00007fcf66551a1d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#32 0x00007fcf68ab87f2 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/konqueror-4.2.0/work/konqueror-4.2.0/apps/konqueror/src/konqmain.cpp:257
#33 0x00007fcf63a405c6 in __libc_start_main (main=0x4009c0 <main>, argc=2, ubp_av=0x7fff70f0e1e8, init=0x4009f0 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff70f0e1d8) at libc-start.c:226
#34 0x00000000004008f9 in _start ()

Comment 5 David Faure 2009-02-09 21:05:30 UTC
Strange. The backtrace you posted is a crash when konqueror is notified about a file that has been created. I'm guessing the relation to "Open terminal here" is that the shell creates a history file (for instance). Do you get the same crash if you simply do "touch ~/foo" in a terminal while konqueror is vieweing ~ ?

Before the assert, there is an informative output from konqueror, can you look in ~/.xsession-errors for 
ERROR: Items emitted in directory....
and everything that follows until the line with "ASSERT"?
Please paste that info here.
Comment 6 BRULE Herman 2009-02-09 22:07:26 UTC
No crash if I view ~ with konqueror and I do touch ~/foo. But the bug is not instant it's show sometime but only after lot of use of konqueror, no bug is I do directly konqueror and after open term here.
The file is here:
http://files.first-world.info/temp/xsession-errors
For reproduct this bug:
- open konqueror at ~
- select file
- ctrl c, ctrl v
- suggest new name, rename
- open terminal here
Comment 7 Frank Reininghaus 2009-03-15 22:01:33 UTC
Looks like a duplicate of bug 181536 (which I've just reproduced with trunk rev. 939826).
Comment 8 Dario Andres 2009-07-07 22:55:35 UTC
*** Bug 197182 has been marked as a duplicate of this bug. ***
Comment 9 Frank Reininghaus 2009-10-14 15:01:18 UTC
*** Bug 195237 has been marked as a duplicate of this bug. ***
Comment 10 Martin Koller 2011-06-05 16:07:00 UTC
Can you reproduce with a current KDE >= 4.6.3 ?