Porteus-v4.0 bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
por01
White ninja
White ninja
Posts: 18
Joined: 19 Apr 2018, 14:17
Distribution: Porteus LXDE 4.0 x86_64

Porteus-v4.0 bug reports

Post#61 by por01 » 03 Jun 2018, 20:53

Porteus LXDE 4.0 64bit

Unfortunately, I experienced some bugs (or problems) found at Porteus LXDE 4.0rc4 64bit version. The same situation in 4.0:

deb2xzm does not work if devel module is mounted at boot time.
deb2xzm from devel module works only in true live (always fresh) mode

Firewall. Serbian Latin keyboard layout. youtube-dl
I do not understand why Porteus' youtube-dl does not work, while youtube-dl downloaded from the youtube-dl site works without problems.

And an other issue: intel-ucode.cpio

For GRUB2, "/boot/syslinux/intel-ucode.cpio,/boot/syslinux/initrd.xz" does not work:

Code: Select all

menuentry 'Porteus LXDE 4.0 64b 20180429 root iuu' {
 set OS=boot/porteus/Porteus-LXDE-v4.0-x86_64
 linux /$OS/boot/syslinux/vmlinuz from=$OS noswap zram=33% \
 login=root
 initrd /$OS/boot/syslinux/intel-ucode.cpio,/$OS/boot/syslinux/initrd.xz
}

Result:

error: file '/boot/porteus/Porteus-LXDE-v4.0-x86_64/boot/syslinux/intel-ucode.cpio,/boot/porteus/Porteus-LXDE-v4.0-x86_64/boot/syslinux/initrd.xz' not found... Kernel panic...

This works:

Code: Select all

menuentry 'Porteus LXDE 4.0 64b 20180429 root iuu' {
 set OS=boot/porteus/Porteus-LXDE-v4.0-x86_64
 linux /$OS/boot/syslinux/vmlinuz from=$OS noswap zram=33% \
 login=root
 initrd /$OS/boot/syslinux/intel-ucode.cpio /$OS/boot/syslinux/initrd.xz
}

Case 1: "initrd /$OS/boot/syslinux/initrd.xz" boot

Code: Select all

# dmesg | grep Spec
[    0.008466] Spectre V2 : Mitigation: Full generic retpoline

# dmesg | grep microcode
[    0.571354] microcode: sig=0x20655, pf=0x10, revision=0x2
[    0.571398] microcode: Microcode Update Driver: v2.2.
Case 2: "initrd /$OS/boot/syslinux/intel-ucode.cpio /$OS/boot/syslinux/initrd.xz" boot

Code: Select all

# dmesg | grep Spec
[    0.008073] Spectre V2 : Mitigation: Full generic retpoline

# dmesg | grep microcode
[    0.000000] microcode: microcode updated early to revision 0x4, date = 2013-06-28
[    0.572922] microcode: sig=0x20655, pf=0x10, revision=0x4
[    0.572984] microcode: Microcode Update Driver: v2.2.
My question: should I use intel-ucode.cpio or not? (It increases the security or not?)

My processor:

Menu > System Tools > Porteus System Info > Machine > Processor

Code: Select all

address sizes	: 36 bits physical, 48 bits virtual
cpu MHz		: 1653.059
cpu MHz		: 2111.142
cpu cores	: 2
cpuid level	: 11
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid popcnt lahf_lm pti dtherm arat
model name	: Intel(R) Pentium(R) CPU        P6200  @ 2.13GHz
vendor_id	: GenuineIntel
Family: Pentium
Signature: Type 0, Family 6, Model 37, Stepping 5
APIC (On-chip APIC hardware supported)
PGE (Page global enable)
ACPI (ACPI supported)
HTT (Multi-threading)
TM (Thermal monitor supported)
External Clock: 533 MHz
Max Speed: 2128 MHz
Last edited by por01 on 04 Jun 2018, 13:15, edited 1 time in total.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1505
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

Porteus-v4.0 bug reports

Post#62 by ncmprhnsbl » 03 Jun 2018, 23:03

por01 wrote:
03 Jun 2018, 20:53
So, what intel-ucode.cpio does?

Code: Select all

#dmesg | grep microcode
to find the revision date..
as far as meltdown/spectre, for a pentium(and any other older intel cpu) probably nothing..
eg. here's my 8? year old i7 :

Code: Select all

#dmesg | grep microcode
[    0.000000] microcode: microcode updated early to revision 0x7, date = 2013-08-20
there definately wasn't any meltdown/spectre mitigations back in 2013..(there might something useful in it, idk what though)
not to worry though, meltdown/spectre is dealt with via kernel and software fixes..
deb2xzm does not work if devel module is mounted at boot time.
deb2xzm requires the package binutils , which was left out(or in devel) to save some space.
if all you want is deb2xzm you can just make a binutils module:

