October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191036] New: google-guest-oslogin: use %_pam_moduledir
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1191036 Bug ID: 1191036 Summary: google-guest-oslogin: use %_pam_moduledir Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: svollath(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adrian.glaubitz(a)suse.com, aosthof(a)suse.com, coolo(a)suse.com, dleuenberger(a)suse.com, dmueller(a)suse.com, ikapelyukhin(a)suse.com, james.mason(a)suse.com, jdsn(a)suse.com, ms(a)suse.com, rjschwei(a)suse.com, sean.marlow(a)suse.com, thardeck(a)suse.com Blocks: 1190946 Found By: --- Blocker: --- The pam package offers a number of macros to avoid hardcoding directory names in spec files: https://build.opensuse.org/package/view_file/openSUSE:Factory/pam/macros.pam Please consider using at least the %_pam_moduledir macro in order to have the package follow UsrMerge. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1079439] New: New area for ARCES Inter-Department Research Center Bologna
by bugzilla_noreply＠novell.com 26 Sep '22

26 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1079439 Bug ID: 1079439 Summary: New area for ARCES Inter-Department Research Center Bologna Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request Assignee: mrueckert(a)suse.com Reporter: marco.giusti(a)posteo.de QA Contact: adrian(a)suse.com Found By: --- Blocker: --- We first reached OBS at ARCES[1] after the demand of porting our application, Virtualbricks[2], to SLE 12. Even without any experience with SUSE or RPM, OBS allowed us to easily create the needed packages and to deliver the software to our partners. Convinced of the benefits of OBS we want to exploit it more. Following the advice from adrianS_ in #opensuse-buildservice here I ask for a dedicated space that could be recognized as connected to us, ideally with arces.unibo.it in the name. Here[3] you can see the results of my attempts made with my account. For a confirmation of the officiality* of my request you can contact Carlo Caini[4], Associate Professor at ARCES, who directed the development of Virtualbricks the last years. A few words about Virtualbricks and how it is exploited by ARCES. Virtualbricks is a frontend for the management of Qemu Virtual Machines (VMs) and VDE virtualized network devices (switches, channel emulators, etc.). Although it can be used to manage isolated VMs, its peculiar aim is to design and manage testbeds consisting of many VMs interconnected by VDE elements. In other words, it allows to extend the concept of VM to testbeds, which thanks to Virtualbricks can become entirely software-defined. Among the wide variety of possible applications, we have academic research and teaching on computer networks. In particular, we would like to use this space as main hub to distribute our software to the students of the course Protocols and Architectures for Space Networks, master degrees in TLC and Computer Engineering of the University of Bologna, as well as to our research partners, including some European space agencies (ESA, DLR). Thank you for taking this request in account. Marco * Although this request received the consensus of the Director of ARCES, this space will not be recognized as *official* by the University of Bologna i.e. it will not receive any direct support from University of Bologna outside our own effort to maintain it. [1] http://www.arces.unibo.it/en [2] https://github.com/virtualsquare/virtualbricks [3] https://build.opensuse.org/project/show/home:marcogiusti [4] https://www.unibo.it/sitoweb/carlo.caini/en -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1062260] New: Repository medical gone ... where are the packages?
by bugzilla_noreply＠novell.com 26 Sep '22

26 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1062260 Bug ID: 1062260 Summary: Repository medical gone ... where are the packages? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- I'd like to know where the packages of the former repository medical are located? I'm missing the packages aeskulap, xmedcon, ... -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1137381] New: A package name passed to the lang_package macro with the -n option is not included in the summary and description
by bugzilla_noreply＠novell.com 26 Sep '22

