Porteus 3.0 final feedback

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
Ed_P
Contributor
Contributor
Posts: 3066
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.0 final feedback

Post#136 by Ed_P » 08 May 2014, 20:49

tome wrote:Looks like very invasive troll. :lol: Nothing works :o
I know. :cry:
Try Always Fresh Mode, update usm, relaunch usm, update databases, relaunch usm -> should work :good: .
But.... what happens when I then reboot with my save.dat file? Do note that I boot from an ISO not an install.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3066
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.0 final feedback

Post#137 by Ed_P » 08 May 2014, 20:55

fanthom wrote: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.
Ed

tome
Contributor
Contributor
Posts: 561
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: Porteus 3.0 final feedback

Post#138 by tome » 08 May 2014, 21:24

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.

User avatar
Ed_P
Contributor
Contributor
Posts: 3066
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.0 final feedback

Post#139 by Ed_P » 08 May 2014, 23:01

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.
Ed

tome
Contributor
Contributor
Posts: 561
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: Porteus 3.0 final feedback

Post#140 by tome » 08 May 2014, 23:18

and works it in always fresh mode?

User avatar
Ed_P
Contributor
Contributor
Posts: 3066
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.0 final feedback

Post#141 by Ed_P » 08 May 2014, 23:49

tome wrote: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.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus 3.0 final feedback

Post#142 by brokenman » 09 May 2014, 00:29

/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.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Philip
Black ninja
Black ninja
Posts: 62
Joined: 28 Dec 2013, 15:21
Distribution: Porteus 3.2.2 XFCE, Openbox
Location: England

Re: Porteus 3.0 final feedback

Post#143 by Philip » 11 May 2014, 14:35

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.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus 3.0 final feedback

Post#144 by Rava » 11 May 2014, 20:07

brokenman wrote: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...
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus 3.0 final feedback

Post#145 by brokenman » 11 May 2014, 21:58

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.
How do i become super user?
Wear your underpants on the outside and put on a cape.

worktowork
White ninja
White ninja
Posts: 13
Joined: 06 May 2014, 10:08
Distribution: MX14RC
Location: Russia

Re: Porteus 3.0 final feedback

Post#146 by worktowork » 12 May 2014, 18:19

Dear Brokenman ,
I want to use porteus 3.0 in my PC , I checked hash - true
my open topic 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.

User avatar
wread
Module Guard
Module Guard
Posts: 1062
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus 3.0 final feedback

Post#147 by wread » 12 May 2014, 19:36

@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)
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!

User avatar
Obosan
Samurai
Samurai
Posts: 113
Joined: 28 Mar 2014, 17:02
Distribution: Porteus xfce 32BIT v3.0
Location: JAPAN

Re: Porteus 3.0 final feedback

Post#148 by Obosan » 12 May 2014, 22:42

worktowork wrote: 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. :Yahoo!:
Now I am writing this post from Porteus KDE v3.0 i486. I hope this solves your problem.

worktowork
White ninja
White ninja
Posts: 13
Joined: 06 May 2014, 10:08
Distribution: MX14RC
Location: Russia

Re: Porteus 3.0 final feedback

Post#149 by worktowork » 13 May 2014, 18:32

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.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4548
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus 3.0 final feedback

Post#150 by fanthom » 13 May 2014, 19:55

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.
Please add [Solved] to your thread title if the solution was found.

Post Reply