** Changed in: snappy
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617251
Title:
console-conf unkillable
To manage notifications about this bug go to:
https://bugs
wouldnt there be any trace of this in a log ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617251
Title:
console-conf unkillable
To manage notifications about this bug go to:
https://bugs.launchp
Hey
Indeed apparmor mediates reception of UNIX signals. There might be a bug
in the base policy where unconfined SIGKILL is not allowed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617251
Title:
see the prompts in the description ;) (pi3 and dragonboard) ...
this is after Ctrl-C'ing on teh serial terminal and then ssh'ing into the
system... from the ssh shell i can not kill -9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
I can't reproduce this in a KVM. Which system is this on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617251
Title:
console-conf unkillable
To manage notifications about this bug go to:
https://
there is nothing in any logs (dmesg, syslog)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617251
Title:
console-conf unkillable
To manage notifications about this bug go to:
https://bugs.launchpa
Check dmesg for AppArmor DENIED messages; it's easy to write a policy
that would forbid kill -9 from killing something.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617251
Title:
console-c
On Fr, 2016-08-26 at 12:44 +, Mathieu Trudel-Lapierre wrote:
> I don't know why you're seeing the PID persist, clearly something
> unexpected happened, but console-conf is meant to be forced onto the
> user if the system isn't otherwise coming pre-configured with a user.
> It
> should not be ki
I don't know why you're seeing the PID persist, clearly something
unexpected happened, but console-conf is meant to be forced onto the
user if the system isn't otherwise coming pre-configured with a user. It
should not be killed, as that would get one a system that is unusable
(with no user to logi
note that i can call "kill -9" as often as i want so this isnt systemd
restarting the process or something, it does not get killed at all (the
PID persists).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
10 matches
Mail list logo
