ubuntuusers.de

Ubuntu 22.04 neben Windows 11 installieren (dualboot)

Status: Gelöst | Ubuntu-Version: Ubuntu 22.04 (Jammy Jellyfish)
Antworten |

alex1004

Anmeldungsdatum:
22. April 2022

Beiträge: 47

Hallo,
hatte mir gestern die brandaktuelle Ubuntu 22.04 ISO heruntergeladen und per Rufus auf einen USB-Stick geladen. Dann hab ich einen technisch relativ aktuellen Notebook von Lenovo (V15 G2-ALC 82KD) mit AMD-Ryzen 5 Prozessor und vorinstalliertem Windows 11, auf 1 TB SSD. Die Windows-Partition hab ich ausreichend verkleinert, d.h. da ist gut Platz Ubuntu zu installieren, Fast-Boot ist abgeschaltet ebenso wie Secure-Boot im BIOS. Das laden vom USB-Stick geht reibungslos, bis auf eine Meldung "problem loading X.. certificate", die man aber angeblich ignorieren kann. Das Ausprobieren funktioniert ganz normal, nur bei der Installation bekomm ich Probleme. Zum einen wird mir die Option "Install alongside with Windows" nicht angezeigt und wenn ich es manuell versuche, kommt zum Schluss ein fataler Fehler bei der Installation von GRUB.

Als "default" Ziel für GRUB wird mit die nvme0n1 angeboten. Damit scheitert es natürlich schon mal. Dann gibt es noch nvme0n1p1 (Window Bootmanager) nvme0n1p2 (EFI) nvme0n1p3 (NTFS, Windows 11) und nvme0n1p4 (/ bzw. es bleibt dann als /target nach Installer-Absturz übrig).
Ich hab's dann mit nvme0n1p2 und nvme0n1p4 für GRUBinstallation versucht, was auch kein Glück brachte. Auf eine SWAP-Partition hab ich mal verzichtet zumal ich 20 GB RAM hab und dann mal davon ausgehe, dass Ubuntu eine Swapdatei passender Größe notfalls automatisch anlegt.

Bin jetzt ziemlich ratlos, d.h. zum einen warum das Windows nicht erkannt wird. Am OS-Prober kann es nicht liegen, weil er mir (manchmal - und ich hab's schon etliche male versucht zu installieren) "install alongside Ubuntu 22.04 anzeigt, d.h. er erkennt die vorherige gescheiterte Installation. Und dann ist das mein erster Computer mit UEFI / GPT, also mit BIOS / MBR hatte ich solche Probleme nie und ich hab schon etliche Linuxe installiert und immer Multi-Boot. D.h. k.A. was ich hier noch anders und besser machen könnte und warum der Installer nicht selber merkt, wenn etwas nicht i.O. ist, also vor dem fatalen Absturz.

Bearbeitet von ChickenLipsRfun2eat:

Forensyntax korrigiert, aus dem Spamfilter gefischt.

black_tencate

Avatar von black_tencate

Anmeldungsdatum:
27. März 2007

Beiträge: 11230

Hej alex1004,

und willkommen im Forum!

alex1004 schrieb:

... Das laden vom USB-Stick geht reibungslos

und Du bist sicher, daß das im EFI Modus efolgt ist? (kannst du mit

[ -d /sys/firmware/efi ] && echo UEFI || echo "legacy"

prüfen)

kommt zum Schluss ein fataler Fehler bei der Installation von GRUB.

Als "default" Ziel für GRUB wird mit die nvme0n1 angeboten. Damit scheitert es natürlich schon mal. Dann gibt es noch nvme0n1p1 (Window Bootmanager) nvme0n1p2 (EFI)

hier liegt also eine EFI Installation von Windows vor, folglich muß Ubuntu im selben Modus installiert werden, damit grub dann als Bootmanager fungieren kann.

Leider hat ubiquity (das ist der Ubuntu Installer) einen bug, nämlich allein die Tatsache, daß (eben im EFI Modus dennoch) ein Ort für den Bootloader "angeboten" wird, obwohl das vollkommen obsolet ist: Im EFI Modus wird immer die (erste gefundene) mit esp markierte Partition gewählt (bei Dir eben nvme0n1p2)

Gruß black tencate

alex1004

(Themenstarter)

Anmeldungsdatum:
22. April 2022

Beiträge: 47

black_tencate schrieb:

Hej alex1004,

und willkommen im Forum!

alex1004 schrieb:

... Das laden vom USB-Stick geht reibungslos

und Du bist sicher, daß das im EFI Modus efolgt ist? (kannst du mit

[ -d /sys/firmware/efi ] && echo UEFI || echo "legacy"

prüfen)

kommt zum Schluss ein fataler Fehler bei der Installation von GRUB.

Als "default" Ziel für GRUB wird mit die nvme0n1 angeboten. Damit scheitert es natürlich schon mal. Dann gibt es noch nvme0n1p1 (Window Bootmanager) nvme0n1p2 (EFI)

hier liegt also eine EFI Installation von Windows vor, folglich muß Ubuntu im selben Modus installiert werden, damit grub dann als Bootmanager fungieren kann.

Leider hat ubiquity (das ist der Ubuntu Installer) einen bug, nämlich allein die Tatsache, daß (eben im EFI Modus dennoch) ein Ort für den Bootloader "angeboten" wird, obwohl das vollkommen obsolet ist: Im EFI Modus wird immer die (erste gefundene) mit esp markierte Partition gewählt (bei Dir eben nvme0n1p2)

Gruß black tencate

Die Antwort lautet "UEFI". Ich hab's nochmal mit einer 1GB swap Partition versucht und vorher schon auch mit eingeschaltetem Secure-Boot, aber immer dasselbe, d.h. weder das Angebot "neben Windows" zu installieren und dann fataler Fehler bei der GRUB Installation. Hatte dann auch mal das Wifi an und entsprechenden "Report" an die Ubuntu-Entwickler verschickt. Hoffentlich bringt das dann was - ich geb's mal vorläufig auf. Könnte es vllt. mal mit einer anderen Distro versuchen, dann läge das Problem wohl an den vorinstallierten Partitionen bzw. irgendwelchen Inkompatibilitäten, wenn auch das nicht funktioniert. Das Windows 11 bootet aber weiter problemlos und ich hab mich auch vergewissert, dass es *keine* "dynamischen" Partitionen sind, d.h. ?????

black_tencate

Avatar von black_tencate

Anmeldungsdatum:
27. März 2007

Beiträge: 11230

Hej alex1004,

nicht gleich aufgeben!

Zeige

  • sudo mount /dev/nvme0n1p2 /mnt && sudo ls -R /mnt && sudo umount /mnt

und

  • sudo efibootmgr -v

Gruß black tencate

alex1004

(Themenstarter)

Anmeldungsdatum:
22. April 2022

Beiträge: 47

black_tencate schrieb:

Hej alex1004,

nicht gleich aufgeben!

Zeige

  • sudo mount /dev/nvme0n1p2 /mnt && sudo ls -R /mnt && sudo umount /mnt

und

  • sudo efibootmgr -v

Gruß black tencate

Ist ja Schwerstarbeit... 😉

Also zu 1)

