March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1021577] New: llvm 3.9.1 made some icons red
by bugzilla_noreply＠novell.com 24 Jul '20

24 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1021577 Bug ID: 1021577 Summary: llvm 3.9.1 made some icons red Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading LLVM to 3.9.1, some icons in the system tray turned red. This only happened in the system using the open source AMD GPU driver. The upstream bugs: https://bugs.freedesktop.org/show_bug.cgi?id=99078 https://llvm.org/bugs/show_bug.cgi?id=31722 Some distro like gentoo reverted this patch to stop the detect: https://github.com/llvm-mirror/llvm/commit/c280d74837d8239fc6cf567576b766ca… -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1061208] New: zypper segfaults upon refresh
by bugzilla_noreply＠novell.com 19 Jul '20

19 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1061208 Bug ID: 1061208 Summary: zypper segfaults upon refresh Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: richard(a)nod.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 742668 --> http://bugzilla.suse.com/attachment.cgi?id=742668&action=edit zypper core After adding the mozilla repo zypper crashes every time upon refresh. e.g. zypper> ref Repository 'go' is up to date. Repository 'libdvdcss repository' is up to date. Repository 'Packman Repository' is up to date. Retrieving repository 'mozilla' metadata -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[/]Segmentation fault (core dumped) Core file is attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1042986] New: Missing build requires in e2fsprogs
by bugzilla_noreply＠novell.com 15 Jul '20

15 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1042986 Bug ID: 1042986 Summary: Missing build requires in e2fsprogs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lchiquitto(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- e2fsprogs.spec calls %{?regenerate_initrd_posttrans} in %post, but this macro is only available at build time if suse-module-tools is listed as a build requirement. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1078466] New: systemd: duplicated entries in tmpfiles.d
by bugzilla_noreply＠novell.com 10 Jul '20

10 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1078466 Bug ID: 1078466 Summary: systemd: duplicated entries in tmpfiles.d Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:19] Duplicate line for path "/var/cache", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring. -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1083723] New: Kernels from Kernel:* are not signed by the SUSE key -- cannot be secure-booted
by bugzilla_noreply＠novell.com 10 Jul '20

10 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1083723 Bug ID: 1083723 Summary: Kernels from Kernel:* are not signed by the SUSE key -- cannot be secure-booted Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: General Assignee: adrian(a)suse.com Reporter: jslaby(a)suse.com QA Contact: adrian(a)suse.com CC: jlee(a)suse.com, mls(a)suse.com Found By: --- Blocker: --- Would it be possible to add the SUSE key (which is used for signing released openSUSE:* kernels) to sign also kernels in the Kernel:* space on OBS and Devel:Kernel:* space in IBS? This would allow for enabling secure boot even when one uses kernel-of-the-day from the above repos. And there are plenty of those people (from developers like me to users as can be seen on the opensuse lists). -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 941629] New: config.rpath from gettext-tools adds unnessary rpaths in x86_64 builds
by bugzilla_noreply＠novell.com 09 Jul '20

09 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=941629 Bug ID: 941629 Summary: config.rpath from gettext-tools adds unnessary rpaths in x86_64 builds Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: pth(a)suse.com Reporter: i(a)marguerite.su QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- Hi, I found two unnessary rpaths are added to LDFLAGS during building Cinnamon: https://build.opensuse.org/build/home:MargueriteSu:branches:X11:Cinnamon:Fa… <pre> [ 98s] libtool: link: gcc -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Wmissing-prototypes -o test-theme st/test_theme-test-theme.o ./.libs/libst-1.0.a -lclutter-1.0 -lcogl-path -lcogl-pango -lcogl -lgmodule-2.0 -lwayland-egl -lgbm -ldrm -lEGL -lXrandr -ljson-glib-1.0 -lwayland-cursor -lwayland-client -lxkbcommon -lwayland-server -lXext -lXdamage -lXfixes -lXcomposite -lXi -lcroco-0.6 /usr/lib64/libxml2.so -ldl -lz -llzma -lm -lcinnamon-desktop -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lX11 -pthread -Wl,-rpath -Wl,/usr/lib64 -Wl,-rpath -Wl,/usr/lib64 </pre> by grep in the build directory, I found those two rpaths comes from config.rpath: <pre> d_shlibs=yes if test "$with_gnu_ld" = yes; then # Set some defaults for GNU ld with shared library support. These # are reset later if shared libraries are not supported. Putting them # here allows them to be overridden if necessary. # Unlike libtool, we use -rpath here, not --rpath, since the documented # option of GNU ld is called -rpath, not --rpath. hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir' case "$host_os" in </pre> it seems that x86_64 didn't pass the host_os test. please have a look -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 943628] New: Networkmanager looses Wi-Fi connection
by bugzilla_noreply＠novell.com 06 Jul '20

