November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1048692] New: version downgrade of libgcj_bc1
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1048692 Bug ID: 1048692 Summary: version downgrade of libgcj_bc1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 42.2 vs 42.3: libgcj48: libgcj_bc1-4.8.5-24.14.x86_64 is older than libgcj_bc1-6.2.1+r239768-5.5.2.x86_64 in 42.2 libgcj_bc1 came from libgcj-gcc6 which isn't in 42.3. What is correct here? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1048660] New: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts are no longer supported.
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1048660 Bug ID: 1048660 Summary: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts are no longer supported. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: bugrprt21882(a)online.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 13th July 2017: With the Leap 42.2 upgrade of LibreOffice from version 5.2.5 to version 5.3.3 the fact that, with version 5.3 LibreOffice has dropped support for Type 1 (Postscript) fonts was a not so pleasant surprise. Please consider placing a note indicating that, LibreOffice as of version 5.3 no longer supports Type 1 (Postscript) fonts in the Release Notes. Is also, possibly an issue for the Leap 42.3 Release Notes. --------------------------------------------------------- I haven't found anything in the LibreOffice Release Notes indicating this issue: <https://www.libreoffice.org/download/release-notes/> There's only this article in "Linux Magazine": <http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blo…> There's information in this Document Foundation Bug Report: Bug 104701 <https://bugs.documentfoundation.org/show_bug.cgi?id=104701> --------------------------------------------------------- There's possibly help for the folks (like me) with a suite of Type 1 fonts here: <https://slackbuilds.org/repository/14.2/system/afdko/> Haven't tried to build the "Adobe Font Development Kit for OpenType" yet -- will happen later today. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1048392] New: [doc] Extended Permission bits: Konqueror is also the Plasma 5 version
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1048392 Bug ID: 1048392 Summary: [doc] Extended Permission bits: Konqueror is also the Plasma 5 version Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: bugrprt21882(a)online.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 3.2 Dolphin Does Not Set Extended Permission Bits https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.3/#sec.gener… Unfortunately, with Leap 42.3, Konqueror is also the Plasma 5 version and, it also can not set the Extended Permissions bits . . . Therefore, the Leap 42.3, CLI only to toggle the Extended Permission bits . . . -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1111572] New: patch segfaults if it can't write *.orig
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1111572 Bug ID: 1111572 Summary: patch segfaults if it can't write *.orig Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: jdelvare(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 785784 --> http://bugzilla.opensuse.org/attachment.cgi?id=785784&action=edit reproducer (tar.gz) Tumbleweed 20181009, patch-2.7.6-3.5.x86_64 I tried to apply a (non-matching) patch, and when patch tried to create the *.orig file, it printed a long list of error messages: # patch cleanprofile.py < changes.diff patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied [...] patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.origSegmentation fault (core dumped) I'd expect _one_ "Permission denied" message, and no segfault. Reproducer: - unpack the attached tarball (as user) - chown root cleanprofile.py.orig (obviously as root) - run patch cleanprofile.py < changes.diff as user Note: This seems to be related to the files in the attached tarball. If I try with a simple one-line file and a boring patch, patch doesn't segfault. The reproducer files must have something special that send patch into an endless loop. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[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 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