MX Linux Forum

Thank you for pointing out that the clock is the XFCE datetime plugin. I assumed it was orage, because that's somehow what's on my mx-18.3 install. I'll use orage instead, so I easily remove the week numbers.

chrispop99 wrote: Wed Sep 11, 2019 12:00 pm

dolphin_oracle wrote: Wed Sep 11, 2019 10:41 am Chris, let's try purging off and putting it back.

first purge off

Code: Select all

sudo ddm-mx -p nvidia

then reboot (probably not necessary but safer).

then run the apt-get command instead of ddm-mx, and post output.

you will need to purge off nvidia-persistenced, and it probably wouldn't hurt to do a "dpkg-configure -a" after that, just to make sure things are all nice and tidy.

I took the cautious approach, and did a fresh install. I then ran:

Code: Select all

sudo apt-get install --install-recommends --reinstall bumblebee-nvidia nvidia-legacy-390xx-driver primus primus-libs-ia32:i386 nvidia-settings virtualgl virtualgl-libs:i386

It returned this error:

Code: Select all

The following packages have unmet dependencies:
 nvidia-legacy-390xx-driver : Depends: nvidia-legacy-390xx-driver-libs (= 390.116-1) but it is not going to be installed or
                                       nvidia-legacy-390xx-driver-libs-nonglvnd (= 390.116-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Chris

ok good. now drop nvidia-settings out of that list.

dolphin_oracle wrote: Wed Sep 11, 2019 12:27 pm

chrispop99 wrote: Wed Sep 11, 2019 12:00 pm

dolphin_oracle wrote: Wed Sep 11, 2019 10:41 am Chris, let's try purging off and putting it back.

first purge off

Code: Select all

sudo ddm-mx -p nvidia

then reboot (probably not necessary but safer).

then run the apt-get command instead of ddm-mx, and post output.

you will need to purge off nvidia-persistenced, and it probably wouldn't hurt to do a "dpkg-configure -a" after that, just to make sure things are all nice and tidy.

I took the cautious approach, and did a fresh install. I then ran:

Code: Select all

sudo apt-get install --install-recommends --reinstall bumblebee-nvidia nvidia-legacy-390xx-driver primus primus-libs-ia32:i386 nvidia-settings virtualgl virtualgl-libs:i386

It returned this error:

Code: Select all

The following packages have unmet dependencies:
 nvidia-legacy-390xx-driver : Depends: nvidia-legacy-390xx-driver-libs (= 390.116-1) but it is not going to be installed or
                                       nvidia-legacy-390xx-driver-libs-nonglvnd (= 390.116-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Chris

ok good. now drop nvidia-settings out of that list.

Still gives the dependencies error.

Chris

In the dropdown terminal, the tabs don't fit into the panel where they are shown (they are slightly bigger).

As odd as it may seem...

Setting the MX panel to horizontal with extended to both monitors, has the menu (alt) showing up on the external monitor (right where i want it to be) while the conky stays on the default laptop monitor (which is also where i want it to be at every boot time).

So, even if (for the moment) alt+ no longer works to move the conky, i got what i wanted.

All swell, that ends well...

Using disk manager to mount a partition on another drive works as in 18.3 asking for a root password and modifies fsatb as follows:
Upon a cold boot the fstab entry is identical but when attempting to access the same partition it is not mounted and password entry is again required to mount it. In 18.3 it would be automounted on a cold boot.
I was surprised to see the vfat entry as the file system as it is formatted ext4 as gparted shows. Also it is sd3 not sd1

Nevermind

Here is the fstab entry in 18.r where it is automounted.

can you show a screen shot of disk manager?

18.3
MX-19beta-2.1
I see the problem the UUID for data partition in 18.3 is identical to the UUID for the 512MB vfat partiton. Not sure if changing the partition UUID in 19 beta to the one in 18.3 would resolve the problem.
And more to the point for feedback why it happened.
Other than having to mount the partition at each boot the Data partition acts normally in when mounted.