June 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1043393] New: [Build 20170607] autoyast installation - failure in ntp_conf.rb:401
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1043393 Bug ID: 1043393 Summary: [Build 20170607] autoyast installation - failure in ntp_conf.rb:401 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/416998/modules/instal lation/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-autoyast_reinstall_gnome@64bit fails in [installation](http://openqa.opensuse.org/tests/416998/modules/installation/… ## Reproducible Fails since (at least) Build [20170607](http://openqa.opensuse.org/tests/416966) ## Expected result Last good: [20170605](http://openqa.opensuse.org/tests/415603) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?machine=64bit&test=autoyast… ## More info The test has been running three times in openQA, always failing the same way. I will try to reproduce locally and get some yast logs in order to help here (unless you spot already what is wrong like this) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c28 --- Comment #28 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Fabian Vogt from comment #27) > (In reply to Josef Reidinger from comment #25) > > (In reply to Fabian Vogt from comment #24) > > > (In reply to Josef Reidinger from comment #23) > > > > (In reply to Fabian Vogt from comment #22) > > > Maybe QCoreApplication::setApplicationName("YaST2") works here. As YaST does > > > not use QSettings, that shouldn't have any ill side effects > > > > that is what we already doing, so title is correct, but for not known reason > > yet, no effect for icon > > > > https://github.com/libyui/libyui-qt/blob/master/src/YQApplication.cc#L777 > > > > maybe we need to call also this > > qApp->setWindowIcon ( QIcon ( pixmap ) ); > > to some predefined icon for yast, but I am not sure how it works with all > > modules, as it probably have own icons. > > The icon is not the issue here, WM_CLASS is wrong. > > In 42.2, where everything works fine, WM_CLASS = "YaST2", "YaST2", while in > 42.3 and TW WM_CLASS = "ruby", "YaST2 - sw_single @ linux-lm3i.site" ok, I will try to play with passing -name option to qt server, which should fix it. Problem is that WM_CLASS is by default argv[0], which is newly ruby. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043390] New: qemu uses gcc6 to build
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1043390 Bug ID: 1043390 Summary: qemu uses gcc6 to build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- qemu has explicit requires/patches to build using GCC6. Back in the days this was done to favor gcc6 over 4.x/5, in order to produce smaller code. Since TW now moved to gcc7, this is sort-of contra, as we now favor an older compiler over the current one (and the old one is likely supposed to disappear sooner or later) It would thus be great if qemu can be built using gcc7 too -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 944866] smbstatus machine column doesn't resolve hostname and show ip
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=944866 http://bugzilla.suse.com/show_bug.cgi?id=944866#c13 David Mulder <david.mulder(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(bruno(a)ioda-net.ch | |) --- Comment #13 from David Mulder <david.mulder(a)suse.com> --- Please run tcpdump with the -w flag. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c27 --- Comment #27 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Josef Reidinger from comment #25) > (In reply to Fabian Vogt from comment #24) > > (In reply to Josef Reidinger from comment #23) > > > (In reply to Fabian Vogt from comment #22) > > Maybe QCoreApplication::setApplicationName("YaST2") works here. As YaST does > > not use QSettings, that shouldn't have any ill side effects > > that is what we already doing, so title is correct, but for not known reason > yet, no effect for icon > > https://github.com/libyui/libyui-qt/blob/master/src/YQApplication.cc#L777 > > maybe we need to call also this > qApp->setWindowIcon ( QIcon ( pixmap ) ); > to some predefined icon for yast, but I am not sure how it works with all > modules, as it probably have own icons. The icon is not the issue here, WM_CLASS is wrong. In 42.2, where everything works fine, WM_CLASS = "YaST2", "YaST2", while in 42.3 and TW WM_CLASS = "ruby", "YaST2 - sw_single @ linux-lm3i.site" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018770] New: cpu frequency scaling intel_pstate broken
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1018770 Bug ID: 1018770 Summary: cpu frequency scaling intel_pstate broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: napseis(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: hi, I just realized that on my machine, the cpu speed is always maximum. I'm running a clean install of Leap 42.2 with all updates. cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 4.40 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 4.40 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Model name: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c26 --- Comment #26 from Josef Reidinger <jreidinger(a)suse.com> --- note for me: cannot be test in common installation, as common installation do not show any icons. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c25 --- Comment #25 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Fabian Vogt from comment #24) > (In reply to Josef Reidinger from comment #23) > > (In reply to Fabian Vogt from comment #22) > > > (In reply to Josef Reidinger from comment #21) > > > > ok, so we at least move forward. I will check this icon issue, how to do it > > > > in qt properly. > > > > > > It's not the icon, it's the WM_CLASS. It should be enough to just override > > > the passed argv[0] to the QApplication constructor, restoring the behaviour > > > before YaST launched with argv[0] == "ruby" > > > > and that's the part that is not so easy, as libyui obtain it from /proc > > > > see > > https://github.com/libyui/libyui-qt/blob/ > > 817ddbe637c98a54460b1152ec9d51e7f2d9422e/src/YQUI.cc#L126 > > > > in past it works due to this dirty hack, but we no longer want such nasty > > hack. So we need find better way to pass it > > https://github.com/libyui/libyui-qt/blob/ > > 817ddbe637c98a54460b1152ec9d51e7f2d9422e/src/YQUI.cc#L141 > > Maybe QCoreApplication::setApplicationName("YaST2") works here. As YaST does > not use QSettings, that shouldn't have any ill side effects that is what we already doing, so title is correct, but for not known reason yet, no effect for icon https://github.com/libyui/libyui-qt/blob/master/src/YQApplication.cc#L777 maybe we need to call also this qApp->setWindowIcon ( QIcon ( pixmap ) ); to some predefined icon for yast, but I am not sure how it works with all modules, as it probably have own icons. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043146] Put drm-kmp to default installation or media
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043146 http://bugzilla.suse.com/show_bug.cgi?id=1043146#c9 --- Comment #9 from Frederic Crozat <fcrozat(a)suse.com> --- (In reply to Steffen Winterfeldt from comment #8) > https://github.com/openSUSE/installation-images/pull/187 > > I will include the drm only for leap-42.3. If it should be done for > sle12-sp3, Frederic, please let me know. I think we can stay without drm-default on SLED (ans SLES of course). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1022999] VUL-0: CVE-2017-0358: ntfs-3g: modprobe influence vulnerability via environment variables
by bugzilla_noreply＠novell.com 08 Jun '17

08 Jun '17

http://bugzilla.novell.com/show_bug.cgi?id=1022999 SMASH SMASH <smash_bz(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| | | |CVSSv3:RedHat:CVE-2017-0358 | |:7.0:(AV:L/AC:H/PR:L/UI:N/S | |:U/C:H/I:H/A:H) | |CVSSv2:SUSE:CVE-2017-0358:6 | |.9:(AV:L/AC:M/Au:N/C:C/I:C/ | |A:C) -- You are receiving this mail because: You are on the CC list for the bug.

1 0