April 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 908383] New: VirtualBox Kernelmodule not loaded if fstab with not mountable cifs mountpoint
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=908383 Bug ID: 908383 Summary: VirtualBox Kernelmodule not loaded if fstab with not mountable cifs mountpoint Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: juergenhuber(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 1. Install openSUSE 64bit from scratch 2. Install VirtualBox-qt with yast, install all recommended dependencies 3. Create a new Machine with an .iso - CD-ROM-File -> test Startup of VM -> VM starts up. 4. Add an remote cifs mountpoint to your fstab which isn't online 5. Reboot the Machine 6. Try to start the even working new VM -> VirtualBox reports that the startup isn't possible because the kernel module is missing. 7. Remove the fstab Entry from 4. -> Reboot -> Restart VM, Works again. My sample-Entry to fstab: //192.168.0.1/dat /server cifs users,credentials=/etc/.pass-pw,gid=users,uid=jue 0 0 The credentials-file was available (double-checked). In my case the remote-share is inside of a VM, so the first mount during startup will fail. Since the error appears the mount will never work because the VM cannot come up. Same configuration on openSUSE 12.3 worked. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 929224] New: system can't start/top services anymore, can't reboot, can't be shutdown
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=929224 Bug ID: 929224 Summary: system can't start/top services anymore, can't reboot, can't be shutdown Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: chuller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The problem manifested itself the first time i tried to restart libvirtd: ------------------------snip-------------------------- skaro:~ # rclibvirtd restart Failed to restart libvirtd.service: Transaction is destructive ------------------------snip-------------------------- The message only appeared lie 5 minutes after entering the command Next i wanted to reboot the system, which simply just did not do anything at all, it just hung: ------------------------snip-------------------------- skaro:/usr/src/chuller/pennyworth # reboot ------------------------snip-------------------------- So I started looking for logs or any indication on why it does behave so weird. dmesg did not show anything suspicious but one i ran journalctl it became pretty clear that systemd somehow seems to be responsible for the current state my machine was in. It showed a entry saying "systemd[1]: Looping too fast. Throttling execution a little." every single second: ------------------------snip-------------------------- -- Logs begin at Fri 2014-11-28 18:35:55 CET, end at Thu 2015-04-30 14:53:41 CEST. -- Apr 30 14:53:41 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:40 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:39 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:38 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:36 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:35 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:34 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:32 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:31 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:30 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:28 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:27 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:26 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:24 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:23 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:22 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:21 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:19 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:18 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:17 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:15 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:14 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:13 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:11 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:10 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:09 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:08 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:06 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:05 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:04 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:02 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:01 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:00 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:58 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:57 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:56 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:54 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:53 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:52 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:51 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:49 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:48 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:47 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:45 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:44 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:43 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:41 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:40 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:39 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:38 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:36 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:35 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:34 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:32 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:31 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:30 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:28 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:27 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:26 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:25 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:23 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:22 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:21 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:19 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:18 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:17 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:15 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:14 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:13 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:12 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:10 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:09 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:08 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:06 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:05 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:04 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:02 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:01 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:00 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:58 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:57 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:56 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:54 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:53 skaro systemd[1]: Looping too fast. Throttling execution a little. ------------------------snip-------------------------- which also made me chek ho much of diskspace the log file already uses: ------------------------snip-------------------------- skaro:~ # journalctl --disk-usage Journals take up 552.0M on disk. ------------------------snip-------------------------- that made me try some more journalctl functions and it turned out my journal was not consistent anymore as well: ------------------------snip-------------------------- skaro:~ # journalctl --verify 392b28: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% 3912e8: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% ccbd68: unused data (entry_offset==0)██████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 46% ccbdc8: unused data (entry_offset==0) Entry number mismatch File corruption detected at /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system@00051483eed4fe2e-4ab91595e03ea8a3.journal~:000000 (of 16777216 bytes, 0%). FAIL: /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system(a)00051483eed4fe2e-4ab91595e03ea8a3.journal~ (Bad message) 391bb0: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% Data object references invalid entry at 4002856███████████████████████████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 75% File corruption detected at /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system.journal:000000 (of 16777216 bytes, 0%). FAIL: /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system.journal (Bad message) ------------------------snip-------------------------- Please advise on how to be able to reboot the system once in such a stage, or even better on how to fix the problem without a reboot. I currently am unable to do productive work with it and need to get it back into a state where i can do QA on kvm/libvirt environments. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 922299] New: rpmlint ghost-files-without-postin useless
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=922299 Bug ID: 922299 Summary: rpmlint ghost-files-without-postin useless Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: lnussel(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- looks like the ghost-files-without-postin was intended to skip %config(missingok) but it doesn't -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 918787] New: logprof fails to parse audit.log
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=918787 Bug ID: 918787 Summary: logprof fails to parse audit.log Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A lot of daemons produce log entries like: type=AVC msg=audit(1424425690.883:716630): apparmor="ALLOWED" operation="file_mmap" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/httpd2-prefork//null-4172" name="var/run/nscd/passwd" pid=25333 comm="id" requested_mask="r" denied_mask="r" fsuid=1002 ouid=0 but logprof is not able to parse this entry cause name="var/run/nscd/passwd" is an invalid entry for it. So either apparmor produces wrong entries in audid.log or the tool should be able to handle it! -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 918571] New: perl-DBIx-Class data corruption
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=918571 Bug ID: 918571 Summary: perl-DBIx-Class data corruption Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: gerrit.beine(a)gmx.de Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- DBIx::Class suffers from a data corruption bug that could result in entire tables getting dropped: https://github.com/dbsrgits/dbix-class/commit/31160673f390e178ee347e7ebee1f… This affects openQA. Would it be possible to upgrade 13.2 to 0.082801? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 910780] New: Disable IPv6 from the "gnome-control-center->network" is not workable
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=910780 Bug ID: 910780 Summary: Disable IPv6 from the "gnome-control-center->network" is not workable Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: xdzhang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 617961 --> http://bugzilla.suse.com/attachment.cgi?id=617961&action=edit the ipv6 is disabled Tested with fresh installed opensuse 13.2 Steps: 1. Open "gnome-control-center->network", disable the ipv6 of the wired connection. Actual result: It still get ipv6 address. Expected result: It should not get ipv6 address any more. Attached is the screenshot. More information: 1. After disabled ipv6 from the gnome-control-center, I also tried with "systemctl restart network" but still got same result. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 907718] New: NetworkManager 'CRITICAL' errors on boot: assertion 'G_TYPE_CHECK_INSTANCE (instance)' & 'G_IS_DBUS_PROXY (proxy)' failed
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=907718 Bug ID: 907718 Summary: NetworkManager 'CRITICAL' errors on boot: assertion 'G_TYPE_CHECK_INSTANCE (instance)' & 'G_IS_DBUS_PROXY (proxy)' failed 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: --- on opensuse 13.2, with rpm -qa | grep -i networkmanager NetworkManager-gnome-0.9.10.0-2.2.1.x86_64 NetworkManager-devel-0.9.10.0-3.1.4.x86_64 NetworkManager-0.9.10.0-3.1.4.x86_64 NetworkManager-openvpn-0.9.10.0-2.1.4.x86_64 libNetworkManagerQt1-0.9.8.2-3.1.3.x86_64 typelib-1_0-NetworkManager-1_0-0.9.10.0-3.1.4.x86_64 on boot journalctl -b | egrep -i "networkmanager" Nov 30 12:11:49 laptop014 NetworkManager[960]: <info> NetworkManager (version 0.9.10.0) is starting... Nov 30 12:11:49 laptop014 NetworkManager[960]: <info> Read config: /etc/NetworkManager/NetworkManager.conf Nov 30 12:11:49 laptop014 NetworkManager[960]: <info> WEXT support is enabled Nov 30 12:11:49 laptop014 NetworkManager[960]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn Nov 30 12:11:49 laptop014 NetworkManager[960]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list. Nov 30 12:11:49 laptop014 NetworkManager[960]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Nov 30 12:11:49 laptop014 NetworkManager[960]: <info> new connection /etc/NetworkManager/system-connections/ROAMING !! Nov 30 12:12:15 laptop014 NetworkManager[960]: (NetworkManager:960): GLib-GObject-WARNING **: invalid (NULL) pointer instance !! Nov 30 12:12:15 laptop014 NetworkManager[960]: (NetworkManager:960): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> monitoring kernel firmware directory '/lib/firmware'. !! Nov 30 12:12:15 laptop014 NetworkManager[960]: (NetworkManager:960): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:04:00.0/ieee80211/phy0/rfkill1) (driver ath9k) Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (platform driver acer-wmi) Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> WiFi hardware radio set enabled Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> WWAN hardware radio set disabled Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> WiFi enabled by radio killswitch; enabled by state file Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> WWAN enabled by radio killswitch; disabled by state file Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> WiMAX enabled by radio killswitch; enabled by state file Nov 30 12:12:15 laptop014 NetworkManager[960]: <info> Networking is enabled by state file Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Setting system hostname to 'laptop014.loc' (from system configuration) Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (lo): link connected Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (lo): carrier is ON Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1) Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0 Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): carrier is OFF Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): new Ethernet device (driver: 'atl1c' ifindex: 2) Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): link connected Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): preparing device Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): using nl80211 for WiFi device control Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): driver supports Access Point (AP) mode Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3) Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/2 Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): preparing device Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> wpa_supplicant started Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Auto-activating connection 'Wired@HOME'. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) starting connection 'eth0' Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> ModemManager available in the bus Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): disconnecting for new activation request. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: prepare -> deactivating (reason 'none') [40 110 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: deactivating -> config (reason 'none') [110 50 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> NetworkManager state is now CONNECTED_LOCAL Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> NetworkManager state is now CONNECTED_GLOBAL Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Policy set 'eth0' (eth0) as default for IPv4 routing and DNS. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> Activation (eth0) successful, device activated. Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0) supports 4 scan SSIDs Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): supplicant interface state: starting -> ready Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0): supplicant interface state: ready -> disconnected Nov 30 12:12:15 laptop014.loc NetworkManager[960]: <info> (wlan0) supports 4 scan SSIDs Nov 30 12:12:26 laptop014.loc systemd[1]: Unit NetworkManager-wait-online.service entered failed state. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 915098] New: yast2 does not reinstall the bootloader
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=915098 Bug ID: 915098 Summary: yast2 does not reinstall the bootloader Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: ohering(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I replaced the built-in 1.5TB hard disk with a new 2TB harddisk. The partition content was copied with rsync from the old paritions to the new partitions. I adjusted all relevant settings in /etc/fstab, /etc/grub.conf, /etc/default/grub_installdevice, /boot/grub2/device.map, /etc/sysconfig/bootloader, /etc/default/grub to match the LABEL and /dev/disk/by-* of the new 2TB disk. Then I started yast2 to let it update /boot/grub2/grub.cfg, /boot/grub2/grubenv and to reinstall the bootloader on the 13.1 parition. But all it does is to redo grub.cfg and grubenv. It did not install the bootloader into the root partition. As a result chainloading the given root partition fails. Maybe I just missed the knob to reinstall grub2, instead of just regenerating its runtime config files? Will try again with the Factory partition now. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 916364] New: yast tests need to port to rspec 3.1.x or need to evaluate that
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=916364 Bug ID: 916364 Summary: yast tests need to port to rspec 3.1.x or need to evaluate that Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mlin(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the Staging:B - https://build.opensuse.org/project/show/openSUSE:Factory:Staging:B , that has newer rspec version 3, but yast2-* tests basically unhappy with it, sounds yast tests need to port to adopt with new rspec, or at least to evaluate that. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 908049] New: [13.2, NetworkManager GUI] Duplication of network-records in list
by bugzilla_noreply＠novell.com 19 Mar '18

19 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=908049 Bug ID: 908049 Summary: [13.2, NetworkManager GUI] Duplication of network-records in list 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: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Given: OpenSUSE 13.2, XFCE 4.10, NetworkManager Applet 0.9.8.8 (on 0.9.10.0 is also reproduced), NetworkManager.service is active. /sbin/ifconfig ===== enp0s3 Link encap:Ethernet HWaddr 08:00:27:34:73:18 inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:25800 errors:0 dropped:0 overruns:0 frame:0 TX packets:10022 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:29022540 (27.6 Mb) TX bytes:1183638 (1.1 Mb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:114 errors:0 dropped:0 overruns:0 frame:0 TX packets:114 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6061 (5.9 Kb) TX bytes:6061 (5.9 Kb) ===== Steps to reproduce: 1. Left-click on NM Applet in tray. Displays network-records list: Wired Connections - enp0s3 in section of avaliable connections. 2. Choose Turn Off. 3. Left-click on NM Applet in tray again. Displays 'enp0s3' in section of avaliable connections twice. 4. Choose the first 'enp0s3' in list. Returns "(1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/24' failed in libnm-glib." message, but network became active anyway. 5. Repeat steps 3 and 4, but choose the second 'enp0s3' in list. Network became active without any error-message. 6. Left-click on NM Applet in tray and choose VPN Connections - Set VPN. Displays the windows of available connection. Expand "Ethernet" and see duplication of 'enp0s3' again. I've made the video of reproducing this bug: https://yadi.sk/i/hxCm9D6qd74wC (It's better to save webm-file on disk and run it locally in Firefox). NM Applet has RU-locale, but I tried to describe steps-to-reproduce clearly. -- You are receiving this mail because: You are on the CC list for the bug.

1 6