MX-19 RC1 Feedback thread

[ChrisUK]

So, I did a test install (System info not relevant for this post) to test out the "Preserve Home" option, but when Home is on root, not a separate partition... a couple of points:

• Installer asks if you want to preserve Home - selected this option.
• When install nearly complete, you get a rather confusing Dialog - something like (I forgot to screenshot) "Home dir already exists" [reuse] [delete] [save] [cancel]
• I figured "reuse" was the correct choice, but why am I being asked again? I selected "save", as I thought some might select that instead of "reuse" as some might fear "reuse" would delete existing contents.
• After booting new install, faced with a standard Desktop, my Home was now a nice new clean Home... none of my settings or data etc. However, browsing I find my old Home exists, but with the ".001" extension. So I needed to delete say "/home/chris" and delete the extension from the Home I expected to find.

So, thinking about it, I guess the installer did actually do what I asked, but maybe not what I expected. Anyway, easy enough for me, but not, I suspect, for any newish users.

[Adrian]

I figured "reuse" was the correct choice, but why am I being asked again? I selected "save", as I thought some might select that instead of "reuse" as some might fear "reuse" would delete existing contents.

It might need clarification. You preserve /home but that doesn't mean that automatically you are going to us the same username, so when you enter the user information if the username is the same as the one one /home it asks what you want to do: reuse the old me, save it to a .001 folder or delete (probably it should not offer delete option since you wanted to preserve it, cancel also, what it does when you cancel? So yes, there's room for improvement.

[BitJam]

Would you mind trying the new vcard=menu boot option and select the found nvidia card.

Hey fehlix, I tried the vcard=menu boot option...both with persistence and no persistence
-Detected the card correctly...yes!
-Then, I selected that card...
-Then unfortunately, I was sent to terminal login prompt, no gui

I looked in /blah/blah/Live-usb/Live-usb-storage/ but could not identify a log that made any sense

...tell me where to look for a log and I will post

Thanks for testing!

When it boots correctly, what is the output of "inxi -Gxx"?

The relevant log file is /var/log/Xorg.0.log but this is not saved under ~/Live-usb-storage/live-logs/. Maybe I should fix that. But I don't think that file would help ATM.

Ah, yes. I think I know what went wrong. The problem is that since you installed the nvidia driver there is a battle between the nvidia driver and the nouveau driver for control over the Nvidia hardware. The vcard=menu does not resolve this conflict and hence the blank screen. When you used "xorg=nvidia", this did resolve the conflict and allowed the nvidia driver to take precedence.

ISTM one way out of this mess is to detect this situation (Nvidia card selected and both nivdia and nouveau drivers available) then offer a 2nd menu. What do you think of this idea?

In fact, even if there is just one video card, if it's Nvidia then we could still offer this nvidia/nouveau menu when both drivers are available.

We could also try defaulting to "nvidia" if both nvidia and nouveau drivers are detected.

[fehlix]

Would you mind trying the new vcard=menu boot option and select the found nvidia card.

Hey fehlix, I tried the vcard=menu boot option...both with persistence and no persistence
-Detected the card correctly...yes!
-Then, I selected that card...
-Then unfortunately, I was sent to terminal login prompt, no gui

I looked in /blah/blah/Live-usb/Live-usb-storage/ but could not identify a log that made any sense

...tell me where to look for a log and I will post

Thanks for testing!

When it boots correctly, what is the output of "inxi -Gxx"?

The relevant log file is /var/log/Xorg.0.log but this is not saved under ~/Live-usb-storage/live-logs/. Maybe I should fix that. But I don't think that file would help ATM.

Ah, yes. I think I know what went wrong. The problem is that since you installed the nvidia driver there is a battle between the nvidia driver and the nouveau driver for control over the Nvidia hardware. The vcard=menu does not resolve this conflict and hence the blank screen. When you used "xorg=nvidia", this did resolve the conflict and allowed the nvidia driver to take precedence.

ISTM one way out of this mess is to detect this situation (Nvidia card selected and both nivdia and nouveau drivers available) then offer a 2nd menu. What do you think of this idea?

In fact, even if there is just one video card, if it's Nvidia then we could still offer this nvidia/nouveau menu when both drivers are available.

We could also try defaulting to "nvidia" if both nvidia and nouveau drivers are detected.

Sounds good. ... perhaps also checking powerstate via vgaswitcheroo in case nvidia is in Off state to allow it to turn On, and if in DynOff state user need to reboot to have be able to turn it On .. (after we first turned if Off , I know.. sounds weird) EDIT: that's only for those dual-cards where nvidia stays on powerOff

[Paul..]

When it boots correctly, what is the output of "inxi -Gxx"?

Glad to help as always...Booting from MX19rc installed on metal...here it is

Code: Select all

inxi -Gxx
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: ASUSTeK driver: nvidia v: 435.21 
           bus ID: 09:00.0 chip ID: 10de:1380 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 
           direct render: Yes 

[gimbleguy]

When I check for update, it shows I have one update. But after that it shows none.

https://youtu.be/-VSp4T0qhsY

I'm using Virtualbox.
HostOS: Windows 10
GuestOS: MXlinux 19RC1

[dolphin_oracle]

do an apt-get dist-upgrade.

someone else reported that package being held back. it shouldn't be, but I think the updater is flagging it because the update removes a different package and installs a new one.

[gimbleguy]

still the same issue. dist-upgrade doesn't do any thing :(

[micronaut]

Can't create pp2p vpn connection:

WARNING **: 22:28:03.161: Could not load editor VPN plugin for “org.freedesktop.NetworkManager.pptp” (missing plugin file "/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-vpn-plugin-pptp-editor.so").

[Srdjan]

I think network-manager-pptp-gnome package holds that plugin.