Bug 225957 - saving file mounted over sshfs
Summary: saving file mounted over sshfs
Status: RESOLVED DUPLICATE of bug 224229
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-08 21:17 UTC by Zach Dwiel
Modified: 2010-02-10 13:42 UTC (History)
1 user (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 Zach Dwiel 2010-02-08 21:17:27 UTC
Application that crashed: kate
Version of the application: 3.3.5
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
crashed while saving a file.  The file was mounted with sshfs.  I was also listening to music on that mount and had no problems with it.  Someone else had the same backtrace and said that they had tried saving a readonly file, but there is no reason why the file should have been in a read only mode.

 -- Backtrace:
Application: Kate (kate), signal: Segmentation fault
[KCrash Handler]
#6  0x00ad38e5 in QString::size (this=0xa5dad88, other=...) at ../../include/QtCore/../../src/corelib/tools/qstring.h:104
#7  QString::operator== (this=0xa5dad88, other=...) at tools/qstring.cpp:1912
#8  0x045c7daf in KDirWatchPrivate::Entry::findSubEntry (this=0x9c1e550) at ../../kio/kio/kdirwatch_p.h:157
#9  KDirWatchPrivate::inotifyEventReceived (this=0x9c1e550) at ../../kio/kio/kdirwatch.cpp:297
#10 0x045c94cb in KDirWatchPrivate::qt_metacall (this=0x9c1e550, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfa728d8) at ./kdirwatch_p.moc:75
#11 0x00b96263 in QMetaObject::activate (sender=0x9c11d90, from_signal_index=4, to_signal_index=4, argv=0xbfa728d8) at kernel/qobject.cpp:3113
#12 0x00b96ec2 in QMetaObject::activate (sender=0x9c11d90, m=0xc718b0, local_signal_index=0, argv=0xbfa728d8) at kernel/qobject.cpp:3187
#13 0x00bd0503 in QSocketNotifier::activated (this=0x9c11d90, _t1=31) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#14 0x00b9ac87 in QSocketNotifier::event (this=0x9c11d90, e=0xbfa72c94) at kernel/qsocketnotifier.cpp:316
#15 0x00df6f54 in QApplicationPrivate::notify_helper (this=0x9aa0ab8, receiver=0x9c11d90, e=0xbfa72c94) at kernel/qapplication.cpp:4056
#16 0x00dfe67c in QApplication::notify (this=0xbfa72ffc, receiver=0x9c11d90, e=0xbfa72c94) at kernel/qapplication.cpp:3603
#17 0x0061d25a in KApplication::notify (this=0xbfa72ffc, receiver=0x9c11d90, event=0xbfa72c94) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x00b806cb in QCoreApplication::notifyInternal (this=0xbfa72ffc, receiver=0x9c11d90, event=0xbfa72c94) at kernel/qcoreapplication.cpp:610
#19 0x00bab2ca in QCoreApplication::sendEvent (source=0x9aa3660) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 socketNotifierSourceDispatch (source=0x9aa3660) at kernel/qeventdispatcher_glib.cpp:110
#21 0x04ffee88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x05002730 in ?? () from /lib/libglib-2.0.so.0
#23 0x05002863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00bab02c in QEventDispatcherGlib::processEvents (this=0x9a889d8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#25 0x00e97be5 in QGuiEventDispatcherGlib::processEvents (this=0x9a889d8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x00b7ec79 in QEventLoop::processEvents (this=0xbfa72f34, flags=) at kernel/qeventloop.cpp:149
#27 0x00b7f0ca in QEventLoop::exec (this=0xbfa72f34, flags=...) at kernel/qeventloop.cpp:201
#28 0x00b8153f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x00df6dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#30 0x00445aed in kdemain () from /usr/lib/libkdeinit4_kate.so
#31 0x080485cb in _start ()

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

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-10 13:42:17 UTC
Merging with bug 224229. Regards

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