X doesn't start properly after NoblePup32 rebuild [CLOSED]

[peebee]

CLOSED - thanks @norgo

Just done a rebuild of a new version (NoblePup32) which was working OK - but after the rebuild X doesn't start properly - I get a frozen desktop at the wrong dimensions....

I need some advice on how to diagnose problem - i.e. if I boot with nox what terminal commands should I issue to get error reports?

The list of updated items since the working version is below - can anybody see anything that might affect module loading or X startup??

-rw-r--r-- 1 root root 81004 Feb 15 12:32 libatkmm-1.6-1v5_2.28.4-1_i386.deb
-rw-r--r-- 1 root root 33986 Feb 15 12:32 libatkmm-1.6-dev_2.28.4-1_i386.deb
-rw-r--r-- 1 root root 15460 Feb 15 12:32 libcap-ng0_0.8.4-2_i386.deb
-rw-r--r-- 1 root root 91546 Feb 15 12:32 libgc1_8.2.6-1_i386.deb
-rw-r--r-- 1 root root 9824 Feb 15 12:32 libkeyutils1_1.6.3-3_i386.deb
-rw-r--r-- 1 root root 48582 Feb 15 12:32 libkeyutils-dev_1.6.3-3_i386.deb
-rw-r--r-- 1 root root 19534 Feb 15 12:32 python3-cap-ng_0.8.4-2_i386.deb
-rw-r--r-- 1 root root 88040 Feb 15 12:30 liburi-perl_5.27-1_all.deb
-rw-r--r-- 1 root root 45982 Feb 15 12:30 python3-idna_3.6-2_all.deb
-rw-r--r-- 1 root root 394156 Feb 15 04:35 iptables_1.8.10-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 24398 Feb 15 04:35 libip4tc2_1.8.10-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 6454 Feb 15 04:35 libip4tc-dev_1.8.10-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 25000 Feb 15 04:35 libip6tc2_1.8.10-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 5758 Feb 15 04:35 libip6tc-dev_1.8.10-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 38364 Feb 15 04:35 libxtables12_1.8.10-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 104372 Feb 14 18:39 libuv1_1.46.0-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 146466 Feb 14 18:39 libuv1-dev_1.46.0-3ubuntu1_i386.deb
-rw-r--r-- 1 root root 34914 Feb 13 14:28 gsettings-desktop-schemas_46_beta-1ubuntu1_all.deb
-rw-r--r-- 1 root root 2240184 Feb 8 08:25 libpython3.11_3.11.8-1_i386.deb
-rw-r--r-- 1 root root 5354616 Feb 8 08:25 libpython3.11-dev_3.11.8-1_i386.deb
-rw-r--r-- 1 root root 839752 Feb 8 08:25 libpython3.11-minimal_3.11.8-1_i386.deb
-rw-r--r-- 1 root root 1930502 Feb 8 08:25 libpython3.11-stdlib_3.11.8-1_i386.deb
-rw-r--r-- 1 root root 589228 Feb 8 08:25 python3.11_3.11.8-1_i386.deb
-rw-r--r-- 1 root root 507340 Feb 8 08:25 python3.11-dev_3.11.8-1_i386.deb
-rw-r--r-- 1 root root 2282574 Feb 8 08:25 python3.11-minimal_3.11.8-1_i386.deb
-rw-r--r-- 1 root root 49584 Feb 8 05:44 libapparmor1_4.0.0_alpha4-0ubuntu1_i386.deb
-rw-r--r-- 1 root root 105600 Feb 7 21:14 libsemanage2_3.5-1build2_i386.deb
-rw-r--r-- 1 root root 159378 Feb 7 12:37 ca-certificates_20240203_all.deb
-rw-r--r-- 1 root root 52834 Feb 7 03:04 libseccomp2_2.5.5-1ubuntu1_i386.deb
-rw-r--r-- 1 root root 95496 Feb 7 03:04 libseccomp-dev_2.5.5-1ubuntu1_i386.deb

[ozsouth]

@peebee - maybe this .deb? Can you revert it?
-rw-r--r-- 1 root root 34914 Feb 13 14:28 gsettings-desktop-schemas_46beta-1ubuntu1_all.deb

And for a terminal command, maybe: ldd /usr/libexec/Xorg

[peebee]

Thanks for the suggestions @ozsouth

