l...@gnu.org (Ludovic Courtès) skribis:
> Thread 14 is in scm_readdir, so it holds the terrible
> ‘scm_i_misc_mutex’, but calling SCM_SYSERROR there causes it to try and
> lock it again, leading to a deadlock:
>
> #3 0x7f7ee9545969 in scm_dynwind_pthread_mutex_lock
> (mutex=0x7f7ee97bbfa0 )
Hi,
Roel Janssen skribis:
> On CentOS 7, the following happens (yes, I added the echo-statement to
> /etc/bashrc on CentOS as well):
> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
> Goodbye, world
>
> On GuixSD:
> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
> H
> hi, when starting asileriot (sol) I get:
>
> GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings
> will not be saved or shared with other applications.
>
> I think its this problem:
>
>
> https://stackoverflow.com/questions/44934641/glib-gio-
> message-using-the-memory-gsettin
If we look at our worker threads, they’re all stuck in mutex_lock:
--8<---cut here---start->8---
(gdb) info threads
Id Target Id Frame
* 1Thread 0x7f7ee99d5f00 (LWP 4105) "guix publish" 0x7f7ee79c60ad in
poll () from
/gnu/store/n6nvxlk2j8ys
Dear Guix,
This is more of an issue for GuixSD.
Our 'bash' package seems to behave differently from other distributions
(like CentOS 7), and it behaves differently from the way described in its
manual page.
I added the following line to /etc/bashrc:
echo "Hello, world"
Here's the command to repr
Hello,
On berlin I’ve noticed that the ‘guix publish’ workers would
occasionally stop working: the main thread would keep replying to HTTP
requests, but the worker threads would no longer do anything, and would
leave behind them a bunch of .tmp files in /var/cache/guix/publish.
I captured the out
Eric Bavier skribis:
> Looks good to me.
Pushed as 232b3d31016439b5600e47d845ffb7c9a4ee4723.
Thanks,
Ludo’.