26 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137381 Bug ID: 1137381 Summary: A package name passed to the lang_package macro with the -n option is not included in the summary and description Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ralf.habacker(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- See implementation for macro lang_package at https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0:Update/rpm/… for details -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1185512] New: dracut (mkinitrd) does not update /etc/crypttab
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1185512 Bug ID: 1185512 Summary: dracut (mkinitrd) does not update /etc/crypttab Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem 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: --- After changing /etc/crypttab and rebuilding initrd, I noticed (after booting) that the system failed to boot as the /etc/inittab in initrd was obsolete: # ll /etc/crypttab; lsinitrd |grep crypttab -rw------- 1 root root 173 Apr 30 18:35 /etc/crypttab -rw------- 1 root root 37 Mar 13 17:02 etc/crypttab Problem caused during boot: 2021-04-29T14:01:30.712242+02:00 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-7135c231\x2d90f1\x2d4a16\x2daf63\x2d3d7190a1f1c0.device. 2021-04-29T14:01:30.712591+02:00 localhost systemd[1]: Dependency failed for /dev/disk/by-uuid/7135c231-90f1-4a16-af63-3d7190a1f1c0. 2021-04-29T14:01:30.712973+02:00 localhost systemd[1]: dev-disk-by\x2duuid-7135c231\x2d90f1\x2d4a16\x2daf63\x2d3d7190a1f1c0.swap: Job dev-disk-by\x2duuid-7135c231\x2d90f1\x2d4a16\x2daf63\ x2d3d7190a1f1c0.swap/start failed with result 'dependency'. The workaround was to mount the root, add "nofail" to /etc/fstab, them rebuild initrd and reboot. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1180373] New: Welcome: The translation of "Współtwórz" is wrong
by bugzilla_noreply＠suse.com 25 Sep '22

25 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180373 Bug ID: 1180373 Summary: Welcome: The translation of "Wsp��tw��rz" is wrong Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: giecrilj(a)stegny.2a.pl QA Contact: ke(a)suse.com Found By: --- Blocker: --- "B��d�� cz��cia spo��eczno��i openSUSE" It seems nobody has bothered to check the spelling. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1093827] New: imagewriter fails with dbus error
by bugzilla_noreply＠novell.com 24 Sep '22

24 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1093827 Bug ID: 1093827 Summary: imagewriter fails with dbus error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hacking(a)mail.quatrox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SUSE Studio Image Writer (imagewriter) does not work for me (in Tumbleweed). The GUI opens and I select the image and device and click write. Then it asks to umount the disk (if it is already mounted). The partitions are now unmounted. It now asks me to confirm to overwrite the content of the device, and I click OK. Now nothing is happening for maybe 30 seconds. Then a dialog window appears with the following text: DBUS error (sdc): Did not receive reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. The dialog only gives me the option to accept this by pressing OK. Then a new dialog appears with the following text: Couldn't open /dev/sdc: Resource temporarily unavailable Again, I have to press OK. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1153174] New: Yasts's "%posttrans" progress display gets stuck in online_update
by bugzilla_noreply＠novell.com 22 Sep '22

