The wayland issue should be gone in bookworm/sid.
As stated in https://gitlab.gnome.org/GNOME/gdm/-/issues/103,
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/128 is merged (in
gdm 40).
It supersedes https://gitlab.gnome.org/GNOME/gdm/merge_requests/37
I cannot tell about the initial gdm3
The wayland issue should be gone in bookworm/sid.
As stated in https://gitlab.gnome.org/GNOME/gdm/-/issues/103,
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/128 is merged (in
gdm 40).
It supersedes https://gitlab.gnome.org/GNOME/gdm/merge_requests/37
I cannot tell about the initial gdm3
The wayland issue should be gone in bookworm/sid.
As stated in https://gitlab.gnome.org/GNOME/gdm/-/issues/103,
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/128 is merged (in
gdm 40).
It supersedes https://gitlab.gnome.org/GNOME/gdm/merge_requests/37
I cannot tell about the initial gdm3
Hi:
I'm compiling it, but is there a way of easily create a .deb package
with the compiled code? (there seems to be debian/control files, so it
seems to be something quite straight up...)
El 14/4/19 a las 16:36, Iain Lane escribió:
Hi,
Sorry for the delay. Niels pointed me at this bug,
Hi,
Sorry for the delay. Niels pointed me at this bug, which is suspiciously
similar to one we saw on Ubuntu around the same time ...
On Wed, Jun 13, 2018 at 01:43:18PM +0200, rastersoft wrote:
> After several tests, I started to suspect that the problem could be in the
> firmware loading: my
Package: gdm3
Version: 3.28.2-2
Found extra info that, in my opinion, points to a race condition during
boot process, as already commented in my previous entry.
In my system, when I install debian SID in a mechanical hard disk, GDM3
boots fine and allows me to enter in both X11 and Wayland.
Hi,
I'm having the same issue and removing the. ICEAuthority* files fixed the issue
here as well.
Thank you for the fix Philipp .
On Mon, 07 May 2018 11:08:14 +0200 Philipp Falk
wrote:
> Package: gdm3
> Version: 3.22.3-3+deb9u1
> Severity: wishlist
>
> Dear Maintainer,
>
> I just
Package: gdm3
Version: 3.28.1-1
More info: it also fails when booting SID with kernel 4.9.0-6 (from
Debian Stable).
--- System information. ---
Architecture:
Kernel: Linux 4.16.0-1-amd64
Debian Release: buster/sid
500 unstable ftp.debian.org
--- Package information. ---
Depends (Version) |
Package: gdm3
Version: 3.28.1-1
I have this same problem since about ten days. This weekend I decided to
do a clean install and found that I was unable: I deleted the system
partition, booted an USB with debian netinst version, installed stable
with just gnome shell, and everything worked
Looks like it does boot after ten minutes or so. It seems only Wayland
variant of gdm is failing. Gnome on Wayland has no issues though.
On Sat, May 5, 2018, 14:00 Mladen Mijatov wrote:
> Package: gdm3
> Version: 3.28.1-1
> Severity: grave
> Justification: renders package
Package: gdm3
Version: 3.22.3-3+deb9u1
Followup-For: Bug #897975
Dear Maintainer,
I observe the same problem on my notebook and would like to add some additional
information.
1) CPU Intel(R) Celeron(R) CPU N3160 with integrated graphics. This might be
interesting, as there is one (EE) entry
Package: gdm3
Version: 3.22.3-3+deb9u1
Followup-For: Bug #897975
Dear Maintainer,
after recent upgrade, gdm3 also fails to start as for the other reportes. It
doesn't even switch to graphical mode and so the few text boot messages stay
visible.
In contrast to previous reporters, I do not see
Package: gdm3
Version: 3.22.3-3+deb9u1
Severity: wishlist
Dear Maintainer,
I just wanted to confirm that I also encountered this bug on a debian
stable installation.
I also see the "ICELockAuthFile fail: Already exists" message in
the systemd journal.
Removing /var/lib/gdm3/.ICEAuthority* and
Package: gdm3
Version: 3.28.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After recent update system is unable to boot due to GDM3 constantly restarting.
Journal contained message "IceLockAuthFile fail: Already exists" before GDM
exiting and starting againg.
Other
14 matches
Mail list logo