Bug 495914

Summary:	Error running inkscape through the commandline in kate
Product:	[Applications] kate	Reporter:	Ryan <jryan.daniels>
Component:	application	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	christoph, waqar.17a
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Snap
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ryan 2024-11-07 09:09:35 UTC

#### Summary:
Inkscape works well through kitty and foot but I cannot run inkscape through the cli on kate.

#### Steps to reproduce:
- Running ```inkscape``` at the kitty/foot terminal launches the gui. (as expected).
- Running ```inkscape /path/to/file.svg``` at kitty/foot terminal launches with the file as expected.
- Running ```inkscape /path/to/file.svg``` with konsole on kate does not launch inkscape.

#### What happened?
- Running ```inkscape /path/to/file.svg``` cause inkscape to produce the following error on the terminal. ```inkscape: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory ``` (not expected).
- The same goes for jpeg, eps and pdf (those are all that I tested).
- Launching inkscape through the latex package ```includesvg``` causes the same error message as above.
- Running ```inkscape --debug-info``` causes the same error message.

#### What should have happened?
- Launching inkscape with the specified file

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
OS: Ubuntu 24.04.1 LTS x86_64
Host: ASUS TUF Gaming A15 FA506IH_FA506IH 1.0
Kernel: 6.8.0-48-generic
Uptime: 1 hour, 53 mins
Packages: 3015 (dpkg), 118 (snap)
Shell: bash 5.2.21
Resolution: 2560x1440
WM: sway
Terminal: kate
CPU: AMD Ryzen 7 4800H with Radeon Graphics (16) @ 2.900GHz
GPU: AMD ATI Radeon RX Vega 6
GPU: NVIDIA GeForce GTX 1650 Mobile / Max-Q
Memory: 11259MiB / 39524MiB

ADDITIONAL INFORMATION

commands:
- kate
snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR
tracking: latest/stable
refresh-date: 13 days ago, at 18:26 CEST

Comment 1 Waqar Ahmed 2024-11-14 13:15:33 UTC

If you launch Kate from terminal, and then launch Inkscape from Kate's terminal does it work? I suspect you are launching Kate from GUI launcher and it doesn't have the proper enviornment set

Comment 2 Ryan 2024-11-14 13:42:52 UTC

(In reply to Waqar Ahmed from comment #1)
> If you launch Kate from terminal, and then launch Inkscape from Kate's
> terminal does it work? I suspect you are launching Kate from GUI launcher
> and it doesn't have the proper enviornment set

Hello Waqar
Thank you for the response. 
I tested and it does not change the outcome. Here is what I tried using kitty and foot terminal to launch kate.

``` kate ``` : The session launch screen pops up asking what session to launch. I select a session and then  run inkscape in the konsole. Same error message as the original description.
``` kate -n ``` : The session launch screen pops up asking what session to launch. I select a session and then  run inkscape in the konsole.  Same error message as the original description.
``` kate --new ``` : The session launch screen pops up asking what session to launch. I select a session and then  run inkscape in the konsole.  Same error message as the original description.
``` kate --start <session_name> ``` : The requested session is started and then I run  inkscape in the konsole.  Same error message as the original description.

Ryan

Comment 3 Waqar Ahmed 2024-11-14 13:48:52 UTC

Then maybe its because you are using the snap package.

Nothing we(kate) can do about I think.

Comment 4 Christoph Cullmann 2024-11-17 19:05:44 UTC

Yeah, I don't see how that can properly work in a container.

Comment 5 Christoph Cullmann 2024-11-23 15:13:11 UTC

Don't see that we can fix that, this is the drawback of containers.