Package: xdg-utils
Version: 1.1.0~rc1+git20111210-7.4
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Create one file and one folder with names that contain double quotes '"':

        /tmp/"file".txt         (is a FILE)
        /tmp/"folder"           (is a FOLDER)

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Calling xdg-open on both of these paths.

   * What was the outcome of this action?

In the case of the file, xdg-open launched an editor/viewer for the file --
this is the expected and correct behaviour.

In the case of the directory, xdg-open launched a file browser with a BOGUS
PATH:
/tmp/"folder" got opened as /tmp/fileW55Y0D/ with subsequent invocations of
xdg-open
yielding different bogus paths of the same format (prefix + 6 character
suffix).

In both cases, special attention was being given to use proper shell quoting:

        xdg-open \"file\".txt
        xdg-open \"folder\"

The quoting works properly with other applications.

The result is the same regardless of whether relative or absolute paths are
being used.

   * What outcome did you expect instead?

In the case of the directory, the file browser application should be opened
with the
path to the specified folder instead of a bogus path.



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

xdg-utils depends on no packages.

Versions of packages xdg-utils recommends:
ii  libfile-mimeinfo-perl  0.26-1
ii  libnet-dbus-perl       1.0.0-2+b2
ii  libx11-protocol-perl   0.56-6
ii  x11-utils              7.7+2
ii  x11-xserver-utils      7.7+3+b1

Versions of packages xdg-utils suggests:
pn  gvfs-bin  <none>

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to