Am Mittwoch, den 12.11.2014, 02:10 +0100 schrieb Michael Biebl:
> Am 11.11.2014 um 23:49 schrieb Paul Menzel:
> > Am Dienstag, den 11.11.2014, 13:34 +0100 schrieb Michael Biebl:
> >> Sounds like dbus is not installed. Paul, can you confirm that?
> >
> > It is installed. The failure happened with
Le 10/11/2014 07:04, Martin Pitt a écrit :
Hey Martin,
The downside is that we loose the return code, indeed (we could
concatenate it if needed).
Yes, I think it should save the return code if it's != 0 and return
that. I. e. the script will fail if processing any unit fails.
done, deb-system
On Nov 11, Michael Biebl wrote:
> Please boot with systemd.log_level=debug on the kernel command line, the
> attach the output of "journalctl -alb"
I guess these are the relevant lines:
Found ordering cycle on graphical.target/start
Found dependency on multi-user.target/start
Found dependen
Am 12.11.2014 um 09:45 schrieb Paul Menzel:
> Am Mittwoch, den 12.11.2014, 02:10 +0100 schrieb Michael Biebl:
>> incident, I'd suggest we close the bug report and re-open once you run
>> into it again and can reproduce it.
>>
>> Are you ok with that?
>
> Not yet. ;-) Does the following help?
Not
Am 12.11.2014 um 14:29 schrieb Uwe Storbeck:
> On Nov 11, Michael Biebl wrote:
>> Please boot with systemd.log_level=debug on the kernel command line, the
>> attach the output of "journalctl -alb"
>
> I guess these are the relevant lines:
>
> Found ordering cycle on graphical.target/start
> F
On 12/11/14 13:33, Michael Biebl wrote:
> Not quite, all it shows is that the problem is most likely in dbus and
> not systemd itself.
Based on the log you quoted, I'm not sure I agree. The problem is
certainly in the interaction between dbus and systemd, but it doesn't
look as though systemd is d
Version: 215-5+b1
I too am getting slammed by this message, one
every ~51 seconds.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maint
Am 12.11.2014 um 14:44 schrieb Michael Biebl:
> Am 12.11.2014 um 14:29 schrieb Uwe Storbeck:
>> On Nov 11, Michael Biebl wrote:
>>> Please boot with systemd.log_level=debug on the kernel command line, the
>>> attach the output of "journalctl -alb"
>>
>> I guess these are the relevant lines:
>>
>>
Hello Tim Wootton, release-team, et.al.!
Thanks for your bug report.
On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote:
> Package: bsdutils
> Version: 1:2.25.2-2
> Severity: serious
> Justification: Policy 2.5
>
> Dear Maintainer,
>
> libsystemd0 dependancy violates constraint at the
Am 12.11.2014 um 14:44 schrieb Michael Biebl:
> Am 12.11.2014 um 14:29 schrieb Uwe Storbeck:
>> On Nov 11, Michael Biebl wrote:
>>> Please boot with systemd.log_level=debug on the kernel command line, the
>>> attach the output of "journalctl -alb"
>>
>> I guess these are the relevant lines:
>>
>>
Am 12.11.2014 um 15:04 schrieb Andreas Henriksson:
> Hello Tim Wootton, release-team, et.al.!
>
> Thanks for your bug report.
>
> On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote:
>> Package: bsdutils
>> Version: 1:2.25.2-2
>> Severity: serious
>> Justification: Policy 2.5
>>
>> Dear M
I don't change adapters/adapter locations often enough to have
a need for the new network name schemes and have long ago put in
place a custom '/etc/udev/rules.d/70-persistent-net.rules', template
generated by '/lib/udev/rules.d/75-persistent-net-generator.rules'.
The wired adapter is 'eth0
On Wed, Nov 12, 2014 at 03:04:56PM +0100, Andreas Henriksson wrote:
> Hello Tim Wootton, release-team, et.al.!
>
> Thanks for your bug report.
>
> On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote:
> > Package: bsdutils
> > Version: 1:2.25.2-2
> > Severity: serious
> > Justification: Po
Am 12.11.2014 um 15:30 schrieb Dominique Brazziel:
> I don't change adapters/adapter locations often enough to have
> a need for the new network name schemes and have long ago put in
> place a custom '/etc/udev/rules.d/70-persistent-net.rules', template
> generated by '/lib/udev/rules.d/75-pe
Am 12.11.2014 um 15:35 schrieb Bill Allombert:
> It is well settled that priority changes are done throught the distribution
> override file and not in the package control file and thus, an error of
> priority is not a RC bug in the package.
And that. Adjusting library package priorities is useles
On 12/11/14 14:29, Michael Biebl wrote:
Am 12.11.2014 um 15:04 schrieb Andreas Henriksson:
Hello Tim Wootton, release-team, et.al.!
Thanks for your bug report.
On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote:
Package: bsdutils
Version: 1:2.25.2-2
Severity: serious
Justification: P
Whatever happened to cause the NamePolicy messages
to appear every n seconds. As noted previously by Martin Krafft,
"I have not opted-in, but I also see the message all the time. Maybe
opt-in isn't working as planned?".
Let's see what I would have to do to make these messages
go
Am 12.11.2014 um 16:30 schrieb Dominique Brazziel:
> Whatever happened to cause the NamePolicy messages
> to appear every n seconds.
You should only get the message about the NamePolicy once during boot.
That it's repeated over and over again is caused by an incomplete debian
patch for the h
Now I get it. Thank you.
___
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 Wed, Nov 12, 2014 at 02:44:53PM +0100, Michael Biebl wrote:
> Yeah, it shows that watchdog.service is involved in dependency cycle and
> systemd therefore removes it from the transaction.
Why doesn't it show the same reaction on my system then? Uwe's system doesn't
seem to have any changes out
> To be sure: what are you trying to do here and why? Maybe we can find a
> better solution
Watchdog should be started as late as possible during the boot process and
stopped as early as possible during shutdown.
> Btw, is "echo /sbin/modprobe $watchdog_module" really intended? that
> will just
On Wed, Nov 12, 2014 at 03:17:22PM +0100, Michael Biebl wrote:
> That's the part that causes the dep cycle afaics.
>
> By being hooked into multi-user.target, watchdog.service will have an
> explicit
> Before=multi-user.target
> dependency.
>
> multi-user.target on the other hand is an alias of r
I looked at this a little more. I found someone saying setting
plymouth.conf to theme=detail would help, so I tried that. I also
apt-get update'd and apt-get dist-upgrade'd.
Basically, there are two issues. The prompts to enter passwords for
luks encrypted volumes are mixed in with boot messages.
Package: systemd
Version: 215-5+b1
File: /usr/share/man/man1/systemd.1.gz
The user sees:
OPTIONS
The following options are understood:
--test
Determine startup sequence, dump it and exit. This is an option
useful for debugging only.
The user tries:
$ systemd
Tim Wootton writes:
> or just build without the dependency in the 1st place like it used to
> be. After all it's not like it adds anything that's essential.
No, including the dependency is the right approach and is consistent with
how Debian has always handled issues like this. We always enable
More information:
* reboot -f and poweroff -f work fine.
* if I start a debug-shell on a serial port, at some point the shell
seems to freeze as well.
* if I boot with sysvinit (installing sysvinit-core instead of
systemd-sysv), things work fine:
- The system reboots even if an X11 console i
Hi,
Tim Wootton:
> or just build without the dependency in the 1st place like it used to be.
> After all it's not like it adds anything that's essential.
>
Most dependencies don't add anything that's "essential" in the strict
sense. The vast majority of uses of computers aren't essential either,
27 matches
Mail list logo