Code: Select all

#getpkg binutils
downloads the binutils package (to /tmp i think)
so

Code: Select all

#cd /tmp
#txz2xzm binutils*
then stick it in modules or optional and activate it when you want it.
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

por01
White ninja
White ninja
Posts: 18
Joined: 19 Apr 2018, 14:17
Distribution: Porteus LXDE 4.0 x86_64

Porteus-v4.0 bug reports

Post#63 by por01 » 03 Jun 2018, 23:50

About deb2xzm: I do not think that the binutils is the problem here. As I wrote, deb2xzm does not work ONLY if the devel module was mounted at boot time, together with the core modules (and this happens if the devel module is placed in modules directory). If I mount it later, deb2xzm works without any problem.

I set Porteus with config scripts executed with cliexec boot option. And one of them does just this job. devel.sh:

Code: Select all

#!/bin/bash

# Edit this variable if needed
mydevel=$(dirname $(realpath $0))/devel/05-devel.xzm

[[ $(mount) = *devel.xzm* ]] && exit 64
[ -f $mydevel ] || exit 65

activate $mydevel

exit 0


User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1505
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

Porteus-v4.0 bug reports

Post#64 by ncmprhnsbl » 04 Jun 2018, 01:48

por01 wrote:
03 Jun 2018, 23:50
As I wrote, deb2xzm does not work ONLY if the devel module was mounted at boot time,
ah, i misread.. that is odd..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

fulalas
DEV Team
DEV Team
Posts: 1124
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Mission, goals and mean: working toward a better porteus

Post#65 by fulalas » 07 Jun 2018, 03:49

@donald, so you mean this. I see. These icon theme issues are really boring to solve. I must confess that I don't have much time to understand and fix something like this. Sorry.

@francois, what you mean exactly? :)

donald
Full of knowledge
Full of knowledge
Posts: 1391
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Mission, goals and mean: working toward a better porteus

Post#66 by donald » 07 Jun 2018, 10:56

:( ...hopefully someone else (brokenman?) will lend a hand to solve these issues.

These panel problems do not exist in Porteus 3.2.2-XFCE.
evidence:
Panel 22px
Image

It's amazing how many regressions are allowed into new builds.

M. Eerie
Samurai
Samurai
Posts: 102
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

Mission, goals and mean: working toward a better porteus

Post#67 by M. Eerie » 07 Jun 2018, 20:43

donald wrote:
02 Jun 2018, 04:50
These inconsistencies are what make the operating system look amateurish.
just my point of view - no offence
Indeed. It's a pity. And I think Porteus (and Linux in general) deserves this. I'm not very skilful but, I've made some progress with ~/.config/gtk.css patching some common diseases... and also trying to bring some good looking menu that goes well whith Qogir (dark) theme.

Paper as main icon theme, is a great addition. I will try to do an icon (both for Nemesis and Porteus) to mitigate the lack of .xzm mimetype. Suggestions for other icons (not too much, I hope) are welcomed. :)

I'm pretty sure that having a sleek look attracts more users. For example, Archlabs is really easy on the eyes.

Cheers.

fulalas
DEV Team
DEV Team
Posts: 1124
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Mission, goals and mean: working toward a better porteus

Post#68 by fulalas » 08 Jun 2018, 03:02

donald wrote:
07 Jun 2018, 10:56
:( ...hopefully someone else (brokenman?) will lend a hand to solve these issues.
You can try to use a different icon pack and see if this solves the problem. Your help is really welcome! :good:
donald wrote:
07 Jun 2018, 10:56
It's amazing how many regressions are allowed into new builds.
And what about all the evolution of so many other things? For instance, Xfce module is now taking just 18 MB (compared to 45 MB of Porteus 3.2.2), although it was updated to latest version. Xfce now has a decent file search integrated to Thunar. The defaults are more friendly, allowing you to drag the open windows on the taskbar, files size are now correctly shown, the main theme are cleaner now, Audacious is integrated to Thunar. Besides that, we updated all the packages, which includes new features (a decent video player) and many bug fixes. And, still, we have a full system that takes less than 300 MB after boot :) Not to remember that now we're offering seven DEs!

The problem with Porteus community (and many other distros) is that we are just a few guys that have just a small fraction of time to work on many things, so we ended focusing our time on the critical stuff, leaving the cosmetics to... who knows? I'm definitely not the guy for this, even in my profession. :unknown:

@M. Eerie, your help is more than welcome! :)

donald
Full of knowledge
Full of knowledge
Posts: 1391
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Mission, goals and mean: working toward a better porteus

Post#69 by donald » 08 Jun 2018, 08:22

