From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org links and Flatpak firefox
Date: Sun, 3 Jul 2022 10:46:39 +0700 [thread overview]
Message-ID: <t9r3f1$10i0$1@ciao.gmane.io> (raw)
In-Reply-To: <CAFdBzEoT_cFrtGt_ho1e2h9RxqqD96bcMCp5Y_E21Qkatg-5Wg@mail.gmail.com>
On 02/07/2022 23:03, Ken Mankoff wrote:
>
> I've just upgraded to Kubuntu 22.04. Firefox is no longer instsallable
> via apt so I chose flatpak over snap. Now when I C-c C-o
> (org-open-at-point) on a URL, Firefox comes to the foreground, but
> nothing else happens. The page does not load. If I 'xdg-open URL' then
> the URL loads, so the system outside of emacs does interact correctly
> with the flatpak app.
Please, seek for various messages reported during this action:
- Emacs *Messages* buffer (C-h C-e)
- Firefox console (Ctrl+Shift+J)
- stderr of the Firefox process, unsure where it can be expected for
flatpak apps: terminal application from which Firefox was initially
started, output of "journalctl --user", in earlier days X11 errors may
be saved to ~/.xsession-errors
- flatpak may have its own log file.
It is rather strange that Firefox receives some event, xdg-open works in
isolation, but not from Emacs. What does happen when
- `browse-url' is called from Emacs,
- a link is activated in an Org document when Firefox application is closed?
Notice that you did not specify which versions of Emacs and Org you have
installed (M-x org-version), and the source of the package: bundled with
emacs, elpa-org deb package, Emacs ELPA package, etc.
next prev parent reply other threads:[~2022-07-03 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 16:03 Org links and Flatpak firefox Ken Mankoff
2022-07-02 23:10 ` Tim Cross
2022-07-03 3:46 ` Max Nikulin [this message]
2022-07-03 13:25 ` Ken Mankoff
2022-07-05 15:16 ` Max Nikulin
2022-07-28 23:41 ` Ken Mankoff
2022-07-30 3:49 ` Tim Cross
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='t9r3f1$10i0$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).