March 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1016288] konsole doesn't set the 'Machine' property when run remotely
by bugzilla_noreply＠novell.com 03 Mar '19

03 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1016288 http://bugzilla.opensuse.org/show_bug.cgi?id=1016288#c2 Wolfgang Bauer <wbauer(a)tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer(a)tmo.at --- Comment #2 from Wolfgang Bauer <wbauer(a)tmo.at> --- (In reply to Fabian Vogt from comment #1) > Indeed, it looks like this got lost when Qt switched to XCB. > > No idea what the equivalent to XSetWMProperties is. Maybe this helps? https://lists.freedesktop.org/archives/xcb/2009-May/004658.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124762] VUL-0: CVE-2019-7628: pagure: leaks API keys by e-mailing them to users
by bugzilla_noreply＠novell.com 03 Mar '19

03 Mar '19

http://bugzilla.novell.com/show_bug.cgi?id=1124762 http://bugzilla.novell.com/show_bug.cgi?id=1124762#c2 Neal Gompa <ngompa13(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Neal Gompa <ngompa13(a)gmail.com> --- Fixed with the update to 5.3: https://build.opensuse.org/package/rdiff/openSUSE:Leap:15.1/pagure?linkrev=… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1112973] New: Cant't start yast2 from menu
by bugzilla_noreply＠novell.com 03 Mar '19

03 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1112973 Bug ID: 1112973 Summary: Cant't start yast2 from menu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: bdonauba(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Since a few weeks I can not start yast2 from the menu. The command line behind the menu entry is: > /usr/bin/xdg-su -c /sbin/yast2 If I enter this command in a terminal I get this output: > No protocol specified > lxqt-sudo: Stripping child environment except for: DISPLAY, LANG, LANGUAGE, LC_ADDRESS, LC_ALL, LC_COLLATE, LC_CTYPE, LC_IDENTIFICATION, LC_MEASUREMENT, LC_MESSAGES, LC_MONETARY, LC_NAME, LC_NUMERIC, LC_PAPER, LC_TELEPHONE, LC_TIME, PATH, QT_PLATFORM_PLUGIN, QT_QPA_PLATFORMTHEME, WAYLAND_DISPLAY, XAUTHORITY > > No protocol specified > No protocol specified > qt.qpa.screen: QXcbConnection: Could not connect to display :0 > Could not connect to any X display. > qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. > qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" > This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. > > Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. > > /sbin/yast2: Zeile 455: 8361 Abgebrochen (Speicherabzug geschrieben) $y2ccbin $Y2UI_ARGS "$@" If I do first "su -" and call then "yast2" everything is fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1127260] New: Internal compiler error when trying to build VTK 8.2.0
by bugzilla_noreply＠novell.com 03 Mar '19

