Problem with the 002-xorg module since last update

Technical issues/questions of an intermediate or advanced nature.
itrukrakso
Black ninja
Black ninja
Posts: 62
Joined: 23 Jul 2022, 07:42
Distribution: Porteus 5.01_x86_64 Xfce

Problem with the 002-xorg module since last update

Post#1 by itrukrakso » 22 May 2023, 09:42

Hi,

on 2023-05-04 the modules 001-core and 002-xorg were updated.
With the 001-core module my Porteus 5 works, but when I update the 002-xorg there are problems:
on the screen appears only the cursor, but no icons and no xfce-panel.
As far as I can see the packages in the new and old module are identical.
With the old module i mean the version from 2023-02-18
Can someone tell me what has been changed in the new 002-xorg module?

Thanks

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Problem with the 002-xorg module since last update

Post#2 by beny » 22 May 2023, 10:25

in console write xfwm4 enter,if you have a clean desktop without icon and toolbar..

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Problem with the 002-xorg module since last update

Post#3 by Ed_P » 22 May 2023, 14:38

itrukrakso wrote:
22 May 2023, 09:42
Can someone tell me what has been changed in the new 002-xorg module?
I would be nice if this could be updated when updates are loaded: Porteus-v5.0 updates (Post by ncmprhnsbl #93139)
Ed

itrukrakso
Black ninja
Black ninja
Posts: 62
Joined: 23 Jul 2022, 07:42
Distribution: Porteus 5.01_x86_64 Xfce

Problem with the 002-xorg module since last update

Post#4 by itrukrakso » 22 May 2023, 15:19

Hi,
Ed_P wrote:I would be nice if this could be updated when updates are loaded: Porteus-v5.0 updates (Post by ncmprhnsbl #93139)
exactly, that's what I meant
Thanks Ed_P

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Problem with the 002-xorg module since last update

Post#5 by Ed_P » 22 May 2023, 15:56

BTW I have the two 230430 updates and am having no problems with my Cinnamon system.
Ed

itrukrakso
Black ninja
Black ninja
Posts: 62
Joined: 23 Jul 2022, 07:42
Distribution: Porteus 5.01_x86_64 Xfce

Problem with the 002-xorg module since last update

Post#6 by itrukrakso » 22 May 2023, 16:33

Hi,

That's quite possible. I'm running xfce4 4.18.
After the updates, the xorg server starts and also initializes a screen 0:0.
Only the window manager and the panel are not started.
When I start them in the terminal, they run, but without accepting the default settings.
Overall not a big problem for me. If I can't find a solution, this update isn't for me.

itrukrakso
Black ninja
Black ninja
Posts: 62
Joined: 23 Jul 2022, 07:42
Distribution: Porteus 5.01_x86_64 Xfce

Problem with the 002-xorg module since last update

Post#7 by itrukrakso » 23 May 2023, 12:40

Hi,
the cause of my problem is the modified file:
/opt/porteus-scripts/xorg/update-cache
2 lines were added:
[ -n $(find $MOD -name "*.so" | tail -n1) ] && touch $CACHES/ldconfig
.
.
[ -e $CACHES/ldconfig ] && ldconfig &

I have commented out these lines, and so i can use the update.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Problem with the 002-xorg module since last update

Post#8 by Ed_P » 23 May 2023, 15:08

I'm impressed with your persistence and debugging skills itrukrakso. :o :)

Try uncommenting the last line to see if it's the culprit.
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Problem with the 002-xorg module since last update

Post#9 by ncmprhnsbl » 26 May 2023, 08:02

itrukrakso wrote:
23 May 2023, 12:40
the cause of my problem is the modified file:
/opt/porteus-scripts/xorg/update-cache
2 lines were added:
[ -n $(find $MOD -name "*.so" | tail -n1) ] && touch $CACHES/ldconfig
.
.
[ -e $CACHES/ldconfig ] && ldconfig &

I have commented out these lines, and so i can use the update.
considering that the scripting (by me) is so bad that it's quite likely that it does nothing at all :p.. and if it did what it's supposed to, i can't really see how running ldconfig could result in what you were experiencing..
my apologies for not announcing the update, i've been busy. it's basically security package updates from slackware patches and a couple of minor script changes..
if you want to try debugging this further, could you try putting this in your boot line: (either via TAB at boot or on your APPEND line)

Code: Select all

cliexec=ldconfig
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

itrukrakso
Black ninja
Black ninja
Posts: 62
Joined: 23 Jul 2022, 07:42
Distribution: Porteus 5.01_x86_64 Xfce

Problem with the 002-xorg module since last update

Post#10 by itrukrakso » 02 Jun 2023, 06:54

Hi,
Thanks ncmprhnsbl
I don't think that ldconfig is the reason, for me ldconfig runs like in Slackware in the rc.M.
[ -n $(find $MOD -name "*.so" | tail -n1) ] && touch $CACHES/ldconfig
The find command takes too long because my porteus system is 1.7G in size.
If I add a delay of 10s in the rc.S after the call of the script, it's ok.
@ncmprhnsbl:
One question: where to start find the search for any libs
and what should $MOD be, a path?

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Problem with the 002-xorg module since last update

Post#11 by ncmprhnsbl » 03 Jun 2023, 02:55

itrukrakso wrote:
02 Jun 2023, 06:54
The find command takes too long because my porteus system is 1.7G in size.
yeah, my thought too, afterwards..
itrukrakso wrote:
02 Jun 2023, 06:54
and what should $MOD be, a path?
and this is the why the find line is broken and takes too long, because of where i put it in the script, $MOD is undefined.. so anything mounted would be searched too i guess..
the proper place should be in the following loop command, like so:
/opt/porteus/scripts/xorg/update-cache

Code: Select all

#!/bin/sh
# Script called by rc.S to update various system cache's
# if additional xzm modules were added to the union.

if [ "$1" = rc.S ]; then
	echo "[1m""Additional xzm modules have been found - updating system caches ...""[0m"
else
	echo "[1m""Updating system caches ...""[0m"
fi

# Arch specific variables:
[ `uname -m` = x86_64 ] && lib=lib64 || lib=lib

CACHES=/mnt/live/tmp/caches
mkdir -p $CACHES

if [ $lib = lib64 ]; then
	for y in `ls /mnt/live/memory/images | grep -v "^00"`; do
		MOD=/mnt/live/memory/images/$y
		[ -n $(find $MOD -name "*.so" | tail -n1) ] && touch $CACHES/ldconfig
		[ -e $MOD/usr/share/applications ] && touch $CACHES/desktop
		[ -e $MOD/usr/share/mime ] && touch $CACHES/mime
		[ -e $MOD/usr/share/fonts ] && touch $CACHES/fonts
		[ -e $MOD/usr/lib64/gtk-2.0/*/immodules ] && touch $CACHES/immodules
		[ -e $MOD/usr/lib64/gtk-3.0/*/immodules ] && touch $CACHES/immodules
		[ -e $MOD/usr/lib64/gdk-pixbuf-*/*/loaders ] && touch $CACHES/pixbuf
		[ -e $MOD/usr/share/glib-2.0/schemas ] && touch $CACHES/schemas
		[ -e $MOD/usr/lib64/gio/modules ] && touch $CACHES/gio
		[ -e $MOD/etc/ssl/certs ] && touch $CACHES/certs
		# Multilib support for x86_64 arch:
		[ -e $MOD/usr/lib/gtk-2.0/*/immodules ] && touch $CACHES/immodules
		[ -e $MOD/usr/lib/gtk-3.0/*/immodules ] && touch $CACHES/immodules
		[ -e $MOD/usr/lib/gdk-pixbuf-*/*/loaders ] && touch $CACHES/pixbuf
	done
else
	for y in `ls /mnt/live/memory/images | grep -v "^00"`; do
		MOD=/mnt/live/memory/images/$y
		[ -n $(find $MOD -name "*.so" | tail -n1) ] && touch $CACHES/ldconfig
		[ -e $MOD/usr/share/applications ] && touch $CACHES/desktop
		[ -e $MOD/usr/share/mime ] && touch $CACHES/mime
		[ -e $MOD/usr/share/fonts ] && touch $CACHES/fonts
		[ -e $MOD/usr/lib/gtk-2.0/*/immodules ] && touch $CACHES/immodules
		[ -e $MOD/usr/lib/gtk-3.0/*/immodules ] && touch $CACHES/immodules
		[ -e $MOD/usr/lib/gdk-pixbuf-*/*/loaders ] && touch $CACHES/pixbuf
		[ -e $MOD/usr/share/glib-2.0/schemas ] && touch $CACHES/schemas
		[ -e $MOD/usr/lib/gio/modules ] && touch $CACHES/gio
		[ -e $MOD/etc/ssl/certs ] && touch $CACHES/certs
	done
fi

[ -e $CACHES/desktop ] && update-desktop-database &
[ -e $CACHES/mime ] && update-mime-database /usr/share/mime &
[ -e $CACHES/fonts ] && fc-cache -f &
[ -e $CACHES/immodules ] && update-gtk-immodules &
[ -e $CACHES/schemas ] && glib-compile-schemas /usr/share/glib-2.0/schemas &
[ -e $CACHES/pixbuf ] && update-gdk-pixbuf-loaders &
[ -e $CACHES/gio ] && gio-querymodules /usr/$lib/gio/modules &
[ -e $CACHES/certs ] && update-ca-certificates --fresh &
[ -e $CACHES/ldconfig ] && ldconfig &

that way, only /mnt/live/memory/images/<non_00*_base_modules> is searched instead of 'everywhere'
so you can edit or replace /opt/porteus/scripts/xorg/update-cache with above, and that should fix the problem and it will fixed in the next update, sooner rather than later..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply