Page 10 of 12

Re: Porteus 3.1rc feedback

Posted: 29 Nov 2014, 03:34
by sean
@Ed_P

Hi Ed, From the panel MainMenu/Preferences/Desktop/Advanced, unclick it.

Sean

Re: Porteus 3.1rc feedback

Posted: 29 Nov 2014, 05:09
by Ed_P
Perfect. :good:

Thank you Sean. :beer:

Re: Porteus 3.1rc feedback

Posted: 29 Nov 2014, 12:17
by ncmprhnsbl
re: pcmanfm-qt superuser
--in lxqt session:
calling su terminal from rightclick menu (* ROOT *)
then $pcmanfm-qt --- works

Code: Select all

** (pcmanfm-qt:4292): WARNING **: The directory '~/Templates' doesn't exist, ignoring it
isPrimaryInstance
start-loading
finish-loading
to see drives:

Code: Select all

root@porteus:~# dbus-launch pcmanfm-qt
Error creating proxy: Error calling StartServiceByName for org.gtk.Private.GPhoto2VolumeMonitor: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/libexec/gvfs-gphoto2-volume-monitor exited with status 127 (g-dbus-error-quark, 25)

** (pcmanfm-qt:4303): WARNING **: The directory '~/Templates' doesn't exist, ignoring it
isPrimaryInstance
start-loading
finish-loading
opening guest terminal then suing to root
then $pcmanfm-qt -- doesnt work???

Code: Select all

Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

** (pcmanfm-qt:4263): WARNING **: The directory '~/Templates' doesn't exist, ignoring it
logging in to root account works no problem
suing to guest in terminal, then $pcmanfm-qt also doesnt work

openbox session:
pcmanfm-qt must be called with dbus-launch in order for drives
to be visible. i just made a .desktop file with line
Exec=dbus-launch --exit-with-session /usr/bin/pcmanfm-qt %U
similarly for root in guest session
Exec=ktsuss dbus-launch --exit-with-session /usr/bin/pcmanfm-qt /root

i,m guessing the ktsuss wrapper doesnt work outside lxqt session(either)

my workaround: use spacefm or mc or log in to root ;)

Re: Porteus 3.1rc feedback

Posted: 29 Nov 2014, 16:18
by sean
1) Porteus 3.1-rc2 32bit Mate

Before today all Mate testing was done with VirtualBox and the .iso, and that worked fine. However, today I tried to install this to a 4Gig USB flash drive. I tried using several machines to no avail. Using a CD and Porteus Installer resulted in a minute or two of nothing, then the installer window just vanishing. Trying to run the executable in /boot resulted in this message:

"An error occurred while loading the archive"

2) Porteus 3.1-rc2 64bit LXQt

Installed this to a 4GIG USB flash drive. Swapped out the old 003-lxqt.xzm for the new using Super User Mode Terminal. Used drop down menu to activate the module. In the main menu under office AbiWord had no icon, and upon clicking it there was no response. Never got an AbiWord.

I found no way to activate the AbiWord module.

