https://bugs.kde.org/show_bug.cgi?id=402793
Nate Graham changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/fram
|
https://bugs.kde.org/show_bug.cgi?id=402793
--- Comment #11 from Christoph Cullmann ---
Git commit ff6a3d40270a372a7b8d0d2e59d15e19b4b81dd0 by Christoph Cullmann, on
behalf of David Edmundson.
Committed on 23/08/2020 at 12:22.
Pushed by cullmann into branch 'master'.
Fix potential crash deleting
https://bugs.kde.org/show_bug.cgi?id=402793
--- Comment #10 from Patrick Silva ---
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f7c64793800
(LWP 1736))]
[KCrash Handler]
#6 wl_proxy_get_listener (proxy=proxy@entry=0x0
https://bugs.kde.org/show_bug.cgi?id=402793
--- Comment #8 from Patrick Silva ---
It's harder to reproduce on neon unstable and I'm getting apparently different
backtraces.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402793
--- Comment #9 from Patrick Silva ---
Thread 7 (Thread 0x7fa545500700 (LWP 19065)):
#0 0x7fa564b729f3 in futex_wait_cancelable (private=,
expected=0,
futex_word=0x5580ffbec018) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_co
https://bugs.kde.org/show_bug.cgi?id=402793
--- Comment #7 from David Edmundson ---
OOOH!
BreezeShadows is doing a roundtrip (Our registry usage is so broken)
This means we are processing drag move events processes at a really really
weird time from a Qt POV.
Picking out key points from a longe
https://bugs.kde.org/show_bug.cgi?id=402793
--- Comment #6 from David Edmundson ---
I might have a different bug with the same symptom, my stack trace isn't
matching 'm having an issue with the platform window getting destroyed by a
previous move event, not in handling the data_device_enter.
In
https://bugs.kde.org/show_bug.cgi?id=402793
Patrick Silva changed:
What|Removed |Added
Version|18.12.0 |20.07.80
Summary|Sometimes Dolphin c
