Bug 299222 - Dolphin crashes when I enter the Documents folder
Summary: Dolphin crashes when I enter the Documents folder
Status: RESOLVED DUPLICATE of bug 273233
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 2.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-02 09:04 UTC by Vito Macchia
Modified: 2012-05-02 10:46 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 Vito Macchia 2012-05-02 09:04:49 UTC
Application: dolphin (2.0)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic-pae i686
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I just saved a new copy of a pdf file into the Documents folder (which is named "Documenti" because I have italian localization on), then tried to open the folder and it crashes, each time I try to open it.

- Unusual behavior I noticed:
Crash

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4784740 (LWP 4623))]

Thread 4 (Thread 0xb216db40 (LWP 4624)):
#0  0xb501ac64 in __pthread_mutex_unlock_usercnt (mutex=0xb1800550, decr=1) at pthread_mutex_unlock.c:52
#1  0xb7669634 in pthread_mutex_unlock (mutex=0xb1800550) at forward.c:184
#2  0xb4f8a3d0 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb4f4b1cb in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb65258e7 in QEventDispatcherGlib::processEvents (this=0xb1800468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0xb64f150d in QEventLoop::processEvents (this=0xb216d240, flags=...) at kernel/qeventloop.cpp:149
#6  0xb64f17a9 in QEventLoop::exec (this=0xb216d240, flags=...) at kernel/qeventloop.cpp:204
#7  0xb63da94c in QThread::exec (this=0x9e36b48) at thread/qthread.cpp:501
#8  0xb64ceb5d in QInotifyFileSystemWatcherEngine::run (this=0x9e36b48) at io/qfilesystemwatcher_inotify.cpp:248
#9  0xb63ddde0 in QThreadPrivate::start (arg=0x9e36b48) at thread/qthread_unix.cpp:298
#10 0xb5017d4c in start_thread (arg=0xb216db40) at pthread_create.c:308
#11 0xb765bace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb1333b40 (LWP 4625)):
#0  0xb5000dcd in __GI_clock_gettime (clock_id=1, tp=0xb1332fb8) at ../sysdeps/unix/clock_gettime.c:116
#1  0xb643c315 in do_gettime (frac=0xb1332fb0, sec=0xb1332fa8) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb6526226 in QTimerInfoList::updateCurrentTime (this=0xb0a02074) at kernel/qeventdispatcher_unix.cpp:343
#4  0xb652657a in QTimerInfoList::timerWait (this=0xb0a02074, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#5  0xb6524e23 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb13330bc) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb6524ebd in timerSourcePrepare (source=0xb0a02040, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb4f4a762 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb4f4af6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb4f4b1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb65258e7 in QEventDispatcherGlib::processEvents (this=0xb0a00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#11 0xb64f150d in QEventLoop::processEvents (this=0xb1333240, flags=...) at kernel/qeventloop.cpp:149
#12 0xb64f17a9 in QEventLoop::exec (this=0xb1333240, flags=...) at kernel/qeventloop.cpp:204
#13 0xb63da94c in QThread::exec (this=0xa091920) at thread/qthread.cpp:501
#14 0xb64ceb5d in QInotifyFileSystemWatcherEngine::run (this=0xa091920) at io/qfilesystemwatcher_inotify.cpp:248
#15 0xb63ddde0 in QThreadPrivate::start (arg=0xa091920) at thread/qthread_unix.cpp:298
#16 0xb5017d4c in start_thread (arg=0xb1333b40) at pthread_create.c:308
#17 0xb765bace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xaf574b40 (LWP 4701)):
[KCrash Handler]
#7  0xb13b84c8 in ?? () from /usr/lib/kde4/dolphin-box-plugin.so
#8  0xb73e1a89 in UpdateItemStatesThread::run (this=0xa2d8798) at ../../../dolphin/src/views/versioncontrol/updateitemstatesthread.cpp:66
#9  0xb63ddde0 in QThreadPrivate::start (arg=0xa2d8798) at thread/qthread_unix.cpp:298
#10 0xb5017d4c in start_thread (arg=0xaf574b40) at pthread_create.c:308
#11 0xb765bace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb4784740 (LWP 4623)):
#0  0xb77c3424 in __kernel_vsyscall ()
#1  0xb764b17b in read () at ../sysdeps/unix/syscall-template.S:82
#2  0xb4f8966e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb4f4aaf0 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb4f4b002 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb4f4b1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb6525887 in QEventDispatcherGlib::processEvents (this=0x9cf1798, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#7  0xb5a15aaa in QGuiEventDispatcherGlib::processEvents (this=0x9cf1798, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#8  0xb64f150d in QEventLoop::processEvents (this=0xbf82bf74, flags=...) at kernel/qeventloop.cpp:149
#9  0xb64f17a9 in QEventLoop::exec (this=0xbf82bf74, flags=...) at kernel/qeventloop.cpp:204
#10 0xb64f6eba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#11 0xb595aa74 in QApplication::exec () at kernel/qapplication.cpp:3820
#12 0xb77801da in kdemain (argc=6, argv=0xbf82c1f4) at ../../../dolphin/src/main.cpp:89
#13 0x0804850b in main (argc=6, argv=0xbf82c1f4) at dolphin_dummy.cpp:3

This bug may be a duplicate of or related to bug 273233.

Possible duplicates by query: bug 291694, bug 273233.

Reported using DrKonqi
Comment 1 Peter Penz 2012-05-02 10:46:25 UTC

*** This bug has been marked as a duplicate of bug 273233 ***