[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #12 from Tcll --- (In reply to Waqar Ahmed from comment #11) > Can you confirm if it still crashes with latest master? thanks for notifying ;) I can confirm with the latest kate-21.08.3-537 appimage the segfault appears to have been resolved :+1: I can now run multiple instances with behavior similar to mousepad :) also just to note, there's another issue where the process doesn't terminate after being closed. I no longer use kate now that I've found xed, but I'm at least glad to have confirmed the fix. ;) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #10 from Tcll --- yes as stated, it's the appimage, read the initial post for the build reference. ;) no it's not the latest, but it's within the week to at least be relevant... (I'm fairly certain this hasn't been tackled yet in the latest appimage, but I can transfer it over when my flash drive is free to test) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #8 from Tcll --- well I didn't have gdb on my system, and there wasn't a release available for download (only a source package) so I found this portable program called Insight which bundled gdb in it's release... anyways, I did some probing and may have found a lead on something related to one of the plugins: KF5WindowSystemX11Plugin.so I had to extract kate from the appimage to get it to work, but the attached image (kate_debug.png) may hopefully provide more info the green line is the moment of the crash `rdi+0x968` is a solid address hopefully that relates to an existing pointer in the source -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #7 from Tcll --- Created attachment 139272 --> https://bugs.kde.org/attachment.cgi?id=139272&action=edit Insight-gdb moment of kate crash -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #5 from Tcll --- well, it's not libX11 just had a friend copy their libX11.so.6.3.0 and when I ran kate with that, the same segfault happened so now I'm starting to think something's not installed that libX11 needs that I don't have installed... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #4 from Tcll --- I won't deny it could be a Void Linux issue, since my old Void machine runs Blender 2.8+ at 1.5FPS, where this one runs it just fine (updated) and it seems like it specifically has to do with libX11... which funny enough is something I'm RE-ing the protocol of for a project of my own that manages /tmp/.X11-unix/X0 directly as a bi-directional named pipe for performance and compatibility reasons. but unfortunately, I wouldn't know how to tell you what functions or such specifically seem to be missing from my specific patch to where it could potentially be worked around as an exception... my experience with C is rather lacking due to there not being a decent FOSS IDE for it... (CLion is quite a big load to cover) ;) ... I could probably patch it manually, and then deal with any XBPS issues later if I can find a decent download >.> (no internet on the target machine) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #2 from Tcll --- just checked dmesg: [317934.260387] AppRun.wrapped[9317]: segfault at 968 ip 7fdd88b2005a sp 0007ffe0e5e2d50 error 4 in libX11.so.6.4.0[7fdd88b0a000+8b000] [317934.260392] Code: 8b 47 58 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 8b 47 50 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 41 54 55 48 89 fd 48 83 ec 08 <48> 8b 87 68 09 00 00 48 85 c0 74 02 ff 10 48 89 ef e8 50 26 01 00 hopefully that helps -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] New: Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 Bug ID: 438509 Summary: Segfault in open window when opening a new window Product: kate Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: tcll5...@tutanota.com Target Milestone: --- SUMMARY When a Kate instance is running, running a new instance of Kate will cause the existing instance to segfault before the new instance opens. STEPS TO REPRODUCE 1. Open any text file in Kate (`-n` from file manager or command) 2. Open another text file in Kate (`-n` from file manager or command) 3. The previous window should close before the new window opens. OBSERVED RESULT When running the command to create an instance, Creating another instance causes the initial instance to close with: "Segmentation fault" while the 2nd instance replaces the first. EXPECTED RESULT 2 windows should be displayed SOFTWARE/OS VERSIONS Void Linux: 5.9.14_1 XFCE: 4.14 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 AppImage build #356 Files opened with: Nemo: 4.6.5 GNOME Terminal: 3.38.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 428501] New: configure default name colors without semantic highlights
https://bugs.kde.org/show_bug.cgi?id=428501 Bug ID: 428501 Summary: configure default name colors without semantic highlights Product: kdevplatform Version: 5.6.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sourceformatter Assignee: kdevelop-bugs-n...@kde.org Reporter: tcll5...@tutanota.com Target Milestone: --- semantics put way too many random colors on screen for me which makes things far too overwhelming to make out the syntax. I'd prefer things to be highlighted more like my themes in IDEA: (based on python's IDLE for an IDE I'm working on) light: https://ipfs.io/ipfs/QmYRT6cUFMehggtiecdGWSNxp2wmdrZejFCxVpb1Q2biH5?filename=getting_closer.png dark: https://ipfs.io/ipfs/QmVYwYVPEjEHXG4qq9GD2wxYwPSaooMW9ynh2p4TvcCQtM?filename=Collection_problems.png in KDevelop, if I disable semantic highlights (like I've done in IDEA as well), then all variable, class, and function names are normal text. in IDEA, `normal = param.call()` would be colored (my theme) `gray = navy.skyblue()` and params like `self` or `cls` (first method param) would be a light teal so you can see there's some colors going on also doc-comments aren't red (my theme) ;) -- You are receiving this mail because: You are watching all bug changes.