/mnt:
EFI
System Volume Information

/mnt/EFI:
Boot
Microsoft

/mnt/EFI/Boot:
bootx64.efi

/mnt/EFI/Microsoft:
Boot
Recovery

/mnt/EFI/Microsoft/Boot:
BCD
BCD.LOG
BCD.LOG1
BCD.LOG2
bg-BG
bootmgfw.efi
bootmgr.efi
BOOTSTAT.DAT
boot.stl
CIPolicies
cs-CZ
da-DK
de-DE
el-GR
en-GB
en-US
es-ES
es-MX
et-EE
fi-FI
Fonts
fr-CA
fr-FR
hr-HR
hu-HU
it-IT
ja-JP
kd_02_10df.dll
kd_02_10ec.dll
kd_02_1137.dll
kd_02_14e4.dll
kd_02_15b3.dll
kd_02_1969.dll
kd_02_19a2.dll
kd_02_1af4.dll
kd_02_8086.dll
kd_07_1415.dll
kd_0C_8086.dll
kdnet_uart16550.dll
kdstub.dll
ko-KR
lt-LT
lv-LV
memtest.efi
nb-NO
nl-NL
pl-PL
pt-BR
pt-PT
qps-ploc
Resources
ro-RO
ru-RU
sk-SK
sl-SI
sr-Latn-RS
sv-SE
tr-TR
uk-UA
winsipolicy.p7b
zh-CN
zh-TW

/mnt/EFI/Microsoft/Boot/bg-BG:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/CIPolicies:
Active

/mnt/EFI/Microsoft/Boot/CIPolicies/Active:
{5DAC656C-21AD-4A02-AB49-649917162E70}.cip
{82443e1e-8a39-4b4a-96a8-f40ddc00b9f3}.cip
{CDD5CB55-DB68-4D71-AA38-3DF2B6473A52}.cip

/mnt/EFI/Microsoft/Boot/cs-CZ:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/da-DK:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/de-DE:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/el-GR:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/en-GB:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/en-US:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/es-ES:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/es-MX:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/et-EE:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/fi-FI:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/Fonts:
chs_boot.ttf
cht_boot.ttf
jpn_boot.ttf
kor_boot.ttf
malgun_boot.ttf
malgunn_boot.ttf
meiryo_boot.ttf
meiryon_boot.ttf
msjh_boot.ttf
msjhn_boot.ttf
msyh_boot.ttf
msyhn_boot.ttf
segmono_boot.ttf
segoen_slboot.ttf
segoe_slboot.ttf
wgl4_boot.ttf

