March 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1182835] New: systemctl --user not working
by bugzilla_noreply＠suse.com 04 Mar '21

04 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182835 Bug ID: 1182835 Summary: systemctl --user not working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, i did a clean install of microOS 20210223 which is the last version, in the mode Container Host because of podman. after the installation i proceed to create the user and the subu(g)ids. when i do systemctl --user i got: Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user) -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1182988] brp-99-pesign fails for fwupd package
by bugzilla_noreply＠suse.com 04 Mar '21

04 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182988 https://bugzilla.suse.com/show_bug.cgi?id=1182988#c1 --- Comment #1 from Gary Ching-Pang Lin <glin(a)suse.com> --- It's a known issue that fwupd 1.5.6 didn't copy the .data section to the EFI image. The build script is fixed in 1.5.7. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182988] brp-99-pesign fails for fwupd package
by bugzilla_noreply＠suse.com 04 Mar '21

04 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182988 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com Assignee|screening-team-bugs(a)suse.de |glin(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182240] [Build 20210211] Login to awesomeWM fails
by bugzilla_noreply＠suse.com 04 Mar '21

04 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182240 https://bugzilla.suse.com/show_bug.cgi?id=1182240#c2 --- Comment #2 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: otherDE_awesome https://openqa.opensuse.org/tests/1652971 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182233] [Build 20210211][glibc2.33] chromium fails to render websites
by bugzilla_noreply＠suse.com 04 Mar '21

04 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182233 https://bugzilla.suse.com/show_bug.cgi?id=1182233#c9 --- Comment #9 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: kde-live_installation https://openqa.opensuse.org/tests/1653506 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182957] New: grub2-install fails to install on NVME SSD with GPT (no EFI)
by bugzilla_noreply＠suse.com 04 Mar '21

04 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182957 Bug ID: 1182957 Summary: grub2-install fails to install on NVME SSD with GPT (no EFI) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 846693 --> http://bugzilla.opensuse.org/attachment.cgi?id=846693&action=edit output of `grub2-install -vvvv /dev/nvme0n1` This is what I see tux:~ # grep -A1 warning: log grub2-install: warning: not a newc filesystem. grub-core/kern/fs.c:57: Detecting hostfs... -- grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. grub2-install: error: will not proceed with blocklists. with the layout tux:~ # parted -l Model: ATA ST2000LM003 HN-M (scsi) Disk /dev/sda: 2000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 2000GB 2000GB extended lba, type=0f 5 2097kB 1100GB 1100GB logical xfs type=83 6 1100GB 1207GB 107GB logical xfs type=83 7 1207GB 1422GB 215GB logical xfs type=83 8 1422GB 2000GB 579GB logical xfs type=83 Model: NVMe Device (nvme) Disk /dev/nvme0n1: 128GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 8591MB 8590MB linux-swap(v1) swap swap 2 8591MB 19.3GB 10.7GB ext3 boot legacy_boot 3 19.3GB 128GB 109GB xfs root -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1183001] New: i915 graphics driver fails to auto-detect correct RGB colors range on 24 bit LCD monitor connected via HDMI
by bugzilla_noreply＠suse.com 04 Mar '21

04 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183001 Bug ID: 1183001 Summary: i915 graphics driver fails to auto-detect correct RGB colors range on 24 bit LCD monitor connected via HDMI Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: davidkacerek(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Customer Blocker: --- Created attachment 846731 --> http://bugzilla.opensuse.org/attachment.cgi?id=846731&action=edit Taken right after boot to desktop, with "drm.debug=0x1e" & "log_buf_len=4M" kernel parameters set in GRUB2. Overview: At the start of OS booting, colors are fine (black is deep). During booting, at the moment the Intel driver i915 is loaded, screen flickers once and colors get degraded (black gets grey). Note I'm not using Plymouth so I'm looking at the black tty. After the boot, when executing 'xrandr --output DP-1 --set "Broadcast RGB" Full', I can confirm the colors get immediately fixed up (white is light, black is deep, colors are more saturated). The issue is related to another bug report in upstream and is resolved for some people but not for me: https://bugs.freedesktop.org/show_bug.cgi?id=107476. Steps to reproduce: 1) Start the PC. 2) Watch the boot console with Plymouth disabled. 3) Pay attention to the moment the screen flickers and the graphics driver is loaded. Actual results: Step 3) is the moment colors get degraded. And stay that way. Expected results: After the screen flickering during the step 3), colors should stay the same. Affected Linux kernel versions: The standard Linux version in openSUSE Leap 15.2: 5.3.18 The newest stable Linux from the Kernel:stable repo: 5.11.2 Affected hardware: GPU: Intel Iris Plus Graphics 640 (Which uses the i915 kernel module = the common denominator of the problem reported by other people.) LCD monitor: Iiyama ProLite XB2483HSU-B3 (Supports 24 bit colors, like other reported affected monitors.) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1181643] Rust 1.47 - 1.49 fails to build on armv7
by bugzilla_noreply＠suse.com 03 Mar '21

03 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1181643 https://bugzilla.suse.com/show_bug.cgi?id=1181643#c6 --- Comment #6 from William Brown <william.brown(a)suse.com> --- No - attempting the build causes an out-of-memory on the build servers for all arches during the build process. I have been unable to successfully build with bundled llvm at this time. I need to revisit this to see why. Certainly the fact that you can use the upstream rust that has bundled llvm vs our rust that uses the platform llvm does hint that there is an incompatibility between our llvm and rust's expectations. My ideal outcome in this matter would be that we just use the bundled llvm since it has stronger quality assurances from upstream rust than using our own llvm - using our own can lead to exactly this kind of issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182987] New: ERRO[0000] The storage 'driver' option must be set in /etc/containers/storage.conf
by bugzilla_noreply＠suse.com 03 Mar '21

03 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182987 Bug ID: 1182987 Summary: ERRO[0000] The storage 'driver' option must be set in /etc/containers/storage.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: jalausuch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Creation of containers throw new errors and warnings in TW build 20210302. > openSUSE-MicroOS-DVD-x86_64-Snapshot20210302-Media.iso > localhost:~ # podman run alpine:3.6 id > ERRO[0000] The storage 'driver' option must be set in /etc/containers/storage.conf, guarantee proper operation. > WARN[0000] Path "/etc/SUSEConnect" from "/etc/containers/mounts.conf" doesn't exist, skipping > WARN[0000] Path "/etc/zypp/credentials.d/SCCcredentials" from "/etc/containers/mounts.conf" doesn't exist, skipping > uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video) > localhost:~ # podman -v > ERRO[0000] The storage 'driver' option must be set in /etc/containers/storage.conf, guarantee proper operation. > podman version 3.0.1 It can also be observed in O3 for both TW and MicroOS: https://openqa.opensuse.org/tests/1653150#step/podman/83 https://openqa.opensuse.org/tests/1653269#step/podman/31 https://openqa.opensuse.org/tests/1653269/modules/podman/steps/35 However, the command returns 0, so the tests pass. localhost:~ # grep -A 1 Driver /etc/containers/storage.conf # Default Storage Driver driver = "" Probably these configuration is wrong in TW and should be applied only to SLE > localhost:~ # cat /etc/containers/mounts.conf > # This configuration file specifies the default mounts for each container of the > # tools adhering to this file (e.g., CRI-O, Podman, Buildah). The format of the > # config is /SRC:/DST, one mount per line. > /etc/SUSEConnect:/etc/SUSEConnect > /etc/zypp/credentials.d/SCCcredentials:/etc/zypp/credentials.d/SCCcredentials I haven't observed this error in SLE Micro, but there we have podman version 2.1.1. So, probably a podman package update in TW is causing this messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1182951] Testing with Leap 15.3 Beta b 91.1 - Issues with dangling syslink
by bugzilla_noreply＠suse.com 03 Mar '21

03 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182951 http://bugzilla.opensuse.org/show_bug.cgi?id=1182951#c2 --- Comment #2 from Dick Waite <dick.waite(a)ostiasolutions.com> --- Many Thanks for the update. It's grand to know I'm not alone ;o) __R -- You are receiving this mail because: You are on the CC list for the bug.

1 0