Bug 296511 - Kate crash while attempting to save file
Summary: Kate crash while attempting to save file
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: libsolid-fstab (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: VHI crash
Target Milestone: ---
Assignee: Mario Bensi
URL:
Keywords:
: 296537 297015 297330 298007 298017 298527 298630 298891 299078 299139 299603 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-03-21 17:50 UTC by Kevin Adler
Modified: 2012-10-27 20:36 UTC (History)
13 users (show)

See Also:
Latest Commit: https://projects.kde.org/projects/kde/kdelibs/repository/revisions/c96ad34d124519d30d3c0f4b369a9f0fa33b36f6
Version Fixed In: 4.8.4

Attachments
New crash information added by DrKonqi (8.30 KB, text/plain)
2012-04-01 07:28 UTC, mms 		Details
New crash information added by DrKonqi (10.71 KB, text/plain)
2012-04-09 12:07 UTC, Bruno Friedmann 		Details
New crash information added by DrKonqi (17.74 KB, text/plain)
2012-05-30 03:06 UTC, Bill McGonigle 		Details
New crash information added by DrKonqi (8.64 KB, text/plain)
2012-06-14 01:33 UTC, Bill McGonigle 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Adler 2012-03-21 17:50:25 UTC 
Application: kate (3.8.1)
KDE Platform Version: 4.8.1 (4.8.1) "release 481"
Qt Version: 4.8.0
Operating System: Linux 3.1.9-1.4-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

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

I opened a save dialog to save a new file. After that, Kate became unresponsive. Finally, the save dialog came up. I tried to change the file name, but it was apparent the save dialog was unresponsive. I left it be for a while, periodically checking responsiveness. Eventually, it just crashed.

-- Backtrace:
Application: Kate (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f87511dc760 (LWP 15737))]

