From: "bdju" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Tobias Geerinckx-Rice" <me@tobias.gr>,
"Giovanni Biscuolo" <g@xelera.eu>
Cc: 49460@debbugs.gnu.org
Subject: bug#49460: links not clickable in some qt programs (nheko, quaternion)
Date: Fri, 23 Jul 2021 11:28:44 -0500 [thread overview]
Message-ID: <CD0NTRVIP2WS.17QLC6CNSRCP4@masaki> (raw)
In-Reply-To: <aea14f962b82c09c2292f306ad52adf1@tobias.gr>
On Fri Jul 23, 2021 at 7:40 AM CDT, Tobias Geerinckx-Rice wrote:
> Some programmes have a bug where they save absolute file names
> instead of looking in $PATH every time. That should be fixed upstream.
This seems likely to be the issue. I rebooted in the last week and I
just noticed that links in nheko are working again. That makes me wonder
if updating my packages without restarting my session/computer is what
breaks the links, and then rebooting maybe fixes the functionality again
if it re-saves an absolute file name to the new spot after a reboot.
I just tested quaternion and I can currently open a link from there as
well.
guix (GNU Guix) c170abba4735a2c8a6845063fae8bf090975cbf9
4 days uptime.
One of the nheko devs says nheko doesn't do this, but that it calls a Qt
function. So, this could be a wider Qt issue, or "Qt weirdness", as
raingloom said earlier.
next prev parent reply other threads:[~2021-07-23 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 0:47 bug#49460: links not clickable in some qt programs (nheko, quaternion) bdju via Bug reports for GNU Guix
2021-07-09 1:15 ` raingloom
2021-07-12 6:37 ` Giovanni Biscuolo
2021-07-23 10:30 ` Giovanni Biscuolo
2021-07-23 12:40 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-07-23 16:10 ` Giovanni Biscuolo
2021-07-23 16:28 ` bdju via Bug reports for GNU Guix [this message]
2021-09-30 9:58 ` Hamzeh Nasajpour
2021-10-12 13:44 ` Robin Templeton
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=CD0NTRVIP2WS.17QLC6CNSRCP4@masaki \
--to=bug-guix@gnu.org \
--cc=49460@debbugs.gnu.org \
--cc=bdju@tilde.team \
--cc=g@xelera.eu \
--cc=me@tobias.gr \
/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.