unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: 35408@debbugs.gnu.org
Cc: Ben Sturmfels <ben@sturm.com.au>
Subject: bug#35408: External monitor not working with GDM
Date: Thu, 25 Apr 2019 14:16:39 +0200	[thread overview]
Message-ID: <20190425141622.175fe961@scratchpost.org> (raw)
In-Reply-To: <17cc954b1feb50becef0df5bcafa56b6c9e45da7.camel@sturm.com.au>

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

Hi,

On Thu, 25 Apr 2019 21:41:27 +1000
Ben Sturmfels <ben@sturm.com.au> wrote:

> Apr 25 20:30:54 localhost gdm: gdm_session_set_environment_variable:
> assertion 'value != NULL' failed 

Yeah, that one again.  It might make sense to patch that so the assertion
actually prints name and value passed.

You can also set "debug"'s "Enable=true" in gnu/services/xorg.scm , in
gdm-configuration-file , but it will only help in a limited way here.

> Apr 25 20:30:55 localhost gdm: Could not start command
> '/gnu/store/072cd7r7zx2fgp1v16bv2si5s435lwkj-gdm-3.26.2.1/libexec/gdm-
> session-worker': Too many open files 

WTF.  Parts of gdm have full root privileges and for it to contain
simple mistakes like that is worrying.

> Apr 25 20:30:55 localhost gdm: GLib: g_child_watch_add_full: assertion
> 'pid > 0' failed 

gdm should have checked for errors before calling g_child_watch_add_full.

> Apr 25 20:30:55 localhost gdm: Child process -15096 was already dead. 
> Apr 25 20:30:55 localhost gdm: Child process 15093 was already dead. 
> Apr 25 20:30:55 localhost gdm: Unable to kill session worker process 

WTF.  I hope they don't kill the same pid twice and thus risk killing
innocent bystanders that happen to reuse the pid of the dead process.

common/gdm-common.c gdm_signal_pid ... yes, they do.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-04-25 12:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  4:25 bug#35408: External monitor not working with GDM Ben Sturmfels
2019-04-25  9:08 ` Ludovic Courtès
2019-04-25 11:41   ` Ben Sturmfels
2019-04-25 12:16     ` Danny Milosavljevic [this message]
2019-04-25 12:53       ` Ben Sturmfels
2019-04-25 16:37       ` Ludovic Courtès
2019-04-26  1:12       ` Ben Sturmfels
2019-04-26  8:12         ` Ludovic Courtès
2019-04-25 22:13     ` Diego Nicola Barbato
2019-04-26  0:42       ` Ben Sturmfels
2019-04-26  8:14         ` Ludovic Courtès
2019-05-02  2:00           ` Ben Sturmfels
2019-05-02  8:01             ` Ben Sturmfels
2019-05-02 15:20               ` Ludovic Courtès
2019-05-08  2:50                 ` Ben Sturmfels
2020-06-11  4:01 ` Royce Strange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190425141622.175fe961@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=35408@debbugs.gnu.org \
    --cc=ben@sturm.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).