New Mint cursor themes

After upgrading your packages you will be able to select the latest mint-cursor-themes. You can do this by opening LXappearance from the menu (Customize Look and Feel) and change the cursor to Bibata Modern Classic. You will have to log out from the Mint-LXDE session and log back in to have it working across all applications. Your desktop will now look like the latest Linux Mint.

Published by admin

Developer of MintPPC

Join the Conversation


  1. After update the mint theme package, there is booting issue. The new splash screen shows after LMDE grub menu, and the black screen with unable to locate GPU BIOS ROM ERROR message appears. No LXDM loaded and I need to press main power button to let it shut down. I press ESC to bypass the splash screen at second boot, it loads LXDM successfully after boot messages screen. I don’t know if this problem caused by the splash or GPU driver as the splash screen is blue tinted. Color distorted and made the splash all blue with LM logo light purple.

    1. Just modified the /etc/default/grub file and remove ‘quiet” after the GRUB parameter, update the grub file and reboot, splash still appears.

  2. You could try to remove plymouth, but only if it does not remove all kinds of other importamt packages. What is the output of:
    apt-cache depends plymouth

    1. Here is the output:
      Depends: init-system-helpers
      |Depends: initramfs-tools
      Depends: dracut
      Depends: lsb-base
      Depends: systemd
      Depends: udev
      Depends: libc6
      Depends: libdrm2
      Depends: libplymouth5
      Conflicts: console-common
      Breaks: mawk
      Breaks: plymouth-themes
      Suggests: desktop-base
      Suggests: plymouth-themes
      Replaces: plymouth-themes

    1. no effects with the kernel parameters above, even remove the parameter “quiet splash” in /etc/default/grub and perform sudo update-grub2, after reboot and check the grub menu, “quiet splash” still exists after the linux command. I checked all the debian distribution and all the methods are the same.

    1. If use edit function in grub boot menu to remove “splash”, Splash screen turns off and it shows the systemd boot message

    1. it’s Apple iBook G4, before update the mint theme related packages splash is turned off by default, another problem that made me confusing long time is the blue tinted display problem. The graphic/video works normally on VLC(now broken dependencies and can’t install again) and smplayer, etc. When use ristretto image viewer to see photo preview the photo will get blue tinted and high brightness effect, the same problem won’t appear on gpicviewer. Also if I use Sealion with viewtube plugin to play video directly, the video will get blue tinted and hue ran off setting. The video can be played correctly with smplayer. So I suspect the splash problem is caused by radeon driver setting as splash screen is blur tinted with wrong hue setting also.

    2. I check the /var/log/boot.log after make an unsuccessful boot up, the plymouth-quit-wait.service just hold until boot process finishes up, LXDM process started before it. There is some problem blocks plymouth-quit-wait service to hand over the process to LXDM

  3. There should be a way to remove splash from the kernel arguments by default after editing the configuration file. Maybe update-grub instead of update-grub2?

    1. I tried both update-grub and update-grub2 already, still can’t alter the code shown in grub when press ‘e’

    1. Thanks, he got the lxdm working after plymouth splash screen or he can disable splash successfully?

    1. After some research I found a similar case of grub setup problem:

      It seems the /etc/default/grub.conf cannot generate update script to cover /boot/grub/grub.cfg even use update-grub or update-grub2 function, I used the suggestion to make grub.cfg writable and remove “splash” after the linux command line, now the splash disabled and boot process works again.

      1. First run “sudo dpkg –list | grep linux-image” and purge the unused kernel with sudo apt-get purge [package-name]” where “[package-name]” is replaced with the name of the package you want to remove. Then, if you want to get rid of the splash screen, “sudo nano /etc/default/grub” and change GRUB_DEFAULT=1 and GRUB_TIMEOUT=0.

          1. I found the cause why I modified /etc/default grub and no effect on /boot/grub/grub.cfg, there is a folder grub.d in /etc/default, inside the folder there are 2 cfg files, one is 50_lmde.cfg and the other is 60_mint_theme.cfg, I think the following code in 50_lmde.cfg is the cause of problem:

            # Use a plymouth splash by default
            # In EFI mode, when grub-efi-amd64 is installed, it removes grub-pc
            # grub-pc’s postinst has some unwanted conffile management which removes
            # /etc/default/grub, thus removing “quiet splash” from grub.
            # Setting it here ensures we continue to have a splash, whether or not
            # /etc/default/grub is present.

            GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”

            Before I found this file I upgrade the system kernel to 6.5.0-2 to see if it has kernel panic or not. Splash appears again when reboot to 6.5 kernel so I think there is some files which can bypass the /etc/default/grub setting and use it’s default setup to update grub file. Hope this will help.

  4. For your information:
    The kernel panic problem in 6.5.0-1 has been picked up in the Debian powerpc mailing list. Some people are reporting it upstream to the kernel developers. Apparently the 6.6 and 6.4 kernels do not have this problem.

    1. Use Synaptics to check the latest linux-image-powerpc, latest kernel version is 6.5.0-2, may be the bug fix version of 6.5.0-1.

      1. Yes indeed, 6.5.0-2 fixed the bug. I now have MintPPC running on my humble G4 Quicksilver using the default kernel. I’m writing this comment on it now.

  5. Well thank you Poe, the information you gave me about this grub.d directory is probably the cause of it indeed. I can fiddle around the source code and recompile a version that takes away this 50_lmde.cfg configuraton file. Hopefully it will be solved then. To be continued…It may take a few days though as I am admitted into the hospital with a blood infection. 🙁

    1. Take care, there is solution so recompile the code is not the urgent case. Health is important than these stuff.

  6. Ok, I found a solution as written in the link. I will change the code in debian-system-adjustments soon, recompile and upload to the server. The problem should then disappear. Do you guys prefer “quiet” or nothing. In the latter case you see the full systemd boot output.

  7. I just upgraded a freshly installed MintPPC system on a PowerBook G4 with a Radeon graphics card. After booting into the new kernel 6.5.0-2, I got a working splash and it went straight into LXDM without a problem. I guess I have a different GPU than yours. I will however still amend debian-system-adjustments.
    OS: Debian GNU/Linux trixie/sid ppc
    Host: PowerBook5,6
    Kernel: 6.5.0-2-powerpc
    CPU: 7447A (1) @ 1.666GHz
    GPU: AMD ATI Mobility Radeon 9600

    1. My iBook G4 has a ATI Mobility Radeon 9550 GPU so may be the different of chipset leads the splash/blue tinted screen problem. Another possibility is that my mintppc system is upgrade from kernel 5.X.X (debian 10) and changed from SID to Trixie so the system may have some incompatibilities for such long time of system upgrade.

  8. Well, I updated debian-system-adjustments. It worked but I started fiddling with grub-customizer and now I can’t write anymore in /boot/grub/grub.cfg. It complains about a read only file system. I don’t know what to do in this test system. Any idea?

    1. I check the cfg file using the following command:
      sudo chmod u+w /boot/grub/grub.cfg
      sudo mousepad /boot/grub/grub.cfg
      after finishing check turn off write permission with this:
      sudo chmod -w /boot/grub/grub.cfg

      If the system still said the cfg is read only, that means the file system corrupted and you can try to use fsck function to check errors in initramfs mode.

  9. My system is bricked now. I can’t do anything anymore, as my system can’t write into /boot/grub/grub.cfg anymore. It looks quite dangerous to fiddle around with grub. I don’t have a lot of experience as I still use yaboot on the develop machine (luckily). I will do a reinstallation and do some more testing soon. I hope that this update solves the problem. If not, I will make another version without anything in the /etc/default/grub.d folder.

  10. Just tried a fresh installation but it failed. vim-tiny, which depends on vim-common, has not been built. The installation stalled. I will try in another week.

    1. vim-common has dependence problem in the upgrade so it kept back the old one when I perform upgrade. You need to install the old one.

  11. Poe, can you tell me when your system upgrades vim-common and there are no other held-back packages? In other words, can you notify me when you have a clean system? I want to try an installation then.
    The Debian installer fails in situations like now, it all has to somehow work at thr moment of installation. You have to be lucky if you don’t know the status of the system.

    1. Message shown when performing upgrade –
      The following packages have been kept back:
      libfm-modules libfm4 libgd3 libpipewire-0.3-0 libpipewire-0.3-modules libreoffice-report-builder libspa-0.2-modules links2 lxpanel lxpanel-data pcmanfm pipewire pipewire-bin vim-common

      I know the status of Debian SID as many applications have broken dependency problems, including the following:

      My mintppc was installed from Debian 10 SID when you open this webpage again after termination of previous webpage , then it just ran with update/upgrade, no re-installation after that. I plan to reinstall the system when I get a SSD HD.

      If you can contact the Debian SID POWERPC developer group, please tell them these problems exists over a year.

  12. There are no people willing or able to maintain packages for powerpc anymore. All packages are built automatically by the buildd machines. It is pure luck that these packages get built correctly I think. It is of no use to tell this to the powerpc Debian group. The problem is volunteers. I hope you understand the situation. Even with this in mind, it is worthwhile to go on with MintPPC. Once you have it installed in the right way, you can enjoy a rolling release Linux distribution for PowerPC that works quite well. I know there are numerous people out there using my project on their old Macs.

    1. I know the problem, before you re-open this page, I even consider when minppc just become obsolete , I need to make decision on the OS choice, and there are 3 choices only – MorphOS/Gentoo/FreeBSD, I tried MorphOS before, it ran quite well and fast, the problem is software support, especially Chinese input/environment. I even try to test Gentoo on my machine but its too hard for the hardware to compile such huge binary code. Update process also is not an easy job for me and the iBook, I don’t want to waste so much time for squeezing a little bit performance from the machine. So FreeBSD may be my last choice.

    1. I think it works, but I modify the cfg file before, after upgrade the debian-system-adjustments I try to modify /etc/default/grub and see if it can update /boot/grub/grub.cfg, it works as expect.

  13. Well, if you have Debian installed, there are no big troubles anymore. Just update and upgrade regularly, don’t wait too long.
    I saw that you have a lot of old packages. You might be able to upgrade them by issuing a sudo apt package_name instead of the general sudo apt upgrade. Be careful though.

    1. I use synaptic software manager to check the dependence problem of those kept back files, for pipewire and lxpanel, upgrade will remove the library files in-use, links2 has broken, the remaining files relate to some files which still not update.

  14. I can tell you that on my develop system I have upgraded lxpanel and pcmanfm to the latest version. Sometimes you have to remove packages first to upgrade others. This is basically what’s done in a dist-upgrade. As long as you know which packages are removed. You can always install them back easily.

    1. Just try to update lxpanel/pcmanfm, it removes libfm-gtk4 and install libfm-gtk3.4, and result is Desktop pager plugin not work properly, it makes the panel’s length in half , the remaining panel becomes transparent and all the plugins/function widgets disappear.

  15. The only thing I know is that if you do a fresh installation, you will end up with the latest lxde packages and that they work.
    If all else fails, purge all lxde stuff and start from scratch:
    apt install task-lxde-desktop lxdm
    That is what the preseed.cfg pulls in.

Leave a comment

Your email address will not be published. Required fields are marked *