Hi Luis,

Thanks for the answer,

Le jeudi 13 mars 2025 à 19:05 +0000, Luis Felipe a écrit :
> Hi Christophe,
> 
> This has happened to me before, and it usually goes away by rebooting
> once again (restarting GNOME session is not enough).

I also restarted, but the problem persisted.
> 
> Besides what I mentioned above, I also experience problems similar to
> the ones mentioned in issue #36924.¹ They occur from time to time
> after 
> having reconfigured the system. If rebooting again doesn't solve your
> problem, maybe take a look at that issue for other workarounds.

There's too much information for me: I can't come to a conclusion about
what I might try.

> 
> Right now for example, I can't start a GNOME session using the latest
> generation of my system (guix f1810c8). When I log in, all I see is a
> black screen. I assume it is one of those state-related issues
> because 
> if I create a new user I can log in normally with that user only.

I'll create a test user to see if it works for me too. 
I'm not sure what syntax to use for more than one user. 
For two users, should we do: 

(users (cons* (user-account
                                (name "bob")
                                (comment "Alice's bro")
                                (group "users")
                                (home-directory "/home/bob")
                                (supplementary-groups '("wheel"
"netdev" "audio" "video"))
                                (name "alice")
                                (comment "Bob's sister")
                                (group "users")
                                (home-directory "/home/alice")
                                (supplementary-groups '("wheel"
"netdev" "audio" "video")))
%base-user-accounts))


Le jeudi 13 mars 2025 à 23:15 +0000, Luis Felipe a écrit :
> On 13/03/25 19:05, Luis Felipe wrote:
> > Right now for example, I can't start a GNOME session using the
> > latest 
> > generation of my system (guix f1810c8). When I log in, all I see is
> > a 
> > black screen. I assume it is one of those state-related issues
> > because 
> > if I create a new user I can log in normally with that user only.
> Ha, in the meantime, I found that my custom 
> «~/.config/shepherd/init.scm» was the root of this problem.
> Apparently 
> it became obsolete in the new generation of the system because 
> Shepherd's API has changed.

There are no custom "~/.config/shepherd/init.scm" in my home
directory. 

Christophe

Reply via email to