September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1175678] New: complete packages --unneeded featureset (mostly "apt-mark auto")
by bugzilla_noreply＠suse.com 04 Oct '22

04 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175678 Bug ID: 1175678 Summary: complete packages --unneeded featureset (mostly "apt-mark auto") Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: openSUSE Leap 15.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: duge(a)pre-sense.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE-13.1 (zypper-1.9.*, libzypp-13.9.*) introduced some nice features: # Remove a package and it's dependencies (if unused) zypper remove --clean-deps PACKAGE # Show unused packages, which haven't been explicitly installed zypper packages --unneeded Sadly this featureset still misses some points. This can also be seen in relation to other package managers: https://wiki.archlinux.org/index.php/Pacman/Rosetta#Basic_operations Especially a counterpart to this command is missing: apt-mark auto PACKAGE # remove manually installed property # Additionally these commands would be nice. apt-mark manual PACKAGE apt-mark showmanual # show manually installed packages # But they can be workarounded. (although it's quite nasty) # apt-mark manual PACKAGE zypper install --force PACKAGE # apt-mark showmanual zypper search '' | grep -E '^i\+' Also it would be very helpfull if "zypper packages --unneeded" would work recursive. The command "zypper remove --clean-deps PACKAGE" already seems to work recursive. And Debian's "apt autoremove" also does. What I mean when saying "recursive": Currently "zypper packages --unneeded" only lists packages which are completely unneeded by other packages (and not manually installed). Let's call them package set A. But after removing set A, all packages which where required by packages in set A also become unneeded. So you have to run "zypper packages --unneeded" again. This repeats, until you finally removed only packages, that didn't had requirements to otherwise unneeded packages themselves. Related: https://bugzilla.opensuse.org/show_bug.cgi?id=1002507 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1181970] New: Can't restart service because masked services
by bugzilla_noreply＠suse.com 03 Oct '22

03 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1181970 Bug ID: 1181970 Summary: Can't restart service because masked services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Salt Assignee: salt-maintainers(a)suse.de Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, i am being bothered because each time i do a upgrade on opensuse tumbleweed and need to restart some service like apache, php-fpm, postfix, etc..., i found that they wont restart/start because the next masked partitions. mercurio:/etc/apache2/vhosts.d # systemctl restart apache2.service php-fpm.service postfix.service Failed to restart apache2.service: Unit tmp.mount is masked. Failed to restart php-fpm.service: Unit tmp.mount is masked. Failed to restart postfix.service: Unit var-run.mount is masked. Each time i do update and have to restart/stop the service appear message like the one before. doing: systemctl unmask --now tmp.mount wont do nothing, tryed masking and unmasking again but the issue persist and have to reboot the server to apply those reboot of service. Status of the .mount: mercurio:/etc/apache2/vhosts.d # systemctl status tmp.mount �� tmp.mount - /tmp Loaded: masked (Reason: Unit tmp.mount is masked.) Active: active (mounted) (Result: exit-code) since Mon 2021-02-08 22:01:05 AST; 10min ago Where: /tmp What: tmpfs Tasks: 0 (limit: 4915) CGroup: /system.slice/tmp.mount Feb 08 22:01:05 mercurio umount[16479]: umount: /tmp: target is busy. Feb 08 22:01:05 mercurio systemd[1]: Unmounting /tmp... Feb 08 22:01:05 mercurio systemd[1]: tmp.mount: Mount process exited, code=exited, status=32/n/a Feb 08 22:01:05 mercurio systemd[1]: Failed unmounting /tmp. mercurio:/etc/apache2/vhosts.d # systemctl status var.mount �� var.mount - /var Loaded: masked (Reason: Unit var.mount is masked.) Active: active (mounted) (Result: exit-code) since Mon 2021-02-08 22:01:05 AST; 11min ago Where: /var What: /dev/mapper/vg0-root Tasks: 0 (limit: 4915) CGroup: /system.slice/var.mount Feb 05 20:37:25 localhost systemd[1]: Mounting /var... Feb 05 20:37:25 localhost systemd[1]: Mounted /var. Feb 08 22:01:05 mercurio systemd[1]: Unmounting /var... Feb 08 22:01:05 mercurio umount[16480]: umount: /var: target is busy. Feb 08 22:01:05 mercurio systemd[1]: var.mount: Mount process exited, code=exited, status=32/n/a Feb 08 22:01:05 mercurio systemd[1]: Failed unmounting /var. mercurio:/etc/apache2/vhosts.d # systemctl status var-run.mount �� var-run.mount Loaded: masked (Reason: Unit var-run.mount is masked.) Active: inactive (dead) Condition: start condition failed at Fri 2021-02-05 20:37:25 AST; 3 days ago Feb 05 20:37:25 localhost systemd[1]: Condition check resulted in Runtime Directory being skipped. journalctl said nothing about this issue. systemctl list-units: https://susepaste.org/56464129 -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1183642] New: x2go cannot connect after last update on tumbleweed
by bugzilla_noreply＠suse.com 03 Oct '22

