October 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1095817] New: containers packages fail randomly due to %check
by bugzilla_noreply＠novell.com 30 Apr '21

30 Apr '21

http://bugzilla.suse.com/show_bug.cgi?id=1095817 Bug ID: 1095817 Summary: containers packages fail randomly due to %check Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We've had tests in the %check section for a long time, but to be honest they've been nothing but a source of trouble. We end up having to run smoke tests anyway, and I'm not aware of a single time %check has actually caught an issue (and it has also caused many issues). So we have to remove it from basically all of our container packages (docker/containerd/runc/docker-libnetwork and the corresponding Kubic packages). -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1051429] New: docker and runc failed to build with kernel 4.12 on ppc64le
by bugzilla_noreply＠novell.com 30 Apr '21

30 Apr '21

http://bugzilla.suse.com/show_bug.cgi?id=1051429 Bug ID: 1051429 Summary: docker and runc failed to build with kernel 4.12 on ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de CC: asarai(a)suse.com, jmassaguerpla(a)suse.com, jslaby(a)suse.com, normand(a)linux.vnet.ibm.com Found By: --- Blocker: --- Currently we see docker[1] and runc[2] failed to build with kernel 4.12[3] in the staging project, and it does happened only on ppc64le build. [1] https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… [2] https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… [3] https://build.opensuse.org/request/show/512894 -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1102261] New: "zypper patch --with update" should implicitly assume "--with-optional" and not tell me that I need to do something more to install optional patches, since it will install them anyway
by bugzilla_noreply＠novell.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1102261 Bug ID: 1102261 Summary: "zypper patch --with update" should implicitly assume "--with-optional" and not tell me that I need to do something more to install optional patches, since it will install them anyway Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm reporting this in severity "enhancement" because it is an RFE, not a bug. The following is from my latest run of "zypper patch --with-update": > Loading repository data... > Reading installed packages... > Patch '8464-1' is optional. Use 'zypper in patch:8464' to install it, or > '--with-optional' to include all optional patches. > Resolving package dependencies... > > The following 2 NEW packages are going to be installed: > ffmpeg-3 libzimg2 > > The following package is going to be REMOVED: > ffmpeg > > The following 14 packages are going to be upgraded: > libavcodec57 libavcodec58 libavdevice57 libavfilter6 libavformat57 libavformat58 > libavresample3 libavutil55 libavutil56 libpostproc54 libsodium23 libswresample2 > libswresample3 libswscale4 > > 14 packages to upgrade, 2 new, 1 to remove. > Overall download size: 8.5 MiB. Already cached: 0 B. After the operation, additional > 997.9 KiB will be used. > Continue? [y/n/...? shows all options] (y): Of course, these 1 removed, 2 new and 14 updated packages are from patch 8464, and after letting this update run its course, "zypper lp -a" shows patch 8464 as "installed". So "--with-update" should not believe that it won't install optional patches: ideally, it should have said instead: "The following patch is going to be installed: 8464". -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 986593] New: security/john: Tools in run/ not packaged and undefined maintainer of john
by bugzilla_noreply＠novell.com 25 Apr '21

25 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=986593 Bug ID: 986593 Summary: security/john: Tools in run/ not packaged and undefined maintainer of john Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: sebix+novell.com(a)sebix.at QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: meissner(a)suse.com Found By: --- Blocker: --- The tools which are in run/ in the jumbo-repository[2] are not packaged. The tools like pdf2john.py (and other *2john programs) are very helpful (or essential) to work with john. Beside packing them into the john-package, another possibility would be to create a john-tools package. Which variant do you prefer? (I can help with packaging in July) And: The mentioned maintainer-email on OBS (solar(a)false.com) is not reachable (no MX or A record for that domain. And: By clicking "report bug" on https://build.opensuse.org/package/show/security/john "lars.vogdt(a)microfocus.dmm" was assigned, but bugzilla did not accept this input. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1028399] New: zypper could use a function to show package version release notes, like `dnf updateinfo info`
by bugzilla_noreply＠novell.com 23 Apr '21

23 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1028399 Bug ID: 1028399 Summary: zypper could use a function to show package version release notes, like `dnf updateinfo info` Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: pointedstick(a)zoho.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- I'm using OpenSUSE Tumbleweed. Some updated packages are available, and I want to read their release notes so I can find out what's changing. On Fedora, I would do the following: `dnf updateinfo --refresh info <package name, or empty to see all>` zypper doesn't seem to have a similar feature, which is a shame! It should. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1108163] New: Firefox does not notice connection status of NetworkManager
by bugzilla_noreply＠novell.com 23 Apr '21

23 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1108163 Bug ID: 1108163 Summary: Firefox does not notice connection status of NetworkManager Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If Firefox is started before NetworkManager connects to a network, Firefox thinks the system is offline. One needs to close Firefox and open it again. Chromium on the other hand detects the system connection status. I guess it talks to NetworkManager. Could Firefox do the same? -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1023335] New: X11:Deepin: Deepin Desktop Environment for X11:Deepin?
by bugzilla_noreply＠novell.com 20 Apr '21

