[SOLVED] No available TTYs when logged in to GNOME session (LFS v9 SysV)
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Good to know That at least tells us its me and not LFS or GDM. I've more or less decided to restart my build from scratch (pun intended) at this point. Too many small weird issues. Pulseaudio isn't working either for instance. But I do believe all these weird issues have a common cause (dbus-elogind etc), but it might be easier to just redo everything even if it's gonna take a heckload of time. At least this time I'll do a systemd build.
The rebuild will have to wait at least a week before I have the time to put the effort into it, so I'm still gonna try and figure it out until then and I'm open for any helpful suggestions.
I've uploaded parts of sys.log to pastebin. A couple things stand out, which may or may not be related:
Code:
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: DEBUG(+): Enabling debugging
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: DEBUG(+): Could not make systemd aware of QT_IM_MODULE=ibus environment variable: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: DEBUG(+): Could not make systemd aware of XMODIFIERS=@im=ibus environment variable: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: DEBUG(+): Could not make systemd aware of XDG_MENU_PREFIX=gnome- environment variable: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: DEBUG(+): Using systemd for session tracking
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: DEBUG(+): GsmManager: setting client store 0x7f5b980078d0
Dec 9 14:45:47 bioLinux gnome-session-binary[829]: DEBUG(+): Could not make systemd aware of SESSION_MANAGER=local/bioLinux:@/tmp/.ICE-unix/829,unix/bioLinux:/tmp/.ICE-unix/829 environment variable: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files
I've checked in the service directory (/usr/share/dbus-1/services) and "org.freedesktop.systemd1.service" isn't there, but I don't know whether that's because I'm on SysV that uses elogind or if it's actually supposed to be there.
I managed to get rid of the errors listed above, but to no effect on my issue. I think I'll start over again today with a systemd build, the only question is if I should go for the development version. Do you think it would be much of a risk? Would be nice to have the latest version of gnome and fewer security vulnerabilities.
I'm think I know what may have caused this issue now. Early in the lfs book the authors mention that if something is wrong with either gcc or glibc, it may result in a "subtly broken" system that won't show up until near the completion of a distribution. Indeed, in some of the logs there were mentions of glibc errors. Just a guess, but it's the best I have so far.
Anyway, the new base LFS systemd build is now done, complete with lynx, gpm, sudo, wget etc. Now only 1461294638503029598 packages remain
System is now completely rebuilt and working. I guess I'll mark this thread as solved now, even though it's not really solved as such. But for anyone else coming here from google, maybe going with systemd is a better choice if you want to build gnome. The exact cause of my issue was probably something I did early on that screwed up my build though. At least everything seems to be working smoothly now. Next up, firefox, vlc, libreoffice, transmission, openvpn etc.
Hmm.. That's interesting. Seems somewhat similar to what I saw in my logs as well. I'll mark this mentally as a definite vindication, haha From what people have been telling me, it seems gnome just works better on systemd anyhow.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.