[Touch-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 Ubuntu Touch seeded 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/~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 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-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 Ubuntu Touch seeded 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/~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 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 Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
