230890 2010-03-15 22:57:10 +0000 Dolphin crash when renaming a file 2010-03-16 21:57:29 +0000 1 1 2 Applications dolphin general 16.12.2 Fedora RPMs Linux RESOLVED DUPLICATE 224848 NOR crash --- 0 kmg952 peter.penz19 andresbajotierra kmg952 0 oldest_to_newest 934197 0 kmg952 2010-03-15 22:57:10 +0000 Application: dolphin (1.4) KDE Platform Version: 4.4.00 (KDE 4.4.0) Qt Version: 4.6.2 Operating System: Linux 2.6.32.9-70.fc12.i686.PAE i686 Distribution (Platform): Fedora RPMs -- Information about the crash: Dolphin crashed immediately after I renamed a file. The strange thing is that the file name "900.00AdminStopHawk+030.40#f+040.50#f" was mangled. From memory, I think it was displayed as "900.00AdminStopHawk+030.40#040.50#f+f". When I pressed F2 just to see what would happen, the file name was reported correctly -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [Current thread is 1 (Thread 0xb78777a0 (LWP 3106))] Thread 2 (Thread 0xb5f83b70 (LWP 11627)): [KCrash Handler] #6 deref (this=0x96f2d2c, other=...) at ../../src/corelib/arch/qatomic_i386.h:132 #7 QString::operator= (this=0x96f2d2c, other=...) at tools/qstring.cpp:1281 #8 0x0809be74 in KLoadMetaDataThread::run (this=0x96f2d20) at /usr/src/debug/kdebase-4.4.0/apps/dolphin/src/panels/information/kloadmetadatathread.cpp:89 #9 0x03dd4cdf in QThreadPrivate::start (arg=0x96f2d20) at thread/qthread_unix.cpp:248 #10 0x009e1ab5 in start_thread (arg=<value optimized out>) at pthread_create.c:297 #11 0x00938dce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb78777a0 (LWP 3106)): #0 0x004b9424 in __kernel_vsyscall () #1 0x0092e3d6 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x00a4b0c0 in ?? () from /usr/lib/libxcb.so.1 #3 0x00a4b62b in ?? () from /usr/lib/libxcb.so.1 #4 0x00a4b9c8 in xcb_writev () from /usr/lib/libxcb.so.1 #5 0x00b91d59 in _XSend (dpy=<value optimized out>, data=<value optimized out>, size=<value optimized out>) at xcb_io.c:332 #6 0x00b92360 in _XEventsQueued (dpy=<value optimized out>, mode=<value optimized out>) at xcb_io.c:253 #7 0x00b7a9ef in XEventsQueued (dpy=<value optimized out>, mode=<value optimized out>) at Pending.c:44 #8 0x0477325f in x11EventSourcePrepare (s=0x9371168, timeout=0xbf89c83c) at kernel/qguieventdispatcher_glib.cpp:79 #9 0x00a9e120 in IA__g_main_context_prepare (context=<value optimized out>, priority=<value optimized out>) at gmain.c:2280 #10 0x00a9e4d9 in g_main_context_iterate (context=0x9370490, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2571 #11 0x00a9e9e4 in IA__g_main_context_iteration (context=0x9370490, may_block=<value optimized out>) at gmain.c:2654 #12 0x03ef2e46 in QEventDispatcherGlib::processEvents (this=0x9347330, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #13 0x047730c6 in QGuiEventDispatcherGlib::processEvents (this=0x9347330, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #14 0x03ec92da in QEventLoop::processEvents (this=0xbf89ca54, flags=...) at kernel/qeventloop.cpp:149 #15 0x03ec961a in QEventLoop::exec (this=0xbf89ca54, flags=...) at kernel/qeventloop.cpp:201 #16 0x03ecbce7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #17 0x046c4dd8 in QApplication::exec () at kernel/qapplication.cpp:3579 #18 0x08078047 in main (argc=5, argv=0xbf89ccd4) at /usr/src/debug/kdebase-4.4.0/apps/dolphin/src/main.cpp:101 Possible duplicates by query: bug 230822, bug 230701, bug 230591, bug 230064, bug 229600. Reported using DrKonqi 934421 1 andresbajotierra 2010-03-16 12:31:03 +0000 Fixed in KDE SC 4.4.2. Check the duplicates. Regards *** This bug has been marked as a duplicate of bug 224848 *** 935218 2 kmg952 2010-03-16 21:02:10 +0000 OK, perhaps I could have checked the duplicates. But I was at work, using Dolphin for work activities. It took me around 15 minutes to install the 'devel' RPM's to get a usable stack trace. I did not have the time to trawl through a slew of bug reports to see if the stack trace matched an existing but. But, what about the corrupted file name? 935242 3 andresbajotierra 2010-03-16 21:34:00 +0000 No problem... About the broken filename... if you can repeat the situation, open a new bug report detailing which filesystem are you using. (sorry about that, but we have the "one report per issue" policy to not mixup different things...) Regards 935259 4 kmg952 2010-03-16 21:55:21 +0000 Bug 231030 raised 935260 5 andresbajotierra 2010-03-16 21:57:29 +0000 Thank you