Porteus-v5.0x86_64_bugs reports
- wread
- Module Guard
- Posts: 1255
- Joined: 09 Jan 2011, 18:48
- Distribution: Porteus v5.0-kde-64 bits
- Location: Santo Domingo
- Contact:
Porteus-v5.0x86_64_bugs reports
Hi all!
I always run Porteus KDE as root and in Always Fresh mode. Instead of a changes folder I make separate "myXXX.xzm" files and put them in a subfolder "Settings" in modules. To start Porteus, I select Always Fresh <enter> and in about 1 minute I am online. If I mess anything, rebooting solves it!
Of course, the regular versions of Porteus fail to respond to that procedure; they weren't thought to work so. Then the first change i make is to /boot/syslinux/porteus.cfg; there I add "login=root" to the APPEND line of the "Always Fresh"menu. Then try to start Porteus -> It doesn´t work! But this is still not a bug...
Then I try to force start in AF root mode: start up in text and login as root; switch to X by typing xinit; Porteus responds with a red prompt...Then moving the X cursor to the upper left corner and typing "startx", the desktop should come to life..hurra! If it doesn´t, there is a bug!
To automate the startup as described in the third sentence of the first paragraph, I must extract 003-kde5.xzm (in my case) in base and go there to file /etc/rc.d/rc4. This file is small but very complex! It should collect information from the initial selection screen and proceed accordingly!
I changed the two lines following "#Start KDE desktop" as follows:
# Start KDE desktop:
login=`egrep -o " login=[^ ]+*" /proc/cmdline | cut -d= -f2`
nologin=`grep -o "^nologin" /proc/cmdline`
I only changed the file to scan to /proc/cmdline an deleted a spurios "^" that was in the first line ("^login= -> " login=)....
After rebuilding the module, starting Porteus in AF as root got as expected.
The next addition I did was adding login sound to my Porteus 5.0. but that and other twists, I will describe later in another post.
Enjoy
I always run Porteus KDE as root and in Always Fresh mode. Instead of a changes folder I make separate "myXXX.xzm" files and put them in a subfolder "Settings" in modules. To start Porteus, I select Always Fresh <enter> and in about 1 minute I am online. If I mess anything, rebooting solves it!
Of course, the regular versions of Porteus fail to respond to that procedure; they weren't thought to work so. Then the first change i make is to /boot/syslinux/porteus.cfg; there I add "login=root" to the APPEND line of the "Always Fresh"menu. Then try to start Porteus -> It doesn´t work! But this is still not a bug...
Then I try to force start in AF root mode: start up in text and login as root; switch to X by typing xinit; Porteus responds with a red prompt...Then moving the X cursor to the upper left corner and typing "startx", the desktop should come to life..hurra! If it doesn´t, there is a bug!
To automate the startup as described in the third sentence of the first paragraph, I must extract 003-kde5.xzm (in my case) in base and go there to file /etc/rc.d/rc4. This file is small but very complex! It should collect information from the initial selection screen and proceed accordingly!
I changed the two lines following "#Start KDE desktop" as follows:
# Start KDE desktop:
login=`egrep -o " login=[^ ]+*" /proc/cmdline | cut -d= -f2`
nologin=`grep -o "^nologin" /proc/cmdline`
I only changed the file to scan to /proc/cmdline an deleted a spurios "^" that was in the first line ("^login= -> " login=)....
After rebuilding the module, starting Porteus in AF as root got as expected.
The next addition I did was adding login sound to my Porteus 5.0. but that and other twists, I will describe later in another post.
Enjoy
Last edited by wread on 17 Jul 2022, 14:54, edited 1 time in total.
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!
The Porteus Community never sleeps!
Porteus-v5.0x86_64_bugs reports
Hi all,
Supplement to #45 in this thread
if you open 2 files one after the other with mousepad, the first window disappears.
This error also occurs when both files are in the same folder.
I use Porteus 5.0 Xfce
Supplement to #45 in this thread
if you open 2 files one after the other with mousepad, the first window disappears.
This error also occurs when both files are in the same folder.
I use Porteus 5.0 Xfce
- ncmprhnsbl
- DEV Team
- Posts: 3938
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-v5.0x86_64_bugs reports
actually, the thing changed that mattered was the cut delineator : from 'n' to '='
as far as i can see, mousepad opens files in a new tab in the same window, not a new window.
yup, thanks,
typo.. see /usr/local/bin/pmod line 13: "search-file" should be "file-search"
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
Porteus-v5.0x86_64_bugs reports
Yes, this is probably beating a dead horse but-- Kulle, if you want the other behavior in Mousepad, click:ncmprhnsbl wrote: ↑18 Jul 2022, 00:04as far as i can see, mousepad opens files in a new tab in the same window, not a new window.
Edit -> Preferences -> Window
then at the bottom, change the dropdown for "Open files in" from "new tabs" to "new windows".
(And of course make sure you are saving changes in Porteus to keep as your new default.)
Porteus-v5.0x86_64_bugs reports
Language setup
All files (de-core_locales.xzm, de-devel_locales.xzm, de-xfce4_locales.xzm, de_DE-locales-files.xzm) are in the modules folder.
But the right-click menus
"Create luncher, Create URL Link, ... Applications "
"Create Folder, Create Document, ... Properties"
remain completely in English
All files (de-core_locales.xzm, de-devel_locales.xzm, de-xfce4_locales.xzm, de_DE-locales-files.xzm) are in the modules folder.
But the right-click menus
"Create luncher, Create URL Link, ... Applications "
"Create Folder, Create Document, ... Properties"
remain completely in English
Porteus-v5.0x86_64_bugs reports
Language files (German)
I have now found:
When I use the language files from dl.porteus.org
http://dl.porteus.org/x86_64/Porteus-v5.0/language/
everything stays in English.
However, when I use the Porteus 4.0 language files (in Porteus 5.0 !!)
almost everything is in German.
I am therefore in Porteus 5.0 now using the language files from 4.0
I have now found:
When I use the language files from dl.porteus.org
http://dl.porteus.org/x86_64/Porteus-v5.0/language/
everything stays in English.
However, when I use the Porteus 4.0 language files (in Porteus 5.0 !!)
almost everything is in German.
I am therefore in Porteus 5.0 now using the language files from 4.0
Porteus-v5.0x86_64_bugs reports
Noticeable size difference:
in 4.0 de-xfce4_locales.xzm 2,8 MiB
in 5.0 de-xfce4_locales.xzm 204 kiB
in 4.0 de-xfce4_locales.xzm 2,8 MiB
in 5.0 de-xfce4_locales.xzm 204 kiB
-
- Full of knowledge
- Posts: 2070
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Porteus-v5.0x86_64_bugs reports
@ Kulle
Yep, it does not work automatically. (modules in module folder)
What works - until it get fixed - is:
log out and select de_DE at the bottom of the log in screen
or better, in rootcopy create /var/lib/lxdm/lxdm.conf with following content:
Let us know if it works for you.
Yep, it does not work automatically. (modules in module folder)
What works - until it get fixed - is:
log out and select de_DE at the bottom of the log in screen
or better, in rootcopy create /var/lib/lxdm/lxdm.conf with following content:
Code: Select all
[base]
last_session=__default__
last_lang=de_DE.UTF-8
last_langs=de_DE.UTF-8
- ncmprhnsbl
- DEV Team
- Posts: 3938
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-v5.0x86_64_bugs reports
should have glibc-i18n-2.33-x86_64-5.xzm too, i believe...
but yes, the problem was in de_DE-locales-files.xzm, because the script was incorrectly linking to some non-existing files in a non-existing directory.
should be fixed now on the server..
@Kulle, you can fix it yourself by (as root) extracting de_DE-locales-files.xzm, deleting the usr directory and rebuilding the module.
assuming you're talking about the 32bit version (since i'd say the above problem is 64bit only) and that's(lxdm) a whole other issue that could perhaps be handled in the script too..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
Porteus-v5.0x86_64_bugs reports
Thank you ncmprhnsbl,
the glibc-i18n-2.33-x86_64-5.xzm file exists.
But this size difference:
in 4.0 de-xfce4_locales.xzm 2.8 MiB
in 5.0 de-xfce4_locales.xzm 204 kiB
In 5.0 de-xfce4_locales.xzm is only 204 kiB ??
the glibc-i18n-2.33-x86_64-5.xzm file exists.
But this size difference:
in 4.0 de-xfce4_locales.xzm 2.8 MiB
in 5.0 de-xfce4_locales.xzm 204 kiB
In 5.0 de-xfce4_locales.xzm is only 204 kiB ??
-
- Full of knowledge
- Posts: 2070
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Porteus-v5.0x86_64_bugs reports
nope, both versions.ncmprhnsbl wrote: ↑21 Jul 2022, 08:27assuming you're talking about the 32bit version (since i'd say the above problem is 64bit only) and that's(lxdm) a whole other issue that could perhaps be handled in the script too..
I started with what I had - 32bit - core and xfce language module from i586 folder
put into the modules folder > reboot, modules are loaded but language didn't change.
Log out guest > at the bottom-panel at the (green) login screen click language > more
and there it was, de_DE, login guest and language had changed to german.
I had my doubts that it could be different in a 64bit version so I wiped the usb-drive
and replaced the 32bit with a 64bit version.
Now using the language module from the x86_64 download folder and it was exatly the same.
Language did not change at start-up, logout select language login worked and also the path
to the lxdm.conf is the same.
btw, I only used the core and xfce language modules.
- ncmprhnsbl
- DEV Team
- Posts: 3938
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-v5.0x86_64_bugs reports
ah, this is the key point.. the language-setup tool also generates a third module(de_DE-locales-files.xzm) which contains /etc/profile.d/lang.sh , which sets the LANG environment variable system wide, like so:
Code: Select all
#!/bin/bash
# File generated by Porteus Language-Selection tool
#export LC_ALL=$LNG.utf8
export LANG=$LNG.utf8
export LC_COLLATE=C
i guess lxdm has some influence like this on a session level..
what the glibc-i18n-2.33-x86_64-5.xzm does exactly, i'm not sure... something not obvious at a gui level, i guess..
a combination of things moved to the 002* xzms(like gtk3 etc) , terminfo, and localized man files not included and some inclusions in the 4.0 module (gcc.mo?) that i don't know why or how they got there..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
-
- Full of knowledge
- Posts: 2070
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Porteus-v5.0x86_64_bugs reports
@ ncmprhnsbl
Thanks!
Good to know which file needs to be changed without a tool doing its "black magic".
Thanks!
Good to know which file needs to be changed without a tool doing its "black magic".
-
- Black ninja
- Posts: 88
- Joined: 01 Mar 2013, 19:16
- Distribution: Porteus 3.2 32 bit XFCE
- Location: Duisburg, Germany
Porteus-v5.0x86_64_bugs reports
Hi folks,
Virtualbox crashes just after startwindow ops up. I have used the vb 6.1.34 from the mirrors as well as downloaded with VB Builder (and dev module and crippled sources module activated). When I start from the console I get:
Virtualbox crashes just after startwindow ops up. I have used the vb 6.1.34 from the mirrors as well as downloaded with VB Builder (and dev module and crippled sources module activated). When I start from the console I get:
Code: Select all
(process:1545): GLib-GObject-WARNING **: 09:23:03.868: cannot register existing type 'NMAgentManagerError'
(process:1545): GLib-CRITICAL **: 09:23:03.868: g_once_init_leave: assertion 'result != 0' failed
(process:1545): GLib-GObject-WARNING **: 09:23:03.868: cannot retrieve class for invalid (unclassed) type '<invalid>'
Speicherzugriffsfehler (that means Memory acces error)
- AcnapyxoB
- Samurai
- Posts: 191
- Joined: 24 Dec 2014, 10:15
- Distribution: Porteus 5.01
- Location: Planet Earth
Porteus-v5.0x86_64_bugs reports
Use the last one v6.1.36: https://download.virtualbox.org/virtual ... _amd64.run
old one (VirtualBox 6.1.34) does not support kernel 5.18.8
it might be useful for you also: viewtopic.php?p=83715#p83715
Porteus v5.01 KDE x86_64