March 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1146936] New: nmcli-examples: add examples of bonding + vlan + bridge
by bugzilla_noreply＠novell.com 04 Apr '23

04 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1146936 Bug ID: 1146936 Summary: nmcli-examples: add examples of bonding + vlan + bridge Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Configuring a bond + vlan + bridge is not completely straightforward or clear with nmcli. An example should be added such as: nmcli conn add type bond con-name bond0 ifname bond0 mode 802.3ad ipv4.method disabled ipv6.method ignore nmcli connection add type ethernet con-name bond0-eth1 ifname eth1 master bond0 slave-type bond nmcli connection add type ethernet con-name bond0-eth2 ifname eth2 master bond0 slave-type bond nmcli connection add type bridge con-name net_18 ifname net_18 ipv4.method disabled ipv6.method ignore nmcli connection add type vlan con-name bond0.18 ifname bond0.18 dev bond0 id 18 master net_18 slave-type bridge This is suitable for libvirt/vms to use the bridges. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1176818] New: Wrong public keys in openSUSE-build-key for verifying container image signatures
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1176818 Bug ID: 1176818 Summary: Wrong public keys in openSUSE-build-key for verifying container image signatures Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: meissner(a)suse.com Reporter: rhafer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: sgrunert(a)suse.com Found By: --- Blocker: --- The openSUSE-build-keys package contains /usr/lib/rpm/gnupg/keys/opensuse-container-key.asc and /usr/lib/rpm/gnupg/keys/suse-container-key.asc which symlink to the "openSUSE Project Signing Key <opensuse(a)opensuse.org>" and "SuSE Package Signing Key <build(a)suse.de>" but apparently the images we provide on registry.opensuse.org are signed by some other key. When enabling signature verification for "registry.opensuse.org" using the key "/usr/lib/rpm/gnupg/keys/opensuse-container-key.asc" all images fail to verify because the images are signed with a different key. Looking into the signatures, which are fetched from "https://registry.opensuse.org/sigstore/" it seem the images are signed by a key with the ID "D754694F9AB48CE9". The key in /usr/lib/rpm/gnupg/keys/opensuse-container-key.asc however AFAICS is: "B88B2FD43DBDC284". So something is wrong here. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1172949] New: iphone not recognized when plugged into usb port
by bugzilla_noreply＠suse.com 02 Apr '23

02 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1172949 Bug ID: 1172949 Summary: iphone not recognized when plugged into usb port Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: 1chip(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838816 --> http://bugzilla.opensuse.org/attachment.cgi?id=838816&action=edit dmesg output when Iphone x is plugged into usb port it only charges.Can't import any photos and does not show up in dolphin. Using opensuse leap 15.2 with KDe plasma 5.18.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1189907] New: gnome-software: packages from the main distro repository should not be marked as potentially dangerous
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1189907 Bug ID: 1189907 Summary: gnome-software: packages from the main distro repository should not be marked as potentially dangerous Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- it should work more like software.o.o categorizes packages. i think the main culprit might be that it doesnt have any permissions information like it has for flatpak based apps. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1088738] New: xhost setting fails to have affect in /etc/gdm/Xsession --- "no protocol specified"
by bugzilla_noreply＠novell.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1088738 Bug ID: 1088738 Summary: xhost setting fails to have affect in /etc/gdm/Xsession --- "no protocol specified" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: noah(a)chromakey.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- line 154 xhost+ si:localuser ... needs to be in /etc/X11/xinit/xinitrc.d/what-ever.sh ... ... or maybe somewhere else all I know is that in Xsession it fails to have any affect ... effectively breaking the X11 gnome access for remote logins/ssh/etc. I'd expect a lot of bug reports of people angry, confused .. and complaining about "no protocol specified" errors. Thanks! -noah -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1160249] New: VNC issues (meta bug)
by bugzilla_noreply＠novell.com 31 Mar '23

31 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1160249 Bug ID: 1160249 Summary: VNC issues (meta bug) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: sndirsch(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- VNC issues (meta bug) -- You are receiving this mail because: You are on the CC list for the bug.

2 62

[Bug 1195391] New: identify and declare bash dependencies explicitly
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1195391 Bug ID: 1195391 Summary: identify and declare bash dependencies explicitly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a lot of fear that the openSUSE and SUSE distributions are, due to historic reason alone always assuming that /bin/sh is a symlink to bash, so that scripts executed with /bin/sh are actually only executable with bash. in order to explore that dependency, we need to figure out how many scripts actually use bash specifics when being invoked for /bin/sh and then fix these to declare the bash dependency if they have it. this bug is a tracker issue for fixes related to that. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1193579] New: Lifearea misses python3-cairo dependency
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193579 Bug ID: 1193579 Summary: Lifearea misses python3-cairo dependency Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: bluedzins(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Lifearea misses python3-cairo dependency, without using TrayIcon plugin is impossible, and in turn it is not possible to close&stay Lifera window, which for such type of the program is basically a must. For the record -- my report in Lifearea github: https://github.com/lwindolf/liferea/issues/1025 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1184334] New: Missing translation fixes for YaST and Welcome screen
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1184334 Bug ID: 1184334 Summary: Missing translation fixes for YaST and Welcome screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: noga.dany(a)gmail.com QA Contact: ke(a)suse.com Found By: --- Blocker: --- openSUSE-Leap-15.3-DVD-x86_64-Build117.13-Media.iso During installation via YaST with Czech translation I saw strange czech text "Zm��rn��n�� CPU" . I wanted to fix it, but it looks correct here https://l10n.opensuse.org/translate/yast-installation/master/cs/?checksum=6… Another wrong translation was with Welcome screen, where is czech text "Uk��zat p��i p��t��m sup��t��n��", where is typo, which I fixed almost year ago: https://l10n.opensuse.org/translate/opensuse-welcome/master/cs/?checksum=f7… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1185441] New: "system is compromised" during boot after grub2+shim update
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1185441 Bug ID: 1185441 Summary: "system is compromised" during boot after grub2+shim update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: robert.simai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed the most recent kernel-default-5.3.18-lp152.72.1.x86_64 shim-15.4-lp152.4.8.1.x86_64 grub2-2.04-lp152.7.25.1.x86_64 on my Dell Precision 3620 this week and rebooted as required. The system doesn't come up but shows "system is compromised" for a second, followed by power down. If I change from "UEFI with secure boot" to "UEFI without secure boot" it behaves well again and just boots. I've set "mokutil --set-verbosity true" as advised which outputs a lot of messages, I unfortunately have no serial console at hand to connect and save them. I'll try to attach a video from the screen that shows the boot process and messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 33