[03:22] hello? [03:22] anybody here? [03:24] o/ [03:28] yes [03:28] * Bashing-om Sometimes thinks I am a body [03:36] gwaily, if you have a Xubuntu support question, please just ask it (be patient, people respond when they can). For general discussion, #xubuntu-offtopic is more appropriate [03:40] what is this thing used for? I'm new to linux [03:42] IRC is a chat protocol that's kinda like Discord, only it's a lot older. This particular chat room (or channel, in IRC terms) is for Xubuntu technical support. [03:42] Basically, if something goes wrong with your computers, there's a bunch of volunteers here who might be able to help you fix it. [03:43] (Heh, "computers" was a typo, though still accurate :P) [03:45] There's also channels for just chatting with people (#ubuntu-offtopic being one of the most popular), channels for discussing a particular topic (#ubuntu-discuss and #linux for instance), etc. [03:46] this room is specifically for Xubuntu questions (supported releases only) [05:41] Hi, I have a very strange problem with Xubuntu 22.04.1, can someone please help? I have a PC that I need to autologin (it's running a graphical program unattended as an appliance), but randomly I will still get a login prompt on boot. On certain hardware I get a login prompt 99% of the time, on certain other hardware (with a cloned disk image) [05:41] I'll get a login prompt 10% of the time. I've already followed some online suggestions to create the autologin group and add the user to that, it doesn't solve the issue. How can I troubleshoot what's going on? Is there a way to nuke PAM or the greeter or something, so it's literally impossible to get a login prompt? [05:46] Silly question, but are you sure it's the login prompt you're seeing and not the screen locker? [05:47] Thanks for your reply. I am not sure. How can I tell the difference? I have configured power options to not sleep nor lock, though. This is the first screen that appears on boot. [05:50] As part of trying to fix the problem, I had also put the user into the group nopasswd login. At which point the login prompt doesn't require a password anymore, instead you had to just click the login button. I've removed the user from that group. [05:55] Sorry, got distracted, back now. [05:55] There's two possible ways to tell the difference. [05:55] For one, a login screen *should* let you attempt to shut the computer down. A lock screen usually won't provide that option. [05:56] For two, a login screen will take a while to log into, whereas a lock screen will come unlocked almost instantly when you provide your password and hit Enter. [05:56] If the screen is impeding your ability for the app to work, though, it's probably a login screen. [05:57] Ok. I have the power icon on the top right, which allows me to shutdown/restart the machine. So that mean's it's a login screen? [05:57] Yeah. [05:57] The tricky thing is, the problem occurs intermittently. I can reboot over and over, and it will autologin half of the time sometimes. [05:58] I'm sadly not too familiar with how autologin works without a greeter, and if autologin with a greeter doesn't work, then I don't really know how to proceed here. What you might be able to do is uninstall the greeter (which will make the system boot into a terminal, I believe), then enable autologin on the console and add a "startx" line to $HOME/.profile to start the X session. [05:58] You'll definitely want to test that before actually doing it in production. [05:59] Also the GUI might end up looking wonky - it may be possible to rectify that by making a change to $XDG_CONFIG_DIRS just before running startx, but I don't know if that will work on Xubuntu or not. [06:00] Ok, I will try that, thanks. Also, I'm not too familiar with the deep guts of linux. Can you point me to a log file where I might look for errors and such? Would it be var/log/lightdm/lightdm.log? [06:05] That sounds likely. [06:05] Maybe also look at the output of "journalctl". [06:06] kk Thanks. If anyone else has any insights, please help? [06:12] Hmm, /var/log/lightdm/seat0-greeter.log has these lines: [06:12] ** Message: 16:35:27.836: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf [06:12] Excess arguments. [06:12] (lightdm-gtk-greeter:879): Gtk-WARNING **: 16:35:28.417: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar) [06:12] Is this normal? [06:15] There's nothing in lightdm.log that indicates it was trying to autologin, would it normally say something if so? [06:21] I actually don't know :P [06:21] Sorry, I've never had autologin fail on me, so I'm giving somewhat general troubleshooting advice and ideas that are mostly shots in the dark. [06:23] It's very mysterious. It works perfectly 100% in a VM. Just on actual hardware does it act oddly. [06:24] If sometimes autologin works and sometimes it doesn't, and especially if it's hardware-dependent, I'm guessing this is a race condition bug in LightDM itself. [06:24] Might be worth filing a bug report on. [06:24] But in the mean time, you just need the system to work. [06:25] So, here's a possibly helpful question. Is the GUI actually used? Or is it just part of the app but you never interact with it? [06:25] Meh, that's still going to lead to complicated answers though. [06:25] hmm... [06:26] This is for a digital signage system. So I need to be able to display MPV at least. Also the other staff onsite aren't familiar with Linux so having a GUI kinda helps them if they need to change IP address or whatever. [06:27] "Further investigation on what I was seeing showed this to be a race between X starting and the intel i915 graphics kernel module being loaded (because it's not built into the kernel)." Drat. [06:27] https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875 Looks like you're running into this bug. [06:27] -ubottu:#xubuntu- Launchpad bug 1250875 in lightdm (Ubuntu) "Lightdm sometimes fails to auto login" [Undecided, Confirmed] [06:28] I don't know if that comment is accurate or not, but it looks like this is something that's happened to other peopel. [06:28] *people [06:30] Ah, nice find, thanks. Hmm, I already jumped ship on this system from Kubuntu to Xubuntu due to running into some obscure bug. Maybe it's time to jump to Lubuntu -_-; [06:30] What was the bug on Kubuntu? [06:30] Was it also with the greeter? [06:31] Because you should be aware that Kubuntu and Lubuntu both use the same greeter, SDDM. [06:31] (Xubuntu uses LightDM, which is different.) [06:31] AlanSmith425: OK, I found some interesting info. [06:32] Is there a ~/.dmrc file? [06:32] No, with Kubuntu the problem was, if the system was booted when the screen was turned off, then turning the screen on wouldn't display an image. [06:33] Yes, I have tried some troubleshooting around the ~/.dmrc file. I have tried having it, deleting it, and also changing the session name to "xfce" [06:33] Do you have an /etc/lightdm/lightdm.conf file or /etc/lightdm/lightdm.conf.d directory? [06:33] Deleting the ~/.dmrc file sometimes causes the next boot to autologin correctly. But I couldn't get it to be fixed permanently. [06:35] I have the lightdm.conf file. I also have the directory, but it seems to be empty. [06:35] Try opening the lightdm.conf file with nano or whatever. [06:35] (You'll need to open it as root, e.g. sudo nano /etc/lightdm/lightdm.conf) [06:35] [Seat:*] [06:35] autologin-guest=false [06:35] autologin-user=build [06:35] autologin-user-timeout=0 [06:36] (build is the correct username) [06:36] So you already did this. [06:36] The autologin-user thing? Yeah. [06:37] Maybe the timeout field should be removed, or possibly set to -1? [06:38] (Sometimes 0 means "instant" and -1 means "indefinite".) [06:38] (I don't know if it will act that way here, but it might.) [06:38] I have also been able to reproduce on a fresh install of xubuntu using the "login automatically" option in the installer, on this hardware. Hmm, how do I show what graphics kernel module I am using? (To check if I am running into the Intel race condition in that bug you linked to me.) [06:39] If your system has an Intel CPU and no discrete graphics card, then it's almost certainly using the i915 driver. [06:39] `lspci -k` should show you what drivers are used for what hardware. [06:39] (For at least some hardware in the system.) [06:39] Ok, yeah, it's a small form factor corporate machine with an intel CPU. So highly likely. [06:40] Yup, i915 [06:41] Bah. I don't have a Xubuntu ISO on my system at the moment for testing. [06:42] Hmm, so the bug is "Confirmed" and 10 years old. I guess there's zero chance of anyone bothering to fix this anytime soon...? [06:43] Probably more like "almost no one else can reproduce the bug so it's impossible to fix". [06:43] Oh wow. My Internet is horribly slow, I won't be able to test things locally to see how to work around the bug. [06:43] Yeah, you might try Lubuntu and see if it gives you better results. I have yet to hear of Lubuntu's autologin failing to work. [06:44] Ok, I'll give it a try. By finding that bug, you've at least saved me a few days of bashing my head against a wall :) Thanks so much. [06:46] Glad to at least try to help! :) === alloy is now known as Iron_Chef [17:23] hi, I'minstalling xubuntu right now and I'm wondering about the button "skip" ... what does it skip? [19:31] Hi [19:31] I am installing Xubuntu, the last version [19:31] I am installing it in a pendrive [19:33] I want to use windows when I don't insert my pendrive in my computer [19:33] I hope I can do the boot correctly [19:34] I did the partition in my pendrive whit the root partition with a default setting [19:34] and an ESI or something called like that because it was reiquiered [19:35] I hope everything will be okay [19:35] any suggestions or opinions? [19:35] thank you === xu-irc55w is now known as Bob_Munkatars === hasley is now known as mahler [22:40] what are these loop2 loop18 disks when you do sudo fdisk -l [22:53] porquilho, they're artifacts of installed snaps, it's how the squashfs that holds the snap gets mounted. [22:53] thanks [22:53] im going to delet eit [22:53] den [22:54] porquilho, "lsblk" will show you which loop is connected to which snap [22:54] porquilho, in general you should just ignore them [22:55] https://i.imgur.com/RTJ4rHc.png [22:55] is this normal [22:55] gtk? [22:55] i have xubuntu i dont need gtk [22:56] what is gtk [23:01] porquilho, gtk is a graphic toolkit used by many apps, mainly GNOME related but some apps running on Xubuntu would use them. firefox may need them, I forget how to display dependencies... [23:01] its okay [23:01] thank yoiu [23:03] porquilho, it's "snap connections | grep firefox" and indeed firefox depends on gtk-common-themes and gnome-3-38 [23:04] ill check then [23:04] https://i.imgur.com/hPPCc7a.png [23:05] rfm: