# Main issue
Solanum in flatpak failed to render its logo.
# Reproduce step
Run
```
guix shell flatpak
flatpak install org.gnome.Solanum
flatpak run org.gnome.Solanum
```
# Investigation
The issue maybe caused by missing gdk pixbuf loaders. Try `flatpak run
--command=sh --devel
Hi,
guix home reconfigure config.scm [1], throw error and freezes even
ctrl-c doesn't help
Uncaught exception in task:
In fibers.scm
150:0 9 (_)
In ice-9/boot-9.scm
1747:15 8 (with-exception-handler # at ic..>
...)
In shepherd.scm
439:9 7 (_)
In ice-9/boot-9.scm
1747:15 8
Hello,
I'm following these instructions (
https://gist.github.com/giuliano108/49ec5bd0a9339db98535bc793ceb5ab4) to
get guix up and running in WSL2 on Windows 11.
Everything worked until guix pull at which point I get the following error:
*/mnt/c/Tools/WSL/guix #
On Wed, 18 Aug 2021 at 12:07, Ricardo Wurmus
wrote:
We have since upgraded to 4.10.3, but the problems still
persist. Conda still
asks users to run “conda init”, which attempts to run “sudo”
to modify
root-owned files. It’s a big mess.
I don't think conda init will ever work on Guix, and
Versions:
guile-json 4.5.2 out
/gnu/store/grjvqx3xfjlczak7j3gsdf0q4wf7fnw6-guile-json-4.5.2
guile-git 0.5.2 out
/gnu/store/b9srz33q8nxfchf93qbs2qpal0a0fmdk-guile-git-0.5.2
guile-avahi 0.4.0-1.6d43caf out
On Thu, 31 Mar 2022 15:31:56 +0200
Danny Milosavljevic wrote:
> Possible alternative fixes:
d. Move the definitions of XCreateFontCursor and XCreatePixmapCursor to
libxcursor (i.e. delete their definitions from libx11 and create them
in libxcursor). Fix up now-failing packages such that they
Hi!
Tobias Geerinckx-Rice skribis:
> I can't build the older installer image I want, ostensibly because my
> installed system is too new (anno-post-apteryx-versioning; no time to
> further investigate I'm afraid).
>
> I expect a self-contained system not to care and certainly not to crash.
>
>
Hi,
Denis 'GNUtoo' Carikli skribis:
> The fact that Valgrind doesn't work out of the box seems to already be
> known[1] but I didn't find any bugreports on it.
Indeed. Fixed in 6b6fb78724869c03394d0e6dc2f50f0777f6d467 on
‘core-updates’ as discussed with Mark (mjw) a couple of days ago on IRC.
Hi!
Following the Shepherd upgrade in commit
400c9ed3d779308e56038305d40cd93acb496180, attempts to open non-root LUKS
devices from a Shepherd service fail with this cryptsetup message:
Nothing to read on input.
This is because standard input is now /dev/null so it cannot read the
passphrase.
Am Donnerstag, dem 07.04.2022 um 15:50 +0300 schrieb Roman Riabenko:
> I believe that the above is enough to close this issue.
Consider it closed.
Hello
Thank you for directing me to those options.
Setting _XOPEN_SOURCE to 500 or higher seems to restore the expected
functionality of attrset in ncurses for colour. _XOPEN_SOURCE is a
feature test macro, so it just determines that some functionality from
X/Open is used (X/OPEN 5 for
Hi Maxime,
sorry for this late reply!
I solved my problem with an ugly workaround: installing the Debian
provided guix package and temporarily using that updated daemon in the
systemd service, so I was able to upgrade to an updated Guix (since the
package in Debian is not up to date with
A patch has been submitted for the second part of this issue [0] and a new
issue has been created for the first part [1]. I'm therefore closing this issue.
0: https://issues.guix.gnu.org/54729
1: https://issues.guix.gnu.org/54760
On Wed, 6 Apr 2022, at 21:27, zimoun wrote:
> Hi,
>
> On Mon, 31
The attoparsec package on hackage defines multiple internal libraries inside
one package, named "attoparsec" and "attoparsec-internal", with the first
depending on the latter. Importing attoparsec using `guix import hackage
attoparsec` therefore yields the following erroneous package
Hi
On Thu, 7 Apr 2022, at 09:45, zimoun wrote:
> On Tue, 08 Mar 2022 at 11:04, zimoun wrote:
>> And the "cycle" seems expected from OneTuple.cabal:
>>
>> $ cat OneTuple-0.3.1/OneTuple.cabal
>> cabal-version: >=1.10
>>
>> [...]
>>
>> test-suite th
>> type: exitcode-stdio-1.0
>>
Hi,
On Tue, 08 Mar 2022 at 11:04, zimoun wrote:
> On dim., 28 nov. 2021 at 02:50, John Kehayias
> wrote:
>
>> While working on importing a bunch of Haskell packages, I came across
>> a cycle created by the importer (twice actually, but forgot the other
>> one). Perhaps this is from the metadata
16 matches
Mail list logo
