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
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
Hi,
> I opened some user apps: smplayer playing radio, system monitor, gnome
> terminal and
> two root terminals and synaptic. I used 3 workspaces and I could move freely
> from one
> another, either hitting the upper left hand corner or clicking on Activities.
According to some comments from
Hi,
> I'm not convinced it is libpam-systemd which is responsible here.
You can check [1] to get some info about libpam-systemd doing
something wrong here.
Also we had this issue for months in Linux Mint before Clement Lefebvre
made a patch [2] that fixed it. After the patched libpam-systemd ha
> I've tried most if not all of those instructions without being able to
>
> reproduce.
>
> If someone can provide the exact environment under which this is
>
> reproducle, then this would certainly help.
Please read the mentioned comments. I didn't just list the comments
with "me too". I've ch
> Well, can you provide instructions how to reproduce it?
>
> Everything which has been posted so far was not sufficient to trigger
>
> this issue here. So it is indeed not reproducible for me.
Not enough instructions?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732209#15
https://bugs.deb
Hi,
Can you please try the patch for systemd from [1]
and check if the issue is still present?
[1]
https://github.com/linuxmint/systemd/commit/f7ab85f1e1169ac1598dfc1fba1c01063840b3c5.patch
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintain
Weird... today I'm able to reproduce it with "gksu pluma" again, 100%.
I'm out of clues :-/
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-mainta
Hi,
Can you still reproduce it in the current Jessie?
Does the ownership of /run/user/1000/dconf/user change
to root:root?
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mai
Hi Miklos,
For some reason, now I'm having trouble reproducing the ownership
change of /run/user/1000/dconf/user to root using my method from [1].
I've tried it on two Jessie installations, one has traditional sysvinit and
another has systemd-sysv. Both systems are fully updated, the version
of
Hi,
This is weird, I can reproduce it 100% with "gksu pluma" (even without
arguments, i.e. not opening any file). Did you use gksu or gksudo BTW?
Also can you please post the output of "aptitude search ~isystemd" and
"aptitude search ~isysv"?
Here's what I have in one of my VMs:
monsta@jessica:~
Hi,
> Just out of curiosity, what init system are you using? Usually, these
> weird bugs only occur when using something like systemd-shim and any
> other of these hacky systemd work arounds.
Well, I have one system with systemd-shim + sysvinit-core and a few ones
with systemd as init. I can repr
Hi,
Can you please provide step-by-step instructions, how to setup the test
environment (which packages are installed, which environment is running)
and which commands to use to trigger the problem.
The best way I know is to run MATE's text editor (pluma) via gksu, as
I've described in [1]. I
found 732209 217-3
thanks
Also tried systemd 217-3 from Experimental, the issue is still present.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-system
Hi,
> BTW, this only happens with GNOME sessions. With other window managers
> (e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a
> systemd bug, rather it's related to GNOME. Do you agree to reassign this
> bug against either the 'gnome-session' or the 'gnome-shell' package?
No,
Hi,
I just decided to nofity all the participants here, in case
this new info might be interesting or useful :)
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listi
16 matches
Mail list logo
