https://bugs.kde.org/show_bug.cgi?id=405335

--- Comment #3 from brian <brian.glo...@gmail.com> ---
This is what the crash looks like when running from a terminal:

~ $ kdevelop
kdevplatform.shell: Could not load plugin "kdevperforce" , it reported the
error: "The variable P4CONFIG is not set. Is perforce installed on the system?"
Disabling the plugin now.
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
/bin/cat:
/home/brian/.local/share/kdevelop/sessions/{46199e2d-b3a6-4556-baa3-294f6e633a4f}/default.sh:
No such file or directory
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4181, resource
id: 23069278, major code: 40 (TranslateCoords), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4368, resource
id: 23069283, major code: 40 (TranslateCoords), minor code: 0
kf.kio.slaves.file: copy()
QUrl("file:///home/brian/projects/median/median.kdev4") to
QUrl("file:///tmp/kdevelop.SktrYI") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///home/brian/projects/qtqml.qml")
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6431, resource
id: 23069289, major code: 40 (TranslateCoords), minor code: 0


[[[[ crash happens here: ]]]]]]
kf.kio.slaves.file: copy()
QUrl("file:///home/brian/projects/median/median.kdev4") to
QUrl("file:///tmp/kdevelop.upNPEg") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdevelop path = /usr/bin pid = 8674
KCrash: Arguments: /usr/bin/kdevelop 
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 69 and type 'Read', disabling...

[1]+  Stopped                 kdevelop

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to