April 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1210302] New: Snapshot entries aren't being created for grub
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210302 Bug ID: 1210302 Summary: Snapshot entries aren't being created for grub Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: lilfrogg(a)posteo.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is my second MicroOS install in a row where new snapshots at some point stopped showing up in the grub menu. The snapshots themselves are created as normal and it appears that the script of the grub2-snapper-plugin fails to create the entries because my snapshots appear to be writable for some reason. Here are some terminal outputs I was asked to create in the oS support channel: sudo find /.snapshots -maxdepth 2 -type f -name grub-snapshot.cfg �/.snapshots/91/grub-snapshot.cfg /.snapshots/grub-snapshot.cfg� Snapshot 91 is one I manually created with 'snapper create' which creates a grub entry. all the other snapshots don't show up Using 'sh -o xtrace usr/lib/snapper/plugins/grub --enable' in a transactional-update shell �+ set -e + grub_mkconfig=/usr/sbin/grub2-mkconfig + grub_mkrelpath=/usr/bin/grub2-mkrelpath + grub_script_check=/usr/bin/grub2-script-check + grub_setting=/etc/default/grub + grub_cfg=/boot/grub2/grub.cfg + grub_snapshot_cfg=/boot/grub2/snapshot_submenu.cfg + snapper_snapshot_path=/.snapshots + snapshot_submenu_name=grub-snapshot.cfg + snapper_snapshots_cfg=/.snapshots/grub-snapshot.cfg + hotkey= ++ uname -m + machine=x86_64 + case "$machine" in + cmdline='/usr/lib/snapper/plugins/grub --enable hotkey='\'''\''' + test 1 -gt 0 + option=--enable + shift + case "$option" in + opt_enable=true + test 0 -gt 0 + '[' xtrue = xtrue ']' + snapper_snapshots_cfg_refresh + '[' '!' -d /.snapshots ']' + cs= + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/79/snapshot + '[' '!' -d /.snapshots/79 -o -w /.snapshots/79/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/80/snapshot + '[' '!' -d /.snapshots/80 -o -w /.snapshots/80/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/81/snapshot + '[' '!' -d /.snapshots/81 -o -w /.snapshots/81/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/82/snapshot + '[' '!' -d /.snapshots/82 -o -w /.snapshots/82/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/83/snapshot + '[' '!' -d /.snapshots/83 -o -w /.snapshots/83/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/84/snapshot + '[' '!' -d /.snapshots/84 -o -w /.snapshots/84/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/85/snapshot + '[' '!' -d /.snapshots/85 -o -w /.snapshots/85/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/86/snapshot + '[' '!' -d /.snapshots/86 -o -w /.snapshots/86/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/87/snapshot + '[' '!' -d /.snapshots/87 -o -w /.snapshots/87/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/88/snapshot + '[' '!' -d /.snapshots/88 -o -w /.snapshots/88/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/89/snapshot + '[' '!' -d /.snapshots/89 -o -w /.snapshots/89/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/90/snapshot + '[' '!' -d /.snapshots/90 -o -w /.snapshots/90/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/grub-snapshot.cfg/snapshot + '[' '!' -d /.snapshots/grub-snapshot.cfg -o -w /.snapshots/grub-snapshot.cfg/snapshot ']' + continue + hk= + '[' -z '' ']' ++ printf %s '' ++ sort -Vr + cat + /usr/bin/grub2-script-check /.snapshots/grub-snapshot.cfg.new + mv -f /.snapshots/grub-snapshot.cfg.new /.snapshots/grub-snapshot.cfg + '[' x = xtrue ']' + '[' x = xtrue ']'� ls -lad /.snap* �drwxr-x---. 1 root root 98 Apr 11 11:02 /.snapshots� mount | grep snapshots �/dev/mapper/cr_root on / type btrfs (ro,relatime,seclabel,space_cache=v2,subvolid=363,subvol=/(a)/.snapshots/90/snapshot) /dev/mapper/cr_root on /.snapshots type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=266,subvol=/@/.snapshots)� -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1197645] rpi-eeprom-config / vcgencmd fails on raspberry pi 400
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1197645 https://bugzilla.suse.com/show_bug.cgi?id=1197645#c5 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Hi, I have quickly looked over lore.kernel and I don't see anyone working on this except "fix typo in comment" patches. So I don't see what we can do here, I am afraid. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210065] GTK outside GNOME starts super slow any window
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210065 Martin Sirringhaus <martin.sirringhaus(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.sirringhaus(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209818] Slow startup of evolution and other applications on i3
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209818 https://bugzilla.suse.com/show_bug.cgi?id=1209818#c5 Yifan Jiang <yfjiang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yfjiang(a)suse.com --- Comment #5 from Yifan Jiang <yfjiang(a)suse.com> --- Just for the record, I suspected there was an issues on the portal backends (either gnome or gtk), when this bug may be tangled up in a similar cause: https://bugzilla.opensuse.org/show_bug.cgi?id=1210065#c9 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196618] New: RPi3/RPi4: Occasional "error -110 whilst initialising SD card" on boot
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1196618 Bug ID: 1196618 Summary: RPi3/RPi4: Occasional "error -110 whilst initialising SD card" on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2218590/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)opensuse.org Found By: openQA Blocker: Yes Leap 15.4: https://openqa.opensuse.org/tests/2218590#step/journal_check/10 Tumbleweed: https://openqa.opensuse.org/tests/2218201#step/journal_check/10 This does not always happen, e.g.: https://openqa.opensuse.org/tests/2192626 ## Observation openQA test in scenario opensuse-15.4-JeOS-for-RPi-aarch64-jeos@RPi4 fails in [journal_check](https://openqa.opensuse.org/tests/2218590/modules/journal_ch… ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [5.1](https://openqa.opensuse.org/tests/2076851) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1210264] New installation option: partial disk encryption with Trusted Platform
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210264 https://bugzilla.suse.com/show_bug.cgi?id=1210264#c4 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE --- Comment #4 from Lukas Ocilka <locilka(a)suse.com> --- Please file this as a feature if you believe this is something that the distribution really needs https://code.opensuse.org/leap/features/issues -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205588] New: Page Fault when booting with PE NX-compatibility DLL Characteristic flag
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1205588 Bug ID: 1205588 Summary: Page Fault when booting with PE NX-compatibility DLL Characteristic flag Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am trying the "Page Fault when booting with PE NX-compatibility DLL Characteristic flag" support in openSUSE TW: When PcdDxeNxMemoryProtectionPolicy be set to 0x4 (protect EfiLoaderData) in OVMF, openSUSE TW can not boot. We got a Page Fault: Loading Linux 6.1.0-rc5-default+.old ... Loading initial ramdisk ... !!!! X64 Exception Type - 0E(#PF - Page-Fault) CPU Apic ID - 00000000 !!!! ExceptionData - 0000000000000011 I:1 R:0 U:0 W:0 P:1 PK:0 SS:0 SGX:0 RIP - 0000000076A6F390, CS - 0000000000000038, RFLAGS - 0000000000210206 RAX - 000000007DA98DF8, RCX - 0000000076A6F390, RDX - 000000007DED3000 RBX - 0000000076A6F000, RSP - 000000007FF0D5A8, RBP - 000000007DED3000 RSI - 000000007F9EE018, RDI - 000000007E7A9718 R8 - 0000000076A6F000, R9 - 0000000000000190, R10 - 000000007FF1D658 R11 - 0000000000000004, R12 - 0000000000000190, R13 - 000000007DA98E00 R14 - 000000007DA936B4, R15 - 000000007BF0CBD5 DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030 GS - 0000000000000030, SS - 0000000000000030 CR0 - 0000000080010033, CR2 - 0000000076A6F390, CR3 - 000000007FC01000 CR4 - 0000000000000668, CR8 - 0000000000000000 DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000 DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400 GDTR - 000000007F9DE000 0000000000000047, LDTR - 0000000000000000 IDTR - 000000007F2E9018 0000000000000FFF, TR - 0000000000000000 FXSAVE_STATE - 000000007FF0D200 !!!! Find image based on IP(0x7BF0BAB5) (No PDB) (ImageBase=000000007BDEB7A0, EntryPoint=000000007C92A0AF) !!!! The same EFI_STUB kernel can direct boot by EFI boot manager with the following boot entry: echo " root=UUID=6ffd1fb1-ddac-4105-a25a-20a602c93e7d showopts console=ttyS0,115200n8 console=tty0 earlyprintk=tty0 debug loglevel=9 efi=debug nomodeset initrd=\EFI\opensuse\initrd-6.1.0-rc5-default+" | \ iconv -f ascii -t ucs2 | efibootmgr -v -cL "vmlinuz-6.1.0-rc5-default+.efi (EFISTUB)" -d /dev/vda -p 1 -l '\EFI\opensuse\vmlinuz-6.1.0-rc5-default+.efi' --append-binary-args - Looks that the Page Fault is in grub2. The grub2 rpm is grub2-x86_64-efi-2.06-31.1.noarch. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1209818] Slow startup of evolution and other applications on i3
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209818 https://bugzilla.suse.com/show_bug.cgi?id=1209818#c4 Martin Sirringhaus <martin.sirringhaus(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |GNOME Assignee|screening-team-bugs(a)suse.de |gnome-bugs(a)suse.de --- Comment #4 from Martin Sirringhaus <martin.sirringhaus(a)suse.com> --- I've put a lock on xdg-desktop-portal, xdg-desktop-portal-gnome and gnome-* and did a full `zypper dup`. Everything still works. So I'm moderately sure it's a GNOME-bug. Marking this bug accordingly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193596] No graphical display in Plymouth on Raspberry Pi 4
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1193596 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Installation Assignee|kernel-bugs(a)opensuse.org |yast2-maintainers(a)suse.de QA Contact|qa-bugs(a)suse.de |jsrain(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193596] No graphical display in Plymouth on Raspberry Pi 4
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1193596 https://bugzilla.suse.com/show_bug.cgi?id=1193596#c8 --- Comment #8 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- I also think that some initrd adjustment for installation images should be made, but I don't think we at @kernel-bugs could help. -- You are receiving this mail because: You are on the CC list for the bug.

1 0