bug#75269: Crash of shepherd service, of GNU Artanis app, only happening in the server, not on my machine
Hola, Josep Bigorra skribis: > Jan 1 22:20:17 localhost shepherd[1]: make[911] ERROR: In procedure > apply-smob/0: > Jan 1 22:20:17 localhost shepherd[1]: make[911] In procedure dbi-close: > Wrong type argument in position 1: # For the record, this sounds like a memory management bug in guile-dbi: ‘dbi-close’ is passed a “SMOB” (a Scheme wrapper for a C object) that has been freed in the meantime. Closing! Ludo’.
bug#75390: least-authority-wrapper for bitlbee-service-type breaks Bonjour support
Hello! Ricardo Wurmus skribis: > The bitlbee-service-type uses the least-authority-wrapper to run bitlbee > in a container. A side effect when using bitlbee-purple is that the > Bonjour protocol no longer works as bitlbee cannot connect to the local > mDNS server: > > <@rekado> account add bonjour rekado > Account successfully added with tag bonjour > <@rekado> account on > Trying to get all accounts connected... > bonjour - Login error: Unable to establish connection with the local >mDNS server. Is it running? > bonjour - Logging in: Signing off.. > bonjour - Logging in: Reconnecting in 5 seconds.. I never used this feature, but I suspect the patch below should fix it: diff --git a/gnu/services/messaging.scm b/gnu/services/messaging.scm index a914d0f89e..f796afbc82 100644 --- a/gnu/services/messaging.scm +++ b/gnu/services/messaging.scm @@ -850,6 +850,12 @@ (define bitlbee-shepherd-service (file-system-mapping (source "/run/current-system/locale") (target source)) +(file-system-mapping ;for Avahi + (source "/var/run/dbus") + (target source)) +(file-system-mapping + (source "/run/avahi-daemon") + (target source)) (file-system-mapping (source conf) (target conf))) Only problem is that things may go wrong if these directories don’t exist. So I think we should add a ‘bonjour?’ field in the config record, add these mapping conditionally, and also add a Shepherd requirement on ‘avahi-daemon’. > The Bonjour protocol allows for serverless messaging, which is also used > by the Sugar desktop's Chat activity. Interesting! Ludo’.
bug#68895: `guix repl` breaks Guile REPL features
45mg <45mg.wri...@gmail.com> writes: > It looks like this isn't the only REPL command that doesn't work in > `guix repl`. I haven't done anything close to a full investigation (I am > new to using Guile!), but many other commands simply don't work. Thank you for your investigation. I am cc-ing guix-devel in case they have insight regarding these. -- Suhail
bug#68895: Difference between trace behavior in guix repl and guile
Suhail Singh writes: >> It looks like this isn't the only REPL command that doesn't work in >> `guix repl`. I haven't done anything close to a full investigation (I am >> new to using Guile!), but many other commands simply don't work. > > Thank you for your investigation. I am cc-ing guix-devel in case they > have insight regarding these. Whoops, sent too quickly. Current (probably inexhaustive) list: - trace - tracepoint - break -- Suhail
bug#75450: tor-onion-service-configuration example in Guix Manual does not work
Guix has been pestering me about the deprecation of `tor-hidden-service` for a
year now. So I checked out the manual to see the correct official way that
replaces `tor-hidden-service`:
```text
-- Variable: tor-service-type
Type for a service that runs the Tor (https://torproject.org)
anonymous networking daemon. The service is configured using a
‘’ record. By default, the Tor daemon runs as
the ‘tor’ unprivileged user, which is a member of the ‘tor’ group.
Services of this type can be extended by other services to specify
“onion services” (in addition to those already specified in
‘tor-configuration’) as in this example:
(simple-service 'my-extra-onion-service tor-service-type
(list (tor-onion-service-configuration
(name "extra-onion-service")
(mapping '((80 . "127.0.0.1:8080"))
```
I created a simple `configuration.scm` that uses the above example verbatim in
the `services` list, and got this error on `guix system build`:
```text
building /gnu/store/c3x922pfx3lcb8nzwcns6k43ncaj2asj-torrc.drv...
Backtrace:
4 (primitive-load "/gnu/store/1flyd8skq8cx6p8d7cpv5b99rxc?")
In ice-9/ports.scm:
433:17 3 (call-with-output-file _ _ #:binary _ #:encoding _)
In ice-9/eval.scm:
619:8 2 (_ #(#(#) #))
In ice-9/boot-9.scm:
260:13 1 (for-each # ?)
In ice-9/eval.scm:
619:8 0 (_ #(#(# ("e?" ?
ice-9/eval.scm:619:8: Throw to key `match-error' with args `("match" "no
matching pattern" ("extra-onion-service" (80 . "127.0.0.1:8080")))'.
builder for `/gnu/store/c3x922pfx3lcb8nzwcns6k43ncaj2asj-torrc.drv' failed with
exit code 1
build of /gnu/store/c3x922pfx3lcb8nzwcns6k43ncaj2asj-torrc.drv failed
```
Please do not deprecate `tor-hidden-service` until your replacement has
actually been tested to ***actually work*** on some very simple use-case
example.
I attached the simple example that fails.
base.scm
Description: Lotus Screencam
bug#71173: [bug#75100] [PATCH 0/3] Shepherd service of 'static-networking' completes in timely fashion
Pushed: 20a74ce28d tests: Run without the Linux kernel “quiet” argument. 431ab10344 services: static-networking: Fail when devices don’t show up. 8d649a8d17 services: static-networking: Run set-up/tear-down as a separate process.
