No new software install possible - no nexttcloud install possible

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version 9.7.1
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname --all
  • Linux Pi54G 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16) aarch64 GNU/Linux
  • Architecture | dpkg --print-architecture >> arm64
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3) >>RPi5 4 Gb
  • Power supply used | (EG: 5V 1A RAVpower) >> 5V 3 A
  • SD card used | (EG: SanDisk ultra) M.2 256 Gb

Additional Information (if applicable)

  • Software title | (EG: Nextcloud) no install nextcloud possible
  • Was the software title installed freshly or updated/migrated?

I am only an user , no programmer or anything.

no update is possible:

after ÂŽapt updateÂŽ and apt upgrade will raspberry Pi 5 4GB in case of start `dietpi-software ÂŽ an reboot.

after reboot the same procedure . no software install is possible ( will only install nextcloud)

  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID >> 908ff217-e242-48d6-9653-35aad8cffddc

have anybody an workaround ?

BR RalphE

This is a public forum where users try to help other users. For data protection reasons, only the (very small) development team has access to bug reports. As well they are gone after 48h. Therefore, it is always beneficial to share error messages or logs directly here. Otherwise, no one except the development team can help you.

But you’re in luck, I can view the reports and I found yours. It doesn’t contain any error messages itself. So it would be good if you could describe exactly what isn’t working.

That’s strange. According to your report, there’s a lot of software running there that is definitely not standard and was installed afterwards.

  • NFS
  • Apache web server
  • DBUS
  • switched from Dropbear to OpenSSH
  • polkit authorization manager ??
  • unbound
  • PHP8.2
  • XRDP
  • PiHole
  • Webmin
  • Squid Web Proxy Server
  • vsftpd FTP server
  • Nginx web server (not active, conflicting with Apache)

Looks you installed a hell of software, even some conflicting.

Therefore we need way more information on what you have done and what issues you have during NC installation

Well, I already wrote that the software was installed only through the DietPi software module, except for one or two packages. I haven’t been able to resolve the conflict between Nginx and Apache yet. Which packages are still conflicting with each other? I would be grateful for further help.

BR RalphE

I don’t know how else to describe it. When I launch DietPi-Software, the message ‘reboot required’ appears. After rebooting and starting DietPi-Software again, the same message appears. apt update and apt upgrade make no difference.

Only the message “Reboot required”? No menu or something like that?
And I guess you isntalled Apache together with Webmin or some other web app and then installed nginx also?

That is correct. When starting the DietPi software, ‘reboot needed’ appears. Apache and Webmin were installed together first. I don’t remember why I installed nginx. But I can’t uninstall it with ‘rm’ right now.

ok the loaded kernel is not matching installed one.

can you share following

uname -a
df -h
ls -la /boot

rm is a command to remove files or folder. It’s not supposed to uninstall software

uname -a
Linux Pi54G 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1\~bookworm (2025-09-16) aarch64 GNU/Linux

you need to provide all information

df -h
Dateisystem    GrĂ¶ĂŸe Benutzt Verf. Verw% EingehĂ€ngt auf
/dev/root       235G     13G  213G    6% /
devtmpfs        2,0G       0  2,0G    0% /dev
tmpfs           2,0G    4,5M  2,0G    1% /dev/shm
tmpfs           810M     12M  799M    2% /run
tmpfs           5,0M       0  5,0M    0% /run/lock
tmpfs           4,0G     32K  4,0G    1% /tmp
tmpfs            50M     64K   50M    1% /var/log
/dev/mmcblk0p1  127M     44M   84M   35% /boot/firmware
tmpfs           405M     32K  405M    1% /run/user/0
ls -la /boot
insgesamt 10096
drwxr-xr-x  4 root root    4096 20. Jan 20:00 .
drwxr-xr-x 18 root root    4096 20. Jan 20:00 ..
lrwxrwxrwx  1 root root      20 25. Feb 2024  cmdline.txt → firmware/cmdline.txt
-rw-r–r--   1 root root  248768 19. Jan 10:09 config-6.12.62+rpt-rpi-2712
lrwxrwxrwx  1 root root      19 25. Feb 2024  config.txt → firmware/config.txt
drwxr-xr-x  4 root root    4096 12. Jan 18:28 dietpi
-rw-r–r--   1 root root   18092 21. Feb 2024  dietpi-LICENSE.txt
-rw-r–r--   1 root root   16059 21. Feb 2024  dietpi-README.md
-rw-r–r--   1 root root   17483 20. Jan 17:17 dietpi.txt
drwxr-xr-x  4 root root    4096  1. Jan 1970  firmware
-rw-------  1 root root   27139 20. Jan 19:39 initrd.img-6.12.62+rpt-rpi-2712
-rw-r–r--   1 root root      83 19. Jan 10:09 System.map-6.12.62+rpt-rpi-2712
-rw-r–r--   1 root root 9980718 19. Jan 10:09 vmlinuz-6.12.62+rpt-rpi-2712

you are using any sort of additional bootloader?

no, no other bootloader

somewhere an older kernel is loaded from. This is not normal.

Somehing more to share

dpkg -l linux*
ls -la /boot/firmware/
ls -la /boot
insgesamt 10096
drwxr-xr-x  4 root root    4096 20. Jan 20:00 .
drwxr-xr-x 18 root root    4096 20. Jan 20:00 ..
lrwxrwxrwx  1 root root      20 25. Feb 2024  cmdline.txt → firmware/cmdline.txt
-rw-r–r--   1 root root  248768 19. Jan 10:09 config-6.12.62+rpt-rpi-2712
lrwxrwxrwx  1 root root      19 25. Feb 2024  config.txt → firmware/config.txt
drwxr-xr-x  4 root root    4096 12. Jan 18:28 dietpi
-rw-r–r--   1 root root   18092 21. Feb 2024  dietpi-LICENSE.txt
-rw-r–r--   1 root root   16059 21. Feb 2024  dietpi-README.md
-rw-r–r--   1 root root   17483 20. Jan 17:17 dietpi.txt
drwxr-xr-x  4 root root    4096  1. Jan 1970  firmware
-rw-------  1 root root   27139 20. Jan 19:39 initrd.img-6.12.62+rpt-rpi-2712
-rw-r–r--   1 root root      83 19. Jan 10:09 System.map-6.12.62+rpt-rpi-2712
-rw-r–r--   1 root root 9980718 19. Jan 10:09 vmlinuz-6.12.62+rpt-rpi-2712
root@Pi54G:\~# dpkg -l linux\*
GewĂŒnscht=Unbekannt/Installieren/R=Entfernen/P=VollstĂ€ndig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhÀngig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name                                      Version                   Architek
tur  Beschreibung
++±=========================================-=========================-========
====-===============================================
ii  linux-base                                4.9                       all Linux image base package
un  linux-doc-6.12                                               (keine Beschreibung vorhanden)
un  linux-doc-6.6                                                (keine Beschreibung vorhanden)
un  linux-firmware-raspi3                                        (keine Beschreibung vorhanden)
ii  linux-image-6.12.62+rpt-rpi-2712          1:6.12.62-1+rpt1\~bookworm arm64 Linux 6.12 for Raspberry Pi 2712, Raspberry Pi
rc  linux-image-6.6.74+rpt-rpi-2712           1:6.6.74-1+rpt1           arm64 Linux 6.6 for Raspberry Pi 2712, Raspberry Pi
ii  linux-image-rpi-2712                      1:6.12.62-1+rpt1\~bookworm arm64 Linux for Raspberry Pi 2712 (meta-package)
un  linux-initramfs-tool                                         (keine Beschreibung vorhanden)
un  linux-latest-modules-6.12.62+rpt-rpi-2712                          (keine Beschreibung vorhanden)
ii  linux-libc-dev                            1:6.12.62-1+rpt1\~bookworm all          Linux support headers for userspace development
un  linux-perf                                                         (keine Beschreibung vorhanden)
Pi54G:\~# ls -la linux
ls: Zugriff auf ‘linux’ nicht möglich: Datei oder Verzeichnis nicht gefunden
root@Pi54G:\~# ls -la /boot/firmware/
insgesamt 42963
drwxr-xr-x 4 root root     4096  1. Jan 1970   .
drwxr-xr-x 4 root root     4096 20. Jan 20:00  ..
-rwxr-xr-x 1 root root    32503 16. Sep 13:31  bcm2710-rpi-2-b.dtb
-rwxr-xr-x 1 root root    34695 16. Sep 13:31  bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root    35330 16. Sep 13:31  bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root    33684 16. Sep 13:31  bcm2710-rpi-cm0.dtb
-rwxr-xr-x 1 root root    32266 16. Sep 13:31  bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root    33672 16. Sep 13:31  bcm2710-rpi-zero-2.dtb
-rwxr-xr-x 1 root root    33672 16. Sep 13:31  bcm2710-rpi-zero-2-w.dtb
-rwxr-xr-x 1 root root    56293 16. Sep 13:31  bcm2711-rpi-400.dtb
-rwxr-xr-x 1 root root    56289 16. Sep 13:31  bcm2711-rpi-4-b.dtb
-rwxr-xr-x 1 root root    56810 16. Sep 13:31  bcm2711-rpi-cm4.dtb
-rwxr-xr-x 1 root root    39913 16. Sep 13:31  bcm2711-rpi-cm4-io.dtb
-rwxr-xr-x 1 root root    53510 16. Sep 13:31  bcm2711-rpi-cm4s.dtb
-rwxr-xr-x 1 root root    78769 16. Sep 13:31  bcm2712d0-rpi-5-b.dtb
-rwxr-xr-x 1 root root    78761 16. Sep 13:31  bcm2712-d-rpi-5-b.dtb
-rwxr-xr-x 1 root root    78721 16. Sep 13:31  bcm2712-rpi-500.dtb
-rwxr-xr-x 1 root root    78765 16. Sep 13:31  bcm2712-rpi-5-b.dtb
-rwxr-xr-x 1 root root    79710 16. Sep 13:31  bcm2712-rpi-cm5-cm4io.dtb
-rwxr-xr-x 1 root root    79776 16. Sep 13:31  bcm2712-rpi-cm5-cm5io.dtb
-rwxr-xr-x 1 root root    79751 16. Sep 13:31  bcm2712-rpi-cm5l-cm4io.dtb
-rwxr-xr-x 1 root root    79817 16. Sep 13:31  bcm2712-rpi-cm5l-cm5io.dtb
-rwxr-xr-x 1 root root    52624 12. Nov 18:04  bootcode.bin
-rwxr-xr-x 1 root root      114 13. MĂ€r 2024   cmdline.txt
-rwxr-xr-x 1 root root     3022 26. Sep 20:24  config.txt
-rwxr-xr-x 1 root root    17431 25. Feb 2024   dietpi.txt
-rwxr-xr-x 1 root root     3950 25. Feb 2024   dietpi-wifi.txt
-rwxr-xr-x 1 root root     3270 12. Nov 18:04  fixup4cd.dat
-rwxr-xr-x 1 root root     5496 12. Nov 18:04  fixup4.dat
-rwxr-xr-x 1 root root     8489 12. Nov 18:04  fixup4db.dat
-rwxr-xr-x 1 root root     8489 12. Nov 18:04  fixup4x.dat
-rwxr-xr-x 1 root root     3270 12. Nov 18:04  fixup_cd.dat
-rwxr-xr-x 1 root root     7365 12. Nov 18:04  fixup.dat
-rwxr-xr-x 1 root root    10334 12. Nov 18:04  fixup_db.dat
-rwxr-xr-x 1 root root    10332 12. Nov 18:04  fixup_x.dat
-rwxr-xr-x 1 root root 10195462 15. Feb 2025   initramfs_2712
-rwxr-xr-x 1 root root  9971983 12. Nov 18:04  kernel_2712.img
-rwxr-xr-x 1 root root     1594 12. Nov 18:04  LICENCE.broadcom
drwxr-xr-x 2 root root    31744 12. Nov 18:04  overlays
-rwxr-xr-x 1 root root   846684 12. Nov 18:04  start4cd.elf
-rwxr-xr-x 1 root root  3797224 12. Nov 18:04  start4db.elf
-rwxr-xr-x 1 root root  2299008 12. Nov 18:04  start4.elf
-rwxr-xr-x 1 root root  3046664 12. Nov 18:04  start4x.elf
-rwxr-xr-x 1 root root   846684 12. Nov 18:04  start_cd.elf
-rwxr-xr-x 1 root root  4869064 12. Nov 18:04  start_db.elf
-rwxr-xr-x 1 root root  3023264 12. Nov 18:04  start.elf
-rwxr-xr-x 1 root root  3770312 12. Nov 18:04  start_x.elf
drwxr-xr-x 2 root root     1024 13. MĂ€r 2024  ‘System Volume Information’
root@Pi54G:\~# ^C

I’m not sure why, but the last kernel update doesn’t seem to have been completed. At least, the image file is from November and probably from the kernel 6.12.47

Currently installed should be 6.12.62

you can try to reinstall the kernel and reboot your system afterwards

apt install --reinstall linux-image-rpi-2712 linux-image-6.12.62+rpt-rpi-2712

once booted, check current kernel version loaded

uname -a

ok i make it

uname -a
Linux Pi54G 6.12.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1\~bookworm (2026-01-19) aarch64 GNU/Linux
1 Like

hey, i can say its function ok.

can i spend for your support?