MX-19 Beta 2.1 Feedback

[timkb4cq]

Only problem so far on mx19beta2.1 unable to access any of my 3 iPads or 2 iPhones![/b][/u] Using “idevice” but no problem on any of my mx18.3

It worked in betaa1 but it doesn't on beta2.1 or 3.
Debian changed the 39usbmuxd udev rules to not include bare udev anymore. Every stanza in that file refers to usbmuxd.service.
Fortunately, the old version of that file still works - both when MX is booted in sysvinit and when systemd is chosen so I just need to rebuild the usbmuxd package with that patched.

[winemaker]

i appreciate your and others people's hard work here! looking forward to 19 after a pleasant 18.3 intro to MX!

[davemx]

A weird one this. I've been having a problem with the switch to MX18, that my USB remote controls URC6440 and OARUSB04G (essentially the same unit) were no longer automounted under MX19. But this is also true in many distros, and I think it's due to its nonstandard (to say the least) partitioning. In the end, I believe it's not a bug, just the system not welcoming access by a nonstandard item. Anyway I came up with a way of getting it to mount automatically in MX19ß, and it also works in PCLinuxOS.

The issue is that, although it is mounted under ownership of the user, in MX19 (but not in PCLOS) it demands the root password when I attempt to unmount it for the first time in a session.

The code I used to get it to automount in the first place is described here: http://www.hifi-remote.com/wiki/index.p ... with_Linux

I'm at a loss as to why the root password is demanded to unmount it, is it a bug?

[asqwerth]

... Anyway I came up with a way of getting it to mount automatically in MX19ß, and it also works in PCLinuxOS.

The issue is that, although it is mounted under ownership of the user, in MX19 (but not in PCLOS) it demands the root password when I attempt to unmount it for the first time in a session.

The code I used to get it to automount in the first place is described here: http://www.hifi-remote.com/wiki/index.p ... with_Linux

I'm at a loss as to why the root password is demanded to unmount it, is it a bug?

It could be due to differences in UID and GID numbers of both distros. MX, like a lot of Debian/Ubuntu-based distros, has a UID and GID of 1000.

PCLOS is 500.

Even if the text username looks the same, so long as the UID/GID is different, it's deemed a different user. So if say you first created/formatted the device in distro 1, then tried to access the device in distro 2 with a different UID/GID, you might not be allowed - as a different user - to access the device from distro 2 without root.

I faced that issue when I couldn't figure out why I couldn't write to my Data partition, created while using Mint (UID 1000), while running in PCLOS without root no matter how many times I edited my PCLOS fstab. It just stubbornly kept being Read-Only. Finally I changed the UID and GID of PCLOS to 1000 to match my other distros, after which it worked.

[kajukenbo]

I do have an issue with suspend and hibernate. Neither seem to work as I suspect when closing the lid. The computer stays awake and the screen turns right back on after I open the lid, but then no actions work (all keyboard and mouse input is ignored until I hit Ctrl+Alt+Backspace and log back in).

Take a look at Settings > Power Manager.

Not just you. It frequently does the same thing to me when the screen saver (blank) triggers.
I open the lid and it looks like my Firefox session is still open but I cannot move the mouse to any effect.
Occasionally I've been able to enter my password into the "lock screen" that isn't visible and it works again.
I deliberately turned Suspend & Hibernate off. Same behavior.
The only work-around I've found is to turn off the lock screen functionality. Not great for security.
It might be coincidence but it seemed like it went to the Lock/Login screen once when I may have been sitting in a terminal window instead of the browser.
I did not work too hard to reproduce it.

I've also seen the issue that has been reported where muting the audio doesn't change the icon.
The only work-around I've found is to turn the Compositing Window Manager back on.
I usually turn it off because I don't care about fancy; I want FAST.
I would prefer separate Right (slider), Left (mute), and Middle click (menu) options for the audio icon as well.

[richb]

Thread Closed with Release of MX-19 Beta 3