[prev in list] [next in list] [prev in thread] [next in thread]
List: konq-bugs
Subject: [Bug 297112] New: Konqueror Filemanager profile crash with multiple panes open
From: Nick Leverton <nick () leverton ! org>
Date: 2012-03-30 11:42:40
Message-ID: bug-297112-5021 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=297112
Bug ID: 297112
Severity: crash
Version: unspecified
Priority: NOR
Assignee: konq-bugs@kde.org
Summary: Konqueror Filemanager profile crash with multiple
panes open
Classification: Unclassified
OS: Linux
Reporter: nick@leverton.org
Hardware: Ubuntu Packages
Status: UNCONFIRMED
Component: general
Product: konqueror
Application: konqueror (4.7.4 (4.7.4))
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-17-generic-pae i686
Distribution: Ubuntu 11.10
-- Information about the crash:
- What I was doing when the application crashed:
I was using Konqui in FileManagement mode to tidy up my home directory by
moving things into folders or deleting them. In the one konqui instance, one
tab, I had three panes open:
1: viewing home directory, locked to current directory, view linked to pane 3
2: viewing other directory, not locked, not linked
3: viewing file contents, not locked, but linked to pane 1
(the use case obviously being that I could click on a file in pane 1, preview
its contents in pane 3, and then either delete it or drag it to the appropriate
folder in pane 2).
I had noticed that this konqui instance was getting quite slow to respond - it
was newly opened for this purpose so didn't have any old URL history hanging
around. This counts as unusual behaviouor as Konqui is normally pretty quick
to respond in the file management view.
In order to delete an oddly named directory I had opened the Terminal Emulator
view, done the rm and then closed the view, shortly before the crash. I don't
know if it was related.
I then clicked on a few more files and dragged them across. After a few
seconds further moving files around, konqui crashed. Can't tell whether it was
in response to the previous click-and-drag or to the next click as they were
quite close together.
-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4cef710 (LWP 21401))]
Thread 3 (Thread 0xafd17b70 (LWP 6365)):
#0 0xb53ddd44 in __pthread_mutex_unlock_usercnt (mutex=0xd24d6bc, decr=1) at
pthread_mutex_unlock.c:52
#1 0xb75fb2f4 in pthread_mutex_unlock (mutex=0xd24d6bc) at forward.c:184
#2 0xb5309102 in g_main_context_dispatch (context=0xd24d6b8) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3014
#3 0xb5309990 in g_main_context_iterate (context=0xd24d6b8, block=-1255046368,
dispatch=1, self=<optimized out>) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3089
#4 0xb5309c2a in g_main_context_iteration (context=0xd24d6b8, may_block=1) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3152
#5 0xb6773b37 in QEventDispatcherGlib::processEvents (this=0xd236ec8,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6 0xb67441dd in QEventLoop::processEvents (this=0xafd172b0, flags=...) at
kernel/qeventloop.cpp:149
#7 0xb6744421 in QEventLoop::exec (this=0xafd172b0, flags=...) at
kernel/qeventloop.cpp:201
#8 0xb664790b in QThread::exec (this=0xd236480) at thread/qthread.cpp:498
#9 0xb6724e2d in QInotifyFileSystemWatcherEngine::run (this=0xd236480) at
io/qfilesystemwatcher_inotify.cpp:248
#10 0xb664a7b3 in QThreadPrivate::start (arg=0xd236480) at
thread/qthread_unix.cpp:331
#11 0xb53dad31 in start_thread (arg=0xafd17b70) at pthread_create.c:304
#12 0xb75ed46e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Backtrace stopped: Not enough registers or memory available to unwind further
Thread 2 (Thread 0xa7ce9b70 (LWP 6592)):
#0 0xb53c2d10 in __GI_clock_gettime (clock_id=1, tp=0xa7ce9028) at
../sysdeps/unix/clock_gettime.c:116
#1 0xb66a17d5 in do_gettime (frac=0xa7ce9020, sec=0xa7ce9018) at
tools/qelapsedtimer_unix.cpp:123
#2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3 0xb67744b6 in QTimerInfoList::updateCurrentTime (this=0xaf4116cc) at
kernel/qeventdispatcher_unix.cpp:339
#4 0xb677480a in QTimerInfoList::timerWait (this=0xaf4116cc, tm=...) at
kernel/qeventdispatcher_unix.cpp:442
#5 0xb6773053 in timerSourcePrepareHelper (src=<optimized out>,
timeout=0xa7ce912c) at kernel/qeventdispatcher_glib.cpp:136
#6 0xb67730ed in timerSourcePrepare (source=0xaf411698, timeout=<optimized
out>) at kernel/qeventdispatcher_glib.cpp:169
#7 0xb530888c in g_main_context_prepare (context=0xaf40bb78,
priority=0xa7ce9188) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2762
#8 0xb5309637 in g_main_context_iterate (context=0xaf40bb78, block=1,
dispatch=1, self=<optimized out>) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3069
#9 0xb5309c2a in g_main_context_iteration (context=0xaf40bb78, may_block=1) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3152
#10 0xb6773b37 in QEventDispatcherGlib::processEvents (this=0x11b9e140,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0xb67441dd in QEventLoop::processEvents (this=0xa7ce92b0, flags=...) at
kernel/qeventloop.cpp:149
#12 0xb6744421 in QEventLoop::exec (this=0xa7ce92b0, flags=...) at
kernel/qeventloop.cpp:201
#13 0xb664790b in QThread::exec (this=0xfc43b18) at thread/qthread.cpp:498
#14 0xb6724e2d in QInotifyFileSystemWatcherEngine::run (this=0xfc43b18) at
io/qfilesystemwatcher_inotify.cpp:248
#15 0xb664a7b3 in QThreadPrivate::start (arg=0xfc43b18) at
thread/qthread_unix.cpp:331
#16 0xb53dad31 in start_thread (arg=0xa7ce9b70) at pthread_create.c:304
#17 0xb75ed46e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Backtrace stopped: Not enough registers or memory available to unwind further
Thread 1 (Thread 0xb4cef710 (LWP 21401)):
[KCrash Handler]
#7 QCoreApplication::notifyInternal (this=0xbf94f17c, receiver=0x1f1b4eb0,
event=0xbf94e9ac) at kernel/qcoreapplication.cpp:774
#8 0xb5bf764b in sendEvent (event=<optimized out>, receiver=<optimized out>)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#9 QApplicationPrivate::dispatchEnterLeave (enter=0x1f1b4eb0,
leave=0xb6561cbc) at kernel/qapplication.cpp:2810
#10 0xb5c82ca5 in QApplication::x11ProcessEvent (this=0xbf94f17c,
event=0xbf94ecfc) at kernel/qapplication_x11.cpp:3766
#11 0xb5caf28c in x11EventSourceDispatch (s=0x9f06640, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#12 0xb530925f in g_main_dispatch (context=0x9f04af0) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:2441
#13 g_main_context_dispatch (context=0x9f04af0) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3011
#14 0xb5309990 in g_main_context_iterate (context=0x9f04af0, block=-1255046368,
dispatch=1, self=<optimized out>) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3089
#15 0xb5309c2a in g_main_context_iteration (context=0x9f04af0, may_block=1) at
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3152
#16 0xb6773ada in QEventDispatcherGlib::processEvents (this=0x9f01678,
flags=...) at kernel/qeventdispatcher_glib.cpp:422
#17 0xb5caee7a in QGuiEventDispatcherGlib::processEvents (this=0x9f01678,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#18 0xb67441dd in QEventLoop::processEvents (this=0xbf94f004, flags=...) at
kernel/qeventloop.cpp:149
#19 0xb6744421 in QEventLoop::exec (this=0xbf94f004, flags=...) at
kernel/qeventloop.cpp:201
#20 0xb674919d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#21 0xb5bf4924 in QApplication::exec () at kernel/qapplication.cpp:3760
#22 0xb7767bd5 in kdemain (argc=3, argv=0xbf94f4d4) at
../../../konqueror/src/konqmain.cpp:242
#23 0x0804850b in main (argc=3, argv=0xbf94f4d4) at konqueror_dummy.cpp:3
Possible duplicates by query: bug 296296, bug 295391, bug 294979, bug 294380,
bug 294279.
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Konq-bugs mailing list
Konq-bugs@kde.org
https://mail.kde.org/mailman/listinfo/konq-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic