On Tue, Oct 28, 2014 at 10:02:26AM +0900, Norbert Preining wrote:
> But the point is that there are events generated from kbd that are
> not coming over the socket, and thus are completely lost.
The service file was provided by a member of the systemd team IIRC.
Unfortunately I do not know much ab
I don't generally like adding "me too"s, but in this case I can't
resist. Today I went to give a public presentation using my
up-to-date Debian Jessie laptop. I booted the system with just
minutes before the talk was due to start, only to find that this was
the magical 30th boot where fsck is for
Hello,
I noticed that error messages relating to systemd-modules-load.service
on startup.
After the boot, I ran
$ sudo systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
Your message dated Wed, 05 Nov 2014 00:47:22 +0100
with message-id <5459658a.6060...@debian.org>
and subject line Re: Bug#765683: systemd: causes failure of startup scripts
has caused the Debian Bug report #765683,
regarding systemd: causes failure of startup scripts
to be marked as done.
This mea
thanks you can close this report as the problem is outside this package.
I found out that the nat function names are all new on experimental
kernel 3.17+ which is why iptables was failing.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintaine
Processing control commands:
> tags -1 moreinfo
Bug #765683 [systemd] systemd: causes failure of startup scripts
Added tag(s) moreinfo.
--
765683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
_
Control: tags -1 moreinfo
Am 17.10.2014 um 12:31 schrieb westlake:
> Package: systemd
> Version: 215-5+b1
> Severity: important
>
> I recently filed
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764950 , but it's not
> the netfilter package
>
> The problem is /lib/lsb/init-functions.d/40-s
Your message dated Tue, 04 Nov 2014 21:57:12 +0100
with message-id <54593da8.8070...@debian.org>
and subject line Re: Bug#768081: systemd-sysv: shutting down not complete
has caused the Debian Bug report #768081,
regarding systemd-sysv: shutting down not complete
to be marked as done.
This means t
Package: systemd-sysv
Version: 215-5+b1
Severity: normal
halt does not shut down the machine with power-off.
Simply typing "halt" should power off Debian as it has previously been
with Wheezy.
please fix this bug
thanks
___
Pkg-systemd-maintainers
Your message dated Tue, 04 Nov 2014 18:33:07 +0100
with message-id <54590dd3.4040...@debian.org>
and subject line Re: Bug#768025: systemd-logind: default configuration breaks
any existing ACPI button handling
has caused the Debian Bug report #768025,
regarding systemd-logind: default configuration
Your message dated Tue, 4 Nov 2014 16:11:58 +0100
with message-id
and subject line Re: Bug#767894: More permission issues
has caused the Debian Bug report #767894,
regarding More permission issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Processing control commands:
> tags -1 fixed-upstream
Bug #767951 [systemd-cron] systemd-cron: "crontab -r user" will remove root
crontab
Added tag(s) fixed-upstream.
--
767951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
control: tags -1 fixed-upstream
fixed
https://github.com/systemd-cron/systemd-cron/commit/805f5a2656b0a1e328f4a6dbbcbf2eeccfc6cc46
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cg
Control: reassign -1 initramfs-tools
Am 04.11.2014 um 13:37 schrieb Arnaud Installe:
> On Tue, 04 Nov 2014 13:20:05 +0100
> Michael Biebl wrote:
>
>> Am 04.11.2014 um 11:46 schrieb Arnaud Installe:
>> cue shell is booted off an initrd image which doesn't have
>>> enough of systemd / journalctl a
Processing control commands:
> reassign -1 initramfs-tools
Bug #767589 [systemd] systemd: cryptdisks other than root/swap fail cryptsetup
Bug reassigned from package 'systemd' to 'initramfs-tools'.
No longer marked as found in versions systemd/215-5.
Ignoring request to alter fixed versions of bug
Am 04.11.2014 um 11:46 schrieb Arnaud Installe:
cue shell is booted off an initrd image which doesn't have
> enough of systemd / journalctl available (libraries missing etc.). So I
> ran the commands you mention after I manually ran cryptsetup for
> boulez-_home_, boulez-_usr_, and boulez-_var_, ex
Processing commands for cont...@bugs.debian.org:
> reassign 768026 systemd-shim 8-4
Bug #768026 [systemd] systemd-logind: logging noise in the kernel log
Bug reassigned from package 'systemd' to 'systemd-shim'.
No longer marked as found in versions systemd/215-5.
Ignoring request to alter fixed ve
Processing control commands:
> forcemerge 756247 -1
Bug #756247 [systemd-shim] Failed to start unit user@1000.service: Unknown
unit: user@1000.service
Bug #760070 [systemd-shim] logind : error at login and logout
Unable to merge bugs because:
package of #768026 is 'systemd' not 'systemd-shim'
Fai
Control: forcemerge 756247 -1
Bjørn Mork [2014-11-04 10:56 +0100]:
> systemd-logind[2790]: Failed to start user service: Unknown unit:
> user@106.service
> systemd-logind[2790]: New session c1 of user lightdm.
This is unimplemented stuff from systemd-shim, duplicating to existing
bug.
Martin
--
Package: systemd
Version: 215-5+b1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind puts what seems like debugging messages in the kernel
log. Examples:
systemd-logind[2790]: Failed to start user service: Unknown unit:
user@106.service
systemd-logind[2790]: New se
Package: systemd
Version: 215-5+b1
Severity: critical
Justification: breaks unrelated software
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind breaks acpid by default.
Merely installing systemd with default configuration causes it to start
handling the PowerKey, LidSwitch, Hibernate
Package: systemd
Version: 215-5+b1
Severity: normal
File: systemd-hostnamed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I get this noise in the kernel log when systemd-hostnamed starts (which
it seems to do for whatever default reason):
systemd-hostnamed[2574]: Warning: nss-myhostname is not
> Generally, user crontabs are only visible by the owner.
Ok, from now on [1], systemd-cron do it's best to keep those secret:
-) the crontab line is not anymore in the job description
-) "chmod o-r /run/systemd/generator/cron---#.(timer|service)"
"systemctl status" is fixed ; and a ordinary user
23 matches
Mail list logo
