Porteus

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.

I noticed that the 4.0 ISOs in http://dl.porteus.org/x86_64/testing/Porteus-v4.0rc1/ are labeled "rc1".
For as far as I am aware beta and rc releases are for public testing, but one will not get much testing without announcing them ... I was aware of the alpha (?) ISOs of some months ago, but I missed the beta ones.
Anyway, some preliminary testing the ISOs under VirtualBox showed one bigish problem: autologin results in a black screen. One has to boot in text mode, login and issue "startx" to get a fully functional X session.
Other than that my only complaint thus far is that the very nice Porteus Browser Tool is only available in the Cinnamon version. Any reason why it is not available in the other versions?
Kind regards, Dick

Anyway, some preliminary testing the ISOs under VirtualBox showed one bigish problem: autologin results in a black screen. One has to boot in text mode, login and issue "startx" to get a fully functional X session.
Other than that my only complaint thus far is that the very nice Porteus Browser Tool is only available in the Cinnamon version.

And now you see why there hasn't been a public announcement. That combined with brokenman and others being on vacation till January.

Here my research on Porteus-4.0-cinnamon:
First I moved NetworkManager to 002-xorg. It is not culprit of NM. Jay was right!

Then I moved 003-cinnamon to "optional" and started Porteus in text mode. Xorg seems to be ok. Activated 003-cinnamon and started it under X and there came the clue: by activating cinnamon you get various warnings indicating paths that should not start with /desktop, /system, etc. etc..

The wrong files are located at /usr/share/GConf/gsettings in 003-cinnamon. These files are read at activation time by /usr/bin/glib-compile-schemas to build caches at /usr/share/glib-2.0/schemas, resulting in wrong caches that lead to the black screen at start.

As I am not a Cinnamon expert, I do not know how to correct the wrong files to avoid the warnings at activation. The author of the module (fulalas?) will know better how to do it!

I hope this will resolve the issue

Regards!

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 wrong files are located at /usr/share/GConf/gsettings in 003-cinnamon. These files are read at activation time by /usr/bin/glib-compile-schemas to build caches at /usr/share/glib-2.0/schemas, resulting in wrong caches that lead to the black screen at start.

I don't think this is the culprit either. I confirm the blank screen but only in virtualbox. In vurtualbox if you boot into text mode and run startx it works ok. I would like some help with this bug.

EDIT: Added quotations

How do i become super user?
Wear your underpants on the outside and put on a cape.

The wrong files are located at /usr/share/GConf/gsettings in 003-cinnamon. These files are read at activation time by /usr/bin/glib-compile-schemas to build caches at /usr/share/glib-2.0/schemas, resulting in wrong caches that lead to the black screen at start.
I don't think this is the culprit either. I confirm the blank screen but only in virtualbox. In vurtualbox if you boot into text mode and run startx it works ok. I would like some help with this bug.

Could this be Mate problem to or something like it?

I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

The wrong files are located at /usr/share/GConf/gsettings in 003-cinnamon. These files are read at activation time by /usr/bin/glib-compile-schemas to build caches at /usr/share/glib-2.0/schemas, resulting in wrong caches that lead to the black screen at start.

Not sure I follow. Could you please elaborate on this please? If there are wrong caches, why is it that with wireless on a marvel chipset (that I have) not having this problem?

The only way to stop the black screen is this, I have to use this ISO porteus-4.0-x86_64-20171120.iso any thing after that I get the black screen. I still say it is in module 001 or 002 but what test I did I am 99% sure it is in 001 module if I remember.

I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

It seems File roller (The archive manager in cinnamon) can unpack ISOs. Ed_P, could you explain please? The link for your reference is here: viewtopic.php?t=7342&start=15 Thanks.
BTW, raja, if you still think file roller is ineffective in unpacking ISOs I would be happy to add isomaster. We decided not to do so in our debug channel.

Yes, also noted by Ed_P. The problem is because of Adwaita theme. This is the reason why Evo Vertex theme (proposed by Blaze) has also been included in cinnamon (change to this theme and you will not have this problem). By rc2, I will raise the question again as to which theme should be the default one.

You may love to eliminate all those useless 'cinnamon warning messages' during shutdown.

Yes, and maybe it would please you to be aware that fulalas and I have discussed and actually removed a lot of these warnings on all desktops. By the way, these warnings are not coming during shutdown. Press Ctrl-Alt-F1 and you will see that they are already there. It is just that when you shutdown, these warning messages are shown, as the gui and the system shuts down.
Also, if you see some GTK warnings, these are because linux mint (and hence cinnamon) are still on the old LTS ubuntu and hence on an older gtk3, while slackware current is already on the latest gtk3. When ubuntu and hence linux mint (and hence cinnamon) jumps to the next LTS this April, they wouls also be on the latest (and final) gtk3, whch might eliminate more warnings regarding gtk3.

It seems File roller (The archive manager in cinnamon) can unpack ISOs. Ed_P, could you explain please? The link for your reference is here: viewtopic.php?t=7342&start=15 Thanks.

From my limited experience it seems the archive manager supports Adding files to the ISO and Extracting files from the ISO but it does not support deleting files from the ISO. Whether adding a file with the same name as one in the ISO would replace the file in the ISO I didn't try. I have updated Porteus ISOs in the past using ISOMaster.

Yes, also noted by Ed_P. The problem is because of Adwaita theme. This is the reason why Evo Vertex theme (proposed by Blaze) has also been included in cinnamon (change to this theme and you will not have this problem). By rc2, I will raise the question again as to which theme should be the default one.

One that supports rename. The current one doesn't. Not crazy about the Evo ones.

I was updating my kde5 last week end and got also a black screen....
Culprit was a duplicated version of icu4c's, 56 and 60 in 001-core and 002-xorg. It took me 3 evenings to solve the problem...I will take a look at cinnamons case again..

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!

I use changes module built here. OS, too saves a "psc settings.xzm" during shut down. This particular module (loopx in memory) introduces a "reiserfs" error message, Kernel warning. Boot message clean, after removing this psc settings module. May be 'file system' creation is not perfect and kernel conducts a reiserfsck?