03 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1183642 Bug ID: 1183642 Summary: x2go cannot connect after last update on tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After last update x2go cannot connect to server. Sorry but i cant understand how to collect log files in this case. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1180962] New: Kernel did not see the status numlock from bios.
by bugzilla_noreply＠suse.com 03 Oct '22

03 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1180962 Bug ID: 1180962 Summary: Kernel did not see the status numlock from bios. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel did not see the status numlock from bios. After several updates I found what the numlock status is off by default. Checking the setting in BIOS. It is on by default With settings KBD_NUMLOCK="bios" in /etc/sysconfig/keyboard it is always off. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1173123] New: Alt+F2 sometimes start krunner (Why???)
by bugzilla_noreply＠suse.com 03 Oct '22

03 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1173123 Bug ID: 1173123 Summary: Alt+F2 sometimes start krunner (Why???) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Something wrong with keybind alt+f2 It is start krunner sumtimes under lxde -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1184315] New: Correct messages that contain Deamon to Daemon
by bugzilla_noreply＠suse.com 02 Oct '22

02 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184315 Bug ID: 1184315 Summary: Correct messages that contain Deamon to Daemon Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: ndordea(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I noticed that some messages are slightly incorrect . journalctl -a | grep Deamon Apr 02 11:13:23 xxxxxxxxx systemd[1]: Starting Clamav antivirus Deamon... Apr 02 11:14:28 xxxxxxxxx systemd[1]: Started Clamav antivirus Deamon. ------------ Deamon should be changed to Daemon . Thanks, ND -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1161828] New: Sound crack on some frequency or peak of audio
by bugzilla_noreply＠novell.com 30 Sep '22

30 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1161828 Bug ID: 1161828 Summary: Sound crack on some frequency or peak of audio Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lspci -vvv -s 00:1f.3 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Micro-Star International Co., Ltd. [MSI] Device 1219 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 138 Region 0: Memory at a4310000 (64-bit, non-prefetchable) [size=16K] Region 4: Memory at a4100000 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] Vendor Specific Information: Len=14 <?> Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee00438 Data: 0000 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 993401] New: grub2-install for EFI installs an EFI entry that is not bootable
by bugzilla_noreply＠novell.com 30 Sep '22

