This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Desktop file won't load application

Tags: None
(comma "," separated)
gone_bush
Registered Member
Posts
6
Karma
0
OS

Desktop file won't load application

Thu Nov 19, 2020 11:19 pm
Sorry if this is not the right place to post this - admins: please move as necessary.

The following .desktop won't load the nominated application. The .xsession-errors file contains:

Code: Select all
An error occured while setting up locale.
You may need to reconfigure the missing locales, likely by running the "locale-gen" and "dpkg-reconfigure locales" commands.
SuperSlicer will now terminate.

locale::facet::_S_create_c_locale name not valid

When the run from the command line, I get

Code: Select all
$ superslicer
create settings  print.ui
create settings  filament.ui
create settings  sla_print.ui
create settings  sla_material.ui
create settings  printer_fff.ui
create settings  extruder.ui
[2020-11-20 09:02:43.206525] [0x00007fa7798fb700] [error]   Error getting: `https://files.prusa3d.com/wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaSlicer.version`: HTTP 0, Problem with the SSL CA cert (path? access rights?):
error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
[Error 77]

but the application runs.

The desktop file:

Code: Select all
$ cat /usr/share/applications/superslicer.desktop
[Desktop Entry]
Categories=Graphics;3DGraphics;Engineering;
Comment=Superslicer software - port of prusa-slicer
Exec=/usr/local/bin/superslicer %F
GenericName=3D Printing Software
Icon=prusa-slicer
Keywords=3D;Printing;Slicer;slice;3D;printer;convert;gcode;stl;obj;amf;SLA
MimeType=model/stl;
Name=SuperSlicer
StartupNotify=false
StartupWMClass=super-slicer
Terminal=false
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-Desktop-File-Install-Version=0.24
X-KDE-RunOnDiscreteGpu=false
X-KDE-SubstituteUID=false
X-KDE-Username=


What am I doing wrong?

Kevin
davost
Registered Member
Posts
1
Karma
0
I had the same issue with PrusaSlicer (common code I guess). What ended up working for me was to supply the locale as part of the command:
Code: Select all
LC_ALL=en_US.utf-8 <path to prusa/super-slicer>


I hope it solves your issue.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]