[Touch-packages] [Bug 1241752] Re: Crash when opening image files larger than 5M (>5M)
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1241752 Title: Crash when opening image files larger than 5M (>5M) Status in cairo package in Ubuntu: Confirmed Bug description: This is similar to the bug reported here: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=710701 However, the crash that is now getting generated is from an entirely different call and file. Specifically, the error is: eog: /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed. Aborted (core dumped) In the message above, I was using eog, but this affects other apps, like gThumb as well. In terms of the environment, I'm using Ubuntu 13.10 on an 64-bit machine, and am using libcairo2-1.12.16. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libcairo2 1.12.16-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 18 11:08:27 2013 InstallationDate: Installed on 2013-04-25 (176 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cairo UpgradeStatus: Upgraded to saucy on 2013-10-15 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1241752/+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 1434986] Re: Not working network connection after boot
** Tags added: xenial -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- 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/network-manager/+bug/1434986/+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 1442044] Re: Ordering processes: networkmanager should wait for kernel'module been activated first before starting
i still get this bug ** Tags added: wily -- 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/1442044 Title: Ordering processes: networkmanager should wait for kernel'module been activated first before starting Status in One Hundred Papercuts: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: Get that journalctl log showing networkmanager starting before the related kernel'module been ready: systemd[1]: Starting Network. systemd[1]: Starting /etc/rc.local Compatibility... NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (lo): link connected NetworkManager[724]: (lo): carrier is ON NetworkManager[724]: (lo): new Generic device (driver: 'unknown' ifindex: 1) NetworkManager[724]: (lo): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth0): carrier is OFF NetworkManager[724]: (eth0): new Ethernet device (driver: 'sky2' ifindex: 2) NetworkManager[724]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[724]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[724]: (eth0): preparing device NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth1): carrier is OFF NetworkManager[724]: (eth1): new Ethernet device (driver: 'sky2' ifindex: 3) NetworkManager[724]: (eth1): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager[724]: (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] kernel: sky2 :04:00.0 eth0: enabling interface kernel: sky2 :03:00.0 eth1: enabling interface NetworkManager[724]: (eth1): preparing device NetworkManager[724]: urfkill disappeared from the bus that mobo have eth0 & eth1 ports, but only eth1 is used. As the last lines logged, networworkmanager is able to be loaded when the module sky2 is enabled. network-manager 0.9.10.0-4ubuntu13 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:41:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1442044/+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 1442044] Re: Ordering processes: networkmanager should wait for kernel'module been activated first before starting
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1518681 -- 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/1442044 Title: Ordering processes: networkmanager should wait for kernel'module been activated first before starting Status in One Hundred Papercuts: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: Get that journalctl log showing networkmanager starting before the related kernel'module been ready: systemd[1]: Starting Network. systemd[1]: Starting /etc/rc.local Compatibility... NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (lo): link connected NetworkManager[724]: (lo): carrier is ON NetworkManager[724]: (lo): new Generic device (driver: 'unknown' ifindex: 1) NetworkManager[724]: (lo): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth0): carrier is OFF NetworkManager[724]: (eth0): new Ethernet device (driver: 'sky2' ifindex: 2) NetworkManager[724]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[724]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[724]: (eth0): preparing device NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth1): carrier is OFF NetworkManager[724]: (eth1): new Ethernet device (driver: 'sky2' ifindex: 3) NetworkManager[724]: (eth1): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager[724]: (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] kernel: sky2 :04:00.0 eth0: enabling interface kernel: sky2 :03:00.0 eth1: enabling interface NetworkManager[724]: (eth1): preparing device NetworkManager[724]: urfkill disappeared from the bus that mobo have eth0 & eth1 ports, but only eth1 is used. As the last lines logged, networworkmanager is able to be loaded when the module sky2 is enabled. network-manager 0.9.10.0-4ubuntu13 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:41:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1442044/+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 1434986] Re: Not working network connection after boot
I get this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- 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/network-manager/+bug/1434986/+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 1518681] [NEW] NM failed to initialize WiFi driver (after boot/ return from suspend)
Public bug reported: Since 15.10 my network is not working because of this bug. I got this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. Only workaround: sudo systemctl restart network-manager.service ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 22 11:23:48 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-11-21 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev wlxf81a67191694 proto static metric 600 169.254.0.0/16 dev wlxf81a67191694 scope link metric 1000 192.168.1.0/24 dev wlxf81a67191694 proto kernel scope link src 192.168.1.126 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxf81a67191694 wifi connected /org/freedesktop/NetworkManager/Devices/2 WG-WLAN c2683c87-f2df-40a9-b40b-d2b4ec6f1d12 /org/freedesktop/NetworkManager/ActiveConnection/0 eno1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1518681 Title: NM failed to initialize WiFi driver (after boot/ return from suspend) Status in network-manager package in Ubuntu: New Bug description: Since 15.10 my network is not working because of this bug. I got this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. Only workaround: sudo systemctl restart network-manager.service ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov
[Touch-packages] [Bug 1518681] Re: NM failed to initialize WiFi driver (after boot/ return from suspend)
This error is in the systemd boot logs: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed -- 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/1518681 Title: NM failed to initialize WiFi driver (after boot/ return from suspend) Status in network-manager package in Ubuntu: New Bug description: Since 15.10 my network is not working because of this bug. I got this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. Only workaround: sudo systemctl restart network-manager.service ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 22 11:23:48 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-11-21 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev wlxf81a67191694 proto static metric 600 169.254.0.0/16 dev wlxf81a67191694 scope link metric 1000 192.168.1.0/24 dev wlxf81a67191694 proto kernel scope link src 192.168.1.126 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxf81a67191694 wifi connected /org/freedesktop/NetworkManager/Devices/2 WG-WLAN c2683c87-f2df-40a9-b40b-d2b4ec6f1d12 /org/freedesktop/NetworkManager/ActiveConnection/0 eno1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- 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/ubuntu/+source/network-manager/+bug/1518681/+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 1424664] Re: no ifupdown configuration found
*** This bug is a duplicate of bug 1447146 *** https://bugs.launchpad.net/bugs/1447146 ** Tags added: wily -- 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/1424664 Title: no ifupdown configuration found Status in network-manager package in Ubuntu: Fix Released Bug description: booted with systemd-sysv found into syslog: NetworkManager[770]: management mode: unmanaged NetworkManager[770]: devices added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0) NetworkManager[770]: device added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0): no ifupdown configuration found. NetworkManager[770]: devices added (path: /sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1) NetworkManager[770]: device added (path: /sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1): no ifupdown configuration found. NetworkManager[770]: devices added (path: /sys/devices/virtual/net/lo, iface: lo) NetworkManager[770]: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. NetworkManager[770]: end _init. NetworkManager[770]: (NetworkManager:770): GLib-CRITICAL **: g_dir_read_name: assertion 'dir != NULL' failed . NetworkManager[770]: (eth1): link connected NetworkManager[770]: (eth1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] NetworkManager[770]: Auto-activating connection 'Wired connection 1'. Feb 23 15:06:39 u32 NetworkManager[770]: Activation (eth1) starting connection 'Wired connection 1' NetworkManager[770]: Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager[770]: Activation (eth1) Stage 1 of 5 (Device Prepare) started... NetworkManager[770]: (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0] NetworkManager[770]: NetworkManager state is now CONNECTING note: only eth1 is used to get stream; so it looks like a race as networkmanager seems working as expected; but what a confusing process: do really need a better design, because that one is a real mess. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-6.6-generic 3.19.0 Uname: Linux 3.19.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Mon Feb 23 15:45:26 2015 IpRoute: default via 192.168.1.1 dev eth1 proto static metric 1024 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.3 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 802-3-ethernet 1424702496 lun. 23 févr. 2015 15:41:36 CET yes no /org/freedesktop/NetworkManager/Settings/0 yes eth1activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected/org/freedesktop/NetworkManager/Devices/2 Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- 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/ubuntu/+source/network-manager/+bug/1424664/+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 1438003] Re: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.
Same bug on wily ** Tags added: wily -- 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/1438003 Title: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm- glib. Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: While attempting to connect to an SSID for the first time, it fails, and I consistently get: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Mar 29 23:08:37 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/4 www.ubuntu.com 71c36534-c491-4479-aa91-9238b10f3945 /org/freedesktop/NetworkManager/ActiveConnection/1 wlan1 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- 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/network-manager/+bug/1438003/+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 1434986] Re: Not working network connection after boot
please fix this, ist very annoying ** Tags added: wily -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- 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/network-manager/+bug/1434986/+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 1489154] Re: NetworkManager does not start / fails to start
the bug is still there -- 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/1489154 Title: NetworkManager does not start / fails to start Status in One Hundred Papercuts: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: Yesterday i did the upgrade to version 1.0.4 of NetworkManger. Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash report. This also fails cause the start of the NetworkManger fails after booting. Trying manually to start with ~$ sudo systemctl start NetworkManager leads that the icon comes up, disappears, comes up, disappears for 3, 4 times and then it's gone forever. ~$ journalctl -xe Aug 26 22:02:34 Wily NetworkManager[1578]: monitoring ifupdown state file '/run/network/ifstate'. Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVxlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVethFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMTunFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMMacvlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMInfinibandFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMGreFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMEthernetFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBridgeFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBondFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMAtmManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWifiFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBluezManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWwanFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so) Aug 26 22:02:34 Wily NetworkManager[1578]: WiFi enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WWAN enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WiMAX enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: Networking is enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): new Ethernet device (carrier: ON, driver: 'e1000', ifindex: 2) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Aug 26 22:02:34 Wily NetworkManager[1578]: keyfile: add connection in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1") Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): created default wired connection 'Kabelnetzwerkverbindung 1' Aug 26 22:02:34 Wily NetworkManager[1578]: urfkill disappeared from the bus Aug 26 22:02:34 Wily NetworkManager[1578]: wpa_supplicant running Aug 26 22:02:34 Wily NetworkManager[1578]: ModemManager available in the bus Aug 26 22:02:34 Wily NetworkManager[1578]: ofono is now available Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemAdded' is invalid for instance Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemRemoved' is invalid for instan Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a sp bffb4890 error 4 in libglib-2.0.so.0.4504.0[b6ec8000+127000] Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Unit entered failed state. Aug 26
[Touch-packages] [Bug 269170] Re: NetworkManager crashed with SIGSEGV in g_main_context_dispatch()
** Tags added: wily -- 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/269170 Title: NetworkManager crashed with SIGSEGV in g_main_context_dispatch() Status in network-manager package in Ubuntu: Invalid Bug description: Binary package hint: network-manager Network Manager Crashes @ boottime, not able to start it ... ProblemType: Crash Architecture: amd64 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/sbin/NetworkManager Gconf: Package: network-manager 0.7~~svn20080908t183521+eni0-0ubuntu2 ProcCmdline: /usr/sbin/NetworkManager ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () ?? () g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/libglib-2.0.so.0 g_main_loop_run () from /usr/lib/libglib-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_main_context_dispatch() Uname: Linux 2.6.27-3-generic x86_64 UserGroups: mythtv WpaSupplicantLog: CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-TERMINATING - signal 15 received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/269170/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
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/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
New
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Released
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with "mmcblkXrpmb" if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 ->
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 -> mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 ->
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 ->
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 ->
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 ->
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 ->
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 ->
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"
For issue 2:
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}"
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
** Tags added: vivid
--
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/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
New
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Released
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with "mmcblkXrpmb" if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 ->
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 -> mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 ->
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 ->
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 ->
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 ->
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 ->
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 ->
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"
For issue 2:
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}"
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
It's also important that you fix the live medium + installer because it
takes a long time to boot up an install ubuntu.
--
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/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Released
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with "mmcblkXrpmb" if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 ->
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 -> mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 ->
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 ->
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 ->
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 ->
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 ->
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 ->
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"
For issue 2:
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}"
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1359729] Re: [System Product Name, Realtek ALC889, Green Headphone Out, Front] Underruns, dropouts or crackling sound
No i changed nothing. This is the default config. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1359729 Title: [System Product Name, Realtek ALC889, Green Headphone Out, Front] Underruns, dropouts or crackling sound Status in “alsa-driver” package in Ubuntu: New Bug description: Crackling sound while playing music etc. With higher cpu utilization, it gets worse. Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vincent1984 F pulseaudio /dev/snd/controlC0: vincent1984 F pulseaudio /dev/snd/pcmC0D0p: vincent1984 F...m pulseaudio CurrentDesktop: Unity Date: Thu Aug 21 14:28:50 2014 InstallationDate: Installed on 2014-08-13 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Internes Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [System Product Name, Realtek ALC889, Green Headphone Out, Front] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Maximus IV GENE-Z dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusIVGENE-Z:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1359729/+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 1359729] [NEW] [System Product Name, Realtek ALC889, Green Headphone Out, Front] Underruns, dropouts or crackling sound
Public bug reported: Crackling sound while playing music etc. With higher cpu utilization, it gets worse. Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vincent1984 F pulseaudio /dev/snd/controlC0: vincent1984 F pulseaudio /dev/snd/pcmC0D0p: vincent1984 F...m pulseaudio CurrentDesktop: Unity Date: Thu Aug 21 14:28:50 2014 InstallationDate: Installed on 2014-08-13 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Internes Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [System Product Name, Realtek ALC889, Green Headphone Out, Front] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Maximus IV GENE-Z dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusIVGENE-Z:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1359729 Title: [System Product Name, Realtek ALC889, Green Headphone Out, Front] Underruns, dropouts or crackling sound Status in “alsa-driver” package in Ubuntu: New Bug description: Crackling sound while playing music etc. With higher cpu utilization, it gets worse. Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vincent1984 F pulseaudio /dev/snd/controlC0: vincent1984 F pulseaudio /dev/snd/pcmC0D0p: vincent1984 F...m pulseaudio CurrentDesktop: Unity Date: Thu Aug 21 14:28:50 2014 InstallationDate: Installed on 2014-08-13 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Internes Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [System Product Name, Realtek ALC889, Green Headphone Out, Front] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Maximus IV GENE-Z dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusIVGENE-Z:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1359729/+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 1345505] Re: lock screen leaks keystrokes to window behind greeter
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1345505 Title: lock screen leaks keystrokes to window behind greeter Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When my machine comes out of suspend, I am shown the unity lockscreen. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: BugDistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1345505/+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