gsettings-desktop-schemas reverted with a ydrv - no different.....

checkdeps -system
shows that build has no missing dependencies

The screen "flashes" during boot suggest to me that possibly drivers are being loaded and segfaulting but with no usable desktop I can't confirm.

Will have to see if I can put some diagnostics into root/Startup to capture dmesg info......

[user1234]

Are you running this directly on your hardware, or is it QEMU that you use?

FYI, I was asking this because, with QEMU, the commands I used to run Jammy64 were unusable with Fossa64.

But, I don't think that might be the issue since earlier without the changes, as you say, the build was working fine for you .

---

Additional notes:
I think libcap-ng might affect Xorg (source: ldd).

See also: https://packages.ubuntu.com/noble/libcap2 and https://packages.ubuntu.com/noble/libcap-ng0.

[Clarity]

Hi @peebee
Would boot parm loglevel=7 provide more and useful information of what is occurring in INIT at boot time?

Not sure if it will give the info you would want, but maybe...

If your test PC(s) are like mine, namely old, QEMU will mimic what is seen on bare-metal ... in all of my cases.
As you know I boot WoofCE PUPs via their ISO file in both a VM as well as via SG2D. All expected PUP operations works as expectedly; the exact same as would a frugal.

Hope this helps somehow.

[peebee]

Thanks All for suggestions....

A smidgen of evidence.......

If I boot nox lsmod shows radically different loaded modules comparing the previous (working) build with the new build.

Also if I then do:
modprobe nouveau
xwin

then a desktop of the correct resolution appear - but still very frozen

So which of the changed packages affects module loading??

Attached - lsmod from the 2 builds and dmesg from the new build.

[dimkr]

It will be easier for others to help if you provide an ISO that reproduces the problem.

[bigpup]

Maybe this one:
libcap-ng0_0.8.4-2_i386.deb

Libcap implements the user-space interfaces to the POSIX 1003.1e capabilities available in Linux kernels. These capabilities are a partitioning of the all powerful root privilege into a set of distinct privileges.

[bigpup]

There are a few listed packages, in first post, that do not have i386 in their name.

Maybe one or all of them is the cause

[BologneChe]

I did a Frugal installation on an Acer Spin 1. I did not detect this type of problem. I installed it with the available ISO.

[peebee]

It will be easier for others to help if you provide an ISO that reproduces the problem.

Delta uploaded

Apply
https://sourceforge.net/projects/zestyp ... a/download

to
https://sourceforge.net/projects/zestyp ... o/download

to create: 1f09fff6fd7331fa5e8c04cbae7b3108 NoblePup32-24.04+A1.iso

I tried reverting libcap-ng0 via ydrv and it made no difference.

The all.deb packages are architecture independent. All packages are i386 valid.

I am testing on real hardware with nvidia graphics - hence test with modprobe nouveau.

[Keef]

Just tried a manual frugal install to my Dell M4600 with NVDIA Quadro 1000M.
Booted to desktop, but frozen - not able to use mouse. Although I could alter the screen brightness with the Fn + arrow keys, nothing desktop related worked.
Quick Setup dialogue shows correct resolution (1920x1080) but says vesa module loaded. Unable to exit X, had to hit the power button and reboot.

Also booted with nox, then did modprobe nouveau, xwin. Nouveau loaded ok, but desktop still frozen as before.

[bugnaw333]

I also tried in my Fujitsu Futro MA574 laptop on USB stick, After X...line cursor blinks then gone--frozen black screen.

[BologneChe]

I tested the latest proposal under Virtualbox and my Acer Spin 1 laptop. It starts well and everything is functional.

[norgo]

@peebee
the reason is udev

used package version
libgudev-1.0-0_238-3_i386.deb
udev_255.2-3ubuntu2_i386.deb

created a symlink /sbin/udevd -> /usr/bin/udevadm

Now needed kernel modules becomes loaded automatically again and system is working fine

[peebee]

@peebee
the reason is udev

used package version
libgudev-1.0-0_238-3_i386.deb
udev_255.2-3ubuntu2_i386.deb

created a symlink /sbin/udevd -> /usr/bin/udevadm

Now needed kernel modules becomes loaded automatically again and system is working fine

Excellent - many thanks

[peebee]

CLOSED

574cfad6631800edacd62ab0bee4c046 NoblePup32-24.04+A1.iso

as delta to +A0