03 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127260 Bug ID: 1127260 Summary: Internal compiler error when trying to build VTK 8.2.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 798338 --> http://bugzilla.opensuse.org/attachment.cgi?id=798338&action=edit Preprocessed code G++ fails with the following message: --- /home/abuild/rpmbuild/BUILD/VTK-8.2.0/Filters/Extraction/vtkValueSelector.cxx: In instantiation of 'void {anonymous}::ArrayValueMatchFunctor::operator()(InputArrayType*, SelectionListArrayType*) [with InputArrayType = vtkAOSDataArrayTemplate<char>; SelectionListArrayType = vtkAOSDataArrayTemplate<char>]': /home/abuild/rpmbuild/BUILD/VTK-8.2.0/Common/Core/vtkArrayDispatch.txx:160:13: required from 'static bool vtkArrayDispatch::impl::Dispatch2Trampoline<Array1T, vtkTypeList::TypeList<U, Tail> >::Execute(Array1T*, vtkDataArray*, Worker&) [with Worker = {anonymous}::ArrayValueMatchFunctor; Array1T = vtkAOSDataArrayTemplate<char>; Array2Head = vtkAOSDataArrayTemplate<char>; Array2Tail = vtkTypeList::NullType]' /home/abuild/rpmbuild/BUILD/VTK-8.2.0/Common/Core/vtkArrayDispatch.txx:215:33: required from 'static bool vtkArrayDispatch::impl::Dispatch2Same<vtkTypeList::TypeList<T, Tail>, ArrayList2>::Execute(vtkDataArray*, vtkDataArray*, Worker&) [with Worker = {anonymous}::ArrayValueMatchFunctor; ArrayHead = vtkAOSDataArrayTemplate<char>; ArrayTail = vtkTypeList::TypeList<vtkAOSDataArrayTemplate<double>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<float>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long long int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<short int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<signed char>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<unsigned char>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<unsigned int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long unsigned int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long long unsigned int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<short unsigned int>, vtkTypeList::NullType> > > > > > > > > > > >; ArrayList2 = vtkTypeList::TypeList<vtkAOSDataArrayTemplate<char>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<double>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<float>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long long int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<short int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<signed char>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<unsigned char>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<unsigned int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long unsigned int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<long long unsigned int>, vtkTypeList::TypeList<vtkAOSDataArrayTemplate<short unsigned int>, vtkTypeList::NullType> > > > > > > > > > > > >]' /home/abuild/rpmbuild/BUILD/VTK-8.2.0/Common/Core/vtkArrayDispatch.txx:640:31: required from 'static bool vtkArrayDispatch::Dispatch2BySameValueType<ValueTypeList>::Execute(vtkDataArray*, vtkDataArray*, Worker&) [with Worker = {anonymous}::ArrayValueMatchFunctor; ValueTypeList = vtkTypeList::TypeList<double, vtkTypeList::TypeList<float, vtkTypeList::TypeList<char, vtkTypeList::TypeList<int, vtkTypeList::TypeList<long int, vtkTypeList::TypeList<long long int, vtkTypeList::TypeList<short int, vtkTypeList::TypeList<signed char, vtkTypeList::TypeList<unsigned char, vtkTypeList::TypeList<unsigned int, vtkTypeList::TypeList<long unsigned int, vtkTypeList::TypeList<long long unsigned int, vtkTypeList::TypeList<short unsigned int, vtkTypeList::NullType> > > > > > > > > > > > >]' /home/abuild/rpmbuild/BUILD/VTK-8.2.0/Filters/Extraction/vtkValueSelector.cxx:362:76: required from here /home/abuild/rpmbuild/BUILD/VTK-8.2.0/Filters/Extraction/vtkValueSelector.cxx:123:50: internal compiler error: in lookup_template_class_1, at cp/pt.c:9459 --- Affected: TW/Factory, x86_64, aarch64 https://build.opensuse.org/project/monitor/home:StefanBruens:branches:scien… gcc version 8.2.1 20190204 [gcc-8-branch revision 268513] (SUSE Linux) Preprocessed output (attached) fails to build, e.g. g++ -o /tmp/o.o -c vtkValueSelector.cxx -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1126106] New: home:Sauerland/rtl8812AU_8821AU: Bug
by bugzilla_noreply＠novell.com 03 Mar '19

03 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1126106 Bug ID: 1126106 Summary: home:Sauerland/rtl8812AU_8821AU: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: Sauerlandlinux(a)gmx.de Reporter: ocortes(a)mpcnet.com.br QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- After install this version (20190205) on OpenSuse 15.1 (4.12.14-lp150.12.48-default) I couldn't mount nfs drivers neither run remote X applications (e.g. yast2). -- You are receiving this mail because: You are on the CC list for the bug.

1 32

[Bug 1126362] New: Forum text is not preserved for a reply with Konqueror 18.12.2.
by bugzilla_noreply＠novell.com 03 Mar '19

