October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[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 1192014] New: provide admin option to NOT automatically REbuild initrds for previously installed kernels
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192014 Bug ID: 1192014 Summary: provide admin option to NOT automatically REbuild initrds for previously installed kernels Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: martin.wilck(a)suse.com Found By: --- Blocker: --- Initial Summary: provide admin option to NOT automatically REbuild initrds for previously installed kernels From bug 1189772, where this request has already had some discussion about how it might be implemented: [quote] > (In reply to Martin Wilck from comment #7) >> (In reply to Felix Miata from comment #6) >> IMO, openSUSE should also have an admin option not to rebuild, regardless of >> use case. What I do on openSUSE is set immutable flag on initrds. It doesn't >> stop the rebuild waste of CPU cycles and SSD writes, but I get the result I >> want. > Fair enough. Please open a feature request. [/quote]: On Debians there's been this to implement admin preference since forever: # cat /etc/initramfs-tools/update-initramfs.conf # # Configuration file for update-initramfs(8) # # # update_initramfs [ yes | all | no ] # # Default is yes # If set to all update-initramfs will update all initramfs # If set to no disables any update to initramfs beside kernel upgrade update_initramfs=no # # backup_initramfs [ yes | no ] # # Default is no # If set to no leaves no .bak backup files. backup_initramfs=no -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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

[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 1184014] New: maliit-keyboard2 is not available in the main repos
by bugzilla_noreply＠suse.com 23 Oct '22

23 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184014 Bug ID: 1184014 Summary: maliit-keyboard2 is not available in the main repos Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: pointedstick(a)zoho.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This package provides the Maliit virtual keyboard, which is required in the KDE Plasma Wayland session ever since support for the much worse QtVirtualKeyboard was removed. However the package is not available in Tumbleweed, meaning that the Plasma Wayland session has no virtual keyboard, making it unusable for touch devices. I see that https://software.opensuse.org/package/maliit-keyboard2 exists in a personal repo. It needs to get moved to the main repo, with any required cleanup such a move would entail. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[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