October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1103239] New: valgrind doesn't understand -z separate-code linked objects
by bugzilla_noreply＠novell.com 10 May '22

10 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1103239 Bug ID: 1103239 Summary: valgrind doesn't understand -z separate-code linked objects Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When linking with -z separate-code (which is the default on x86_64 starting with binutils 2.31 currently in staging) valgrind doesn't seem to find debuginfo anymore. Reproduce like > echo 'int main() { return 0; }' | gcc -g -Wl,-z,separate-code -x c - > valgrind --tool=callgrind ./a.out > grep main callgrind.out.* fn=(220) (below main) fn=(14) dl_main while the correct one looks like cfn=(220) (below main) fn=(246) main fn=(14) dl_main -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1131299] New: fontconfig creates an enormous number of files in /var/cache/fontconfig that are never cleaned up
by bugzilla_noreply＠novell.com 10 May '22

10 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1131299 Bug ID: 1131299 Summary: fontconfig creates an enormous number of files in /var/cache/fontconfig that are never cleaned up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: shundhammer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Earlier today I discovered that I had over 350,000 files in /var/cache/fontconfig that had accumulated in the 4 years that I have been using Tumbleweed. This not only consumed a lot of disk space, it also brought the system to a screeching halt every once in a while: All those files were in that single directory without any subdirectory. Even modern filesystems like XFS (which is what I use on that filesystem) break down completely in terms of performance when so many files are dumped into a single directory. It took more than 20 minutes (!) to remove the files (which needed "ls | xargs rm" because the argument list was much too long). So this directory needs to be cleaned up automatically every once in a while. Better yet, don't create so many files there in the first place. And even better, if so many files are needed, do it like the browsers (for their cache directories) and use an intermediate subdirectory (maybe on multiple levels) for better performance. [shundhammer @ morgul] ~ % cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190318" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20190318" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20190318" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" [shundhammer @ morgul] ~ % rpm -q fontconfig fontconfig-2.13.1-2.1.x86_64 After the cleanup, some files were recreated: [shundhammer @ morgul] ~ % ls -1 /var/cache/fontconfig 4bc6e738-4f14-4bb3-b1c1-113e1440c1c9-x86_64.cache-7 62a2cfd2-5b41-4739-9b75-5f646215de71-x86_64.cache-7 66f92a5c-8bae-4b9c-ba14-cf0cecec77a2-x86_64.cache-7 6f5661a4-b4de-4837-a6cb-77408b27d222-x86_64.cache-7 81ea5785-41f1-4169-a014-a9180af45296-x86_64.cache-7 8bfbb25c-ea26-45ef-9fa8-8bc1cd23e6c8-x86_64.cache-7 a74dc887-85ed-4c63-a0b3-3520f4be1244-x86_64.cache-7 b77b3349-5612-4eeb-95e2-a017bef0b7b7-x86_64.cache-7 be89a7c6-246d-476f-9e7e-e63a135fcfea-x86_64.cache-7 c210a518-33c5-48da-a1b9-55b4a4895c28-x86_64.cache-7 cbe681e7-c178-45ed-a1dd-523a6515af68-x86_64.cache-7 e0f28a10-064e-443c-9da1-1ad111a20ab1-x86_64.cache-7 e50cc437-bedf-4c0d-a1fb-f06def71d136-x86_64.cache-7 f5d4db0f-7acc-412e-b184-266c457f1a79-x86_64.cache-7 f6c4cbb4-f12c-4f74-8d69-264c5d8bbf56-x86_64.cache-7 That is a reasonable number. 350,000+ is not. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1114741] New: Spectacle fail to take screenshot on multi-monitor
by bugzilla_noreply＠novell.com 09 May '22

09 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1114741 Bug ID: 1114741 Summary: Spectacle fail to take screenshot on multi-monitor Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lubomirov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Half of the time or more Spectacle fails to take screenshot from either screen - initial overlay is created, no selection box can be created, and Esc/Enter doesnt work, so its just stuck on the overlay. When overlay is created at start, content from right screen is moved to the left one and right screen remains all white. Following command is applied manually after user login and may or may not be related to the issue: xrandr --output DisplayPort-0 --auto --output HDMI-0 --auto --panning 3840x2160+3840+0 --scale 2x2 --right-of DisplayPort-0 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1112518] New: KDE3 + KDE Plasma doubled taskbar
by bugzilla_noreply＠novell.com 09 May '22

