xorg x server crash on reboot after quick-remaster BookwormDog

a very small Live CD shaped to look and act like Puppy Linux.

Moderator: fredx181

Post Reply
User avatar
mouldy
Posts: 437
Joined: Tue Dec 08, 2020 3:53 pm
Has thanked: 26 times
Been thanked: 109 times

xorg x server crash on reboot after quick-remaster BookwormDog

Post by mouldy »

Dang curiosity... Anyway somebody on another thread in off topic section kept asking for an "iso" of dog with waydroid so I tried that quick-remaster. Ok remaster completed and yes there was an iso produced, and also quick-remaster modified the original. And yes I saved the original changes folder before running quick-remaster, so not a biggie to restore. However, when I try to boot the remastered version, either modified original or from the iso in ventoy, it mostly boots only to fail with x server crash? I dont need the iso myself and personally would just zip the changes folder to "install" it on another computer, as that would be lot easier... but kinda curious if it was a failure of quick-remaster or if its cause waydroid files confused it or what. Waydroid added lot size, but the iso came out around 1.8GB which really isnt that bad considering those android img files. Any hack so it can finish booting? Or way to stop this from happening if I remastered it again? As say, not super important and not spending much time on it since I can easily just delete the modified version and put it back like it was. Here is the log:

[ 31.087]
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[ 31.087] Current Operating System: Linux live 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64
[ 31.087] Kernel command line: BOOT_IMAGE=/live/vmlinuz1 from=/ noauto changes=/changes
[ 31.087] xorg-server 2:21.1.7-3+deb12u5 (https://www.debian.org/support)
[ 31.087] Current version of pixman: 0.42.2
[ 31.087] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 31.087] Markers: (--) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 31.088] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 13 00:17:30 2024
[ 31.093] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 31.110] (==) No Layout section. Using the first Screen section.
[ 31.110] (==) No screen section available. Using defaults.
[ 31.110] (
) |-->Screen "Default Screen Section" (0)
[ 31.110] (**) | |-->Monitor "<default monitor>"
[ 31.111] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 31.111] (==) Automatically adding devices
[ 31.111] (==) Automatically enabling devices
[ 31.111] (==) Automatically adding GPU devices
[ 31.111] (==) Automatically binding GPU devices
[ 31.111] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 31.113] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[ 31.113] Entry deleted from font path.
[ 31.113] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 31.113] Entry deleted from font path.
[ 31.113] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 31.113] Entry deleted from font path.
[ 31.113] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 31.113] Entry deleted from font path.
[ 31.114] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 31.114] Entry deleted from font path.
[ 31.114] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 31.114] Entry deleted from font path.
[ 31.114] (==) FontPath set to:
/usr/share/fonts/X11/Type1,
built-ins
[ 31.114] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 31.114] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 31.114] (II) Loader magic: 0x55d8e01c5f00
[ 31.114] (II) Module ABI versions:
[ 31.114] X.Org ANSI C Emulation: 0.4
[ 31.114] X.Org Video Driver: 25.2
[ 31.114] X.Org XInput driver : 24.4
[ 31.114] X.Org Server Extension : 10.0
[ 31.118] (++) using VT number 1

