Porteus

@Ahau

Ahau wrote: To test my fix, su to root and run:

Code: Select all

gpasswd -d guest plugdev

that will remove guest from the plugdev group. Now you should get a popup prompting for root password before udisks will allow you to unmount disks that were not mounted by guest. If this works, I'll see about a fix for 2.2 so we can get thorough testing on it.

Your fix works partly.If the permission is given once (to mount sda2 for example),
then "guest" is also able to mount sda3,4,5 etc, without beeing asked for the
root-Pw again. (the same for umount)
In General:
what i am looking for is this:
I start the system,log in as root,umount partitions which should not be accessible
for guest,-- this should survive a shutdown/reboot.Unmounted Partitions
(by root) should not at all be visible for "guest".(no Icon) 8)

Hi,

It seems that deb2xzm command is not working, please advise!

p.s. I am using Porteus 2.1 KDE

@Saman
please post an url to the deb package so i can check myself

thanks

I wrote a script to extract debian packages (among others)
I believe I used undeb script.
http://forum.porteus.org/viewtopic.php?f=53&t=1313

Hi, I boot MATE/LXDE/XFCE from USB with copy2ram params, no save file. If USB is mounted, or even unmounted (but physically still inside USB slot) suspend doesn't work - or, actually, looks like nothing happens, but when I pull out USB stick, laptop immediately suspends. Is that by design?

Another, smaller issue, is that even though I set in power management settings to "ask" when power button is pressed, it immediately switches off my laptop. I have to go via "menu"->"shutdown"->suspend.

KDE4 i486 with libreoffice.

LibreOffice Crashes when using presenter. Copy and paste some text, tried to change from 32pt font to smaller font and program crashed
Other than this crash, most other things work great and are looking beautifully! Great Job folks developers, programmers, & all porteus users working to make porteus better and one of the best pocket linux system available.

Wrong colours on youtube on flash videos

System: XFCe Porteus 2.1 rc2, x86-64, FlashPlayer is: 11.2.202.285
nVidia driver used: nVidia-304.88-porteus-v2.1-rc2-x86_64-1ftm.xzm

Same issue like described on other pages:
https://answers.launchpad.net/ubuntu/+s ... ion/192181
https://bugbase.adobe.com/index.cfm?eve ... id=3077076

Most recognized error are the blue faces.

I put this in my cat /etc/adobe/mms.cfg , and it worked until reboot, now it won't work anymore: I also have to disable "enable hardware acceleration" in the flash player settings (right click on a video: "Settings ..."), after reloading the video page the error vanishes.

Anything we can do to get rid of this error without the need of the user doing anything? To be included in 2.1 finale...

[Porteus-LXDE-v2.1-rc2-i486.iso]
X driver modesetting is degraded.
[/usr/lib/xorg/modules/drivers/modesetting_drv.la,modesetting_drv.so in 002-xorg]

On netbook MSI u180 (cpu:Atom N2800),
Porteus-LXDE-v2.1-rc2-i486.iso can not be booted,
but Porteus-LXDE-v2.1-rc1.5-i486.iso can be booted.

/usr/lib/xorg/modules/drivers/modesetting_drv.* of v2.1-rc2 are replaced ones of v2.1-rc1.5.
Then the modefied Porteus-LXDE-v2.1-rc2-i486.iso can be booted on Atom N2800.

@Saman
any chance to get a deb archive which does not convert to xzm?

@solnyshok
tested on my laptop and i can suspend when usb is plugged. please check if disabling 'laptop-mode-tools' helps: @Rava
i would like to avoid quirks as they may work for one hardware but not for other. disabling flash HW accel globally is a bad idea as probably only small percentage of nVidia users are affected by this bug. you need to fix this issue locally. try to add: to mms.cfg as per:
https://bugs.launchpad.net/ubuntu/+sour ... bug/967091

@neko
confirmed this bug and will be downgrading to modesetting-0.7.0
thanks a lot.

@all porteus users
brokenman is still on holiday and hamza just went on it but will try to push 2.1 final early next week. it's a last chance to report bugs so please do not hesitate to do it if you find them.

thanks

There is an issue, at least since 2.0 finale, and also in 2.1 rc1 and 2.1 rc2.

All versions: XFCe, x86-64
All systems with Dual Core CPU, nVidia card, 2.1 rc2 had nVidia-304.88-porteus-v2.1 driver.

The systems have either 3 GB of RAM or 3 1/2 GB of RAM (actually, that machine has technically 4 GB or RAM, but the BIOS only supports 3 1/2 GB, only the RAM tester that got shipped with older Porteus could see 4 GB of RAM and test all RAM, all other x86-64 Linux OS I tried so far only sees what BIOS tells them: 3 1/2 GB, and not 4 GB... Is there a startup tweak that could tell Porteus that there is 4 GB of RAM?)

Anyhow, back to the bug.
As you can see above, the hardware is quite well equipped, and usually the system runs just fine.
But at times, when I open, like, 3 or such new tabs in FFx, the whole system freezes. All I could do this time it happened, was pressing CTRL+ALT+F8, this gets me to my virtual console 8 (yes, I tweaked Porteus so that I have the virtual terminals 1-6 and 8-12, since we all have these Fx keys on our keyboards...)
When log into "virtual terminal 8" as root, this is run there via my own /etc/profile.local : So, I get to see the most recent /var/log/messages, even when X is no longer reacting.

I could upload the camera made screenshot, but there is nothing interesting to see: The freeze happened approx between 10:00 and 10:05 ...
I tried to kill FFx via virtual console, but all I typed in any of the open and running virtual consoles was not even showing as I typed it, even after waiting for some time; and sure was not executed.
The USB stick that has the Porteus files on it started blinking continuously, even after I shut down the PC with pressing the Power Button >4 seconds the USB stick still was blinking continuously, only after I pulled it out and plugged it into again (it was connected via a 4 port USB hub) the USB stick stopped blinking, starting Porteus anew went just fine... (I am typing from that very machine / the very same USB Porteus media)

What can I do to capture more interesting logs to investigate this freezing behaviour better? Or will there be none, since /var/log/messages shows nothing...

@Rava
looks like a GPU driver bug. please try to recreate and save /var/log/dmesg and /var/log/Xorg.0.log somewhere then upload to pastebin.com.
you could also try to recreate it using nouveau to confirm it's nVidia driver fault.

fanthom wrote:looks like a GPU driver bug. please try to recreate and save /var/log/dmesg and /var/log/Xorg.0.log somewhere then upload to pastebin.com.
you could also try to recreate it using nouveau to confirm it's nVidia driver fault.

How could I put only these files on my USB stick, while the system is running?
Cause trying to save them when it freezes might again fail...

I know there is one console program that could split one file on the terminal's screen, and also in a different file, but I forgot which one that was, or which parameter did the trick...

Is there a way to disable the screen blanking after 10 minutes,
or a setting in mplayerto override while mplayer is used?
I saw kiosk has the ability to override blanking, wondering if possible.
I don't use changes, I recreate module with setting in it.
I've been trying different types of settings the last couple of days.
The last thing I can come up with is a shortcut on desktop to change
the setting for blanking(have not done this yet), but would like to know
if there is a more permanent way of changing the setting

thanks in advance

@Rava
i thought you could switch to VT2 -> login as root -> copy them on your stick?

@n2prtsusr
DPMS is enabled by default so you could create /etc/X11/xorg.conf (run 'xconf' script in runlevel 3) and then add "DPMS" "false" in monitor section or (in case you are using porteus on different PCs) edit /opt/porteus-scripts/xorg/gui-autostart and add following code:

@fanthom

PERFECT!
Thank you VERY much