09 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1112518 Bug ID: 1112518 Summary: KDE3 + KDE Plasma doubled taskbar Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: anatoly.a.shipov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 786501 --> http://bugzilla.opensuse.org/attachment.cgi?id=786501&action=edit KDE3 + KDE Plasma doubled taskbar OpenSUSE 15.0 with KDE Plasma. If KDE3 is installed, it will be running 'inside' KDE Plasma. No such behavior if KDE3 is installed on top of MATE (no KDE plasma at all). -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1021059] New: [s390x-port][Build0001] dependency issues when installing default with kde
by bugzilla_noreply＠novell.com 08 May '22

08 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1021059 Bug ID: 1021059 Summary: [s390x-port][Build0001] dependency issues when installing default with kde Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mgriessmeier(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 710981 --> http://bugzilla.opensuse.org/attachment.cgi?id=710981&action=edit y2logs I'm trying to install Tumbleweed on s390x for the first time. Default pattern and KDE as default desktop, resulting in following dependency problems: #### YaST2 conflicts list - generated 2017-01-20 10:15:31 #### nothing provides libpfm.so.4()(64bit) needed by s390-tools-1.34.0-1.1.s390x [ ] do not install grub2-2.02~beta3-16.1.s390x [ ] break s390-tools-1.34.0-1.1.s390x by ignoring some of its dependencies nothing provides plasma5-desktop needed by patterns-openSUSE-kde_plasma-20151112-29.1.s390x [ ] do not install pattern:kde-20151112-29.1.s390x [ ] break patterns-openSUSE-kde_plasma-20151112-29.1.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install ntp-4.2.8p9-1.2.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install xinetd-2.3.15-11.4.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install kernel-default-4.9.0-2.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install pattern:base-20151112-29.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install pattern:x11-20151112-29.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies #### YaST2 conflicts list END ### see attached y2logs -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1102408] New: trackerbug: packages do not build reproducibly from race conditions
by bugzilla_noreply＠novell.com 05 May '22

05 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1102408 Bug ID: 1102408 Summary: trackerbug: packages do not build reproducibly from race conditions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1021335, 1021353 Blocks: 1081754 Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/race When packages build with make -j$N (N>1), it sometimes results in binaries that differ between builds and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. Build results can also be incorrect due to races. Often it is possible to fix races by adding proper dependencies between build targets (e.g. https://bugzilla.sudo.ws/show_bug.cgi?id=842 ) or fixing involved racy tools -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1116053] New: Please convert SysV init scripts by xfs into native systemd services
by bugzilla_noreply＠novell.com 25 Apr '22

25 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1116053 Bug ID: 1116053 Summary: Please convert SysV init scripts by xfs into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1135733] New: vorta package should be updated
by bugzilla_noreply＠novell.com 25 Apr '22

25 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1135733 Bug ID: 1135733 Summary: vorta package should be updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sekhemty(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "vorta" package should be updated https://build.opensuse.org/package/show/openSUSE%3AFactory/vorta currently the repo has version 0.6.10, while upstream has v0.6.20, which includes several fixes and performance improvements -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1081947] New: PAM module pam_keyinit is still not included in the PAM stack
by bugzilla_noreply＠novell.com 20 Apr '22

20 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1081947 Bug ID: 1081947 Summary: PAM module pam_keyinit is still not included in the PAM stack 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Bug #1045886 revealed the lack of the integration of the PAM module "pam_keyinit". The pam_keyinit PAM module ensures that the invoking process has a session keyring other than the user default session keyring. The created session keyring will be linked to the user keyring. Even if it currently works without the integration of "pam_keyinit", in this case the user session keyring is used as fallback, it's strongly recommended to use a session-keyring instead especially for root user, see man user-session-keyring(7). That would also has the benefit to re-enable the keyring support in systemd where each system service gets its own session keyring automatically not linked with the user-keyring (the root one). pam-config gained support for the configuration of pam_keyinit recently [1] but it's still not used and therefore pam_keyinit is still not integrated in the PAM stack. [1] https://build.opensuse.org/request/show/565816 -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[Bug 1128846] New: chrony-dnssrv@.service has wrong path to helper script
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1128846 Bug ID: 1128846 Summary: chrony-dnssrv@.service has wrong path to helper script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomas.blume(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190307" # grep helper /usr/lib/systemd/system/chrony-dnssrv@.service ExecStart=/usr/share/chrony-helper update-dnssrv-servers %I ^^^^^^^^^^^^^^^^^^^^^^^^ rpm -ql chrony | grep helper /usr/lib/chrony/helper ^^^^^^^^^^^^^^^^^^^^^^ Please correct the path in ExecStart to point correctly to the helper script. -- You are receiving this mail because: You are on the CC list for the bug.

2 7