Open project file with spaces in path doesn't work

Bug #1803995 reported by Oleg Endo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Undecided
Jean-Samuel Reynaud

Bug Description

It seems this is a new on on nightly.
Trying to start kicad with a .pro path/filename which contains spaces will not open the project file. I'm on ubuntu 18.

Application: kicad
Version: 6.0.0-rc1-unknown-240051f~84~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-38-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

By starting, do you mean from a command line? Do you escape spaces or quote the file name?

Revision history for this message
Oleg Endo (oleg.endo) wrote :

The problem happens when double-clicking a .pro file in the file manager (e.g. nautilus), or when starting kicad from the command line, not in the same directory as the .pro file.

Adding quotes when starting from command line doesn't change anything.

Starting kicad from within the same directory as the .pro file (where the path of the current directory contains spaces) works OK, it opens the .pro file.

Revision history for this message
Seth Hillbrand (sethh) wrote :

Is this still happening? I cannot recreate the issue in the current nightly build using XFCE.

Changed in kicad:
status: New → Incomplete
Revision history for this message
Oleg Endo (oleg.endo) wrote :

I've switched the PPA from kicad-nightly to the legacy nightly builds, as the installation of the former had several other issues. I don't know whether that was "the fix", but the problem went away for me since then.

Revision history for this message
Seth Hillbrand (sethh) wrote :

What is a legacy nightly build?

Revision history for this message
Oleg Endo (oleg.endo) wrote :

legacy nightly build is the nightly build but without any program suffix. The normal nightly build has the "-nightly" suffix .. so "kicad" becomes "kicad-nightly".

See also http://kicad-pcb.org/download/ubuntu/

Revision history for this message
Seth Hillbrand (sethh) wrote :

OK. That must be packaging-related then. Maybe the nightly build doesn't register the applications with the shell the same way.

@js-reynaud, can you shed some light on the shell difference here?

Revision history for this message
Jean-Samuel Reynaud (js-reynaud) wrote :

Yes It's a packaging issue specific to nightly build branch. Fix is commited.

Changed in kicad:
assignee: nobody → js-reynaud (js-reynaud)
status: Incomplete → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.