/mnt/EFI/Microsoft/Boot/fr-CA:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/fr-FR:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/hr-HR:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/hu-HU:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/it-IT:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/ja-JP:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/ko-KR:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/lt-LT:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/lv-LV:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/nb-NO:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/nl-NL:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/pl-PL:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/pt-BR:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/pt-PT:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/qps-ploc:
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/Resources:
bootres.dll
de-DE

/mnt/EFI/Microsoft/Boot/Resources/de-DE:
bootres.dll.mui

/mnt/EFI/Microsoft/Boot/ro-RO:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/ru-RU:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/sk-SK:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/sl-SI:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/sr-Latn-RS:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/sv-SE:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/tr-TR:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/uk-UA:
bootmgfw.efi.mui
bootmgr.efi.mui

/mnt/EFI/Microsoft/Boot/zh-CN:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Boot/zh-TW:
bootmgfw.efi.mui
bootmgr.efi.mui
memtest.efi.mui

/mnt/EFI/Microsoft/Recovery:
BCD
BCD.LOG
BCD.LOG1
BCD.LOG2

/mnt/System Volume Information:

Und 2)

BootCurrent: 0016
Timeout: 0 seconds
BootOrder: 0012,0000,0013,0014,0015,0016,0017,0018,0019
Boot0000* Windows Boot Manager	HD(2,GPT,97d0ca3e-d585-4b1f-865e-8e6989e331c7,0x40800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012* NVMe: MS100 - 1TB                            	PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/NVMe(0x1,00-00-01-00-00-00-00-00)....2.LN........
Boot0013* ATA HDD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0014* ATA HDD1:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot0015* ATAPI CD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0016* USB HDD: Kingston DT 100 G2	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4)/USB(0,0)3.!..3.G..A.....
Boot0017* PCI LAN:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0018* USB FDD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* USB CD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)

black_tencate

Avatar von black_tencate

Anmeldungsdatum:
27. März 2007

Beiträge: 11230

Hej alex1004,

(Terminalausgaben nächstes mal bitte in codeblocks → so: {{{…}}})

Da ist nichts ubuntumäßiges installiert. Achte auf die Zuordnung der Partitionen (s. 6d-6i in Baustelle/Ubuntu Installation – Gegenüberstellung der Flavours)

Gruß black tencate

alex1004

(Themenstarter)

Anmeldungsdatum:
22. April 2022

Beiträge: 47

black_tencate schrieb:

Hej alex1004,

(Terminalausgaben nächstes mal bitte in codeblocks → so: {{{…}}})

Da ist nichts ubuntumäßiges installiert. Achte auf die Zuordnung der Partitionen (s. 6d-6i in Baustelle/Ubuntu Installation – Gegenüberstellung der Flavours)

Gruß black tencate

Dass da nichts ubuntumäßiges installiert ist, ist ja genau das Problem. D.h. das ist der Zustand nach der Installation und dem Absturz des Installers und bevor ich die ubuntu Partition wieder gelöscht hab.

Also er installiert ganz normal, bis dann GRUB und der Absturz dran ist.

black_tencate

Avatar von black_tencate

Anmeldungsdatum:
27. März 2007

Beiträge: 11230

Hej alex1004,

alex1004 schrieb:

...relativ aktuellen Notebook von Lenovo (V15 G2-ALC 82KD) mit AMD-Ryzen 5 Prozessor und vorinstalliertem Windows 11

was da jetzt genau der Hinderungsgrund ist, k.A (per PW blockiertes UEFI o.ä.?)

Aber → schwachstellen-in-lenovo-laptops und https://support.lenovo.com/us/de/product_security/len-73440#Lenovo%20Notebook solltest Du auf alle Fälle beachten, also UEFI updaten.

Gruß black tencate

Lidux

Anmeldungsdatum:
18. April 2007

Beiträge: 16667

Hallo alex1004,

Hast du das Fastboot / den Schnellstart im EFI und in Windows 11 deaktiviert ? Das Secure Boot muss im EFI aktiviert werden, da ansonsten das Windows 11 wahrscheinlich nicht mehr starten kann. Beim Bootloader sollte sich derer automatisch die EFI Partition krallen. Zur Sicherheit trotzdem die EFI Partion auswählen und einstellen.

PS: Firmware EFI muss natürlich aktuell sein.

Gruss Lidux

alex1004

(Themenstarter)

Anmeldungsdatum:
22. April 2022

Beiträge: 47

black_tencate schrieb:

Hej alex1004,

alex1004 schrieb:

...relativ aktuellen Notebook von Lenovo (V15 G2-ALC 82KD) mit AMD-Ryzen 5 Prozessor und vorinstalliertem Windows 11

was da jetzt genau der Hinderungsgrund ist, k.A (per PW blockiertes UEFI o.ä.?)

Aber → schwachstellen-in-lenovo-laptops und https://support.lenovo.com/us/de/product_security/len-73440#Lenovo%20Notebook solltest Du auf alle Fälle beachten, also UEFI updaten.

Gruß black tencate

Ich hab mir das Gerät zum 10.04. 😉 als Geburtstagsgeschenk liefern lassen und wollte es eigentlich erst mit Ubuntu 22.04 so richtig nutzen. Aber zwischenzeitlich hab ich mir das "Lenovo Vantage" installiert, was dann überprüft ob alle Treiber etc auf dem neusten Stand sind. Und im Rahmen dessen wurde ein neues BIOS "geflashed." Von einem Passwort weiss ich nichts, also bis auf alles was automatisch aktuallisiert wird und Verkleinerung der Windows 11 Partition hatte ich nichts gemacht. Erst als dieses Installationsproblem aufkam, hab ich angefangen rumzufummeln. Die Hibernation war z.B. gar nicht aktiviert und somit das "Fast-Boot" auch kein Thema. Aber ich hab sie dann aktiviert und Fast-Boot explizit deaktiviert. Dann mit dem Secure-Boot, mal deaktiviert, aktiviert, deaktiviert, aber kein Fortschritt. Zum Glück geht die Installation recht zügig, und deshalb hab ich schon ~10 Versuche absolviert. K.A. ob die Partitiontable da irgendwann einen Schaden abbekommt und die SSD dann futsch ist, denn die wird ja bei jedem Versuch mehrfach manipuliert. Ich würde ja von einem Programm erwarten, wenn es schon Hardwaretest etc. macht, dass es in der Lage wäre zu sagen was das Problem, z.B. mit einem Passwort ist, statt nur abzustürzen und ich darf jetzt Rätselraten woran das liegen soll. Wie gesagt, mit dem UEFI/GPT hatte ich bislang keinerlei Erfahrung und wenn schon sowas kompliziertes, dann sollte es wenigstens möglichst automatisch sein.

Nachtrag:

BIOS Version: GLCN44WW
EC Version: GLEC44WW
MTM: 82KD001NGE

Administrator & User Password "Not Set" und Secure Boot ist momentan "Disabled". Einzig seltsam oder nicht HDD Password "Frozen"???

alex1004

(Themenstarter)

Anmeldungsdatum:
22. April 2022

Beiträge: 47

Lidux schrieb:

Hallo alex1004,

Hast du das Fastboot / den Schnellstart im EFI und in Windows 11 deaktiviert ? Das Secure Boot muss im EFI aktiviert werden, da ansonsten das Windows 11 wahrscheinlich nicht mehr starten kann. Beim Bootloader sollte sich derer automatisch die EFI Partition krallen. Zur Sicherheit trotzdem die EFI Partion auswählen und einstellen.

PS: Firmware EFI muss natürlich aktuell sein.

Gruss Lidux

Windows 11 startet bei mir problemlos mit oder ohne Secure Boot. Wie gesagt, das Fastboot sollte nie ein Problem gewesen sein, weil die Hibernation ursprünglich abgeschaltet war und es gar keine Option "Schnellstart aktivieren" gab. Ich hab dann Hibernation aktiviert und mit der dann vorhandenen Option ist das Fastboot offensichtich deaktiviert. Und das Secure Boot war beim ersten Versuch/Absturz bzw. zwischenzeitlich auch. Hab's ja auch versucht die EFI Partition nvme0n1p2 auszuwählen. Die Firmware kann aktueller nicht sein. Also das erste Problem ist schon mal, dass die Option "Install alongside Windows Bootmanager" gar nicht erscheint. Und wenn ich's dann manuell mache installiert es ganz normal, bis er dann bei der GRUB-installation auf "Fatal error" kommt.

alex1004

(Themenstarter)

Anmeldungsdatum:
22. April 2022

Beiträge: 47

Nächster Versuch. Hab mir eine 64bit "boot-repair" usb Disk erstellt und mal laufen lassen. Das ist der Report nach dem "repair":

boot-repair-4ppa200                                              [20220423_1338]

============================= Boot Repair Summary ==============================




Default settings: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the MBR.
Additional repair would be performed:  win-legacy-basic-fix

User settings: _________________________________________________________________

No OS to fix.
The settings chosen by the user will not act on the MBR.
Additional repair will be performed:  win-legacy-basic-fix


Quantity of real Windows: 1

Boot successfully repaired.

You can now reboot your computer.