06 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=943628 Bug ID: 943628 Summary: Networkmanager looses Wi-Fi connection Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: armv5 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have Raspberry Pi 1B system with a Wi-Fi USB interface running one of the latest Tumbleweed openSUSE images. After installation of the image I added nmcli-dmenu without recommends. I disabled wicked and enabled NetworkManager. Using nmtui I configured the wlan0 interface with a fixed IP address and the required other network parameters. When I boot the system without a connected Ethernet cable, the system comes up with an active Wi-Fi connection. The system is relatively far from the AP. So when I run a ping to the default gateway I always have a few percent loss. When I leave the system running for a few days a see each few hours - no fixed interval - a "Connection disconnected" with different reasons in the journal. At a certain moment I see "Activation: failed" to the AP. The system remains at the same location. After that NM does not try to re-establish the connection, so the system is not reachable anymore. When I connect the Ethernet cable I have access to the system again. Restarting the network.service re-establishes the Wi-Fi connection, so I can pull the Ethernet cable and still have a connection via Wi-Fi. I would expect NM to continuously try to re-establish the Wi-Fi connection. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 915168] New: During boot message i2c_hid i2c-SYN1B7E:01: failed to retrieve report from device. is shown
by bugzilla_noreply＠novell.com 06 Jul '20

06 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=915168 Bug ID: 915168 Summary: During boot message i2c_hid i2c-SYN1B7E:01: failed to retrieve report from device. is shown Classification: openSUSE Product: openSUSE Factory Version: 201501* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my Acer laptop with Intel N3530 and apparently a touchpad with name SYN1B7E I see the following: During boot message: i2c_hid i2c-SYN1B7E:01: failed to retrieve report from device. is shown. Ifound some reference about this device in http://www.adamdrew.net/?tag=kernel -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 984594] New: Use of cpan on Raspberry Pi 1 B armv6l has unsatisfied requirements
by bugzilla_noreply＠novell.com 06 Jul '20

06 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=984594 Bug ID: 984594 Summary: Use of cpan on Raspberry Pi 1 B armv6l has unsatisfied requirements Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a just installed Tumbleweed system on a Raspberry Pi 1B (armv6l) I tried to install a perl module using cpan. After some experimenting I found that I needed to install the packages make and gcc. Apparently the package perl, which provides /usr/bin/cpan, needs requirements for these two packages. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 986387] New: Device wlan0 on Raspberry Pi unexpectedly stopped and does not try to restart
by bugzilla_noreply＠novell.com 06 Jul '20

06 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=986387 Bug ID: 986387 Summary: Device wlan0 on Raspberry Pi unexpectedly stopped and does not try to restart Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a Raspberry Pi 1B I use Wi-Fi dongle to connect to the network. After about one week of running I noticed the network connection was down, so I had to power off and on the system to get again a network connection. I found the following error messages in the journal: jun 21 16:16:01 frans wickedd-nanny[474]: device wlan0: got signal linkDown jun 21 16:16:01 frans wickedd-nanny[474]: wlan0: failed to bring up device, still continuing jun 21 16:16:15 frans wickedd-dhcp4[456]: unable to rebind lease In the meantime the system worked as expected and the next morning the power off/on resulted in a connected system afgain. I wonder what caused the linkDown and why the system did not try to re-establish the connection. -- You are receiving this mail because: You are on the CC list for the bug.

2 1