April 2017 - 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 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

[Bug 1029775] New: systemd-presets-branding: Versioning inconsistency between openSUSE and SLE
by bugzilla_noreply＠novell.com 30 Jun '20

30 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1029775 Bug ID: 1029775 Summary: systemd-presets-branding: Versioning inconsistency between openSUSE and SLE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: lnussel(a)suse.com Reporter: sbrabec(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fbui(a)suse.com, meissner(a)suse.com Blocks: 1012850 Found By: --- Blocker: --- While creating unified util-linux.spec that can be used for Tumbleweed, Leap and SLE, I found a versioning problem that makes impossible to require or conflict correct version of systemd-presets-branding symbol: systemd-presets-branding-SLE has version 12.1 in SLE 12 SP3. systemd-presets-branding-openSUSE has version 0.3 in Leap 42.3. systemd-presets-branding-openSUSE has version 0.4 in Tumbleweed. All three packages export symbol systemd-presets-branding = %{version} This versioning is not usable. Now I am going to add uuidd to both Leap and SLE. It requires version increment for branding package and conflict in util-linux package. We have to make branding versioning consistent between SLE and openSUSE. And we have to use numbers > 12.1. Maybe all branding packages should use: Version: %{suse_version} or Version: %{suse_version}.1 >From systemd-presets-branding-SLE: Wed Feb 12 16:35:33 UTC 2014 - meissner(a)suse.com - bump version to match product This versioning change was never done in systemd-presets-branding-SLE. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1033277] New: Gnome does not scale all elements on 4k display with wayland
by bugzilla_noreply＠novell.com 29 Jun '20

29 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1033277 Bug ID: 1033277 Summary: Gnome does not scale all elements on 4k display with wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 720542 --> http://bugzilla.suse.com/attachment.cgi?id=720542&action=edit screenshot.png In multimonitor setup where one screen is 4k and other is normal fullhd the scaling seem to work weirdly. See the attached image, the gnome shell menu is still tiny as hell compared to the terminal bellow it. There also is a bit of problem with mutter as it by default does not scale the elements at all unless I patch it with patch I will attach as another comment. Last it seems that mutter does not tell this scaling factor to Qt applications, thus they are remaining really tiny, unless I override them via env variable. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1001473] New: Can not record screen via gnome-shell's integrated screen-recorder
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1001473 Bug ID: 1001473 Summary: Can not record screen via gnome-shell's integrated screen-recorder Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: tbechtold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is Tumbleweed 20160925 with gnome-shell 3.22 (but I had the same problem with gnome-shell 3.20). When starting gnome-shell recording and after some seconds stop it, the resulting file has 0 bytes and no recording is available. The log output is: Sep 27 16:11:50 basilikum org.gnome.Shell.desktop[2613]: Recording to /home/tom/Videos/Screencast from 27.09.2016 16:11:50.webm Sep 27 16:11:50 basilikum gnome-shell[2613]: Error in recording pipeline: Internal data flow error. Sep 27 16:11:50 basilikum gnome-shell[2613]: recorder_record_frame: assertion 'recorder->current_pipeline != NULL' failed Sep 27 16:11:54 basilikum gnome-shell[2613]: shell_recorder_close: assertion 'recorder->state != RECORDER_STATE_CLOSED' failed -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1036432] New: gnome-shell crashes when restarting display-manager service
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1036432 Bug ID: 1036432 Summary: gnome-shell crashes when restarting display-manager service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: vliaskovitis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 722858 --> http://bugzilla.opensuse.org/attachment.cgi?id=722858&action=edit core dump backtrace of gnome-shell gnome-shell crashes in mutter when attempting to restart the display-manager (systemctl restart display-manager) from a VT. Attached is the gnome-shell backtrace. It looks like an X11 error. Tested with TW20170407 and current TW. I can also open a GNOME bugzilla, if the issue is suspected to be an upstream mutter/gnome-shell bug. Sometimes when restarting the display-manager, there is no segfault, but there are weird input problems and/or screen tearing in the VT. I will open a separate ticket for that if I can reproduce. -- You are receiving this mail because: You are on the CC list for the bug.

2 2