Bug 208294 - Dolphin crashes in splitted view when opening automounted directory by typing a path in an address bar
Summary: Dolphin crashes in splitted view when opening automounted directory by typing...
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-23 14:13 UTC by Anton Alkin
Modified: 2018-03-25 13:30 UTC (History)
2 users (show)

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 Anton Alkin 2009-09-23 14:13:56 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30.5-43.fc11.i586 i686
Distribution: "Fedora release 11 (Leonidas)"

What I was doing when the application crashed:
I'm not really sure it's related to automounting

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

Thread 2 (Thread 0xb64dbb70 (LWP 10177)):
[KCrash Handler]
#6  QMutex::lock (this=0x44) at thread/qmutex.cpp:152
#7  0x03f5d420 in QMutexLocker::relock (this=<value optimized out>) at ../../src/corelib/thread/qmutex.h:120
#8  QMutexLocker (this=<value optimized out>) at ../../src/corelib/thread/qmutex.h:102
#9  QThreadPrivate::finish (this=<value optimized out>) at thread/qthread_unix.cpp:198
#10 0x03f5d2fa in ~__pthread_cleanup_class (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/include/pthread.h:535
#11 QThreadPrivate::start (this=<value optimized out>, __in_chrg=<value optimized out>) at thread/qthread_unix.cpp:190
#12 0x003e7935 in start_thread (arg=0xb64dbb70) at pthread_create.c:297
#13 0x0031c94e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7f5e9b0 (LWP 9481)):
#0  0x00155422 in __kernel_vsyscall ()
#1  0x00312396 in *__GI___poll (fds=0x3aaff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0x0069f0a0 in ?? () from /usr/lib/libxcb.so.1
#3  0x006a0cc2 in xcb_wait_for_reply () from /usr/lib/libxcb.so.1
#4  0x00566026 in _XReply (dpy=0x94413a8, rep=0xbf9e5ae0, extra=0, discard=1) at xcb_io.c:454
#5  0x00559cf7 in XSync (dpy=0x94413a8, discard=0) at Sync.c:48
#6  0x0775c371 in QApplication::syncX () at kernel/qapplication_x11.cpp:2974
#7  0x0776092d in QETWidget::translateConfigEvent (this=0x99280e0, event=0xbf9e726c) at kernel/qapplication_x11.cpp:5166
#8  0x0776dcfe in QApplication::x11ProcessEvent (this=0xbf9e760c, event=0xbf9e726c) at kernel/qapplication_x11.cpp:3450
#9  0x077995d2 in x11EventSourceDispatch (s=0x9420c68, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#10 0x03c6f308 in g_main_dispatch (context=<value optimized out>) at gmain.c:1824
#11 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2377
#12 0x03c729e0 in g_main_context_iterate (context=0x941fe90, block=<value optimized out>, dispatch=1, self=0x94250f0) at gmain.c:2455
#13 0x03c72b13 in IA__g_main_context_iteration (context=0x941fe90, may_block=1) at gmain.c:2518
#14 0x040785ec in QEventDispatcherGlib::processEvents (this=0x9400880, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327
#15 0x07798cb5 in QGuiEventDispatcherGlib::processEvents (this=0x9400880, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#16 0x0404c0d9 in QEventLoop::processEvents (this=0xbf9e7564, flags={i = 36}) at kernel/qeventloop.cpp:149
#17 0x0404c52a in QEventLoop::exec (this=0xbf9e7564, flags={i = 0}) at kernel/qeventloop.cpp:201
#18 0x0404e9af in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#19 0x076f97f7 in QApplication::exec () at kernel/qapplication.cpp:3525
#20 0x08078355 in main (argc=2, argv=0xbf9e77e4) at /usr/src/debug/kdebase-4.3.1/apps/dolphin/src/main.cpp:94

This bug may be a duplicate of or related to bug 186474

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-25 02:48:28 UTC
Mh, weird, the backtrace only contains Qt functions.
- Does Dolphin crash again if you repeat the situation ?
Thanks
Comment 2 Julian Steinmann 2018-03-25 13:30:24 UTC
I cannot reproduce this issue with Dolphin 17.12.3. Closing because of missing activity. If you can still reproduce this behavior with the newest version of Dolphin, please reopen this bug.