Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

Control: reassign -1 systemd 238-4 Control: retitle -1 Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm On 2018-04-09 15:10:47 +0200, Vincent Lefevre wrote: > After the upgrade to policykit-1 0.105-20, the Restart, Suspend, > Hibernate, Shut Down menu entries are all grey

Bug#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

On 2018-04-09 20:41:55 +0200, Michael Biebl wrote: > Not reproducible with a default GNOME / systemd as init installation. > > Please investigate, if this issue is specific to sysvinit, xfce or some > other custom modification (like special kernel parameters) I'd say that it is specific to sysvin

Bug#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

On 2018-04-10 12:45:51 +0200, Michael Biebl wrote: > Do you use hidepid for /proc? No, I don't. > > Apr 9 15:33:25 ypig dbus-daemon[2930]: [system] Successfully activated > > service 'org.freedesktop.ConsoleKit' > > Please uninstall/purge consolekit. It's not only useless when logind is > used

Bug#788498: udev: breaks the keyboard configuration

On 2015-06-12 13:11:45 +0200, Martin Pitt wrote: > Vincent Lefevre [2015-06-11 23:51 +0200]: > > Severity: grave > > Justification: renders package unusable > > This bug is highly hardware specific and specific to local > configuration, so it does only affect very few pe

Bug#788498: udev: breaks the keyboard configuration

Control: tags -1 - moreinfo Control: clone -1 -2 Control: retitle -1 udev: the change of keyboard configuration system should be announced Control: retitle -2 udev: "udevadm trigger /dev/input/event*" doesn't work Hi Martin, I've found the problem: the command udevadm trigger /dev/input/event

Bug#788498: udev: breaks the keyboard configuration

On 2015-06-19 21:53:31 +0200, Sven Arvidsson wrote: > While looking into this I also discovered that there is finally a way > to get sane settings by setting > /sys/module/hid_apple/parameters/iso_layout to 0. Thanks. I confirm that this is working. > It's still handy to use udev to assign a ded

Bug#790974: systemd: System Clock not saved to the Hardware Clock (RTC) at shutdown

Package: systemd Version: 221-1 Severity: important When I reboot my HP Zbook G2 after a few days, the clock time is several seconds late, and this can be something like 20 seconds (probably more if I reboot less often), so that it means that it takes several hours to be corrected. This can break

Bug#791897: systemd: incorrect x bit for group on .journal log files after setting Storage=persistent

Package: systemd Version: 222-1 Severity: normal The .journal files under /var/log/journal/*/ have an incorrect x bit for the group: -rw-r-x---+ 1 root root50331648 2015-07-09 12:25:09 system.journal -rw-r-x---+ 1 root systemd-journal 16777216 2015-07-09 11:27:15 user-1000.journal A

Bug#791897: systemd: incorrect x bit for group on .journal log files after setting Storage=persistent

Control: forwarded -1 https://github.com/systemd/systemd/issues/534 On 2015-07-09 13:37:58 +0200, Michael Biebl wrote: > Please consider filing this upstream. Done and set forwarded. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#791920: systemd: with ifupdown, ifup@.service forces ifup eth0 even with no Ethernet link

Package: systemd Version: 222-1 Severity: important Note: the following applies when /etc/network/interfaces contains: allow-hotplug eth0 iface eth0 inet dhcp which is the default. With ifupdown, ifup@.service forces ifup eth0 even with no Ethernet link (e.g. no Ethernet cable plugged in), whic

Bug#766182: systemd: incorrect dmesg message about missing nss-myhostname

On 2015-09-11 08:32:41 +0200, Michael Biebl wrote: > The presence of /etc/hosts does not mean that your local hostname is > configured there. It can easily get out of sync from what's configured > in /etc/hostname. I disagree: you could also check whether the local hostname is configured there. An

Bug#801354: libpam-systemd: breaks lightdm: Failed to create session: Connection timed out

Package: libpam-systemd Version: 227-1 Severity: serious After the upgrade to systemd packages 227-1, I get various timeouts with lightdm: [...] Oct 09 02:57:45 zira systemd[1581]: run-rpc_pipefs.mount: Mount process exited, code=exited status=1 Oct 09 02:57:45 zira systemd[1581]: Failed unmount

Bug#801354: libpam-systemd: breaks lightdm: Failed to create session: Connection timed out

On 2015-10-09 03:22:17 +0200, Michael Biebl wrote: > Why does a simple umount fail? I don't know. These errors appeared with this upgrade. I never got such errors before (logs begin at Fri 2015-07-03 14:03:14 CEST). > Which version of libmount1/mount is installed? 2.27-3 for both. > Please prov

Bug#788499: udev: incorrect documentation in /lib/udev/hwdb.d/60-keyboard.hwdb

Control: found -1 227-2 Control: forwarded -1 https://github.com/systemd/systemd/issues/1813 On 2015-11-09 02:24:02 +0100, Michael Biebl wrote: > Thanks for your bug report. Since this is not a Debian specific issue, > it would be great if you can file this issue upstream at > https://github.com/s

Bug#809513: udev: typo in /usr/share/doc/udev/README.Debian.gz

Package: udev Version: 228-2+b1 Severity: minor In the /usr/share/doc/udev/README.Debian.gz file: Then for all of thse use a command like It should be "these". I also suggest adding commas for clarity: Then, for all of these, use a command like -- Package-specific in

Bug#825941: screen is killed by systemd when the user logs out

Hi, On 2016-05-31 18:19:41 +0200, Salvatore Bonaccorso wrote: > Not the screen maintainer here. JFR, this should be handled in systemd > as #825394 and disabled by default in Debian again with the 230-2 > upload. I'll test once 230-2 is available. But the change in 230-2 might also just be a work

Bug#825995: systemd: slow boot: pam_systemd(su:session): Failed to create session: Connection timed out

Package: systemd Version: 230-2 Severity: important As of systemd 230, the boot is much slower than before, which is rather annoying. journalctl shows: [...] Jun 01 10:14:24 zira systemd[1]: Started Initialize hardware monitoring sensors. Jun 01 10:14:24 zira systemd[1]: Starting LSB: lm-sensors

Bug#825995: systemd: slow boot: pam_systemd(su:session): Failed to create session: Connection timed out

On 2016-06-01 10:40:53 +0200, Vincent Lefevre wrote: > which is new. Earlier in the logs: > > Jun 01 10:14:22 zira su[718]: Successful su for vinc17 by root > Jun 01 10:14:22 zira systemd[1]: Reached target Sockets. > Jun 01 10:14:22 zira su[718]: + ??? root:vinc17 > Jun 01 10:

Bug#825995: systemd: slow boot: pam_systemd(su:session): Failed to create session: Connection timed out

On 2016-06-01 11:35:42 +0200, Michael Biebl wrote: > Am 01.06.2016 um 10:40 schrieb Vincent Lefevre: > > > This is part of one of my /etc/network/if-up.d scripts, where I have > > "su vinc17 -c some_script" (which just does a rewrite of one of my > > config file

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

Package: systemd Version: 232-7 Severity: minor Tags: upstream patch I've reported the following bug upstream: https://github.com/systemd/systemd/issues/4842 With the following commands after "zsh -f" autoload -U compinit compinit setopt RC_QUOTES the journalctl completion fails: cventin% j

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

On 2016-12-06 11:40:35 -0300, Felipe Sateler wrote: > I think the better fix is to somehow make zsh use default option > values when evaluating the completion functions. I see that some > completions use `emulate -LR zsh` (although both -L and -R are skipped > in some completions). Could you try if

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

On 2016-12-06 16:02:07 +0100, Vincent Lefevre wrote: > No, this has no effect. Even > > emulate -LR zsh > unsetopt RC_QUOTES > > has no effect. I think that the problem comes from the fact that > the '' is parsed at completion time. > > Actually, the &quo

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

On 2016-12-07 10:28:45 -0300, Felipe Sateler wrote: > Hi ZSH Maintainers, Not sure they are reading (or have they been Bcc'ed?), but I started a thread in zsh-workers: http://www.zsh.org/mla/workers/2016/msg02588.html hoping the issue could be solved in zsh itself. But according to the discuss

Bug#850703: systemd: incorrect LSB support with monit's init script

Package: systemd Version: 232-8 Severity: normal The monit service (from the monit package) should be started last and stopped first. This is not the case with systemd. I've attached monit's init script. -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers

Bug#850703: systemd: incorrect LSB support with monit's init script

Hi Martin, On 2017-01-09 16:41:20 +0100, Martin Pitt wrote: > Hello Vincent, > > Vincent Lefevre [2017-01-09 15:15 +0100]: > > The monit service (from the monit package) should be started last and > > stopped first. This is not the case with systemd. > > &g

Re: Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

-01-11 16:20:35 +0100, Vincent Lefevre wrote: > On 2017-01-11 15:09:49 +, Ben Hutchings wrote: > > Unless you can show that some data had been written *and flushed* to > > disk by the application, but was not readable afterward - this does not > > count. Writes are buffere

Re: Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

On 2017-01-11 18:09:51 +0100, Michael Biebl wrote: > Am 11.01.2017 um 18:05 schrieb Michael Biebl: > > Why is this no normal shutdown? Services are not stopped as usual. > > Did you actually have a file corruption? Yes, /var/log/monit.log, which got null bytes in it, and some other file created

Bug#850959: Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

On 2017-01-11 19:37:37 +0100, Michael Biebl wrote: > [moving this over to #850959] > Am 11.01.2017 um 19:13 schrieb Michael Biebl: > > Am 11.01.2017 um 19:12 schrieb Michael Biebl: > >> Am 11.01.2017 um 18:55 schrieb Vincent Lefevre: > >>> What info do you need? &

Bug#850703: systemd: incorrect LSB support with monit's init script

On 2017-01-11 18:20:14 +0100, Michael Biebl wrote: > Given that we only have a handful of packages left which use $all, our > time is better spent if those few packages add native service files. > > Please consider filing a bug report against monit for that. I've reported: https://bugs.debian.

Bug#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Package: systemd Version: 208-7 Severity: important The systemd upgrade from 204-14 to 208-7 introduced a regression in lightdm: the "Suspend", "Hibernate", "Restart" and "Shut Down" menu items of lightdm are now greyed out (even before the first login). Note: I'm using SysV init. -- Package-spe

Bug#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Control: reassign -1 systemd-shim On 2014-08-07 13:11:38 +0200, Michael Biebl wrote: > reassign 757348 systemd-shim It wasn't taken into account. Really reassigning... -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: W

Bug#766182: systemd: incorrect dmesg message about missing nss-myhostname

Package: systemd Version: 215-5+b1 Severity: minor dmesg output gives: systemd-hostnamed[3013]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! This is incorrect: nss-myhostname is not needed when there is a