Puppy Linux Discussion Forum

Thanks willams2. Sadly, it seems that a pinboard disable does not solve the problem. I was successful once with that tact but subsequent tries result in the same issue of a stuck ROX window. Curiously, this only happens with Fluxbox. I decided to revisit Pekwm and all is well with ROX while running ...

I posted about this quite a while back. See here: viewtopic.php?p=5215#p5215

What I have discovered is that disabling the default Pinboard causes this problem to resolve. Does anyone know how to permanently disable PuppyPin or at least to disable it at each boot?

Is there a devx file available anywhere? I'd like to build a package from source...

Thank you

Every time I set up a share using Samba Simple Management at the next boot of the system I have lost internet connectivity. No amount of playing with SNS, Frisbee, nor Network Wizard rectifies the problem. In order to restore connectivity I have to boot into a fresh Fossapup, connect to my network ...

So, I've documented elsewhere a strange problem with ROX when running Fluxbox WM under Fossapup64: https://forum.puppylinux.com/viewtopic.php?p=5215#p5215 I'm posting here just in case there are any other Fluxbox users so that my workaround is available. I believe that the problem is with the ...

hi @rek769 , have you tried unticking "override window manager control of the pinboard and panels' in rox options >>> compatibility Thanks @666philb: Yes, that was the first thing I tried. I've also turned on (and off again) "Panel as dock", "Panel stays on top", and "Panel confined to work area ...

hi @rek769 , have you tried unticking "override window manager control of the pinboard and panels' in rox options >>> compatibility Thanks @666philb: Yes, that was the first thing I tried. I've also turned on (and off again) "Panel as dock", "Panel stays on top", and "Panel confined to work area ...

Now my next weird problem... Opening a ROX filer window gives me a window with no decorations (no window title bar, no borders). The window is stuck in the upper left corner of the desktop and I can't move it...not even with alt + left mouse button. I can not resize the window manually but it will ...

Hi @rek769 Another tnint2 fan here... Did you look to see which monitor the system sees as primary? in setup > zarfy maybe too obvious but thought I'd ask I think maybe it has to do with how I use XRANDR to setup the monitor configurations. However, even if I turn off the laptop monitor via xrandr ...

Hi @rek769 Another tnint2 fan here... Did you look to see which monitor the system sees as primary? in setup > zarfy maybe too obvious but thought I'd ask I think maybe it has to do with how I use XRANDR to setup the monitor configurations. However, even if I turn off the laptop monitor via xrandr ...

Greetings all, I've gotten the latest Fossapup booted up successfully. I am using a fresh install (no previous save file) The first things I do with a new puppy is to download, install, and configure Fluxbox and the Tint2 panel. I have a dual monitor setup. When I use the exact same config files for ...

To whomever added "SOLVED" to my post....please be aware this is not solved. The AppImage is not able to be run as normal. It must be extracted and ran with special commands from the terminal. I'm still looking for a way to run it as a normal AppImage... To that end I am still hoping for some ...

garnet Sweet...that did the trick but I had to extract the AppImage in my root folder...extracting to my mounted hard drive resulted in an error complaining that libffmpeg.so was not found. Maybe something to do with system path?? Anyway, could you explain to me what that last line does? Also, do ...

I found the deb file here: https://packages.riot.im/debian/pool/main/e/element-desktop/ Running via the deb produces the exact same error message as the AppImage so I don't think this is an issue with the AppImage. There seems to be something basal about Puppy Linux that it causing this...just don't ...

As I stated in my original post, I have already tried running it with the --no-sandbox flag. Also, as stated in the original post, I have corrected the permissions issue that was suggested by the terminal error message to no avail. Changing the name of the AppImage has zero effect as you stated. The ...

Greetings all, I am successfully running a RIOT IM Appimage on my 64 bit Bionic Pup. However, RIOT underwent a name change to Element and someone has seen fit to create a new Appimage. The problem I'm having is when trying to run the Appimage with the --no-sandbox flag I get a fatal error related to ...