intrigeri writes:
> Hi,
>
> intrigeri wrote (17 Jul 2014 09:19:21 GMT) :
>> I'll try to re-enable hidepid in the next few days, to see if current
>> sid's GDM/GNOME Shell/whatever are still incompatible with this
>> security measure.
>
> I've hidepid=2 re-enabled hidepid=2 in fstab for /proc, reg
Hi,
intrigeri wrote (17 Jul 2014 09:19:21 GMT) :
> I'll try to re-enable hidepid in the next few days, to see if current
> sid's GDM/GNOME Shell/whatever are still incompatible with this
> security measure.
I've hidepid=2 re-enabled hidepid=2 in fstab for /proc, regenerated
initramfs just in case
Hi,
Stig Sandbeck Mathisen wrote (16 Mar 2014 09:14:06 GMT) :
> When starting gnome session from startx, or starting gdm3, the
> gnome-shell process tries to access /proc/1/cgroup, which would
> obviously not work when /proc is mounted with -o hidepid=, but I could
> not find anything relevant in
Control: reassign -1 gnome-shell
Michael Stapelberg writes:
> So, I think the problem is in how gdm figures out whether it should
> talk to logind in the first place, not in any systemd component. Can
> you verify this? (And if so, can you please reassign the bug?)
>
> ① https://bugs.archlinux.
Hi Stig,
Stig Sandbeck Mathisen writes:
> I can reproduce this issue on my workstation now, I run systemd and
> gnome on a freshly updated and rebooted jessie workstation.
>
> When /proc is mounted with hidepid=1 or hidepid=2, I can log in with
> gdm3, but I get no gnome session, only a "Oh, no!
Control: found 733112 204-7
I can reproduce this issue on my workstation now, I run systemd and
gnome on a freshly updated and rebooted jessie workstation.
When /proc is mounted with hidepid=1 or hidepid=2, I can log in with
gdm3, but I get no gnome session, only a "Oh, no! Something went wrong"
Kjö Hansi Glaz wrote (19 Feb 2014 23:36:31 GMT) :
> I don't have access to the buggy system anymore. On a new jessie install
> the problem doesn't show up. This problem might still be an issue for
> wheezy to jessie migration.
Are you using hidepid on the new Jessie system?
Cheers,
--
intriger
Hi,
I don't have access to the buggy system anymore. On a new jessie install
the problem doesn't show up. This problem might still be an issue for
wheezy to jessie migration.
Cheers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Michael Stapelberg wrote (17 Feb 2014 19:41:33 GMT) :
>> I sent it to Michael on Jan 13.
> Correct, and I replied to Kjö’s private email with this message:
Sorry for the noise.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Hi Kjö,
Kjö Hansi Glaz writes:
>> Do you think you'll be able to provide the additional information
>> Michael asked?
>>
> I sent it to Michael on Jan 13.
Correct, and I replied to Kjö’s private email with this message:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733112#27
--
Best regar
Hi,
> > Can you repeat that with -s 2048 so that we can actually see a bit of
> > the message’s content? Also, a trace of what’s happening on dbus would
> > be useful. I think you can use dbus-monitor for that.
>
> Do you think you'll be able to provide the additional information
> Michael asked?
Hi,
intrigeri wrote (23 Jan 2014 16:30:29 GMT):
> I had the exact same buggy behaviour, and workaround'd it by removing
> hidepid=2 (and the corresponding gid=) from the /proc mount
> options in /etc/fstab. Maybe GDM3 fails to detect a running logind
> when it cannot list all running processes
Hi Kjö,
Michael Stapelberg wrote (01 Jan 2014 14:49:13 GMT) :
> Kjö Hansi Glaz writes:
>> I use systemd as init. It seems that gdm3 fails to communicate with
>> logind as it fallsback to consolekit as a login manager.
> Can you also strace gdm3 please? I’m not yet convinced the bug is in
> system
Hi,
I had the exact same buggy behaviour, and workaround'd it by removing
hidepid=2 (and the corresponding gid=) from the /proc mount
options in /etc/fstab. Maybe GDM3 fails to detect a running logind
when it cannot list all running processes?
Cheers,
--
intrigeri
| GnuPG key @ https://ga
Hi Kjö,
Kjö Hansi Glaz writes:
> On Sun, Jan 12, 2014 at 10:49:16PM +0100, Michael Stapelberg wrote:
>> Kjö Hansi Glaz writes:
>> > Find attached:
>> >
>> > gdm3.strace: strace of gdm3 (attached after a service gdm3 restart)
>> > gdm-simple-slave.strace: strace of gdm-simple-slave (idem)
>> You
Hi Kjö,
Kjö Hansi Glaz writes:
> I use systemd as init. It seems that gdm3 fails to communicate with
> logind as it fallsback to consolekit as a login manager.
Can you also strace gdm3 please? I’m not yet convinced the bug is in
systemd-logind (or libsystemd-login0).
> Please find attached a str
Hi,
On Wed, Dec 25, 2013 at 09:33:30PM +0100, Tollef Fog Heen wrote:
> > I use systemd as init. It seems that gdm3 fails to communicate with
> > logind as it fallsback to consolekit as a login manager.
> >
> > As a result, several features of gnome doesn't work as expected.
>
> Do you have libpa
]] Kjö Hansi Glaz
Hi,
> I use systemd as init. It seems that gdm3 fails to communicate with
> logind as it fallsback to consolekit as a login manager.
>
> As a result, several features of gnome doesn't work as expected.
Do you have libpam-systemd installed? If not, does installing it fix
the
Package: libsystemd-login0
Version: 204-5
Severity: normal
Dear Maintainer,
I use systemd as init. It seems that gdm3 fails to communicate with
logind as it fallsback to consolekit as a login manager.
As a result, several features of gnome doesn't work as expected.
Please find attached a strace
19 matches
Mail list logo
