Bug 707876 – gdm fails to switch to initial vt if compiled --with-plymouth

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 707876 - gdm fails to switch to initial vt if compiled --with-plymouth


Summary:	gdm fails to switch to initial vt if compiled --with-plymouth


Status:	RESOLVED OBSOLETE

Product:	gdm
Classification:	Core
Component:	general
Version:	3.8.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GDM maintainers
QA Contact:	GDM maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-09-10 18:37 UTC by Jan Vesely
Modified:	2018-05-24 10:56 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Jan Vesely 2013-09-10 18:37:12 UTC

after the boot the screen is stuck on vt1 and displays console login,
manual switch to vt7 works correctly and displays gdm login.

configuration:
                    GDM 3.8.4
                    ============

	prefix:                   /usr
	exec_prefix:              ${prefix}
        libdir:                   /usr/lib64
        bindir:                   ${exec_prefix}/bin
        sbindir:                  ${exec_prefix}/sbin
        sysconfdir:               /etc
        sysconfsubdir:            gdm
        gdmconfdir:               ${sysconfdir}/${sysconfsubdir}
        dmconfdir:                /etc/dm
        localstatedir:            /var
        datadir:                  /usr/share
	consolekit location:      ${libexecdir}
	gnome-session-check-accel location: ${libexecdir}
	polkit-gnome location:    ${libexecdir}
	source code location:	  .
	compiler:		  x86_64-pc-linux-gnu-gcc
	cflags:		          -O2 -march=native -mtune=native -fomit-frame-pointer -pipe
        Maintainer mode:          no

        user:                     gdm
        group:                    gdm

        dbus-1 system.d dir:      /etc/dbus-1/system.d
        PAM prefix:               ${sysconfdir}
        PAM config:               exherbo
        X server:                 /usr/bin/Xorg

        TCP Wrappers support:     no
        Xinerama support:         
        XDMCP support:            yes
        SELinux support:          no
        ConsoleKit support:       no
        systemd support:          yes
        systemd unit dir:         /usr/lib/systemd/system
        plymouth support:         yes
        UPower support:           yes
        Build with RBAC:          no
        Initial VT:               7
        Enable documentation:     yes

Comment 1 Pacho Ramos 2014-03-19 22:33:53 UTC

Any news on this? If we aren't supposed to use vt7 with plymouth then I would make both configure options exclusive (or ignored) to prevent this strange issues

Thanks

Comment 2 Ray Strode [halfline] 2014-03-20 14:00:13 UTC

plymouth and GDM both have build time options for deciding which VT to start on. The options need to match.  This is part of the job of the distribution doing hte integration work between the two.

Comment 3 Pacho Ramos 2014-03-20 21:23:32 UTC

But I don't think doesn't have much change to allow to set vt7 at configure time if it will later fail if plymouth is enabled :/

Comment 4 Pacho Ramos 2014-03-20 21:29:50 UTC

Anyway, just handle downstream too :)

Comment 5 Ray Strode [halfline] 2014-03-21 13:11:55 UTC

if they're both configured for VT 7 it shouldn't fail if plymouth is enabled.

Comment 6 GNOME Infrastructure Team 2018-05-24 10:56:48 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/166.