Thread 3 (Thread 0x7f87384a5700 (LWP 15746)):
#0  0x00007f874fa78e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f8744872942 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f8744b6be80) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f8744872979 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f874fa74f05 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f874e7d463d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f87367d5700 (LWP 17066)):
#0  0x00007f874fa7701e in pthread_mutex_lock () from /lib64/libpthread.so.0
#1  0x00007f874b5a6b74 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f874b5a6f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f874fe38956 in QEventDispatcherGlib::processEvents (this=0x7f87300008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f874fe08682 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f874fe088d7 in QEventLoop::exec (this=0x7f87367d4df0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f874fd09537 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f874fde848f in QInotifyFileSystemWatcherEngine::run (this=0x15b7b40) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f874fd0c55b in QThreadPrivate::start (arg=0x15b7b40) at thread/qthread_unix.cpp:298
#9  0x00007f874fa74f05 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f874e7d463d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f87511dc760 (LWP 15737)):
[KCrash Handler]
#6  ref (this=0x41) at ../../src/corelib/arch/qatomic_x86_64.h:121
#7  QString::operator= (this=0x7fffa15405c8, other=...) at tools/qstring.cpp:1406
#8  0x00007f87486b148c in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fffa15405a0, device=0x7f272a0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9  0x00007f87486afbf1 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x00007f874863d7e9 in Solid::Device::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/solid/solid/device.cpp:143
#11 0x00007f873683a419 in KFilePlacesItem::deviceData (this=0x7f627b0, role=1) at /usr/src/debug/kdelibs-4.8.1/kfile/kfileplacesitem.cpp:174
#12 0x00007f873683b7be in KFilePlacesItem::data (this=<optimized out>, role=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kfile/kfileplacesitem.cpp:127
#13 0x00007f873683bb7e in KFilePlacesModel::data (this=<optimized out>, index=<optimized out>, role=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kfile/kfileplacesmodel.cpp:270
#14 0x00007f873683beea in KFilePlacesModel::icon (this=<optimized out>, index=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kfile/kfileplacesmodel.cpp:213
#15 0x00007f873685b6c0 in KDEPrivate::KUrlNavigatorPlacesSelector::updateMenu (this=0xa2e2bd0) at /usr/src/debug/kdelibs-4.8.1/kfile/kurlnavigatorplacesselector.cpp:79
#16 0x00007f874fe1d761 in QMetaObject::activate (sender=0x9938990, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa1540a20) at kernel/qobject.cpp:3556
#17 0x00007f874fe6a054 in QAbstractItemModel::rowsRemoved (this=<optimized out>, _t1=<optimized out>, _t2=17, _t3=17) at .moc/release-shared/moc_qabstractitemmodel.cpp:211
#18 0x00007f874fe041ad in QAbstractItemModel::endRemoveRows (this=0x9938990) at kernel/qabstractitemmodel.cpp:2487
#19 0x00007f873683f0d5 in KFilePlacesModel::Private::_k_reloadBookmarks (this=0x71caf20) at /usr/src/debug/kdelibs-4.8.1/kfile/kfileplacesmodel.cpp:432
#20 0x00007f87368404ed in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=0x9938990, _c=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/build/kfile/kfileplacesmodel.moc:70
#21 KFilePlacesModel::qt_static_metacall (_o=0x9938990, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/build/kfile/kfileplacesmodel.moc:60
#22 0x00007f874fe1d761 in QMetaObject::activate (sender=0x1375f40, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa1540dd0) at kernel/qobject.cpp:3556
#23 0x00007f874863e7e5 in Solid::DeviceNotifier::deviceRemoved (this=<optimized out>, _t1=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/build/solid/solid/devicenotifier.moc:108
#24 0x00007f874863fb7d in Solid::DeviceManagerPrivate::_k_deviceRemoved (this=0x1375f40, udi=...) at /usr/src/debug/kdelibs-4.8.1/solid/solid/devicemanager.cpp:207
#25 0x00007f874fe1d761 in QMetaObject::activate (sender=0x115d160, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa1540fc0) at kernel/qobject.cpp:3556
#26 0x00007f87486537f5 in Solid::Ifaces::DeviceManager::deviceRemoved (this=<optimized out>, _t1=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/build/solid/solid/ifaces/devicemanager.moc:108
#27 0x00007f87486af013 in Solid::Backends::Fstab::FstabManager::_k_updateDeviceList (this=0x115d160) at /usr/src/debug/kdelibs-4.8.1/solid/solid/backends/fstab/fstabmanager.cpp:126
#28 0x00007f87486af335 in Solid::Backends::Fstab::FstabManager::onMtabChanged (this=0x115d160) at /usr/src/debug/kdelibs-4.8.1/solid/solid/backends/fstab/fstabmanager.cpp:136
#29 0x00007f874fe1d761 in QMetaObject::activate (sender=0xd0a000, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3556
#30 0x00007f874fe1d761 in QMetaObject::activate (sender=0x13f0b40, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa1541320) at kernel/qobject.cpp:3556
#31 0x00007f874fe6ac6e in QSocketNotifier::activated (this=<optimized out>, _t1=14) at .moc/release-shared/moc_qsocketnotifier.cpp:103
#32 0x00007f874fe26aeb in QSocketNotifier::event (this=0x13f0b40, e=0x7fffa1541990) at kernel/qsocketnotifier.cpp:317
#33 0x00007f874ef71e84 in notify_helper (e=0x7fffa1541990, receiver=0x13f0b40, this=0x6f3dd0) at kernel/qapplication.cpp:4550
#34 QApplicationPrivate::notify_helper (this=0x6f3dd0, receiver=0x13f0b40, e=0x7fffa1541990) at kernel/qapplication.cpp:4522
#35 0x00007f874ef76d03 in QApplication::notify (this=0x7fffa1543590, receiver=0x13f0b40, e=0x7fffa1541990) at kernel/qapplication.cpp:4411
#36 0x00007f8750bc9656 in KApplication::notify (this=0x7fffa1543590, receiver=0x13f0b40, event=0x7fffa1541990) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311
#37 0x00007f874fe0989c in QCoreApplication::notifyInternal (this=0x7fffa1543590, receiver=0x13f0b40, event=0x7fffa1541990) at kernel/qcoreapplication.cpp:876
#38 0x00007f874fe37f47 in sendEvent (event=0x7fffa1541990, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#39 socketNotifierSourceDispatch (source=0x6f0d00) at kernel/qeventdispatcher_glib.cpp:110
#40 0x00007f874b5a658d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#41 0x00007f874b5a6d88 in ?? () from /usr/lib64/libglib-2.0.so.0
#42 0x00007f874b5a6f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#43 0x00007f874fe388ef in QEventDispatcherGlib::processEvents (this=0x6f4540, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#44 0x00007f874f0152de in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#45 0x00007f874fe08682 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#46 0x00007f874fe088d7 in QEventLoop::exec (this=0x7fffa1541bd0, flags=...) at kernel/qeventloop.cpp:204
#47 0x00007f874f43e086 in QDialog::exec (this=0x7fffa1541c50) at dialogs/qdialog.cpp:552
#48 0x00007f8749040fce in KEncodingFileDialog::getSaveUrlAndEncoding (encoding=..., dir=..., filter=<optimized out>, parent=<optimized out>, caption=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kio/kfile/kencodingfiledialog.cpp:203
#49 0x00007f87389ef33c in KateDocument::documentSaveAs() () from /usr/lib64/libkatepartinterfaces.so.4
#50 0x00007f87389f0e92 in ?? () from /usr/lib64/libkatepartinterfaces.so.4
#51 0x00007f874fe1d761 in QMetaObject::activate (sender=0x8244b90, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa1541f60) at kernel/qobject.cpp:3556
#52 0x00007f874ef6b9d2 in QAction::triggered (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:277
#53 0x00007f874ef6bbbf in QAction::activate (this=0x8244b90, event=<optimized out>) at kernel/qaction.cpp:1257
#54 0x00007f874f33cfca in QAbstractButtonPrivate::click (this=0x483ab90) at widgets/qabstractbutton.cpp:528
#55 0x00007f874f33d27c in QAbstractButton::mouseReleaseEvent (this=0x99d7d20, e=0x7fffa1542840) at widgets/qabstractbutton.cpp:1121
#56 0x00007f874f3faaea in QToolButton::mouseReleaseEvent (this=<optimized out>, e=<optimized out>) at widgets/qtoolbutton.cpp:718
#57 0x00007f874efc2594 in QWidget::event (this=0x99d7d20, event=0x7fffa1542840) at kernel/qwidget.cpp:8361
#58 0x00007f874ef71e84 in notify_helper (e=0x7fffa1542840, receiver=0x99d7d20, this=0x6f3dd0) at kernel/qapplication.cpp:4550
#59 QApplicationPrivate::notify_helper (this=0x6f3dd0, receiver=0x99d7d20, e=0x7fffa1542840) at kernel/qapplication.cpp:4522
#60 0x00007f874ef775d3 in QApplication::notify (this=<optimized out>, receiver=0x99d7d20, e=0x7fffa1542840) at kernel/qapplication.cpp:4093
#61 0x00007f8750bc9656 in KApplication::notify (this=0x7fffa1543590, receiver=0x99d7d20, event=0x7fffa1542840) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311
#62 0x00007f874fe0989c in QCoreApplication::notifyInternal (this=0x7fffa1543590, receiver=0x99d7d20, event=0x7fffa1542840) at kernel/qcoreapplication.cpp:876
#63 0x00007f874ef72e52 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231
#64 QApplicationPrivate::sendMouseEvent (receiver=0x99d7d20, event=0x7fffa1542840, alienWidget=0x99d7d20, nativeWidget=0xae1c50, buttonDown=0x99d7d20, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3161
#65 0x00007f874efeec05 in QETWidget::translateMouseEvent (this=0xae1c50, event=<optimized out>) at kernel/qapplication_x11.cpp:4505
#66 0x00007f874efedaca in QApplication::x11ProcessEvent (this=0x7fffa1543590, event=0x7fffa1543100) at kernel/qapplication_x11.cpp:3631
#67 0x00007f874f015652 in x11EventSourceDispatch (s=0x6f0e90, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#68 0x00007f874b5a658d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#69 0x00007f874b5a6d88 in ?? () from /usr/lib64/libglib-2.0.so.0
#70 0x00007f874b5a6f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#71 0x00007f874fe388ef in QEventDispatcherGlib::processEvents (this=0x6f4540, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#72 0x00007f874f0152de in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#73 0x00007f874fe08682 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#74 0x00007f874fe088d7 in QEventLoop::exec (this=0x7fffa15434d0, flags=...) at kernel/qeventloop.cpp:204
#75 0x00007f874fe0d435 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#76 0x00007f873e49a405 in kdemain () from /usr/lib64/libkdeinit4_kate.so
#77 0x00000000004088e4 in launch (argc=3, _name=0x690988 "/usr/bin/kate", args=<optimized out>, cwd=0x0, envc=<optimized out>, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x690a0c "kadler;1331924925;957821;15156_TIME101002403") at /usr/src/debug/kdelibs-4.8.1/kinit/kinit.cpp:734
#78 0x00000000004099e6 in handle_launcher_request (sock=8, who=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kinit/kinit.cpp:1226
#79 0x0000000000409f27 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.8.1/kinit/kinit.cpp:1419
#80 0x00000000004057a7 in main (argc=4, argv=0x7fff00000001, envp=0x7fffa1545c10) at /usr/src/debug/kdelibs-4.8.1/kinit/kinit.cpp:1907

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-03-29 07:38:17 UTC 
*** Bug 297015 has been marked as a duplicate of this bug. ***
Comment 2 mms 2012-04-01 07:28:03 UTC 
Created attachment 70048 [details]
New crash information added by DrKonqi