03 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1126362 Bug ID: 1126362 Summary: Forum text is not preserved for a reply with Konqueror 18.12.2. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am trying the software “Konqueror 18.12.2-1.1” out. Now I would like to reply to a message for a specific topic by a well-known user interface for a discussion forum. https://forums.opensuse.org/newreply.php?do=newreply&p=… The form “Reply to Thread” is displayed together with the input field which offers a few extra editing options. Unfortunately, the quoted message text did not appear there. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1127602] VUL-0: CVE-2019-5786: chromium: Use-after-free in FileReader
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127602 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127607] New: Old Arabic fonts remain for Arabic texts after restoring the default fonts or replacing them with other non-Arabic fonts.
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127607 Bug ID: 1127607 Summary: Old Arabic fonts remain for Arabic texts after restoring the default fonts or replacing them with other non-Arabic fonts. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: naguib.iceman(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36 Build Identifier: I have changed all the fonts except the Fixed width font to Noto Kufi Arabic, but it was not good for me. So I have restored the default fonts, but I have found that Arabic texts (e.g. files' and folders' names) remained viewed in Noto Kufi Arabic while non-Arabic texts changed to be viewed in the default fonts. I then changed all the fonts except the Fixed width font to KacstOne and the all texts changed to be viewed in it. Whenever I restore the default fonts or choose non-Arabic fonts, Arabic texts become viewed in Noto Kufi Arabic. It's also noteworthy that while my default font is KacstOne, some applications like Google Chrome and Firefox default to Noto Kufi Arabic. Even after changing all Google Chrome's fonts to KacstOne, in certain places (e.g. the Search Bar and the Tab Bar) Arabic texts remain viewed in Noto Kufi Arabic rather than KacstOne. Reproducible: Always Steps to Reproduce: 1. Open YaST from System in the Application Menu. 2. Choose Language from System. 3. Select Arabic from Secondary Languages. 4. Press OK. 5. Create, anywhere on the computer, a file or folder with the following name (to display the results): محمود محمَّد نجيب محمَّد. 6. Open Configure Desktop from Settings in the Application Menu. 7. Choose Adjust All Fonts. 8. Click on Font and select Noto Kufi Arabic then press OK. 9. Restore the default fonts or change all the fonts to a non-Arabic font. Actual Results: Even after logging out and then logging in, restarting the computer, and shutting the the computer down and starting it up, the file or folder named محمود محمَّد نجيب محمَّد remains viewed in Noto Kufi Arabic instead of the system's default font or the non-Arabic font selected as the default font. Expected Results: The file or folder named محمود محمَّد نجيب محمَّد should have been viewed in the system's default font or any non-Arabic font selected as the default font. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1127443] New: Can't install vagrant, nothing provides /usr/bin/ruby.ruby2.5
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127443 Bug ID: 1127443 Summary: Can't install vagrant, nothing provides /usr/bin/ruby.ruby2.5 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: sekhemty(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It is currently not possible to correctly install vagrant due to a ruby dependency. To be more specific: ~> LANG=C sudo zypper in vagrant [sudo] password for root: Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides /usr/bin/ruby.ruby2.5 needed by vagrant-2.2.0-1.3.x86_64 Solution 1: do not install vagrant-2.2.0-1.3.x86_64 Solution 2: break vagrant-2.2.0-1.3.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): -- You are receiving this mail because: You are on the CC list for the bug.

1 7

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

02 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127605 Bug ID: 1127605 Summary: Can not install packages via 1-click install in appliance if dummy-release is installed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 798633 --> http://bugzilla.opensuse.org/attachment.cgi?id=798633&action=edit y2logs There is appliance (ISO image for Live CD) created in openSUSE Build service. I boot from it, download YMP file (1-click install file). I open it, but it fails: Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Details: Failed to load Module 'OneClickInstallWidgets' due to: No base product found Caller: /usr/share/YaST2/modules/Product.rb:130:in `FindBaseProducts' Workaround: remove "dummy-release" package and install "openSUSE-release" package. After this workaround, I can successfully install via 1-click install -- You are receiving this mail because: You are on the CC list for the bug.

1 0