February 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1158667] Qt5 Combobox does not open (or open in wrong location) in multi-monitor setup
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1158667 Maintenance Robot <maint-coord+maintenance_robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:13634:important | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1148080] New: Running update-desktop-database causes some errors related to font category
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1148080 Bug ID: 1148080 Summary: Running update-desktop-database causes some errors related to font category Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: smar(a)smar.fi QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- Hi, When running command update-desktop-database, I get two errors: Error in file "/usr/share/applications/org.kde.kfontview.desktop": "font/otf" is an invalid MIME type ("font" is an unregistered media type) Error in file "/usr/share/applications/org.kde.kfontview.desktop": "font/ttf" is an invalid MIME type ("font" is an unregistered media type) font category didn’t originally exist, but it was added to upstream, where the patch has been ported to different distributions. Upstream patch: https://cgit.freedesktop.org/xdg/desktop-file-utils/commit/?id=92af4108750c… This probably exists in standard Leap packages too, but I can’t test it. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1163052] [Build 563.1] [Hyper-V] YaST2 internal error while saving network configuration
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1163052 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://trello.com/c/vz51Cg | |DT/3917-leap-152-p5-1163052 | |-internal-error-while-savin | |g-network-configuration -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1163052] [Build 563.1] [Hyper-V] YaST2 internal error while saving network configuration
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1163052 http://bugzilla.suse.com/show_bug.cgi?id=1163052#c3 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de --- Comment #3 from Arvin Schnell <aschnell(a)suse.com> --- Maybe the 'include Logger' in save_network.rb should be 'include Yast::logger'. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1163110] New: VUL-1: CVE-2013-3564: vlc: The web interface in no access control which allows remote attackers to view directory listings via the 'dir' command or issue other commands without authenticating
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1163110 Bug ID: 1163110 Summary: VUL-1: CVE-2013-3564: vlc: The web interface in no access control which allows remote attackers to view directory listings via the 'dir' command or issue other commands without authenticating Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/252583/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: rfrohl(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2013-3564 The web interface in VideoLAN VLC media player before 2.0.7 has no access control which allows remote attackers to view directory listings via the 'dir' command or issue other commands without authenticating. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-3564 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-3564 https://www3.trustwave.com/spiderlabs/advisories/TWSL2013-007.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1086755] LibreOffice Calc: Copy only works every other time.
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1086755 http://bugzilla.suse.com/show_bug.cgi?id=1086755#c17 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsegitz(a)suse.com --- Comment #17 from Johannes Segitz <jsegitz(a)suse.com> --- FWIW I have the same issue on Leap 15.1 (current libreoffice, notion as windowmanager) and the SAL_USE_VCL_PLUGIN=gen workaround worked for me -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161832] kernel: scsi_dh_alua: module verification failed: signature and/or required key missing - tainting kernel
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161832 http://bugzilla.suse.com/show_bug.cgi?id=1161832#c15 --- Comment #15 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #14) > > - Why doesn't the OS installer suggest kernel-pae if the CPU supports PAE? > > Is this another bug/issue to report? > > It looks like that. Installer mostly install pae correctly. Maybe your model > is not whitelisted. So open a bug against the installer to find out the > reasons, please. And I am wrong here: PAE allows for NX, but not all CPUs implement that. Yours is one of them (according to lscpu). So maybe that's the reason why -pae was not installed on your system (I'm not sure what's the logic in the installer). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161832] kernel: scsi_dh_alua: module verification failed: signature and/or required key missing - tainting kernel
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161832 http://bugzilla.suse.com/show_bug.cgi?id=1161832#c14 --- Comment #14 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Suse User from comment #13) > Created attachment 829601 [details] > with kernel-pae > > > It really looks like you should use more secure kernel-pae (NX), not kernel-default. > > I was using the kernel which the OS installer suggested. I wasn't aware that > a better option exists and that PAE is relevant for a computer which doesn't > support more than 2GB of RAM. I know what PAE means but I never know it is > "more secure". When a processor supports PAE, it has to (spec says so) support other features like NX too (generally, this one does not allow executing code from data pages). > > Doesn't it work for you? Could you try it? It won't fix this problem, though. > > I installed it and it seems to work (see attachment). > > Now there is a mitigation for L1TF and Meltdown. Unfortunately the other > vulnerabilities remain. The bug reported here remains with kernel-pae too. > (also seen in the attachment) Sure. We have to fix it as per comment 9 first. > Questions: > > - Why doesn't the OS installer suggest kernel-pae if the CPU supports PAE? > Is this another bug/issue to report? It looks like that. Installer mostly install pae correctly. Maybe your model is not whitelisted. So open a bug against the installer to find out the reasons, please. > - Could you please suggest a solution for mitigation of the other > vulnerabilities? (I realize this is "off-topic" but I would very very much > appreciate an advice. Please feel free to email me directly if you think it > is more appropriate or direct me to a proper place to ask/read). Again, open a new bug. It's likely because Intel hasn't released fixed microcode either because the cpu cannot be fixed via microcode or it is too old for them to care about it at all. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161832] kernel: scsi_dh_alua: module verification failed: signature and/or required key missing - tainting kernel
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161832 http://bugzilla.suse.com/show_bug.cgi?id=1161832#c13 --- Comment #13 from Suse User <suseino(a)riseup.net> --- Created attachment 829601 --> http://bugzilla.suse.com/attachment.cgi?id=829601&action=edit with kernel-pae > It really looks like you should use more secure kernel-pae (NX), not kernel-default. I was using the kernel which the OS installer suggested. I wasn't aware that a better option exists and that PAE is relevant for a computer which doesn't support more than 2GB of RAM. I know what PAE means but I never know it is "more secure". > Doesn't it work for you? Could you try it? It won't fix this problem, though. I installed it and it seems to work (see attachment). Now there is a mitigation for L1TF and Meltdown. Unfortunately the other vulnerabilities remain. The bug reported here remains with kernel-pae too. (also seen in the attachment) Questions: - Why doesn't the OS installer suggest kernel-pae if the CPU supports PAE? Is this another bug/issue to report? - Could you please suggest a solution for mitigation of the other vulnerabilities? (I realize this is "off-topic" but I would very very much appreciate an advice. Please feel free to email me directly if you think it is more appropriate or direct me to a proper place to ask/read). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1163088] New: Add SOCK4|5 proxy parameters
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1163088 Bug ID: 1163088 Summary: Add SOCK4|5 proxy parameters Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dgonzalez(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 829592 --> http://bugzilla.opensuse.org/attachment.cgi?id=829592&action=edit Example of how could look This is a feature request done by Mikhail Kasimov via Github issue[1]. I'm just transferring it here. > > > The idea is not unique, but is inspired by Firefox native proxy settings window, which has such field by default -- address:port. > > Additional options to be good to have here: > > 1. sites, CIDRs exclude-list. > > 2. sites, CIDRs include-list. > > SOCK4|5 switcher is radio-button. > > Something like this: > > (see attached image) > > Real story as the reason to have this: A couple of days ago my ISP changed some settings on his side and some IPs, including mine, went to ban-list, but connection via SOCK5 was fine. But I couldn't get system updates via zypper. So, having such setting for zypper seems to be right idea: user sets his socks4|5 proxy connection via yast-proxy module and can have up-to-dated system. > > [1] https://github.com/yast/yast-proxy/issues/13 -- You are receiving this mail because: You are on the CC list for the bug.

1 2