MX-19 Beta 2.1 Feedback

[Jerry3904]

Cool, glad that helped.

[chrispop99]

Is the first user still logged in when you do this?

It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.

Could you look in session and startup for the second user. I have been messing with the desktop.defaults and it's possible.you've found a problem if the new settings have been applied.to your new user.

Specifically look.for pulseaudiostart and volumeicon

The second user has 2 pulse audio entries, although one is unchecked:

user2.png

Here is the relevant part for the first user created:

user1.png

Chris

[dolphin_oracle]

Is the first user still logged in when you do this?

It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.

Could you look in session and startup for the second user. I have been messing with the desktop.defaults and it's possible.you've found a problem if the new settings have been applied.to your new user.

Specifically look.for pulseaudiostart and volumeicon

The second user has 2 pulse audio entries, although one is unchecked:


user2.png


Here is the relevant part for the first user created:


user1.png


Chris

that's what I thought. the new user has the new defaults, but the original user doesn't, because they updated after beta 2.1 released.

when you copied over the existing config, you overwrote the volumeicon.desktop entry in ~/.config/autostart. the new version prevents volumeicon from starting, in lieu of starting it from the "pulseaudiostart" entry.

so you are starting it twice. just uncheck the "volumeicon" entry, logout, login.

[chrispop99]

Is the first user still logged in when you do this?

It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.

Could you look in session and startup for the second user. I have been messing with the desktop.defaults and it's possible.you've found a problem if the new settings have been applied.to your new user.

Specifically look.for pulseaudiostart and volumeicon

The second user has 2 pulse audio entries, although one is unchecked:


user2.png


Here is the relevant part for the first user created:


user1.png


Chris

that's what I thought. the new user has the new defaults, but the original user doesn't, because they updated after beta 2.1 released.

when you copied over the existing config, you overwrote the volumeicon.desktop entry in ~/.config/autostart. the new version prevents volumeicon from starting, in lieu of starting it from the "pulseaudiostart" entry.

so you are starting it twice. just uncheck the "volumeicon" entry, logout, login.

I just opened this to post I had tried what you have suggested!

If I uncheck the 2nd user's pulseaudio entry, so there are two entries unchecked, it all works fine even after a reboot, and whomever is logged in first.

Presumably there will be a way to fix it so that won't be needed?

Chris

[fehlix]

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 **

The closest to the mentioned requirement I can get with something like to "ignore" those which are going to be added or re-partitioned. E.g. for new or recreaterd sda4, sdas5 sda6 creating such rule

Code: Select all

echo 'KERNEL=="sda[456]", SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/00-udisk2-ignore-block.rules
udevadm control --reload; udevadm trigger --subsystem-match=block

seems to not trigger any automount. Perhaps also related to udev polling time. After removing later that rule devies are shown but automount is not triggered.

[dolphin_oracle]

It makes no difference whether you log the 2nd user in with the 1st user still logged in, or reboot and only log the 2nd user in.



The second user has 2 pulse audio entries, although one is unchecked:


user2.png


Here is the relevant part for the first user created:


user1.png


Chris

that's what I thought. the new user has the new defaults, but the original user doesn't, because they updated after beta 2.1 released.

when you copied over the existing config, you overwrote the volumeicon.desktop entry in ~/.config/autostart. the new version prevents volumeicon from starting, in lieu of starting it from the "pulseaudiostart" entry.

so you are starting it twice. just uncheck the "volumeicon" entry, logout, login.

I just opened this to post I had tried what you have suggested!

If I uncheck the 2nd user's pulseaudio entry, so there are two entries unchecked, it all works fine even after a reboot, and whomever is logged in first.

Presumably there will be a way to fix it so that won't be needed?

Chris

joys of beta. it will be fine on RC without any intervention. basically if you hadn't have copied over the stuff from your first user the second user would have been fine.

[chrispop99]

joys of beta. it will be fine on RC without any intervention. basically if you hadn't have copied over the stuff from your first user the second user would have been fine.

I'm only trying things to see if they break!

Chris

[dolphin_oracle]

joys of beta. it will be fine on RC without any intervention. basically if you hadn't have copied over the stuff from your first user the second user would have been fine.

I'm only trying things to see if they break!

Chris

and I apprecite it very much !!!!!!!!!!

that particular one won't break on release, rest assured!

[dolphin_oracle]

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 **

The closest to the mentioned requirement I can get with something like to "ignore" those which are going to be added or re-partitioned. E.g. for new or recreaterd sda4, sdas5 sda6 creating such rule

Code: Select all

echo 'KERNEL=="sda[456]", SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1", ENV{UDISKS_AUTO}="0"' > /run/udev/rules.d/00-udisk2-ignore-block.rules
udevadm control --reload; udevadm trigger --subsystem-match=block

seems to not trigger any automount. Perhaps also related to udev polling time. After removing later that rule devies are shown but automount is not triggered.

that's close. but the ones that I get asked to automount aren't the ones we are installing to anyway (there are already mounted), its other partitions and especially partitions on other devices.

[dolphin_oracle]

**never mind, I don't like what I wrote so I removed it**