Package: gdm3
Version: 3.8.4-3
Followup-For: Bug #724731
I managed to solve by removing and reinstalling the following packages,
as suggested in commment 71:
gnome-core gnome-shell gdm3 gnome-session
When I reinstalled, I see more packages than those removed. Maybe it's
a hint to find the culprit
Package: gdm3
Version: 3.8.4-3
Followup-For: Bug #724731
Hi,
I solved the blank screen issue (3.8.4-3) installing systemd-ui package.
I tested using both sysvinit and systemd, working like a charm.
Victor
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (
It seems to be solved for me after upgrading to 3.8.4-3.
Here are the information regarding each packages that seems involved in
this bug report :
===
gdm3 :
===
-- System Informat
Package: gdm3
Followup-For: Bug #724731
Same here, libpam-systemd did NOT solve the issue.
When using gdm3, I get a splash screen saying that something went wrong
( "Oops! A problem has occured! .. ") with the only option too log out.
No greeter, username field or password field.
-- System In
Hi,
Installing libpam-systemd only was not a workaround for me. I had to
switch to lightdm as a greeter. Here is the details of my packages :
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architectur
I've been analyzing the list of packages that are having problems and
comparing with my packages.
And what draws the most attention is the libglib2.0-0, which is the package
that I have more updated and it's dependence on GDM3.
Compared with a live version of UbuntuGnome 13.10 which uses GDM 3.8
Package: gdm3
Version: 3.8.4-2
Followup-For: Bug #724731
Now that 3.8.4 has entered unstable I've run into this issue too.
Changing init systems is a drastic work around, I was able to continue
logging in to gnome classic by:
* renaming the .configs directory in my home dir
* using kdm as my log
Followup-For: Bug #724731
Package: gdm3
Version: 3.8.4-2
Hi,
In my case, I use like the systemd to replace sysvinit.
Greetings.
Valdinilson.
PS: I do not use autologin.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experime
FYI: I've disabled autologin, so your theory could be right. I'll
investigate it tomorrow.
--
Jascha Geerds
j...@ekby.de
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: gdm3
Version: 3.8.4-2
Followup-For: Bug #724731
Disabling autologin (along with having libpam-systemd installed) seems
to fix the problem, at least for initial startup. I've observed some
reliability issues when restarting gdm3, but initial startup seems to
work.
So: broken without libp
Did you only installed "libpam-systemd" or did you also boot with
systemd (instead of SysVinit) ?
You can temporary boot using systemd by editing the GRUB kernel command
line (press "e" inside GRUB) and append "init=/lib/systemd/systemd" to
it. For further information see https://wiki.debian.org/s
Package: gdm3
Version: 3.8.4-2
Followup-For: Bug #724731
I'm observing this issue as well, and installing libpam-systemd (with a
reboot to restart all services including gdm) did not fix it for me. I
still get a black screen from gdm, but I can startx from a terminal.
- Josh Triplett
-- System
Hi,
I've been with this problem for a long time. And after seeing the review of
Jascha Geerds, I decided to install libpam-systemd.
# apt-get install libpam-systemd
Problem solved.
Valdinilson.
GDM 3.8 just migrated to unstable and I am also hit by this bug.
A workaround for logging in is to use an alternate logging manager for
now. LightDM did the job well and does not pull a lot of additional
dependencies.
I can't really add anything more to this bug report at this point,
although if
I have also tested GDM 3.8. Unfortunately, all I see is a blank screen.
I heard that Gnome 3.6 and higher requires systemd to work. So I
installed the sytsemd packages (without its recommended packages) but
the screen remains blank. Then I figured out that I need to install the
"libpam-systemd" pac
Package: gdm3
Version: 3.8.4-1
Followup-For: Bug #724731
Hi,
Here, gdm3 also stopped working.
My workaround was installing lightdm (has a lot less dependencies
than kdm).
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (150, 'experiment
Package: gdm3
Version: 3.8.4-1
Severity: grave
Hi,
I updated to 3.8 today, and after restarting the gdm3, I cannot login
anymore. Gdm3 somehow starts (graphics are visible) but the login field
is missing.
:0-slave.log says:
--
** (gdm-simple-slave:19770): WARNING **: Couldn't co
17 matches
Mail list logo
