Feedback and Bug Reports for Porteus v2.1 RC2

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
francois
Contributor
Contributor
Posts: 5124
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#16 by francois » 10 Jul 2013, 01:02

I am working with the following menu.lst:

Code: Select all

title porteus v2_32 on sda7 /32bit_v21rc2
kernel (hd0,6)/32bit_v21rc2/boot/syslinux/vmlinuz from=/dev/sda7/32bit_v21rc2 changes=EXIT:/32bit_v21rc2/porteus login=root
initrd=(hd0,6)/32bit_v21rc2/boot/syslinux/initrd.xz
boot
Carpe diem.

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

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#17 by brokenman » 10 Jul 2013, 01:26

silasthemic
Please try these things in this order to fix your flash problem:
1) boot with the cheatcode: noload=opera (Just to verify that the problem is not the flash included in opera)
2) Download the nVidia module for your machine (Maybe a video accel problem)
http://ponce.cc/porteus/x86_64/testing/ ... 2/drivers/
3) Give the output of: grep -o "sse2" /proc/cpuinfo|wc -l
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
francois
Contributor
Contributor
Posts: 5124
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#18 by francois » 10 Jul 2013, 02:08

Though, I did not had any clock problem, pbundle functioning here:

Code: Select all

root@porteus:~# pbundle get clock

Would you like to download: clock-crashfix-1.0-i486-1misc.xzm
[y] or [n]
y--2013-07-09 22:07:35--  http://www.porteus.org/mate/clock-crashfix-1.0-i486-1misc.xzm
Resolving www.porteus.org (www.porteus.org)... 198.50.156.88
Connecting to www.porteus.org (www.porteus.org)|198.50.156.88|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 692224 (676K) [text/plain]
Saving to: ‘/mnt/sda7/32bit_v21rc2/porteus/modules/clock-crashfix-1.0-i486-1misc.xzm’

25% [=========>                             ] 178,104      865KB/s             
100%[======================================>] 692,224     1.10MB/s   in 0.6s   

2013-07-09 22:07:35 (1.10 MB/s) - ‘/mnt/sda7/32bit_v21rc2/porteus/modules/clock-crashfix-1.0-i486-1misc.xzm’ saved [692224/692224]

Activate clock-crashfix-1.0-i486-1misc.xzm now?
[y] or [n]

Your modules can be
Carpe diem.

mkarwin
Ronin
Ronin
Posts: 2
Joined: 09 Jul 2013, 14:43
Distribution: P-2.1rc2/#!11/LMDE/Arch/SUSE
Location: Poland

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#19 by mkarwin » 10 Jul 2013, 06:12

brokenman wrote: mkarwin
I will need to reboot into another DE to test because under Mate i can't reproduce this problem with ogg, flac, mp3 or wav. Can anyone else confirm this?
Well I did try the media using a couple of DEs, as mentioned. The stutter is present in guest account, yet root seems to suffer far less, only once in about 20s. Still looking for solution, but tested gmplayer, vlc, deadbeef, audacious to no avail.
Example file/site - http://www.jamendo.com/pl/list/a104054 or http://www.jamendo.com/pl/list/a46306/eftos-early where neither playing on site nor downloaded media works correctly. Will provide further examples if needed. Really low bitrates helped extend downloaded media playback, but on site - whether through Chrome (as reported by others, screen blacks out, sound does not start...) or Firefox (stutter/no sound whatsoever every couple of seconds) from the module directory provided as "for rc2".
hope you can [help me] pinpoint the source of the problem, and repair it ASAP ;) I really like what you did since version 1.2 ;D
Cheers,
m.

Lukas
White ninja
White ninja
Posts: 10
Joined: 11 Jun 2012, 04:17
Location: masovia province

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#20 by Lukas » 10 Jul 2013, 14:27

Could You guys update Firefox to the latest STABLE version that would be available, at the release date of final version of Porteus 2.1? :Rose: I don't know if it would be 22 or 23.
What's the point You ask? - they added OdinMonkey with Asm.js in which I'm particularly interested.

n2prtsusr
White ninja
White ninja
Posts: 14
Joined: 12 Nov 2012, 02:33
Distribution: Porteus 2.1 lxde 130809
Location: us

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#21 by n2prtsusr » 10 Jul 2013, 15:37

Porteus is my primary os
I'm using porteus 2.1rc2 lxde
on a directory right click to build a module - it does not work but gives
message module name was built
so i used lxterminal to create module that worked but showed a gzip error but
module was created
hope this helps

