[konversation] [Bug 414727] Konversation crashes without any user input

[Friedrich W. H. Kossebau]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||kosse...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #2 from Friedrich W. H. Kossebau  ---
Thanks for the report. While the backtrace sadly lacks the needed info for the
chain of calls ending up in the crashing operator== call, the present calls and
the crash description hint this is the same cause as for the fixed bug 437595,
so closing as duplicate.

Please reopen if still seeing with versions >= 1.8.21080.

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

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

[konversation] [Bug 414727] Konversation crashes without any user input

[Sam Wilson]

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

Sam Wilson  changed:

   What|Removed |Added

 CC||s...@samwilson.id.au

--- Comment #1 from Sam Wilson  ---
I've noticed this happening usually a few minutes (or less) after waking the
system from sleep. Konversation looks fine, but as soon as I interact with it
it crashes with:

Connection broken with state 5 and error: "The remote host closed the
connection"
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = konversation path = /usr/bin pid = 197606
KCrash: Arguments: /usr/bin/konversation 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
[1]+  Stopped konversation
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
Unable to start Dr. Konqi
Re-raising signal for core dump handling.

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