February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1123798] itstool / python3-libxml2-python randomly segfaults
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123798 http://bugzilla.suse.com/show_bug.cgi?id=1123798#c2 --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- It is bug 1064286 and it is still unfixed: https://gitlab.gnome.org/GNOME/libxml2/issues/12 with possibly related https://bugzilla.gnome.org/show_bug.cgi?id=789714 The "resolved upstream" just meant that we did not want to spend time on it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1106673] LUKS keyboard layout falls back to US instead of DE since last dracut update
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1106673 http://bugzilla.suse.com/show_bug.cgi?id=1106673#c27 --- Comment #27 from Michael Hirmke <opensuse(a)mike.franken.de> --- Created attachment 796375 --> http://bugzilla.suse.com/attachment.cgi?id=796375&action=edit vconsole messages -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1106673] LUKS keyboard layout falls back to US instead of DE since last dracut update
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1106673 http://bugzilla.suse.com/show_bug.cgi?id=1106673#c26 --- Comment #26 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Thomas Blume from comment #25) > (In reply to Aender Boy from comment #20) > > Created attachment 796325 [details] > > sudo journalctl -axb > journalctl.out > > The log shows: > > --> > Feb 07 20:23:23 aendersu systemd[149]: systemd-vconsole-setup.service: > Executing: /usr/lib/systemd/systemd-vconsole-setup > > Feb 07 20:23:23 aendersu systemd-vconsole-setup[149]: cannot open include > file compose.latin1 > Feb 07 20:23:23 aendersu systemd-vconsole-setup[149]: syntax error, > unexpected ERROR > Feb 07 20:23:23 aendersu systemd[151]: systemd-modules-load.service: > Executing: /usr/lib/systemd/systemd-modules-load > Feb 07 20:23:23 aendersu systemd-vconsole-setup[149]: Sysfs UTF-8 flag > enabled > --< > > That looks like the bug addressed in upstream commit: > > https://github.com/dracutdevs/dracut/commit/ > 44f2fe5170b3f5f161cfee04e62b713f2e47237d > > Are the other reporters seeing the same error? No. The only warning I get from vconsole is: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented. I attached all messages regarding vconsole. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1100496] neovim should depend on specific version of libtermkey1
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1100496 http://bugzilla.suse.com/show_bug.cgi?id=1100496#c6 --- Comment #6 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2019:0151-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1094627,1098800,1100496 CVE References: Sources used: openSUSE Leap 15.0 (src): libtermkey-0.20-lp150.2.3.1, lua51-bit32-5.3.0-lp150.2.1, neovim-0.3.1-lp150.2.3.1, python-neovim-0.3.1-lp150.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1094627] neovim mouse support is broken due to incompatibility with libtermkey library
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1094627 http://bugzilla.suse.com/show_bug.cgi?id=1094627#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2019:0151-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1094627,1098800,1100496 CVE References: Sources used: openSUSE Leap 15.0 (src): libtermkey-0.20-lp150.2.3.1, lua51-bit32-5.3.0-lp150.2.1, neovim-0.3.1-lp150.2.3.1, python-neovim-0.3.1-lp150.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 993025] do not show the packages that will not get updated in quiet mode
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=993025 http://bugzilla.novell.com/show_bug.cgi?id=993025#c2 Benjamin Zeller <bzeller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #2 from Benjamin Zeller <bzeller(a)suse.com> --- fixed in zypper >= 1.14.25 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018736] New: random freezes and filesystem errors
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1018736 Bug ID: 1018736 Summary: random freezes and filesystem errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: diamantis.karagkiaouris.dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 709003 --> http://bugzilla.suse.com/attachment.cgi?id=709003&action=edit Journalctl log I face some random freezes which i could not understand the cause of them. Sometimes it happens when i zypper dup, i searching in google or watching videos. I could not investigate the issue. My thought from the attached log of journalclt is that somehow my partitions become non writable. I am on a ssd with ext4 partitions (home/ root). Did anyone encounter something like this? -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1059169] cannot boot on degraded raid - dracut exits on emergency shell (leap 42.3 after update)
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1059169 http://bugzilla.suse.com/show_bug.cgi?id=1059169#c5 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jjletho67-esus(a)yahoo.it, | |thomas.blume(a)suse.com Flags| |needinfo?(jjletho67-esus@ya | |hoo.it) --- Comment #5 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Marco M. from comment #3) > Created attachment 745020 [details] > file /etc/fstab > > /etc/fstab on the system where I experienced and reproduced the issue. There seems to be a problem with the softraid device naming. The rdsosreport shows 2 softraid devices, md0 and md2: --> [ 33.259180] linux-owe6 mdadm[784]: mdadm: started array /dev/md2 [ 33.386220] linux-owe6 kernel: md2: detected capacity change from 0 to 16104947712 [ 33.261113] linux-owe6 systemd[1]: Started Activate md array even though degraded. [ 33.263144] linux-owe6 mdadm[785]: mdadm: started array /dev/md0 [ 33.390096] linux-owe6 kernel: md0: detected capacity change from 0 to 1077870592 [ 33.266270] linux-owe6 systemd[1]: Started Activate md array even though degraded. [ 33.511023] linux-owe6 systemd[1]: Stopped Timer to wait for more drives before activating degraded array.. [...] --< but the boot parameters show a resume device on /dev/md1: --> BOOT_IMAGE=/vmlinuz-4.4.87-25-default root=/dev/mapper/systemVG-rootLV ro resume=/dev/md1 showopts --< Since dracut cannot find md1, the boot fails. There is no error message referring to md1, so it seems that this device name is not present in the mdadm.conf file of the initrd or the devices where md1 resides on are not present. Can you find the devicename md1 in /etc/mdadm.conf of your running system? If so, what are the device names from which md1 should be assembled? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1119355] u-boot from Leap:15.1 needs to be updated
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1119355 http://bugzilla.suse.com/show_bug.cgi?id=1119355#c4 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #4 from Matthias Brugger <mbrugger(a)suse.com> --- u-boot updated to new version. Should be fixed by that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124471] New: update will not install
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124471 Bug ID: 1124471 Summary: update will not install Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gvogts(a)onlinehome.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- i am trying to install the latest software update and take the following error as seen in the screen shots i took. it has to do with python three and will nt install. -- You are receiving this mail because: You are on the CC list for the bug.

1 4