[SOLVED] X is Borked

business_kid · 03-21-2024, 09:25 AM

As it says, my X setup seems nicely borked. I had executed some scripts in /etc/X11/xinit. I was looking at installing Mate instead of XFCE. That screwed things.

Now I run 'startx' from runlevel 3 and I get a blue screen with one grey icop in top left & top right corners and this error

Quote:

Unable to determine failsafe session name. Possible causes: xfconfd not running; XDG_CONF_DIRS is set incorrectly (must include /etc); or xfce4-session is intalled incorrctly.

I checked and

$XDG_CONF_DIRS is not set.
xfconfd is not running and exits immediately anyhow. Running 'startx & /well/hidden/path/to/xfconfd' also fails.

I deserve this because I had been holding on to stuff in /etc/X11 for years simply to keep the look & feel of XFCE that I was used to, so I know better than to try and fix this, so a clean install of current is coming, I want Mate, DEFINITELY not KDE, and not XFCE.

What's my kosher way of doing that? Do I vaguely remember some script? Has anyone tried it? I can afford to, because I have a working backup to get me back to where I was recently. Otherwise, with the standard iso, if I leave out kde & XFCE, and put Mate there instead, does it work?

kgha · 03-21-2024, 10:56 AM

kosher-schmosher... my favourite install method is to grab Eric's liveslak ( in this case the mate variety) and then run setup2hd

From Eric's wiki:

Quote:

The “setup2hd” script has some capabilities that the original Slackware 'setup' lacks:

It will launch fdisk/gdisk if you forgot to create Linux partitions in advance;
It will allow you to create a regular user account and set its password;
It will prompt you to set the root password in a graphical dialog.

If you've tweaked the liveslak (e.g. added Multilib), those changes will also be part of the install.

That's how I've done it in the past, and I consider it failsafe.

business_kid · 03-21-2024, 11:32 AM

Brilliant. Thanks for the reply.

Updating my homedir backup at the moment. I'm impressed with these LiveSlak USBs. I was on the Cinnamon one this morning and even got Libreoffice printing in short order. I'll choose carefully what to restore. I see my homedir has sprouted an fvwm directory, for instance.

No doubt I'll manage to make an adventure of it but I have the backup.

garpu · 03-21-2024, 12:32 PM

When I installed current on this box, I used Eric's liveslak, and it was completely no-drama.

(If another testimonial is needed.) he's got it set up to use ventoy now, too.

jayjwa · 03-21-2024, 01:20 PM

I wouldn't go with the nuclear option just because (it seems) like XFCE isn't behaving. There's alot of fixes if you search for that error message, most have to do with starting under dbus-launch xfce4-session. Probably some start-up script is wrong.

business_kid · 03-22-2024, 05:30 AM

