Your message dated Mon, 16 Feb 2015 08:55:44 +0100
with message-id <20150216075544.ga21...@sym.noone.org>
and subject line Re: Bug#778464: systemd: HandleLidSwitch=suspend in
/etc/systemd/logind.conf ignored since one of the recent uploads
has caused the Debian Bug report #778464,
regarding system
Stefan Fritsch [2015-02-13 10:32 +0100]:
> Can't you agree that the best way forward for jessie is to change this in
> systemd?
For jessie I'd be okay with this. I'd rather have the actual unit in
util-linux and then unmask it in systemd, but that'd require even more
coordination/uploads.
I'll d
Package: systemd
Version: 215-11
purging the systemd package leaves the system dirty, as it does not
remove /etc/sytemd/system/*remote-fs* (or something similar) and
possibly other files and directories created on postinst
one cannot simply remove the /etc/systemd directory as it may contains
fil
> I haven't looked at the service file in more detail, but the WantedBy=
> line is certainly wrong. Please remove that one.
Oops, indeed this is wrong; good I didn't forwarded it to #755359
> The display manager is supposed to be started via the
> display-manager.service symlink.
signature.asc
Your message dated Sun, 15 Feb 2015 22:54:13 +0100
with message-id <54e11585.9000...@debian.org>
and subject line Re: Bug#778362: Periodic (90s) restart of KDM by systemd on
jessie
has caused the Debian Bug report #778362,
regarding Periodic (90s) restart of KDM by systemd on jessie
to be marked a
Processing control commands:
> tags -1 moreinfo unreproducible
Bug #778464 [systemd] systemd: HandleLidSwitch=suspend in
/etc/systemd/logind.conf ignored since one of the recent uploads
Added tag(s) unreproducible and moreinfo.
> severity -1 important
Bug #778464 [systemd] systemd: HandleLidSwitc
control: tags -1 moreinfo unreproducible
control: severity -1 important
Am 15.02.2015 um 13:59 schrieb Axel Beckert:
> 20c22
> < #HandleLidSwitch=suspend
> ---
>> HandleLidSwitch=suspend
Since that is the default anyway, no need to uncomment it.
> Until the last reboot, the laptop went to sleep
Am 15.02.2015 um 15:24 schrieb Thomas Koch:
> Hi,
>
> I want to know, why sleepd (debian package) does not start. Before systemd I
> put a set -x on top of the init.d script and look where the script exits.
>
> Now the script exits in some systemd lsb script.
>
> How can I get more info what's
Am 14.02.2015 um 09:14 schrieb Alexandre Detiste:
> tchet@antec:~$ systemctl cat kdm
> # /etc/systemd/system/kdm.service
> [Unit]
> Description=KDM Display Manager
> Conflicts=getty@tty1.service
> After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service
>
> [Service]
> ExecSta
Hi,
I want to know, why sleepd (debian package) does not start. Before systemd I
put a set -x on top of the init.d script and look where the script exits.
Now the script exits in some systemd lsb script.
How can I get more info what's going on?
Where do I find a tutorial for Debian Maintainers
Package: systemd
Version: 215-12
Severity: grave
Justification: Unexpected behaviour change during freeze which may lead to
hardware damage
Dear Maintainer,
* What led up to the situation?
After 50 days of uptime I recently rebooted my Thinkpad X240. Last two
reboots were on:
# uprecords -B
Hi,
On 13/02/15 10:32, Stefan Fritsch wrote:
Once jessie is released, the correct long-term fix can be discussed in a
more relaxed way.
As a user impacted by this issue, I would like to second this motion!
Most important is to have it work for the Debian users.
Thanks, Eric
--
I'm subscribed
12 matches
Mail list logo