gwenview (2.8.1) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

Gwenview and also dolphin are quite unstable! If running both, crashes occur regulary!

As I posted a separate bug report which was noted a duplicate of this one, I do post some debug info here!!

-- Backtrace (Reduced):
#7  QString::operator= (this=0x7fff6d38a1d8, other=...) at tools/qstring.cpp:1406
#8  0x00007f7cb9ee61bc in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fff6d38a1b0, device=0x21811d0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at ../../../solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9  0x00007f7cb9ee4921 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at ../../../solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x00007f7cb9e72099 in Solid::Device::emblems (this=<optimized out>) at ../../../solid/solid/device.cpp:143
#11 0x00007f7cbd3f2369 in KFilePlacesItem::deviceData (this=0x211e290, role=1) at ../../kfile/kfileplacesitem.cpp:174
Comment 3 Dominik Haumann 2012-04-02 21:14:52 UTC 
*** Bug 297330 has been marked as a duplicate of this bug. ***
Comment 4 Dominik Haumann 2012-04-02 21:15:08 UTC 
*** Bug 296537 has been marked as a duplicate of this bug. ***
Comment 5 Dominik Haumann 2012-04-02 21:16:07 UTC 
Bug #296537 comment #2 contains steps how to reproduce:

> 1. Launch kdevelop
> 2. On another konsole window, run "umount -a"
> 3. Enjoy the crash.
> 
> I use automount, so this crash happens every few minutes, so I am not able to use Kdevelop anymore.
Comment 6 Kevin Adler 2012-04-06 21:58:54 UTC 
I just tested again on 4.8.2 and I'm no longer getting this problem.

