Application that crashed: kate
Version of the application: 3.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 188.8.131.52-64.fc11.i586 i686
Distribution: "Fedora release 11 (Leonidas)"
Application: Kate (kate), signal: Segmentation fault
#6 0x0626ce00 in QDataStream::operator>>(int&) () from /usr/lib/libQtCore.so.4
#7 0x06815e5d in KServiceFactory::KServiceFactory() () from /usr/lib/libkdecore.so.5
#8 0x068161ac in KServiceFactory::self() () from /usr/lib/libkdecore.so.5
#9 0x0680dc05 in KService::serviceByDesktopName(QString const&) () from /usr/lib/libkdecore.so.5
#10 0x07fd06f0 in KTextEditor::EditorChooser::editor(QString const&, bool) () from /usr/lib/libktexteditor.so.4
#11 0x07e43cb1 in ?? () from /usr/lib/libkateinterfaces.so.4
#12 0x07e35317 in KateApp::KateApp(KCmdLineArgs*) () from /usr/lib/libkateinterfaces.so.4
#13 0x004ae5a7 in kdemain () from /usr/lib/libkdeinit4_kate.so
#14 0x0804864b in _start ()
Reported using DrKonqi
This is the first time since the installation of Fedora 11 that Kate has been accessed via SSH X forwarding. Immediately following this crash I attempted to duplicate the results by using the exact command and syntax, however the command functioned normally thus far. I will begin testing various Kate functions (editing, saving, opening, searching, etc) to see if any of these functions returns errors. I will include any data gathered from bug report generator and command line.
I don't really know the internals of the SSH X forwarding, but, could that also mean that you were running the app as a different user? That would be bug 211401. Thanks
I have attempted to recreate the bug, to no avail. It appears to occur only on the first use attempt, and is limited to Kate. All other X applications via forwarding do not experience this issue. ausearch of the appropriate log archive reveals nothing that suggests selinux to be the culprit. I have since upgraded to 12, still attempting to recreate the glitch.
Thanks for looking into this, and I will both check out the above bug report and keep you posted.
*** This bug has been marked as a duplicate of bug 211401 ***