============================ Boot Info After Repair ============================

 => No boot loader is installed in the MBR of /dev/nvme0n1.
 => No known boot loader is installed in the MBR of /dev/sda.

nvme0n1p1: _____________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info: 

nvme0n1p2: _____________________________________________________________________

    File system:       vfat
    Boot sector type:  Windows 8/10/11/2012: FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /efi/Boot/bootx64.efi /efi/Microsoft/Boot/bootmgfw.efi 
                       /efi/Microsoft/Boot/bootmgr.efi

nvme0n1p3: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/10/11/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows 10 or 11
    Boot files:        /Windows/System32/winload.exe

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Windows 8/10/11/2012: FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /boot/grub/grub.cfg /syslinux.cfg /efi/BOOT/grubx64.efi


================================ 1 OS detected =================================

OS#1:   Windows 10 or 11 on nvme0n1p3

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Advanced Micro Devices, Inc. [AMD/ATI] from Advanced Micro Devices, Inc. [AMD/ATI]
Live-session OS is Ubuntu 64-bit (Boot-Repair-Disk 64bit 20200604, bionic, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: GLCN44WW from LENOVO
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot enabled but mokutil says: SecureBoot enabled - Please report this message to boot.repair@gmail.com.
BootCurrent: 0016
Timeout: 0 seconds
BootOrder: 0012,0000,0013,0014,0015,0016,0017,0018,0019
Boot0000* Windows Boot Manager	HD(2,GPT,97d0ca3e-d585-4b1f-865e-8e6989e331c7,0x40800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012* NVMe: MS100 - 1TB                            	PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/NVMe(0x1,00-00-01-00-00-00-00-00)....2.LN........
Boot0013* ATA HDD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0014* ATA HDD1:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot0015* ATAPI CD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0016* USB HDD: General UDisk	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4)/USB(0,0)3.!..3.G..A.....
Boot0017* PCI LAN:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0018* USB FDD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* USB CD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)

62ad2d96df1db720085d1cf4d4e64f4c   nvme0n1p2/Boot/bootx64.efi
62ad2d96df1db720085d1cf4d4e64f4c   nvme0n1p2/Microsoft/Boot/bootmgfw.efi
7a545293b3a88dc43bb913a045c4443d   nvme0n1p2/Microsoft/Boot/bootmgr.efi

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

nvme0n1	: is-GPT,	no-BIOSboot,	has---ESP, 	not-usb,	not-mmc, has-os,	has-win,	34 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p2	: no-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	not-far
nvme0n1p3	: is-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	farbios

Partitions info (2/3): _________________________________________________________

nvme0n1p2	: is---ESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot
nvme0n1p3	: isnotESP,	part-has-no-fstab,	no-nt,	haswinload,	no-recov-nor-hid,	no-bmgr,	notwinboot

Partitions info (3/3): _________________________________________________________

nvme0n1p2	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme0n1
nvme0n1p3	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme0n1

fdisk -l (filtered): ___________________________________________________________

Disk nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors
Disk identifier: 5D808DC0-311B-4D25-8682-737C5ADB7B6F
           Start        End    Sectors  Size Type
nvme0n1p1     34     262177     262144  128M Microsoft reserved
nvme0n1p2 264192     468991     204800  100M EFI System
nvme0n1p3 468992 1678190591 1677721600  800G Microsoft basic data
Disk sda: 3.8 GiB, 4026531840 bytes, 7864320 sectors
Disk identifier: 414C4255-1B29-48B4-8A65-0297AA8F462C
      Start     End Sectors  Size Type
sda1   2048 7864286 7862239  3.8G Microsoft basic data
Disk zram0: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram1: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram2: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram3: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram4: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram5: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram6: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram7: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram8: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram9: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram10: 747 MiB, 783331328 bytes, 191243 sectors
Disk zram11: 747 MiB, 783331328 bytes, 191243 sectors

parted -lm (filtered): _________________________________________________________

sda:4027MB:scsi:512:512:gpt:General UDisk:;
1:1049kB:4027MB:4025MB:fat32:Main Data Partition:msftdata;
nvme0n1:1024GB:nvme:512:512:gpt:MS100 - 1TB:;
1:17.4kB:134MB:134MB:::msftres;
2:135MB:240MB:105MB:fat32::boot, esp;
3:240MB:859GB:859GB:ntfs::msftdata;

Free space >10MiB: ______________________________________________________________

nvme0n1: 819429MiB:976762MiB:157333MiB

blkid (filtered): ______________________________________________________________

