Your message dated Thu, 1 Jun 2017 14:50:19 +0200
with message-id <[email protected]>
and subject line Re: Bug#863866: gdm3: GDM3 possibly not reading any config
files on Stretch
has caused the Debian Bug report #863866,
regarding gdm3: GDM3 possibly not reading any config files on Stretch
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.)
--
863866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863866
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.22.3-2
Severity: important
Dear Maintainer,
I have been using stretch now for several weeks. I believe that it seems GDM3
is not reading any config files I place in /var/lib/gdm3/.config.
In this directory I have placed a monitors.xml that specifies which monitor is
primary (copied from ~/.config/monitors.xml). Furthermore I configured GDM3 not
to capture a bluetooth ad2p sink (as described in the wiki:
https://wiki.debian.org/BluetoothUser/a2dp).
Now it seems that still GDM3 captures the ad2p sink (because I can't get
bluetooth to work), and the monitor I specified as primary in monitors.xml is
not made primary. Hence I believe GDM3 is not reading any config files in
/var/lib/gdm3/.config.
I checked the file permissions on the directories and files, which should be
okay; both the user and group are Debian-gdm, and files have rw permissions,
and directories rwx permissions.
I know for a fact that my bluetooth a2dp sink is working properly, because if I
use lightdm there are no issues with bluetooth.
Any ideas if I am doing something wrong, or might there be a bug somewhere in
GDM 3.22? Is there a major change between 3.22, and 3.14 (3.14 is the GDM
version in Jessie) that could explain these two issues (it worked fine in
Jessie)?
Please let me know if you require any more information.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gdm3 depends on:
ii accountsservice 0.6.43-1
ii adduser 3.115
ii dconf-cli 0.26.0-2+b1
ii dconf-gsettings-backend 0.26.0-2+b1
ii debconf [debconf-2.0] 1.5.61
ii gir1.2-gdm-1.0 3.22.3-2
ii gnome-session [x-session-manager] 3.22.3-1
ii gnome-session-bin 3.22.3-1
ii gnome-settings-daemon 3.22.2-2
ii gnome-shell 3.22.3-3
ii gnome-terminal [x-terminal-emulator] 3.22.2-1
ii gsettings-desktop-schemas 3.22.0-1
ii konsole [x-terminal-emulator] 4:16.12.0-4
ii libaccountsservice0 0.6.43-1
ii libaudit1 1:2.6.7-2
ii libc6 2.24-10
ii libcanberra-gtk3-0 0.30-3
ii libcanberra0 0.30-3
ii libgdk-pixbuf2.0-0 2.36.5-2
ii libgdm1 3.22.3-2
ii libglib2.0-0 2.50.3-2
ii libglib2.0-bin 2.50.3-2
ii libgtk-3-0 3.22.11-1
ii libkeyutils1 1.5.9-9
ii libpam-modules 1.1.8-3.5
ii libpam-runtime 1.1.8-3.5
ii libpam-systemd 232-23
ii libpam0g 1.1.8-3.5
ii librsvg2-common 2.40.16-1+b1
ii libselinux1 2.6-3+b1
ii libsystemd0 232-23
ii libwrap0 7.6.q-26
ii libx11-6 2:1.6.4-3
ii libxau6 1:1.0.8-1
ii libxcb1 1.12-1
ii libxdmcp6 1:1.1.2-3
ii lsb-base 9.20161125
ii mutter [x-window-manager] 3.22.3-2
ii policykit-1 0.105-17
ii ucf 3.0036
ii x11-common 1:7.7+19
ii x11-xserver-utils 7.7+7+b1
ii xterm [x-terminal-emulator] 327-2
Versions of packages gdm3 recommends:
ii at-spi2-core 2.22.0-6
ii desktop-base 9.0.2
ii x11-xkb-utils 7.7+3+b1
ii xserver-xephyr 2:1.19.2-1
ii xserver-xorg 1:7.7+19
ii zenity 3.22.0-1+b1
Versions of packages gdm3 suggests:
ii gnome-orca 3.22.2-3
ii libpam-gnome-keyring 3.20.0-3
-- debconf information:
* shared/default-x-display-manager: lightdm
gdm3/daemon_name: /usr/sbin/gdm3
--- End Message ---
--- Begin Message ---
Am 01.06.2017 um 11:02 schrieb Jeroen Meijer:
> Package: gdm3
> Version: 3.22.3-2
> Severity: important
>
> Dear Maintainer,
>
> I have been using stretch now for several weeks. I believe that it seems GDM3
> is not reading any config files I place in /var/lib/gdm3/.config.
> In this directory I have placed a monitors.xml that specifies which monitor is
> primary (copied from ~/.config/monitors.xml). Furthermore I configured GDM3
> not
> to capture a bluetooth ad2p sink (as described in the wiki:
> https://wiki.debian.org/BluetoothUser/a2dp).
> Now it seems that still GDM3 captures the ad2p sink (because I can't get
> bluetooth to work), and the monitor I specified as primary in monitors.xml is
> not made primary. Hence I believe GDM3 is not reading any config files in
> /var/lib/gdm3/.config.
Pitfall: gdm by default uses Wayland, the default GNOME session uses X.
You probably can't just copy the monitors.xml over and expect it to work.
Also, make sure that the permissions are correct.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
