Page 6 of 9

Re: OpenBox Re-spin

Posted: Sun May 12, 2019 11:57 am
by manyroads
[removed by author]
see next post...

OpenBox Re-spin (draft release)

Posted: Mon May 13, 2019 11:02 am
by manyroads
MX Linux Openbox respin draft release

---- Update! ----

This release/ version seems to be running lighter than the previous draft versions and also a bit lighter than the version I created on antiX. The fact that it runs neck & neck with the antiX version is a HUGE surprise to me. "htop" reports ~325MB of RAM usage on my VirtualBox setup.

But when I compare the openbox resource usage (~325MB) to the 1.5 GB used by xfce4 on my main machine, openbox on MX is VERY skinny, indeed.

There are a few bugs in the release. You'll be happy to note, I do not charge extra for those. :wink: If you know of a fix or two, please send them along.

Known bug(s)- unknown solution (s) - workarounds noted where they are known
--- flatpak does not load in mxpi
--- synaptic does not start with menu selection (obmenu, jgmenu or via synapse); it only loads via terminal (cli)
--- neither of the above problems is fixed by using systemd
--- lightdm-gtk-greeter-settings, also, only runs from terminal via cli
--- "move to trash" (does not find the trash folder); Delete works fine.

Known bug(s)- known solution?? - simple work-around
-- after the install the system is not using the sardi-flat icon them... you will need to set that manually for now. Even I should be able to figure that problem out. ;)

If you have ideas on how to fix the above bugs, or others you might find, please let me know.

Screenshots:
https://ibb.co/s3MVdpG
https://ibb.co/SmcBzWS
https://ibb.co/rFwwwnQ

Download (MX Snapshot)-- this should be fully uploaded and available by 1000 (Mountain Daylight Time) 1600 (UTC) Zulu
http://treemagic.org/MX%20Desktops/MX-L ... nbox-v-0.2

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 12:21 pm
by dolphin_oracle
I would look at your polickit authentication agent and make sure its running. its sounds to me like a lot of issues point towards a wonky policykit setup.

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 12:48 pm
by manyroads
dolphin_oracle wrote:
Mon May 13, 2019 12:21 pm
I would look at your polickit authentication agent and make sure its running. its sounds to me like a lot of issues point towards a wonky policykit setup.
Thank you @dolphin_oracle.... I have never worked with that. I'll give it a go. :lipsrsealed:

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 1:18 pm
by manyroads
dolphin_oracle wrote:
Mon May 13, 2019 12:21 pm
I would look at your polickit authentication agent and make sure its running. its sounds to me like a lot of issues point towards a wonky policykit setup.
Well I tried:
-- reinstalling policykit (that did nothing)...
-- copying a working set of policykit files from my home xfce machine (no joy)

I read debian instructions on policykit installations with sysVinit & shim and they didn't offer any obvious clues.
Mother google did not turn up much that looked helpful except for some things on stackexchange that mirrored the above actions. :eek:

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 2:12 pm
by dolphin_oracle
manyroads wrote:
Mon May 13, 2019 1:18 pm
dolphin_oracle wrote:
Mon May 13, 2019 12:21 pm
I would look at your polickit authentication agent and make sure its running. its sounds to me like a lot of issues point towards a wonky policykit setup.
Well I tried:
-- reinstalling policykit (that did nothing)...
-- copying a working set of policykit files from my home xfce machine (no joy)

I read debian instructions on policykit installations with sysVinit & shim and they didn't offer any obvious clues.
Mother google did not turn up much that looked helpful except for some things on stackexchange that mirrored the above actions. :eek:
is not always enough to have policykit installed. you also need an authentication agent. we use policykit-1-gnome as the authenticator.

if your WM doesn't autostart via xdg autostart standards, then you may need to manually launch it. lxpolkit is often easier in that sort of environment, rather than policykit-1-gnome.

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 3:27 pm
by Head_on_a_Stick
The OP indicates that /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 is listed in the openbox autostart file and so should be running.

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 3:31 pm
by dolphin_oracle
Head_on_a_Stick wrote:
Mon May 13, 2019 3:27 pm
The OP indicates that /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 is listed in the openbox autostart file and so should be running.
I have not had success starting policykit-1-gnome that way. lxpolkit yes, but not policykit-1-gnome.

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 3:44 pm
by Head_on_a_Stick
dolphin_oracle wrote:
Mon May 13, 2019 3:31 pm
I have not had success starting policykit-1-gnome that way.
It works for BunsenLabs :happy:

The OP lifted the autostart file from that distribution and it was in turn inherited from CrunchBang (with some changes).

Re: OpenBox Re-spin

Posted: Mon May 13, 2019 3:49 pm
by dolphin_oracle
Head_on_a_Stick wrote:
Mon May 13, 2019 3:44 pm
dolphin_oracle wrote:
Mon May 13, 2019 3:31 pm
I have not had success starting policykit-1-gnome that way.
It works for BunsenLabs :happy:

The OP lifted the autostart file from that distribution and it was in turn inherited from CrunchBang (with some changes).
ok. the synaptic not starting was my main clue (synaptic uses synaptic-pkexec to start). the trash problem could be related (gvfs/thunar might use policykit, don't know, it wouldn't surprise me).

on the other hand, it might be worth exploring weather "menus" and/or "gksu" is installed and working.

to me it all sounds like a authentication and/or privledge escalation problem.