GNU bug report logs - #41025
blueman does not start

Previous Next

Package: guix;

Reported by: Pierre Neidhardt <mail <at> ambrevar.xyz>

Date: Sat, 2 May 2020 13:40:02 UTC

Severity: normal

Done: Pierre Neidhardt <mail <at> ambrevar.xyz>

Bug is archived. No further changes may be made.

Full log

Message #20 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Raghav Gururajan <raghavgururajan <at> disroot.org>
To: Pierre Neidhardt <mail <at> ambrevar.xyz>
Cc: bug-guix <at> gnu.org
Subject: Re: blueman does not start
Date: Sun, 3 May 2020 23:18:53 -0400

Hi Pierre!

> Suggestion: instead of adding one phase per wrapper, use a single phase,
> loop over the executables to generate the wrapper.  This should shorten
> your code.
> 
> I think the "gi" issue is because "(getenv ...)" does not include the
> output "out".  I'm guessing you need to add (string-append out
> "/lib/python...blueman...") to the PYTHONPATH.

I tried using (string-append (assoc-ref outputs "out")
"/lib/python3.7/site-packages/blueman"); instead of (getenv PYTHONPATH). I got
the same error.

Regards,
RG.
This bug report was last modified 5 years and 91 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.