Bug#806922: systemctl do not work for non-root

2015-12-02 Thread Martin Pitt
Hello Juhapekka, Juhapekka Tolvanen [2015-12-03 4:02 +0200]: > > Package: systemd > Version: 215-17+deb8u3 > Severity: grave > > > juhtolv@heresy | to 03 joulu 2015 03:52:26 | 1 | pts/1.1 > /home/juhtolv > % systemctl --user status --all > Failed to get D-Bus connection: Yhteys torjuttu I

Processed: Re: Bug#806922: systemctl do not work for non-root

2015-12-02 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #806922 [systemd] systemctl do not work for non-root Severity set to 'normal' from 'grave' > tags -1 moreinfo Bug #806922 [systemd] systemctl do not work for non-root Added tag(s) moreinfo. -- 806922: http://bugs.debian.org/cgi-bin/bugreport.

Bug#806922: systemctl do not work for non-root

2015-12-02 Thread Michael Biebl
Control: severity -1 normal Control: tags -1 moreinfo Hi Am 03.12.2015 um 03:02 schrieb Juhapekka Tolvanen: > > juhtolv@heresy | to 03 joulu 2015 03:52:26 | 1 | pts/1.1 > /home/juhtolv > % systemctl --user status --all > Failed to get D-Bus connection: Yhteys torjuttu What's the output (as

Bug#806922: systemctl do not work for non-root

2015-12-02 Thread Juhapekka Tolvanen
Package: systemd Version: 215-17+deb8u3 Severity: grave juhtolv@heresy | to 03 joulu 2015 03:52:26 | 1 | pts/1.1 /home/juhtolv % systemctl --user status --all Failed to get D-Bus connection: Yhteys torjuttu juhtolv@heresy | to 03 joulu 2015 03:57:32 | 10001 | pts/1.1 /home/juhtolv % system

Bug#806913: udev: user-defined eth naming ignored; worked before upgrade

2015-12-02 Thread Michael Biebl
Am 02.12.2015 um 23:35 schrieb Michael Biebl: > Am 02.12.2015 um 22:15 schrieb Jose Luis Tallon: >> The ethernet interfaces were not renamed at boot, and left as eth0-eth9. >> During boot, systemd actually reported those names (eth0-eth9) when >> configuring networking. > > Please boot with "udev.

Bug#773538: systemd: journal is quite big compared to rsyslog output

2015-12-02 Thread Yuri D'Elia
Package: systemd Version: 228-2 Followup-For: Bug #773538 I'd also like to add that journalctl logging format is not just a bit, but a *lot* bigger than a regular syslog daemon. On two similar systems that I have, one configured with rsyslog and one with journalctl, I have ~200MB for the entire /

Bug#806913: udev: user-defined eth naming ignored; worked before upgrade

2015-12-02 Thread Michael Biebl
Am 02.12.2015 um 22:15 schrieb Jose Luis Tallon: > The ethernet interfaces were not renamed at boot, and left as eth0-eth9. > During boot, systemd actually reported those names (eth0-eth9) when > configuring networking. Please boot with "udev.log-priority=debug" on the kernel command line and then

Bug#806302: marked as done (systemd does not start bluetooth.service if bluetooth soft rfkilled in the previous boot)

2015-12-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Dec 2015 23:10:43 +0100 with message-id <565f6c63.3080...@debian.org> and subject line Re: Bug#806302: systemd does not start bluetooth.service if bluetooth soft rfkilled in the previous boot has caused the Debian Bug report #806302, regarding systemd does not start bluet

Bug#806913: udev: user-defined eth naming ignored; worked before upgrade

2015-12-02 Thread Jose Luis Tallon
On 12/02/2015 09:50 PM, Michael Biebl wrote: Control: tags -1 + moreinfo Am 02.12.2015 um 21:12 schrieb Jose Luis Tallon: Package: udev Version: 215-17+deb8u2 Severity: normal Dear Maintainer, After upgrading a system from wheezy+backports to jessie, udev/systemd-udev (upgraded to systemd

Bug#806302: systemd does not start bluetooth.service if bluetooth soft rfkilled in the previous boot

2015-12-02 Thread Mattia Belluco
On 12/02/2015 09:53 PM, Michael Biebl wrote: > Am 02.12.2015 um 20:30 schrieb Mattia Belluco: >> On 11/26/2015 04:01 PM, Michael Biebl wrote: >>> Am 26.11.2015 um 09:53 schrieb Mattia Belluco: >>> I'm confused, why is this a bug in particular (you disabled bluetooth) >>> and systemd specifically (b

Bug#806302: systemd does not start bluetooth.service if bluetooth soft rfkilled in the previous boot

2015-12-02 Thread Michael Biebl
Am 02.12.2015 um 20:30 schrieb Mattia Belluco: > On 11/26/2015 04:01 PM, Michael Biebl wrote: >> Am 26.11.2015 um 09:53 schrieb Mattia Belluco: >> I'm confused, why is this a bug in particular (you disabled bluetooth) >> and systemd specifically (bluetooth.service is not shipped by systemd)? > You

Bug#806913: udev: user-defined eth naming ignored; worked before upgrade

2015-12-02 Thread Michael Biebl
Control: tags -1 + moreinfo Am 02.12.2015 um 21:12 schrieb Jose Luis Tallon: > Package: udev > Version: 215-17+deb8u2 > Severity: normal > > Dear Maintainer, > >After upgrading a system from wheezy+backports to jessie, > udev/systemd-udev > (upgraded to systemd+newer udev) has stopped renami

Processed: Re: Bug#806913: udev: user-defined eth naming ignored; worked before upgrade

2015-12-02 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #806913 [udev] udev: user-defined eth naming ignored; worked before upgrade Added tag(s) moreinfo. -- 806913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___

Bug#806302: systemd does not start bluetooth.service if bluetooth soft rfkilled in the previous boot

2015-12-02 Thread Mattia Belluco
On 11/26/2015 04:01 PM, Michael Biebl wrote: > Am 26.11.2015 um 09:53 schrieb Mattia Belluco: >> Package: systemd >> Version: 228-2 >> Arch:amd64 >> >> If bluetooth is disabled by soft rfkill (blueman applet) the status >> survives reboot and systemd no longer loads bluetoothd (which in tur

Bug#806885: systemd: Unable to disable mount of /run/user/$something

2015-12-02 Thread Joerg Jaspert
Am 2015-12-02 15:04, schrieb Felipe Sateler: In general, I'm not comfortable forwarding stuff that I won't personally use, since if feedback is required then I would not now what to respond. A 2way gateway you play then? :) Upstream tracker is at https://github.com/systemd/systemd/issues A

Bug#806885: systemd: Unable to disable mount of /run/user/$something

2015-12-02 Thread Felipe Sateler
On 2 December 2015 at 10:20, Joerg Jaspert wrote: > Package: systemd > Version: 215-17+deb8u2 > Severity: normal > > Dear Maintainer, > > (thats mostly a bug/feature for upstream, please forward to wherever needed, > thanks). In general, I'm not comfortable forwarding stuff that I won't personall

Bug#806885: systemd: Unable to disable mount of /run/user/$something

2015-12-02 Thread Joerg Jaspert
Package: systemd Version: 215-17+deb8u2 Severity: normal Dear Maintainer, (thats mostly a bug/feature for upstream, please forward to wherever needed, thanks). It seems that the mounting of /run/user/$something as tmpfs can not be disabled. Would be nice if it has an option for this. Background