March 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1120754] [META] GCC 9 package failures
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1120754 Bug 1120754 depends on bug 1121395, which changed state. Bug 1121395 Summary: GCC 9: ceph build fails http://bugzilla.suse.com/show_bug.cgi?id=1121395 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121395] GCC 9: ceph build fails
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1121395 http://bugzilla.suse.com/show_bug.cgi?id=1121395#c9 Nathan Cutler <ncutler(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #9 from Nathan Cutler <ncutler(a)suse.com> --- Local build passed. Confirmed fixed in the next Factory SR. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1126901] New: gnome-terminal-server: SIGSEGV in gdk_x11_device_manager_xi2_translate_event
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1126901 Bug ID: 1126901 Summary: gnome-terminal-server: SIGSEGV in gdk_x11_device_manager_xi2_translate_event Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: pmonrealgonzalez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In gnome-terminal, system freezes for some seconds and then segfaults, reported upstream and not yet fixed: https://gitlab.gnome.org/GNOME/gtk/issues/855 (gdb) bt #0 0x00007f99b151a67a in gdk_x11_device_manager_xi2_translate_event (xevent=<optimized out>, event=<optimized out>, display=<optimized out>, translator=<optimized out>) at gdkdevicemanager-xi2.c:1794 #1 0x00007f99b151a67a in gdk_x11_device_manager_xi2_translate_event (translator=<optimized out>, display=<optimized out>, event=<optimized out>, xevent=<optimized out>) at gdkdevicemanager-xi2.c:1478 #2 0x00007f99b15248e8 in _gdk_x11_event_translator_translate (translator=translator@entry=0x560486365000, display=0x5604863410e0 [GdkX11Display], xevent=xevent@entry=0x7ffc65a6c330) at gdkeventtranslator.c:51 #3 0x00007f99b15244c1 in gdk_event_source_translate_event (xevent=0x7ffc65a6c330, event_source=0x56048634c0b0) at gdkeventsource.c:230 #4 0x00007f99b15244c1 in _gdk_x11_display_queue_events (display=0x5604863410e0 [GdkX11Display]) at gdkeventsource.c:341 #5 0x00007f99b14ee950 in gdk_display_get_event (display=display@entry=0x5604863410e0 [GdkX11Display]) at gdkdisplay.c:438 #6 0x00007f99b1524072 in gdk_event_source_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at gdkeventsource.c:363 #7 0x00007f99b1163e2e in g_main_dispatch (context=0x56048637eb10) at gmain.c:3182 #8 0x00007f99b1163e2e in g_main_context_dispatch (context=context@entry=0x56048637eb10) at gmain.c:3847 #9 0x00007f99b11640c8 in g_main_context_iterate (context=context@entry=0x56048637eb10, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3920 #10 0x00007f99b116415c in g_main_context_iteration (context=context@entry=0x56048637eb10, may_block=may_block@entry=1) at gmain.c:3981 #11 0x00007f99b133142d in g_application_run (application=0x56048634e420 [TerminalApp], argc=<optimized out>, argv=0x0) at gapplication.c:2470 #12 0x0000560484ee956c in main (argc=<optimized out>, argv=<optimized out>) at server.c:187 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1123342] YaST "boot loader" module error (Unknown device, exit code 4)
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1123342 http://bugzilla.suse.com/show_bug.cgi?id=1123342#c4 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS Assignee|yast-internal(a)suse.de |aschnell(a)suse.com --- Comment #4 from Arvin Schnell <aschnell(a)suse.com> --- My analysis so far shows that the problem happens when there 1. are LUKS devices on some available devices, 2. entries in /etc/crypttab for unavailable devices exist, 3. these entries are before the entries of the available devices and 4. the entries in /etc/crypttab start with /dev (so do not use UUID= as YaST writes per default (at least since a year)). So as a workaround you could try to use UUID= in /etc/crypttab. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123350] New: Newest image of Tumbleweed, Snapshot20190121, on Raspberry Pi 2 does not boot
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1123350 Bug ID: 1123350 Summary: Newest image of Tumbleweed, Snapshot20190121, on Raspberry Pi 2 does not boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After installing image openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2019.01.08-Snapshot20190121.raw.xz the system does not boot properly. The output on the console is: [ 0.356882] Initramfs unpacking failed: junk in compressed archive [ 0.487556] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 0.495835] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.20.0-1-lpae #1 openSUSE Tumbleweed (unreleased) [ 0.505224] Hardware name: BCM2835 [ 0.508660] [<c04469a0>] (unwind_backtrace) from [<c043f270>] (show_stack+0x1c/0x28) [ 0.516411] [<c043f270>] (show_stack) from [<c0dfdad4>] (dump_stack+0xac/ 0xd8) [ 0.523641] [<c0dfdad4>] (dump_stack) from [<c0482508>] (panic+0x108/0x29c) [ 0.530612] [<c0482508>] (panic) from [<c1601790>] (mount_block_root+0x260/0x30c) [ 0.538099] [<c1601790>] (mount_block_root) from [<c1601a24>] (prepare_namespace+0x158/0x1a0) [ 0.546628] [<c1601a24>] (prepare_namespace) from [<c1601328>] (kernel_init_freeable+0x3f8/0x410) [ 0.555506] [<c1601328>] (kernel_init_freeable) from [<c0e15e30>] (kernel_init+0x10/0x11c) [ 0.563775] [<c0e15e30>] (kernel_init) from [<c04011cc>] (ret_from_fork+0x14/0x28) [ 0.571343] Exception stack(0xef12bfb0 to 0xef12bff8) Also a "zypper dup --no-r" from a previous version to this version gives a system that does not boot anymore. Did not think about booting a previous kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1127605] Can not install packages via 1-click install in appliance if dummy-release is installed
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127605 http://bugzilla.suse.com/show_bug.cgi?id=1127605#c1 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schubi(a)suse.com --- Comment #1 from Stefan Schubert <schubi(a)suse.com> --- Hm, I cannot find any hint in the log files regarding your problem. Are you sure that you have sent the correct one ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127714] [Build 20190301] yast2_apparmor does not display mode column when profile name is too long
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127714 http://bugzilla.suse.com/show_bug.cgi?id=1127714#c2 Joaquín Rivera <jeriveramoya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jeriveramoya@suse | |.com) | --- Comment #2 from Joaquín Rivera <jeriveramoya(a)suse.com> --- Sure, this is the build from three days ago: https://openqa.opensuse.org/tests/866126#step/yast2_apparmor/9 showing properly Mode and PID column, now with that long name in the profile we need to scroll to the right to see those columns. For such a long names we would expect some elipsis (...) or some reasonable column size that allow user to see the whole thing in one shot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114779] VUL-0: CVE-2018-4013: live555: critical remote code execution vulnerability in the LIVE555 media streaming library
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1114779 http://bugzilla.suse.com/show_bug.cgi?id=1114779#c12 --- Comment #12 from George Anchev <studio(a)anchev.net> --- > openSUSE-SU-2019:0058-1: An update that fixes two vulnerabilities is now available. > [...] > openSUSE Leap 15.0 (src): live555-2018.12.14-lp150.2.3.1 Could someone please clarify what this means? On my system 'zypper se -s live555' shows version 2017.10.28-lp150.1.9 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127618] midori always crashes
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127618 http://bugzilla.suse.com/show_bug.cgi?id=1127618#c1 --- Comment #1 from Maurizio Galli <maurizio.galli(a)gmail.com> --- Are you on midori 0.5.11 from Leap 15? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127714] [Build 20190301] yast2_apparmor does not display mode column when profile name is too long
by bugzilla_noreply＠novell.com 04 Mar '19

04 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127714 http://bugzilla.suse.com/show_bug.cgi?id=1127714#c1 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeriveramoya(a)suse.com, | |schubi(a)suse.com Flags| |needinfo?(jeriveramoya@suse | |.com) --- Comment #1 from Stefan Schubert <schubi(a)suse.com> --- Could you please be a little bit verbose what is exactly wrong and what is expected ? I cannot see the issue here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0