Okay, thanks.
I guess I'll go so what's going on with getting this bug addressed in stable.
On Sun, 7/9/17, Simon McVittie wrote:
Subject: Re: systemd 230-7~bpo8+2 (bug causes shutdown freeze)
To: garnut992-deb...@yahoo.com
Cc: debian-backpo...@li
https://github.com/systemd/systemd/pull/6316
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
On 07/09/2017 10:22 AM, Brian Potkin wrote:
fvwm here. But I do not think the WM is relevant.
me either, but since three wm reported now, it is more evidence that wm
isn't relevant.
I reverted back to sysvinit/uninstalled systemd (and configured Xwrapper to
run X as root again, so it wou
On Sun 09 Jul 2017 at 00:37:08 -0700, Grant Chesy wrote:
> Followup-For: Bug #806256
> Package: systemd
> Version: 232-25
>
> Hello, I also experienced this bug.
>
> steps to reproduce:
> 1. start X with startx
> 2. switch to any VT from X
> 3. log in as the same user* as the user running X
> 4.
On Sun, 09 Jul 2017 at 00:30:49 +, garnut992-deb...@yahoo.com wrote:
> It says on the Debian Backports webpage (https://backports.debian.org/)
> that "backports are packages taken from the next Debian release (called
> "testing")." So I'm confused, why can't this be updated from testing? Is
> i
I will send a list when this happend again - sorry, hadn't a debug shell
at hand last time. The situation become a little bit worse because we
had some fixes upstream that prevent triggering this behaviour most of
the time.
___
Pkg-systemd-maintainer
Am 09.07.2017 um 12:05 schrieb Alf Gaida:
> ok - maybe more clear:
> * have a session running
> * have some applications and user processes open
> * end the session
> * when logged out, check running processes
> * be not happy about finding some processes that run with the logged out
> user as owne
Processing commands for cont...@bugs.debian.org:
> tags 867710 + moreinfo
Bug #867710 [systemd] systemd don't stop user processes reliable on logout,
even with KillUserProcesses=yes
Added tag(s) moreinfo.
> severity 867710 normal
Bug #867710 [systemd] systemd don't stop user processes reliable on
Processing commands for cont...@bugs.debian.org:
> reassign 867762 openssh-server
Bug #867762 [systemd] socket activated ssh leaves failed units behind
Bug reassigned from package 'systemd' to 'openssh-server'.
No longer marked as found in versions systemd/232-25.
Ignoring request to alter fixed v
ok - maybe more clear:
* have a session running
* have some applications and user processes open
* end the session
* when logged out, check running processes
* be not happy about finding some processes that run with the logged out
user as owner
even if KillUserProcesses=Yes is set.
And the worst
Package: systemd
Version: 232-25
Severity: normal
Hi,
I am using socket activated ssh since this (a) hopefully reduces the
possibility of not being able to log in in case of a daemon failure, and
socket activation does cleanly shut down the ssh daemon on system
shutdown, what ssh running as a dae
Followup-For: Bug #806256
Package: systemd
Version: 232-25
Hello, I also experienced this bug.
steps to reproduce:
1. start X with startx
2. switch to any VT from X
3. log in as the same user* as the user running X
4. logout from VT. If login to the VT was as the same user as the user
running
12 matches
Mail list logo