1. mount cifs client
2. open file in mounted directory in kate
3. umount directory

I got 'The file ... was deleted by another program' dialog like it normally would, instead of crashing.
Comment 7 Bruno Friedmann 2012-04-09 12:07:38 UTC 
Created attachment 70256 [details]
New crash information added by DrKonqi

dolphin (2.0) on KDE Platform 4.8.2 (4.8.2) "release 491" using Qt 4.8.1

- What I was doing when the application crashed:
dolphin was open on a mounted nfs directory, then networkmanager restart the connection (or systemd, for no good reason)
Dolphin start to crash with a very minimal error 

Application: Dolphin (kdeinit4 (deleted)), signal: Segmentation fault
[Current thread is 1 (process 19877)]

Thread 1 (process 19877):
#0  0x874a68dd in ?? ()

And then I get this new crash.

In NetworkManager logs 
Apr  9 12:43:09 localhost NetworkManager[1361]: DHCPACK from 192.168.103.151
Apr  9 12:43:09 localhost NetworkManager[1361]: bound to 192.168.103.131 -- renewal in 5994 seconds.
Apr  9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): device state change: activated -> failed (reason 'ip-config-unavailable') [100 120 5]
Apr  9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): device state change: activated -> failed (reason 'ip-config-unavailable') [100 120 5]
Apr  9 14:00:09 localhost NetworkManager[1361]: <warn> Activation (eth0) failed.
Apr  9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <warn> Activation (eth0) failed.
Apr  9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr  9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): deactivating device (reason 'none') [0]
Apr  9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr  9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): deactivating device (reason 'none') [0]
Apr  9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): canceled DHCP transaction, DHCP client pid 2366
Apr  9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): canceled DHCP transaction, DHCP client pid 2366
Apr  9 14:00:09 localhost NetworkManager[1361]: <info> Clearing nscd hosts cache.
Apr  9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> Clearing nscd hosts cache.
Apr  9 14:00:09 localhost NetworkManager[1361]: sent invalidate(hosts) request, exiting
Apr  9 14:00:09 localhost NetworkManager[1361]: <info> Clearing nscd hosts cache

