Page 14 of 16
Porteus-v5.0x86_64_bugs reports
Posted: 17 Nov 2022, 17:08
by Ed_P
Rava wrote: ↑17 Nov 2022, 16:39
and then I ran this:
Code: Select all
root@porteus:~# updatedb
root@porteus:~# echo $?
0
Thanks
Rava.
What module got updated?
Porteus-v5.0x86_64_bugs reports
Posted: 17 Nov 2022, 17:17
by Rava
Ed_P wrote: ↑17 Nov 2022, 17:08
Thanks Rava.
What module got updated?
No module got updated but man is your friend:
man updatedb :
Code: Select all
updatedb(8) System Manager's Manual updatedb(8)
NAME
updatedb - update a database for mlocate
SYNOPSIS
updatedb [OPTION]...
DESCRIPTION
updatedb creates or updates a database used by locate(1). If the data‐
base already exists, its data is reused to avoid rereading directories
that have not changed.
updatedb is usually run daily by cron(8) to update the default data‐
base.
EXIT STATUS
updatedb returns with exit status 0 on success, 1 on error.
When I tried yesterday
on the now crashed system ( see here:
Some tips on getting to the reason for the recent suspend crashes ) it also did report the same successful results, seems by then cron did run updatedb in the background by itself.
Porteus-v5.0x86_64_bugs reports
Posted: 31 Jan 2023, 08:54
by Kulle
Prteus 5.0 Xfce
Strange change of system time/date after "suspend"
look here #32 :
XFCE - The keyboard layout changes automatically
Porteus-v5.0x86_64_bugs reports
Posted: 28 Feb 2023, 14:47
by Ed_P
I don't know what changes went into the Feb 16 Porteus update but they don't work in my Cinnamon system. I boot to a black screen and an xterm window.
I noticed during the booting process something about being unable to create a directory.
Added in 2 hours 38 minutes 42 seconds:
And the directory msg is:
mkdir: can't create directory '/memory/images/001-core.xzm' : File exists -> 001-core.xzm
And a similar msg for 002-xorg.xzm
I'm booting the Porteus 5.0 ISO and I put the 2 update modules in my /Porteus50/Modules directory with the extramod= cheatcode pointing to it. This boot option use to work.
Added in 12 hours 19 minutes 14 seconds:
Interesting.
So I rename the updates as 001-corenu.xzm and 002-xorgnu.xzm, added 001-core.xzm;002-xorg.xzm to my noload= cheatcode, rebooted my ISO, no mkdir errors.
But I end up with the same black screen with the small Xterm window.
Porteus-v5.0x86_64_bugs reports
Posted: 02 Mar 2023, 05:28
by ncmprhnsbl
Ed_P wrote: ↑01 Mar 2023, 05:45
I'm booting the Porteus 5.0 ISO and I put the 2 update modules in my /Porteus50/Modules directory with the extramod= cheatcode pointing to it. This boot option use to work.
question: what's in your "extramod" directory?
what it seems like to me:
as you know, modules from extramod= directory are loaded after modules from base, so, yes "extramod" 001-core with overwrite base/001-core (with some mkdir complaints)
but, if you don't also have 003-cinnamon in extramod directory, the /etc/rc.d/rc.4 file in "extramod" 001-core will overwrite base/003-cinnamon /etc/rc.d/rc.4
which is my guess as to why you're booting to openbox(that's the black screen/xterm that you see) and not cinnamon.
Porteus-v5.0x86_64_bugs reports
Posted: 02 Mar 2023, 06:02
by Ed_P
ncmprhnsbl wrote: ↑02 Mar 2023, 05:28
but, if you don't also have 003-cinnamon in extramod directory, the /etc/rc.d/rc.4 file in "extramod" 001-core will overwrite base/003-cinnamon /etc/rc.d/rc.4
Good guess.
Code: Select all
~# uname -a
Linux porteus.example.net 5.18.8-porteus #1 SMP PREEMPT_DYNAMIC Sat Jul 2 10:05:31 MSK 2022 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
~# cat /etc/porteus/*
001-core.xzm:20230217
002-xorg.xzm:20230217
002-xtra.xzm:20221211
003-cinnamon.xzm:20220925
initrd.xz:20220928
Why does the 001-core have the desktop /etc/rc.d/rc.4 file? Or deletes the one there? Is this new? I don't remember this problem before.
Thank you for your help.
Porteus-v5.0x86_64_bugs reports
Posted: 02 Mar 2023, 07:49
by ncmprhnsbl
Ed_P wrote: ↑02 Mar 2023, 06:02
Why does the 001-core have the desktop /etc/rc.d/rc.4 file? Or deletes the one there? Is this new? I don't remember this problem before.
it's always been there, for the purpose of booting to a very minimal openbox when using no 003-*.xzm at all, perhaps in the case of making your very own 003-DE.xzm
Porteus-v5.0x86_64_bugs reports
Posted: 05 Mar 2023, 23:31
by Ed_P
BTW & FWIW
When ISO booting and putting update modules in an extramod= folder one will see:
Code: Select all
mkdir: can't create directory: '/memory/images/001-core.xzm' : File exists
-> 001-core.xzm
mkdir: can't create directory: '/memory/images/001-xorg.xzm' : File exists
-> 001-xorg.xzm
mkdir: can't create directory: '/memory/images/001-cinnamon.xzm' : File exists
-> 001-cinnamon.xzm
Don't worry, they are not a problem. Once booted when one runs a syssnapshot script they will see the updated modules loaded and are active.
Code: Select all
~# uname -a
Linux porteus.example.net 5.18.8-porteus #1 SMP PREEMPT_DYNAMIC Sat Jul 2 10:05:31 MSK 2022 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
~# cat /etc/porteus/*
001-core.xzm:20230217
002-xorg.xzm:20230217
002-xtra.xzm:20221211
003-cinnamon.xzm:20220925
initrd.xz:20220928
~# ls -l /mnt/live/memory/images
000-kernel.xzm : Jul 2 2022
001-core.xzm : Feb 17 00:24
002-xorg.xzm : Feb 17 00:32
002-xtra.xzm : Dec 11 01:13
003-cinnamon.xzm : Sep 25 01:21
011-slapt-get-0.11.6-x86_64-2gv.xzm : Oct 29 13:51
07-printing-x86_64-2023-02-04.xzm : Feb 4 12:17
Remember when testing 001-core.xzm update modules to include the ISO's 003- desktop file in the extramod= folder.
(thank you
ncmp)
Porteus-v5.0x86_64_bugs reports
Posted: 07 Apr 2023, 05:10
by Ed_P
No wireless device found (Post by roadie #93669)
roadie wrote: ↑06 Apr 2023, 23:14
The reason wireless is not displayed is because of the way the search for the info is done. Using lspci doesn't show "Wireless", rather, it shows "Network".
You can fix this yourself if you're willing to edit the file /opt/porteus-scripts/xpsinfo. As root, open the file in an editor and change lines 229 and 233. Just switch "Wireless" for "Network".
You can backup the original first as root, then edit:
Code: Select all
cd /opt/porteus-scripts
cp xpsinfo xpsinfo.bak
Edit the original, save the changes, and open Porteus System Info and the wireless should be displayed. This bug always bothered me too, but I didn't look into it until you posted.
Porteus-v5.0x86_64_bugs reports
Posted: 15 Apr 2023, 14:45
by Blaze
In Mozilla Firefox 112 am I the only one who is seeing double actions in the browser window?
BTW it's Cinnamon DE.
Porteus-v5.0x86_64_bugs reports
Posted: 15 Apr 2023, 15:06
by AcnapyxoB
Blaze wrote: ↑15 Apr 2023, 14:45
In Mozilla Firefox 112
It started from older versions, I cured it with:
about:config
browser.tabs.inTitlebar=0
Porteus-v5.0x86_64_bugs reports
Posted: 15 Apr 2023, 17:49
by Blaze
Hi
AcnapyxoB.
AcnapyxoB wrote: ↑15 Apr 2023, 15:06
I cured it with:
about:config
browser.tabs.inTitlebar=0
I have this option by default and it does not help me
Thanks
Porteus-v5.0x86_64_bugs reports
Posted: 15 Apr 2023, 18:19
by Ed_P
Firefox 110 in my Cinnamon DE and my browser.tabs.inTitlebar=2.
Do note the - + characters on line 2 of my browser are not the same as the 2 characters above it.
Porteus-v5.0x86_64_bugs reports
Posted: 16 Apr 2023, 05:17
by AcnapyxoB
Blaze wrote: ↑15 Apr 2023, 17:49
I have this option by default and it does not help me
Strange!
https://disk.yandex.com/i/4MBeG3WYrBFtoQ
tested on fresh Cinnamon
Porteus-v5.0x86_64_bugs reports
Posted: 21 Apr 2023, 16:49
by Blaze
Hi
AcnapyxoB.
Yep, it works fine. Thanks.
BTW by default a new version of firefox comes with option
and we have this issue with double tabs in titlebar
it's not good
