https://bugs.kde.org/show_bug.cgi?id=382733
Mate Soos changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=427227
--- Comment #9 from Mate Soos ---
Ah! Nce! Sorry, I was somehow convinced it must be my wrong setup
somehow that made the UI crash under GDB. That crash was making it *really*
hard for me to submit a backtrace, to be honest, so I'd be really
https://bugs.kde.org/show_bug.cgi?id=427246
Mate Soos changed:
What|Removed |Added
CC||soos.m...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=427227
--- Comment #7 from Mate Soos ---
Hey,
Francis Herne has already figured it out thankfully and he has an upcoming
fix in the next version. In the meanwhile, I disabled Python parsing and
now it doesn't crash :) So this can be closed now. Thanks to all
https://bugs.kde.org/show_bug.cgi?id=427227
--- Comment #5 from Mate Soos ---
Thanks for getting back to me! I worked a lot to get the core to be dumped (oh,
how I kinda hate/love systemd...), glad that it confirmed your suspicion. I
also have now disabled the Python parser and indeed
https://bugs.kde.org/show_bug.cgi?id=427227
--- Comment #3 from Mate Soos ---
Created attachment 132061
--> https://bugs.kde.org/attachment.cgi?id=132061=edit
GDB backtrace
Ah, I managed to fix the core issue, so now I am getting a core and can check
it in GDB. Yay! I have to say, fight
https://bugs.kde.org/show_bug.cgi?id=427227
Bug ID: 427227
Summary: kdevelop parser crashes with SEGFAULT
Product: kdevelop
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #6 from Mate Soos <ms...@gdssecurity.com> ---
Wow, thanks! Great work :) Owe you a beer! Let me know if you are coming to CCC
(34C3) conf. Cheers,
Mate
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #3 from Mate Soos <ms...@gdssecurity.com> ---
Created attachment 108189
--> https://bugs.kde.org/attachment.cgi?id=108189=edit
hwinfo output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #2 from Mate Soos <ms...@gdssecurity.com> ---
Cool, thanks for picking this up. I was pretty happy I could run valgrind to be
honest. It's nice trace I think.
Using:
msoos@msoos: pacman -Qs "kwin*"
[...]
local/kwin
https://bugs.kde.org/show_bug.cgi?id=385397
Bug ID: 385397
Summary: Crash (segfault) on startup at memmove
Product: kwin
Version: 5.10.5
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=382733
--- Comment #4 from Mate Soos <soos.m...@gmail.com> ---
,Oh, OK. I didn't know that -- I exported it and it didn't import back, maybe I
did something wrong :S Can you check for me that it does indeed import back?
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=382733
--- Comment #2 from Mate Soos <soos.m...@gmail.com> ---
I think it's a really bad idea to have 2 files exported, a .kwl and a .salt.
Inevitably, people will forget the salt. I strongly suggest to merge the two.
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=382733
Bug ID: 382733
Summary: kwallet export does not save salt file
Product: frameworks-kwallet
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
14 matches
Mail list logo
