September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1174868] New: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed
by bugzilla_noreply＠suse.com 20 Jul '22

20 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174868 Bug ID: 1174868 Summary: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of our machines here a Thinkpad T480s on openSUSE 15.2 kernel 5.3.18-lp152.33-default. In general this machine was upgraded from LEAP 15.1 to 15.2 and then the problems started to show. The CPU is constantly hotter while working. by 20°C. This machine now freezes sometimes completely. The machine is then - not pingable - no keyboard interaction works - lid close/open does nothng - no mouse interaction works - the notebook is really warm - When a freeze happens also a trim of the journal happens... e.g. we loose the whole journal for the day. - We SSH'ed into the machine and watched via "htop", "journal -f" and "sensors". WHen the machine freezes, there is no significant load via htop seeable, there are no interesting logs in journal and sensors shows that it is simply hotter. Interestingly, we upgraded another machine before (also a Thinkpad T480s) and this does not have any problems. We are btw on the latest firmwares using fwupdmgr. What should we try? How can we debug it? -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1116431] New: systemd tmpfiles does not clean-up sddm-auth files
by bugzilla_noreply＠novell.com 20 Jul '22

20 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1116431 Bug ID: 1116431 Summary: systemd tmpfiles does not clean-up sddm-auth files Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin(a)winter-rosenheim.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Over time, the /tmp directory contains a growing number of sddm-auth files. The systemd tmpfile services makes no attempt to clean them up. I would suggest to add a rule to /etc/tmpfiles.d to remove these files. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1189604] New: Configuration file /etc/xdg/autostart/klipper.desktop is marked executable.
by bugzilla_noreply＠suse.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189604 Bug ID: 1189604 Summary: Configuration file /etc/xdg/autostart/klipper.desktop is marked executable. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: bugrprt21882(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SUMMARY On logout, the systemd user journal contains the entry mentioned below. The rogue file is supplied by the openSUSE "plasma5-workspace" RPM package. STEPS TO REPRODUCE 1. Logout OBSERVED RESULT The following systemd user Journal entry: systemd-xdg-autostart-generator[30490]: Configuration file /etc/xdg/autostart/klipper.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. EXPECTED RESULT No error message ADDITIONAL INFORMATION This seems to be have been seen about 4 years ago on StackExchange. ---------------- I've changed the permissions locally. ---------------- KDE Bug Report: 440792 Comment made 2021-08-09 - "You are using a very old Plasma version, this was fixed long ago" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1189606] New: KDE Plasma package plasma5-workspace-debuginfo is not available.
by bugzilla_noreply＠suse.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189606 Bug ID: 1189606 Summary: KDE Plasma package plasma5-workspace-debuginfo is not available. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: bugrprt21882(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When reporting a KDE Plasma crash to the KDE folks, the Debug Info is needed. Without these packages we can not properly report KDE Plasma crashes upstream to the KDE folks. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1084717] New: The Leap 15.0 installation procedure creates a 500 MB EFI partition
by bugzilla_noreply＠novell.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 Bug ID: 1084717 Summary: The Leap 15.0 installation procedure creates a 500 MB EFI partition Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: bugrprt21882(a)online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Executing a default "fresh" Leap 15.0 installation (Build 153) results in a 500 MB EFI partition being created. Attempting to change the EFI partition size to something less than 256 MB results in an error message indicating that, "the partition size is much too small" being raised. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1168104] New: Issue with Patch openSUSE-2020-401
by bugzilla_noreply＠novell.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1168104 Bug ID: 1168104 Summary: Issue with Patch openSUSE-2020-401 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: bugrprt21882(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running the Patch openSUSE-2020-401 from the KDE Update Plasma - PackageKit - results in the following errors being noted in the Zypper history: # 2020-03-29 15:26:07 Output of grub2-i386-pc-2.02-lp151.21.12.1.noarch.rpm %posttrans script: # update-bootloader: 2020-03-29 15:26:04 <3> update-bootloader-6892 run_command.294: '/usr/lib/bootloader/grub2-efi/ install' failed with exit code 127, output: # <<<<<<<<<<<<<<<< # target = x86_64-efi # + /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg # copying /usr/lib64/efi/grub.efi to /boot/efi/EFI/opensuse/grub.efi # x86_64-efi wird f374r Ihre Plattform installiert. # installation beendet. Keine Fehler aufgetreten. # /usr/sbin/shim-install: Zeile 326: efibootmgr: Kommando nicht gefunden. # /usr/sbin/shim-install: Zeile 352: efibootmgr: Kommando nicht gefunden. # >>>>>>>>>>>>>>>> # update-bootloader: 2020-03-29 15:26:07 <3> update-bootloader-6892 run_command.294: '/usr/lib/bootloader/grub2-efi/config' failed with exit code 127, output: # <<<<<<<<<<<<<<<< # + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg # Generating grub configuration file ... # Found theme: /boot/grub2/themes/openSUSE/theme.txt # Found linux image: /boot/vmlinuz-4.12.14-lp151.28.44-default # Found initrd image: /boot/initrd-4.12.14-lp151.28.44-default # Found linux image: /boot/vmlinuz-4.12.14-lp151.28.40-default # Found initrd image: /boot/initrd-4.12.14-lp151.28.40-default # Found linux image: /boot/vmlinuz-4.12.14-lp151.28.36-default # Found initrd image: /boot/initrd-4.12.14-lp151.28.36-default # /etc/grub.d/80_suse_btrfs_snapshot: Zeile 7: btrfs: Kommando nicht gefunden. # >>>>>>>>>>>>>>>> -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1129549] New: YaST Control Center - Multilingual issue
by bugzilla_noreply＠novell.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129549 Bug ID: 1129549 Summary: YaST Control Center - Multilingual issue Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: bugrprt21882(a)online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- System Language and System Locale: de_DE.UTF-8 User "root" Locale: de_DE.UTF-8 Regardless of whether the Qt graphical user interface or the ncurses text-mode user interface, the following module names and, where noted, also the associated comment, are English: * "Software-Repositories" - comment also in English. * "Create New Directory Server" - comment also in English. * "Create New Kerberos Server" - comment also in English. * "User Logon Management" - comment also in English. The following German language module names have English comments: * "Datum und Zeit". * "Netzwerkeinstellungen". * "Benutzer und Gruppenverwaltung". -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1176666] New: KDE: akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault
by bugzilla_noreply＠suse.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1176666 Bug ID: 1176666 Summary: KDE: akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: bugrprt21882(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- KDE PIM KMail repair tracking: KDE Bug Report 425786 has been resolved and fixed: <https://bugs.kde.org/show_bug.cgi?id=425786> Application: akonadi_archivemail_agent (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.36-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 The changed code has been committed in PIM KMail branch 'release/20.08': <https://invent.kde.org/pim/kmail/commit/0922a95a692f6424773cd28f21a83237a60…> ---------------------------------------------------------------------- Reason for the repair: New, fresh, KMail installation - 1 Akonadi MailDir resource per POP3 Resource - all the needed e-Mail has been re-imported - no e-Mails without a RID - periodic pull of POP3 accounts setup - setting up the first periodic Archive - of the Inbox - pressed "OK" ... * Bong!!!! -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1179448] New: Vim - defaults.vim - :runtime suse.vim points to a non-existent file
by bugzilla_noreply＠suse.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1179448 Bug ID: 1179448 Summary: Vim - defaults.vim - :runtime suse.vim points to a non-existent file Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: bugrprt21882(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Looking at what happened as a result of installing the optional patch openSUSE-2020-2068 - /etc/vimrc is removed and syntax highlighting is now off by default - I noticed that, /usr/share/vim/vim80/vimrc_example.vim sources /usr/share/vim/vim80/defaults.vim which attempts to "ru" 'suse.vim' - which doesn't exist in the Vim "runtimepath". /usr/share/vim/vim80/ does however, contain a 'suse.vimrc' file. Has an oversight occurred in the modification of the Vim ��defaults.vim�� file? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1151703] New: python3-yamllint is missing requirement on python3-setuptools
by bugzilla_noreply＠novell.com 18 Jul '22

18 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1151703 Bug ID: 1151703 Summary: python3-yamllint is missing requirement on python3-setuptools Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: jayvdb(a)gmail.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation yamllint tries to read out information during runtime using "pkg_resources" which is supplied by setuptools, if installed, but the package does not pull in this dependency. ## Steps to reproduce ``` $ docker run --rm -it registry.opensuse.org/opensuse/tumbleweed 5da80e2533ad:/ # zypper -n in python3-yamllint && yamllint Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata ............................................[done] Building repository 'openSUSE-Tumbleweed-Non-Oss' cache .................................................[done] Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata ................................................[done] Building repository 'openSUSE-Tumbleweed-Oss' cache .....................................................[done] Retrieving repository 'openSUSE-Tumbleweed-Update' metadata .............................................[done] Building repository 'openSUSE-Tumbleweed-Update' cache ..................................................[done] Loading repository data... Reading installed packages... Resolving package dependencies... The following 9 NEW packages are going to be installed: libexpat1 libpython3_7m1_0 libuuid1 libyaml-0-2 python-rpm-macros python3-PyYAML python3-base python3-pathspec python3-yamllint 9 new packages to install. Overall download size: 8.9 MiB. Already cached: 0 B. After the operation, additional 34.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package libexpat1-2.2.7-1.2.x86_64 (1/9), 87.7 KiB (206.3 KiB unpacked) Retrieving: libexpat1-2.2.7-1.2.x86_64.rpm ..............................................................[done] Retrieving package libpython3_7m1_0-3.7.3-1.3.x86_64 (2/9), 1.1 MiB ( 3.2 MiB unpacked) Retrieving: libpython3_7m1_0-3.7.3-1.3.x86_64.rpm .......................................................[done] Retrieving package libuuid1-2.34-2.1.x86_64 (3/9), 50.3 KiB ( 30.1 KiB unpacked) Retrieving: libuuid1-2.34-2.1.x86_64.rpm ................................................................[done] Retrieving package libyaml-0-2-0.2.2-2.1.x86_64 (4/9), 53.9 KiB (126.3 KiB unpacked) Retrieving: libyaml-0-2-0.2.2-2.1.x86_64.rpm ............................................................[done] Retrieving package python-rpm-macros-20190610.2ee3233-1.2.noarch (5/9), 25.8 KiB ( 47.0 KiB unpacked) Retrieving: python-rpm-macros-20190610.2ee3233-1.2.noarch.rpm ...........................................[done] Retrieving package python3-base-3.7.3-1.3.x86_64 (6/9), 7.2 MiB ( 29.7 MiB unpacked) Retrieving: python3-base-3.7.3-1.3.x86_64.rpm ...............................................[done (4.5 MiB/s)] Retrieving package python3-pathspec-0.5.9-1.4.noarch (7/9), 47.0 KiB (188.0 KiB unpacked) Retrieving: python3-pathspec-0.5.9-1.4.noarch.rpm .......................................................[done] Retrieving package python3-PyYAML-5.1.2-1.1.x86_64 (8/9), 189.8 KiB (739.6 KiB unpacked) Retrieving: python3-PyYAML-5.1.2-1.1.x86_64.rpm .........................................................[done] Retrieving package python3-yamllint-1.17.0-1.1.noarch (9/9), 71.9 KiB (294.0 KiB unpacked) Retrieving: python3-yamllint-1.17.0-1.1.noarch.rpm ......................................................[done] Checking for file conflicts: ............................................................................[done] (1/9) Installing: libexpat1-2.2.7-1.2.x86_64 ............................................................[done] (2/9) Installing: libpython3_7m1_0-3.7.3-1.3.x86_64 .....................................................[done] (3/9) Installing: libuuid1-2.34-2.1.x86_64 ..............................................................[done] (4/9) Installing: libyaml-0-2-0.2.2-2.1.x86_64 ..........................................................[done] (5/9) Installing: python-rpm-macros-20190610.2ee3233-1.2.noarch .........................................[done] (6/9) Installing: python3-base-3.7.3-1.3.x86_64 .........................................................[done] (7/9) Installing: python3-pathspec-0.5.9-1.4.noarch .....................................................[done] (8/9) Installing: python3-PyYAML-5.1.2-1.1.x86_64 .......................................................[done] (9/9) Installing: python3-yamllint-1.17.0-1.1.noarch ....................................................[done] Traceback (most recent call last): File "/usr/bin/yamllint", line 6, in <module> from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' ``` ``` -- You are receiving this mail because: You are on the CC list for the bug.

2 1