February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1022427] mpv lacks bash-completion
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022427 http://bugzilla.suse.com/show_bug.cgi?id=1022427#c6 --- Comment #6 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1022427) was mentioned in https://build.opensuse.org/request/show/454513 42.2 / mpv -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1021470] New: Cannot build package with alternative providers of dependency
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1021470 Bug ID: 1021470 Summary: Cannot build package with alternative providers of dependency Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- <td class="status_unresolvable buildstatus nowrap"><a title="have choice for java-devel = 1.8.0: java-1_8_0-ibm-devel java-1_8_0-openjdk-devel" id="id-Arduino_SLE_12_SP2_ppc64le" class="unresolvable" href="#">unresolvable</a></td> What is the point of the java-devel provide if you cannot use it? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1022053] New: mozilla/mozilla-nss: libfreebl3 3.28.1 and libsoftokn3 3.28.1 cause the JVM to crash when using sun.security.ec.ECKeyPairGenerator
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1022053 Bug ID: 1022053 Summary: mozilla/mozilla-nss: libfreebl3 3.28.1 and libsoftokn3 3.28.1 cause the JVM to crash when using sun.security.ec.ECKeyPairGenerator Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: wolfgang(a)rosenauer.org Reporter: tom.warnke(a)kolabnow.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 711741 --> http://bugzilla.opensuse.org/attachment.cgi?id=711741&action=edit JVM crash log After updating libfreebl3 and libsoftokn3 from 3.26.2 to 3.28.1 from the OBS mozilla project, Maven can not download artifacts anymore. The java process crashes with a SIGSEGV. From the crash log, I assembled a minimal example. The following Java program can be executed with libfreebl3 and libsoftokn3 3.26.2, but crashes the JVM with 3.28.1: import sun.security.ec.ECKeyPairGenerator; public class Main { public static void main(String[] args) { ECKeyPairGenerator keyPairGenerator = new ECKeyPairGenerator(); keyPairGenerator.generateKeyPair(); } } I also attached the crash log from the minimal example. If this is not the right place to report this bug, please direct me to a better one. In any case, these two packages should not enter the 42.2 main repositories yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1012504] Under "Repository Management", when adding a local ISO image, making any change prior to exiting YaST produces an error
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1012504 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:planned:update |ibs:running:4136:important |ibs:running:4136:important |ibs:running:4137:important |ibs:running:4137:important |ibs:running:3352:important |ibs:running:3352:important | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 937652] New: nbd shutdown crash
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=937652 Bug ID: 937652 Summary: nbd shutdown crash Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: cbosdonnat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 640583 --> http://bugzilla.suse.com/attachment.cgi?id=640583&action=edit test script triggering the problem When shutting down a libvirt-lxc container with an NBD mounts, we sometimes get a crash. Steps to reproduce: * Get libvirt, and virt-sandbox from the Virtualization project * Install guestfs-tools * systemctl start libvirtd * Run the attached test script. The QEMU tests can be commented in it as those aren't the ones triggering the bug. Note that the crash may not happen at each run of the script, don't hesitate to run it several times if needed. What happens: * the 'sandbox' container isn't correctly terminated due to the qemu-nbd segfaulting. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 908499] New: systemd: Many stale rfkill services accumulates after suspend/resume cycles
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908499 Bug ID: 908499 Summary: systemd: Many stale rfkill services accumulates after suspend/resume cycles Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- See http://lists.freedesktop.org/archives/systemd-devel/2014-November/025321.ht… for details. For systems where rfkill devices are connected via USB they get new names after each suspend/resume causing large number of stale services to be accumulated (and defeating the purpose of rfkill.service to store device state). This apparently was fixed in upstream 4844262f25a3ff6bd23de05a0a6f84a8e2983d74 + 812bd1e6ab4c463507557f2bdbb8875fedd92ade. Please consider including it in systemd update (fix is very much self contained and should be non-intrusive). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1020283] No password prompt for LUKS-cryptsetup shown after upgrade of systemd
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1020283 http://bugzilla.opensuse.org/show_bug.cgi?id=1020283#c34 --- Comment #34 from Thiago Macieira <thiago(a)kde.org> --- (In reply to Martin Wilck from comment #32) > When plymouth switches to text mode (an indication that some critical error > message was seen), the prompt may be hidden between other system output. I > have this very often. You can normally simply type the password (you should > see a "*" for every key stroke on the text console). I specifically tested this and it did not work. I typed my password blindly and pressed Enter, and nothing happened. In fact, Ctrl+Alt+Del did not work either, and the Caps Lock LED did not come on, as reported on comment #25. Alt+SysRq,B was required to reboot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1020283] No password prompt for LUKS-cryptsetup shown after upgrade of systemd
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1020283 http://bugzilla.opensuse.org/show_bug.cgi?id=1020283#c33 --- Comment #33 from Thiago Macieira <thiago(a)kde.org> --- (In reply to Ju_Ping Chan from comment #31) > I tried Robby's suggestion, and managed to boot into KDE by switching to > tty7. Didn't think it would be that straightforward. Anyway, since I added > the boot parameter "debug printk.devkmsg=on". Indeed, about every third login required a text-mode password prompt, not the graphical one. It was pretty much random which one I'd get, with about only a 33% success rate in getting the graphical one at all. That has been happening for at least three years, since I started using OpenSUSE Tumbleweed. By "text mode password", it was still a full-screen text entry, with the prompt more or less centred on screen. That's not how I had to boot the last two times, though, to recover from this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1022758] kernel-source master does not boot with KASAN enabled
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022758 http://bugzilla.suse.com/show_bug.cgi?id=1022758#c5 --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- And the root cause is linear table search which follows an unsuccessful binary one. It seems to be superfluous when the system is started (dwarf_setup called). Killing it temporarily gives: real 0m0.018s user 0m0.001s sys 0m0.017s from: real 0m1.808s user 0m0.001s sys 0m1.807s in 1000 iterations. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017610] During Initialize software manager - YAST not able to create repository from external USB diskdrive
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1017610 http://bugzilla.suse.com/show_bug.cgi?id=1017610#c20 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #20 from Ladislav Slezák <lslezak(a)suse.com> --- Oh, zeroes in "products" file... BTW if you boot the DVD there is "More ..." -> "Check Installation Media" menu item which checks the DVD medium checksum. To check the ISO medium before burning it you can run "checkmedia image.iso" command. I'm closing the bug as this is either a HW or medium problem, the "products" content in the ISO ("/ openSUSE 42.2-0") is correct. -- You are receiving this mail because: You are on the CC list for the bug.

1 0