MintPPC Forum - Recent Posts

RE: Full Mint Power ISO / DVD installer

admin — Mon, 13 Apr 2026 09:23:49 +0000

Did you get it sorted out?

Make Log in Screen (LightDM) use same Display Properties as When Logged in

admin — Sat, 04 Apr 2026 07:16:50 +0000

Hey everyone,

I recently figured this one out, and figured I'd document it here for posterity.

If you are anything like me, you have multiple screens rotated in different directions which works fine once logged in, but your log-in screen is all messed up.

As an example, here is how I have my screens set up in Cinnamon:

A 20" 1600x1200 screen in portrait rotated counter clockwise on the left
A 43" 3840x2160 screen in lanscape in the center
Another 20" 1600x1200 screen in portrait rotated clockwise on the right.

Lets just say that on the system login screen (LightDM) the screens are not configured like this, and if you knock your mouse pointer off the center one, it can be surprisingly difficult to get it back, tilting your head sideways and trying to navigate the pointer to the right place.

It also looks cleaner if your login matches the layout you want, so here is how to achieve that.

1.) Configure your screens how you want them in the Display properties settings.

2.) Install and use arandr to create an xrandr string from your preferred layout.

Open a terminal and do the following:

Code: Select all

sudo apt update
sudo apt install arandr

Run arandr from the GUI menu:

You should see your screen layout as you have it configured.

If you are happy with it as is, then save it to an xrandr string:

Layout Menu -> Save As

Save it somewhere you know where it is, and name it something nice. I chose to put it on my Desktop and name it "lightdm_xrandr.sh"

3.) Prepare the file containing your xrandr string for use:

The file contained my somewhat semi-complicated xrandr string:

Code: Select all

#!/bin/sh
xrandr --output DisplayPort-0 --primary --mode 3840x2160 --pos 1200x0 --rotate normal --output DisplayPort-1 --mode 1600x1200 --pos 0x560 --rotate left --output DisplayPort-2 --off --output HDMI-A-0 --mode 1600x1200 --pos 5040x560 --rotate right

Unless you have the exact screen layout I do, yours will look different.

For good measure I decided to edit it and add an "exit 0" to the end. This is probably not necessary, but it is proper.

Code: Select all

sudo nano ~/Desktop/lightdm_xrandr.sh

Code: Select all

#!/bin/sh
xrandr --output DisplayPort-0 --primary --mode 3840x2160 --pos 1200x0 --rotate normal --output DisplayPort-1 --mode 1600x1200 --pos 0x560 --rotate left --output DisplayPort-2 --off --output HDMI-A-0 --mode 1600x1200 --pos 5040x560 --rotate right
exit 0

after saving, we should check to make sure it is executable. arandr seems to do this by default, but it doesn't hurt to check:

Code: Select all

# ls -l ~/Desktop/lightdm_xrandr.sh
-rwx------ 1 matt matt 263 Oct 22 23:38 lightdm_xrandr.sh

-rwx------ -> Read Write eXecute. Permissions are correct (in Mints default bash config the file should also be listed as green if it is executable)

If it is not executable you can make it so with the following command:

Code: Select all

chmod 700 ~/Desktop/lightdm_xrandr.sh

Then move this script to /etc/lightdm

Code: Select all

sudo mv ~/Desktop/lightdm_xrandr.sh /etc/lightdm/

So now we have a "script" that sets the proper screen orientation. Now we have to tell lightdm to execute it on startup.

4.) Tell lightdm to execute your xrandr string on boot:

First we have to find the config file. Since the file may differ by version or specific configuration, rather than tell you which file I edited, I will show you how to find yours, just in case yours is different.

Run lightdm --show-config to display the current configuration.

Code: Select all

# lightdm --show-config

   
A  allow-guest=false
C  greeter-wrapper=/usr/lib/lightdm/lightdm-greeter-session
D  guest-wrapper=/usr/lib/lightdm/lightdm-guest-session
E  xserver-command=X -core
F  greeter-session=slick-greeter
G  user-session=cinnamon

   
B  backup-logs=false

Sources:
A  /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
B  /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
C  /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
D  /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
E  /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
F  /usr/share/lightdm/lightdm.conf.d/90-slick-greeter.conf
G  /etc/lightdm/lightdm.conf.d/70-linuxmint.conf

Look for a config file that says something about "slick greeter". In my case this was:
/usr/share/lightdm/lightdm.conf.d/90-slick-greeter.conf

Edit this file:

Code: Select all

