Hi Ron,
Am 05.09.2012 02:32, schrieb Ron Murray:
I did some work on the remaining machine today. First I enabled
debugging on the gdm3 daemon, set up an strace, and started gdm. As
before, gdm3 respawned multiple times in short order before I stopped
it.
Only serious thing I could find was
On Sep 5, 2012, at 5:11, deb...@mikapflueger.de wrote:
Hi Ron
Are you absolutely sure the context for gdm3 is correct at the machine where
it doesn't work? You wrote that you relabeled and rebooted and that would
restore the (wrong) context. Unfortunately (I'm not sure if this is a bug -
Package: selinux-policy-default
Version: 2:2.20110726-9
Followup-For: Bug #683756
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did some work on the remaining machine today. First I enabled
debugging on the gdm3 daemon, set up an strace, and started gdm. As
before, gdm3 respawned multiple
On 08/29/12 06:27, Laurent Bigonville wrote:
Hello,
Alright, I got it.
/usr/sbin/gdm3 is not labeled with the right context.
On my machine here it's labeled:
-rwxr-xr-x. 1 root root system_u:object_r:xdm_exec_t:SystemLow 160296 jun 25
20:29 /usr/sbin/gdm3
And by default in wheezy it's
Hello,
Alright, I got it.
/usr/sbin/gdm3 is not labeled with the right context.
On my machine here it's labeled:
-rwxr-xr-x. 1 root root system_u:object_r:xdm_exec_t:SystemLow 160296 jun 25
20:29 /usr/sbin/gdm3
And by default in wheezy it's labeled as bin_t.
Could you please confirm that
You want us to change the type bin_t into what?
I assumed that you want to relabel the type and I tried relabelling
#chcon -t xdm_exec_t /usr/sbin/gdm3
but it didn't work. Still stuck with a black screen. I had to disable the
selinux at boot to login to X.
Now I am at
#ls -Z /usr/sbin/gdm3
Le Wed, 29 Aug 2012 16:45:02 +0530,
piruthiviraj natarajan piruthivi...@gmail.com a écrit :
You want us to change the type bin_t into what?
I assumed that you want to relabel the type and I tried relabelling
#chcon -t xdm_exec_t /usr/sbin/gdm3
but it didn't work. Still stuck with a black
Hi,
Am Wed, 29 Aug 2012 14:23:29 +0200
schrieb Laurent Bigonville bi...@debian.org:
Le Wed, 29 Aug 2012 16:45:02 +0530,
piruthiviraj natarajan piruthivi...@gmail.com a écrit :
You want us to change the type bin_t into what?
I assumed that you want to relabel the type and I tried
Mika Pflüger:
I just couldn't imagine the label having any influence on the
functionality in permissive mode. Well, I still don't really
understand, but it works. (-:
I also would really like to understand how the label could break gdm
in permissive mode.
I do not like unexplained this
Le 29 Aug 2012 22:42:19 +0200,
Andreas Kuckartz a.kucka...@ping.de a écrit :
Mika Pflüger:
I just couldn't imagine the label having any influence on the
functionality in permissive mode. Well, I still don't really
understand, but it works. (-:
I also would really like to understand
Hi,
Could you please check if you have the selinux-policy-default package
installed?
Also, what is the semanage login -l command giving you?
Cheers
Laurent Bigonville
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
I have the selinux-policy-default package installed.
root@debian:~# semanage login -l
Login NameSELinux User MLS/MCS
Range
__default__ unconfined_u systemLow-systemHigh
root unconfined_u
Hi,
Am Tue, 28 Aug 2012 19:00:46 +0200
schrieb Laurent Bigonville bi...@debian.org:
Could you please check if you have the selinux-policy-default package
installed?
yes, it is recommended by selinux-basics, thus I have it installed.
Also, what is the semanage login -l command giving you?
On 08/28/12 13:00, Laurent Bigonville wrote:
Hi,
Could you please check if you have the selinux-policy-default package
installed?
Also, what is the semanage login -l command giving you?
Cheers
Laurent Bigonville
selinux-policy-default package is installed.
semanage login -l gets me:
The enforcing mode of selinux breaks the gdm3 too.
tag 683756 + moreinfo
thanks
Le Mon, 13 Aug 2012 22:33:14 -0400,
Ron Murray r...@rjmx.net a écrit :
Running gdm3 in debug mode, I get this in the gdm slave log:
-
gdm-welcome][4275]: DEBUG(+): GdmSessionWorker: received pam message
of type 2 with payload 'Would you
On 08/14/12 05:03, Laurent Bigonville wrote:
I'm running selinux in permissive mode and using GDM3 as DM and I've no
problem with it.
Could you look in /etc/pam.d/ and see and see what are call to
pam_selinux module in the gdm3 related services?
Also what is the version of gdm3 package?
Package: selinux-policy-default
Version: 2:2.20110726-9
Followup-For: Bug #683756
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Running gdm3 in debug mode, I get this in the gdm slave log:
-
gdm-welcome][4275]: DEBUG(+): GdmSessionWorker: received pam message of type 2
Package: selinux-policy-default
Version: 2:2.20110726-9
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the last selinux update (around July 6), running selinux in
permissive mode stops gdm3 and X from working for me (haven't tried
enforced mode).
Bootup proceeds normally
19 matches
Mail list logo
