MX-21 beta 1 feedback thread

[dolphin_oracle]

@SwampRabbit what's needed is something for making shares. Gigolo is a mounting tool.

[oops]

@SwampRabbit what's needed is something for making shares. Gigolo is a mounting tool.

The tool to do that into MX19 was simple and perfect, similar to the redhat one
http://web.mit.edu/rhel-doc/3/rhel-sag- ... uring.html

... And Samba is useful with rsync and grsync
https://rsync.samba.org/
http://www.opbyte.it/grsync/

[SwampRabbit]

@SwampRabbit what's needed is something for making shares. Gigolo is a mounting tool.

yeah my bad, I went back and looked at the first pot about it now.

funny thing is right now OOTB on MX-21 when in Thunar you can right-click and get "Share a folder on your network".
when doing that, it asks for your password, but dies silently.

I'm looking at fixing the thunar-shares-plugin if possible ... but we already talked about that.

[figueroa]

Rats; I found a bug that only appears (at least in the case of a persistent Live-usb) when accessing MX-21 beta 1 remotely through x2go. The glitch appears to be an authorization problem when using the updater icon on the panel notification area, running in either the default XFCE DE, or the LXDE DE, which I installed from MXPI. This is a new glitch and the update function works normally in MX-18 and MX-19 when accessed remotely with x2go.

When the updater notification icon turns green, I click on the icon and review the available updates. Then click on the bottom middle Update button, the terminal briefly appears showing "apt-get full-upgrade" then in about one second crashes, never prompting for a password.

I suspect this might be the result of changes somewhere in /usr/lib/apt-notifier/ which are beyond my programming and scripting knowledge. There is an error message in the auth.log pertaining to this:

Code: Select all

Aug  2 23:39:48 mx1 pkexec[11676]: demo: Error executing command as another user: Not authorized [USER=root] [TTY=/dev/pts/1] [CWD=/home/demo] [COMMAND=/usr/lib/apt-notifier/actions/updater_full-upgrade_action]

All of the other functions requring authorization via the updater icon work as expected, prompting for the expected password.

[fehlix]

Rats; I found a bug that only appears (at least in the case of a persistent Live-usb) when accessing MX-21 beta 1 remotely through x2go. The glitch appears to be an authorization problem when using the updater icon on the panel notification area, running in either the default XFCE DE, or the LXDE DE, which I installed from MXPI. This is a new glitch and the update function works normally in MX-18 and MX-19 when accessed remotely with x2go.

When the updater notification icon turns green, I click on the icon and review the available updates. Then click on the bottom middle Update button, the terminal briefly appears showing "apt-get full-upgrade" then in about one second crashes, never prompting for a password.

I suspect this might be the result of changes somewhere in /usr/lib/apt-notifier/ which are beyond my programming and scripting knowledge. There is an error message in the auth.log pertaining to this:

Code: Select all

Aug  2 23:39:48 mx1 pkexec[11676]: demo: Error executing command as another user: Not authorized [USER=root] [TTY=/dev/pts/1] [CWD=/home/demo] [COMMAND=/usr/lib/apt-notifier/actions/updater_full-upgrade_action]

All of the other functions requring authorization via the updater icon work as expected, prompting for the expected password.

Probably a polkit thing about authorization of the fine-grained difference between active and inactive session. The apt-notifier authorization policy is currently set active_session to allow_admin (=root) for upgrade. Seems "remote" x2go sessions are regarded as inactive sessions. I guess other functions mentioned do have a more relaxed authorization policy by allowing in addition "inactive" or "any" session.

[agnivo007]

@SwampRabbit Gigolo is like smb4k, right? Just to browse/mount different protocol shares but NOT create them?

I'm still at a loss as to what happened to system-config-samba and thunar samba plugin , didn't follow it well or understand or mere ignorance, dunno. Can you explain in short?

[dolphin_oracle]

@SwampRabbit Gigolo is like smb4k, right? Just to browse/mount different protocol shares but NOT create them?

I'm still at a loss as to what happened to system-config-samba and thunar samba plugin , didn't follow it well or understand or mere ignorance, dunno. Can you explain in short?

thunar shares plugin is broke (or there is a mismatch with the thunar version maybe) and system-config-samba is python2 and no longer maintained.

[SwampRabbit]

@SwampRabbit Gigolo is like smb4k, right? Just to browse/mount different protocol shares but NOT create them?

I'm still at a loss as to what happened to system-config-samba and thunar samba plugin , didn't follow it well or understand or mere ignorance, dunno. Can you explain in short?

The system-config-samba is python2 and development stopped and no one has picked it up. The death of python2 has killed a ton of applications because no one ported or help port them over to python3.

This helps demonstrate the importance and need for people to stay involved with, contribute to, and support the FOSS applications they use and enjoy. Most everything FOSS is 100% created for free with someone’s free time. People make a big deal about an application being abandoned, but never actually chose to support it or the developer really in the first place. Just simply giving a star on GitHub or telling someone you appreciate and like their application if nothing else can make a difference. Instead people will complain or bombard developers with nonsense.
The old saying goes… “ if you’re not part of the solution, you’re part of the problem”.

Enough detailing of the thread now from me


I am working on the Thunar plugin, I think the updated version I packaged is broke, and dolphin told me earlier that him and Adrian are working on another solution. I’m sure all will be good in time for final release.

Edit: ninja’d by dolphin it seems as I typed a long winded reply

[agnivo007]

Thanks for the explanation. KDE is in a better shape regards to sharing I hope and look forward to it in the future to test; only if it works with systemd boot this time.

Good to know that xfce edition will get something working when ready.

[SwampRabbit]

I believe I have now the thunar-share-plugin fixed, just need to verify more