Your message dated Tue, 05 Feb 2013 16:28:27 +0100
with message-id <1360078107.8280.29.camel@tomoyo>
and subject line Re: Bug#681310: gdm3 sometimes starts greater with ugly
graphics (no wallpaper and poor gtk theme for the login window)
has caused the Debian Bug report #681310,
regarding gdm3 sometimes starts greater with ugly graphics (no wallpaper and
poor gtk theme for the login window)
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.)
--
681310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681310
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.4.1-2
Severity: normal
Dear Maintainer,
sometimes on the first start (just after the boot process) gdm3 starts in an
ugly mode without graphic stuff: a black screen instead of the nice debian
background and without the usual gtk theme for the login window.
If I manually restart the service all work as expected.
I suspect a problem with the service start order during boot... here is my
(cleaned) bootlog file:
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
[....] Starting enhanced syslogd: rsyslogd
[....] Starting system message bus: dbus
[....] Starting network connection manager: NetworkManager
[....] Starting ACPI services...
[....] Starting virtual private network daemon
[....] Starting GNOME Display Manager: gdm3
[....] Starting acpi_fakekey daemon...
[....] Enabling power management...
[....] Starting anac(h)ronistic cron: anacron
[....] Starting deferred execution scheduler: atd
[....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
[....] Enabling additional executable binary formats: binfmt-support
[....] Starting bluetooth: bluetoothd
[....] Starting Common Unix Printing System: cupsd
[....] Starting DNS forwarder and DHCP server: dnsmasq
[....] Starting web server: apache2
[....] Starting periodic command scheduler: cron
[....] Loading cpufreq kernel modules...
[....] CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...
Applying Intel IA32 Microcode update... done.
[....] Starting MySQL database server: mysqld
[....] Starting NFS common utilities: statd idmapd
[....] PulseAudio configured for per-user sessions ...
[....] Starting rpcbind daemon...
[....] Starting OpenBSD Secure Shell server: sshd
[....] Starting VirtualBox kernel modules
Workaround:
* switch to the tty1
* /etc/init.d/gdm3 restart
Cheers,
Laurento
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (450, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdm3 depends on:
ii accountsservice 0.6.21-5
ii adduser 3.113+nmu3
ii dconf-gsettings-backend 0.12.1-2
ii dconf-tools 0.12.1-2
ii debconf [debconf-2.0] 1.5.44
ii dpkg 1.16.4.3
ii gir1.2-freedesktop 1.32.1-1
ii gir1.2-glib-2.0 1.32.1-1
ii gnome-session [x-session-manager] 3.4.2.1-1
ii gnome-session-bin 3.4.2.1-1
ii gnome-session-fallback [x-session-manager] 3.4.2.1-1
ii gnome-settings-daemon 3.4.2-3
ii gnome-terminal [x-terminal-emulator] 3.4.1.1-1
ii gsettings-desktop-schemas 3.4.2-1
ii libaccountsservice0 0.6.21-5
ii libatk1.0-0 2.4.0-2
ii libattr1 1:2.4.46-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-33
ii libcairo-gobject2 1.12.2-2
ii libcairo2 1.12.2-2
ii libcanberra-gtk3-0 0.28-4
ii libcanberra0 0.28-4
ii libdbus-1-3 1.6.0-1
ii libdbus-glib-1-2 0.100-1
ii libfontconfig1 2.9.0-6
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libglib2.0-bin 2.32.3-1
ii libgtk-3-0 3.4.2-2
ii libpam-modules 1.1.3-7.1
ii libpam-runtime 1.1.3-7.1
ii libpam0g 1.1.3-7.1
ii libpango1.0-0 1.30.0-1
ii librsvg2-common 2.36.1-1
ii libselinux1 2.1.9-5
ii libupower-glib1 0.9.17-1
ii libwrap0 7.6.q-23
ii libx11-6 2:1.5.0-1
ii libxau6 1:1.0.7-1
ii libxdmcp6 1:1.1.1-1
ii libxklavier16 5.2.1-1
ii libxrandr2 2:1.3.2-2
ii lsb-base 4.1+Debian7
ii metacity [x-window-manager] 1:2.34.3-2
ii policykit-1-gnome 0.105-2
ii upower 0.9.17-1
ii x11-common 1:7.7+1
ii x11-xserver-utils 7.7~3
Versions of packages gdm3 recommends:
ii desktop-base 7.0.0
ii gnome-icon-theme 3.4.0-2
ii libatk-adaptor [at-spi] 2.5.3-1
ii x11-xkb-utils 7.7~1
ii xserver-xephyr 2:1.12.1.902-1
ii xserver-xorg 1:7.7+1
ii zenity 3.4.0-2
Versions of packages gdm3 suggests:
ii gnome-mag 1:0.16.3-1
ii gnome-orca 3.4.2-2
ii gnome-shell 3.4.1-8
pn gok <none>
ii libpam-gnome-keyring 3.4.1-4
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
--- End Message ---
--- Begin Message ---
Le vendredi 01 février 2013 à 11:16 +0100, Laurento a écrit :
> This problem doesn't happen since months here, I think it has been
> fixed implicitly by some gnome3 related upgrade.
Might be the new gnome-settings-daemon with its bugfixes.
Thanks for checking.
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--- End Message ---