3) I noticed when using LXQt via USB that the CD drive runs continuously (at least I think it's the CD/DVD drive), regardless, I never hear it any other time unless I'm loading something from that drive. This is why I decided to install Mate on a flash drive, just to see if it would also run the CD drive. But the install wouldn't work for me.

Sean

Re: Porteus 3.1rc feedback

Posted: 29 Nov 2014, 17:09
by francois
porteus 3.1 rc2 xfce:

The shutdown button on the right of the panel. Is it possible to add the logout, suspend, hibernate and reboot functions?

Thanks.

Re: Porteus 3.1rc feedback

Posted: 29 Nov 2014, 20:08
by brokenman
i,m guessing the ktsuss wrapper doesnt work outside lxqt session(either)
My work around is to call ktsuss from a script and then to call pcmanfm-qt once elevated to root.

The script is:

Code: Select all

if [ $UID -ne 0 ]; then
    ktsuss $0 &
    exit
fi

dbus-launch --exit-with-session pcmanfm-qt
Then the desktop file calls this script. This works for me but I am informed that it only works sporadically for others.
Trying to run the executable in /boot resulted in this message:
"An error occurred while loading the archive"
The script is the same one in all desktops so not sure why it didn't work for you. I will check out the pinstaller (also the same in every desktop) tonight.

Re: Porteus 3.1rc feedback

Posted: 30 Nov 2014, 02:12
by donald
@ francois
Hi
right-click this button > properties > choose the options you like... :wink:

Re: Porteus 3.1rc feedback

Posted: 30 Nov 2014, 06:03
by Ed_P
brokenman wrote:The script is:

Code: Select all

if [ $UID -ne 0 ]; then
    ktsuss $0 &
    exit
fi

dbus-launch --exit-with-session pcmanfm-qt
sumpcmanfm.sh

Code: Select all

#!/bin/sh 
# http://forum.porteus.org/viewtopic.php?f=53&t=3983&p=29541#p29537

if [ $UID -ne 0 ]; then
    ktsuss $0 &
    exit
fi

dbus-launch --exit-with-session pcmanfm-qt

Code: Select all

guest@porteus:~$ ./sumpcmanfm.sh
guest@porteus:~$ 
Error creating proxy: Error calling StartServiceByName for org.gtk.Private.GPhoto2VolumeMonitor: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/libexec/gvfs-gphoto2-volume-monitor exited with status 127 (g-dbus-error-quark, 25)

** (pcmanfm-qt:2717): WARNING **: The directory '~/Templates' doesn't exist, ignoring it
./sumpcmanfm.sh: line 9:  2717 Segmentation fault      dbus-launch --exit-with-session pcmanfm-qt

guest@porteus:~$ 
:no:

And:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# dbus-launch --exit-with-session pcmanfm-qt
Error creating proxy: Error calling StartServiceByName for org.gtk.Private.GPhoto2VolumeMonitor: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/libexec/gvfs-gphoto2-volume-monitor exited with status 127 (g-dbus-error-quark, 25)

** (pcmanfm-qt:3148): WARNING **: The directory '~/Templates' doesn't exist, ignoring it
Segmentation fault
root@porteus:/home/guest# 

Re: Porteus 3.1rc feedback

Posted: 30 Nov 2014, 22:57
by Ed_P
LXQt 64-bit

If Power Management Lid Watcher's "Action when lid is closed" "On Battery" is set to Suspend when the lid is closed then reopened the screen is blank and the system is unresponsive. SysRq REIBUS doesn't help. Netbook has to be powered down to be rebooted to restart the system.

Re: Porteus 3.1rc feedback

Posted: 01 Dec 2014, 12:26
by fanthom
here is updated 003-lxqt.xzm module:
http://dl.porteus.org/x86_64/testing/003-lxqt.xzm

a) activation of modules uses bit risky but the most reliable method to update desktop menu. let me know if your system hangs or something ... (never happened here but still)
b) i have made some progress on the 'super user mode pcmanfm' front:
- pcmanfm works every time if you open terminal -> switch to root with 'su' -> run pcmanfm-qt (i have added: 'export $(dbus-launch --exit-with-session)' to /root/.bashrc and this seems to work)
- i'm using the same workaround when running pcmanfm-qt directly from desktop menu: lxterminal opens -> you have to type root password -> now you have to run 'pcmanfm-qt' manually

this method works almost perfectly (sometimes pcmanfm segfaults during first run but at least you can see what happened and repeat the command).
here is how i do it from the /usr/share/applicaitons/su-pcmanfm.desktop:

Code: Select all

Exec=lxterminal -e "su -c 'echo start pcmanfm-qt now; bash'"
would be great if someone could find a way to run pcmanfm automatically once user provide root password.

thanks for any help given - there is only a week left before 3.1. is released so we must hurry up.

Re: Porteus 3.1rc feedback

Posted: 01 Dec 2014, 14:07
by Bogomips
Ed_P wrote:LXQt 64-bit

If Power Management Lid Watcher's "Action when lid is closed" "On Battery" is set to Suspend when the lid is closed then reopened the screen is blank and the system is unresponsive. SysRq REIBUS doesn't help.
Sure your mirror isn't playing tricks on you?

Re: Porteus 3.1rc feedback

Posted: 01 Dec 2014, 18:55
by Ed_P
Bogomips wrote:
Ed_P wrote:SysRq REIBUS doesn't help.
Sure your mirror isn't playing tricks on you?
:shock: :oops:

Hey, I at least remembered all the letters. :D

Re: Porteus 3.1rc feedback

Posted: 02 Dec 2014, 17:22
by Bogomips
KDE 32 bit AF

If for some reason when system is loaded, network connection not made, then the time shows incorrectly, and continues to be incorrect, even after network connection made. System does not readjust itself upon establishing network connection. Is this expected behaviour?

Re: Porteus 3.1rc feedback

Posted: 02 Dec 2014, 18:11
by fanthom
@Bogomips
nice catch ;)
will make it that after syncing through ntp the time will get saved to the hardware clock (it was not the case till now)
thanks

another LXQT update:
http://dl.porteus.org/i486/testing/003-lxqt.xzm
http://dl.porteus.org/x86_64/testing/003-lxqt.xzm
this is the final version so please test it when you have a chance.

'pcmanf-qt super user mode' started from system menu works 9 times on 10 attempts. the one faulty attempt is when pcmanfm segfaults and you can see it by running dmesg :crazy:

Re: Porteus 3.1rc feedback

Posted: 02 Dec 2014, 19:00
by francois
donald wrote:@ francois
Hi
right-click this button > properties > choose the options you like... :wink:
Thanks donald.

There is also the xfce menu which offers all these options. I only thought that offering more than the shutdown button similar to what is offered on kde would lead to standardisation of porteus desktops. :)