# sudo nano /usr/share/lightdm/lightdm.conf.d/90-slick-greeter.conf

By default it should look like this:

Code: Select all


greeter-session=slick-greeter

Add this line between and greeter-sessiion as follows:

greeter-setup-script=/etc/lightdm/lightdm_xrandr.sh

Code: Select all


greeter-setup-script=/etc/lightdm/lightdm_xrandr.sh
greeter-session=slick-greeter

Reboot. Your login screen should now be oriented the same as your desktop once logged in.

I hope this helps someone else.

RE: Installation problems.

admin — Fri, 27 Mar 2026 23:54:17 +0000

I will add those required packages and then we will see if you can downgrade mesa. I will do it later today, I will tell you when it’s done.

Edit: it should work now

RE: Installation problems.

Kristoffer Fin — Fri, 27 Mar 2026 18:09:51 +0000

@admin

Thank you,

Installation went PERFECTLY on my FireWire SSD. Boots fine.

But Mesa libs still are problematic

root@debian:/home/g5# chmod u+x mesa-64

root@debian:/home/g5#./mesa-64

Hit:1 http://deb.debian.org/debian-ports sid InRelease

Hit:2 http://deb.debian.org/debian-ports unreleased InRelease

Hit:3 Hit:4 http://u58733p55594.web0093.zxcs-klant.nl/repo-64 unstable InRelease http://u58733p55594.web0093.zxcs-klant.nl/xeno74./ InRelease

Get:5 http://u58733p55594.web0093.zxcs-klant.nl/mesa-64./ InRelease

Get:6 http://u58733p55594.web0093.zxcs-klant.nl/mesa-64./ Packages [4,419 BJ

Fetched 6,505 B in 14s (481 B/s)

All packages are up to date.

Warning: Skipping acquire of configured file 'main/source/Sources' as repository 'http://deb.debian.org/debian-ports sid InRelease does not seem to prow

Solving dependencies... Error!

Notice: Some sources can be modernized. Run 'apt modernize-sources to do so.

Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.

The following information may help to resolve the situation:

Unsatisfied dependencies:

libegl-mesa: Depends: libglapi-mesa (= 24.1.6-1) Depends: libxcb-dri2-0 (>= 1.8) but it is not going to be installed

libgll-mesa-dri: Depends: libglapi-mesa (= 24.1.6-1) Depends: libllvm17t64 but it is not installable

libglx-mesa Depends: libglapi-mesa (= 24.1.6-1)

Depends: libxcb-dri2-0 (>= 1.8) but it is not going to be installed mesa-va-drivers: Depends: libllvm17t64 but it is not installable

Depends: libxcb-dri2-0 (>= 1.8) but it is not going to be installed mesa-vdpau-drivers: Depends: libvdpaul but it is not going to be installed

Depends: libllvm17t64 but it is not installable

Depends: libxcb-dri2-0 (>= 1.8) but it is not going to be installed mesa-vulkan-drivers: Depends: libllvm17t64 but it is not installable

Error: Unable to satisfy dependencies. Reached two conflicting assignments:

1. mesa-va-drivers:ppc64-24.1.6-1 is selected for install

but none of the choices are installable:

2. mesa-va-drivers:ppc64-24.1.6-1 Depends libllvm17t64

libegl-mesa set on hold.

libgbml set on hold.

libgll-mesa-dri set on hold.

libglx-mesae set on hold.

mesa-va-drivers set on hold.

mesa-vdpau-drivers set on hold.

mesa-vulkan-drivers set on hold.

root@debian:/home/g5# nano /etc/apt/sources.list

root@debian:/home/g5#

RE: Installation problems.

admin — Fri, 27 Mar 2026 07:08:54 +0000

Try again, I think I fixed it. The mesa problem should be gone now, as well as the sylpheed problem.

RE: Installation problems.

admin — Fri, 27 Mar 2026 03:11:48 +0000

I will replace sylpheed with claws-mail. It is another lightweight email client which is still supported in Debian sid.

RE: Installation problems.

admin — Fri, 27 Mar 2026 01:45:25 +0000

@eastone mesa can’t be built right now on ppc64 (since a long time, I will look into this):

https://buildd.debian.org/status/package.php?p=mesa&suite=sid

RE: Installation problems.

admin — Fri, 27 Mar 2026 01:41:29 +0000

@eastone thanks for testing! I just noticed that Debian removed sylpheed from sid, therefore it can’t be installed anymore. I will remove sylpheed from the package list in the preseed file.

RE: Installation problems.

