GNU bug report logs - #55707
syslogd logging kernel messages slowly?

Previous Next

Full log

Message #38 received at 55707 <at> debbugs.gnu.org (full text, mbox):

From: Luis Felipe <luis.felipe.la <at> protonmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 55707 <at> debbugs.gnu.org, 55488 <at> debbugs.gnu.org
Subject: Re: bug#55488: GDM, GNOME: Can't start desktop session after upgrade
Date: Mon, 06 Jun 2022 18:11:53 +0000

[Message part 1 (text/plain, inline)]

It turns out the problem is related to user services. I just disabled my user services, rebooted, and GNOME session started.

I only have one user service defined in ~/.config/shepherd/init.scm as follows

~~~
;;; Definition of my user-level services.
(use-modules (shepherd service))


;;; SERVICE DEFINITIONS
;;; ===================

(define rygel
  (make <service>
    #:provides '(rygel)
    #:docstring "Run the Rygel media server."
    #:start (make-forkexec-constructor '("rygel"))
    #:stop (make-kill-destructor)
    #:respawn? #t))


;;; REGISTER SERVICES
;;; =================

(register-services rygel)


;;; START SERVICES
;;; ==============

(start rygel)

;;; Send shepherd to the background.
(action 'shepherd 'daemonize)
~~~

And I call "shepherd" in the ~/.profile file. This never posed a problem until my recent system generations from April to date, though, where I was never able to start a GNOME session. So I wonder what's going on now...

For what it's worth, the only error I see in ~/.config/shepherd/shepherd.log is this

2022-04-07 11:01:57 system-error("getpgid" "~A" ("No existe el proceso") (3))

"No existe el proceso" meaning, "The process doesn't exist". This error has occurred several times since 2021, though.

[publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc (application/pgp-keys, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.