September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[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 1185267] New: Firefox 88.0 does not work at all
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1185267 Bug ID: 1185267 Summary: Firefox 88.0 does not work at all Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: mozilla-bugs(a)suse.de Reporter: michael(a)stroeder.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The complete UI of Firefox 88.0 is dysfunctional. Almost nothing is clickable, toolbar is missing etc. FWIW: Binary download from official Firefox web site does not work either, I'm using XFCE4. Did not test other desktop environments. Firefox 87.0 works without any problems. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1178447] New: /etc/xdg/autostart/ibus-autostart.desktop contains extraneous underscore characters
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1178447 Bug ID: 1178447 Summary: /etc/xdg/autostart/ibus-autostart.desktop contains extraneous underscore characters Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: genes1122(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After every update to ibus, I get the following error messages at boot: > sudo journalctl -b | grep -B 1 GLib-GObject-CRITICAL Nov 04 09:15:00 Mobile-PC mate-session[1801]: WARNING: Could not parse desktop file /etc/xdg/autostart/ibus-autostart.desktop: Key file does not have key “Name” in group “Desktop Entry” Nov 04 09:15:00 Mobile-PC mate-session[1801]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x564d076905e0 finalized while still in-construction Nov 04 09:15:00 Mobile-PC mate-session[1801]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead. I downloaded the package from https://software.opensuse.org/package/ibus, and drilled down to the /etc/xdg/autostart/ibus-autostart.desktop file in the package. It's contents are as folllows: [Desktop Entry] _Name=IBus _GenericName=IBus Daemon _Comment=Start IBus daemon Exec=ibus-autostart Icon=ibus-setup Terminal=false Type=Application Categories=System;Utility; StartupNotify=false NoDisplay=true X-GNOME-Autostart-Phase=Applications X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false X-KDE-autostart-after=panel X-KDE-StartupNotify=false Running desktop-file-validate on the file results in: > desktop-file-validate /etc/xdg/autostart/ibus-autostart.desktop ibus-autostart.desktop: error: file contains key "_Name" in group "Desktop Entry", but key names must contain only the characters A-Za-z0-9- (they may have a "[LOCALE]" postfix) ibus-autostart.desktop: error: file contains key "_GenericName" in group "Desktop Entry", but key names must contain only the characters A-Za-z0-9- (they may have a "[LOCALE]" postfix) ibus-autostart.desktop: error: file contains key "_Comment" in group "Desktop Entry", but key names must contain only the characters A-Za-z0-9- (they may have a "[LOCALE]" postfix) ibus-autostart.desktop: hint: value "System;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu ibus-autostart.desktop: error: required key "Name" in group "Desktop Entry" is not present Removing the leading underscores from lines 2-4 in /etc/xdg/autostart/ibus-autostart.desktop gets rid of the boot and desktop-file-validate errors. Why are those underscores in the package file? Shouldn't they be removed? Gene -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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 1191067] New: libewf: finish UsrMerge, install to /usr
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1191067 Bug ID: 1191067 Summary: libewf: finish UsrMerge, install to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Greg.Freemyer(a)gmail.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1191054 Found By: --- Blocker: --- Following up on the discussion on the Factory list https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… All packages installing files into /bin, /sbin, /lib and /lib64 should change the location to the counterpart in /usr instead. Please consider doing that for libewf. If libewf still needs to build for released distros you may keep the legacy locations within a "%if %suse_version < 1550" block of course. If you do that, please do *NOT* install symlinks from/to /usr as it was done with some packages in the past. Move the files in question instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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 1190591] New: drbd: fail to start drbd due to lack of "/usr/var/run/drbd" and "/usr/var/lock/drbd-147-4"
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1190591 Bug ID: 1190591 Summary: drbd: fail to start drbd due to lack of "/usr/var/run/drbd" and "/usr/var/lock/drbd-147-4" 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: nwang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In rpm-4.16.1.3, macros of "--localstatedir" changed from "/var" to "%{_prefix}/var" Which led to DRBD_RUN_DIR/DRBD_LOCK_DIR (and some others in configure.ac) changed from "/var/run"/"/var/lock" to "/usr/var/run"/"/usr/var/lock". However, "/usr/var" not created after boot. Unless manually create "/usr/var/run" and "/usr/var/lock", DRBD will fail to start and have error message like: ``` /usr/var/run/drbd: No such file or directory open(/usr/var/lock/drbd-147-4): No such file or directory Command 'drbdsetup new-minor 1-single-2 4 0' terminated with exit code 20 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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 1170378] New: guile .go files vary from parallelism
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1170378 Bug ID: 1170378 Summary: guile .go files vary from parallelism Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: peter.simons(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jbrielmaier(a)opensuse.org Blocks: 1102408 Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that guile .go object files vary when created in parallel e.g. with make -j3 This not only affected the guile package itself until https://build.opensuse.org/request/show/732638 It also still affects our guix package. But only that one seems to be left. Building non-parallel means a slowdown of roughly 200-250% so 2200-2600 seconds instead of 1100. Not sure, if there is already a better upstream bug than https://issues.guix.gnu.org/issue/20272 You could search for a better report there or file one. I know several Guix devs stumbled over guile .go nondeterminism and would like to see it fixed. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[opensuse-bugs] [Bug 1179173] New: pcscd: Card not transacted: 612
by bugzilla_noreply＠suse.com 23 Oct '22

23 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1179173 Bug ID: 1179173 Summary: pcscd: Card not transacted: 612 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using my REINER SCT cyberJack RFID komfort with e-id (either open-ecard-app, or AusweisApp2) authentication fails after PIN entry when the reader's display says "Tunnel aktiv" and syslog is repeating two messages over and over: pcscd[6597]: 99999999 ifdwrapper.c:477:IFDControl() Card not transacted: 612 pcscd[6597]: 00000039 ifdwrapper.c:364:IFDStatusICC() Card not transacted: 612 pcscd[6597]: 00000005 eventhandler.c:336:EHStatusHandlerThread() Error communicating to: REINER SCT cyberJack RFID komfort (9876543210) 00 00 pcscd[6597]: 00400074 ifdwrapper.c:364:IFDStatusICC() Card not transacted: 612 cscd[6597]: 00000008 eventhandler.c:336:EHStatusHandlerThread() Error communicating to: REINER SCT cyberJack RFID komfort (9876543210) 00 00 pcscd[6597]: 00170145 ifdwrapper.c:364:IFDStatusICC() Card not transacted: 612 pcscd[6597]: 00000006 winscard.c:937:SCardDisconnect() Error resetting card. ... So I suspect there's a bug in pcsc-lite-1.8.24-lp152.2.6.x86_64. -- You are receiving this mail because: You are on the CC list for the bug.

1 2