SUMMARY Kate 24.05.2 (current latest/edge version) does not run when launched. STEPS TO REPRODUCE 1. Launch Kate OBSERVED RESULT Kate doesn't run. EXPECTED RESULT Kate runs. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: openSUSE Leap 15.5, N/A (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: 5.15.12 ADDITIONAL INFORMATION Kate 23.08.4 (current latest/stable version) runs normally. LXQt 1.2 I'm unsure whether or not Kate or its snap exclusively support KDE Plasma, but I haven't been informed by the Kate/KDE Snapcraft page, the tracker or Kate itself about it. Thanks for the awesome text editor! Full terminal output: /snap/kate/175/usr/bin/kate: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory
This is now happening to latest/stable (currently 24.05.2), but not latest/candidate (currently 23.08.4).
Correction: I'm using LXQt 1.4, not 1.2.
Hi, this makes no good impression, could we have some basic auto testing for the snaps? Like at least start the app with all plugins enabled?
*** Bug 491255 has been marked as a duplicate of this bug. ***
*** Bug 491892 has been marked as a duplicate of this bug. ***
*** Bug 492151 has been marked as a duplicate of this bug. ***
Hi, Kate is classic so it will use host libraries if they are missing from snap. So when I tested it ( which I do ) I must have this lib installed because it worked. I am only one person with one computer and can't possibly test every possible configuration out there. I am working on 24.08 and will ensure this is fixed. Please assign snap bugs to me so I am made aware quicker. Thanks. Scarlett
please test the latest in --candidate
(In reply to Scarlett Moore from comment #8) > please test the latest in --candidate Just tested Kate 24.08.0, from the Snap store. FYI I am using Ubuntu 22.04 $ sudo snap info kate ... channels: latest/stable: 24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.0 2024-09-05 (181) 2GB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic installed: 24.08.0 (181) 2GB classic And it crashes immediately when I click "open folder" or "open file" as I original created a bug for that issue which then got merged into this one. I also tried installing directly from the command line with: $ sudo snap install kate --channel=latest/candidate --classic Same result, crashes when "open file" or "open folder" is clicked. I also tried running it from the command line with: $ snap run kate hoping I might see some additional output about the crash in the terminal but nothing. Is there a way to get more information about the crash somehow? I tried checking: $ journalctl -u snapd ... Sep 05 10:34:52 sol snapd[953]: api_snaps.go:427: Installing snap "kate" revision unset But nothing useful there. Let me know if there is someway for me to get you some more useful information about the problem I am having. Cheers, and thanks for the work on Kate. It is my favorite editor.
(In reply to chris.m.geroux from comment #9) > (In reply to Scarlett Moore from comment #8) > > please test the latest in --candidate There is no change for my side. I get the same error message as before. ``` /snap/kate/181/usr/bin/kate: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory ``` ``` snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/candidate refresh-date: today at 20:46 CEST channels: latest/stable: 24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.0 2024-09-05 (181) 2GB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic installed: 24.08.0 (181) 2GB classic ```
(In reply to Ryan from comment #10) > (In reply to chris.m.geroux from comment #9) > > (In reply to Scarlett Moore from comment #8) > > > please test the latest in --candidate > > There is no change for my side. I get the same error message as before. > ``` > /snap/kate/181/usr/bin/kate: error while loading shared libraries: > libpcre.so.3: cannot open shared object file: No such file or directory > ``` > ``` > snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR > tracking: latest/candidate > refresh-date: today at 20:46 CEST > channels: > latest/stable: 24.05.2 2024-08-04 (177) 2GB classic > latest/candidate: 24.08.0 2024-09-05 (181) 2GB classic > latest/beta: ↑ > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > installed: 24.08.0 (181) 2GB classic > ``` Thank you for all the hard work!
Thanks for testing, it is clear I have to change my approach to creating the Kate snap. It is a different kind of beast being --classic. I will start on this in the morning. Thanks for your patience everyone. Scarlett
(In reply to Scarlett Moore from comment #8) > please test the latest in --candidate Same results
(In reply to Ryan from comment #10) > (In reply to chris.m.geroux from comment #9) > > (In reply to Scarlett Moore from comment #8) > > > please test the latest in --candidate > > There is no change for my side. I get the same error message as before. > ``` > /snap/kate/181/usr/bin/kate: error while loading shared libraries: > libpcre.so.3: cannot open shared object file: No such file or directory > ``` > ``` > snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR > tracking: latest/candidate > refresh-date: today at 20:46 CEST > channels: > latest/stable: 24.05.2 2024-08-04 (177) 2GB classic > latest/candidate: 24.08.0 2024-09-05 (181) 2GB classic > latest/beta: ↑ > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > installed: 24.08.0 (181) 2GB classic > ``` After seeing the path you used to run kate when installed as a snap I found a similar path and gave it a try: $ /snap/kate/181/usr/bin/kate --version /snap/kate/181/usr/bin/kate: error while loading shared libraries: libkateprivate.so.24.08.0: cannot open shared object file: No such file or directory Similar but slightly different error.
I noticed there was a new version of the kate latest/candidate snap out a few days ago. Thought I would give it a try. $ sudo snap info kate ... snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/candidate refresh-date: today at 11:12 ADT channels: latest/stable: 24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.1 2024-09-15 (182) 509MB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic installed: 24.08.1 (182) 509MB classic $ /snap/kate/182/usr/bin/kate --version qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Aborted (core dumped)
(In reply to chris.m.geroux from comment #15) > I noticed there was a new version of the kate latest/candidate snap out a > few days ago. Thought I would give it a try. > > $ sudo snap info kate > ... > snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR > tracking: latest/candidate > refresh-date: today at 11:12 ADT > channels: > latest/stable: 24.05.2 2024-08-04 (177) 2GB classic > latest/candidate: 24.08.1 2024-09-15 (182) 509MB classic > latest/beta: ↑ > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > installed: 24.08.1 (182) 509MB classic > > $ /snap/kate/182/usr/bin/kate --version > qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in "" > This application failed to start because no Qt platform plugin could be > initialized. Reinstalling the application may fix this problem. > > Aborted (core dumped) I'm getting the same error
Wonder if the snap could be tested inside a virtual box VM (or similar) with a fresh linux OS installed on it so there are no extra dev libs or something installed there. Maybe there is an easier way to do similar testing? While setting up such a VM would have a little initial overhead, it might speed up the dev-test cycle a bit in the long term.
Hello --candidate is testing. Obviously it hasn't passed QA. I am trying to work out the new failure. Thanks, Scarlett
$ snap info kate ... refresh-date: today at 16:56 ADT channels: latest/stable: 24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.1 2024-09-20 (183) 580MB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic installed: 24.08.1 (183) 580MB classic $ /snap/kate/183/usr/bin/kate --version /snap/kate/183/usr/bin/kate: error while loading shared libraries: libkateprivate.so.24.08.1: cannot open shared object file: No such file or directory
Please try build 184 in --candidate.
(In reply to Scarlett Moore from comment #20) > Please try build 184 in --candidate. Now I'm getting this: /snap/kate/184/usr/bin/kate: error while loading shared libraries: libffi.so.8: cannot open shared object file: No such file or directory
Ugh. Works for me of course. So it looks like I am back to the drawing board. Using packages creates a bit problem as --classic snaps apparently uses -rpath which means a huge unmaintainable list of libraries that have to be patched with patchelf. Kate developers don't want this, and I agree with them. So one last approach before I give up, is to build all the dependencies from source and enable patchelf at build time. This will take some time.. sorry
Hmm, I think better we just be a 'normal' snap that having more of this issues. I must confess I not even know why one needs Snaps and Flatpaks, given one of them should be enough to work on 'all major' distros.
Is the classic snap needed to allow read/writing to the file systems? Might be hard to edit files otherwise, though maybe I am wrong. https://askubuntu.com/questions/917049/what-is-the-classic-mode-of-snap-and-why-do-some-snaps-not-install-without-it
How were snaps being done before with the 23 version of Kate, they seemed to work well. Has something changed that those methods couldn't be used any more?
Are their flatpacks for Kate? Snaps are supported by ubuntu out of the box.. but I could probably use flatpacks if that is available.
(In reply to chris.m.geroux from comment #26) > Are their flatpacks for Kate? Snaps are supported by ubuntu out of the box.. > but I could probably use flatpacks if that is available. I think we just moved our flatpak out of beta.
(In reply to chris.m.geroux from comment #24) > Is the classic snap needed to allow read/writing to the file systems? Might > be hard to edit files otherwise, though maybe I am wrong. > https://askubuntu.com/questions/917049/what-is-the-classic-mode-of-snap-and- > why-do-some-snaps-not-install-without-it I would hope snaps still allow to give permissions to access the home and Co., if not that would be strange, Flatpak does that.
I just refreshed the snap and kate is now up and running (the icons are working too which is new ). Thank you for getting this sorted!! ``` snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/candidate refresh-date: today at 21:38 CEST channels: latest/stable: 24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.1 2024-09-20 (184) 580MB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic installed: 24.08.1 (184) 580MB classic ```
(In reply to Christoph Cullmann from comment #28) > (In reply to chris.m.geroux from comment #24) > > Is the classic snap needed to allow read/writing to the file systems? Might > > be hard to edit files otherwise, though maybe I am wrong. > > https://askubuntu.com/questions/917049/what-is-the-classic-mode-of-snap-and- > > why-do-some-snaps-not-install-without-it > > I would hope snaps still allow to give permissions to access the home and > Co., if not that would be strange, Flatpak does that. Yes there is a plug that allows $HOME
$ snap info kate channels: latest/stable: 24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.1 2024-09-20 (184) 580MB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic installed: 24.05.2 (177) 2GB classic $ /snap/kate/184/usr/bin/kate --version /snap/kate/184/usr/bin/kate: error while loading shared libraries: libkateprivate.so.24.08.1: cannot open shared object file: No such file or directory. I can, however, start kate up from the applications screen. However, as soon as I click "open file" or "open folder" it crashes. This is similar to behaviour I saw with 24.05.2 so I am not sure this is new. I have to admit I haven't been testing this for all versions I have tried recently though so perhaps it could have been different for some.
(In reply to chris.m.geroux from comment #31) > $ snap info kate > channels: > latest/stable: 24.05.2 2024-08-04 (177) 2GB classic > latest/candidate: 24.08.1 2024-09-20 (184) 580MB classic > latest/beta: ↑ > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > installed: 24.05.2 (177) 2GB classic > $ /snap/kate/184/usr/bin/kate --version > /snap/kate/184/usr/bin/kate: error while loading shared libraries: > libkateprivate.so.24.08.1: cannot open shared object file: No such file or > directory. > > I can, however, start kate up from the applications screen. However, as soon > as I click "open file" or "open folder" it crashes. This is similar to > behaviour I saw with 24.05.2 so I am not sure this is new. I have to admit I > haven't been testing this for all versions I have tried recently though so > perhaps it could have been different for some. Note, I had both 24.05.2 and 24.08.1 installed. However, same result when only 24.05.2 snap installed. I also had the deb version installed as that is currently the only version I can run. I tested out uninstalling that and only having 24.08.1 installed, thinking maybe it is finding the wrong library version somewhere, but same result.
$ snap info kate channels: latest/stable: 24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.1 2024-09-25 (185) 575MB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic $ /snap/kate/185/usr/bin/kate --version /snap/kate/185/usr/bin/kate: error while loading shared libraries: libkateprivate.so.24.08.1: cannot open shared object file: No such file or directory If I run it from the applications screen, it starts but crashes as soon as I click open folder or open file.
(In reply to Ryan from comment #29) > I just refreshed the snap and kate is now up and running (the icons are > working too which is new ). > Thank you for getting this sorted!! > > ``` > snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR > tracking: latest/candidate > refresh-date: today at 21:38 CEST > channels: > latest/stable: 24.05.2 2024-08-04 (177) 2GB classic > latest/candidate: 24.08.1 2024-09-20 (184) 580MB classic > latest/beta: ↑ > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > installed: 24.08.1 (184) 580MB classic > ``` It is broken again. I spent a week using the working version and everything worked perfectly. After refreshing the snap, it will now no longer start up again. The error message on the terminal is 'segmentation fault'
New qt6/kf6 content pack. Fix is in candidate and will land in stable in the morning.
Released to stable
(In reply to chris.m.geroux from comment #33) > $ snap info kate > > channels: > latest/stable: 24.05.2 2024-08-04 (177) 2GB classic > latest/candidate: 24.08.1 2024-09-25 (185) 575MB classic > latest/beta: ↑ > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > > $ /snap/kate/185/usr/bin/kate --version > /snap/kate/185/usr/bin/kate: error while loading shared libraries: > libkateprivate.so.24.08.1: cannot open shared object file: No such file or > directory > > If I run it from the applications screen, it starts but crashes as soon as I > click open folder or open file. Please don't run snaps like $ /snap/kate/185/usr/bin/kate --version as it will not bring in the environment variables and that is why you keep getting shared lib errors. snap run kate ensures it gets the desktop launcher to properly set env. Please run that in a terminal and provide me with output when it crashes. Thanks
(In reply to Ryan from comment #34) > (In reply to Ryan from comment #29) > > I just refreshed the snap and kate is now up and running (the icons are > > working too which is new ). > > Thank you for getting this sorted!! > > > > ``` > > snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR > > tracking: latest/candidate > > refresh-date: today at 21:38 CEST > > channels: > > latest/stable: 24.05.2 2024-08-04 (177) 2GB classic > > latest/candidate: 24.08.1 2024-09-20 (184) 580MB classic > > latest/beta: ↑ > > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > > installed: 24.08.1 (184) 580MB classic > > ``` > > It is broken again. > I spent a week using the working version and everything worked perfectly. > After refreshing the snap, it will now no longer start up again. The error > message on the terminal is 'segmentation fault' Just to clarify, I am getting the same new problem with candidate and stable since the refresh.
(In reply to Ryan from comment #38) snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/stable refresh-date: today at 16:53 CEST channels: latest/stable: 24.08.1 2024-09-28 (187) 575MB classic latest/candidate: 24.08.1 2024-09-27 (187) 575MB classic latest/beta: ↑ latest/edge: 24.08.1 2024-09-27 (188) 2GB classic installed: 24.08.1 (187) 575MB classic
I republished build 184 that worked to stable branch. Please use that. Something is terribly wrong with recent builds and I won't get to it until Monday.
(In reply to Scarlett Moore from comment #40) > I republished build 184 that worked to stable branch. Please use that. > Something is terribly wrong with recent builds and I won't get to it until > Monday. I have refreshed and it works. Thaaaaanks!
$ snap info kate ... snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/candidate refresh-date: today at 09:15 ADT channels: latest/stable: 24.08.1 2024-09-28 (184) 580MB classic latest/candidate: 24.08.1 2024-09-28 (189) 575MB classic latest/beta: ↑ latest/edge: 24.08.1 2024-09-27 (188) 2GB classic installed: 24.08.1 (189) 575MB classic I normally don't run kate with something like /snap/kate/181/usr/bin/kate , but was hoping it would provide some more information about the problem by running at the command line and started running it that way after I saw someone else do that. If I do $ snap run kate It runs without the shared library issues, as you mentioned it would. It starts up, but similarly to before as soon as I try to open a file or folder it crashes. Is there some way to get some more information about why it is crashing that I could provide to you guys to help you troubleshoot the problem?
Are there logs stored somewhere that might have a error message in them?
Noticed a new kate snap version, so gave it a try. $ snap info kate ... commands: - kate snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/candidate refresh-date: today at 11:29 ADT channels: latest/stable: 24.08.1 2024-09-28 (184) 580MB classic latest/candidate: 24.08.2 2024-10-07 (190) 575MB classic latest/beta: ↑ latest/edge: 24.08.1 2024-09-27 (188) 2GB classic installed: 24.08.2 (190) 575MB classic $ snap run kate It starts up fine, but crashes when I click on "Open File", "Open Folder" or "New File" then "File" -> "Save" . Seems like as soon as it needs to do something involving accessing the file system it crashes. This bug originally dealt with crashing at startup, however, this issue seems to be related to accessing the file system from Kate. Should this be a separate bug report. Personally I don't care which way it is dealt with just wondering if creating a separate bug report for it would be helpful since it seems a bit different than the original bug reported?
latest/candidate (190) now outputs this, please let me know if I should file a separate bug report and mark this as resolved: > *** stack smashing detected ***: terminated > Aborted (core dumped)
(In reply to cirnos from comment #45) > latest/candidate (190) now outputs this, please let me know if I should file > a separate bug report and mark this as resolved: > > > *** stack smashing detected ***: terminated > > Aborted (core dumped) Up to you how you would like to track it. How do you see that message?
Apologies. I was in the hospital again. Please install --candidate and snap run kate for me. It runs and opens and saves files in the home directory fine for me. Scarlett
(In reply to Scarlett Moore from comment #47) > Apologies. I was in the hospital again. Please install --candidate and snap > run kate for me. It runs and opens and saves files in the home directory > fine for me. > Scarlett No need to apologise, hope it wasn't anything too serious. $ snap install --candidate --classic kate $ snap info kate name: kate summary: KDE Advanced Text Editor publisher: KDE✓ store-url: https://snapcraft.io/kate contact: https://bugs.kde.org/enter_bug.cgi?product=neon&component=Snaps license: LGPL-2.1+ description: | Kate is a multi-document, multi-view text editor by KDE. It features stuff like codefolding, syntaxhighlighting, dynamic word wrap, an embedded console, an extensive plugin interface and some preliminary scripting support. Features: - MDI, window splitting, window tabbing - Spell checking - CR, CRLF, LF newline support - Encoding support (utf-8, utf-16, ascii etc.) - Encoding conversion - Regular expression based find & replace - Powerful syntax highlighting and bracket matching - Code and text folding - Infinite undo/redo support - Block selection mode - Auto indentation - Auto completion support - Shell integration - Wide protocol support (http, ftp, ssh, webdav etc.) using kioslaves - Plugin architecture for the application and editor component - Customizable shortcuts - Integrated command line - Scriptable using JavaScript commands: - kate snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/candidate refresh-date: today at 10:10 ADT channels: latest/stable: 24.08.1 2024-09-28 (184) 580MB classic latest/candidate: 24.08.2 2024-10-16 (191) 575MB classic latest/beta: ↑ latest/edge: 24.08.1 2024-09-27 (188) 2GB classic installed: 24.08.2 (191) 575MB classic $ snap run kate It still crashes when I go to "File"->"Open" or "File"->"Open Folder". However, this time I happened to run it in a directory with files to edit and noticed the file browser/project open on the left. I can click on files from that list and edit and save them. Either using "ctrl+s", my usual, or "File"->"Save". "File"->"Open Recent"->then pick a file listed, also works to open a file. I also tried "Open Folder" and "Open File" from the "Welcome" screen and that also crashed. I just tried "File"->"Save As" and it crashed also. This then suggests that it maybe it isn't simply about accessing the file system at all but something a bit more subtle. Thanks for your work.
Refresh my memory, what distribution are you on?
(In reply to Scarlett Moore from comment #49) > Refresh my memory, what distribution are you on? Ubuntu 22.04.5, Jammy Jellyfish
(In reply to Scarlett Moore from comment #47) > Apologies. I was in the hospital again. Please install --candidate and snap > run kate for me. It runs and opens and saves files in the home directory > fine for me. > Scarlett Installing libffi8 from my system's Main Repository works around the issue: > $ snap run kate > /snap/kate/191/usr/bin/kate: error while loading shared libraries: libffi.so.8: cannot open shared object file: No such file or directory Also, I am now running openSUSE Leap 15.6, not 15.5.
The latest candidate (192) works normally now, but it's still happening to stable (184).
I have promoted the lasted candidate to stable.
(In reply to Scarlett Moore from comment #53) > I have promoted the lasted candidate to stable. Can confirm it works now, thanks!
(In reply to Scarlett Moore from comment #49) > Refresh my memory, what distribution are you on? Can we move this to a new bug. It is unrelated to this one and I want to keep it separate in case others are affected. I haven't yet been able to sort this out.
(In reply to Scarlett Moore from comment #55) > (In reply to Scarlett Moore from comment #49) > > Refresh my memory, what distribution are you on? > > Can we move this to a new bug. It is unrelated to this one and I want to > keep it separate in case others are affected. I haven't yet been able to > sort this out. I just tried the new 192 candidate and it no longer seems to crash when opening a file or folder. So maybe this is solved? Not sure if you did something that fixed this issue, or something changed on my end, but it seems to work now.
Fantastic!