October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1130723] Wrong DPI when using suse-prime in nvidia mode
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1130723 http://bugzilla.suse.com/show_bug.cgi?id=1130723#c17 --- Comment #17 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1130723) was mentioned in https://build.opensuse.org/request/show/734774 Factory / suse-prime -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1152720] ghostscript 9.27 breaks printing
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1152720 http://bugzilla.suse.com/show_bug.cgi?id=1152720#c15 Jean Delvare <jdelvare(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |maint-coord(a)suse.de Flags| |needinfo?(maint-coord@suse. | |de) --- Comment #15 from Jean Delvare <jdelvare(a)suse.com> --- Given that both packages are shared with SLE products, I guess the SUSE maintenance team should take care of that. Maintenance team, we'd need a fast maintenance update of qpdf and cups-filters in SLE 15, SLE 15 SP1 as well as SLE 12 SP4, to fix the regression caused by the recent maintenance update of ghostscript. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1149792] openssl 1.1.1c causes build failures in other packages
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1149792 http://bugzilla.suse.com/show_bug.cgi?id=1149792#c24 --- Comment #24 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1149792) was mentioned in https://build.opensuse.org/request/show/734761 Factory / nodejs8 https://build.opensuse.org/request/show/734762 Factory / nodejs10 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1139915] Inconsistent names of Tumbleweed image for Raspberry Pi 1B in repository
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1139915 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tchatzimichos(a)suse.com |bnc-team-screening(a)forge.pr | |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1139915] Inconsistent names of Tumbleweed image for Raspberry Pi 1B in repository
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1139915 http://bugzilla.suse.com/show_bug.cgi?id=1139915#c5 --- Comment #5 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- For the missing '.xz' extension in '.sha256' file, it is a kiwi problem reported here: https://github.com/OSInside/kiwi/issues/1223 For the other naming problem, when pushing JeOS images from :ARM project to :ARM:ToTest project, TTM passes 'setrelease=Snapshot...' to the OBS release command and then OBS does its magic to rename files. So, OBS would also need to do some updates inside the '.sha256' file, which is not trivial, since the file is signed. Reported to OBS: https://github.com/openSUSE/open-build-service/issues/8502 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1152036] New: Fatal iwlwifi errors with kernel 5.3
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1152036 Bug ID: 1152036 Summary: Fatal iwlwifi errors with kernel 5.3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 819513 --> http://bugzilla.suse.com/attachment.cgi?id=819513&action=edit journalctl of various boots I'm having severe issues with iwlwifi and kernel 5.3. Using 5.3.0-rc5-2.g126cef1-default or 5.3.1-1.gf187578-default: - Sometimes the wlan interface does not appear at all - Sometimes it appears but is down and scanning fails - On "lucky" boots, it appears to work normally but there is a constant stream of errors in dmesg Using older firmware files didn't help. Using 5.2.0-rc5-3.ga562f5a-default with newer or older firmware files works flawlessly. The attached file contains journalctl snippets for the various combinations I tried. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1140256] VUL-0: CVE-2019-13178: calamares: race condition in modules/luksbootkeyfile/main.py
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.novell.com/show_bug.cgi?id=1140256 http://bugzilla.novell.com/show_bug.cgi?id=1140256#c1 --- Comment #1 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- I am testing Calamares 3.2.14. However seems that Calamares 3.2.2 introduced new bug that prevents us to update Calamares: https://github.com/calamares/calamares/issues/1253 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1152875] New: typelib-1_0-Gtk-3_0 stopped working after glib update
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1152875 Bug ID: 1152875 Summary: typelib-1_0-Gtk-3_0 stopped working after glib update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm packaging solaar (to configure Logitech devices) which is using python3 and the gtk bindings. The program stopped working with the following error when importing the ui: -> import solaar.ui as ui (Pdb) n TypeError: GObject.__init__() takes exactly 0 arguments (4 given) Looking at the solaar.ui init it just does: from gi.repository import GLib, Gtk which seems to fail. I guess that the glib bindings have been updated but not typelib-1_0-Gtk-3_0. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1149619] New: gdb libipt update v2.0 -> v2.0.1
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1149619 Bug ID: 1149619 Summary: gdb libipt update v2.0 -> v2.0.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libipt v2.0.1 has been released: https://github.com/intel/libipt/tree/v2.0.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1124446] New: PHP 7.3 preg_match(): JIT compilation failed: no more memory (need pcre.jit=0 by default in php.ini)
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124446 Bug ID: 1124446 Summary: PHP 7.3 preg_match(): JIT compilation failed: no more memory (need pcre.jit=0 by default in php.ini) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ilya(a)ilya.pp.ua QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://bugs.php.net/bug.php?id=77260 In PHP 7.3 using pcre2 and using by default JIT compilation (pcre.jit=1) This leads to errors like: Warning in ./libraries/classes/Config.php#201 preg_match(): JIT compilation failed: no more memory For everything that uses preg _ * () I get this error on the login screen in phpMyAdmin 4.8.5, while I have 128MB RAM allocated for PHP! Until this is dealt with in the upstream. I suggest set in php.ini pcre.jit=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2