[bts-link] source package systemd

2016-09-15 Thread bts-link-upstream
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #837183 (http://bugs.debian.org/837183) # Bug title: systemd: unprivileged call to sys

Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

2016-09-15 Thread Linas Vepstas
On Thu, Sep 15, 2016 at 6:45 AM, Vlad Orlov wrote: > > > Is su actually used for running graphical apps? In my case, I either accidentally typed into an su window, or possibly ran the gconf editor as root, for some possibly good or bad reason, possibly having to do with xdm, gdm whateverdm, or p

Bug#837759: network configuration stops working reliably

2016-09-15 Thread Felipe Sateler
On 14 September 2016 at 18:34, Wolfgang Walter wrote: > On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote: >> Control: tags -1 moreinfo >> >> On 14 September 2016 at 06:59, Wolfgang Walter >> wrote: >> > Package: systemd >> > Version: 231-6 >> > Severity: grave >> > >> > Startin

Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

2016-09-15 Thread Vlad Orlov
Hi, Just found a link to a pam module [1] (posted in the comment at [2]). > It's a pam module that removes the XDG_RUNTIME_DIR environment variable from > the environment if the user authenticating is different from the user owning > it. This is for the case of programs like gksu clobbering the

Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

2016-09-15 Thread Vlad Orlov
Hi, Is su actually used for running graphical apps? Most people seem to use gksu for that. But gksu --help shows a weird warning about using -l argument: --login, -l Make this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target user

Bug#837893: systemd: Logging from gnome session is passed on to all syslog facilities

2016-09-15 Thread Matijs van Zuijlen
Package: systemd Version: 231-6 Severity: normal Since recently, log messages from programs running under the gnome session have started appearing in all logs in /var/logs, including /var/logs/kern.log, even though my rsyslog configuration has not changed, and correctly only routes kern.* there.

Processed: Re: Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

2016-09-15 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 adduser Bug #837871 [udev] no need for addgroup: The group `input' already exists as a system group. Exiting. messages Bug reassigned from package 'udev' to 'adduser'. No longer marked as found in versions systemd/231-6. Ignoring request to alter fixed v

Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

2016-09-15 Thread Afif Elghraoui
Control: reassign -1 adduser Control: affects -1 + udev Hi, Michael and all, On Thu, 15 Sep 2016 04:25:14 +0200 Michael Biebl wrote: > Control: block -1 by 763055 > > Am 15.09.2016 um 01:56 schrieb 積丹尼 Dan Jacobson: > > Package: udev > > Version: 231-6 > > Severity: wishlist > > > > Pe

Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

2016-09-15 Thread Michael Biebl
Am 15.09.2016 um 06:25 schrieb 積丹尼 Dan Jacobson: > Maybe instead test if the group exists via other means, and then only if > it doesn't, use addgroup to add it. No, as said this is a bug in adduser/addgroup. The root cause should be fixed and not worked around in individual packages. Michael