all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: Hartmut Goebel <h.goebel@crazy-compilers.com>, 38926@debbugs.gnu.org
Subject: bug#38926: pcmanfm-qt unable to open files by double click
Date: Sun, 5 Jan 2020 23:37:45 +0100	[thread overview]
Message-ID: <20200105233729.10add7f5@scratchpost.org> (raw)
In-Reply-To: <2e3e1ced-2c3c-4084-817d-ac19aca5562d@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Hi Reza,

I wouldn't change PATH in a *file manager*, of all programs.  That will make the
user hate his life should it ever pick up the wrong indirect child executable
because of that PATH change--which is opaque the user.

(Otherwise, often, your solution would have been the correct one--especially when
there are no indirect children)

Please try to find the actual source code line where it invokes
gio-launch-desktop .

For glib programs, I would suggest invoking

  gdb --args $(which pcmanfm-qt) --g-fatal-warnings

then

  r

and then wait until it crashes, then

  bt

.  It will tell you the exact location in the source code where the invocation
is.

No idea how to do that with Qt programs.  Hartmut?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-01-05 22:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04 20:24 bug#38926: pcmanfm-qt unable to open files by double click Reza Alizadeh Majd
2020-01-05  9:56 ` Danny Milosavljevic
2020-01-05 13:52   ` Reza Alizadeh Majd
2020-01-05 22:37     ` Danny Milosavljevic [this message]
2020-01-05 22:57       ` Danny Milosavljevic
2020-01-06 10:06         ` Danny Milosavljevic
2020-01-06 16:38         ` Danny Milosavljevic
2020-01-06 16:45           ` Reza Alizadeh Majd
2020-01-06 19:44             ` Danny Milosavljevic
2020-01-07  6:23               ` Reza Alizadeh Majd
2020-01-07  8:03                 ` Reza Alizadeh Majd
2020-01-07 11:19       ` Hartmut Goebel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200105233729.10add7f5@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=38926@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=r.majd@pantherx.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.