[ 31.127] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[ 31.132] (--) PCI:*(0@0:2:0) 8086:22b1:103c:82bd rev 53, Mem @ 0x90000000/16777216, 0x80000000/268435456, I/O @ 0x00001000/64, BIOS @ 0x????????/131072
[ 31.132] (II) LoadModule: "glx"
[ 31.134] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 31.198] (II) Module glx: vendor="X.Org Foundation"
[ 31.198] compiled for 1.21.1.7, module version = 1.0.0
[ 31.198] ABI class: X.Org Server Extension, version 10.0
[ 31.198] (==) Matched modesetting as autoconfigured driver 0
[ 31.198] (==) Matched fbdev as autoconfigured driver 1
[ 31.198] (==) Matched vesa as autoconfigured driver 2
[ 31.198] (==) Assigned the driver to the xf86ConfigLayout
[ 31.198] (II) LoadModule: "modesetting"
[ 31.199] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 31.199] (II) Module modesetting: vendor="X.Org Foundation"
[ 31.200] compiled for 1.21.1.7, module version = 1.21.1
[ 31.200] Module class: X.Org Video Driver
[ 31.200] ABI class: X.Org Video Driver, version 25.2
[ 31.200] (II) LoadModule: "fbdev"
[ 31.200] (WW) Warning, couldn't open module fbdev
[ 31.200] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 31.200] (II) LoadModule: "vesa"
[ 31.201] (WW) Warning, couldn't open module vesa
[ 31.201] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 31.201] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 31.201] (EE) open /dev/dri/card0: No such file or directory
[ 31.201] (WW) Falling back to old probe method for modesetting
[ 31.201] (EE) open /dev/dri/card0: No such file or directory
[ 31.201] (EE) Screen 0 deleted because of no matching config section.
[ 31.201] (II) UnloadModule: "modesetting"
[ 31.201] (EE) Device(s) detected, but none match those in the config file.
[ 31.201] (EE)
Fatal server error:
[ 31.201] (EE) no screens found(EE)
[ 31.202] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 31.202] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 31.202] (EE)
[ 31.207] (EE) Server terminated with error (1). Closing log file.

User avatar
rockedge
Site Admin
Posts: 5711
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 1990 times
Been thanked: 2097 times
Contact:

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by rockedge »

looks like a Xorg configuration file is not set up correctly or is missing.......

not 100% sure but seems to be what the log is saying :ugeek:

User avatar
mouldy
Posts: 437
Joined: Tue Dec 08, 2020 3:53 pm
Has thanked: 26 times
Been thanked: 109 times

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by mouldy »

So can I just swap in an old configuration file from outside the system? Was it something I did or didnt do with the remastering script? Cause the original install was fine, this is only after the quick-remaster script did its thing. Is this script known to work ok with Bookworm Dog? Until it got to the x server part of booting, it was booting ok.

User avatar
fredx181
Posts: 2560
Joined: Tue Dec 03, 2019 1:49 pm
Location: holland
Has thanked: 273 times
Been thanked: 992 times
Contact:

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by fredx181 »

@mouldy
I'l test remastering today or tomorrow to see if I can reproduce, get back later.

User avatar
rockedge
Site Admin
Posts: 5711
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 1990 times
Been thanked: 2097 times
Contact:

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by rockedge »

I have done many remasters that would include a ready to go Zoneminder system and many builds failed to work correctly until I realized that there are files that are very necessary for the web server and mysql components to function correctly were not being copied over to the new file system during the remaster process!

There are files that are in in /etc /root./config and /root/.local and possibly other locations that must be manually transferred to the new file system. Depending on the remaster program you are using there will be differences on how well the remaster scripts grabs the entire current system's components.

User avatar
mouldy
Posts: 437
Joined: Tue Dec 08, 2020 3:53 pm
Has thanked: 26 times
Been thanked: 109 times

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by mouldy »

fredx181 wrote: Wed Mar 13, 2024 4:31 pm

@mouldy
I'l test remastering today or tomorrow to see if I can reproduce, get back later.

Not any high priority, just curious. Figured if it were doing this to me twice in a row, probably something in the script. But it could be all the waydroid baggage too. Guess I can experiment with lighter version of BookwormDog without waydroid, maybe with just couple small added programs. See what it does. That would tell me if its the script or the added weight of waydroid.

User avatar
fredx181
Posts: 2560
Joined: Tue Dec 03, 2019 1:49 pm
Location: holland
Has thanked: 273 times
Been thanked: 992 times
Contact:

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by fredx181 »