silasthemac
White ninja
White ninja
Posts: 4
Joined: 06 Apr 2013, 01:00
Distribution: 32 bit LXDE usb
Location: portland oregon usa

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#22 by silasthemac » 10 Jul 2013, 16:04

FIXED
my flash problem
google-chrome --disable-accelerated-plugins
flash now does not cause black window
with thanks to Peter:
http://peter.sh/experiments/chromium-co ... -switches/

hope this helps others
thanks,
Silas

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

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#23 by fanthom » 10 Jul 2013, 16:49

@mkarwin
first i thought your issue is hardware related but then you wrote it happens on different PC's as well, yet - nobody else is experiencing it (or not reporting).
i'm puzzled.

please dump a link to full system report and will start from checking what's your soundcard model.

@Lukas
the problem is that Pat stopped upgrading firefox for stable slackware branches and stuck to firefox ESR (extended support) instead which is 17.7 at the moment of writing. you may have to use non slackware firefox (for example from mozilla site) to overcome this problem as firefox-21 will be the latest version supported in porteus-2.x line unless we decide to recompile never versions against slackware-14.0 (time/resources consuming task so i would like to avoid this).
sorry about that.
Please add [Solved] to your thread title if the solution was found.

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

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#24 by donald » 10 Jul 2013, 21:21

mate-DE-32bit

confirmed--pbundle is working (without updating first)
Clockfix does his job

Firefox default cache-setting 0MB ?

same old thing still remaining:
If you select Firewall block all, it always jumps back to strict
(e.g. after reboot)

How many Porteus-Installer-Icons do we need ?

maybe dconf-editor should not start without root-pw (for users)

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1022
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#25 by ncmprhnsbl » 11 Jul 2013, 00:41

Lxde 64 wizard built
'Build Module' fails to build, while reporting success, as reported by n2prtsusr
also with spacefm
'dir2xzm dir dir.xzm' works fine.

'Convert tgz/txz to xzm' not working either...
convert deb working :)
and extract.

wizard link on index page giving this error =

Code: Select all

Secure Connection Failed
             
          An error occurred during a connection to build.porteus.org.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)
same thing when pressing download after following link from announcement..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Hamza
Warlord
Warlord
Posts: 1847
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#26 by Hamza » 11 Jul 2013, 01:39

NjVFQzY2Rg==

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

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#27 by brokenman » 11 Jul 2013, 01:53

same old thing still remaining:
If you select Firewall block all, it always jumps back to strict
(e.g. after reboot)
Are you saving changes? Are you changing the firewall settings through porteus settings centre?
How many Porteus-Installer-Icons do we need ?
Just one. Where would you like it?
maybe dconf-editor should not start without root-pw (for users)
For what reason? Can you see some security concerns?
Firefox default cache-setting 0MB ?
What does about:cache show in FF after some browsing?
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#28 by donald » 11 Jul 2013, 02:13

@brokenman

Firewall settings are made in psc (activ at boot, mode block all
as it is a normal usb-installation it should be saved,but isn't
next boot looking at psc it is mode strict, always.iptables -L shows
the differences too.

Installer-Icon:
We have one in psc, that may be enough

hide the dconf-editor:
dconf-editor is very useful, but also dangerous (imho) for the inexperienced
user, (he/she could easily destroy the whole configuration)

What does about:cache show in FF after some browsing?

I will check tomorrow ( i'm not using mate right now)
This value is checkt by default in the preferences of firefox
override automatic cache managment>limit cache to 0 Mb of space
Last edited by donald on 11 Jul 2013, 03:46, edited 4 times in total.

sean
Contributor
Contributor
Posts: 144
Joined: 08 Jul 2012, 02:30
Distribution: Porteus v3.0 LXDE i486
Location: South Central PA, USA

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#29 by sean » 11 Jul 2013, 03:10

Well I like donald's original idea of needing root password to use dconf-editor. For the reason he gave in his second post on the subject.

As for hiding dconf-editor, perhaps he miss-spoke on that?

Sean

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

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#30 by brokenman » 11 Jul 2013, 03:48

Thanks. I'll check out PSC and see what is going on.

As for dconf-editor ... I disagree with a root password (or hiding it for that matter). For example the default window manager (Marco) has a built in compositing manager. How would one enable this for guest? There are various convoluted methods but the easiest way is dconf-editor. Putting a root password on it means that whenever the user starts it, they will not be changing the users config, but root's config.

I admit it is not the most user friendly settings system but for some settings it is the easiest way in. For some hard settings that we don't want guest to change (for example some lockdown settings in dconf-editor) a universal config file could be used. Anyway, I am always open to suggestion so provided an argument has benefits and validity I can turn 180 degrees.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply