March 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1140434] New: Reduced video quality in vlc/kaffeine since 5.1.10
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1140434 Bug ID: 1140434 Summary: Reduced video quality in vlc/kaffeine since 5.1.10 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Michael.Zapf(a)mizapf.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the upgrade to 5.1.10, the video quality in VLC and kaffeine (using the vlclib) has significantly degraded. It seems as if the vertical resolution has been reduced to 50%, then stretched to fill the frame. vlc was not updated (3.0.7.1 "Vetinari"), so I suspect that the different behavior comes from the kernel update. Here are links that show screenshots I created on the openSUSE KDE Plasma desktop. In both cases, the same program was being shown; I reverted to the previous kernel in the meantime using "start with read-only snapshot". Have a closer look at the TV station logo in the upper left corner to spot the difference most easily. With kernel 5.1.7: http://www.mizapf.eu/files/vlc_5.1.7.png With kernel 5.1.10: http://www.mizapf.eu/files/vlc_5.1.10.png Here is one final screenshot that shows another point of different behavior. When vlc is started, the video output is only half-height for about 1 second or slightly less. Then, the video is stretched to the window height. I created this snapshot by launching VLC and then quickly creating a screenshot. http://www.mizapf.eu/files/vlc_5.1.10_sec1.png I just updated to the newest release 5.1.15, but the reduced quality is still there. -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 1132118] New: Xindy does not run due to incompatible CLISP runtime
by bugzilla_noreply＠novell.com 25 Oct '22

25 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 Bug ID: 1132118 Summary: Xindy does not run due to incompatible CLISP runtime Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: christian-david(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- xindy does not run what can be tested with $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 /usr/lib64/clisp-2.49.92/base/lisp.run: initialization file `/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runtime Same error happens if xindy is used for a “real” task. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1041742] New: Filetriggers do not fire (reliably)
by bugzilla_noreply＠novell.com 25 Oct '22

25 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 Bug ID: 1041742 Summary: Filetriggers do not fire (reliably) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In GNOME:Next, we started experimenting with file triggers (with the goal to lower the number of bugs based on missing post scripts) As a sample, I implemented this trigger (on glib2-tools): %transfiletriggerin -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas %transfiletriggerpostun -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas The trigger is confirmed to work, but in some cases, it seems not to fire, eg on the package 'gdm' (which is currently the reason why http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME… fails to boot to desktop) zypper in --no-recommends gdm => the file trigger is not executed rpm -i gdm-3.24.1.rpm => the trigger actually seems to work (which is why I file it against libzypp) This currently stops us from moving forward and proposing file triggers to be more widely used (even though I think they can solve quite some packaging bugs) The packages in question for testing are all in the GNOME:Next repository (glib2 which has the trigger, it has the %glib2_gsettings_schema_post set to %nil, so packages that use it in their post script only get a dummy - once the implementation is complete, we will of course go and clean those out completely) -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1139369] New: multipath-tools: post-0.8.1 upstream bug fixes
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1139369 Bug ID: 1139369 Summary: multipath-tools: post-0.8.1 upstream bug fixes 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upstream multipath-tools fixes from dm-devel, post 0.8.1 1) libmultipath: make vector_foreach_slot_backwards work as expected - Matters only for foreign/NVMe code (also for "multipath -W", but without user noticeable impact) => Factory/SLE15-SP1 only QA test case: Use NVMe native multipath and run multipathd. Remove one or more NVMe paths. => multipathd crashes. 2) multipathd: fix REALLOC_REPLY with max length reply - fix for cd5a9797e "libmpathcmd(coverity): limit reply length" - Factory/SLE15-SP1 only, the others don't contain the broken commit QA test case: None, corner case which occurs only if a client command gets a reply with >= 32768 bytes. 3) multipath: call store_pathinfo with DI_BLACKLIST - performance; cli_add_path() may add blacklisted path - Factory, SLE15, SLE15-SP1, SLE12-SP3/4 QA test case: Blacklist some paths (by any mechanism other than devnode). Verify that "multipathd show paths" doesn't list the blacklisted devices Run "multipathd add path $X" where $X is one of the blacklisted paths. => ok (expected: fail with msg "blacklisted"). 4) multipathd: fix client response for socket activation - minor corner-case fix - Factory/SLE15-SP1 only QA test case: stop multipathd on a system with some multipath maps. Run "multipathd show topology" => success with empty output (expected: success with correct topology output) 5) libmultipath: get_prio(): really don't reset prio for inaccessible paths - Factory, SLE15, SLE12-SP4, SLE15-SP1 QA test case: perhaps reproducible with a setup with lots of pass loss/reinstate events, by monitoring the topology with "group_by_prio". It's a rare condition though which happens only if a path becomes inaccessible in the small time windw between the state check and the get_prio() call in pathinfo(). See bug 1118495. -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1093168] New: pacemaker: using service template in preun/postun
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1093168 Bug ID: 1093168 Summary: pacemaker: using service template in preun/postun Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- you can not used a service template (foo@.service) without parameter in a specfile with the %service_add/del macros: %preun cts %service_del_preun pacemaker-cts-dummyd@.service %postun cts %service_del_postun pacemaker-cts-dummyd@.service this will just result in errors during uninstall of the package: (1/1) Removing pacemaker-cts-1.1.18+20180430.b12c320f5-1.4.noarch ........[done] Additional rpm output: Failed to stop pacemaker-cts-dummyd@.service: Unit name pacemaker-cts-dummyd@.service is missing the instance name. See system logs and 'systemctl status pacemaker-cts-dummyd@.service' for details. Failed to get load state of pacemaker-cts-dummyd@.service: Unit name pacemaker-cts-dummyd@.service is neither a valid invocation ID nor unit name. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1115512] New: pam-config does not find (nor load) pam_yubico.so
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1115512 Bug ID: 1115512 Summary: pam-config does not find (nor load) pam_yubico.so 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: fred.blaise(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 Build Identifier: After installed pam_yubico, and adding the following line in /etc/pam.d/common-auth, running `sudo pam-config --update` fails with `/etc/pam.d/common-auth-pc: Unknown module pam_yubico.so, ignored!` The module never appears in the --list-modules either. Reproducible: Always Steps to Reproduce: 1. sudo zypper in pam_yubico 2. sudo ldconfig (or reboot) 3. Amend /etc/pam.d/common-auth-pc to add pam_yubico as requirement 4. Run pam-config --update and get ignore message. Actual Results: /etc/pam.d/common-auth-pc: Unknown module pam_yubico.so, ignored! Expected Results: Module loads and I can use my yubikey with pam. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1088177] New: Default Active Titlebar color on openSUSEdark and openSUSEdarkalternate colorchemes
by bugzilla_noreply＠novell.com 23 Oct '22

23 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1088177 Bug ID: 1088177 Summary: Default Active Titlebar color on openSUSEdark and openSUSEdarkalternate colorchemes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: andretiago(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 766009 --> http://bugzilla.suse.com/attachment.cgi?id=766009&action=edit Titlebar active color Default Active Titlebar color of openSUSEdark and openSUSEdarkalternate color schemes looks out of place and it's hard to read. https://i.imgur.com/vshYSxz.png I think the default color should be replaced -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1008674] New: Login difficulties with LightDM 1.20
by bugzilla_noreply＠novell.com 22 Oct '22

22 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1008674 Bug ID: 1008674 Summary: Login difficulties with LightDM 1.20 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I dared to update the display manager to the version “LightDM 1.20.0-1.1”. Unfortunately, I observed that the corresponding graphical login did not work as expected. The information “exist status: 1” was recorded in the systemd journal. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1102216] New: Game area is black in KBreakout 18.04.3.
by bugzilla_noreply＠novell.com 22 Oct '22

22 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1102216 Bug ID: 1102216 Summary: Game area is black in KBreakout 18.04.3. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed the software “kbreakout 18.04.3-1.1” also on my system. Now I notice that the game area is displayed only in black while my terminal window (where I started this program for another test try) is filled with the message “QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings” in a XFCE session. Will any updates appear for a bug report like “Kbreakout 15.11.90 just shows black area where game should be”? https://bugs.kde.org/show_bug.cgi?id=356736 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1163046] New: no AMD Raven/Raven2/Fenghuang (HDMI) sound in Leap 15.2 Alpha chip IDs: 1002:15de 1002:15e3
by bugzilla_noreply＠novell.com 20 Oct '22

20 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 Bug ID: 1163046 Summary: no AMD Raven/Raven2/Fenghuang (HDMI) sound in Leap 15.2 Alpha chip IDs: 1002:15de 1002:15e3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 829509 --> http://bugzilla.opensuse.org/attachment.cgi?id=829509&action=edit alsa-info.txt Initial summary: no [AMD/ATI] Raven/Raven2/Fenghuang (HDMI) sound in Leap 15.2 Alpha chip IDs: 1002:15de 1002:15e3 Forum thread: https://forums.opensuse.org/showthread.php/539008-no-AMD-ATI-Raven-Raven2-F… This failure also applies to 15.1, and whether using KDE3 or IceWM. Neither play system sounds nor Youtubes. > inxi -SAxx System: Host: Easystreet Kernel: 5.3.18-lp152.3-default x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: KDE 3 wm: kwin dm: N/A Distro: openSUSE Leap 15.2 Alpha Audio: Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 1002:15de Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 08:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.3.18-lp152.3-default YaST2 sound module claims to set up two devices, but neither play any test sound. > sudo setup-pulseaudio --enable > asplay -v /usr/share/sounds/alsa/test.wav produces: Playing WAVE '/usr/share/sounds/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ALSA <-> PulseAudio PCM I/O Plugin Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 22050 period_size : 5512 period_time : 125000 tstamp_mode : NONE tstamp_type : GETTIMEOFDAY period_step : 1 avail_min : 5512 period_event : 0 start_threshold : 22050 stop_threshold : 22050 silence_threshold: 0 silence_size : 0 boundary : 6206523236469964800 > paplay /usr/share/sounds/alsa/test.wav > (aka nothing) -- You are receiving this mail because: You are on the CC list for the bug.

2 23