Page 34 of 67
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 12:42 pm
by agnivo007
As mentioned by DO, everywhere. Yes, without a history of previous data, how to revert? Maybe a folder.smbak file? (looks like I'm asking too much)
Also: I created user/pass using smbpasswd and can access/mount a share from a different pc. SMB speeds stuck at 8MB/s though, maybe I need to tweak buffers in smb.conf?
I have replied on the rtl8811 thread too.
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 1:38 pm
by SwampRabbit
dolphin_oracle wrote: Wed Aug 04, 2021 11:35 am
@SwampRabbit I saw this last nite. when you do "everyone can use" type share, it changes the linux file system permissions to match. the permisions are not change back afterwards if you remove the share. honestly it would be better if they didn't change them in the first place, but I can see why they did. the fact that samba permisions do not equal linux file system permissions is often a point of confusion.
unless they cached the old permissions, I'm not sure how they would know what to set them back to. and I'm not sure I would in any case.
I concur, this really isn't an issue unless a user is using "Allow other users to write in this folder" AND "Allow Guest access" which is a completely open share.
If they are, that's on them anyway, doesn't matter what OS, DE, tool they use. One can always just delete the folder or change the file permissions back to the default.
The best thing is though, the plugin
will not let a user change a directory/folder they do not own, so no dropping the permissions on /, /var, /etc and the likes.
Initial folder permissions after creation
Code: Select all
drwxr-xr-x 2 bob bob 4096 Aug 4 13:16 'New Folder'
Just setting "Share this folder"
Code: Select all
drwxr-xr-x 2 bob bob 4096 Aug 4 13:19 'New Folder'
After setting "Allow other users to write in this folder" - Note this provides a pop-up warning that it is changed permissions
Code: Select all
drwxrwxrwx 2 bob bob 4096 Aug 4 13:19 'New Folder'
Just using "Allow Guest access"
Code: Select all
drwxr-xr-x 2 bob bob 4096 Aug 4 13:28 'New Folder'
After setting "Allow other users to write in this folder" AND "Allow Guest access"
Code: Select all
drwxrwxrwx 2 bob bob 4096 Aug 4 13:16 'New Folder'
After removing "Allow other users to write in this folder" AND "Allow Guest access"
Code: Select all
drwxrwxrwx 2 bob bob 4096 Aug 4 13:16 'New Folder'
Side note: if there are no other local interactive users on the system, trying to share the actual /home directory errors out, so thats kinda a good thing.
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 1:41 pm
by SwampRabbit
agnivo007 wrote: Wed Aug 04, 2021 12:42 pm
As mentioned by DO, everywhere. Yes, without a history of previous data, how to revert? Maybe a folder.smbak file? (looks like I'm asking too much)
Also: I created user/pass using smbpasswd and can access/mount a share from a different pc. SMB speeds stuck at 8MB/s though, maybe I need to tweak buffers in smb.conf?
I have replied on the rtl8811 thread too.
For now one can change the permissions back to drwxr-xr-x, or if they just created a new folder like "my-share", they can deleted.
This is ONLY a issue if someone uses BOTH "Allow other users to write in this folder" AND "Allow Guest access"... in that case... we can't stop them from doing that if they want to.
The smb config is probably not optimized, should be a lot of other things too, smb/samba is really hit or miss, doesn't matter if you have everything set right or not sometimes.
This will need more time to test, analyze, and tweak if we need to.
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 1:51 pm
by anticapitalista
Can I request feedback from those running live either from a usb or frugal install.
Particularly for non English set up.
* are the live boot menus localised into your language (legacy and UEFI boot)?
* if so, do they make sense?
* when setting up persistence, is it localised?
* if so, does it make sense?
* when remastering, is it localised?
* if so, does it make sense?
* any bugs running live sessions?
Thanks
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 2:03 pm
by fehlix
anticapitalista wrote: Wed Aug 04, 2021 1:51 pm
* are the live boot menus localised into your language (legacy and UEFI boot)?
to add: Do also check the GRUB menus in legacy boot: last menu entry "Switch to GRUB Bootloader".
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 2:13 pm
by oops
@SwampRabbit "... The best thing is though, the plugin will not let a user change a directory/folder they do not own, so no dropping the permissions on /, /var, /etc and the likes."
... they do not own and if the chmod is 750 or so (the default into umask 022 here (755): grep -i umask /etc/login.defs ), so if the others are not allowed for a public share.
PS: how to revert a custom setting? Maybe a folder.smbak file? ... Can be a good idea.
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 2:29 pm
by agnivo007
One question : I'm currently testing with a NTFS partition that I mount using thunar which is shared via smb.
If I mount using fstab, will that work? Where (and which mount options) should I mount it to be able to share successfully using the current solution?
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 2:32 pm
by CharlesV
Love the new release! Finally got it installed on my Yoga and a few things showing .
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: LENOVO product: 80UE v: Lenovo YOGA 900-13ISK2 serial: <filter>
Chassis: type: 10 v: Lenovo YOGA 900-13ISK2 serial: <filter>
Mobo: LENOVO model: VIUU4 v: SDK0J40709 WIN serial: <filter> UEFI: LENOVO v: 2UCN10T
date: 10/14/2016
Battery: ID-1: BAT1 charge: 27.7 Wh condition: 59.5/66.0 Wh (90%) volts: 7.5/7.5
model: Simplo BASE-BAT type: Li-poly serial: <filter> status: Discharging
CPU: Topology: Dual Core model: Intel Core i7-6560U bits: 64 type: MT MCP arch: Skylake
family: 6 model-id: 4E (78) stepping: 3 microcode: EA L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 17599
Speed: 500 MHz min/max: 400/3200 MHz Core speeds (MHz): 1: 500 2: 500 3: 500 4: 500
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Iris Graphics 540 vendor: Lenovo driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:1926
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: Mesa Intel Iris Graphics 540 (SKL GT3) v: 4.6 Mesa 20.3.5
direct render: Yes
Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel bus ID: 00:1f.3 chip ID: 8086:9d70
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Intel Wireless 8260 driver: iwlwifi v: kernel port: 4040 bus ID: 01:00.0
chip ID: 8086:24f3
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 238.47 GiB used: 6.07 GiB (2.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLV256HCHP-000L2 size: 238.47 GiB
block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter>
rev: 5L0QBXV7 scheme: GPT
Partition: ID-1: / raw size: 80.73 GiB size: 78.90 GiB (97.74%) used: 6.04 GiB (7.7%) fs: ext4
dev: /dev/nvme0n1p5
ID-2: swap-1 size: 7.98 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/nvme0n1p6
Sensors: System Temperatures: cpu: 37.5 C mobo: 29.8 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 224 Uptime: 31m Memory: 7.68 GiB used: 681.7 MiB (8.7%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
- Desktop settings from right mouse click flickers 5 or 6 times before opening, seems to be some type of partial window draw (real light, then brighter, then light and brighter again .
- Desktop settings - two icons on panel - one is Desktop Settings Dialog, the other and one starts MX shutdown dialog when selected ?
- Firefox - open image in new tab, then right click on the image in the second tab. The context menu stays open ONLY as long as the mouse button is depressed.
Doing the same right click on the FIRST tab window works fine.
- Also received the strange share issue I think. Going to a network share - first time opening gave me log-on dialog, filled it in, clicking on remember forever. Got same dialog again, filled it in again, then it didnt let me fill anything in, but showed a greyed out dialog again.
Dismissed it, approx 5 minutes later, tried it again on the same share and it opened right up with no login request.
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 2:41 pm
by agnivo007
@CharlesV , are you using normal mouse or touchpad?
For the flicker, have you tried window manager tweaks? Or even MX tweak > Compositor>xfwm settings>sync drawing to vblank checkbox>apply
I hope you have done a full update.
I have already reported the share dialog issue.
Re: MX-21 beta 1 feedback thread
Posted: Wed Aug 04, 2021 3:17 pm
by figueroa
fehlix wrote: Tue Aug 03, 2021 1:06 pm
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.
I suspect you are right. That may be the same mechanism that prevents and x2go remote user from editing the NetworkManager connection settings.
Still works fine in 19-4 (xfce-AHS) where I am currently logged in remotely (500 miles away) with x2go in an LXDE desktop, installing 40 updates on the school administrators desktop machine. The current version has been a joy to maintain remotely compared to the previous popular distribution.
ADDED: Back to the beta, I changed the default authorization from USER to ROOT. That works and when appropriate I am prompted for the root password and the application works as normal. But no change in the updater failing when updates are available.