MX Linux Forum

I have a problem with the MX19Beta, I'm not sure it is a bug, or just a way that the new version of the underlying code reacts to a USB item being plugged in. In any case, the upshot is that my One4All Remote URC6440 does not mount under MX19 though it does under MX18.

Because I'm not sure if it's a bug, I've posted under Hardware as well. I would be grateful to find out if anyone knows the answer to this. Link to other post:

viewtopic.php?f=107&t=52525

I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap. Have there been any reported issues with this?

D

blindside wrote: Fri Sep 06, 2019 4:50 am I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap. Have there been any reported issues with this?

D

Not that I've seen, but you can find out yourself by reading the MX-19 Beta 1 Feedback topic (to which this post should probably be moved?)
viewtopic.php?f=94&t=52318

Topics merged. I hope I did that right..

blindside wrote: Fri Sep 06, 2019 4:50 am I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap. Have there been any reported issues with this?

D

Sounds like it may be in use by the installer - I had to unmount & use swapoff on one of my 4 installs - this is the one usage that shouldn't have automount activated.

Actually now that you mention that.. I saw something like that too sometime. I don't remember if it was during the actual install or during the assigning of the partitions though.

*note to self: pay attention on the next beta install!*

I thought the latest version of the installer which should be part of the beta did a swapoff already.

@blindside: It would be nice if you could open a terminal and run then copy everything in the terminal and paste it here inside of code tags.

Eadwine Rose wrote: Fri Sep 06, 2019 6:26 am Actually now that you mention that.. I saw something like that too ...
*note to self: pay attention on the next beta install!*

In my case it was whilst I was trying to assign the partitioning - but 3 of the 4 installs, I didn't have any bother from it.

JayM wrote: Fri Sep 06, 2019 6:33 am I thought the latest version of the installer which should be part of the beta did a swapoff already.

@blindside: It would be nice if you could open a terminal and run

Code: Select all

sudo minstall -E

then copy everything in the terminal and paste it here inside of code tags.

I will do that tonight. Just for reference, this is a newly installed nvme drive that was running Debian testing flawlessly. Also, I assume you want me to open a terminal in live?

update the installer before trying again. also, "sudo -E" won't work. just run "minstall-pkexec" from the commandline. or just "sudo minstall".