unarchive #869995
found #869995 232-25+deb9u1
found #869995 232-25+deb9u2
tags #869995 patch stretch
thanks
Hi,
I have missed that this bug was actually closed for good. I can confirm
that the issue is fixed in sid and buster, but is is still a crippling
bug in stretch.
I can confirm that the
found #869995 232-25+deb9u1
found #869995 232-25+deb9u2
tags #869995 patch stretch
thanks
Hi,
I have missed that this bug was actually closed for good. I can confirm
that the issue is fixed in sid and buster, but is is still a crippling
bug in stretch.
I can confirm that the two attached patche
kd as well.
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make
hat the docs said to avoid
defaults from being used.
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon
On Fri, Jun 05, 2015 at 09:45:28PM +0200, Michael Biebl wrote:
> Am 04.06.2015 um 16:02 schrieb Marc Haber:
> > The documentation in resolved.conf(5) suggests that the compiled-in
> > list does only apply if there is no other definition of DNS-Servers.
> > This is not the ca
ed.conf with a not commented
out "DNS=" line?
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | F
Package: dh-systemd
Version: 1.23
Severity: wishlist
File: /usr/bin/dh_systemd_enable
Hi,
dh_systemd_enable behaves differently for service, socket, and tmpfile
units where it installs the actual unit file additionally to
generating postinst code.
Please consider doing this for other unit types
e to use dh_systemd_* directly, but that's
> mostly useless pain.
Can I use it more directly than the way I'm already doing it?
Now, I need to get over the incredible frustration that one cannot
test systemd units in a simple chroot as it was possible with init
scripts. Easier, yeah, right
On Fri, Aug 21, 2015 at 04:07:56PM +0200, Michael Biebl wrote:
> Am 21.08.2015 um 15:59 schrieb Marc Haber:
> > I have systemd-networkd segfault when it works as a DHCP client for
> > IPv4 on a banana pi. Googling has led me to
> > https://bugs.archlinux.org/task/4
severity #815321 serious
thanks
On Sun, Feb 21, 2016 at 12:04:25AM +0100, Marco d'Itri wrote:
> On Feb 20, Marc Haber wrote:
> > DNS=fec0:0:0:::1
> > DNS=fec0:0:0:::2
> I think that the problem is that you did not configure any IPv4 name
> servers. Since it is
Package: systemd
Version: 229-1
Severity: normal
I have a host that is hosting a number of KVM virtual machines. It has
eth0 to the Internet. The virtual machines connect to br0, and the
host is routing between br0 and eth0. Both host and VMs are fully IPv6
enabled. Network configuration is done w
Package: systemd
Version: 229-1
Severity: important
Hi,
systemd 229 has taken over the code to send and accept router
solicitations in IPv6. Unfortunately, it does only send a single RS
immediately after the link comes up, and does not retry if no RA comes
in.
Unfortunately, bigger switches do n
Hi Martin,
On Sun, Feb 28, 2016 at 10:20:22PM +0100, Martin Pitt wrote:
> Marc Haber [2016-02-24 15:01 +0100]:
> > systemd 229 seems to ignore unsolicited router advertisements. This
> > breaks, for example, prefix changes. And it prevents the self-healing
> > character
bought new hardware for virtualization and will use
building the new system as test lab, so your request comes just at the
right time since I can now experiment without breaking productive
systems.
Greetings
Marc
--
-----
On Wed, Jul 06, 2016 at 09:29:35AM +0200, Martin Pitt wrote:
> Marc Haber [2016-07-06 9:03 +0200]:
> > > Do you have some instructions how this can be reproduced? It sounds
> > > like it should be possible to test this using a veth pair, possibly a
> > > dnsmasq on
d a parallel tcpdump like above
> and attach the logs?
I can easily try that without too much pain, yes. I hope I'll get
around to doing so tonight.
Greetings
Marc
--
-----
Marc Haber | "I don't trust
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American
On Wed, Jul 06, 2016 at 11:55:19AM +0200, Martin Pitt wrote:
> Marc Haber [2016-07-06 11:52 +0200]:
> > On Wed, Jul 06, 2016 at 11:49:17AM +0200, Martin Pitt wrote:
> > > This looks the same for 229, 230/upstream and 230/sid (with the
> > > reverted patch). Thus I c
Package: systemd
Version: 230-5pitti1
Severity: minor
Tags: ipv6
Hi,
I am filing this as severity minor because this bug is in a version
that is not officially in Debian. I am filing it nevertheless because
systemd with this IPv6 user space code active should not be in Debian.
If this were an off
d64
with 230-5pitti1.
I have found another showstopper IPv6 bug in 230-5pitti1 and have duly
reported it.
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, G
On Sat, Jul 16, 2016 at 10:55:29AM +0200, Martin Pitt wrote:
> Marc Haber [2016-07-15 21:00 +0200]:
> > I am filing this as severity minor because this bug is in a version
> > that is not officially in Debian.
>
> Bumping as I dropped the reverted patch in git, i. e. the ne
s
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt |
Hi Martin,
On Fri, Jul 15, 2016 at 09:04:59PM +0200, Marc Haber wrote:
> On Wed, Jul 06, 2016 at 08:57:43AM +0200, Martin Pitt wrote:
> > while we reverted the change in 229, we don't want to carry the
> > reversion forever. Also, some problems were fixed already in 230, like
Package: systemd
Version: 230-5pitti1
Severity: important
Dear Maintainer,
since a few months, systemd upstream tries to implement parts of IPv6
inside systemd/networkd while we have perfectly working code inside
the Linux kernel. Unfortunately, the systemd code is wrong in so many
places that it
On Fri, Jul 29, 2016 at 02:42:55PM +0200, Michael Biebl wrote:
> Am 29.07.2016 um 14:08 schrieb Marc Haber:
> > systemd 231-1 on Banana Pi fails with a bunch of "Failed at step
> > SECCOMP spawning systemd-food: Invalid Argument". This at least
> > applies to l
the "real" system because the
system can clean up the queue before the next bunch of items comes in,
and in testing, this might help to make the queue fill up faster.
Greetings
Marc
--
-----
Marc Haber | &qu
Package: systemd
Version: 232-3
Severity: important
Hi,
the systemd IPv6 code ignores the Route Preference that is in an
incoming router advertisement.
Here is what tshark -V says about the packet:
Frame 53: 294 bytes on wire (2352 bits), 294 bytes captured (2352 bits) on
interface 0
Inter
ally set up by systemd-networkd?
You're so right. I apologize.
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."W
On Thu, Dec 22, 2016 at 11:07:18AM +0100, Michael Biebl wrote:
> Is that still reproducible with v232?
No. Please feel free to mark this as closed in any earlier version.
Greetings
Marc
--
-----
Marc Haber |
Package: systemd-cron
Version: 1.5.4-2
Severity: wishlist
Dear Maintainer,
thanks for providing this compatibility layer to help transition from
a cron daemon to systemd timers. Using run-parts in the .service units
prevents all items of a daily|weekly|monthly cron job from starting at
once.
How
and don't change to many things
at once. It's not _that_ hard.
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona R
On Fri, Jan 06, 2017 at 03:03:44PM +0100, Julian Andres Klode wrote:
> On Fri, Jan 06, 2017 at 02:29:19PM +0100, Marc Haber wrote:
> > However, daily|weekly|monthly are started together at midnight, while
> > the classic crond/anacron setup starts them in a staggered way which
&g
Package: systemd
Version: 232-21
Severity: wishlist
Hi,
in the pre-systemd era, a system would continue booting even after an
error. This frequently resulted in a crippled, but running system
which allowed a (sometimes crippled) remote login which allowed fixing
things from remote without having
Hi Felipe,
thanks for your fast answer. I really appreciate your consideration.
On Mon, Mar 27, 2017 at 11:47:40AM -0300, Felipe Sateler wrote:
> On Mon, Mar 27, 2017 at 5:51 AM, Marc Haber
> wrote:
> > (1) allow regular login in emergency mode
> > Instead of using sulogi
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
ply
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
_
tion trying to be helpful. If you
disagree, please complain and remove the forwarded information.
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things.&
DNS).
I think this warrants an "important" priority, if not a release critical
one. Please consider that.
Greetings
Marc
On Sat, Aug 19, 2017 at 11:39:06AM +0200, Marc Haber wrote:
> From: Marc Haber
> Subject: Bug#869995: interface stays in "routable (configuring)"
xRtrAdvInterval 1200;
prefix 2001:db8::/64 {
DeprecatePrefix on;
AdvPreferredLifetime 0;
};
};
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany
This bug severely affects systemd-networkd's usability in Debian stable
and has been without maintainer attention for a month.
Is there any way to help?
Greetings
Marc
--
-
Marc Haber | "I don't
tags #869995 patch
thanks
I have worked in the last days with Susant Sahani to isolate this
issue and can confirm that his patches:
https://github.com/systemd/systemd/pull/6907/commits/e6800d3cfb48542634c25c24a6aae7587d97eb4f
https://github.com/systemd/systemd/pull/6907/commits/c46530942bc0837379e
On Wed, Sep 27, 2017 at 03:47:34PM +0200, Michael Biebl wrote:
> Am 25.09.2017 um 08:50 schrieb Marc Haber:
> > tags #869995 patch
> > thanks
> >
> > I have worked in the last days with Susant Sahani to isolate this
> > issue and can confirm that his patche
would be great if you can also test it with v232, to
> verify that it fixes the issue there as well.
Can I download your package for stretch or should I build from git
myself?
Greetings
Marc
--
-----
Marc Haber
On Wed, Sep 27, 2017 at 05:11:06PM +0200, Michael Biebl wrote:
> Am 27.09.2017 um 17:06 schrieb Marc Haber:
> > On Wed, Sep 27, 2017 at 04:22:09PM +0200, Michael Biebl wrote:
> >> Ok, I've usertagged the bug for now so it shows up at [1] as a possible
> >> candid
tags 854400 - status-open
> usertags 854400 + status-closed
>
> thanks
>
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder |
Hi,
stumbling upon this again. The system behaves now, so the issue as at
least fixed in systemd 234.
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leime
tched software.
Patch attached
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch
Package: systemd
Version: 235-2.0~zgSID+1
Severity: normal
Tags: upstream patch
Forwarded: https://github.com/systemd/systemd/issues/6961
This is upstream issue 6961, where a dummy interface configured into a
bridge gets stuck in "configuring" state, with the usual consequences of
the network neve
On Tue, Oct 17, 2017 at 12:11:07AM +0200, Michael Biebl wrote:
> Control:
> Am 16.10.2017 um 21:57 schrieb Marc Haber:
> > Package: systemd
> > Version: 235-2.0~zgSID+1
>
> Seems the bts is not happy with that version.
> For proper version tracking, which version is af
Package: systemd
Version: 235-2
Severity: normal
Hi,
/usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged
systems. The file should be in /lib/modprobe.d, where already other
files are placed. Moving the file gets it honored.
Greeetings
Marc
-- Package-specific info:
-- Sys
/usr/lib/modprobe.d is a valid place,
modprobe.d(5) should be adapted to document reality.
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose
found #869995 235-2
found #869995 235-3
On Mon, Oct 16, 2017 at 06:58:54PM +0200, Marc Haber wrote:
> I regret to inform you that the fix given in this bug report didn't make
> it into upstream 235. The issue reappears after the update to systemd
> 235, the patches do still app
found #878811 235-3
thanks
On Tue, Oct 17, 2017 at 07:36:43AM +0200, Marc Haber wrote:
> I apologize, I filed this from a system with the fixed version
> installed. Both 232 from stretch and 235 from sid (and 234 which was the
> current version when the patch was developed) are affect
I would like to suggest closing this issue. I have never seen it again.
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things.&
On Fri, Sep 29, 2017 at 04:06:49PM +0200, Marc Haber wrote:
> This bug has not been fixed upstream, upstream doesn't feel like fixing
> it and closed Raphaëls PR without actually pulling.
The issue still happens in current unstable with a 4.15 kernel.
Package: systemd
Version: 215-4
Severity: normal
Hi,
Given a system with a non-essential crypt disk, which should be
unlocked on boot and mounted via /etc/fstab.
I then enter three times a wrong key and get dumped to emergency mode.
In emergency mode, the network seems fine.
I then exit emergen
sid.
I did not deliberate change to the network setup to avoid breaking
things.
Greetings
Marc
--
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things.&q
Package: systemd
Severity: normal
Hi,
I have a current sid system which has been updated to current sid from
May's sid in a big update run and has gotten systemd in the process.
Unfortunately, it dies when X is started.
To debug this issue, I'd like to have a possibility to stop X from
being st
58 matches
Mail list logo