@mouldy
Sorry to say, I couldn't reproduce the problem you got (edit: btw /etc/X11/Xorg.conf is NOT included by default).
Made a remaster including waydroid with quick-remaster and it works ok for me.
Made from a minimal JWM + systemd build, ISO :
File: DDog-custom.iso (1.9 GB) (I'll leave it for a week or so on my Google-Drive)
Download: https://drive.google.com/uc?export=down ... UlFPtd6ABe
Please test (works ok at my end, but doesn't guarantee it works on all computers), must say that it's not perfect "sharable" e.g. didn't bother (well.. forgot ;) ) to remove some custom settings I made , e.g. resolution setting, timezone, wifi conf etc..
Why remastering didn't work well for you may have many causes, difficult to determine, anyway it may be important to stop waydroid session before remastering (I did that), but just guessing, don't know really.
The quick remaster script has never let me down during the years, even with many many stuff included, btw, just a few days ago I've upgraded the package in custom bookworm repo (to v1.4.0) with the change that created ISO has UEFI and GRUB2 support (so also should work booting ISO from Ventoy).

User avatar
mouldy
Posts: 437
Joined: Tue Dec 08, 2020 3:53 pm
Has thanked: 26 times
Been thanked: 109 times

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by mouldy »

I downloaded your iso. And just to make it interesting burned it to dvd rather than thumbdrive or frugal hard drive install. So on my upstairs desktop computer, I booted it, created "changes" folder on hard drive, and rebooted to use it. Ok started waydroid, obviously little slow from dvd, but got to desktop. And the android browser loaded. Only thing that was off, android didnt see my fat32 thumb drive though the live dvd dog did. But hey if you had told me I could do waydroid from a live dvd, would thought you were crazy. The isos I have seen with waydroid included stressed that one had to INSTALL the iso distribution to hard drive to use it. Obviously you dont. Though you do need a read-write save file.

And you beat me to the punch and then some. I tried the quick-remaster on simple BookwormDog with just few changes to let me know it had upgraded. And that worked, no problem booting it. Now think I need to try the remaster on my waydroid install again, might workout better here on desktop than on the laptop. Will see.

User avatar
rockedge
Site Admin
Posts: 5711
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 1990 times
Been thanked: 2097 times
Contact:

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by rockedge »

Should turn off all servers before and during the remaster build process. Prevents cache's and .sock files from being present while assembling the remaster.

User avatar
mouldy
Posts: 437
Joined: Tue Dec 08, 2020 3:53 pm
Has thanked: 26 times
Been thanked: 109 times

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by mouldy »

Ok, apparently makes a difference on computer used. I just tried remaster again. It succeeded this time. So I have not only waydroid but houdini and the Kindle app all rolled into one iso. Yep and it works pretty well booted off a usb SSD. I am impressed. Way BookwormDog works combines well with waydroid. Still not sure why remaster works on my old I5 desktop but not the laptops. But boy once that remastering started, processor use went to 100% and stayed there until it started writing the iso. Cooling fan kicked into high speed. And it says the iso is 1734M, thats with maximum compression. I think how many isos are that much just with a browser and Libre Office and maybe VLC. It even kept my tiny script to start easytether. Oh and looks like the Firefox addons too. I think about this if I were making a public release iso probably want to make sure any personal settings or whatever were gone before I started.

Darn wish I had included RHVoice and Librera. LOL

User avatar
fredx181
Posts: 2560
Joined: Tue Dec 03, 2019 1:49 pm
Location: holland
Has thanked: 273 times
Been thanked: 992 times
Contact:

Re: xorg x server crash on reboot after quick-remaster BookwormDog

Post by fredx181 »

mouldy wrote:

Though you do need a read-write save file

If quick remaster used from newest package (v1.4), the ISO can be used from Ventoy (direct ISO boot, grub.cfg) the grub.cfg has example entry with changes=/deb_dog so if you have "deb_dog" folder (create if not) on a Linux partition it should work for saving (but I only tested this with UEFI boot).
DVD boot may be different (maybe uses isolinux, not sure).
EDIT: quick remaster does some cleaning (e.g. removing cache files) but for the most it includes exactly what's in "/" (but with exceptions, such as e.g. /mnt/* or /proc/* /sys/* etc ...), so yes, for public sharing you need to clean things up manually first (e.g. remove ~/.mozilla or ....)

Post Reply

Return to “DebianDogs”