NAME        FSTYPE   UUID                                 PARTUUID                             LABEL       PARTLABEL
sda                                                                                                        
└─sda1      vfat     C0B9-8D6E                            9dd3b6a3-a344-4d64-9b9b-ed6dfa57af47 BOOT-REPAIR Main Data Partition
nvme0n1                                                                                                    
├─nvme0n1p1                                               ace929f8-80c9-4460-9df3-b98f83cf3474             
├─nvme0n1p2 vfat     20A2-5CFA                            97d0ca3e-d585-4b1f-865e-8e6989e331c7             
└─nvme0n1p3 ntfs     3A1EA4451EA3F7D1                     7e0b801b-66ac-4ea2-95ac-afd88760c434 Windows11   

Mount points (filtered): _______________________________________________________

                Avail Use% Mounted on
/dev/nvme0n1p2  70.3M  29% /mnt/boot-sav/nvme0n1p2
/dev/nvme0n1p3 749.4G   6% /mnt/boot-sav/nvme0n1p3
/dev/sda1        2.9G  23% /cdrom

Mount options (filtered): ______________________________________________________

/dev/nvme0n1p2 vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/nvme0n1p3 fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda1      vfat            ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro

====================== sda1/boot/grub/grub.cfg (filtered) ======================

Boot-Repair-Disk session
Boot-Repair-Disk session (failsafe)

========================= sda1/syslinux.cfg (filtered) =========================

DEFAULT loadconfig

LABEL loadconfig
  CONFIG /isolinux/isolinux.cfg
  APPEND /isolinux/

==================== sda1: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1

================== sda1: Location of files loaded by Syslinux ==================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             syslinux.cfg                                   1

======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown MBR on /dev/sda

