March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1049825] New: zypper bash completion expands non-existing options
by bugzilla_noreply＠novell.com 09 Jan '20

09 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1049825 Bug ID: 1049825 Summary: zypper bash completion expands non-existing options Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There seems to be a bug in the script that extracts available options in zypper. It expands to "*" and "If" $ zypper search [TAB][TAB] * --file-list --name --repo --suggests --case-sensitive --installed-only --not-installed-only --requires --type --conflicts --match-exact --obsoletes --search-descriptions If --details --match-substrings --provides --sort-by-name --details, --match-words --recommends --sort-by-repo This is actually from last two lines of the zypper help output: # zypper help search > -v, --verbose Like --details, with additional information where the > search has matched (useful for search in dependencies). > > * and ? wildcards can also be used within search strings. > If a search string is enclosed in '/', it's interpreted as a regular expression. -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1023732] New: openSUSE:Factory/golang-org-x-net fails to build
by bugzilla_noreply＠novell.com 08 Jan '20

08 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1023732 Bug ID: 1023732 Summary: openSUSE:Factory/golang-org-x-net fails to build 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package golang-org-x-net fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1052970] New: suse-xsl-stylesheets depends on aspell
by bugzilla_noreply＠novell.com 07 Jan '20

07 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1052970 Bug ID: 1052970 Summary: suse-xsl-stylesheets depends on aspell 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: pgajdos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Our management would like to remove aspell from the distro (fate#323578). We need to ensure it is not dependency of any package in Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1053947] New: Korganizer does not display holidays
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1053947 Bug ID: 1053947 Summary: Korganizer does not display holidays Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: eliwap(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running Kontact / Korganizer 17.04.2-1.7.x86_64 (5.5.2) Korganizer does not display any holidays in any view -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 790151] New: When I open nickle-2.70-1.src.rpm,YaST2 finds nothing to install.
by bugzilla_noreply＠novell.com 02 Jan '20

02 Jan '20

https://bugzilla.novell.com/show_bug.cgi?id=790151 https://bugzilla.novell.com/show_bug.cgi?id=790151#c0 Summary: When I open nickle-2.70-1.src.rpm,YaST2 finds nothing to install. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 URL: http://nickle.org/release/nickle-2.70-1.src.rpm OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: jsrain(a)suse.com CC: hrvoje.senjan(a)gmail.com Depends on: 684610 Found By: Community User Blocker: No +++ This bug was initially created as a clone of Bug #684610 +++ User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 When I open nickle-2.70-1.src.rpm, YaST2 does not install anything. Reproducible: Always Steps to Reproduce: 1. Tell Dolphin to open nickle-2.70-1.src.rpm [1]. Actual Results: 1. YaST2 finds nothing to be installed. Expected Results: 1. Let YaST2 install the source package. ___ [1] <URL: http://nickle.org/release/nickle-2.70-1.src.rpm > -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 1022687] New: libqt5-qtimageformats no longer compiled agains libjasper dependency
by bugzilla_noreply＠novell.com 01 Jan '20

01 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1022687 Bug ID: 1022687 Summary: libqt5-qtimageformats no longer compiled agains libjasper dependency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: christoph(a)maxiom.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using KDE:Qt58 repository: Trying to view JPEG-2000 images with Qt5/KF5 applications (Dolphin, Gwenview, etc.) fails, because the QtImageFormats plugins are not compiled with support for jasper library. As far as I understand, jasper was long unmaintained, but recently got several handful of security issues applied, so jasper support can be safely enabled again. JPEG-2000 test image: http://www.fnordware.com/j2k/relax.jp2 Related: https://bugs.kde.org/show_bug.cgi?id=375641 Reporting to KDE maintainers, because I guess they are responsible for Qt packages; if not, please reassign. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 712025] New: openssh helpers wrongly uses %_libdir
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=712025 https://bugzilla.novell.com/show_bug.cgi?id=712025#c0 Summary: openssh helpers wrongly uses %_libdir Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- I had a openSUSE 11.4 i586 installation on one machine, and as I was upgrading its hardware to a 64-bit CPU, I did a x86_64 reinstall, and copied over the configs from the previous install. Among that was /etc/ssh/sshd_config. After this, sftp was no longer usable ("Connection closed by host"), hinting towards the helper not being executable. sshd_config, having been inherited from a i586 environment, contained: Subsystem sftp /usr/lib/ssh/sftp-server However, the sftp helper was installed in /usr/lib64/ssh (%_libdir/ssh), which I consider the wrong place, because the helper is bitness-independent and thus should go to %_libexecdir/ssh instead. The problem persists by looking at the current /network/openssh/openssh.spec. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 536564] New: Packages creating user accounts do not select UID
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=536564 Summary: Packages creating user accounts do not select UID Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Some packages, such as openssh, do explicitly specify a UID/GID when creating its users/groups: /usr/sbin/groupadd -g 65 -o -r sshd 2>/dev/null || :; On the other hand, the hal package does not: /usr/sbin/groupadd -r haldaemon 2>/dev/null || : So, which is correct? Should not hal also use a fixed ID? There are many packages belonging to the latter category. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 518238] New: openSSH chroot security settings faulty
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=518238 Summary: openSSH chroot security settings faulty Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marcus(a)swedcore.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Whenever i tried to setup a chroot environment with OpenSSH the security settings for the user folder must be root or OpenSSH doesn't work, the only solution for now is to either create subfolders in the users chroot folder where the user can have write permissions or land them one step up in the hierarchy and thus making them see other chroot folder which is not good. I followed this Wiki page to the letter: http://en.opensuse.org/Openssh#SFTP_chroot_with_ChrootDirectory I have Swedish community users trying to set this up to with same result as me. This thread takes up the same issue: http://marc.info/?l=openssh-unix-dev&m=122640731518850&w=2 But the solution mentioned there is not acceptable because as it stats on the Wiki you make one folder the chroot folder and then mapping the users home folder relative to the chroot folder, in this scenario the users should get write permissions to his own folder, but that is not possible, thus breaking the functionality intended. So the question is, is this a bug or is it designed to act like this? Reproducible: Always Steps to Reproduce: Done accordingly to this wiki entry: http://en.opensuse.org/OpenSSH Actual Results: Gets a read only home folder root Expected Results: Getting a writable home folder, where they can create on folder and upload files directly to the root of their home folder. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 788344] New: Improving go-doc package wanted
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=788344 https://bugzilla.novell.com/show_bug.cgi?id=788344#c0 Summary: Improving go-doc package wanted Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ke(a)suse.com QAContact: qa-bugs(a)suse.de CC: graham(a)andtech.eu, speilicke(a)suse.com Found By: Development Blocker: --- The go-doc package is rather bewildered. Many links do not work. Many files are included that do not make sense in a doc package (e.g., Makefile or the emacs mode (go-mode.el) that comes with a different package). Les is more. Please ship only those parts that are nicely interlinked via HTML cross-references. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4