22 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1153174 Bug ID: 1153174 Summary: Yasts's "%posttrans" progress display gets stuck in online_update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When updating many packages (e.g. libreoffice, kernel, etc.), I noticed that the "posttrans" display displayed progress for libreoffice icons up to 60%, then got stuck, and it was the last posttrans indicator seen. However from the noises of my disks I noticed that the kernel also had triggered rebuilding the initrd and reinstalling GRUB2. >From that I conclude that the posttrans progress display is broken. I also searched y2log fro "posttrans:" messages, confirming my point of view: 2019-10-07 09:39:12 <1> pc(4931) [zypp::posttrans] RpmPostTransCollector.cc(collectScriptFromPackage):77 COLLECT posttrans: /var/adm/update-scripts/posttransl4NIpO/libreoffice-icon-themes-6.2.7.1-lp151.3.6.1.noarch.rpmLnrBBe{- 0700 0/0 size 254} 2019-10-07 09:40:56 <1> pc(4931) [zypp::posttrans] RpmPostTransCollector.cc(collectScriptFromPackage):77 COLLECT posttrans: /var/adm/update-scripts/posttransl4NIpO/ibus-1.5.19-lp151.2.3.1.x86_64.rpmysd9Ev{- 0700 0/0 size 24} 2019-10-07 09:41:22 <1> pc(4931) [zypp::posttrans] RpmPostTransCollector.cc(collectScriptFromPackage):77 COLLECT posttrans: /var/adm/update-scripts/posttransl4NIpO/libreoffice-l10n-en-6.2.7.1-lp151.3.6.1.noarch.rpmlRMsQg{- 0700 0/0 size 238} 2019-10-07 09:42:23 <1> pc(4931) [zypp::posttrans] RpmPostTransCollector.cc(collectScriptFromPackage):77 COLLECT posttrans: /var/adm/update-scripts/posttransl4NIpO/device-mapper-1.02.149-lp151.4.3.1.x86_64.rpm7jPj3s{- 0700 0/0 size 167} 2019-10-07 09:42:39 <1> pcrz00066(4931) [zypp::posttrans] RpmPostTransCollector.cc(collectScriptFromPackage):77 COLLECT posttrans: /var/adm/update-scripts/posttransl4NIpO/lvm2-2.02.180-lp151.4.3.1.x86_64.rpmH4FrlA{- 0700 0/0 size 167} [...then the scripts are executed...] device-mapper calls dracut to rebuild the initrd All the scripts were actually executed, but not displayed 2019-10-07 09:45:53 <2> pc(4931) [PLUGIN] PluginScript.cc(~PluginDumpStderr):75 ! INFO:root:COMMITEND -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1177262] New: Zypper does not honor locked kernel packages
by bugzilla_noreply＠suse.com 22 Sep '22