Guys,I really appreciate your work on and for Porteus.
fulalas wrote: Xfce module is now taking just 18 MB (compared to 45 MB of Porteus 3.2.2)
I'm just a user and not a developer,
so I don't care about the size of the module.
What is the point of stripping down a module to the bone
if you have to add MB's of stuff afterwards to make it work
like it did before?
fulalas wrote: Not to remember that now we're offering seven DEs!
Well, the only DE I use/love is XFCE, so I would like to see
this one being "perfect" -- the other ones don't count. :)

Besides the mandatory updates a new version should improve the features,
appearance and usability.

I could easily list two or three things that do work in the older version,
but not in the new one.
That's a regression and annoying.

Changes only for the sake of change without real improvement, rather the opposite,
makes no sense.

User avatar
n0ctilucient
Shogun
Shogun
Posts: 407
Joined: 21 Apr 2017, 15:59
Distribution: fullmoonremix
Location: 127.0.0.1
Contact:

Mission, goals and mean: working toward a better porteus

Post#70 by n0ctilucient » 08 Jun 2018, 08:48

What is the point of stripping down a module to the bone
if you have to add MB's of stuff afterwards to make it work
like it did before?
This is so true. TinyCoreOS made it's selling point "tiny"
yet they failed to note "not so tiny" w/ a modern DE.

For me... it's always about a balance of
security... efficiency and performance.

Efficiency usually eliminates the bloat by completely avoiding anything that needs to be stripped.
:hmmm: I do NOT have the "right" to tell anyone what they should do...
but I reserve the "right" to tell them what they should "consider".

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

Mission, goals and mean: working toward a better porteus

Post#71 by Ed_P » 08 Jun 2018, 16:02

donald wrote: Guys,I really appreciate your work on and for Porteus.
Me too. And I wish I knew Linux better so I could help more.

Maybe for XFCE there could be a Lite version and a Plus version. Whether that would be 2 003-XFCE modules or just the one 003-XFCE module with a supporting xzm module with all the functions the 3.2.2 version had I don't know. Whichever is easier to do. But either approach should satisfy the wishes users have.

What modules/files did the 3.2.2 version have included and what modules/files does the 4.0 version have?
Ed

fulalas
DEV Team
DEV Team
Posts: 1124
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Mission, goals and mean: working toward a better porteus

Post#72 by fulalas » 08 Jun 2018, 22:53

@Ed_P, the one million question is: what 3.2.2 does that 4.0 doesn't (except for having decent icons when increasing taskbar size)? :)

User avatar
n0ctilucient
Shogun
Shogun
Posts: 407
Joined: 21 Apr 2017, 15:59
Distribution: fullmoonremix
Location: 127.0.0.1
Contact:

Mission, goals and mean: working toward a better porteus

Post#73 by n0ctilucient » 08 Jun 2018, 23:00

one 003-XFCE module with a supporting xzm module
This sounds perfect. Possibly even a universal support module that can be used w/ all DE's.
(eg... 04-support.xzm)
:hmmm: I do NOT have the "right" to tell anyone what they should do...
but I reserve the "right" to tell them what they should "consider".

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

Mission, goals and mean: working toward a better porteus

Post#74 by Ed_P » 08 Jun 2018, 23:15

fulalas wrote:
08 Jun 2018, 22:53
@Ed_P, the one million question is: what 3.2.2 does that 4.0 doesn't (except for having decent icons when increasing taskbar size)? :)
You have to ask this guy. ;)
donald wrote:
08 Jun 2018, 08:22
I could easily list two or three things that do work in the older version,
but not in the new one.
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1391
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Mission, goals and mean: working toward a better porteus

Post#75 by donald » 09 Jun 2018, 08:42

OK, -- besides the icons/panel disaster -- :)

lets start with the simplyfied "search files/folders" UI.
It is a good example for "changes made for the sake of change"
Search options are lost or one has to do more clicks than before
to access them.
(the old pfilesearch is still there,so if you know how you can revert back)

Other issues - which may not be related solely to the xfce module.
Thunar > context menu > get md5sum = not there
Thunar > right-click a txt file > open as root > expected action =
file opened in (root) mousepad, nope.
If it doesn't work this way,the "open as root" context menu entry
should only be visible for folders,no?

Mousepad in general
> view > color scheme = not working

Text highlighting
Sometimes i get yellow text on the not changeable white background =
not readable without selecting the whole text.
(I would be thankful for a hint how to revert back to the old mousepad behavior.)

Removed utilities:
gcolor2
Iso master

It seems not possible to play/watch movie DVDs with MPV.
i found no way to convince MPV to use the libdvdcss.
- no problem in 3.2.2 (gnome-mplayer) -

MPV UI (settings) is there any?

btw
/var/log/removed_packages /../removed_scripts
still contains the broadcom files which, if you delete them, will produce unnecessary *.wh files

Post Reply