Your message dated Wed, 7 Oct 2026 13:53:26 -0400
with message-id <[email protected]>
and subject line Re: xdm or xorg seems to disregard /etc/X11/Xsession.options
has caused the Debian Bug report #919746,
regarding xdm or xorg seems to disregard /etc/X11/Xsession.options
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
919746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919746
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xdm
Version: 1:1.1.11-3
Severity: normal

Dear Maintainer,

In /etc/X11/Xsession.options, I tried to set

no-use-ssh-agent

so that I could start ssh-agent through gnome-keyring-daemon
instead with xfce4-session (there is an tickable option in xfce4 startup
options to do this).

but now ssh-agent starts anyway.

(If one does this as described in it's possible for the xfce4 terminal emulator
to automatically login to remote machines when one logs into xdm, if one saves
the xfce4 session. It's convenient and I think it's OK as long as Mossad
doesn't get into the apartment.)

https://wiki.gnome.org/Projects/GnomeKeyring/Pam



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), 
LANGUAGE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xdm depends on:
ii  cpp                    4:8.2.0-2
ii  debconf [debconf-2.0]  1.5.69
ii  libc6                  2.28-5
ii  libpam0g               1.1.8-4
ii  libselinux1            2.8-1+b1
ii  libx11-6               2:1.6.7-1
ii  libxau6                1:1.0.8-1+b2
ii  libxaw7                2:1.0.13-1+b2
ii  libxdmcp6              1:1.1.2-3
ii  libxext6               2:1.3.3-1+b2
ii  libxft2                2.3.2-2
ii  libxinerama1           2:1.1.4-1
ii  libxmu6                2:1.1.2-2
ii  libxpm4                1:3.5.12-1
ii  libxrender1            1:0.9.10-1
ii  libxt6                 1:1.1.5-1
ii  lsb-base               10.2018112800
ii  procps                 2:3.3.15-2
ii  x11-utils              7.7+4
ii  x11-xserver-utils      7.7+8

xdm recommends no packages.

xdm suggests no packages.

-- Configuration Files:
/etc/X11/xdm/xdm-config changed:
!
!
!
!
!
DisplayManager.authDir: /var/lib/xdm
DisplayManager.errorLogFile:    /var/log/xdm.log
DisplayManager.pidFile:         /var/run/xdm.pid
DisplayManager.keyFile:         /etc/X11/xdm/xdm-keys
DisplayManager.servers:         /etc/X11/xdm/Xservers
DisplayManager.accessFile:      /etc/X11/xdm/Xaccess
DisplayManager*resources:       /etc/X11/xdm/Xresources
DisplayManager.willing:         su nobody -s /bin/sh -c /etc/X11/xdm/Xwilling
! All displays should use authorization, but we cannot be sure
! X terminals will be configured to support it, so those that do not will
! require individual resource settings.
DisplayManager*authorize:       true
!
DisplayManager*chooser:         /usr/lib/X11/xdm/chooser
DisplayManager*startup:         /etc/X11/xdm/Xstartup
DisplayManager*session:         /etc/X11/xdm/Xsession
DisplayManager*setup:           /etc/X11/xdm/Xsetup
DisplayManager*reset:           /etc/X11/xdm/Xreset
DisplayManager*authComplain:    true
DisplayManager*loginmoveInterval:       10
! SECURITY: do not listen for XDMCP or Chooser requests
! Comment out this line if you want to manage X terminals with xdm
DisplayManager.requestPort:     0
DisplayManager*authName:        MIT-MAGIC-COOKIE-1

/etc/pam.d/xdm changed:
auth            requisite       pam_nologin.so
auth            required        pam_env.so
auth            required        pam_env.so envfile=/etc/default/locale
session [success=ok ignore=ignore module_unknown=ignore default=bad]        
pam_selinux.so close
session required        pam_loginuid.so
session [success=ok ignore=ignore module_unknown=ignore default=bad]        
pam_selinux.so open
session         required        pam_limits.so
@include common-auth
@include common-account
@include common-session
@include common-password
auth            optional        pam_gnome_keyring.so    auto_start
session         optional        pam_gnome_keyring.so


-- debconf information:
  xdm/stop_running_server_with_children: false
  xdm/daemon_name: /usr/bin/xdm
* shared/default-x-display-manager: xdm

--- End Message ---
--- Begin Message ---
notfound 919746 1:1.1.11-3
thanks

Hi,

On Sat, 19 Jan 2019 04:50:11 +0100 Per Gunnarsson <[email protected]> 
wrote:
> Package: xdm
> Version: 1:1.1.11-3
> Severity: normal
>
> Dear Maintainer,
>
> In /etc/X11/Xsession.options, I tried to set
>
> no-use-ssh-agent
>
> so that I could start ssh-agent through gnome-keyring-daemon
> instead with xfce4-session (there is an tickable option in xfce4 startup
> options to do this).
>
> but now ssh-agent starts anyway.
>
> (If one does this as described in it's possible for the xfce4 terminal 
emulator
> to automatically login to remote machines when one logs into xdm, if one saves
> the xfce4 session. It's convenient and I think it's OK as long as Mossad
> doesn't get into the apartment.)
>
> https://wiki.gnome.org/Projects/GnomeKeyring/Pam
>
>
>
> -- System Information:
> Debian Release: buster/sid

Package xdm itself does not read /etc/X11/Xsession.options. Instead, its
Xsession script only runs Debian's common /etc/X11/Xsession, and the ssh-agent
hooks there (/etc/X11/Xsession.d/90x11-common_ssh-agent) does honor
"no-use-ssh-agent". THere are two other places that can launch ssh-agent in your
setup:

  * xfce4-session starts its own ssh-agent unless you disable it explicitly. 
For example,
    xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s 
false

  * with the x11-common package version in buster, adding a "no-use-ssh-agent" 
line
    does not override a "use-ssh-agent" line that was still present. The option 
had
    to be replaced. Current x11-common in Testing/Sid is different and now 
considers
    the "no-" lines with higher priority.

As neither problem is from xdm, I am closing this bug. If you still see 
ssh-agent started
by /etc/X11/Xsession with current x11-common, please file it against x11-common.

Thanks,
Boyuan Yang

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to