Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 1:51 pm
I'll change the icon.
Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
Code: Select all
/usr/sbin/dkms: write error: Broken pipe
E: sub-process /usr/bin/dpkg returned an error code (1)
Well, I ended up installing beta2 from live media for a good surprise!dolphin_oracle wrote: Fri Jun 16, 2023 6:14 pmjust run your regular updates. I'm not changing the labels for updated systems from beta1 and beta2, but you are getting updates.gRegNfo wrote: Fri Jun 16, 2023 5:29 pm Hi there,
Can I ask a simple question here?
How can I upgrade beta1 from beta2 iso without losing my home and setings?
I didnt want to reinstall from scratch and have to handle configs again.
Thanks
once we go final all beta and rc releases will see their version strings bumped.
@operadudeoperadude wrote: Mon Jun 19, 2023 7:43 am I can't post to the Forum from VBox because Firefox keeps crashing.
Unfortunately, also having trouble with copying /var/log/mxpi(.install?) to Host machine, so I can't at this point relay relevant info from VBox environment.
Could use some suggestions about best way to set it up.
I would really like to try Beta-2 on VirtualBox, so if anyone has suggestions:![]()
Code: Select all
sudo mount -t vboxsf Host ~/Host
FWIW, I'm not having any difficulty with Firefox + beta2 + VBox. That's what I'm using to post this reply.
I had set-up VB with a shared folder, as you outlined, but I left-out the VB hint (in dialog box):m_pav wrote: Mon Jun 19, 2023 8:31 pm@operadudeoperadude wrote: Mon Jun 19, 2023 7:43 am I can't post to the Forum from VBox because Firefox keeps crashing.
Unfortunately, also having trouble with copying /var/log/mxpi(.install?) to Host machine, so I can't at this point relay relevant info from VBox environment.
Could use some suggestions about best way to set it up.
I would really like to try Beta-2 on VirtualBox, so if anyone has suggestions:![]()
Same thing I found during the builds, FF in VB is an absolute no-go and I haven't been able to find a work-around.
Set up a shared folder from your host to the virtual appliance. Machine Settings > Shared Folders > Add, set permissions and automount, provide a simple name. Keep all things the same for simplicity, we'll go with the name Host. On your daily driver, make a folder called Host and use this folder as the source, the Share name and the mount point in the VM
Boot the VM, create a new folder called Host, open a terminal and issue the command as below.This is required for running Live, but for an installed VM, you only need the VirtualBox extensions installed in the virtual OS. Personally, I never install the extension pack, I just do as above. When you're all done, you can use this folder to transfer content between the host and the guest.Code: Select all
sudo mount -t vboxsf Host ~/Host
Code: Select all
sudo mount -t vboxsf Host ~/Host
I will await the wisdom of my technological elders to approve that before doing so.Finally, is there any reason @operadude shouldn't solve his Realtek module problem by uninstalling those packages?
As a quick test (using a snapshot), sudo apt remove rtl*-dkms seemed not to cause problems, but as I say, only a quick test.
Open QSI in guest VM. Click button: Copy for Forum. Switch to host system. Open thread using Firefox (or other browser) in the host system. Paste from clipboard.operadude wrote: Tue Jun 20, 2023 2:30 am @pbear: I was trying to use copy-paste for posting my QSI, but Firefox would crash before I could even get logged-in to the Forum! If No Firefox -> No Paste!