August 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 984976] XF86MonBrightnessDown and XF86MonBrightnessUp don't work in TW-20160422
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.novell.com/show_bug.cgi?id=984976 http://bugzilla.novell.com/show_bug.cgi?id=984976#c2 --- Comment #2 from H.Merijn Brand <h.m.brand(a)xs4all.nl> --- I meanwhile have a new laptop (still with TumbleWeed) and both keys work fine on that: Linux 4.11.8-2-default [openSUSE Tumbleweed 20170730] HP ZBook 15G3 Core(TM) i7-6820HQ CPU @ 2.70GHz/3344(8) x86_64 15967 Mb I revived the old laptop and checked. On TW 20170613 the keys were still not functional. 5547 updates and a reboot later, I checked again and the keys still do not act as expected. Brigtness Down (with the cursor shown over an xterm window) removes the cursor, Brightness Up shows the cursor again. When the cursor is over de desktop background (no active window) both seem to be no-ops. That laptop being a Linux 4.11.4-1-default [openSUSE Tumbleweed 20170730] HP EliteBook 8560p/1618 Core(TM) i7-2620M CPU @ 2.70GHz/1047(4) x86_64 7931 Mb I rsynced my home folder from the old to the new laptop, so all personal settings for plasma were identical. Does this need still more info, or should this bug be closed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 439717] Spanish keyboard, key '~' is no longer dead key
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=439717 http://bugzilla.opensuse.org/show_bug.cgi?id=439717#c7 Zhao Qiang 赵强 <qzhao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qzhao(a)suse.com --- Comment #7 from Zhao Qiang 赵强 <qzhao(a)suse.com> --- (In reply to Carlos Robinson from comment #6) > Leap 42.2 one keypress. > > This behaviour has stuck for several years, so behaviour seems to have > stabilized. Closing. Could you give me more information? I don't understand your logic. Do you mean you will close bug because nobody help to fix it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1044409] Yast2 installation error, the drive hd0 is defined multiple times in the device map
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1044409 http://bugzilla.suse.com/show_bug.cgi?id=1044409#c15 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|yast2-maintainers(a)suse.de |jreidinger(a)suse.com --- Comment #15 from Josef Reidinger <jreidinger(a)suse.com> --- fix is in review https://github.com/config-files-api/config_files_api_grub2/pull/19 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1044409] Yast2 installation error, the drive hd0 is defined multiple times in the device map
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1044409 http://bugzilla.suse.com/show_bug.cgi?id=1044409#c14 --- Comment #14 from Josef Reidinger <jreidinger(a)suse.com> --- Now, I reproduced it. It is caused by non-related read of other file. I will prepare fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1011144] qemu-tools: group kvm does not exist - using root
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1011144 http://bugzilla.opensuse.org/show_bug.cgi?id=1011144#c1 Christian Wittmer <chris(a)computersalat.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |chris(a)computersalat.de --- Comment #1 from Christian Wittmer <chris(a)computersalat.de> --- (17/21) Installing: qemu-tools-2.6.2-31.3.3.x86_64 .........................................................................................................................................................[done] Additional rpm output: warning: group kvm does not exist - using root /usr/lib/qemu-bridge-helper: unknown group kvm so any news on this ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1051346] bluetoothd crash
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1051346 Al Cho <acho(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |acho(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1049433] [Build 20170717] openQA test fails in yast2_samba - sbin/yast2 line 448 12743 Aborted (core dumped)
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1049433 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903753] New: usb_modeswitch-2.1.1-2.3.1.x86_64 is incompatible with usb_modeswitch-data-2.1.1-2.3.1.noarch
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903753 Bug ID: 903753 Summary: usb_modeswitch-2.1.1-2.3.1.x86_64 is incompatible with usb_modeswitch-data-2.1.1-2.3.1.noarch Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bpesavento(a)infinito.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In 13.2-OSS repo, package usb_modeswitch-2.1.1-2.3.1.x86_64 is incompatible with matching package usb_modeswitch-data-2.1.1-2.3.1.noarch. Huawei 3G dongles do not switch out of "CD-mode" with thiis setup. With the first one, usb_modeswitch -e yields: * usb_modeswitch: handle USB devices with multiple modes * Version 2.1.1 (C) Josua Dietze 2014 * Based on libusb1/libusbx while the second contains file 40-usb_modeswitch.rules which reads: # Part of usb-modeswitch-data, version 20140529 # # Works with usb_modeswitch versions >= 2.2.0 (introduction of HuaweiNewMode) A workaround is installing usb_modeswitch-data-2.1.1-2.1.6.noarch (from 13.2RC1) whose file 40-usb_modeswitch.rules reads: # Part of usb-modeswitch-data, version 20140327 # # Works with usb_modeswitch versions >= 2.1.0 (introduction of StandardEject) Versions 5.1 and 14.1 available in additional repos as of today are affected too. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1045720] The WWAN-Network is not offered in Leap 42.3. Hardware Thinkpad T470s, WWAN Qualcomm Snapdragon X7 LTE-A
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1045720 http://bugzilla.suse.com/show_bug.cgi?id=1045720#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guenter.stoehr@gs-consult-a | |c.de, tiwai(a)suse.com Flags| |needinfo?(guenter.stoehr@gs | |-consult-ac.de) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Please try to get hwinfo output on both TW and Leap 42.3 systems. This may show the difference. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036788] New: ship current obs cli toolchain
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1036788 Bug ID: 1036788 Summary: ship current obs cli toolchain Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: marco.strigl(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- bug tracker for shipping current cli tool chain -- You are receiving this mail because: You are on the CC list for the bug.

1 4