20 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1023335 Bug ID: 1023335 Summary: X11:Deepin: Deepin Desktop Environment for X11:Deepin? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: i(a)marguerite.su Reporter: sb56637(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Hello X11:Deepin maintainers, Would it be possible to package the latest version of the Deepin Desktop Environment for openSUSE Leap 42.2 and Tumbleweed? DDE appears to be quite portable now, and it is working extremely well on Arch and Manjaro. There are also several sources of RPM spec files for Fedora that should be relatively easy to compile for openSUSE: https://github.com/FZUG/repo/tree/master/rpms/deepin_project https://github.com/cz-guardian/fedora-deepin/ https://copr.fedorainfracloud.org/coprs/mosquito/deepin/ https://copr.fedorainfracloud.org/coprs/jstepanek/deepin/ I release SuseStudio images of openSUSE Leap and Tumbleweed, and I would love to offer a Deepin version as well. Thanks a lot, Sam -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1096241] New: [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL
by bugzilla_noreply＠novell.com 19 Apr '21

19 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1096241 Bug ID: 1096241 Summary: [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL 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: slindomansilla(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 772682 --> http://bugzilla.opensuse.org/attachment.cgi?id=772682&action=edit shutdown-log-timed-out.txt Similar issue was found a long time ago on ArchLinux and Redhat: - https://bugs.archlinux.org/task/52249 - https://bugzilla.redhat.com/show_bug.cgi?id=1152185 My questions here are: - Why do we need this process running on liveCD? - If we don't need it, can we remove it from the liveCD? - If not, how can we avoid that users get that problem? System hung when shutting down (notice 2154.900545 -> 2244.901945): [ 2154.897657] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 2154.900537] systemd-journald[6847]: Received SIGTERM from PID 1 (systemd-shutdow). [ 2154.900545] systemd-journald[6847]: systemd-journald stopped as pid 6847 [ 2244.901945] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 2244.907601] systemd-shutdown[1]: Sending SIGKILL to PID 731 (lvmetad). System not hung when shutting down (notice 2012.262209 -> 2012.314146): [ 2012.259513] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 2012.262200] systemd-journald[6792]: Received SIGTERM from PID 1 (systemd-shutdow). [ 2012.262209] systemd-journald[6792]: systemd-journald stopped as pid 6792 [ 2012.314146] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 2012.317239] systemd-shutdown[1]: Unmounting file systems. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 927268] New: clang link fails with undefined reference to `__stack_chk_guard'
by bugzilla_noreply＠novell.com 18 Apr '21

18 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=927268 Bug ID: 927268 Summary: clang link fails with undefined reference to `__stack_chk_guard' Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: PowerPC-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dap(a)open.by QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 631137 --> http://bugzilla.opensuse.org/attachment.cgi?id=631137&action=edit Full build log. Upstream report: https://llvm.org/bugs/show_bug.cgi?id=22248 My build log error: [ 35s] CMakeFiles/huffar.dir/compress.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] CMakeFiles/huffar.dir/extract.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] clang-3.5: error: linker command failed with exit code 1 (use -v to see invocation) [ 35s] CMakeFiles/huffar.dir/build.make:163: recipe for target 'huffar' failed [ 35s] make[2]: *** [huffar] Error 1 Check attachment for full log. #opensuse-ppc(a)irc.freenode.net: k0da: dark_ss, it seems you've hit an LLVM bug. It adds extra symbol. k0da: dark_ss, you can open an opensuse bug though for that issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1095700] New: setterm reports "cannot (un)set powersave mode: Inappropriate ioctl for device"
by bugzilla_noreply＠novell.com 16 Apr '21

16 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1095700 Bug ID: 1095700 Summary: setterm reports "cannot (un)set powersave mode: Inappropriate ioctl for device" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to re-establish screen blanking and power saving for virtual consoles on machines without X, I am trying to use "setterm -powersave on". This works on some machines, but not on others. I have added the following drop-in: /etc/systemd/system/getty\@.service.d/powersave.conf [Service] Environment=TERM=linux ExecStartPost=-/usr/bin/setterm -powersave on >/dev/%I ExecStartPost=/usr/bin/setterm -blank 2 -powerdown 5 >/dev/%I I have split the setterm into two, because the 'powersave on' keeps fasiling and reporting "cannot (un)set powersave mode: Inappropriate ioctl for device". If I run it when logged into a console, it does not complain, but it also doesn't work. On older openSUSE, e.g. 12.3, it works, but I'm wondering if it might be a graphics driver issue? Maybe also refer to bug#1094452 which prompted me to look for a solution. -- You are receiving this mail because: You are on the CC list for the bug.

2 18