So there's something that can't handle correctly the fact a network connection could be drop. The program should avoid to crash so badly.

-- Backtrace (Reduced):
#7  QString::operator= (this=0x7fffd4b1b778, other=...) at tools/qstring.cpp:1410
#8  0x00007f3f59b7748c in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fffd4b1b750, device=0xcb7870, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kdelibs-4.8.2/solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9  0x00007f3f59b75bf1 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.2/solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x00007f3f59b037e9 in Solid::Device::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.2/solid/solid/device.cpp:143
#11 0x00007f3f5de533a9 in KFilePlacesItem::deviceData (this=0xbd5a20, role=1) at /usr/src/debug/kdelibs-4.8.2/kfile/kfileplacesitem.cpp:174
Comment 8 Milian Wolff 2012-04-13 11:31:52 UTC 
*** Bug 298017 has been marked as a duplicate of this bug. ***
Comment 9 Milian Wolff 2012-04-13 11:32:12 UTC 
reopening, 298017 was reported with kde 4.8.2
Comment 10 Lamarque V. Souza 2012-04-13 22:25:32 UTC 
*** Bug 298007 has been marked as a duplicate of this bug. ***
Comment 11 Jekyll Wu 2012-04-21 08:57:13 UTC 
*** Bug 298527 has been marked as a duplicate of this bug. ***
Comment 12 Pradeep K. Shima 2012-04-26 06:16:38 UTC 
I dont mean to rush since I understand this is open source software and developed mostly as community service. 
But wouldnt it be nice to hear of atleast a workaround for such a critical bug ?
Having Kdevelop crash every 2 minutes is definitly a blocker to its success or even adoption.

On the technical side, I dont see any issue with Kate, but only with Kdeveop. Yet this crash keeps getting duplicated to a bug titled ".. kate ...".
Kate is just an editor. Users can temporarily switch to another easily. Things are not so sweet with kdevelop. Its an IDE too good to have a replacement. 
So titling this bug as a bug in an editor kind of belittles its importance. Dont you think ?
Comment 13 Jekyll Wu 2012-04-27 08:38:01 UTC 
*** Bug 298891 has been marked as a duplicate of this bug. ***
Comment 14 Christoph Feck 2012-04-27 10:05:58 UTC 
*** Bug 298630 has been marked as a duplicate of this bug. ***
Comment 15 Jekyll Wu 2012-05-01 07:45:48 UTC 
*** Bug 299139 has been marked as a duplicate of this bug. ***
Comment 16 Jekyll Wu 2012-05-01 07:46:05 UTC 
*** Bug 299078 has been marked as a duplicate of this bug. ***
Comment 17 Jekyll Wu 2012-05-08 07:07:58 UTC 
*** Bug 299603 has been marked as a duplicate of this bug. ***
Comment 18 Stefan Brüns 2012-05-10 11:11:23 UTC 
This one should be fixed by:
https://git.reviewboard.kde.org/r/104471/
Fix should be in 4.8.4, openSUSE has it cherrypicked:

