Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Dear Andreas, I guess a fresh installation is not yet an option right now, since it would make to much effort. I guess I'll wait until GDM 3.10 hits Debian/testing. The only thing, if I find some time, I could do is set up a new virtual installation of Debian/testing. But you see, you also run into a bug with the display managers. :-) I hope that an Xorg or DM update will fix things for me. Also can't await to see E18 in Debian. Maybe your E17 crashes because of the by default enabled composite manager, I also have to disable the module for E17.3 because with it enabled things get very slow and sluggish. With many greetings, Adrian On Wed, 2014-01-22 at 15:49 +0100, Andreas Cadhalpun wrote: Hi Adrian, On 22.01.2014 14:40, Adrian Immanuel Kieß wrote: yes the screen does indeed turn off for a while while GDM is loading when I dont't exit plymouth. Strange. Maybe should I purge GDM3 and try over again? I have no clue why GDM does only works so sluggish for me. This may help - at least I think this can't make things worse... As noted in my last mail, with XDM, KDM and lightdm I can't even start my xinitrc session, since they refuse to exec enlightenment_start. I just installed lightdm and e17 and started e17 from lightdm. This worked for me (although e17 segfaulted shortly after that). I really have no clue where this all comes from, this is why I am asking on the bugreport list. :-) To note, my installation is a Debian 5 installation, upgraded to Debian/testing and running on so far. I already reported other sometimes strange bugs happening for me, for example gkrellm seqfaulting when I type an umlaut; I use xmodmap by the way. Maybe you have an idea how to make GDM run smoothly again. If you have free hard disk space, I would recommend you to create a fresh jessie installation and see, whether these problems happen there as well. If yes, you know how to reproduce the problem in a fresh installation, which might help solving it. If no, you should think about migrating to the fresh installation. Best regards, Andreas -- With greetings from Leipzig, Germany. Adrian Immanuel Kieß Administrator programmer Unix / Perl / LaTeX mail: adrian (at) kiess.at www: http://www.kiess.at signature.asc Description: This is a digitally signed message part
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Dear Andreas, yes the screen does indeed turn off for a while while GDM is loading when I dont't exit plymouth. Maybe should I purge GDM3 and try over again? I have no clue why GDM does only works so sluggish for me. As noted in my last mail, with XDM, KDM and lightdm I can't even start my xinitrc session, since they refuse to exec enlightenment_start. I really have no clue where this all comes from, this is why I am asking on the bugreport list. :-) To note, my installation is a Debian 5 installation, upgraded to Debian/testing and running on so far. I already reported other sometimes strange bugs happening for me, for example gkrellm seqfaulting when I type an umlaut; I use xmodmap by the way. Maybe you have an idea how to make GDM run smoothly again. Thank you very much, Adrian On Wed, 2014-01-22 at 03:03 +0100, Andreas Cadhalpun wrote: Hi Adrian, On 22.01.2014 01:24, Adrian Immanuel Kieß wrote: the missing part is then: Starting Enable support for additional executable binary formats... 76 Starting LSB: Start acpi_fakekey daemon... 77 Starting LSB: Bluetooth monitoring daemon... 78 Starting LSB: OpenBSD Secure Shell server... 79 Starting LSB: Fetch LDAP SSL public key from the server... 80 Starting Initialize hardware monitoring sensors... 81 Starting /etc/rc.local Compatibility... 82 Starting System Logging Service... 83 Starting Permit User Sessions... 84 [^[[32m OK ^[[0m] Listening on Virtual machine lock manager socket. 85 [^[[32m OK ^[[0m] Listening on Avahi mDNS/DNS-SD Stack Activation Socket. 86 [^[[32m OK ^[[0m] Listening on GPS (Global Positioning System) Daemon Sockets. 87 [^[[32m OK ^[[0m] Listening on PC/SC Smart Card Daemon Activation Socket. 88 [^[[32m OK ^[[0m] Listening on ACPID Listen Socket. 89 [^[[32m OK ^[[0m] Listening on D-Bus System Message Bus Socket. 90 Starting Avahi mDNS/DNS-SD Stack... 91 Starting Login Service... 92 Starting Accounts Service... 93 Starting D-Bus System Message Bus... 94 [^[[32m OK ^[[0m] Started D-Bus System Message Bus. 95 Starting LSB: network connection manager... 96 Starting LSB: Light Display Manager... 97 Starting Virtualization daemon... (taken from /var/log/boot.log) Strange, I can see (using plymouth exited with Esc) lines like: Starting Initialize hardware monitoring sensors... or Starting LSB: network connection manager... I'd like to note when I boot with plymouth and I am not exiting plymouth with [Home] then even the screen suspends and wents off while GDM is starting up. For me the screen goes black (but still is on) for a moment just before GDM comes up. Does it really turn off for you? I have a lot of problems with the window display managers in Debian/testing lateley. With XDM I can't even login with any user and all the other display managers won't execute enlightenment_start and refuse to open a E17 session. :( I did reboot but GDM won't show the banner or the background image set in greeter.gsettings. I don't understand this. The banner works for me. Best regards, Andreas -- With greetings from Leipzig, Germany. Adrian Immanuel Kieß Administrator programmer Unix / Perl / LaTeX mail: adrian (at) kiess.at www: http://www.kiess.at signature.asc Description: This is a digitally signed message part
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Hi Adrian, On 22.01.2014 14:40, Adrian Immanuel Kieß wrote: yes the screen does indeed turn off for a while while GDM is loading when I dont't exit plymouth. Strange. Maybe should I purge GDM3 and try over again? I have no clue why GDM does only works so sluggish for me. This may help - at least I think this can't make things worse... As noted in my last mail, with XDM, KDM and lightdm I can't even start my xinitrc session, since they refuse to exec enlightenment_start. I just installed lightdm and e17 and started e17 from lightdm. This worked for me (although e17 segfaulted shortly after that). I really have no clue where this all comes from, this is why I am asking on the bugreport list. :-) To note, my installation is a Debian 5 installation, upgraded to Debian/testing and running on so far. I already reported other sometimes strange bugs happening for me, for example gkrellm seqfaulting when I type an umlaut; I use xmodmap by the way. Maybe you have an idea how to make GDM run smoothly again. If you have free hard disk space, I would recommend you to create a fresh jessie installation and see, whether these problems happen there as well. If yes, you know how to reproduce the problem in a fresh installation, which might help solving it. If no, you should think about migrating to the fresh installation. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Dear Andreas, I can't find the missing part in /var/log/syslog. The console output seem mostly to stop at Starting fancontrol Regarding to portmap; that's true, but it was not obvious for me at first that I have to delete the old portmap configuration files to make rpcbind working again. :-) I have another small question; Can you tell me how I can set the banner text in GDM v3.8? I tried with dconf and the configuration files under /etc/gdm3 but nothing seems to work. I attached my greetings.gsettings file. It now seems to be ignored by GDM 3.8. With many greetings, Adrian On Mon, 2014-01-20 at 16:17 +0100, Andreas Cadhalpun wrote: Hi Adrian, On 20.01.2014 04:42, Adrian Immanuel Kieß wrote: following to your suggestion I installed systemd-sysv and it is really nice; the system boots much quicker. ;) As a side note, I had to apt-get purge portmap to make nfs-kernel-server working again with systemd; This is not really surprising, considering that portmap is only available in oldstable... but not all of the console output is shown again while booting up, because of GDM is loading and takes the console output away. Can you specify which output is missing, e.g. by copying the relevant part from /var/log/syslog? Installing systemd now fixed the missing console output while shutting the system down. That's strange... So this seems like a bug in sysvinit-core. Best regards, Andreas -- With greetings from Leipzig, Germany. Adrian Immanuel Kieß Administrator programmer Unix / Perl / LaTeX mail: adrian (at) kiess.at www: http://www.kiess.at # These are the options for the greeter session that can be set # through GSettings. Any GSettings setting that is used by the # greeter session can be set here. # Theming options #[org.gnome.desktop.interface] #gtk-theme='Adwaita' # Prevent the power management icon from showing up [org.gnome.power-manager] icon-policy='never' # Disabling sound in the greeter #[org.gnome.desktop.sound] #event-sounds=false [org.gnome.desktop.background] picture-uri='file:///etc/gdm3/mandolux-bcstar-l-1280.jpg' picture-options='zoom' # - Disable user list # disable-user-list=true # - Disable restart buttons # disable-restart-buttons=true # - Show a login welcome message banner-message-enable=true banner-message-text='Welcome to g6.lan.dac' signature.asc Description: This is a digitally signed message part
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Hi Adrian, On 21.01.2014 09:11, Adrian Immanuel Kieß wrote: I can't find the missing part in /var/log/syslog. The console output seem mostly to stop at Starting fancontrol Then you can probably find them in /var/log/boot.log. Regarding to portmap; that's true, but it was not obvious for me at first that I have to delete the old portmap configuration files to make rpcbind working again. :-) To prevent such problems, I prefer to purge outdated packages as soon as they aren't available anymore. I have another small question; Can you tell me how I can set the banner text in GDM v3.8? I tried with dconf and the configuration files under /etc/gdm3 but nothing seems to work. I attached my greetings.gsettings file. It now seems to be ignored by GDM 3.8. Your greetings.gsettings file looks fine, but you have to reboot for changes to take effect. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Dear Andreas, the missing part is then: Starting Enable support for additional executable binary formats... 76 Starting LSB: Start acpi_fakekey daemon... 77 Starting LSB: Bluetooth monitoring daemon... 78 Starting LSB: OpenBSD Secure Shell server... 79 Starting LSB: Fetch LDAP SSL public key from the server... 80 Starting Initialize hardware monitoring sensors... 81 Starting /etc/rc.local Compatibility... 82 Starting System Logging Service... 83 Starting Permit User Sessions... 84 [^[[32m OK ^[[0m] Listening on Virtual machine lock manager socket. 85 [^[[32m OK ^[[0m] Listening on Avahi mDNS/DNS-SD Stack Activation Socket. 86 [^[[32m OK ^[[0m] Listening on GPS (Global Positioning System) Daemon Sockets. 87 [^[[32m OK ^[[0m] Listening on PC/SC Smart Card Daemon Activation Socket. 88 [^[[32m OK ^[[0m] Listening on ACPID Listen Socket. 89 [^[[32m OK ^[[0m] Listening on D-Bus System Message Bus Socket. 90 Starting Avahi mDNS/DNS-SD Stack... 91 Starting Login Service... 92 Starting Accounts Service... 93 Starting D-Bus System Message Bus... 94 [^[[32m OK ^[[0m] Started D-Bus System Message Bus. 95 Starting LSB: network connection manager... 96 Starting LSB: Light Display Manager... 97 Starting Virtualization daemon... (taken from /var/log/boot.log) I'd like to note when I boot with plymouth and I am not exiting plymouth with [Home] then even the screen suspends and wents off while GDM is starting up. I have a lot of problems with the window display managers in Debian/testing lateley. With XDM I can't even login with any user and all the other display managers won't execute enlightenment_start and refuse to open a E17 session. I did reboot but GDM won't show the banner or the background image set in greeter.gsettings. Thank you for your reply, Adrian On Tue, 2014-01-21 at 19:50 +0100, Andreas Cadhalpun wrote: Hi Adrian, On 21.01.2014 09:11, Adrian Immanuel Kieß wrote: I can't find the missing part in /var/log/syslog. The console output seem mostly to stop at Starting fancontrol Then you can probably find them in /var/log/boot.log. Regarding to portmap; that's true, but it was not obvious for me at first that I have to delete the old portmap configuration files to make rpcbind working again. :-) To prevent such problems, I prefer to purge outdated packages as soon as they aren't available anymore. I have another small question; Can you tell me how I can set the banner text in GDM v3.8? I tried with dconf and the configuration files under /etc/gdm3 but nothing seems to work. I attached my greetings.gsettings file. It now seems to be ignored by GDM 3.8. Your greetings.gsettings file looks fine, but you have to reboot for changes to take effect. Best regards, Andreas -- With greetings from Leipzig, Germany. Adrian Immanuel Kieß Administrator programmer Unix / Perl / LaTeX mail: adrian (at) kiess.at www: http://www.kiess.at signature.asc Description: This is a digitally signed message part
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Hi Adrian, On 22.01.2014 01:24, Adrian Immanuel Kieß wrote: the missing part is then: Starting Enable support for additional executable binary formats... 76 Starting LSB: Start acpi_fakekey daemon... 77 Starting LSB: Bluetooth monitoring daemon... 78 Starting LSB: OpenBSD Secure Shell server... 79 Starting LSB: Fetch LDAP SSL public key from the server... 80 Starting Initialize hardware monitoring sensors... 81 Starting /etc/rc.local Compatibility... 82 Starting System Logging Service... 83 Starting Permit User Sessions... 84 [^[[32m OK ^[[0m] Listening on Virtual machine lock manager socket. 85 [^[[32m OK ^[[0m] Listening on Avahi mDNS/DNS-SD Stack Activation Socket. 86 [^[[32m OK ^[[0m] Listening on GPS (Global Positioning System) Daemon Sockets. 87 [^[[32m OK ^[[0m] Listening on PC/SC Smart Card Daemon Activation Socket. 88 [^[[32m OK ^[[0m] Listening on ACPID Listen Socket. 89 [^[[32m OK ^[[0m] Listening on D-Bus System Message Bus Socket. 90 Starting Avahi mDNS/DNS-SD Stack... 91 Starting Login Service... 92 Starting Accounts Service... 93 Starting D-Bus System Message Bus... 94 [^[[32m OK ^[[0m] Started D-Bus System Message Bus. 95 Starting LSB: network connection manager... 96 Starting LSB: Light Display Manager... 97 Starting Virtualization daemon... (taken from /var/log/boot.log) Strange, I can see (using plymouth exited with Esc) lines like: Starting Initialize hardware monitoring sensors... or Starting LSB: network connection manager... I'd like to note when I boot with plymouth and I am not exiting plymouth with [Home] then even the screen suspends and wents off while GDM is starting up. For me the screen goes black (but still is on) for a moment just before GDM comes up. Does it really turn off for you? I have a lot of problems with the window display managers in Debian/testing lateley. With XDM I can't even login with any user and all the other display managers won't execute enlightenment_start and refuse to open a E17 session. :( I did reboot but GDM won't show the banner or the background image set in greeter.gsettings. I don't understand this. The banner works for me. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Hi Adrian, On 20.01.2014 04:42, Adrian Immanuel Kieß wrote: following to your suggestion I installed systemd-sysv and it is really nice; the system boots much quicker. ;) As a side note, I had to apt-get purge portmap to make nfs-kernel-server working again with systemd; This is not really surprising, considering that portmap is only available in oldstable... but not all of the console output is shown again while booting up, because of GDM is loading and takes the console output away. Can you specify which output is missing, e.g. by copying the relevant part from /var/log/syslog? Installing systemd now fixed the missing console output while shutting the system down. That's strange... So this seems like a bug in sysvinit-core. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Hi Adrian, On 19.01.2014 06:35, Adrian Immanuel Kieß wrote: installing systemd-shim helped fine. That's great. I'd like to note that GDM3 in Debian/testing now takes a great time to load and that the console output is not shown right when GDM3 leaves X mode. How long is 'a great time'? Can you make a picture of how the console output is wrong? Additionally; I've read on http://www.phoronix.com/ that Debian now possibly likes to switch to systemd. Is it recommended now to switch to systemd and install systemd-sysv? Currently the answer to this question probably depends strongly on who you ask. This will hopefully change soon, when the technical committee has made it's decision. [1] If you don't feel curious about modern init systems, it is possible to stay with sysvinit for jessie. But since GNOME upstream decided to use features provided by systemd that only afterwards were available on other init systems via systemd-shim, you might want to try out systemd-sysv, as similiar upstream changes might happen again. (And a modern init system is an improvement over the old sysvinit.) I hope that helps you. Best regards, Andreas 1: http://bugs.debian.org/727708 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Dear Andreas, following to your suggestion I installed systemd-sysv and it is really nice; the system boots much quicker. As a side note, I had to apt-get purge portmap to make nfs-kernel-server working again with systemd; but not all of the console output is shown again while booting up, because of GDM is loading and takes the console output away. Installing systemd now fixed the missing console output while shutting the system down. Thanks for your help. With many greetings, Adrian On Sun, 2014-01-19 at 17:12 +0100, Andreas Cadhalpun wrote: Hi Adrian, On 19.01.2014 06:35, Adrian Immanuel Kieß wrote: installing systemd-shim helped fine. That's great. I'd like to note that GDM3 in Debian/testing now takes a great time to load and that the console output is not shown right when GDM3 leaves X mode. How long is 'a great time'? Can you make a picture of how the console output is wrong? Additionally; I've read on http://www.phoronix.com/ that Debian now possibly likes to switch to systemd. Is it recommended now to switch to systemd and install systemd-sysv? Currently the answer to this question probably depends strongly on who you ask. This will hopefully change soon, when the technical committee has made it's decision. [1] If you don't feel curious about modern init systems, it is possible to stay with sysvinit for jessie. But since GNOME upstream decided to use features provided by systemd that only afterwards were available on other init systems via systemd-shim, you might want to try out systemd-sysv, as similiar upstream changes might happen again. (And a modern init system is an improvement over the old sysvinit.) I hope that helps you. Best regards, Andreas 1: http://bugs.debian.org/727708 -- With greetings from Leipzig, Germany. Adrian Immanuel Kieß Administrator programmer Unix / Perl / LaTeX mail: adrian (at) kiess.at www: http://www.kiess.at signature.asc Description: This is a digitally signed message part
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Dear Andreas,
installing systemd-shim helped fine.
I'd like to note that GDM3 in Debian/testing now takes a great time to
load and that the console output is not shown right when GDM3 leaves X
mode.
Additionally; I've read on http://www.phoronix.com/ that Debian now
possibly likes to switch to systemd. Is it recommended now to switch to
systemd and install systemd-sysv?
Thank you very much.
With many greetings,
Adrian
On Fri, 2014-01-17 at 12:04 +0100, Andreas Cadhalpun wrote:
Hi Adrian,
On 17.01.2014 05:09, Adrian Immanuel Kiess wrote:
* What led up to the situation?
Trying to restart system via GDM
* What exactly did you do (or not do) that was effective (or
ineffective)?
Clicking {Restart} button
* What was the outcome of this action?
None
* What outcome did you expect instead?
System restarting
currently in Debian/testing GDM does not restart the system after clicking
{Restart}.
This is due to a missing dependency on systemd-shim | systemd-sysv, see [1].
So you can either install systemd-shim or switch your init system to
systemd, which can be achieved by installing systemd-sysv or adding
the boot parameter 'init=/bin/systemd'.
The root password is asked thou, but no action is taken afterwards.
The strange asking for a root password is tracked in Bug#731882 [2].
Thank you for your efforts.
Thanks for reporting bugs.
Best regards,
Andreas
1: http://bugs.debian.org/726763
2: http://bugs.debian.org/731882
--
With greetings from Leipzig, Germany.
Adrian Immanuel Kieß
Administrator programmer
Unix / Perl / LaTeX
mail: adrian (at) kiess.at
www: http://www.kiess.at
signature.asc
Description: This is a digitally signed message part
Bug#726763: Bug#735628: gdm3: Does not restart system when clicking {Restart}
Hi Adrian,
On 17.01.2014 05:09, Adrian Immanuel Kiess wrote:
* What led up to the situation?
Trying to restart system via GDM
* What exactly did you do (or not do) that was effective (or
ineffective)?
Clicking {Restart} button
* What was the outcome of this action?
None
* What outcome did you expect instead?
System restarting
currently in Debian/testing GDM does not restart the system after clicking
{Restart}.
This is due to a missing dependency on systemd-shim | systemd-sysv, see [1].
So you can either install systemd-shim or switch your init system to
systemd, which can be achieved by installing systemd-sysv or adding
the boot parameter 'init=/bin/systemd'.
The root password is asked thou, but no action is taken afterwards.
The strange asking for a root password is tracked in Bug#731882 [2].
Thank you for your efforts.
Thanks for reporting bugs.
Best regards,
Andreas
1: http://bugs.debian.org/726763
2: http://bugs.debian.org/731882
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
