[Touch-packages] [Bug 1904700] Re: Mouse settings not reapplied after reconnect or resume
Indeed, I forgot to point that out: the settings in the configuration panel stay correct: to switch back to 'Right' as the primary button, I have to first select 'Left', so I can then select 'Right' again. I could probably fix it by hooking some xinput commands into the proper udev event, but since it seems to be a regression, I was hoping someone knowledgeable might realize the underlying issue, and come up with a better fix :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1904700 Title: Mouse settings not reapplied after reconnect or resume Status in systemd package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 20.04 and notice that my mouse settings (I mouse lefthanded) are no longer restored/reapplied when I reconnect its usb receiver (gets disconnected due to use of KVM switch) or when resuming (after suspend). I now have to reselect the right button as my primary every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.xonotic.rules 70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules 60-vboxdrv.rules Date: Wed Nov 18 09:12:11 2020 InstallationDate: Installed on 2016-07-01 (1600 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20L7001LMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-14 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001LMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:svnLENOVO:pn20L7001LMH:pvrThinkPadT480s:rvnLENOVO:rn20L7001LMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7001LMH dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904700] [NEW] Mouse settings not reapplied after reconnect or resume
Public bug reported: I upgraded from 18.04 to 20.04 and notice that my mouse settings (I mouse lefthanded) are no longer restored/reapplied when I reconnect its usb receiver (gets disconnected due to use of KVM switch) or when resuming (after suspend). I now have to reselect the right button as my primary every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.xonotic.rules 70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules 60-vboxdrv.rules Date: Wed Nov 18 09:12:11 2020 InstallationDate: Installed on 2016-07-01 (1600 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20L7001LMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-14 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001LMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:svnLENOVO:pn20L7001LMH:pvrThinkPadT480s:rvnLENOVO:rn20L7001LMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7001LMH dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1904700 Title: Mouse settings not reapplied after reconnect or resume Status in systemd package in Ubuntu: New Bug description: I upgraded from 18.04 to 20.04 and notice that my mouse settings (I mouse lefthanded) are no longer restored/reapplied when I reconnect its usb receiver (gets disconnected due to use of KVM switch) or when resuming (after suspend). I now have to reselect the right button as my primary every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.xonotic.rules 70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules 60-vboxdrv.rules Date: Wed Nov 18 09:12:11 2020 InstallationDate: Installed on 2016-07-01 (1600 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20L7001LMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-14 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001LMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET65
[Touch-packages] [Bug 1650666] Re: GVim crashes when opening new tab
Workaround: remove vim-gnome and vim-gtk3, install vim-gtk (which uses gtk). Perhaps vim-gtk3 should specify a dependency on some specific gtk library, which Nicholas Guriev and me are missing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1650666 Title: GVim crashes when opening new tab Status in vim package in Ubuntu: Confirmed Bug description: When I open new tab using :tabnew command, GVim crashes in unity_gtk_menu_section_get_item_attributes function of libunity- gtk3-parser0 package. Steps to reproduce: 1. Run gvim from vim-gtk3 package 2. Type `:tabnew` 3. GVim exits, the window closes Stack trace obtained via gdb: mymedia@comp2:~$ gdb -silent --args gvim -f -u /dev/null -U /dev/null --noplugin Reading symbols from gvim...(no debugging symbols found)...done. gdb$ run Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe986d700 (LWP 11042)] [New Thread 0x7fffe906c700 (LWP 11043)] [New Thread 0x7fffe886b700 (LWP 11044)] (gvim:11038): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= (gint)rarray->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_label: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed Thread 1 "gvim" received signal SIGSEGV, Segmentation fault. unity_gtk_menu_section_get_item_attributes (model=, item_index=, attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130 130 ../../../lib/unity-gtk-menu-section.c: Нет такого файла или каталога. gdb$ backtrace #0 0x7fffe9a82083 in unity_gtk_menu_section_get_item_attributes (model=, item_index=, attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130 #1 0x7653f23c in g_menu_model_real_iterate_item_attributes (model=0x56016160 [UnityGtkMenuSection], item_index=) at ././gio/gmenumodel.c:299 #2 0x76541070 in g_menu_exporter_menu_describe_item (position=position@entry=1, menu=, menu=) at ././gio/gmenuexporter.c:212 #3 0x765414be in g_menu_exporter_menu_items_changed (model=, position=1, removed=0, added=, user_data=0x55ffd4c0) at ././gio/gmenuexporter.c:276 #4 0x7fffee607e18 in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x7fffee60787a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #10 0x7626efaf in (instance=, signal_id=, detail=) at ././gobject/gsignal.c:3447 #6 0x762547ae in g_cclosure_marshal_generic (closure=0x5607fd10, return_gvalue=0x0, n_param_values=, param_values=, invocation_hint=, marshal_data=) at ././gobject/gclosure.c:1490 #7 0x76253f75 in g_closure_invoke (closure=0x5607fd10, return_value=return_value@entry=0x0, n_param_values=4, param_values=param_values@entry=0x7fff9250, invocation_hint=invocation_hint@entry=0x7fff91d0) at ././gobject/gclosure.c:804 #8 0x76265f82 in signal_emit_unlocked_R (node=node@entry=0x55f38af0, detail=detail@entry=0, instance=instance@entry=0x56016160, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff9250) at ././gobject/gsignal.c:3635 #9 0x7626ebcc in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fff9440) at ././gobject/gsignal.c:3391 #14 0x7626efaf in (instance=, signal_id=, detail=) at ././gobject/gsignal.c:3447 #11 0x76253f75 in g_closure_invoke (closure=0x56054e20, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0x7fff96d0, invocation_hint=invocation_hint@entry=0x7fff9650) at ././gobject/gclosure.c:804 #12 0x76265f82 in signal_emit_unlocked_R (node=node@entry=0x55aee490, detail=detai---Type to continue, or q to quit--- l@entry=0, instance=instance@entry=0x55e7b9c0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff96d0) at ././gobject/gsignal.c:3635 #13 0x7626ebcc in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fff98b0) at ././gobject/gsignal.c:3391 #15 0x5575edef in gui_mch_add_menu_item () #16 0x
[Touch-packages] [Bug 1650666] Re: GVim crashes when opening new tab
Just upgraded to Zesty. Experiencing what seems to be this exact problem. $ gdb -silent --args gvim -f -u /dev/null -U /dev/null --noplugin Reading symbols from gvim...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe94cd700 (LWP 22840)] [New Thread 0x7fffe8ccc700 (LWP 22841)] [New Thread 0x7fffe3fff700 (LWP 22842)] [New Thread 0x7fffe0f29700 (LWP 22843)] [New Thread 0x7fffd6582700 (LWP 22844)] [New Thread 0x7fffd5d81700 (LWP 22845)] [New Thread 0x7fffd5580700 (LWP 22847)] [Thread 0x7fffd5580700 (LWP 22847) exited] [Thread 0x7fffe0f29700 (LWP 22843) exited] [Thread 0x7fffd6582700 (LWP 22844) exited] [Thread 0x7fffd5d81700 (LWP 22845) exited] (gvim:22836): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= (gint)rarray->len' failed ** (gvim:22836): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:22836): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:22836): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:22836): CRITICAL **: unity_gtk_menu_item_get_label: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:22836): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed Thread 1 "gvim" received signal SIGSEGV, Segmentation fault. 0x7fffe96e2083 in ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1650666 Title: GVim crashes when opening new tab Status in vim package in Ubuntu: Confirmed Bug description: When I open new tab using :tabnew command, GVim crashes in unity_gtk_menu_section_get_item_attributes function of libunity- gtk3-parser0 package. Steps to reproduce: 1. Run gvim from vim-gtk3 package 2. Type `:tabnew` 3. GVim exits, the window closes Stack trace obtained via gdb: mymedia@comp2:~$ gdb -silent --args gvim -f -u /dev/null -U /dev/null --noplugin Reading symbols from gvim...(no debugging symbols found)...done. gdb$ run Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe986d700 (LWP 11042)] [New Thread 0x7fffe906c700 (LWP 11043)] [New Thread 0x7fffe886b700 (LWP 11044)] (gvim:11038): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= (gint)rarray->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_label: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed Thread 1 "gvim" received signal SIGSEGV, Segmentation fault. unity_gtk_menu_section_get_item_attributes (model=, item_index=, attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130 130 ../../../lib/unity-gtk-menu-section.c: Нет такого файла или каталога. gdb$ backtrace #0 0x7fffe9a82083 in unity_gtk_menu_section_get_item_attributes (model=, item_index=, attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130 #1 0x7653f23c in g_menu_model_real_iterate_item_attributes (model=0x56016160 [UnityGtkMenuSection], item_index=) at ././gio/gmenumodel.c:299 #2 0x76541070 in g_menu_exporter_menu_describe_item (position=position@entry=1, menu=, menu=) at ././gio/gmenuexporter.c:212 #3 0x765414be in g_menu_exporter_menu_items_changed (model=, position=1, removed=0, added=, user_data=0x55ffd4c0) at ././gio/gmenuexporter.c:276 #4 0x7fffee607e18 in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x7fffee60787a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #10 0x7626efaf in (instance=, signal_id=, detail=) at ././gobject/gsignal.c:3447 #6 0x762547ae in g_cclosure_marshal_generic (closure=0x5607fd10, return_gvalue=0x0, n_param_values=, param_values=, invocation_hint=, marshal_data=) at ././gobject/gclosure.c:1490 #7 0x76253f75 in g_closure_invoke (closure=0x5607fd10, return_value=return_value@entry=0x0, n_param_values=4, param_values=param_valu
[Touch-packages] [Bug 1445134] Re: Network manager never scanning for new access points
I'm seeing this as well: after upgrading to 15.04, I sometimes don't get automatically connected to my default network, because it hasn't been found yet. A manual 'sudo iwlist scan' is needed to get it to find the network, upon which it does automatically connect. I installed a fresh copy of 15.04, retaining my home partition. /etc is entirely fresh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445134 Title: Network manager never scanning for new access points Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
