READ-ONLY Archive
https://oldforum.puppylinux.com/
Yes, that doesn't work, but you can set it in the "Openbox Configuration manager" in Menu > Settingsjohnywhy wrote:Workspaces: Can't adjust number of workspaces. Workspace switcher properties gives error on click "Workspace settings"
Quote:
Unable to open the workspace settings. Failed to execute child process "xfwm4-workspace-settings" (No such file or directory.
You should be able to use apt-get. It is in the repositories.zagreb999 wrote:fred,
is it possible to kreate sfs (or install)
djview4?
thanks.
For me it works, why not for you, what does it say ?zagreb999 wrote:... it is impossible to install
djview4 on xd!!!
Code: Select all
root@xenial:~# apt-get install djview4
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libdjvulibre-text libdjvulibre21 libgudev-1.0-0 libinput-bin libinput10 libpcre16-3
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5 libqt5printsupport5
libqt5widgets5 libwacom-common libwacom2 libxcb-icccm4 libxcb-image0 libxcb-keysyms1
libxcb-randr0 libxcb-render-util0 libxcb-xkb1 libxkbcommon-x11-0
Suggested packages:
djvulibre-bin djview-plugin libqt5libqgtk2 qt5-image-formats-plugins qtwayland5
Recommended packages:
djvulibre-desktop qttranslations5-l10n libqt5svg5 libwacom-bin
The following NEW packages will be installed:
djview4 libdjvulibre-text libdjvulibre21 libgudev-1.0-0 libinput-bin libinput10
libpcre16-3 libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5
libqt5printsupport5 libqt5widgets5 libwacom-common libwacom2 libxcb-icccm4
libxcb-image0 libxcb-keysyms1 libxcb-randr0 libxcb-render-util0 libxcb-xkb1
libxkbcommon-x11-0
0 upgraded, 23 newly installed, 0 to remove and 234 not upgraded.
Need to get 11.6 MB of archives.
After this operation, 44.2 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 libxcb-icccm4 i386 0.4.1-1ubuntu1 [10.8 kB]
Get:2 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 libxcb-keysyms1 i386 0.4.0-1 [8562 B
.....
.....]Assuming you downloaded and installed slimjet .deb from here:zagreb999 wrote:any help?
slimjet 20
on xenialdog?
Code: Select all
#!/bin/bash
xhost +local:puppy
su puppy -c "/usr/bin/flashpeak-slimjet "$@" --user-data-dir=/home/puppy/slimjet/user --disk-cache-dir=/home/puppy/slimjet/cache --disk-cache-size=10000000 --media-cache-size=10000000 "$@""--no-sandbox still works on Chrome latest version. (Google Chromefredx181 wrote:Assuming you downloaded and installed slimjet .deb from here:zagreb999 wrote:any help?
slimjet 20
on xenialdog?
https://www.slimjet.com/en/dlpage.php
Probably the problem is that it won't run as root.
Eerlier adding --no-sandbox worked to run Chromiium based browsers as root, but now it seems not working anymore.
So you need to run it as unprivileged user, if you have user "puppy" on your system, then this script should work to run Slimjet running as user puppy:
FredCode: Select all
#!/bin/bash xhost +local:puppy su puppy -c "/usr/bin/flashpeak-slimjet "$@" --user-data-dir=/home/puppy/slimjet/user --disk-cache-dir=/home/puppy/slimjet/cache --disk-cache-size=10000000 --media-cache-size=10000000 "$@""
#!/bin/sh
/usr/bin/google-chrome-stable --user-data-dir=/live/image/ChromeSettings/google-chrome/config --disk-cache-dir=/live/image/ChromeSettings/google-chrome/cache --disk-cache-size=10000000 --media-cache-size=10000000 --no-sandbox --disable-infobars "$@"
Ah, ok, then probably Slimjet is an exception (only tried 32-bit, btw).dancytron wrote:--no-sandbox still works on Chrome latest version. (Google Chrome
Version 69.0.3497.100 (Official Build) (64-bit)).
I don't think it's possible, I tried the slimjet v20 32-bit a few times again on different systems, cannot run as root.zagreb999 wrote:who knows to ran slimjet20
as root as squashfs module?
--no-sandbox cripples Chrome's security measures. Opening up xhost + is as good as opening up running as root (user puppy can stuff things into any other window that might be running as root, such as a rox/thunar/pcmanfm window - perhaps issuing a file manager's open terminal window command and then stuffing rm -rf / or whatever into that (root) terminal window.fredx181 wrote:Eerlier adding --no-sandbox worked to run Chromium based browsers as root, but now it seems not working anymore.
So you need to run it as unprivileged user, if you have user "puppy" on your system, then this script should work to run Slimjet running as user puppy:Code: Select all
#!/bin/bash xhost +local:puppy su puppy -c "/usr/bin/flashpeak-slimjet "$@" --user-data-dir=/home/puppy/slimjet/user --disk-cache-dir=/home/puppy/slimjet/cache --disk-cache-size=10000000 --media-cache-size=10000000 "$@""
Well, since I am still wiak when running as user 'puppy' and still wiak when running as user 'root', the above is all fine, thanks, and not any cause at all for alarm to me.rufwoof wrote:Opening up xhost + is as good as opening up running as root (user puppy can stuff things into any other window that might be running as root, such as a rox/thunar/pcmanfm window - perhaps issuing a file manager's open terminal window command and then stuffing rm -rf / or whatever into that (root) terminal window.
I'd say just install chromium-browser with Synaptic or apt-get and run with --no-sandboxzagreb999 wrote:regards!
latest chromium as root
32 bit???
Code: Select all
chromium-browser --no-sandbox --disable-infobarsFine. Any web site/link could achieve root access/control of your box via a single browser bug and you accept that. Just pointed it out as others might feel differently. Fred wants to consider it no further here so enough said.wiak wrote:Well, since I am still wiak when running as user 'puppy' and still wiak when running as user 'root', the above is all fine, thanks, and not any cause at all for alarm to me.rufwoof wrote:Opening up xhost + is as good as opening up running as root (user puppy can stuff things into any other window that might be running as root, such as a rox/thunar/pcmanfm window - perhaps issuing a file manager's open terminal window command and then stuffing rm -rf / or whatever into that (root) terminal window.