I'm pretty sure nothing major is wrong, but finding what variables are jammy side down promises to be a nightmare, given that I've been copying over/etc/X11/* for some years into each new install. That will include /etc/X11/xinit/. I have a complete backup, and I'm going to be very fussy that only needed data goes back into the homedir. As it was, I couldn't set runlevel 4, but just ran startx from runlevel 3.

If I don't like it, I can just go back to earlier days. I even have a more historical backup.

business_kid · 03-22-2024, 10:40 AM

Well, I ran the setup2hd script, copied over the packages very nicely, and left me in the lurch in the final setup. Probably my mistake, but I know how to do that stuff anyhow and I did it. So I'm on a new 64bit ext4 filoesystem for /, the 6.6.10-huge kernel, no initrd, and runlevel 3.

It boots fine, but can't mount / because of errors. It asks me to enter the root passwd. But without / mounted, it can't check a passwd. I did try 'root' and no passwd. root was rejected, and no passwd was a reboot command. So I booted on the live usb to fix it. There was no errors! I checked all partitions, and only /home had minor errors.

Is there a root passwd hardcoded into busybox in the ramdisk? What is it? I'll go back and try making a ramdisk and using the generic kernel. But I shouldn't have to - that's the whole point of the huge kernel, isn't it?

EDIT: Made the ramdisk and booted it. It still gives me this root disk error on a new / filesystem. I even booted debian and tried the e2fsck there. No joy.

Windu · 03-22-2024, 11:20 AM

Can you finally please please please be actually specific when you state things like "left me in the lurch in the final setup", "I know how to do that stuff anyhow and I did it" "because of errors" and all the other similarly vague remarks you made over time.
There is nothing in your posts that would actually entice me to hand you something relevant. I would love to help, but not like this.

Petri Kaukasoina · 03-22-2024, 12:15 PM

Quote:

Originally Posted by business_kid

It boots fine, but can't mount / because of errors. It asks me to enter the root passwd. But without / mounted, it can't check a passwd. I did try 'root' and no passwd. root was rejected, and no passwd was a reboot command.

Is this what you got:

Code:

***********************************************************
*** An error occurred during the root filesystem check. ***
*** You will now be given a chance to log into the      ***
*** system in single-user mode to fix the problem.      ***
***                                                     ***
*** If you are using the ext2 filesystem, running       ***
*** 'e2fsck -v -y <partition>' might help.              ***
***********************************************************

Once you exit the single-user shell, the system will reboot.

Type control-d to proceed with normal startup,
(or give root password for system maintenance):

If you got that, '/' was mounted, because the text above is printed by /etc/rc.d/rc.S. It will check the root password against /etc/shadow. Then you can run e2fsck as hinted.

Quote:

Originally Posted by business_kid

try making a ramdisk and using the generic kernel. But I shouldn't have to - that's the whole point of the huge kernel, isn't it?

Even the generic kernel has ext4 built-in in -current now, so usually you don't need huge nor initrd with generic.

Quote:

Originally Posted by kgha

From Eric's wiki:

Quote:

The “setup2hd” script has some capabilities that the original Slackware 'setup' lacks:

It will launch fdisk/gdisk if you forgot to create Linux partitions in advance;
It will allow you to create a regular user account and set its password;
It will prompt you to set the root password in a graphical dialog.

Use that root password.

Quote:

Originally Posted by business_kid

left me in the lurch in the final setup. Probably my mistake, but I know how to do that stuff anyhow and I did it

So, did you set the root password?

business_kid · 03-22-2024, 01:36 PM

Yes, what you showed was the error message I got. Let's be clear, the / partition is fine. I have checked everything, mounted all filesystems, checked all filesystems, and done my best to trap all errors going through. That involved half a dozen reboots. Here's what happens.

/ is mounted read only and /sbin/init is run.
I catch a glimpse of an error, but can't get all of it, because it's followed by kind of 40 lines so fast that I can't follow it up the screen. I have managed to see "Failed to insert...............................................: Format error."
The boot messages say /sbin/e2fsck won't run because it's a directory . It's an executable, but something thinks it's a directory. As I just had (at a guess) a module loading error, I suppose they're related.
An error about / is raised, presumably because the fsck routine exited with an error code.

I didn't get to the end of setup2hd, but was dumped out. Using the live usb, I mounted the future directory tree and chrooted into it, I set up the root passwd before I posted, so obviously I had exited setup2hd before that point. Now I got in, and could progress. I ran 'init 3' and it finished and brought me to a login. Because I remounted / rw and ran 'init 3' it ran rc.M and I got some logs. dmesg was useless. Here's /var/log/syslog in it's entirety:

Code:

Mar 22 17:41:10 darkstar kernel: Speculative Return Stack Overflow: IBPB-extending microcode not applied!
Mar 22 17:41:10 darkstar kernel: Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
Mar 22 17:41:15 darkstar kernel: hid_bpf: error while preloading HID BPF dispatcher: -22
Mar 22 17:41:15 darkstar kernel: Invalid ELF header magic: != \x7fELF
Mar 22 17:41:18 darkstar kernel: usb 3-2.1: Warning! Unlikely big volume range (=5120), cval->res is probably wrong.
Mar 22 17:41:18 darkstar kernel: usb 3-2.1: [5] FU [Mic Capture Volume] ch = 1, val = 7680/12800/1
Mar 22 17:44:11 darkstar elogind-daemon[1370]: Failed to connect to system bus: No such file or directory
Mar 22 17:44:11 darkstar elogind-daemon[1370]: Failed to fully start up daemon: No such file or directory

/var/log/messages was pretty useless also. But the bit that pukes came before this logging.

So now I'll download the latest live iso and run some selective updates, particularly kernel and modules.

Petri Kaukasoina · 03-22-2024, 01:59 PM

Quote:

Originally Posted by business_kid

"Failed to insert...............................................: Format error.#

/sbin/e2fsck won't run because it's a directory

. It's an executable, but something thinks it's a directory. As I just had (at a guess) a module loading error, I suppose they're related.

Code:

Mar 22 17:41:15 darkstar kernel: Invalid ELF header magic: != \x7fELF

All the ELF binaries, libraries, kernel modules should start with \x7fELF. What does smartctl tell about the health of the disk? Or memtest about the memory?

business_kid · 03-23-2024, 04:59 AM

It's not the disk, to my mind. This stuff is less than 2 years old and not stressed. I checked the disk as a matter of form. What does happen is that the usb disk fills it's read or write cache and never thinks to stop and sync itself. At that point, programs are capable of doing funny things. That's my guess. I've been sitting with a terminal open running sync during setups. But I didn't get a chance to interrupt the sxz archives to nvme transfer.

Anyhow, current has moved on. The upgrade will be Sata --> nvme, which I will do in sections and I reckon that will work. It will also give me a different kernel

business_kid · 03-23-2024, 11:55 AM

I'm marking this solved

.

I'm online, & three quarters sorted. The "/sbin/e2fsck is a directory" error proved to be missing files in /etc. Perfectly obvious once you think about it - NOT! It's madness, actually.

You know, after an install, there's a trialsome routine of setting up basic config files. Well, I had wiped / clean, and setup2hd had turfed me out with skid marks on my backside, so those basic files in /etc/ were never set up. So I got back in, ran init 3, and selectively copied over one file at a time - /etc/fstab, /etc/hosts, and other configs I has set up to my liking, and knew to be unpolluted by earlier versions.

Now I'm starting in runlevel 4. It starts the last window manager I had, and I can select Mate, XFCE, or some half-assed spartan thing. They coloured the background, threw in a disgusting terminal, and called it a window manager. It has the hallmarks of an alcoholic CS student blown out by his girl friend. I hadn't seen that option of choosing desktops before. I could have been locking myself out of it by copying over /etc/X11.

Mate is set up to look much the way I had XFCE set up previously. The only thing I lack in Mate is a keyboard shortcut to switch between the 4 screens or windows. XFCE used to do it with Ctrl_F1-F4. What does Mate use?

Current is from this week, Mate is from last month. To do is: installing from Alien Bob's repo; the task of setting up look 'n' feel stuff in Mate's Labyrinthine menus; Building or installing Slackbuilds.

kgha · 03-23-2024, 12:55 PM

OK, so the sddm display manager (the login screen) is driving you nuts. You can get rid of The virtual keyboard:
edit line 24 in /etc/sddm.conf so that it reads
InputMethod=
and nothing else.

If you prefer the old xdm login screen, comment out the sddm lines (lines 43-44) in /etc/rc.d/rc.4

For window switching, look for the menu item Keyboard Shortcuts or run
mate-keybinding-properties
from terminal.

business_kid · 03-23-2024, 01:34 PM

Sorry I was unclear.

Window maker is the half-assed window manager I was bellyaching about. I'll tolerate the login screen for the moment, but mark that spot you mentioned with a comment. I think I know how to get rid of Window maker.

Experience teaches me to stop fixing something at the earliest opportunity, and keep your work reversible where possible. SDDM, is it? I hadn't run that before.

Thanks for the mate tuition. Those keybinding properties are definitely future work. I'd rather leave them as they are and learn them than have to fart about every time I upgrade. I'll configure Mate at my leisure.