Page 16 of 60

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 8:28 pm
by dolphin_oracle
fehlix wrote: Mon Sep 09, 2019 8:25 pm
dolphin_oracle wrote: Mon Sep 09, 2019 8:21 pm we didn't forget. partprobe triggers automounting of partitions, asking for passwords over and over again, which is really annoying when you have a lot of partitions.
I know, but when user pressed "close" partprobe is not triggered.

see edits above. its intentional.

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 8:32 pm
by dolphin_oracle
just tried the udisks2-inhibit approach. close out early still triggers an attempt to automount every partition in the machine. and those that don't require root passwords get automounted.

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 8:39 pm
by dolphin_oracle
fehlix, the real question is...can be block just automounting without actually blocking devices?

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 8:41 pm
by fehlix
dolphin_oracle wrote: Mon Sep 09, 2019 8:32 pm just tried the udisks2-inhibit approach. close out early still triggers an attempt to automount every partition in the machine. and those that don't require root passwords get automounted.
Propably, but I was not talking about automount after closing. Rather about current minstall does not allow to mount with thunar after closing. But prevents any automount during the run of minstall even without the udev-rules used within minstall at all.

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 8:42 pm
by fehlix
dolphin_oracle wrote: Mon Sep 09, 2019 8:39 pm fehlix, the real question is...can be block just automounting without actually blocking devices?
is this meant during the "run" of minstall or after.

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 8:44 pm
by dolphin_oracle
fehlix wrote: Mon Sep 09, 2019 8:42 pm
dolphin_oracle wrote: Mon Sep 09, 2019 8:39 pm fehlix, the real question is...can be block just automounting without actually blocking devices?
is this meant during the "run" of minstall or after.
either way would actually work. during the active minstall run would mimic what we have in 18.3 by just disabling Xfce's automount.

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 9:00 pm
by dolphin_oracle
fehlix wrote: Mon Sep 09, 2019 8:42 pm
dolphin_oracle wrote: Mon Sep 09, 2019 8:39 pm fehlix, the real question is...can be block just automounting without actually blocking devices?
is this meant during the "run" of minstall or after.
what do you think of something like this, if it even still works. got it out of the depths of stackoverflow.

Code: Select all

echo 'SUBSYSTEM=="block", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/90-udisks-inhibit.rules
supposedly that disables automounting. it certainly leaves the list in place in thunar.

i tried with gparted in my test suite with some success, but I need more data points.

**never mind, didn't work in practice **

Re: MX-19 Beta 2.1 Feedback

Posted: Mon Sep 09, 2019 9:31 pm
by JayM
I've edited my post #106 on page 11 to make it clearer what the problem is. I originally posted it yesterday evening and upon rereading it this morning I realized that other people might not be able to understand what problem I was reporting. It seems that the x server isn't detecting my external monitor though Xfce detects it.

Re: MX-19 Beta 2.1 Feedback

Posted: Tue Sep 10, 2019 12:47 am
by cristianmaral
I have just installed the latest MX Linux Beta ISO and I have found an issue.

Window cycling is just showing active windows, the minimized ones are not getting shown on Alt+Tab.

Is there a way to fix this problem?

Thanks in advance.

Edit: Fixed when checked the option "Include hidden (i.e. iconified) windows" on Window Manager Tweaks.

Re: MX-19 Beta 2.1 Feedback

Posted: Tue Sep 10, 2019 4:30 am
by JayM
I just tried changing to the Intel video driver instead of modset in MX Tweaks: no change after restarting. Also I found that the 1280x1020 resolution is still not showing up in QSI after using MX Tweak to change the panel to horizontal and back, which causes the panel to appear as normal on the external monitor for my current session (it doesn't survive a reboot or log out/log in.)