bug#63309: [BUG] evolution caldav sync on xfce doesn't work
Hi guix, GNOME has failed to start for me for a while, so I switched to XFCE. I use Evolution as my main mail client, and would like to use it for tasks and calendars as well, but on startup an error notification appears: TLS support is not available. This seems weird since Mail using TLS/SSL works. Cheers
bug#63308: [BUG] python-pikepdf build broken
Hey guix, I noticed that python-pikepdf is broken on master, which means pdfarranger, a tool I like to use is, too. Updating pikepdf solves the build issues, but I had to disable tests and and sanity-checks. And then, img2pdf which depends on python-pikepdf and is dependency of pdfarranger and pdfarranger still needed modifications. So I wanted to pass on the issue. Cheers
bug#58763: [BUG] gnuzilla: icedove profiles don't work
Hi, Using the recent gnome desktop on a Guix system, Icedove seems to be unable to restore recent/the last used configuration. This appears either by upgrade or reboot. (For some time the configuration was stable, but I'm not sure which of the two killed it. When I start it from the cli with the argument "-ProfileManager" , profiles are listed, but with either one selected, icedove will just boot like a vanilla configuration. However this error shows up "JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory." This is kind of weird since the profiles are actually shown. Since Icedove seems to be a guix product (?) I submit this to guix' bugtracker as well. Cheers, florhizome
bug#58399: [BUG] guix-emacs error -
Hello, when trying to use guix' emacs UI recently, the minibuffer command interface won't work. The issue and a possible fix (a one-line patch) has already been described here: https://gitlab.com/emacs-guix/emacs-guix/-/issues/30 It comes from the newer geiser not containing a file for company support anymore. Since the afroementioned gitlab-repo doesn't have commits since a year, I think it's sensible to go ahead and patch it by ourselves instead of waiting for a fix. But personally I am not very experienced in doing such a thing. Best wishes, florhizome
bug#54354: [BUG] guix home: on foreign distro, ~/.bash_profile is not initialized
Hi Liliana, Hm, well it doesn't seem like the exact same issue, but that thread is helpful. Could systemd/logind be made to use bash for login? For now I thought maybe I can just write shepherd services to do that stuff for me, to stay in guix homes framework. But shepherd seems to have a problem starting up: /gnu/store/y85vzni5yc6lcb7qqhmlkifis9nzmm5l-shepherd.conf wird geladen. herd: Ausnahmefehler während der Ausführung von »load« mit dem Dienst »root«: In procedure fport_write: Eingabe-/Ausgabefehler If you don't speak german, that roughly translates to: loading /gnu/store/...-shepherd.conf herd: exception error during the execution of <> with the service <>: In procedure fport_write: i/o error I got the same error when reconfiguring with two differing simple service configurations (just start a program from a package) passed to shepherd. In anyway I think it would be good to add to guix home's documentation that some features might not work due to the login system of a foreign distro if we are sure of that? cheers Liliana Marie Prikler writes: > Hi Florian > > Am Samstag, dem 12.03.2022 um 13:07 + schrieb florhizome: >> >> Hi guix' ! >> I have been trying to use guix home on my foreign distro partition >> (manjaro); especially in order to set up additional profiles from >> there, but my .bash_profile generated by guix doesn't seem to be >> evaluated at all. >> >> To describe the actual issue finally: None of the things that should >> happen through .bash_profile seem to happen at the moment (it's just >> about different environment variables that will not be set up.), but >> after running bash --login in my terminal-emulator everything is as >> anticipated so my guess is that .bash_profile actually isn't evaluated >> at all after login. I'm happy to hear other suggestions and especially >> solutions. > This looks vaguely like a problem others (myself included) have > experienced/are experiencing on Ubuntu. See [1] among others. > > Given that bash is not used for login, your environment-variables block > has not effect. Now if you were to define that inside a variable, you > could also write up a service that generates systemd unit overrides and > add those definitions to it. I'm not sure how well-received such a > service would be upstream given that we don't use systemd in Guix, but > it's a point to start. > > Cheers > > [1] https://issues.guix.gnu.org/48300#7
bug#54354: [BUG] guix home: on foreign distro, ~/.bash_profile is not initialized
Hi guix' !
I have been trying to use guix home on my foreign distro partition
(manjaro); especially in order to set up additional profiles from
there, but my .bash_profile generated by guix doesn't seem to be
evaluated at all.
To describe the actual issue finally: None of the things that should happen
through .bash_profile seem to
happen at the moment (it's just about different environment variables that
will not be set up.), but after running bash --login in my
terminal-emulator everything is as anticipated so my guess is that
.bash_profile actually isn't evaluated at all after login. I'm happy to hear
other suggestions and especially solutions.
I will attach the file that I use
for home configuration, as well as the current resulting .bashrc,
.bash_profile and .profile files.
I'm aware that there is duplicated code by the generated aliases in
.bashrc and that the prompt customization for guix profiles added by
the "guix-defaults?" field does not work due to other related code that comes
afterwards but I'm not sure it's related to that main issue.
I did the original set up using "guix home import" which seems to have
improved since I tried last in december last year when the generated
file didn't work at all.
Manjaro has a lot of stuff in it's .bashrc that i didn't want to
override, and maybe there are more cases of duplication there that I
don't know about what harm they might introduce.
Greetings, Florian
(use-modules
(gnu home)
(gnu packages)
(gnu packages base)
(gnu services)
(guix gexp)
(gnu home services shells))
(define %enable-extra-profiles
(plain-file "enable-profiles"
"for i in $GUIX_EXTRA_PROFILES/*; do
profile=$i/$(basename \"$i\")
if [ -f \"$profile\"/etc/profile ]; then
GUIX_PROFILE=\"$profile\"
. \"$GUIX_PROFILE\"/etc/profile
fi
unset profile
done"))
(home-environment
(services
(list (service
home-bash-service-type
(home-bash-configuration
(environment-variables
'(("GUIX_EXTRA_PROFILES" . "/home/flo/.extra-profiles")
;;("ALTERNATE_EDITOR" . "\"\"")
("EDITOR" . "\"emacsclient -nw -q\"")
("VISUAL" . "\"emacsclient -c -a \"\"\"")
("GIT_EDITOR" . "\"emacs -nw -q\"")))
(aliases
'(("cp" . "cp -i")
("df" . "df -h")
("egrep='egrep --colour" . "auto")
("fgrep='fgrep --colour" . "auto")
("free" . "free -m")
("grep='grep --colour" . "auto")
("ls='ls --color" . "auto")
("more" . "less")
("np" . "nano -w PKGBUILD")))
(bashrc
(list (local-file
"/home/flo/.config/guix/home/.bashrc"
"bashrc")))
(bash-profile
(list %enable-extra-profiles))
(bash-logout
(list (local-file
"/home/flo/.config/guix/home/.bash_logout"
"bash_logout"
HOME_ENVIRONMENT=$HOME/.guix-home
. $HOME_ENVIRONMENT/setup-environment
$HOME_ENVIRONMENT/on-first-login
alias cp="cp -i"
alias df="df -h"
alias egrep='egrep --colour="auto"
alias fgrep='fgrep --colour="auto"
alias free="free -m"
alias grep='grep --colour="auto"
alias ls='ls --color="auto"
alias more="less"
alias np="nano -w PKGBUILD"
# Bash initialization for interactive non-login shells and
# for remote shells (info "(bash) Bash Startup Files").
# Export 'SHELL' to child processes. Programs such as 'screen'
# honor it and otherwise use /bin/sh.
export SHELL
if [[ $- != *i* ]]
then
# We are being invoked from a non-interactive shell. If this
# is an SSH session (as in "ssh host command"), source
# /etc/profile so we get PATH and other essential variables.
[[ -n "$SSH_CLIENT" ]] && source /etc/profile
# Don't do anything else.
return
fi
# Source the system-wide file.
if [[ -e /etc/bashrc ]]; then
source /etc/bashrc
fi
# Adjust the prompt depending on whether we're in 'guix environment'.
if [ -n "$GUIX_ENVIRONMENT" ]
then
PS1='\u@\h \w [env]\$ '
else
PS1='\u@\h \w\$ '
fi
alias ls='ls -p --color=auto'
alias ll='ls -l'
alias grep='grep --color=auto'
#
# ~/.bashrc
#
[[ $- != *i* ]] && return
colors() {
local fgc bgc vals seq0
printf "Color escapes are %s\n" '\e[${value};...;${value}m'
printf "Values 30..37 are \e[33mforeground colors\e[m\n"
printf "Values 40..47 are \e[43mbackground colors\e[m\n"
printf "Value 1 gives a \e[1mbold-faced look\e[m\n\n"
# foreground colors
for fgc in {30..37}; do
# background colors
for bgc in {40..47}; do
fgc=${fgc#37} # white
bgc=${bgc#40} # black
vals="${fgc:+$fgc;}${bgc}"
vals=${vals%%;}
