Hello Pascal,
You should be able to use systemd just once from your bootloader.
Here is a good start:
https://wiki.debian.org/systemd
Thank you very much Laurent.
I will take a further look at systemd (not yet tested, btw).
Benjamin.
Le 13/05/2014 07:47, Pascal Obry a écrit :
Laurent,
I
Hello Benjamin,
You should be able to use systemd just once from your bootloader.
Here is a good start:
https://wiki.debian.org/systemd
Ok, quite easy in fact. Just did it and could connect using gdm3.
Thanks a lot!
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is
Laurent,
I confirm. As expected, using systemd as init system (PID1) works fine
with last package version of gdm3.
Thank you,
Benjamin.
May 12 10:57:07 * dbus[2026]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.5 (uid=0 pid=2179 comm=/usr/sbin/gdm3 )
Le Mon, 12 May 2014 12:02:12 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
Hello Laurent,
Hello,
I upgraded my system and got gdm3:amd64 3.8.4-8.1 installed. After
reboot, I opened a VC to strace systemd-logind, then I tried to login
through gdm.
I attached the log results.
Hello Benjamin,
Pascal, I also successfully tried lightdm. I got your point, and thank
you very much for your messages.
However, since GDM3 comes with Gnome 3, I am pretty sure it would be
comfy for most users to just get GDM3 working stable without
installing any other package (even if
Le Mon, 12 May 2014 12:02:12 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
Hello Laurent,
I upgraded my system and got gdm3:amd64 3.8.4-8.1 installed. After
reboot, I opened a VC to strace systemd-logind, then I tried to login
through gdm.
I attached the log results.
Laurent,
I think we have identified the issue, basically logind is
started/activated too late. We'll try to fix this to preserve
compatibility with other initsystem than systemd, but I guess it's a
good occasion to start using it if you don't mind :)
Sure, ready for anything...
I would
Hello,
I've got the same problem with gdm3 version 3.8.4-7 and 3.8.4-8. Only
fallback session works.
Regards.
Bob
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Le Wed, 07 May 2014 17:33:01 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
Well, I am not sure… It’s more or less a default Jessie installation.
I hope those following data will help. Please let me know.
[...]
So apparently I see a session opened here so logind itself seems to
Le Thu, 8 May 2014 09:08:36 +0200,
Laurent Bigonville bi...@debian.org a écrit :
Le Wed, 07 May 2014 17:33:01 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
Well, I am not sure… It’s more or less a default Jessie
installation. I hope those following data will help. Please let
Hello,
I reinstalled that package.
# aptitude reinstall libpam-systemd
[…]
Preparing to unpack .../libpam-systemd_204-10_amd64.deb ...
Unpacking libpam-systemd:amd64 (204-10) over (204-10) ...
Processing triggers for man-db (2.6.7.1-1) ...
Paramétrage de libpam-systemd:amd64 (204-10) ...
I’ll
Le Thu, 08 May 2014 11:20:41 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
The issue occurred again:
0. I submit the login form.
1. I see a frozen desktop few seconds (while it should pop-in with a
fancy effect).
2. The screen shutdown (standby).
3. If I hit a key, I see the
Thank you for your time and efforts.
I tried adding this debug parameter into `/etc/pam.d/common-session`:
session optionalpam_systemd.so debug=yes
Then, I flushed the auth.log and rebooted the computer (with v3.8.4-7).
Please see the attached file for results.
Also, when a Gnome
Oups, erratum:
Whith gmd3 v3.8.4-7, before I submit the login form, I get the two
directories (mine and Degian-gdm’s one) under `/run/user/`… until gdm3
tries to open the Gnome session. Then, I get this error notification
from the VC:
[ 178.844254] systemd-logind[2370]: Removed session 1.
And
Le Thu, 08 May 2014 14:44:12 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
[...]
The `/run/user/` directory is 755 root:root.
The Debian-gdm user could fail to create its directory? Should I try
to create this directory from the VC before I try to open a Gnome
session?
I
It did not work… And I had to reinstall those packages (unless the
previous gdm3 neither worked).
Another idea?
I am thinking to try another DM (like, say, LightDM or SLiM). Will see
if the problem still occurs or not. I will let you know.
Thank you,
Benjamin.
Le 08/05/2014 16:14, Laurent
Le Thu, 08 May 2014 17:31:34 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
It did not work… And I had to reinstall those packages (unless the
previous gdm3 neither worked).
Do you still have the output of auth.log with consolekit uninstalled?
Another idea?
I am thinking
Benjamin,
I am thinking to try another DM (like, say, LightDM or SLiM). Will see
if the problem still occurs or not. I will let you know.
As reported earlier I have tested this and it works for me. I can
definitely connect to my gnome-shell session using lightdm.
--
Pascal Obry / Magny
Package: gdm3
Version: 3.8.4-6
Severity: important
Dear Maintainer,
* What led up to the situation?
I upgraded gdm3 package (and its dependencies) version 3.8.4-6 to 3.8.4-7.
* What was the outcome of this action?
Then, the tomorrow, when I startup the computer, I was unable to login:
Hello,
Could you please verify that you have the latest version of
the policykit-1 package installed? (0.105-5 or 0.112-2) and try again?
Cheers,
Laurent Bigonville
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hello,
Currently, the version 0.105 of policykit-1 is installed.
I will try to install the latest version from the experimental repository.
# aptitude show policykit-1
Paquet : policykit-1
État: installé
Automatiquement installé: oui
Multiarchitecture : étranger
Version : 0.105-5
[…]
# aptitude
Le Wed, 07 May 2014 16:40:03 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
Hello,
Currently, the version 0.105 of policykit-1 is installed.
I will try to install the latest version from the experimental
repository.
Well this is not 100% needed, 0.105-5 should work too.
Do you
Well, I am not sure… It’s more or less a default Jessie installation.
I hope those following data will help. Please let me know.
The PID #1 is /sbin/init (which is not a symlink)
# cat /proc/cmdline
\boot\vmlinuz-3.14-1-amd64 ro root=UUID=***
initrd=boot\initrd.img-3.14-1-amd64
# aptitude show
23 matches
Mail list logo
