Bug 294380 - Dolphin crashes frequently when I am renaming files
Summary: Dolphin crashes frequently when I am renaming files
Status: RESOLVED DUPLICATE of bug 293362
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 1.7
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-18 18:36 UTC by Richard Rennie
Modified: 2012-03-07 22:14 UTC (History)
0 users

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 Richard Rennie 2012-02-18 18:36:43 UTC
Application: dolphin (1.7)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

Renaming a file (half-a-dozen times a day at least). I download files via get_iplayer and usually shorten and tidy up the names. It is really annoying - often I have two windows open (tiled vertically) so I can move files to where they belong (both windows usually have 2 tabs or more open) so I am renaming and moving files but it is at the rename that dolphin crashes every time. Happens on more than one computer and has been happening since last version of Kubuntu. I don't think it happened in Mandriva.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb789c710 (LWP 9240))]

Thread 3 (Thread 0xb6bafb70 (LWP 9241)):
#0  0x0094fd10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0x02e287d5 in do_gettime (frac=0xb6baf020, sec=0xb6baf018) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x02efb4b6 in QTimerInfoList::updateCurrentTime (this=0x90b937c) at kernel/qeventdispatcher_unix.cpp:339
#4  0x02efb80a in QTimerInfoList::timerWait (this=0x90b937c, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x02efa053 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb6baf12c) at kernel/qeventdispatcher_glib.cpp:136
#6  0x02efa0ed in timerSourcePrepare (source=0x90b9348, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x07dc088c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x07dc1637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0x07dc1c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x02efab37 in QEventDispatcherGlib::processEvents (this=0x9067cf8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0x02ecb1dd in QEventLoop::processEvents (this=0xb6baf2b0, flags=...) at kernel/qeventloop.cpp:149
#12 0x02ecb421 in QEventLoop::exec (this=0xb6baf2b0, flags=...) at kernel/qeventloop.cpp:201
#13 0x02dce90b in QThread::exec (this=0x90b7260) at thread/qthread.cpp:498
#14 0x02eabe2d in QInotifyFileSystemWatcherEngine::run (this=0x90b7260) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x02dd17b3 in QThreadPrivate::start (arg=0x90b7260) at thread/qthread_unix.cpp:331
#16 0x00b60d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0x006440ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0xb5085b70 (LWP 9243)):
#0  0x07dc0e0d in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x07dc18f0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x07dc1c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x02efab37 in QEventDispatcherGlib::processEvents (this=0x92e6808, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x02ecb1dd in QEventLoop::processEvents (this=0xb50852b0, flags=...) at kernel/qeventloop.cpp:149
#5  0x02ecb421 in QEventLoop::exec (this=0xb50852b0, flags=...) at kernel/qeventloop.cpp:201
#6  0x02dce90b in QThread::exec (this=0x93ea400) at thread/qthread.cpp:498
#7  0x02eabe2d in QInotifyFileSystemWatcherEngine::run (this=0x93ea400) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x02dd17b3 in QThreadPrivate::start (arg=0x93ea400) at thread/qthread_unix.cpp:331
#9  0x00b60d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#10 0x006440ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb789c710 (LWP 9240)):
[KCrash Handler]
#7  0x02ecc2cb in size (this=0x9183380) at ../../include/QtCore/../../src/corelib/tools/qlist.h:94
#8  size (this=0x9183380) at ../../include/QtCore/../../src/corelib/tools/qlist.h:124
#9  QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x8f44458, receiver=0x9747dd0, event=0xbf8e1dbc) at kernel/qcoreapplication.cpp:894
#10 0x01332d52 in notify_helper (e=0xbf8e1dbc, receiver=0x9747dd0, this=0x8f44458) at kernel/qapplication.cpp:4482
#11 QApplicationPrivate::notify_helper (this=0x8f44458, receiver=0x9747dd0, e=0xbf8e1dbc) at kernel/qapplication.cpp:4458
#12 0x01338133 in QApplication::notify (this=0xbf8e1dbc, receiver=0x9747dd0, e=0xbf8e1dbc) at kernel/qapplication.cpp:3886
#13 0x045f5971 in KApplication::notify (this=0xbf8e24a4, receiver=0x9747dd0, event=0xbf8e1dbc) at ../../kdeui/kernel/kapplication.cpp:311
#14 0x02ecc19e in QCoreApplication::notifyInternal (this=0xbf8e24a4, receiver=0x9747dd0, event=0xbf8e1dbc) at kernel/qcoreapplication.cpp:787
#15 0x0133364b in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#16 QApplicationPrivate::dispatchEnterLeave (enter=0x9747dd0, leave=0x1c9dcbc) at kernel/qapplication.cpp:2810
#17 0x013beca5 in QApplication::x11ProcessEvent (this=0xbf8e24a4, event=0xbf8e210c) at kernel/qapplication_x11.cpp:3766
#18 0x013eb28c in x11EventSourceDispatch (s=0x8f48da8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#19 0x07dc125f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#20 0x07dc1990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#21 0x07dc1c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#22 0x02efaada in QEventDispatcherGlib::processEvents (this=0x8f2cbb0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#23 0x013eae7a in QGuiEventDispatcherGlib::processEvents (this=0x8f2cbb0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x02ecb1dd in QEventLoop::processEvents (this=0xbf8e2414, flags=...) at kernel/qeventloop.cpp:149
#25 0x02ecb421 in QEventLoop::exec (this=0xbf8e2414, flags=...) at kernel/qeventloop.cpp:201
#26 0x02ed019d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#27 0x01330924 in QApplication::exec () at kernel/qapplication.cpp:3760
#28 0x008f8453 in kdemain (argc=1, argv=0xbf8e2674) at ../../../dolphin/src/main.cpp:85
#29 0x0804850b in main (argc=1, argv=0xbf8e2674) at dolphin_dummy.cpp:3

Possible duplicates by query: bug 293477, bug 293362, bug 293220, bug 292260, bug 291132.

Reported using DrKonqi
Comment 1 Peter Penz 2012-02-28 10:31:35 UTC

*** This bug has been marked as a duplicate of bug 293362 ***
Comment 2 Richard Rennie 2012-03-07 22:14:45 UTC
This (crashing while renaming) may be to do with previews of files
because it is when the dark 'boxy' preview appears (and touches?) my
rename action that the crash happens (I think). I call the preview
'the shadow of mordor' now because it is like the shadow of a giant
bird of prey appearing over my cursor - then CRASH!

On 28/02/2012, Peter Penz <peter.penz19@gmail.com> wrote:
> https://bugs.kde.org/show_bug.cgi?id=294380
>
>
> Peter Penz <peter.penz19@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |DUPLICATE
>
>
>
>
> --- Comment #1 from Peter Penz <peter penz19 gmail com>  2012-02-28 10:31:35
> ---
>
>
> *** This bug has been marked as a duplicate of bug 293362 ***
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>