On Wed, 2015-04-01 at 05:59 +0200, Janis Hamme wrote:
> On Tue, 31 Mar 2015 03:14:53 +0100 Ben Hutchings
> wrote:
> > By the way, Lennart Poettering told me that other distributions have
> > done that, though I haven't checked whether it is done with a
> > configuration file or a patch to the code
On Wed, 8 Apr 2015, Michael Biebl wrote:
> Can you boot with systemd.log_level=debug on the kernel command line and
> attach the output of journalctl -alb.
Attached.
journalctl-alb.txt.gz
Description: application/gzip
___
Pkg-systemd-maintainers mailin
Processing commands for cont...@bugs.debian.org:
> reassign 782134 systemd-shim
Bug #782134 [systemd] systemctl TAB-completion for unit names does not work
when not root
Bug reassigned from package 'systemd' to 'systemd-shim'.
No longer marked as found in versions systemd/215-14.
Ignoring request
On Wed, 2015-04-08 at 10:45 +0200, Michael Biebl wrote:
> Just like resolved needs explicit opt in by the admin (the service is
> disabled by default).
I don't think that this actually changes anything.
Everything is in a way explicitly opt in, when you install Debian.
The point is can some behavi
On Wed, 8 Apr 2015, Michael Biebl wrote:
> Am 08.04.2015 um 13:33 schrieb Santiago Vila:
> > Package: systemd
> > Version: 215-14
> >
> > After a recent upgrade in a lab where I use NFS, I see messages like this:
> >
> > ifup[370]: mount.nfs: /home/nfs is busy or already mounted
> >
> > but thi
Am 08.04.2015 um 13:51 schrieb Santiago Vila:
> On a computer which is a little bit faster than the others I see this
> instead:
>
> ifup[429]: /sbin/ifup: interface eth0 already configured
>
> I can even reproduce it after *every* reboot:
>
> * One computer (faster than the others) says "eth0 a
Processing commands for cont...@bugs.debian.org:
> tags 781602 + pending
Bug #781602 [systemd] systemd: Invalid DBus call causes systemd to stop
responding to DBus alltogether
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
781602: http://bu
On Wed, Apr 08, 2015 at 01:27:23PM +0200, Michael Biebl wrote:
> Users dist-upgrading from wheezy won't run into this issue. Same for
> users, which kept systemd-shim installed in sid and upgraded to the
> newer version.
>
> I'm afraid there isn't a lot we can do about that (in systemd) and I'm
>
On a computer which is a little bit faster than the others I see this
instead:
ifup[429]: /sbin/ifup: interface eth0 already configured
I can even reproduce it after *every* reboot:
* One computer (faster than the others) says "eth0 already configured".
* The others (older, slower) say "/home/nf
Am 08.04.2015 um 13:33 schrieb Santiago Vila:
> Package: systemd
> Version: 215-14
>
> After a recent upgrade in a lab where I use NFS, I see messages like this:
>
> ifup[370]: mount.nfs: /home/nfs is busy or already mounted
>
> but this didn't happen before. I suspect of recent changes in syste
Processing control commands:
> severity -1 important
Bug #781602 [systemd] systemd: Invalid DBus call causes systemd to stop
responding to DBus alltogether
Severity set to 'important' from 'normal'
--
781602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781602
Debian Bug Tracking System
Con
Control: severity -1 important
Christian Seiler [2015-03-31 17:46 +0200]:
> So it appears this is fixed upstream already. Unfortunately, I don't
> have time to investigate right now (maybe next week).
git bisect says it was fixed in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=0ca454
Package: systemd
Version: 215-14
After a recent upgrade in a lab where I use NFS, I see messages like this:
ifup[370]: mount.nfs: /home/nfs is busy or already mounted
but this didn't happen before. I suspect of recent changes in systemd.
It's not grave as it seems harmless, but if it's a regres
Am 08.04.2015 um 12:45 schrieb Stefano Zacchiroli:
> On Wed, Apr 08, 2015 at 12:38:29PM +0200, Michael Biebl wrote:
>> Do you have systemd-shim installed or had it installed in the past
>> without purging it?
>> I remember an old bug report where the dbus policy shipped by
>> systemd-shim broke sys
On Wed, Apr 08, 2015 at 12:38:29PM +0200, Michael Biebl wrote:
> Do you have systemd-shim installed or had it installed in the past
> without purging it?
> I remember an old bug report where the dbus policy shipped by
> systemd-shim broke systemd.
That's it!
I don't currently have systemd-shim, b
The root of the problem is likely this:
zack@timira:~$ systemctl list-units
Failed to list units: Access denied
which apparently works for others (on #debian-devel) but not me.
I've tried the above both while within a GNOME session and on a tty:
same result.
Cheers.
--
Stefano Zacchiroli
Hi Zack!
Am 08.04.2015 um 12:26 schrieb Stefano Zacchiroli:
> When as non root, I do this:
>
> $ systemctl start l
>
> I get this error:
>
> Failed to list units: Access denied
>
> and TAB completion fail to complete. ("l" is just a sample prefix, TAB
> completion for unit names doesn't w
Package: systemd
Version: 215-14
Severity: minor
When as non root, I do this:
$ systemctl start l
I get this error:
Failed to list units: Access denied
and TAB completion fail to complete. ("l" is just a sample prefix, TAB
completion for unit names doesn't work with any prefix, including t
Processing control commands:
> tags -1 moreinfo unreproducible
Bug #780235 [systemd] "man init" brings up systemd(8) despite /sbin/init coming
from sysvinit-core
Added tag(s) unreproducible and moreinfo.
--
780235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780235
Debian Bug Tracking Syst
Control: tags -1 moreinfo unreproducible
Am 10.03.2015 um 23:59 schrieb Samuel Bronson:
> Package: systemd
> Version: 215-12
> Severity: important
> File: /usr/share/man/man1/systemd.1.gz
>
> Dear Maintainer,
>
> When I run "man init", I expect to see the manpage corresponding to
> /sbin/init; s
also sprach Michael Biebl [2015-04-08 11:44 +0200]:
> > In this light, I agree that there is no urgency.ยน How likely to you
> > regard the possibility that resolved will become non-optional in the
> > near future?
>
> I have no idea, sorry.
Hm, I was looking more for a statement like "nothing is
Am 08.04.2015 um 11:33 schrieb martin f krafft:
> also sprach Michael Biebl [2015-04-08 10:45 +0200]:
>> Just like resolved needs explicit opt in by the admin (the service is
>> disabled by default).
>> Also, it writes the resolv.conf to /run/systemd/resolve/resolv.conf.
>> So the admin needs to e
also sprach Michael Biebl [2015-04-08 10:45 +0200]:
> Just like resolved needs explicit opt in by the admin (the service is
> disabled by default).
> Also, it writes the resolv.conf to /run/systemd/resolve/resolv.conf.
> So the admin needs to explicitly replace /etc/resolv.conf with a symlink
> to
Processing commands for cont...@bugs.debian.org:
> tags 778608 + pending
Bug #778608 [systemd] systemd: please consider backporting logind CAP_SYS_ADMIN
fixes
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
778608: http://bugs.debian.org/cgi
Processing commands for cont...@bugs.debian.org:
> tags 762343 + pending
Bug #762343 [systemd] systemd: timesyncd should run in VMware
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
762343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76
Processing commands for cont...@bugs.debian.org:
> tags 780711 + pending
Bug #780711 [systemd] nspawn: getty restart loop
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
780711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780711
Debian B
Am 08.04.2015 um 09:55 schrieb martin f krafft:
> also sprach Marco d'Itri [2015-04-07 22:57 +0200]:
>>> We don't enable AVAHI nor do we install cups-browsed to make things
>>> work out of the box.
>> Don't we? Then we probably should do it on desktop systems, since
>> autoconfiguration greatly i
also sprach Marco d'Itri [2015-04-07 22:57 +0200]:
> > We don't enable AVAHI nor do we install cups-browsed to make things
> > work out of the box.
> Don't we? Then we probably should do it on desktop systems, since
> autoconfiguration greatly improves the user experience.
Yes, it's great that w
On 04/07/2015 09:25 PM, Michael Biebl
wrote:
and it does check for the ev.code == SW_DOCK event:
http://cgit.freedesktop.org/systemd/systemd/tree/src/login/logind-button.c#n203
Is is the event you get when docking? I boot with the laptop already
do
On 04/07/2015 09:17 PM, Michael Biebl
wrote:
What's your hardware? Which graphics card hardware / drivers do
you use?
It's a nvidia graphic adapter with nvidia drivers.
How does systemd detect the docked status?
30 matches
Mail list logo