30 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=993401 Bug ID: 993401 Summary: grub2-install for EFI installs an EFI entry that is not bootable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: aarch64 OS: openSUSE 42.1 Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: alan(a)softiron.co.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Running grub2-install does not yield a bootable entry in EFI's boot menu. On Leap and Tumbleweed, this means booting relies instead on the startup.nsh in the EFI partition. This occurs on Aarch64 with both AMD/AMI firmware and Tianocore/edk2/OpenPlatformPkg firmware. Steps to reproduce: 1. Install Leap 42.1 from the OEM image 2. Restart and boot the system 2a. Observe that the startup.nsh (in the EFI partition) is used to boot the system. 3. Reboot again, but During boot-up, enter the EFI menu. 3a. Observe that in the boot manager in the EFI menus, there is no entry for Leap. 4. Restart the system or select the UEFI shell option, booting from startup.nsh 5. From the command prompt in Leap, run: grub2-install /dev/sda 6. Reboot the system 7. During start-up enter the EFI menu. 7a. Observe that in the EFI menu there is an entry called opensuse-leap42.1-arm-jeos-devel-efi, or something like it. 8. Select the opensuse-leap* boot menu item and try to boot it. 9. Observe that it does not boot, and returns to the boot menu. 10. Select the UEFI Shell option, and observe that it will boot using startup.nsh. 11. From the Linux command prompt, run "efibootmgr -v" 11a. Observe that the entry for opensuse-leap* is truncated :( 11b. Note the same can be observed by running "dumpstore" from the EFI environment. Note: The same thing happens if the bootloader is re-installed using "yast2 bootloader". Note that this is broken in Leap, but works fine in SLES, probably because the path and OS name for SLES is so much shorter. Interestingly, if I try to add my own entry with the proper path: efibootmgr -c -d /dev/sda -p 1 --loader "EFI\\opensuse-leap42.1-arm-jeos-devel-efi\\grubarm64.efi" -L Test_Entry_By_Alan and then inspect it with: efibootmgr -v I see my entry is truncated too :( Boot0007* Test_Entry_By_Alan HD(1,800,64004,cb3a713f-f051-4c9c-b643-b9e1358f6c2d)File(EFI\opensuse-leap42.1-arm-jeos-devel-ef) In summary, grub2-install and/or efibootmgr is simply putting a boot entry into NVRAM that is truncated and not valid. Thanks! Alan. -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 1180985] New: Kernel 5.10 breaks ethernet connection with lenovo x390
by bugzilla_noreply＠suse.com 30 Sep '22

30 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1180985 Bug ID: 1180985 Summary: Kernel 5.10 breaks ethernet connection with lenovo x390 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fcastelli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a lenovo x390 laptop with an intel CPU. I've been running Tumbleweed on it since a while because I needed a newer kernel compared to Leap to get my network card to work. Everything worked fine since I upgraded to 5.10.x. The upgrade caused the ethernet card to became unreliable (like it happened with old Leap 15.1 kernel). The network card works fine for some time, then it suddenly loses the connection. I can see Gnome NetworkManager trying to setup the card, but the process never ends. The x390 doesn't have a physical eth port, it has a proprietary adapter that provides that to the laptop. This adapter is plagued by the issue. The same issue happens when I connect the computer to its USB-C docking station (an official one provided by Lenovo). The docking station provides an eth port which is affected by this issue. The 5.9.14-1.2 and the 5.9.12-1.1 kernels are the last kernels I tested on my computer that proved to be fine. I'll try to collect more detailed logs from syslog, but right now it's a bit hard for me because I cannot reproduce the issue. I just have to wait for it to happen... -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1163179] New: nscd can't monitor /etc/services after the recent netcfg update
by bugzilla_noreply＠novell.com 29 Sep '22

29 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1163179 Bug ID: 1163179 Summary: nscd can't monitor /etc/services after the recent netcfg update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: arjan.de.jong(a)sighup.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After installing the netcfg update which moves /etc/services to /usr/etc nscd can't monitor the file /etc/services. >From /var/log/zypp/history 2020-02-04 21:03:04|install|netcfg|11.6-5.1|noarch||repo-oss|d37960598c66a976437b84dc749c527b21165630784162c67f9e5a22188937d8| Since that moment I see these entries with "journalctl -u nscd": Feb 04 21:03:04 discovery nscd[2546]: 2546 monitored file `/etc/services` was deleted, removing watch Feb 04 21:03:25 discovery nscd[2546]: 2546 checking for monitored file `/etc/services': No such file or directory Feb 04 21:03:40 discovery nscd[2546]: 2546 checking for monitored file `/etc/services': No such file or directory Feb 04 21:04:00 discovery nscd[2546]: 2546 checking for monitored file `/etc/services': No such file or directory Feb 04 21:04:15 discovery nscd[2546]: 2546 checking for monitored file `/etc/services': No such file or directory Feb 04 21:04:35 discovery nscd[2546]: 2546 checking for monitored file `/etc/services': No such file or directory The entry that states the file was deleted was a single occurence. The entries about no such file or directory continue. -- You are receiving this mail because: You are on the CC list for the bug.

2 5