May 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1029979] New: util-linux has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029979 Bug ID: 1029979 Summary: util-linux has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- util-linux is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1029978] New: tcsh has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029978 Bug ID: 1029978 Summary: tcsh has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- tcsh is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1029974] New: rpm has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029974 Bug ID: 1029974 Summary: rpm has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rpm is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1029972] New: procps has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029972 Bug ID: 1029972 Summary: procps has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- procps is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1025744] New: Shaking rendering on windows resize or some with transparency
by bugzilla_noreply＠novell.com 20 Feb '21

20 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1025744 Bug ID: 1025744 Summary: Shaking rendering on windows resize or some with transparency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: heitorcmj(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- I can't describe as a log what is exactly occurring. Please watch the video I uploaded to try to describe it. When I type an URL in the Firefox the search combobox shakes as well. When resizing a window, as shown in the video, the problem occurs too. When transparency is enable in Terminator, the bug blur all the window and when I hold it with the mouse, the blur is gone. Type again and it blurs again. When transparency is disable, it doesn't happens. In Konsole, the blur doesn't occurs, even if transparency is enable. https://youtu.be/drm_lHXTIBM -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 981271] New: KTTSMgr cannot use festival 2.4 in 13.1 or 13.2 or 42.1
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=981271 Bug ID: 981271 Summary: KTTSMgr cannot use festival 2.4 in 13.1 or 13.2 or 42.1 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 URL: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2657 OS: Other Status: NEW Keywords: accessibility Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: anixx(a)opensuse.org Found By: --- Blocker: --- To reproduce: 1.ensure sound system works reliably 2.install festival and kdeaccessibility3 or trinity-tdeaccessibility from standard repos 3.enable festival with chkconfig (no systemd service for it exists) 4.open a KDE3 or TDE session 5.open KTTSMgr 6.try to add or edit a talker (talker tab) Actual behavior: 1.voice query fails 2.Enable on General tab cannot be selected 3.TTS cannot produce sound Expected behavior: 1.voice query succeeds 2.enabling on General tab is possible 3.TTS works as expected (e.g. speak clipboard) Notes: 1-KDE3's KTTSMgr on 13.1 on host Easystreet made sound until most recent updating, which replaced festival 2.1 with 2.4. Reverting to festival 2.1 from OSS repo restored sound. 2.KDE3' KTTSMgr on 13.2 had never been made to find voices or make sound on host Easystreet. I was only able to make it find voices and make sound after replacing its installed festival 2.4 from KDE3 repo with 2.1 from OSS repo. 3.TDE's KTTSMgr on 42.1 on hosts Easystreet and gx62b would not find voices or make sound until I replaced their festival 2.4 with the 2.1 version from 13.2's OSS repo. 4.TDE's KTTSMgr on Debian stretch on host Easystreet works as expected with its own festival 2.4. Yet to do is figure out why same OS/KTTSMgr/festival on host big41 does not output sound, though it does claim to find voices and appear fully configured to output sound, and other apps do output sound. 5.mailing list thread: http://trinity-users.pearsoncomputing.net/?0::10248 -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 1017652] New: tracker-extract process generating core dumps through udev bad system call to socket()
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1017652 Bug ID: 1017652 Summary: tracker-extract process generating core dumps through udev bad system call to socket() Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: bwilson3013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: After updating openSUSE Tumbleweed yesterday (12/29), I discovered that the tracker-extract process was cyclically failing and causing core dumps to be generated through systemd-coredump. The issue does not start until I log into the GNOME desktop (Wayland and/or X.org), and is not present if I log into the IceWM desktop. When I log into the GNOME desktop, I quickly hear my laptop fans kick into high gear, and I can see several (6-8) systemd-coredump processes running to generate the core dump files. I can see the new core-dump files being actively created in /var/lib/systemd/coredump/ When I first noticed this issue, I was using the packman-essentials repo for codes. I disabled the packman-essentials repo and reverted to the official Tumbleweed versions, and the issue is still present. I did a little debugging with the systemd coredumpctl utility, and the error seems to be caused by a bad system call in glibc socket(). Here's the gdb output and backtrace: Core was generated by `/usr/lib/tracker-extract'. Program terminated with signal SIGSYS, Bad system call. #0 0x00007f34356a1587 in socket () at ../sysdeps/unix/syscall-template.S:84 84 ../sysdeps/unix/syscall-template.S: No such file or directory. [Current thread is 1 (Thread 0x7f3413b15700 (LWP 2777))] (gdb) bt #0 0x00007f34356a1587 in socket () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f342fb0d304 in udev_monitor_new_from_netlink_fd (udev=0x7f340c379be0, name=<optimized out>, fd=-1) at src/libudev/libudev-monitor.c:207 #2 0x00007f343178a3a2 in () at /usr/lib64/libgudev-1.0.so.0 #3 0x00007f3435e9f0d7 in () at /usr/lib64/libgobject-2.0.so.0 #4 0x00007f3435ea0a6e in g_object_new_valist () at /usr/lib64/libgobject-2.0.so.0 #5 0x00007f3435ea0d11 in g_object_new () at /usr/lib64/libgobject-2.0.so.0 #6 0x00007f343178a537 in g_udev_client_new () at /usr/lib64/libgudev-1.0.so.0 #7 0x00007f33fe030d3a in () at /usr/lib64/gstreamer-1.0/libgstvideo4linux2.so #8 0x00007f33fe00ea53 in () at /usr/lib64/gstreamer-1.0/libgstvideo4linux2.so #9 0x00007f34207d10f7 in () at /usr/lib64/libgstreamer-1.0.so.0 #10 0x00007f34207d3068 in () at /usr/lib64/libgstreamer-1.0.so.0 #11 0x00007f34207dfc0e in () at /usr/lib64/libgstreamer-1.0.so.0 #12 0x00007f34207e0d01 in () at /usr/lib64/libgstreamer-1.0.so.0 #13 0x00007f34207e0ed6 in () at /usr/lib64/libgstreamer-1.0.so.0 #14 0x00007f34207e2b24 in gst_update_registry () at /usr/lib64/libgstreamer-1.0.so.0 #15 0x00007f342077d41e in () at /usr/lib64/libgstreamer-1.0.so.0 #16 0x00007f3435bcc988 in g_option_context_parse () at /usr/lib64/libglib-2.0.so.0 #17 0x00007f342077ddef in gst_init_check () at /usr/lib64/libgstreamer-1.0.so.0 #18 0x00007f342077de44 in gst_init () at /usr/lib64/libgstreamer-1.0.so.0 #19 0x00007f342110434b in tracker_extract_gstreamer (uri=uri@entry=0x7f340c007930 "file:///home/bwilson3013/Music/moe_/Sticks%20and%20Stones/02%20Sticks%20and%20Stones.m4a", info=info@entry=0x7f3418003060, type=type@entry=EXTRACT_MIME_AUDIO) at tracker-extract-gstreamer.c:1341 #20 0x00007f3421105b59 in tracker_extract_get_metadata (info=0x7f3418003060) at tracker-extract-gstreamer.c:1470 #21 0x000000000040ba86 in get_file_metadata (task=task@entry=0x17ad590, info_out=info_out@entry=0x7f3413b14d10) at tracker-extract.c:326 #22 0x000000000040bb53 in get_metadata (task=0x17ad590) at tracker-extract.c:510 #23 0x000000000040bbb0 in single_thread_get_metadata (queue=0x1932510) at tracker-extract.c:538 #24 0x00007f3435be81c5 in () at /usr/lib64/libglib-2.0.so.0 #25 0x00007f343595d454 in start_thread (arg=0x7f3413b15700) at pthread_create.c:333 #26 0x00007f34356a037f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Reproducible: Always Steps to Reproduce: 1. Turn on computer 2. Log into GNOME 3. See systemd-coredump processes running Actual Results: New core dump files for /usr/lib/tracker-extract appear in /var/lib/systemd/coredump/ Expected Results: GNOME tracker (or udev) should not be generating core dumps -- You are receiving this mail because: You are on the CC list for the bug.

2 68

[Bug 912059] New: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=912059 Bug ID: 912059 Summary: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 618858 --> http://bugzilla.opensuse.org/attachment.cgi?id=618858&action=edit wrong connection info of networkmanager plugin Create several users. Create in user A a connection with wpa2 encryption, choose: only this user can connect. Save and connect. Look at the list of the plasmoid: it shows all available wlan as not connected and the one you created as connected. Now change to user B or C. As you are still up with user A and you are connected, now in user B or C it should show the same as in user A. Only it should not be possible to end simply this connection or to start it. But you will be able to use it. What happens: in B or C respectively, the list of all available stations shows up as "connected". So in theory you are connected to all wireless of the area. All? No, some do show up correctly as "not connected" but the list here is so long that I can show only the beginning of the screen-shot. The output of ifconfig and netstat seem normal. So this seems to be more an apparent than a real bug. I join a screenshot. What should have done the program: show the correct connection information. Screen-shot: the only "real" connection iw the one with the button disconnect. The other ssids are from the neighborhood. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 980313] New: /usr/lib/zypp/plugins/commit/susemanager should be moved to susemanager related package and not be part of base salt-minion
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=980313 Bug ID: 980313 Summary: /usr/lib/zypp/plugins/commit/susemanager should be moved to susemanager related package and not be part of base salt-minion Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- seen with salt-minion-2015.8.8-68.1.x86_64 from systemsmanagement:saltstack the salt setup on the machine was turned off atm and this noticably slows down all zypp operations. if this plugin is mostly for susemanager it shouldnt be part of the normal salt-minion package. if it is meant to be used with normal salt, i would recommend renaming it. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 978833] New: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=978833 Bug ID: 978833 Summary: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bmaryniuk(a)suse.com Reporter: tchatzimichos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- pkgrepo.managed priority attribute shows the following error: Failed to configure repo 'NON_Public:Infrastructure': zypper command failed: Invalid priority ''102''. Use a positive integer number. The greater the number, the lower the priority. -- You are receiving this mail because: You are on the CC list for the bug.

2 10