00000000  41 4b 45 4f fc 31 c0 fa  8e d0 bc 00 7c fb 8e d8  |AKEO.1......|...|
00000010  bb 13 04 8b 07 83 e8 04  89 07 c1 e0 06 8e c0 b7  |................|
00000020  07 b8 7f 00 cd 10 31 db  31 c9 ba 4f 18 b8 00 06  |......1.1..O....|
00000030  cd 10 31 d2 b4 02 cd 10  b4 41 bb aa 55 cd 13 72  |..1......A..U..r|
00000040  27 81 fb 55 aa 75 21 f7  c1 01 00 74 1b 66 31 c0  |'..U.u!....t.f1.|
00000050  66 50 6a 22 06 66 50 6a  08 6a 10 89 e6 b4 42 cd  |fPj".fPj.j....B.|
00000060  13 9f 83 c4 10 9e eb 0d  b8 08 02 b9 23 00 ba 80  |............#...|
00000070  00 31 db cd 13 bb 07 00  72 0b 31 f6 8c c0 8e d8  |.1......r.1.....|
00000080  e8 3f 00 eb 06 be 17 7d  e8 37 00 31 c0 8e d8 be  |.?.....}.7.1....|
00000090  63 7d e8 2d 00 e8 1d 00  b4 01 cd 16 75 08 b4 02  |c}.-........u...|
000000a0  cd 16 24 04 74 f2 31 c0  8e d8 b8 34 12 a3 73 04  |..$.t.1....4..s.|
000000b0  ea 00 00 ff ff b4 01 cd  16 74 06 b4 00 cd 16 e2  |.........t......|
000000c0  f4 c3 ac 3c 00 74 4f 3c  0d 74 f7 3c 0a 75 10 53  |...<.tO<.t.<.u.S|
000000d0  b4 03 cd 10 fe c6 b2 00  b4 02 cd 10 5b eb e3 3c  |............[..<|
000000e0  5c 75 1c b1 02 ac 3c 46  7f d8 2c 30 3c 09 7e 02  |\u....<F..,0<.~.|
000000f0  2c 07 c0 e3 04 24 0f 08  c3 fe c9 75 e8 eb c3 b9  |,....$.....u....|
00000100  01 00 b4 09 cd 10 53 31  db b4 03 cd 10 fe c2 b4  |......S1........|
00000110  02 cd 10 5b eb ac c3 0d  0a 20 20 20 20 20 20 20  |...[.....       |
00000120  20 20 20 20 20 20 5c 30  34 2a 2a 2a 20 45 52 52  |      \04*** ERR|
00000130  4f 52 3a 20 54 48 49 53  20 4d 45 44 49 41 20 43  |OR: THIS MEDIA C|
00000140  41 4e 4e 4f 54 20 42 4f  4f 54 20 49 4e 20 4c 45  |ANNOT BOOT IN LE|
00000150  47 41 43 59 20 4d 4f 44  45 20 2a 2a 2a 5c 30 37  |GACY MODE ***\07|
00000160  0d 0a 00 0d 0a 0d 0a 20  20 20 20 20 20 20 20 20  |.......         |
00000170  20 20 20 20 5c 37 30 50  6c 65 61 73 65 20 72 65  |    \70Please re|
00000180  6d 6f 76 65 20 74 68 69  73 20 6d 65 64 69 61 20  |move this media |
00000190  61 6e 64 20 70 72 65 73  73 20 61 6e 79 20 6b 65  |and press any ke|
000001a0  79 20 74 6f 20 72 65 62  6f 6f 74 5c 30 37 00 00  |y to reboot\07..|
000001b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001c0  02 00 ee fe 7f e8 01 00  00 00 ff ff ff ff 00 00  |................|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200

D.h. das einzige mögliche Problem wäre was mit "win-legacy-basic-fix" gewesen. Dann ausprobiert ob Windows 11 geht - geht. Dann "Neustart" was ja mal jegliches Problem mit "Fastboot" ausschließt und wieder "Ubuntu installieren". Diesmal ist/war "Secure Boot" aktiviert. Wieder kein Angebot "neben Windows" zu installieren, also manuell und wieder "This is a fatal error" bei der Installation von GRUB.

Hier noch /var/log/installer/debug:

Ubiquity 22.04.15
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:7: PyGIWarning: NM was imported without specifying a version first. Use gi.require_version('NM', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import NM, NMA

(ubiquity:2033): Gtk-WARNING **: 13:48:03.439: GtkBox does not have a child property called left_attach

(ubiquity:2033): Gtk-WARNING **: 13:48:03.439: GtkBox does not have a child property called width

(ubiquity:2033): Gtk-WARNING **: 13:48:03.439: GtkBox does not have a child property called height

(ubiquity:2033): Gtk-WARNING **: 13:48:03.440: GtkBox does not have a child property called width

(ubiquity:2033): Gtk-WARNING **: 13:48:03.440: GtkBox does not have a child property called height

(ubiquity:2033): Gtk-WARNING **: 13:48:03.440: GtkGrid does not have a child property called expand

(ubiquity:2033): Gtk-WARNING **: 13:48:03.440: GtkGrid does not have a child property called fill

(ubiquity:2033): Gtk-WARNING **: 13:48:03.440: GtkGrid does not have a child property called position
No such schema “org.gnome.nautilus.desktop”
expected value:
  (empty input)
  ^
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
/usr/lib/ubiquity/ubiquity/misc.py:710: PyGIWarning: Xkl was imported without specifying a version first. Use gi.require_version('Xkl', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import Xkl, GdkX11
update_release_notes_label()
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:19: Warning: Source ID 327 was not found when attempting to remove it
  GLib.source_remove(self.timeout_id)
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:135: Warning: Source ID 409 was not found when attempting to remove it
  GLib.source_remove(self.rows_changed_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
Could not translate page (prepare): 'NoneType' object has no attribute 'replace'
/usr/lib/ubiquity/plugins/ubi-console-setup.py:114: Warning: Source ID 661 was not found when attempting to remove it
  GLib.source_remove(self.keyboard_layout_timeout_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
/usr/lib/ubiquity/plugins/ubi-console-setup.py:114: Warning: Source ID 1982 was not found when attempting to remove it
  GLib.source_remove(self.keyboard_layout_timeout_id)
/usr/lib/ubiquity/plugins/ubi-console-setup.py:136: Warning: Source ID 668 was not found when attempting to remove it
  GLib.source_remove(self.keyboard_variant_timeout_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
/usr/lib/ubiquity/plugins/ubi-console-setup.py:70: Warning: Source ID 2021 was not found when attempting to remove it
  GLib.source_remove(self.keyboard_layout_timeout_id)
/usr/lib/ubiquity/plugins/ubi-console-setup.py:72: Warning: Source ID 2029 was not found when attempting to remove it
  GLib.source_remove(self.keyboard_variant_timeout_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:19: Warning: Source ID 426 was not found when attempting to remove it
  GLib.source_remove(self.timeout_id)
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:135: Warning: Source ID 505 was not found when attempting to remove it
  GLib.source_remove(self.rows_changed_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
/usr/lib/ubiquity/ubiquity/segmented_bar.py:34: PyGIWarning: PangoCairo was imported without specifying a version first. Use gi.require_version('PangoCairo', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import GObject, Gdk, Gtk, PangoCairo

(ubiquity:2033): Gtk-CRITICAL **: 13:52:41.996: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:52:41.996: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:52:41.996: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:52:41.997: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:52:41.997: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)

(ubiquity:2033): Gtk-CRITICAL **: 13:53:59.776: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:53:59.776: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:53:59.776: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:53:59.777: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:53:59.777: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:53:59.777: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:19: Warning: Source ID 3192 was not found when attempting to remove it
  GLib.source_remove(self.timeout_id)
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:135: Warning: Source ID 3269 was not found when attempting to remove it
  GLib.source_remove(self.rows_changed_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)

(ubiquity:2033): Gtk-CRITICAL **: 13:54:41.984: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:54:41.985: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:54:41.985: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:54:41.985: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:54:41.985: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed

(ubiquity:2033): Gtk-CRITICAL **: 13:54:41.985: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”

(ubiquity:2033): Gtk-CRITICAL **: 09:55:14.106: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
/usr/lib/ubiquity/plugins/ubi-timezone.py:96: PyGIWarning: Soup was imported without specifying a version first. Use gi.require_version('Soup', '2.4') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GObject, GLib, Soup
/usr/lib/ubiquity/plugins/ubi-timezone.py:209: Warning: Source ID 8562 was not found when attempting to remove it
  GLib.source_remove(self.timeout_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
/usr/lib/ubiquity/plugins/ubi-usersetup.py:432: Warning: Source ID 8973 was not found when attempting to remove it
  GLib.source_remove(self.hostname_timeout_id)
/usr/lib/ubiquity/plugins/ubi-usersetup.py:432: Warning: Source ID 8980 was not found when attempting to remove it
  GLib.source_remove(self.hostname_timeout_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)

(ubiquity:2033): Gtk-CRITICAL **: 15:56:23.044: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:19: Warning: Source ID 7723 was not found when attempting to remove it
  GLib.source_remove(self.timeout_id)
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:135: Warning: Source ID 7803 was not found when attempting to remove it
  GLib.source_remove(self.rows_changed_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
No such schema “com.canonical.indicator.session”
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:19: Warning: Source ID 9402 was not found when attempting to remove it
  GLib.source_remove(self.timeout_id)
XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
No such schema “com.canonical.indicator.session”
No such key “active”
No such schema “org.gnome.nautilus.desktop”

Mein Latein ist damit restlosest ausgeschöpft.

black_tencate

Avatar von black_tencate

Anmeldungsdatum:
27. März 2007

Beiträge: 11230

Hej alex1004,

leg mal auf dem freien Platz eine ext4 Parttiion an und zeige dann hier

sudo parted -l

sowie

lsblk -f

Gruß black tencate

alex1004

(Themenstarter)

Anmeldungsdatum:
22. April 2022

Beiträge: 47

Ich bin ja immer dabei die zu löschen, d.h. auf den jungfräulichen Zustand zu bringen.

Aber das ist mal der Zustand *nach* der letzten (gescheiterten 😉) Installation, was ja mal keinen Unterschied machen sollte?

1)

Model: Kingston DT 100 G2 (scsi)
Disk /dev/sda: 7934MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                 Flags
 1      1049kB  7934MB  7932MB  fat32        Main Data Partition  msftdata


Model: Intenso Speed Line (scsi)
Disk /dev/sdb: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  32.0GB  32.0GB  primary


Model: MS100 - 1TB (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size   File system  Name  Flags
 1      17.4kB  134MB   134MB                     msftres
 2      135MB   240MB   105MB  fat32              boot, esp
 3      240MB   859GB   859GB  ntfs               msftdata
 4      859GB   1019GB  160GB  ext4

2)

NAME        FSTYPE   FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                          0   100% /rofs
loop1       squashfs 4.0                                                          0   100% /snap/bare/5
loop2       squashfs 4.0                                                          0   100% /snap/core20/1405
loop3       squashfs 4.0                                                          0   100% /snap/firefox/1232
loop4       squashfs 4.0                                                          0   100% /snap/gnome-3-38-2004/99
loop5       squashfs 4.0                                                          0   100% /snap/gtk-common-themes/1534
loop6       squashfs 4.0                                                          0   100% /snap/snapd-desktop-integration/10
loop7       squashfs 4.0                                                          0   100% /snap/snapd/15177
loop8       squashfs 4.0                                                          0   100% /snap/snap-store/575
sda                                                                                        
└─sda1      vfat     FAT32 UBUNTU 22_0 9A31-663B                                 4G    46% /cdrom
sdb                                                                                        
└─sdb1      exfat    1.0   DATAzILLA   8E5D-7D38                              28.8G     3% /media/ubuntu/DATAzILLA
nvme0n1                                                                                    
├─nvme0n1p1                                                                                
├─nvme0n1p2 vfat     FAT32             20A2-5CFA                                           
├─nvme0n1p3 ntfs           Windows11   3A1EA4451EA3F7D1                                    
└─nvme0n1p4 ext4     1.0               6b775dbe-490a-4b77-a5fe-acb1fd14d754                

Lidux

Anmeldungsdatum:
18. April 2007

Beiträge: 16667

Hallo alex1004,

Du hast da jeweils auf der nvmexxx und auf der sda eine EFI Partition ..... Gehe mal im EFI die Einstellungen durch bezüglich der Platten / Raid. Auch mal im Netz recherchieren nach Lenovo (V15 G2-ALC 82KD) und Ubuntu .....

Gruss Lidux

Antworten |