Porteus 3.0 final feedback

[Ed_P]

i think it could be due do Ed_Ps save.dat being full. maybe some files could not be copied and went as whiteouts?
just guessing as i never worked with full container.

Hey, I thought you were on holiday.

Thanks for checking this. I agree with your conclusion.

[tome]

But.... what happens when I then reboot with my save.dat file?

Remove directories (symlinks) from your save.dat file:
/etc/usm
/var/usm
/tmp/usm

reboot (use save.dat) for changes and update usm, relaunch usm, update databases, relaunch usm.
If it does't work I don't know what is wrong with your save.dat or with usm.

Do note that I boot from an ISO not an install.

It doesn't matter.

[Ed_P]

Didn't work.

I booted Always Fresh, mlooped the save.dat file, renamed the /etc/usm and /var/usm folders, safer than deleting IMO, there was no /tmp/usm folder, ulooped the file and rebooted with the changes=EXIT cheatcode. usm still doesn't work.

[tome]

and works it in always fresh mode?

[Ed_P]

and works it in always fresh mode?

A valid question. And yes it does.

Clicking on the taskbar USM link brings up a Porteus password window asking for the ROOT password.
I then get a Message window saying Missing database files.
On the USM window I click on Updates then the Update USM option and am told I have the current version.
I click on the Help link and see that I have 3.1.0 version. Not 3.1.1.
I eventually get a Message window saying that "An update is available for the usm database files. Please run: update all"

At this point I stopped.

[brokenman]

/etc/usm/usm.conf: No such file or directory
/share/usm/funcelementCreate: No such file or directory

This usm.conf file is part of the package you downloaded. The last line of this file sets the $PREFIX variable (/usr) which means the next block of paths are incorrect.
I tend to agree that whiteout files are at play here. Please try installing the slackware package instead of converting it to a module. Do this in always fresh mode first to test. This will ensure that the file is installed and not mounted.

[Philip]

LXDE and XFCE versions.

All is OK when run on a USB flash disk formatted to FAT32.

But I find that when the disk is formatted to ext2, 3 or 4, the lxdm-binary is using near 100% CPU. Also there is no auto log-in, and you can only log-in as root. Attempting to log in as guest with a ext2,3 or 4 formatted disk always returns you to the log-in screen.

[Rava]

Rava ... I will have to boot into xfce, install 3.1.0 and go from there. I have no doubt you know what you are doing and the problem lies in v3.1.0.
Regarding the temp dir /tmp/usm.XXXXX .... it only exists while the program is running. Once the program exits the directory is removed (you probably already knew that).

Yeah, I knew that.... but why is it deleting its temp dir when it's still running?

And, did you test it already? Could you manage to reciprocate some of my listed errors? Like the inability to update the salix database, or after manual updating all others, still not able to download fbreader: the same old error than before...


_____________________________

Aaand a new issue/bug:
I started into XFCe 3.0 x86-64 version (always fresh, but with some changes saved in a module), but into text console only, did some work there, and without starting X via startx, I suspended the machine via pm-suspend; but after restarting from suspend, all virtual consoles have been black...
usually, I log into tty6 as non root user and startx from that console... and I was logged into non root user on that VT already, so switching blindly into tty6 and typing blindly "startx[enter]" I was able to start X / startup XFCe, but the virtual consoles still are dead: when I switch to these the monitor goes into "Power saving Mode".
Also, typing blindly "reset" in one of the VTs is doing nothing, it keeps dead.

Is there anything that can be done that this won't happen in the future? Cause that means, when someone needs a rescue minimal Porteus without any X for some reason, this someone is screwed when running it and wanting to suspend and work on after suspend...

[brokenman]

but why is it deleting its temp dir when it's still running?

I don't know. I can not reproduce it. The only time this folder is deleted is in a 'cleanup' function which is only called when the user exits the script, or the script exits gracefully.

And, did you test it already? Could you manage to reciprocate some of my listed errors?

Yes. I tested it thoroughly before release. No I can not reproduce ANY of your errors from the latest version 3.1.1. The files download without error for me. This makes it hard to trouble shoot.

[worktowork]

Dear Brokenman ,
I want to use porteus 3.0 in my PC , I checked hash - true
my open topic http://forum.porteus.org/viewtopic.php?f=81&t=3438
please give solution
X -configure - fatal server error and another which I can not remember.
I have to tried from iso , unpack and boot and solution gives from another people - I can not boot and load.

[wread]

@fanthom
As I tried to compile the plasma-applet-screensaverswitch without success, I was forced to hack until I found the reason: a bug in 05-devel led to a wrong version of a library (libkdefakes.so).

The bug is from upstream, it is also on aliens cmake txz module...at least I tried installing it and the compiler said no!

I corrected my module 05-devel and the file compiled ok.

I also made this patch for those of you who might encounter such an obstacle.

Cheers 8)

[Obosan]

X -configure - fatal server error and another which I can not remember.

Try to edit /etc/X11/xorg.conf.
At Section "Device", change the driver to vesa by having
Driver "vesa"
in your file.
I just googled ["fatal server error" solved] to get this info.
Update
I was on the way to make Porteus KDE USB stick and encountered the following error.

# X -configure
Fatal server error:
(EE) Server is already active for display0.
If this server is no longer running, remove /tmp/.X0-lock and start again.

I did "rm /tmp/.X0-lock" and did "X -configure" again. It works.
Now I am writing this post from Porteus KDE v3.0 i486. I hope this solves your problem.

[worktowork]

I have xorg-vesa and xorg ~~setting(true or not I don`t know ) files , so I don`t know what do. I try to change to

At Section "Device", change the driver to vesa by having
Driver "vesa

in the file xorg~~setting
X -configure give known fatal server error
I must leave project porteus.

[fanthom]

please do as follows:
a) login to text mode as root
b) run:

Code: Select all

cp -a /etc/X11/xorg.conf-vesa /etc/X11/xorg.conf

c) run 'startx' and you should be in GUI (using unaccelerated VESA driver but it's better than nothing)

please let me know if that works and i'll tell you how to make this configuration persistent.

[Rava]

but why is it deleting its temp dir when it's still running?
I don't know. I can not reproduce it. The only time this folder is deleted is in a 'cleanup' function which is only called when the user exits the script, or the script exits gracefully.

And, did you test it already? Could you manage to reciprocate some of my listed errors?
Yes. I tested it thoroughly before release. No I can not reproduce ANY of your errors from the latest version 3.1.1. The files download without error for me. This makes it hard to trouble shoot.

I could run a vanilla Porteus 3.0 without any changes and look if it behaves, or misbehaves again...

I also could put in some debug info with the use of echo in the script itself and see what it does, and when it does delete the temp dir and such...