Kristoffer Fin — Thu, 26 Mar 2026 15:23:56 +0000

And Mesa problem:

root@debian:/home/g5#./mesa-64

Hit:1 http://deb.debian.org/debian-ports sid InRelease

Hit:2 http://deb.debian.org/debian-ports unreleased InRelease

Hit:3 http://u58733p55594.web0093.zxcs-klant.nl/repo-64 unstable InRelease

Hit:4 http://u58733p55594.web0093.zxcs-klant.nl/xeno74./ InRelease

Get:5 http://u58733p55594.web0093.zxcs-klant.nl/mesa-64./ InRelease Get:6 http://u58733p55594.web0093.zxcs-klant.nl/mesa-64./ Packages

Fetched 6,505 B in 14s (468 B/s)

All packages are up to date.

Warning: Skipping acquire of configured file 'main/source/Sources' as repository 'http://deb.debian.org/debian-ports sid InRel (sources.list entry misspelt?)

t Notice: Some sources can be modernized. Run 'apt modernize-sources to do so. Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created

or been moved out of Incoming. The following information may help to resolve the situation:

Unsatisfied dependencies:

libegl-mesao: Depends: libglapi-mesa (= 24.1.6-1) Depends: libxcb-dri2-0 (>= 1.8) but it is not going to be installed

libgll-mesa-dri: Depends: libglapi-mesa (= 24.1.6-1) Depends: libllvm17t64 but it is not installable

libglx-mesa Depends: libglapi-mesa (= 24.1.6-1)

Depends: libxcb-dri2-0 (>= 1.8) but it is not going to be installed mesa-va-drivers: Depends: libllvm17t64 but it is not installable

Depends: libxcb-dri2-0 (>= 1.8) but it is not going to be installed mesa-vdpau-drivers: Depends: libvdpaul but it is not going to be installed Depends: libllvm17t64 but it is not installable Depends: libxcb-dr12-0 (>= 1.8) but it is not going to be installed

mesa-vulkan-drivers: Depends: libllvm17t64 but it is not installable Error: Unable to satisfy dependencies. Reached two conflicting assignments:

1. mesa-va-drivers:ppc64-24.1.6-1 is selected for install

2. mesa-va-drivers:ppc64-24.1.6-1 Depends libllvm17t64 but none of the choices are installable:

Error: Invalid operation hold root@debian:/home/g5#

RE: Installation problems.

Kristoffer Fin — Thu, 26 Mar 2026 15:21:57 +0000

I can't attach a picture, so these are the last lines of installation progress:

Mar 26 11:43:18 in-target: Updating certificates in /etc/ssl/certs...^M

Mar 26 11:43:21 in-target: added, e removed; done. M

Mar 26 11:43:21 in-target: Running hooks in /etc/ca-certificates/update.d...^M

Mar 26 11:43:21 in-target: done.^M

Mar 26 11:43:21 in-target: Processing triggers for libc-bin (2.42-13)...

Mar 26 11:43:21 in-target: M

Mar 26 11:43:22 pkgsel: installing additional packages

Mar 26 11:43:23 /bin/in-target: warning: /target/etc/mtab won't be updated since it is a symlink.

Mar 26 11:43:24 in-target: Reading package lists...

Mar 26 11:43:24 in-target: Mar 26 11:43:24 in-target: Building dependency tree...

Mar 26 11:43:25 in-target: Mar 26 11:43:25 in-target: Reading state information...

Mar 26 11:43:25 in-target:

26 11:43:25 in-target: Package sylpheed is not available, but is referred to by another package.

Mar Mar 26 11:43:25 in-target: This may mean that the package is missing, has been obsoleted, or

Mar 26 11:43:25 in-target: is only available from another source

Mar 26 11:43:25 in-target:

Mar 26 11:43:25 in-target: E: Package 'sylpheed' has no installation candidate

Mar 26 11:43:26 /bin/in-target: warning: /target/etc/mtab won't be updated since it is a symlink. : ISO 9660 Extensions: Microsoft Joliet Level 3

Mar 26 11:43:30 kernel

Mar 26 11:43:30 kernel: ISO 9660 Extensions: RRIP_1991A

Mar 26 11:43:30 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3

Mar 26 11:43:30 kernel: ISO 9660 Extensions: RRIP_1991A

Mar 26 11:43:30 main-menu : WARNING **: Configuring 'pkgsel' failed with error code 100

Mar 26 11:43:30 main-menu : WARNING **: Menu item 'pkgsel' failed.