[Desktop-packages] [Bug 1464958] Re: chromium-browser does not run in guest account
This is still a problem. I'm having the exact same issue (though on google-chrome-stable-44.0.2403.125-1 ) Adding /opt/google/chrome/chrome Cx - chromium, /opt/google/chrome/chrome-sandbox Cx - chromium, to /etc/apparmor.d/abstractions/lightdm_chromium-browser did not help (I tried that in case it was a matter of yet more filename changes on google's packaging). google-chrome --no-sandbox works around the issue, with obvious usability (manual startup or manual configuration of switch), stability and security drawbacks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1464958 Title: chromium-browser does not run in guest account Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description: In guest account, start chromium browser shows nothing. Start with command line shows error: guest-1qFsXl@home:~$ chromium-browser http://www.google.com Check failed: NamespaceUtils::DenySetgroups() This used to work for months and found failed for few weeks. Version: Ubuntu 14.04 LTS chromium-browser43.0.2357.81-0ubuntu0.14.04.1.1 linux-image-3.13.0-54-generic3.13.0-54.91 --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes Env: 'None' 'None' Load-Avg-1min: 0.28 Load-Processes-Running-Percent: 0.2% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic root=UUID=85a7733c-fbc4-49bf-84ce-02be4c5ba907 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Tags: third-party-packages trusty Uname: Linux 3.13.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: H97M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-14T08:39:14.796369 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1464958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1389798] Re: Using Bluetooth PAN leaves broken resolv.conf
Okay, so now I verified that the nameserver was added to resolv.conf. Then I rechecked before disconnecting and noted that the extra resolv.conf entry had disappeared (without changes to network configuration in the meanwhile). nm-tool reported the correct nameserver address still, and it seemed to work through the local proxy (one presumes). So the generated resolv.conf entry seems both unnecessary and possibly transient, though as said, it has persisted beyond disconnecting the Bluetooth PAN at least two times. Everything working even without the entry indicates that it probably shouldn't be generated at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1389798 Title: Using Bluetooth PAN leaves broken resolv.conf Status in “network-manager” package in Ubuntu: New Bug description: Having paired an Android phone, the network manager menu in Unity displays the GT-I9300 Network appropriately and I can tether over the phone's mobile broadband just fine. However, the PAN's nameserver setting is put directly into /etc/resolv.conf (instead of doing the dnsmasq thing) _and_ is left there, like so, even after disconnecting and connecting to a different (WiFi) network: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.44.1 nameserver 127.0.1.1 (The 127.0.1.1 part isn't there before connecting to WiFi, it is added at that point, but the now-defunct BT PAN nameserver address persists.) This greatly interferes with DNS queries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: Unity Date: Wed Nov 5 19:23:27 2014 IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICE TYPE STATE DBUS-PATH 4C:BC:A5:EC:12:83 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/4 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1389798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1389798] [NEW] Using Bluetooth PAN leaves broken resolv.conf
Public bug reported: Having paired an Android phone, the network manager menu in Unity displays the GT-I9300 Network appropriately and I can tether over the phone's mobile broadband just fine. However, the PAN's nameserver setting is put directly into /etc/resolv.conf (instead of doing the dnsmasq thing) _and_ is left there, like so, even after disconnecting and connecting to a different (WiFi) network: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.44.1 nameserver 127.0.1.1 (The 127.0.1.1 part isn't there before connecting to WiFi, it is added at that point, but the now-defunct BT PAN nameserver address persists.) This greatly interferes with DNS queries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: Unity Date: Wed Nov 5 19:23:27 2014 IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICE TYPE STATE DBUS-PATH 4C:BC:A5:EC:12:83 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/4 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1389798 Title: Using Bluetooth PAN leaves broken resolv.conf Status in “network-manager” package in Ubuntu: New Bug description: Having paired an Android phone, the network manager menu in Unity displays the GT-I9300 Network appropriately and I can tether over the phone's mobile broadband just fine. However, the PAN's nameserver setting is put directly into /etc/resolv.conf (instead of doing the dnsmasq thing) _and_ is left there, like so, even after disconnecting and connecting to a different (WiFi) network: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.44.1 nameserver 127.0.1.1 (The 127.0.1.1 part isn't there before connecting to WiFi, it is added at that point, but the now-defunct BT PAN nameserver address persists.) This greatly interferes with DNS queries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: Unity Date: Wed Nov 5 19:23:27 2014 IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICE TYPE STATE DBUS-PATH 4C:BC:A5:EC:12:83 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/4 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1389798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1298021] Re: Google Chrome (not chromium) won't start in guest session
Confirmed that the bug exists once more. Martyn's fix works. Could that be packaged, perhaps? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298021 Title: Google Chrome (not chromium) won't start in guest session Status in “lightdm” package in Ubuntu: Fix Released Bug description: Related, but not a dupe of bug 577919 Install Google Chrome (not chromium) and switch to a guest session Start chrome from a terminal See the following error:- Failed to move to new PID namespace: Operation not permitted I see these apparmor denials:- [Tue Mar 25 12:51:46 2014] type=1400 audit(1395861131.882:541): apparmor=DENIED operation=capable profile=/usr/lib/lightdm/lightdm-guest-session pid=30034 comm=chrome-sandbox capability=21 capname=sys_admin [Tue Mar 25 12:52:13 2014] type=1400 audit(1395861159.510:542): apparmor=DENIED operation=open profile=/usr/lib/lightdm/lightdm-guest-session name=/proc/30062/oom_score_adj pid=30062 comm=chrome requested_mask=wc denied_mask=wc fsuid=130 ouid=130 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 26 19:08:04 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (634 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-01-20 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1298021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360102] [NEW] Unity device blacklist nonfunctional
Public bug reported: Installing 14.04 in a classroom dual-boot environment, Unity shows icons for the Windows partitions on the launcher, nonfunctional since they require root to mount. Such extraneous icons only serve to confuse the user. Googling, I found out about the com.canonical.Unity.Devices blacklist gsettings entry. I made a script that generates a schema such as this, for internal drives: [com.canonical.Unity.Devices] blacklist=['F236BFEF36BFB349','1A98C11998C0F473','c251a534-47dd-4ecb-a62c-2ced6914ef4a','122357ec-3130-482f-b20e-a4c6522e0873'] Here's the corresponding output of blkid -o list device fs_type labelmount point UUID --- /dev/sda1ntfsSystem (not mounted)F236BFEF36BFB349 /dev/sda2ntfsOSDisk (not mounted)1A98C11998C0F473 /dev/sda3swap swap c251a534-47dd-4ecb-a62c-2ced6914ef4a /dev/sda4ext4 / 122357ec-3130-482f-b20e-a4c6522e0873 I put the file in /usr/share/glib-2.0/schemas and ran glib-compile- schemas on it. The entry _does_ show up in a user's session as evidenced by gsettings get and dconf-editor. dconf-editor also has a documentation line for the entry that indicates that this _should_ indeed prevent the named drives from appearing. However, the icons persist in appearing, even on a clean home directory (no old user configuration to confuse anything). Can this be fixed, or is there another way to prevent Unity from showing local internal drives to users who have no means of accessing them? Disabling drive icons altogether would be suboptimal but perhaps workable too, though it'd be preferable that the removable drives would get icons. However, even removing unity://devices from com.canonical.Unity.Launcher favorites didn't prevent the icons from appearing (though the same edit did succeed in removing other application icons, so the setting itself went through properly). lsb_release -rd is: Description:Ubuntu 14.04.1 LTS Release:14.04 ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1360102 Title: Unity device blacklist nonfunctional Status in “unity” package in Ubuntu: New Bug description: Installing 14.04 in a classroom dual-boot environment, Unity shows icons for the Windows partitions on the launcher, nonfunctional since they require root to mount. Such extraneous icons only serve to confuse the user. Googling, I found out about the com.canonical.Unity.Devices blacklist gsettings entry. I made a script that generates a schema such as this, for internal drives: [com.canonical.Unity.Devices] blacklist=['F236BFEF36BFB349','1A98C11998C0F473','c251a534-47dd-4ecb-a62c-2ced6914ef4a','122357ec-3130-482f-b20e-a4c6522e0873'] Here's the corresponding output of blkid -o list device fs_type labelmount point UUID --- /dev/sda1ntfsSystem (not mounted)F236BFEF36BFB349 /dev/sda2ntfsOSDisk (not mounted)1A98C11998C0F473 /dev/sda3swap swap c251a534-47dd-4ecb-a62c-2ced6914ef4a /dev/sda4ext4 / 122357ec-3130-482f-b20e-a4c6522e0873 I put the file in /usr/share/glib-2.0/schemas and ran glib-compile- schemas on it. The entry _does_ show up in a user's session as evidenced by gsettings get and dconf-editor. dconf-editor also has a documentation line for the entry that indicates that this _should_ indeed prevent the named drives from appearing. However, the icons persist in appearing, even on a clean home directory (no old user configuration to confuse anything). Can this be fixed, or is there another way to prevent Unity from showing local internal drives to users who have no means of accessing them? Disabling drive icons altogether would be suboptimal but perhaps workable too, though it'd be preferable that the removable drives would get icons. However, even removing unity://devices from com.canonical.Unity.Launcher favorites didn't prevent the icons from appearing (though the same edit did succeed in removing other application icons, so the setting itself went through properly). lsb_release -rd is: Description: Ubuntu 14.04.1 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1360102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1176327] Re: Compiz crashes on a daily basis, will not restart
Changing package to libgl1-mesa-dri due to the xorg-edgers driver upgrade mentioned before eliminating the issue. I am not positive if I should chalk it up to xserver-xorg-video-radeon instead but I get the feeling it's an OpenGL side issue since Compiz does render through that. Compiz has now run with the edgers driver without crashes for a week or so for me (a duration unthinkable with the original raring driver), though the edgers driver does have the occasional freeze (which it recovers from), especially when a large window is being created. I am still open to trying more conservative upgrades to the original raring packages. I can also downgrade from the edgers repository and run specific tests on the original raring driver on request. (Still not sure why compiz had problems restarting after a crash though.) ** Package changed: compiz (Ubuntu) = mesa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1176327 Title: Compiz crashes on a daily basis, will not restart Status in “mesa” package in Ubuntu: Confirmed Bug description: After upgrading to 13.04, compiz crashes pretty much on a daily basis. At least once on making mplayer go full screen, and sometimes even when the computer is just left alone (possibly triggered by screensaver). Unity panels disappear as well. I generally have a leftover undecorated terminal to try to do recovery from, but compiz won't even restart, I have to kill my session and start over from scratch (a reboot is not necessary, however). Killing the leftover decorator and *unity* and *indicator* processes had no effect in restarting attempts. Pending a solution, even a hint what needs cleaning up for a clean restart of compiz without having to exit the whole session would be welcome. IIRC I tried to start metacity once and it started, though was less than fully useful. Here's what comes out when trying to restart it; at first it seems to think that Unity isn't hardware supported, but it is, on the radeon driver: OpenGL renderer string: Gallium 0.4 on AMD RV770. That'll get cleared up on killing the decorator. Incidentally, the panel crash indicator asked if I want to report this but then just sat there for a while and quit without doing anything... This is manually through ubuntu-bug. mjr@phantom:~$ compiz [1] 21295 mjr@phantom:~$ compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile : unity compiz (core) - Info: Loading plugin: composite compiz (core) - Info: Starting plugin: composite compiz (core) - Info: Loading plugin: opengl compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). compiz (core) - Info: Unity is fully supported by your hardware. compiz (core) - Info: Starting plugin: opengl compiz (core) - Info: Loading plugin: decor compiz (core) - Info: Starting plugin: decor compiz (core) - Info: Loading plugin: gnomecompat compiz (core) - Info: Starting plugin: gnomecompat compiz (core) - Info: Loading plugin: grid compiz (core) - Info: Starting plugin: grid compiz (core) - Info: Loading plugin: place compiz (core) - Info: Starting plugin: place compiz (core) - Info: Loading plugin: imgpng compiz (core) - Info: Starting plugin: imgpng compiz (core) - Info: Loading plugin: compiztoolbox compiz (core) - Info: Starting plugin: compiztoolbox compiz (core) - Info: Loading plugin: copytex compiz (core) - Info: Starting plugin: copytex compiz (core) - Info: Loading plugin: session compiz (core) - Info: Starting plugin: session compiz (core) - Info: Loading plugin: mousepoll compiz (core) - Info: Starting plugin: mousepoll compiz (core) - Info: Loading plugin: move compiz (core) - Info: Starting plugin: move compiz (core) - Info: Loading plugin: regex compiz (core) - Info: Starting plugin: regex compiz (core) - Info: Loading plugin: snap compiz (core) - Info: Starting plugin: snap compiz (core) - Info: Loading plugin: resize compiz (core) - Info: Starting plugin: resize compiz (core) - Info: Loading plugin: vpswitch compiz (core) - Info: Starting plugin: vpswitch compiz (core) - Info: Loading plugin: animation compiz (core) - Info: Starting plugin: animation compiz (core) - Info: Loading plugin: unitymtgrabhandles compiz (core) - Info: Starting plugin: unitymtgrabhandles compiz (core) - Info: Loading plugin: workarounds compiz (core) - Info: Starting plugin: workarounds compiz (core) - Info: Loading plugin: wall compiz (core) - Info: Starting plugin: wall compiz (core) - Info: Loading plugin: expo compiz (core) - Info:
[Desktop-packages] [Bug 1050434] Re: NM fails to make UMTS connection; deleting and recreating the connection configuration fixes it
As far as I can see, this doesn't happen anymore. (Artifact of using Xubuntu desktop at the time? Seems unlikely though.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1050434 Title: NM fails to make UMTS connection; deleting and recreating the connection configuration fixes it Status in “network-manager” package in Ubuntu: New Bug description: On occasion, network-manager fails to get an UMTS network connection, and quickly refuses all future attempts to use the connection. Reconfiguration of the interface (exactly the same as before) will fix it; seems like nm may mistake a transient error for a permanent one or something. Even removing the connection description from /etc/NetworkManager/system-connections and copying the exact same file back, and attempting a reconnect will fix this particular situation. (This is what I did also in this instance.) Relevant syslog snippet around the attempt to connect to my provider, Saunalahti: Sep 13 16:29:14 t420s-4 NetworkManager[1278]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.6/net/usb0, iface: usb0) Sep 13 16:29:14 t420s-4 modem-manager[1199]: info (tty/ttyACM0): released by modem /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 Sep 13 16:29:14 t420s-4 modem-manager[1199]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered - disabled) Sep 13 16:29:14 t420s-4 modem-manager[1199]: info (ttyACM2) closing serial port... Sep 13 16:29:14 t420s-4 modem-manager[1199]: info (ttyACM2) serial port closed Sep 13 16:29:14 t420s-4 anacron[13863]: Anacron 2.3 started on 2012-09-13 Sep 13 16:29:14 t420s-4 anacron[13863]: Normal exit (0 jobs run) Sep 13 16:29:14 t420s-4 kernel: [24385.860392] usb 2-1.4: new high-speed USB device number 8 using ehci_hcd Sep 13 16:29:14 t420s-4 kernel: [24385.998849] generic-usb: probe of 0003:0BDB:1912.0007 failed with error -71 Sep 13 16:29:14 t420s-4 mtp-probe: checking bus 2, device 8: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 Sep 13 16:29:14 t420s-4 mtp-probe: bus: 2, device: 8 was not an MTP device Sep 13 16:29:14 t420s-4 kernel: [24386.208526] usb 2-1.4: USB disconnect, device number 8 Sep 13 16:29:15 t420s-4 kernel: [24387.176121] usb 2-1.4: new high-speed USB device number 9 using ehci_hcd Sep 13 16:29:15 t420s-4 kernel: [24387.308285] cdc_acm 2-1.4:1.1: ttyACM0: USB ACM device Sep 13 16:29:15 t420s-4 kernel: [24387.311154] cdc_acm 2-1.4:1.3: ttyACM1: USB ACM device Sep 13 16:29:15 t420s-4 kernel: [24387.319164] cdc_wdm 2-1.4:1.5: cdc-wdm0: USB WDM device Sep 13 16:29:15 t420s-4 kernel: [24387.334945] usb 2-1.4: MAC-Address: 02:80:37:ec:02:00 Sep 13 16:29:15 t420s-4 kernel: [24387.335134] cdc_ncm 2-1.4:1.6: usb0: register 'cdc_ncm' at usb-:00:1d.0-1.4, CDC NCM, 02:80:37:ec:02:00 Sep 13 16:29:15 t420s-4 kernel: [24387.335731] cdc_wdm 2-1.4:1.8: cdc-wdm1: USB WDM device Sep 13 16:29:15 t420s-4 kernel: [24387.336151] cdc_acm 2-1.4:1.9: ttyACM2: USB ACM device Sep 13 16:29:15 t420s-4 mtp-probe: checking bus 2, device 9: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 Sep 13 16:29:15 t420s-4 mtp-probe: bus: 2, device: 9 was not an MTP device Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (ttyACM0) opening serial port... Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (ttyACM2) opening serial port... Sep 13 16:29:15 t420s-4 NetworkManager[1278]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.6/net/usb0, iface: usb0) Sep 13 16:29:15 t420s-4 NetworkManager[1278]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.6/net/usb0, iface: usb0): no ifupdown configuration found. Sep 13 16:29:15 t420s-4 NetworkManager[1278]: warn failed to allocate link cache: (-10) Operation not supported Sep 13 16:29:15 t420s-4 NetworkManager[1278]: info (usb0): carrier is OFF Sep 13 16:29:15 t420s-4 NetworkManager[1278]: error [1347542955.958115] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (usb0): unable to read permanent MAC address (error 0) Sep 13 16:29:15 t420s-4 NetworkManager[1278]: info (usb0): new Ethernet device (driver: 'cdc_ncm' ifindex: 80) Sep 13 16:29:15 t420s-4 NetworkManager[1278]: info (usb0): exported as /org/freedesktop/NetworkManager/Devices/4 Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (ttyACM1) opening serial port... Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (Ericsson MBM): GSM modem /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 claimed port usb0 Sep 13 16:29:16 t420s-4 modem-manager[1199]: info (ttyACM0) closing serial port... Sep 13 16:29:16 t420s-4 modem-manager[1199]: info (ttyACM0) serial port closed Sep 13 16:29:16
[Desktop-packages] [Bug 1084956] [NEW] nm-applet goes unresponsive randomly
Public bug reported: nm-applet sometimes goes unresponsive, generally after a couple of days of intermittent laptop use (including suspends). The menu does come up, but choosing an interface to activate doesn't do anything for either wifi or mobile networks. Not even a visible attempt is made to connect, nor is a failure reported. Killing nm-applet and restarting it is a functional workaround (and thus is also logging out and back in), so it's clearly the applet and not network manager itself that's the problem. While there is a workaround, this is likely to be very frustrating for users, especially those less likely to come up with the kill/restart workaround. Using the standard Unity interface, if that matters. mjrauhal@t420s-4:~$ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 mjrauhal@t420s-4:~$ apt-cache policy network-manager-gnome network-manager-gnome: Installed: 0.9.4.1-0ubuntu2 Candidate: 0.9.4.1-0ubuntu2 Version table: *** 0.9.4.1-0ubuntu2 0 500 http://cubbli.cs.helsinki.fi/mirror/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1084956 Title: nm-applet goes unresponsive randomly Status in “network-manager-applet” package in Ubuntu: New Bug description: nm-applet sometimes goes unresponsive, generally after a couple of days of intermittent laptop use (including suspends). The menu does come up, but choosing an interface to activate doesn't do anything for either wifi or mobile networks. Not even a visible attempt is made to connect, nor is a failure reported. Killing nm-applet and restarting it is a functional workaround (and thus is also logging out and back in), so it's clearly the applet and not network manager itself that's the problem. While there is a workaround, this is likely to be very frustrating for users, especially those less likely to come up with the kill/restart workaround. Using the standard Unity interface, if that matters. mjrauhal@t420s-4:~$ lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 mjrauhal@t420s-4:~$ apt-cache policy network-manager-gnome network-manager-gnome: Installed: 0.9.4.1-0ubuntu2 Candidate: 0.9.4.1-0ubuntu2 Version table: *** 0.9.4.1-0ubuntu2 0 500 http://cubbli.cs.helsinki.fi/mirror/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1084956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050434] Re: UMTS connections require occasional reconfiguring
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1050434 Title: UMTS connections require occasional reconfiguring Status in “network-manager” package in Ubuntu: New Bug description: On occasion, network-manager fails to get an UMTS network connection, and quickly refuses all future attempts to use the connection. Reconfiguration of the interface (exactly the same as before) will fix it; seems like nm may mistake a transient error for a permanent one or something. Even removing the connection description from /etc/NetworkManager/system-connections and copying the exact same file back, and attempting a reconnect will fix this particular situation. (This is what I did also in this instance.) Relevant syslog snippet around the attempt to connect to my provider, Saunalahti: Sep 13 16:29:14 t420s-4 NetworkManager[1278]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.6/net/usb0, iface: usb0) Sep 13 16:29:14 t420s-4 modem-manager[1199]: info (tty/ttyACM0): released by modem /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 Sep 13 16:29:14 t420s-4 modem-manager[1199]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered - disabled) Sep 13 16:29:14 t420s-4 modem-manager[1199]: info (ttyACM2) closing serial port... Sep 13 16:29:14 t420s-4 modem-manager[1199]: info (ttyACM2) serial port closed Sep 13 16:29:14 t420s-4 anacron[13863]: Anacron 2.3 started on 2012-09-13 Sep 13 16:29:14 t420s-4 anacron[13863]: Normal exit (0 jobs run) Sep 13 16:29:14 t420s-4 kernel: [24385.860392] usb 2-1.4: new high-speed USB device number 8 using ehci_hcd Sep 13 16:29:14 t420s-4 kernel: [24385.998849] generic-usb: probe of 0003:0BDB:1912.0007 failed with error -71 Sep 13 16:29:14 t420s-4 mtp-probe: checking bus 2, device 8: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 Sep 13 16:29:14 t420s-4 mtp-probe: bus: 2, device: 8 was not an MTP device Sep 13 16:29:14 t420s-4 kernel: [24386.208526] usb 2-1.4: USB disconnect, device number 8 Sep 13 16:29:15 t420s-4 kernel: [24387.176121] usb 2-1.4: new high-speed USB device number 9 using ehci_hcd Sep 13 16:29:15 t420s-4 kernel: [24387.308285] cdc_acm 2-1.4:1.1: ttyACM0: USB ACM device Sep 13 16:29:15 t420s-4 kernel: [24387.311154] cdc_acm 2-1.4:1.3: ttyACM1: USB ACM device Sep 13 16:29:15 t420s-4 kernel: [24387.319164] cdc_wdm 2-1.4:1.5: cdc-wdm0: USB WDM device Sep 13 16:29:15 t420s-4 kernel: [24387.334945] usb 2-1.4: MAC-Address: 02:80:37:ec:02:00 Sep 13 16:29:15 t420s-4 kernel: [24387.335134] cdc_ncm 2-1.4:1.6: usb0: register 'cdc_ncm' at usb-:00:1d.0-1.4, CDC NCM, 02:80:37:ec:02:00 Sep 13 16:29:15 t420s-4 kernel: [24387.335731] cdc_wdm 2-1.4:1.8: cdc-wdm1: USB WDM device Sep 13 16:29:15 t420s-4 kernel: [24387.336151] cdc_acm 2-1.4:1.9: ttyACM2: USB ACM device Sep 13 16:29:15 t420s-4 mtp-probe: checking bus 2, device 9: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 Sep 13 16:29:15 t420s-4 mtp-probe: bus: 2, device: 9 was not an MTP device Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (ttyACM0) opening serial port... Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (ttyACM2) opening serial port... Sep 13 16:29:15 t420s-4 NetworkManager[1278]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.6/net/usb0, iface: usb0) Sep 13 16:29:15 t420s-4 NetworkManager[1278]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.6/net/usb0, iface: usb0): no ifupdown configuration found. Sep 13 16:29:15 t420s-4 NetworkManager[1278]: warn failed to allocate link cache: (-10) Operation not supported Sep 13 16:29:15 t420s-4 NetworkManager[1278]: info (usb0): carrier is OFF Sep 13 16:29:15 t420s-4 NetworkManager[1278]: error [1347542955.958115] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (usb0): unable to read permanent MAC address (error 0) Sep 13 16:29:15 t420s-4 NetworkManager[1278]: info (usb0): new Ethernet device (driver: 'cdc_ncm' ifindex: 80) Sep 13 16:29:15 t420s-4 NetworkManager[1278]: info (usb0): exported as /org/freedesktop/NetworkManager/Devices/4 Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (ttyACM1) opening serial port... Sep 13 16:29:15 t420s-4 modem-manager[1199]: info (Ericsson MBM): GSM modem /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 claimed port usb0 Sep 13 16:29:16 t420s-4 modem-manager[1199]: info (ttyACM0) closing serial port... Sep 13 16:29:16 t420s-4 modem-manager[1199]: info (ttyACM0) serial port closed Sep 13 16:29:16 t420s-4 modem-manager[1199]: info (ttyACM0) opening serial port... Sep 13 16:29:16 t420s-4 modem-manager[1199]: info (Ericsson MBM): GSM modem