22 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177262 Bug ID: 1177262 Summary: Zypper does not honor locked kernel packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: arcasinky(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Machine in question uses Kernel:stable repository for kernels. I am attempting to configure zypper to not also install kernels from the normal Leap 15.2 update repository. Presently, the 15.2 update repo provides 5.3.x kernels. The Kernel:stable repo provides 5.8.x kernels. Currently-installed kernel packages: # rpm -qa | grep kernel-default-5 kernel-default-5.8.11-1.1.gf4bb27a.x86_64 kernel-default-5.8.12-1.1.g79e03c2.x86_64 kernel-default-5.8.13-1.1.gea492d4.x86_64 Test #1: create a package lock for 5.3.* kernels: # zypper al kernel-default-5.3* kernel-default-devel-5.3* kernel-devel-5.3* kernel-source-5.3* kernel-syms-5.3* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+---------------------------+---------+----------- 1 | kernel-default-5.3* | package | (any) 2 | kernel-default-devel-5.3* | package | (any) 3 | kernel-devel-5.3* | package | (any) 4 | kernel-source-5.3* | package | (any) 5 | kernel-syms-5.3* | package | (any) # zypper update <stuff> The following 11 NEW packages are going to be installed: kernel-default-5.3.18-lp152.44.1 kernel-default-5.8.13-2.1.g08db7a3 kernel-default-devel-5.3.18-lp152.44.1 kernel-default-devel-5.8.13-2.1.g08db7a3 kernel-devel-5.3.18-lp152.44.1 kernel-devel-5.8.13-2.1.g08db7a3 kernel-preempt-devel kernel-source-5.3.18-lp152.44.1 kernel-source-5.8.13-2.1.g08db7a3 kernel-syms-5.3.18-lp152.44.1 kernel-syms-5.8.13-2.1.g08db7a3 <stuff> RESULTS: zypper ignores the package lock and wants to install 5.3.18 kernel. Test #2: Remove all package locks and create repository locks to prevent kernels from being installed from the 15.2 updates repository: # zypper al -r "openSUSE-Leap-15.2-Update" kernel-default* kernel-default-devel* kernel-syms* kernel-source* kernel-macros* kernel-devel* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+-----------------------+---------+------------ 1 | kernel-default* | package | repo-update 2 | kernel-default-devel* | package | repo-update 3 | kernel-devel* | package | repo-update 4 | kernel-macros* | package | repo-update 5 | kernel-source* | package | repo-update 6 | kernel-syms* | package | repo-update # zypper update <stuff> The following 11 NEW packages are going to be installed: kernel-default-5.3.18-lp152.19.2 kernel-default-5.8.13-2.1.g08db7a3 kernel-default-devel-5.3.18-lp152.19.2 kernel-default-devel-5.8.13-2.1.g08db7a3 kernel-devel-5.3.18-lp152.19.2 kernel-devel-5.8.13-2.1.g08db7a3 kernel-preempt-devel kernel-source-5.3.18-lp152.19.2 kernel-source-5.8.13-2.1.g08db7a3 kernel-syms-5.3.18-lp152.19.2 kernel-syms-5.8.13-2.1.g08db7a3 <stuff> RESULTS: No change. The repository locks are ignored. zypper continues to want to install 5.3.18. Test #3: Remove those locks, create repository locks for Kernel:stable. # zypper al -r "Kernel:stable" kernel-default* kernel-default-devel* kernel-syms* kernel-source* kernel-macros* kernel-devel* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+-----------------------+---------+-------------- 1 | kernel-default* | package | Kernel:stable 2 | kernel-default-devel* | package | Kernel:stable 3 | kernel-devel* | package | Kernel:stable 4 | kernel-macros* | package | Kernel:stable 5 | kernel-source* | package | Kernel:stable 6 | kernel-syms* | package | Kernel:stable # zypper update <stuff> The following 6 NEW packages are going to be installed: kernel-default-5.3.18-lp152.44.1 kernel-default-devel-5.3.18-lp152.44.1 kernel-devel-5.3.18-lp152.44.1 kernel-preempt-devel kernel-source-5.3.18-lp152.44.1 kernel-syms-5.3.18-lp152.44.1 <stuff> RESULTS: The locks for Kernel:stable are honored. The 5.8.13 kernels are no longer marked for installation. Final test: Remove the Kernel:stable locks and create repository locks for "@System": # zypper al -r "@System" kernel-default* kernel-default-devel* kernel-syms* kernel-source* kernel-macros* kernel-devel* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+-----------------------+---------+----------- 1 | kernel-default* | package | (any) 2 | kernel-default-devel* | package | (any) 3 | kernel-devel* | package | (any) 4 | kernel-macros* | package | (any) 5 | kernel-source* | package | (any) 6 | kernel-syms* | package | (any) # zypper update <stuff> The following 31 items are locked and will not be changed by any action: Available: kernel-default-base kernel-default-base-rebuild kernel-default-debuginfo kernel-default-debugsource kernel-default-devel-debuginfo kernel-default-livepatch-devel kernel-devel-rt kernel-source-rt kernel-source-vanilla kernel-syms-rt <stuff> The following 9 package updates will NOT be installed: kernel-default-5.8.13-2.1.g08db7a3 kernel-default-devel-5.8.13-2.1.g08db7a3 kernel-devel-5.8.13-2.1.g08db7a3 kernel-macros kernel-source-5.8.13-2.1.g08db7a3 kernel-syms-5.8.13-2.1.g08db7a3 libseccomp-devel ... <stuff> RESULTS: That also seems to work. No kernels are marked for installation now. ---------- So, I can create a repository lock to prevent kernels from being installed from Kernel:stable. I can create a global @System lock to prevent all kernels from being installed. But I seem to be unable to create a lock to specifically prevent 5.3.18 kernels from being installed from the 15.2 updates repo while still allowing kernels to be installed from Kernel:stable. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1125814] New: [Build 20190125] YaST2 keyboard module applies settings even when Cancel button is pressed
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1125814 Bug ID: 1125814 Summary: [Build 20190125] YaST2 keyboard module applies settings even when Cancel button is pressed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: riafarov(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 797088 --> http://bugzilla.suse.com/attachment.cgi?id=797088&action=edit YaST logs ## Steps to reproduce: 1. Change X11 keyboard setting (e.g. run setxkbmap -layout us,ru) 2. Run yast2 keyboard module 3. English US is preselected 4. Press Cancel button 5. English US is set as a keyboard layout, so settings from step 1) are overwritten. Please, find logs in the attachment. -- You are receiving this mail because: You are on the CC list for the bug.

2 8