rpm -q --changelog libkde4 | grep fstabstorageaccess
- fix crash due to race in fstabstorageaccess constructor

As a temporary workaround, it might be enough to disable the places view in the open dialog.
Comment 19 Pradeep K. Shima 2012-05-10 11:25:02 UTC 
Thanks a lot for the response Stefan,

About the fix : You mean version 4.84 of kdelibs ?

About the workaround : which "open dialog" ? I see the crash in Kdevelop without doing anything. the bugs title is way too misleading.
Comment 20 Stefan Brüns 2012-05-10 14:41:35 UTC 
(In reply to comment #19)
> About the workaround : which "open dialog" ? I see the crash in Kdevelop
> without doing anything. the bugs title is way too misleading.

This bug was specifically about the file dialog in kate, and the same bug can also be seen in dolphin, as it uses the same "Places" side pane.

You never submitted a backtrace, so you may be hitting a completely independent bug.
Comment 21 Pradeep K. Shima 2012-05-10 14:58:18 UTC 
Thats quite unfortunate. 
The bug was very much reported on Kdevelop by me along with backtrace (Bug #296537)
But Someone or some = tool keeps marking it as a dup of this bug. 

I added comments on this bug to show criticality of the issue and impact I am facing every few minutes but alas this bug is still titled as a simple bug in an editor :(
Comment 22 Stefan Brüns 2012-05-10 15:17:03 UTC 
(In reply to comment #21)
> The bug was very much reported on Kdevelop by me along with backtrace (Bug
> #296537)

This information would have been useful in the first place - and yes, it is a duplicate (as can be seen from the backtrace).

KDevelop must have a "Places" pane somewhere.
Comment 23 Pradeep K. Shima 2012-05-23 08:40:52 UTC 
Disabling the Filesystem Tool View in Kdevelop is a workaround that seems to work.
Right click on teh Filesystem toolview and click "Remove Toolview".

That aligns with the above comment "KDevelop must have a "Places" pane somewhere."
Comment 24 Bill McGonigle 2012-05-30 03:06:42 UTC 
Created attachment 71435 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

- What I was doing when the application crashed:

waiting for a burn to finish (it was done or very nearly done when the crash happened)
ISO image file was on an NFS mount, if that matters (as has always worked in the past).

-- Backtrace (Reduced):
#7  QString::operator= (this=0x7fff19ea36b8, other=...) at tools/qstring.cpp:1410
#8  0x0000003b3629758c in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fff19ea3690, device=0x11a42b0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9  0x0000003b36295c01 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x0000003b362382f9 in Solid::Device::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/device.cpp:143
#11 0x0000003b444635f9 in KFilePlacesItem::deviceData (this=0x11ced20, role=1) at /usr/src/debug/kdelibs-4.8.3/kfile/kfileplacesitem.cpp:174
Comment 25 Bill McGonigle 2012-06-14 01:33:39 UTC 
Created attachment 71815 [details]
New crash information added by DrKonqi

dolphin (2.0) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2

- What I was doing when the application crashed:

mount data CD.  Dolphin crashes shortly thereafter.  4.8.3.

-- Backtrace (Reduced):
#7  QString::operator= (this=0x7fffb963e3a8, other=...) at tools/qstring.cpp:1410
#8  0x00000031d609758c in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fffb963e380, device=0x1d20540, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9  0x00000031d6095c01 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x00000031d60382f9 in Solid::Device::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/device.cpp:143
#11 0x00000031d9c635f9 in KFilePlacesItem::deviceData (this=0x1b3c340, role=1) at /usr/src/debug/kdelibs-4.8.3/kfile/kfileplacesitem.cpp:174
Comment 26 Stefan Brüns 2012-10-27 19:03:37 UTC 
Please close, this has been fixed by:
https://projects.kde.org/projects/kde/kdelibs/repository/revisions/c96ad34d124519d30d3c0f4b369a9f0fa33b36f6

Fix is in 4.8.4/4.9.0