June 2017 - openSUSE Bugs - openSUSE Mailing Lists

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

07 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043146 http://bugzilla.suse.com/show_bug.cgi?id=1043146#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Oh, one thing I wanted to confirm: currently drm-kmp is built only for x86-64. Does it matter for patterns and installation images? -- 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 07 Jun '17

07 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043146 http://bugzilla.suse.com/show_bug.cgi?id=1043146#c2 --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1043146) was mentioned in https://build.opensuse.org/request/show/501775 42.3 / patterns-openSUSE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043186] New: Leap 42.2 does not support Intel Dual Band Wireless AC(2x2) 8265
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1043186 Bug ID: 1043186 Summary: Leap 42.2 does not support Intel Dual Band Wireless AC(2x2) 8265 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: steil(a)b1-systems.de QA Contact: qa-bugs(a)suse.de CC: seife(a)novell.slipkontur.de Found By: --- Blocker: --- The wifi card in my new Lenovo Thinkpad T470s is not supported. A quick test with a kernel from Kernel:stable (4.11.3-6.g3a35823-default) shows that the driver was added after kernel 4.4, because 4.11.3 works fine. The exact type of card is: # hwinfo --netcard 10: PCI 3a00.0: 0282 WLAN controller [Created at pci.378] Unique ID: y9sn.DVcPkv35sTA Parent ID: hoOk.olPSGAJs4W4 SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:3a:00.0 SysFS BusID: 0000:3a:00.0 Hardware Class: network Model: "Intel WLAN controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x24fd SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x1010 Revision: 0x78 Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlan0 Features: WLAN Memory Range: 0xec100000-0xec101fff (rw,non-prefetchable) IRQ: 130 (50500 events) HW Address: ... Permanent HW Address: ... Link detected: yes WLAN channels: ... WLAN frequencies: ... WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d000024FDsv00008086sd00001010bc02sc80i00" Driver Info #0: Driver Status: iwlwifi is active Driver Activation Cmd: "modprobe iwlwifi" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #17 (PCI bridge) [...] lspci shows it as: # lspci -vn 00:00.0 0600: 8086:5904 (rev 02) Subsystem: 17aa:224b Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=10 <?> [...] 3a:00.0 0280: 8086:24fd (rev 78) Subsystem: 8086:1010 Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at ec100000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-28-f8-ff-ff-3d-5d-d3 Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi [...] It would be great if the driver could be backported, so that this also works in the future Leap 42.3 version. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 908736] New: wicked breaks usage of Predictable Network Interface Names with kernel-xen+xen
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=908736 Bug ID: 908736 Summary: wicked breaks usage of Predictable Network Interface Names with kernel-xen+xen 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: grantksupport(a)operamail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- a 13.2 server, booted to kernel-default, works with auto interface naming. re-booting to xen host Linux lab003 3.17.4-3.gbde0c3f-xen #1 SMP Fri Dec 5 16:20:27 UTC 2014 (bde0c3f) x86_64 x86_64 x86_64 GNU/Linux with xen-4.4.1_06-342.1.x86_64 physical/ethernet devices using automated interface naming, and the bridges that use them, are no longer brought up ... Dec 06 21:23:13 lab003 wickedd[1480]: failed to install generic settings Dec 06 21:23:13 lab003 ModemManager[1430]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:04.0/0000:02:00.0': not supported by any plugin Dec 06 21:23:13 lab003 ModemManager[1430]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:06.0/0000:03:00.0': not supported by any plugin Dec 06 21:23:15 lab003 kernel: Unable to read sysrq code in control/sysrq Dec 06 21:23:16 lab003 systemd[1]: xend.service: Supervising process 1577 which is not our child. We'll most likely not notice when it exits. Dec 06 21:23:16 lab003 systemd[1]: Starting Xen-watchdog - run xen watchdog daemon... Dec 06 21:23:41 lab003 wicked[1495]: device brA failed: operation timed out Dec 06 21:23:41 lab003 wicked[1495]: device brB failed: operation timed out Dec 06 21:23:41 lab003 wicked[1495]: device enp3s0 failed: operation timed out Dec 06 21:23:41 lab003 wicked[1495]: device enp2s0 failed: operation timed out Dec 06 21:23:41 lab003 systemd-journal[801]: Forwarding to syslog missed 26 messages. Dec 06 21:23:41 lab003 wicked[1495]: lo up Dec 06 21:23:41 lab003 wicked[1495]: brA device-not-running Dec 06 21:23:41 lab003 wicked[1495]: brB device-not-running Dec 06 21:23:41 lab003 wicked[1495]: enp2s0 no-device Dec 06 21:23:41 lab003 wicked[1495]: enp3s0 no-device Dec 06 21:23:41 lab003 systemd[1]: Starting Network. Dec 06 21:23:41 lab003 systemd[1]: Reached target Network. ... the system reaches shell, but with no eth/bridge interfaces -- no external/lan networking disabling ifname'ing by adding to grub net.ifnames=0 adding a persistent udev rule ls -al /etc/udev/rules.d/70-persistent-net.rules (empty) cat << EOF > /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="yy:yy:yy:yy:yy:yy", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" EOF and renaming instances of enp2s0 -> eth0 enp3s0 -> eth1 in /etc/sysconfig/network/* fixes the problem; system now boots correctly, with fully functional networking ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master brB state UP mode DEFAULT group default qlen 1000 link/ether yy:yy:yy:yy:yy:yy brd ff:ff:ff:ff:ff:ff 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master brA state UP mode DEFAULT group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff 4: brA: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff 5: brB: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default link/ether yy:yy:yy:yy:yy:yy brd ff:ff:ff:ff:ff:ff -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1040272] The keyboard layout selected in installer is not pre-selected in the yast configuration dialog in the installed system
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1040272 http://bugzilla.suse.com/show_bug.cgi?id=1040272#c4 --- Comment #4 from Oliver Kurz <okurz(a)suse.com> --- One more thing: If in the installed system I just open the "system keyboard layout" module, keep the selection and confirm, the module says "Updating system configuration…" and is busy for quite some time but does not have a visible impact. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1040272] The keyboard layout selected in installer is not pre-selected in the yast configuration dialog in the installed system
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1040272 http://bugzilla.suse.com/show_bug.cgi?id=1040272#c3 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(okurz(a)suse.com) | --- Comment #3 from Oliver Kurz <okurz(a)suse.com> --- (In reply to Stefan Hundhammer from comment #2) > Oliver, did you set the keyboard in the installation ISO's boot screen > (gfxboot) or in one of the first YaST dialogs? It was the second: "welcome" screen in the YaST installer gui. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1021803] glamor (modeset/Xephyr) Wrong lineends in XDrawLine()
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1021803 http://bugzilla.suse.com/show_bug.cgi?id=1021803#c48 --- Comment #48 from Stefan Dirsch <sndirsch(a)suse.com> --- Michal Srb took the patches from the original home:mstaudt:1021803boo-glamor-xdrawline-dashing-sle project and resubmitted xorg-x11-server to https://build.suse.de/request/show/133804 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043122] yast2-registration package installed by upgrade to openSUSE 42.3beta
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1043122 http://bugzilla.opensuse.org/show_bug.cgi?id=1043122#c2 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium --- Comment #2 from Ludwig Nussel <lnussel(a)suse.com> --- Ah, that's where it comes from :-) I also had it on my todo to check this. A !0%{?is_opensuse} around the recommends should fix it in a non-intrusive way. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003085] New: rabbitmq-server fails to start when epmd is started from service
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1003085 Bug ID: 1003085 Summary: rabbitmq-server fails to start when epmd is started from service Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: dmueller(a)suse.com Reporter: tchatzimichos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mchandras(a)suse.com, rhafer(a)suse.com Found By: --- Blocker: --- The following issue affects the currently latest maintenance update for Leap 42.1 for rabbitmq-server, 3.5.1-4.1. It works fine with 3.5.1-2.7. When starting epmd via service, rabbitmq-server fails to start. It works if we don't start epmd from the service, but instead let rabbitmq start it. A few command outputs below: ## working scenario odb:~ # ps aux | grep epmd | grep -v grep odb:~ # rcrabbitmq-server start odb:~ # rcrabbitmq-server status rabbitmq-server.service - RabbitMQ broker Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled) Active: active (running) since Wed 2016-10-05 13:02:44 UTC; 2s ago Process: 5615 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS) Main PID: 5750 (epmd) Status: "Exited." CGroup: /system.slice/rabbitmq-server.service ├─5731 /bin/sh /usr/sbin/rabbitmq-server ├─5735 /usr/lib64/erlang/erts-7.0.3/bin/beam.smp -W w -K true -A30 -P 1048576 -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib64/rabbitmq/lib/rabbitmq_server-3.5.1/sbin/../ebin -noshell -noinput -s rabbit boot -sname rabbit@localhost -boot start_sasl -config /etc/rabbitmq/rabbitmq -kernel inet_default_connect_options [{nodelay,true}] -rabbit tcp_listeners [{"auto",5672}] -sasl errlog_type error -sasl sasl_error_logger false -rabbit error_logger {file,"/var/log/rabbitmq/rabbit(a)localhost.log"} -rabbit sasl_error_logger {file,"/var/log/rabbitmq/rabbit(a)localhost-sasl.log"} -rabbit enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir "/usr/lib64/rabbitmq/lib/rabbitmq_server-3.5.1/sbin/../plugins" -rabbit plugins_expand_dir "/var/lib/rabbitmq/mnesia/rabbit@localhost-plugins-expand" -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit@localhost" -kernel inet_dist_listen_min 25672 -kernel inet_dist_listen_max 25672 └─5750 /usr/lib64/erlang/erts-7.0.3/bin/epmd -daemon Oct 05 13:02:44 odb systemd[1]: Starting RabbitMQ broker... Oct 05 13:02:44 odb systemd[1]: Started RabbitMQ broker. odb:~ # ps aux | grep epmd | grep -v grep rabbitmq 5750 0.0 0.0 25228 208 ? S 13:02 0:00 /usr/lib64/erlang/erts-7.0.3/bin/epmd -daemon ## non-working scenario odb:~ # ps aux | grep epmd | grep -v grep odb:~ # rcepmd start odb:~ # rcepmd status epmd.service - Erlang Port Mapper Daemon Loaded: loaded (/usr/lib/systemd/system/epmd.service; enabled) Active: active (running) since Wed 2016-10-05 13:05:14 UTC; 1s ago Main PID: 5992 (epmd) CGroup: /system.slice/epmd.service └─5992 /usr/bin/epmd -systemd Oct 05 13:05:14 odb systemd[1]: Starting Erlang Port Mapper Daemon... Oct 05 13:05:14 odb systemd[1]: Started Erlang Port Mapper Daemon. odb:~ # ps aux | grep epmd | grep -v grep epmd 5992 0.0 0.0 25228 1480 ? Ss 13:05 0:00 /usr/bin/epmd -systemd odb:~ # rcrabbitmq-server start Job for rabbitmq-server.service failed. See "systemctl status rabbitmq-server.service" and "journalctl -xn" for details. journactl reports: Oct 05 13:07:18 odb systemd[1]: Starting RabbitMQ broker... Oct 05 13:07:18 odb systemd[1]: Cannot find unit for notify message of PID 6294. Oct 05 13:08:48 odb systemd[1]: rabbitmq-server.service start operation timed out. Terminating. Oct 05 13:08:48 odb systemd[1]: Failed to start RabbitMQ broker. Oct 05 13:08:48 odb systemd[1]: Unit rabbitmq-server.service entered failed state. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1043162] New: Unable to add .ovpn files from NetworkManager, "Add" button is greyed-out
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1043162 Bug ID: 1043162 Summary: Unable to add .ovpn files from NetworkManager, "Add" button is greyed-out Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kenziefc(a)teknik.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: Unable to add a ovpn profile from NetworkManager. The same profile works on openSUSE Tumbleweed. Reproducible: Always Steps to Reproduce: 1. Open NetworkManager setting (gnome-shell) 2. Click the add button, (+) sign 3. Choose VPN 4. Select Import From File 5. Select the .ovpn file 6. "Add" button on the bottom right is greyed-out Actual Results: The button "Add" should not be greyed-out Expected Results: The button "Add" is greyed out Fresh installed openSUSE 42.2, tested on 3 different laptops (Lenovo Thinkpads). Running the profile with: openvpn --config profile.ovpn works. -- You are receiving this mail because: You are on the CC list for the bug.

1 0