May 2018 - openSUSE Bugs - openSUSE Mailing Lists

[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 1049382] New: geany does not produce consistent output
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1049382 Bug ID: 1049382 Summary: geany does not produce consistent output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- When the glfw package is built, it calls geany -v -c geany_config -g glfw.c.tags ...c but this produces varying results probably depending on some ordering in the filesystem. Diffing the build logs gave: - In file included from /tmp/tmp_F5J72Y.cpp:2:0: - ./src/wl_platform.h:30:10: fatal error: wayland-client.h: No such file or directory - #include <wayland-client.h> - ^~~~~~~~~~~~~~~~~~ + In file included from ./src/glx_context.c:28:0, + from /tmp/tmp_PQIPOZ.cpp:1: + ./src/internal.h:175:3: error: #error "No supported window creation API selected" + #error "No supported window creation API selected" + ^~~~~ + In file included from /tmp/tmp_PQIPOZ.cpp:6:0: + ./src/egl_context.h:50:3: error: #error "No supported EGL platform selected" + #error "No supported EGL platform selected" + ^~~~~ + In file included from /tmp/tmp_PQIPOZ.cpp:9:0: + ./src/mir_platform.h:34:10: fatal error: mir_toolkit/mir_client_library.h: No such file or directory + #include <mir_toolkit/mir_client_library.h> + ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. so it seems, the 'compilation terminated' happens in different places. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[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 1084758] New: seccheck fails to cleanup some temporary files created during daily and weekly run
by bugzilla_noreply＠novell.com 14 Feb '21

14 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1084758 Bug ID: 1084758 Summary: seccheck fails to cleanup some temporary files created during daily and weekly run Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: During each run of the daily or weekly cron jobs of seccheck afterwards temporary files are left. Specifically these files are daily: created by the pattern specia_files_owner.XXXX in security_daily_helper.inc e.g. /tmp/specia_files_owner.Jx25 weekly: created by the pattern rpm-md5.XXXX in helper.inc e.g. /tmp/rpm-md5.AYWm This is observed with the rpm seccheck-3.0-lp150.2.3.noarch.rpm from Leap 15.0 Build 153.1 Reproducible: Always Steps to Reproduce: 1.have the seccheck rpm installed (and ensure the START_SECCHK="yes" which is the default) 2.let the time pass when the cron job triggers or tweak it to run "soon" 3.check if the files /tmp/rpm-md5.* or /tmp/specia_files_owner.* exist after the cronjob is finished dependent whether the daily or the weekly cron job was executed. Note: the weekly job can run for several minutes. Actual Results: Temporary files created by the cron job are left after the cron job completes. /tmp/specia_files_owner.???? /tmp/rpm-md5.???? Expected Results: seccheck should not leave temporary files after it finishes successfully. I do not consider this bug is not an actual security problem, it is just in a security related component. As far as I remember it even was already once fixed but crept in again. Note: this is not a new problem, AFAIK it also exists in Leap 42.3 and Tumbleweed, but maybe now is a good time to fix it and the fix is simple. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1094834] New: Unable to install leap 15 on Lenovo T430 along with Windows 10 in dual boot
by bugzilla_noreply＠novell.com 13 Feb '21

13 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1094834 Bug ID: 1094834 Summary: Unable to install leap 15 on Lenovo T430 along with Windows 10 in dual boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: rashmiranjan.mohanty(a)microfocus.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 771520 --> http://bugzilla.suse.com/attachment.cgi?id=771520&action=edit Screenshot of hung install I am unable to install openSUSE Leap 15.0 on my Lenovo T430 laptop. It already has Windows 10 installed. I am trying to install Leap 15 as dual OS. It just gets stuck on the progress bar screen (After loading Kernel and before installer UI comes up). Attaching screenshot. System does not hang though. System responds to Ctrl+Alt+Delete fine and reboots. Additional information : 1. On the same laptop Windows 7 and OpenSUSE leap 42.3 were running fine in dual boot mode before formatting the whole system. 2. I tried DVD and NET media for Leap 15 and it gets stuck at same place. 3. Even tried installing Leap 42.3. That also got stuck in the progress screen. 4. Then I tried installing Fedora 27 and it installed fine. I know since the media is already released there may not be much that can be done to fix the issue in media, but if any workaround can be provided so that I can install Leap 15 on the system, I will be more than happy. -- You are receiving this mail because: You are on the CC list for the bug.

2 43

[Bug 1093098] New: document minimum disk size
by bugzilla_noreply＠novell.com 13 Feb '21

13 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1093098 Bug ID: 1093098 Summary: document minimum disk size Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: lnussel(a)suse.com QA Contact: lnussel(a)suse.com CC: ancor(a)suse.com Found By: --- Blocker: --- The installer will only propose a partitioning scheme if the available hard disk size is larger than 12GB. Administrators wanting to install e.g. very small virtual machines images will have to use the guided setup to tune the parameters for the partitioning manually. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1091103] New: Release notes entry about automatic Qt HiDPI scaling
by bugzilla_noreply＠novell.com 13 Feb '21

13 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1091103 Bug ID: 1091103 Summary: Release notes entry about automatic Qt HiDPI scaling Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: fvogt(a)suse.com QA Contact: lnussel(a)suse.com CC: opensuse-kde-bugs(a)opensuse.org Found By: --- Blocker: --- Release notes entry for bsc#1089932 and related. It's a rather complicated topic unfortunately, with no easy fix or workarounds available. Qt supports automatic per-monitor scaling on X. It uses the DPI value of the virtual X screen to calculate the font size for the primary monitor, which is by default 96. It uses the relative DPI of the primary monitor to derive font DPI for all other monitors. If the primary monitor is HiDPI (>= 144dpi), this means the font has effectively a 0.5x scale on all monitors. Applications which request it (e.g. VLC) have too small text on all monitors. Applications which do not request scaling (e.g. YaST) are not affected and use the same DPI value on all monitors. Applications run on KDE Plasma or GNOME are not affected as Plasma disables automatic scaling by default and GNOME sets Xft.dpi according to the monitor scale. Workarounds: a) Use a non-HiDPI monitor as primary monitor. VLC is then scaled accordingly on the HiDPI monitor. b) Set the font DPI (Xft.dpi) using the DE configuration or "echo Xft.dpi: <value> | xrdb -nocpp -merge" to equal the DPI of the primary monitor c) Disable automatic scaling: export QT_AUTO_SCREEN_SCALE_FACTOR=0 (maybe this part into a separate section?) HiDPI support in sddm: To enable HiDPI support in sddm, edit /etc/sddm.conf and set: [X11] EnableHiDPI=true ServerArguments=-nolisten tcp -dpi <dpi> with <dpi> being 96*scale of the first monitor listed by "xrandr". -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1089315] New: Tracker bug for bugs impacting transactional-netboot
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1089315 Bug ID: 1089315 Summary: Tracker bug for bugs impacting transactional-netboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for all issues having an impact on transactional-netboot. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1089349] New: overlayfs does not work with NFS as lower layer
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1089349 Bug ID: 1089349 Summary: overlayfs does not work with NFS as lower layer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 766955 --> http://bugzilla.suse.com/attachment.cgi?id=766955&action=edit 0001-ovl-Allow-copying-of-files-to-the-upper-layer-from-c.patch When replicating a file/dir from a lower to the upper layer, it tries to copy all xattrs. However, this fails with NFSv4 as it has a special "system.nfs4_acl" xattr" which can't be written if the upper layer isn't NFSv4 (which is not supported anyway). A patch which fixes this issue is attached, but I'm not very familiar with either overlayfs nor xattrs to be able to tell whether it's correct. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[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