GNU bug report logs -
#77415
Native Messaging in librewolf doesn't work
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 77415 in the body.
You can then email your comments to 77415 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 31 Mar 2025 19:44:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Konrad Hinsen <konrad.hinsen <at> fastmail.net>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Mon, 31 Mar 2025 19:44:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi everyone,
I noticed that librewolf is now in Guix, and tried to migrate from my
current installation via librewolf's Debian repository to a Guix-based
installation.
This works mostly fine, except for one point: in the Guix-built
librewolf, the Native Messaging implementation has some problem.
My setup:
- librewolf 136.0.4-1 (from commit
2e17b532ed659ed38c738f44f11c35a887bd31c0)
- PassFF extension (https://codeberg.org/PassFF/passff)
- PassFF host (https://codeberg.org/PassFF/passff-host)
- password-store from Guix
With this setup, PassFF signals an error
"Connection to the host app failed or returned an unexpected result!"
every time it is opened. Some debugging reveals that the Python script
from PassFF host is never run.
Running the apt-installed librewolf (same version), with everything else
exactly the same (same user profile), PassFF works fine.
Cheers,
Konrad.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 31 Mar 2025 20:19:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 77415 <at> debbugs.gnu.org (full text, mbox):
Hello Konrad,
I would like to confirm the same behavior on my end. This happens with
every native messaging extension I tried, doesn't seem to be just some.
Actually, it used to work, then after something updated in Guix it
stopped working. The same for Firefox from nonguix.
I have no idea how to debug this since Firefox apparently decided to
print the most helpful message ever for any and every error in the
native hosting! Sigh. That's why I haven't even reported it, because I
wanted to share at least some information about it, but could find
nothing. My only other idea was to look through the librewolf
compilation log, maybe it will print a warning about a missing/wrong
dependency etc.
Regards,
Rutherther
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 07 Apr 2025 14:09:01 GMT)
Full text and
rfc822 format available.
Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi all,
Did you try the guix passff-icecat package?
$ guix shell icecat-minimal passff-icecat
then you start icecat, and it works
Same if you replace icecat-minimal with mullvadbrowser or torbrowser.
With librewolf there is an extra step due to a librewolf package bug:
$ guix shell librewolf passff-icecat
then
- you start librewolf
- [extra step] you go to about:addons and enable passff
- then it works
As to why it does not work with your non-guix extension, I imagine it's
because your native-messaging-hosts path is wrong?
Did you try either
- ~/.librewolf/native-messaging-hosts
- $ICECAT_SYSTEM_DIR/native-messaging-hosts
?
Cheers,
Clément Lassieur
On Mon, Mar 31 2025, Rutherther via Bug reports for GNU Guix wrote:
> Hello Konrad,
>
> I would like to confirm the same behavior on my end. This happens with
> every native messaging extension I tried, doesn't seem to be just some.
> Actually, it used to work, then after something updated in Guix it
> stopped working. The same for Firefox from nonguix.
>
> I have no idea how to debug this since Firefox apparently decided to
> print the most helpful message ever for any and every error in the
> native hosting! Sigh. That's why I haven't even reported it, because I
> wanted to share at least some information about it, but could find
> nothing. My only other idea was to look through the librewolf
> compilation log, maybe it will print a warning about a missing/wrong
> dependency etc.
>
> Regards,
> Rutherther
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 07 Apr 2025 14:09:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 07 Apr 2025 14:57:02 GMT)
Full text and
rfc822 format available.
Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi Clément,
Clément Lassieur <clement <at> lassieur.org> writes:
> Hi all,
>
> Did you try the guix passff-icecat package?
>
> $ guix shell icecat-minimal passff-icecat
> then you start icecat, and it works
>
> Same if you replace icecat-minimal with mullvadbrowser or torbrowser.
>
> With librewolf there is an extra step due to a librewolf package bug:
>
> $ guix shell librewolf passff-icecat
> then
> - you start librewolf
> - [extra step] you go to about:addons and enable passff
> - then it works
>
> As to why it does not work with your non-guix extension, I imagine it's
> because your native-messaging-hosts path is wrong?
>
> Did you try either
> - ~/.librewolf/native-messaging-hosts
> - $ICECAT_SYSTEM_DIR/native-messaging-hosts
>
I think you've discovered the actual bug. The issue is that
.librewolf/native-messaging-hosts is not checked, instead
ICECAT_SYSTEM_DIR is, with no fallback even if it's empty. When I set
ICECAT_SYSTEM_DIR to $HOME/.librewolf all is working fine again.
Since I use Guix Home to symlink the native messaging hosts json file
anyway, I will change it on my end and am happy with that, but I still
think it's a packaging bug.
Thanks,
Rutherther
> ?
>
> Cheers,
> Clément Lassieur
>
>
> On Mon, Mar 31 2025, Rutherther via Bug reports for GNU Guix wrote:
>
>> Hello Konrad,
>>
>> I would like to confirm the same behavior on my end. This happens with
>> every native messaging extension I tried, doesn't seem to be just some.
>> Actually, it used to work, then after something updated in Guix it
>> stopped working. The same for Firefox from nonguix.
>>
>> I have no idea how to debug this since Firefox apparently decided to
>> print the most helpful message ever for any and every error in the
>> native hosting! Sigh. That's why I haven't even reported it, because I
>> wanted to share at least some information about it, but could find
>> nothing. My only other idea was to look through the librewolf
>> compilation log, maybe it will print a warning about a missing/wrong
>> dependency etc.
>>
>> Regards,
>> Rutherther
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 07 Apr 2025 14:57:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 07 Apr 2025 15:13:02 GMT)
Full text and
rfc822 format available.
Message #23 received at submit <at> debbugs.gnu.org (full text, mbox):
On Mon, Apr 07 2025, Rutherther via Bug reports for GNU Guix wrote:
> I think you've discovered the actual bug. The issue is that
> .librewolf/native-messaging-hosts is not checked, instead
> ICECAT_SYSTEM_DIR is, with no fallback even if it's empty. When I set
> ICECAT_SYSTEM_DIR to $HOME/.librewolf all is working fine again.
I don't think so, because on my computer,
$HOME/.librewolf/native-messaging-hosts/passff.json
works (without changing ICECAT_SYSTEM_DIR)
and if I remove that file it doesn't work anymore.
So just to make it clear: I can't reproduce the bug.
Cheers,
Clément
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Mon, 07 Apr 2025 15:13:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 07:12:01 GMT)
Full text and
rfc822 format available.
Message #29 received at 77415 <at> debbugs.gnu.org (full text, mbox):
Clément Lassieur <clement <at> lassieur.org> writes:
> On Mon, Apr 07 2025, Rutherther via Bug reports for GNU Guix wrote:
>
>> I think you've discovered the actual bug. The issue is that
>> .librewolf/native-messaging-hosts is not checked, instead
>> ICECAT_SYSTEM_DIR is, with no fallback even if it's empty. When I set
>> ICECAT_SYSTEM_DIR to $HOME/.librewolf all is working fine again.
>
> I don't think so, because on my computer,
>
> $HOME/.librewolf/native-messaging-hosts/passff.json
>
> works (without changing ICECAT_SYSTEM_DIR)
>
> and if I remove that file it doesn't work anymore.
>
> So just to make it clear: I can't reproduce the bug.
Okay, I was wrong. The problem is only when ICECAT_SYSTEM_DIR is unset.
When it's set to anywhere, like /, it works fine for me as well.
Regards,
Rutherther
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 07:13:01 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 07:37:02 GMT)
Full text and
rfc822 format available.
Message #35 received at submit <at> debbugs.gnu.org (full text, mbox):
On Tue, Apr 08 2025, Rutherther via Bug reports for GNU Guix wrote:
> Clément Lassieur <clement <at> lassieur.org> writes:
>
>> On Mon, Apr 07 2025, Rutherther via Bug reports for GNU Guix wrote:
>>
>>> I think you've discovered the actual bug. The issue is that
>>> .librewolf/native-messaging-hosts is not checked, instead
>>> ICECAT_SYSTEM_DIR is, with no fallback even if it's empty. When I set
>>> ICECAT_SYSTEM_DIR to $HOME/.librewolf all is working fine again.
>>
>> I don't think so, because on my computer,
>>
>> $HOME/.librewolf/native-messaging-hosts/passff.json
>>
>> works (without changing ICECAT_SYSTEM_DIR)
>>
>> and if I remove that file it doesn't work anymore.
>
>>
>> So just to make it clear: I can't reproduce the bug.
>
> Okay, I was wrong. The problem is only when ICECAT_SYSTEM_DIR is unset.
> When it's set to anywhere, like /, it works fine for me as well.
Great!
Closing :)
Regards,
Clément
Reply sent
to
Clément Lassieur <clement <at> lassieur.org>
:
You have taken responsibility.
(Tue, 08 Apr 2025 07:37:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Konrad Hinsen <konrad.hinsen <at> fastmail.net>
:
bug acknowledged by developer.
(Tue, 08 Apr 2025 07:37:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 08:13:02 GMT)
Full text and
rfc822 format available.
Message #43 received at 77415 <at> debbugs.gnu.org (full text, mbox):
>> Okay, I was wrong. The problem is only when ICECAT_SYSTEM_DIR is unset.
>> When it's set to anywhere, like /, it works fine for me as well.
>
> Great!
>
> Closing :)
Should this really be closed? I think it's a bug that ought to be fixed.
Or at least the user's should get to know somehow they have to set it.
If user is not using any extensions via Guix, they won't be able to use
native messaging unless they know about this culprit.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 08:33:01 GMT)
Full text and
rfc822 format available.
Message #46 received at 77415 <at> debbugs.gnu.org (full text, mbox):
Rutherther <rutherther <at> ditigal.xyz> writes:
>>> Okay, I was wrong. The problem is only when ICECAT_SYSTEM_DIR is unset.
>>> When it's set to anywhere, like /, it works fine for me as well.
>>
>> Great!
>>
>> Closing :)
>
> Should this really be closed? I think it's a bug that ought to be fixed.
> Or at least the user's should get to know somehow they have to set it.
> If user is not using any extensions via Guix, they won't be able to use
> native messaging unless they know about this culprit.
I agree!
It's absolutely not obvious that LibreWolf users should
- look for extension packages labeled "icecat"
- set an undocumented environment variable to make the
documented standard behavior of LibreWolf work
In particular, if it is possible to restore the standard behavior
(search for extensions under ~/.librewolf), that should be done.
Cheers,
Konrad.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 11:26:02 GMT)
Full text and
rfc822 format available.
Message #49 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Tue, Apr 08 2025, Rutherther via Bug reports for GNU Guix wrote:
>>> Okay, I was wrong. The problem is only when ICECAT_SYSTEM_DIR is unset.
>>> When it's set to anywhere, like /, it works fine for me as well.
>>
>> Great!
>>
>> Closing :)
>
> Should this really be closed? I think it's a bug that ought to be fixed.
> Or at least the user's should get to know somehow they have to set it.
> If user is not using any extensions via Guix, they won't be able to use
> native messaging unless they know about this culprit.
Oh right, I reopen.
Would the attached patch fix your issue? (Can't test it right now.)
Thanks,
Clément
[0001-gnu-librewolf-Create-lib-icecat-so-that-ICECAT_SYSTE.patch (text/x-diff, attachment)]
Did not alter fixed versions and reopened.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 08 Apr 2025 11:33:02 GMT)
Full text and
rfc822 format available.
Added tag(s) patch.
Request was from
Clément Lassieur <clement <at> lassieur.org>
to
control <at> debbugs.gnu.org
.
(Tue, 08 Apr 2025 11:35:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 15:15:02 GMT)
Full text and
rfc822 format available.
Message #56 received at 77415 <at> debbugs.gnu.org (full text, mbox):
On Tue, Apr 08 2025, Clément Lassieur wrote:
> On Tue, Apr 08 2025, Rutherther via Bug reports for GNU Guix wrote:
>
>>>> Okay, I was wrong. The problem is only when ICECAT_SYSTEM_DIR is unset.
>>>> When it's set to anywhere, like /, it works fine for me as well.
>>>
>>> Great!
>>>
>>> Closing :)
>>
>> Should this really be closed? I think it's a bug that ought to be fixed.
>> Or at least the user's should get to know somehow they have to set it.
>> If user is not using any extensions via Guix, they won't be able to use
>> native messaging unless they know about this culprit.
>
> Oh right, I reopen.
>
> Would the attached patch fix your issue? (Can't test it right now.)
I could try the patch, it works.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Tue, 08 Apr 2025 18:35:02 GMT)
Full text and
rfc822 format available.
Message #59 received at 77415 <at> debbugs.gnu.org (full text, mbox):
Clément Lassieur <clement <at> lassieur.org> writes:
>> Would the attached patch fix your issue? (Can't test it right now.)
>
> I could try the patch, it works.
Great, thanks!
I had tried to build Librewolf with this patch, but my laptop is too
small for this. Parallel combination runs out of memory (I have "only"
16 GB), and serial compilation runs out of disk space.
I'll wait for this to appear as a substitute!
Thanks again,
Konrad.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77415
; Package
guix
.
(Wed, 09 Apr 2025 17:35:01 GMT)
Full text and
rfc822 format available.
Message #62 received at 77415 <at> debbugs.gnu.org (full text, mbox):
On Tue, Apr 08 2025, Konrad Hinsen wrote:
> Clément Lassieur <clement <at> lassieur.org> writes:
>
>>> Would the attached patch fix your issue? (Can't test it right now.)
>>
>> I could try the patch, it works.
>
> Great, thanks!
>
> I had tried to build Librewolf with this patch, but my laptop is too
> small for this. Parallel combination runs out of memory (I have "only"
> 16 GB), and serial compilation runs out of disk space.
I can understand this :)
> I'll wait for this to appear as a substitute!
It should be available on bordeaux.guix.gnu.org:
https://data.qa.guix.gnu.org/gnu/store/3126vqyzvvf4xzj00xxpwylzg15482rq-librewolf-136.0.4-1.drv
(Triggered by https://issues.guix.gnu.org/77677)
bug closed, send any further explanations to
77415 <at> debbugs.gnu.org and Konrad Hinsen <konrad.hinsen <at> fastmail.net>
Request was from
Clément Lassieur <clement <at> lassieur.org>
to
control <at> debbugs.gnu.org
.
(Sat, 12 Apr 2025 07:44:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 10 May 2025 11:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 37 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.