angelog missed
the required "Closes: #nn".
Thanks!
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
100% sure). In my case it happens after
a regular boot though, not tried in emergency mode.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listin
ails stuff to systemd and failed, so now you make me hope that
I missed something obvious :)
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
lib/dracut/modules.d/98dracut-systemd/dracut-shutdown.service:After=local-fs.target
boot.mount boot.automount
I guess that next step would be that I try reproducing this problem
with initramfs-tools => tagging moreinfo, so it's clear that the ball
is now in my court. Thank
Michael Biebl wrote (29 Aug 2015 15:50:40 GMT) :
> Could you attach the output of systemd-analyze dump
Yes and no => send privately.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.or
is it a bug?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
of other ways for an
attacker to do what they want. Thanks in advance!
To end with, I'm wondering whether this email is really
about timesyncd.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.de
duced in the tor package a few
weeks ago.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Hi,
Josh Triplett wrote (15 Jun 2015 15:56:33 GMT) :
> [...] I do think this functionality from wheezy should be restored.
I'm aware this is not a poll, so just for the record:
Tails Installer will soon be uploaded to Debian, and then to
jessie-backports; it uses udisks whenever possible, but so
Hi,
Martin Pitt wrote (03 May 2015 08:39:55 GMT) :
> intrigeri [2015-05-02 12:36 +0200]:
>> Do you have any target date for this upload?
> I quickly discussed that with Michael the other day. So far the plan
> is to keep 215 in unstable/master until Debian 8.1, and upload 219
&g
d wouldn't mind
uploading it to sid whenever you need it there. The only concern
I have is about the removal of the $remote_fs dependency, that I'm not
entirely convinced with, as expressed on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782700#52
C
Hi systemd and lightdm maintainer,
please have a look at #782456 -- it might be local misconfiguration
(in which case, asking Ralf for the debugging info you need would be
very nice of you), or a bug in the new DM / systemd integration.
Cheers,
--
intrigeri
> Control: retitle -1 base: HP EliteBook 840 G1 laptop fails to halt/poweroff
> after 15/12/2014 upgrade
FWIW, the very same laptop powers off just fine here with current sid.
intel-microcode 3.20150121.1 is installed, and my PID 1 is systemd.
___
Pkg-
(#771667).
The apparmor package in experimental now has moved libapparmor to
/lib, thanks to Martin's patch, so I believe that AppArmor support can
now be re-enabled in systemd/experimental.
Thanks in advance!
Cheers,
--
intrigeri
___
Pkg-sy
tx breaks
> mouse and keyboard.
> Does apparmor mandate new kernel configuration? New user space setup?
Can you reproduce this with AppArmor disabled?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.al
Control: tag -1 + moreinfo
Hi Stephen,
Stephen Hemminger wrote (30 Nov 2014 17:09:27 GMT) :
> When I attempt to shutoff my desktop system either via Gnome, poweroff,
> shutdown or by directly invoking systemctl, the normal shutdown starts
> but then the script invokes kexec on the new kernel.
Do
way it works. Maybe it's worth
pointing systemd upstream at that piece of documentation.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
nstable's systemd, and confirm that it works and fixes the issue
for you?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listin
stemd
control group hierarchy" as enabled?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Andrei POPESCU wrote (18 Nov 2014 21:40:00 GMT) :
> I can try to help.
Yay :)
> Is the output of 'journalctl -alb' from the debug console enough for
> a first assessment?
That's a good start, but the output of the systemd bugscript gives
more useful info
t; status 1
It works fine for me on current sid:
intrige+ 11871 0.0 0.0 5804 660 ?Ss 11:03 0:00 /bin/sleep 3600
Can you still reproduce this bug?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-syst
d be
helpful: no need to be a systemd expert to do the first pass of making
sure that all basic debugging info are provided by the submitter!]
Cheers!
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
h
Jessie, then I guess we'll
want to document this workaround in NEWS.Debian, and make sure the
release notes point there.
IMO, let's not spend time on #2 right now, and instead focus on #1.
Cheers,
--
intrigeri
___
Pkg-systemd-ma
Hi dAgeCKo,
dAgeCKo wrote (17 Nov 2014 20:59:15 GMT) :
>>> journalctl -al
[...]
> Here are joined why you requested.
> I hope that the provided information could help you.
Thanks!
However, the journalctl output seems to be empty (or is it my MUA?) =>
may you please double-check that you were run
rch?
>>
>>
> Not yet, unfortunately, for lack of time...
Any progress on that one?
Can you reproduce it on current Debian testing/sid?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.ali
Hi Giuseppe,
Michael Biebl wrote (21 Sep 2014 18:43:54 GMT) :
> Are you sure this was actually systemd which unmasked the services?
> Can you reproduce the problem (e.g. by re-installing systemd or
> downgrading and upgrading systemd again)?
Ping?
Cheers,
--
e also attach your network configuration (e.g.
> /etc/network/interface, if you use ifupdown) and your /etc/fstab.
Ping?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debia
ches
> between systemd and sysvinit (and vice versa) and they work fine for
> 208-8 (and hopefully again for v215 once cgmanager is fixed).
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
t via the kernel command line,
> the problem is gone?
Ping? Can you still reproduce this issue? If yes, may you please
answer Michael's questions? Thanks in advance.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
you
> into emergency shell (timeout3.png).
> Does that address your issues?
Ping?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
interesting, I think)
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
er errors whenever
a needed kernel feature is missing. Retitling accordingly.
Next step for anyone interested is to check if things have improved
upstream in this area since v215, and if not, to check if there's
a ticket in their bug tracker.
Cheers,
--
intrigeri
to become a daemon, when the process
is started from the command line or from a startup script such as an
init script or a SystemStarter script, involves:
* Dissociating from the controlling tty
(I realize that pointing to Wikipedia feels weird here.)
Cheers,
--
intrigeri
__
nclined to tag this bug wontfix, or to close it. I'll let the
maintainers make the decision, though.
(The only reason why it actually completes the boot, I guess, is
because the filesystems hosted on the missing encrypted devices are
not listed in fstab.)
Cheers,
--
intrigeri
___
Control: tag -1 + upstream
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=52630
Control: retitle -1 systemd-cryptsetup handles keyfile differently from
cryptsetup on plain mode
Hi again,
intrigeri wrote (16 Nov 2014 18:32:58 GMT) :
> Could you please try to pinpoint wh
please report it upstream?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Control: tag -1 + moreinfo
Hi,
can any of you reproduce this on current testing/sid (that is, with
systemd v215)?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http
at line.
So, apparently this bug report is about two different problems:
1. Joseph's one is about a harmless warning message
2. Wayne's one was caused by a local misconfiguration
=> so I think we should close it.
Cheers,
--
intrigeri
__
notes bug, whose expected outcome would be
a paragraph in the release notes that points to the aforementioned
documentation
?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://
e commands?
# systemctl status display-manager.service
# systemctl status lightdm.service
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
t/init
> to the kernel command line makes the bug disappear.
Could you please try to pinpoint which exact option, among the many
ones you're using, is badly handled?
E.g. start with a plain dm-crypt device, then use an external key
file, then add ci
ot on others.
> My first guess was the graphics driver, but it happens with both intel
> (i915) and nvidia (nouveau) cards.
> Which card and module are you using?
Do you have plymouth installed? i.e. what's the output of
dpkg -l ply
e
?
(I'll soon be out of clues, so if one of the maintainers wants to take
it from here, don't hesitate.)
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian
Hi,
John Goerzen wrote (25 Oct 2014 22:48:43 GMT) :
> No journal files were found.
Ah, you've got the journal disabled. Then please grep logind in
whatever place your system logs live?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mail
d (and
then, why). May you please look in the journal:
# journalctl -u systemd-logind.service
... to try and find why this happens?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.or
on.
> I will try to take a look later, once I can find a VM to debug it.
Thanks a lot for caring about this :)
Just to be clear: is any of this a blocker in your opinion to enable
AppArmor support for Jessie (that is, in the next ~14 days), e.g.
with the patch I've proposed?
Chee
Hi,
intrigeri wrote (24 Sep 2014 05:33:37 GMT) :
> So, I don't think that the problem I'm seeing here is a blocker for
> enabling AppArmor support in systemd. The attached patch implements
> this. Once something like this is applied, I'll clone this bug report
> to t
Package: systemd
Version: 215-5
Severity: normal
Hi,
ProtectSystem was adjusted (#759689) to be better suitable for Debian,
but the corresponding manpage wasn't updated accordingly.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing lis
Control: tag -1 + patch
Hi,
intrigeri wrote (23 Sep 2014 17:01:21 GMT) :
> Michael Biebl wrote (23 Sep 2014 11:59:22 GMT) :
>>> a) I don't see any dependency automatically added on libapparmor1, and
>>>I've no idea which binary package exactly should hav
I didn't: my understanding of the upstream build system is that
AppArmor support is opt-out (if libapparmor-dev can be found, it's
enabled by default). But I'll trust you that explicitly enabling it
might affect the resulting runtime depende
Hi,
intrigeri wrote (09 Sep 2014 00:14:30 GMT) :
> So: yes, please. I've been waiting for it eagerly, and will submit
> patches to the Tor upstream unit file as soon as Debian's systemd
> supports this option.
I really want this to land in time for Jessie, so I've g
and will submit
patches to the Tor upstream unit file as soon as Debian's systemd
supports this option.
> CCing Kees here, since he is the maintainer of apparmor.
... which is in the process of moving to team-maintenance (decided
in-person at DebConf with Kees), so Cc'ing the t
orProfile= in its unit file as soon as systemd v210+ is
available in Debian, to replicate how we're doing it in the
initscript. I'll double-check once we're at this point, though.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
ing a bit misleading, then.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
there a bug somewhere?
Cheers,
--
intrigeri
[Unit]
Description = Anonymizing overlay network for TCP
After = syslog.target network.target nss-lookup.target
[Service]
Type = simple
ExecStartPre = /usr/bin/tor --defaults-torrc
/usr/share/tor/tor-service-defaults-torrc --verify-config
# A torrc that
[2] https://wiki.archlinux.org/index.php/kexec
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
ng the
output of `systemctl list-units --failed', run after switching back to
multi-user runlevel, might help.
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debia
lem.
Any news on this front?
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
broken?
Thanks in advance!
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
e when you switch back to the
>> multi-user runlevel? Do yo have any error messages in the log files?
... so I'm leaving the moreinfo tag set for now.
Also, it might be useful to try and reproduce this problem on
current sid.
Cheers,
--
intrigeri
___
s a lot for maintaining systemd in Debian!
Cheers,
--
intrigeri
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
vanced options for Debian GNU/Linux
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
___
Pkg-systemd-maintainers mailing list
Pkg-s
62 matches
Mail list logo
