[Touch-packages] [Bug 2018457] Re: [SRU] Enable support for Bobcat Cloud Archive
Hey folks, just curious... Why the https://wiki.ubuntu.com/OpenStack/CloudArchive page doesn't mention Bobcat? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2018457 Title: [SRU] Enable support for Bobcat Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Status in software-properties source package in Mantic: Fix Released Bug description: Please add support for: cloud-archive:bobcat cloud-archive:bobcat-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:bobcat sudo add-apt-repository cloud-archive:bobcat-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2018457/+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 1767314] Re: Ubuntu Bionic vi/vim not working correctly
Any news about this?! The vim is still very bad on Ubuntu 20.04. Any recommendation for a better /etc/vim/* ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly Status in vim package in Ubuntu: Confirmed Bug description: The vim default configuration in Bionic does not match Ubuntu 17.10 nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and the '/' search mode command works differently (pressing enter is required before you can use cursors left/right). For some discussion, please see https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic- not-normal/1028684#1028684 Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+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 1226855] Re: Cannot use open-iscsi inside LXC container
Is this still a problem on Ubuntu 18.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+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 1767314] Re: Ubuntu Bionic vi/vim not working correctly
Thanks! vim on Ubuntu 18.04 is so annoying! lol The workaround is good! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly Status in vim package in Ubuntu: Confirmed Bug description: The vim default configuration in Bionic does not match Ubuntu 17.10 nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and the '/' search mode command works differently (pressing enter is required before you can use cursors left/right). For some discussion, please see https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic- not-normal/1028684#1028684 Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets
Is it possible to reproduce this problem with upstart or sysvinit-core? -- 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/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Confirmed Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: (https://launchpadlibrarian.net/291303059/Screenshot.jpg) This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1579294] Re: Lightdm crash on Xenial after upgrading kernel to 4.4.0-22-generic
Impossible to reproduce it with current versions... ** No longer affects: linux ** No longer affects: lightdm ** Changed in: lightdm (Ubuntu) Status: New => Incomplete ** Changed in: lightdm (Ubuntu) Status: Incomplete => Invalid -- 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/1579294 Title: Lightdm crash on Xenial after upgrading kernel to 4.4.0-22-generic Status in lightdm package in Ubuntu: Invalid Bug description: Guys, I just upgraded Xenial, to kernel 4.4.0-22-generic and Lightdm does not work anymore. A high-resolution message appear, telling me that it is operating in low-resolution mode, Ubuntu Desktop is not accessible anymore. I rebooted back into 4.4.0-21-generic, all good! I'm using Ubuntu 16.04 on a Macbook Pro, 2015. Thanks! Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 7 00:13:25 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-30 (97 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579294/+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 1579294] [NEW] Lightdm crash on Xenial after upgrading kernel to 4.4.0-22-generic
Public bug reported: Guys, I just upgraded Xenial, to kernel 4.4.0-22-generic and Lightdm does not work anymore. A high-resolution message appear, telling me that it is operating in low-resolution mode, Ubuntu Desktop is not accessible anymore. I rebooted back into 4.4.0-21-generic, all good! I'm using Ubuntu 16.04 on a Macbook Pro, 2015. Thanks! Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 7 00:13:25 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-30 (97 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm Importance: Undecided Status: New ** Affects: linux Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Also affects: lightdm Importance: Undecided Status: New ** Also affects: linux Importance: Undecided Status: New -- 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/1579294 Title: Lightdm crash on Xenial after upgrading kernel to 4.4.0-22-generic Status in Light Display Manager: New Status in Linux: New Status in lightdm package in Ubuntu: New Bug description: Guys, I just upgraded Xenial, to kernel 4.4.0-22-generic and Lightdm does not work anymore. A high-resolution message appear, telling me that it is operating in low-resolution mode, Ubuntu Desktop is not accessible anymore. I rebooted back into 4.4.0-21-generic, all good! I'm using Ubuntu 16.04 on a Macbook Pro, 2015. Thanks! Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 7 00:13:25 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-30 (97 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1579294/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
I'm seeing this BUG on most recent Xenial Beta release (updated today). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Status in os-prober package in Debian: Fix Released Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|
[Touch-packages] [Bug 1101825] Re: IPv6 static default route added incorrectly by network-manager
This is fixed on Xenial 16.04! YAY! :-D -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1455967] Re: NM disables accept_ra for an IPv6 connection, where it should enable it!
Fixed on Ubuntu Xenial 16.04 development branch! ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- 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/1455967 Title: NM disables accept_ra for an IPv6 connection, where it should enable it! Status in network-manager package in Ubuntu: Fix Released Bug description: Guys, I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and Network Manager disable the Router Advertisement for my IPv6 connection! My connection settings for both wired and WiFi have: Edit Connection -> Edit Settings -> IPv6 Settings -> Method = Automatic But, take a look: --- root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra 0 root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra 0 --- So, my IPv6 connection doesn't work. I need to manually re-enable it, by running: --- echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra --- Then, my IPv6 works again! Everytime I reconnect to a network, I need to "echo 1 > accept_ra" again... Very annoying. Please, help! Thanks in advance... Cheers! Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 15:02:12 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-15 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 400 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) 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/1455967/+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 1013597] Re: No default route for stateful DHCPv6
So, nobody will look into this anymore (apparently), are we moving to
systemd's networkd (16.04) to "fix" this? I'm so tired of ifupdown...
:-P
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1013597
Title:
No default route for stateful DHCPv6
Status in ifupdown package in Ubuntu:
Fix Released
Status in ifupdown source package in Precise:
Triaged
Bug description:
The default route cannot be provided via DHCPv6, it must be obtained
from router advertisements. However, when using the dhcp method for
inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
will set net.ipv6.conf..accept_ra=0, resulting in no default
route for IPv6. Instead, it should explicitly set accept_ra=1.
A workaround is to set it in a post-up script. However, Linux
apparently only sends router solicitations when the interface is
brought up, so if unsolicited RA:s are infrequent the host will be
without a default route until the next RA.
Another problem is that when bringing the interface down on dual-stack
hosts, there will be a long timeout. This is because bringing down
IPv4 also brings the interface link down, and afterwards dhclient
cannot release the DHCPv6 lease due to the link being down ("RTNETLINK
answers: Cannot assign requested address"). The workaround is to bring
the link back up before bringing IPv6 down.
So the workarounds (which obviously should not be needed) for a dual-
stack dhcp client look like this:
iface eth0 inet dhcp
iface eth0 inet6 dhcp
up sysctl net.ipv6.conf.$IFACE.accept_ra=1
pre-down ip link set dev $IFACE up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1013597/+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 1455967] Re: NM disables accept_ra for an IPv6 connection, where it should enable it!
** Description changed: Guys, I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and Network Manager disable the Router Advertisement for my IPv6 connection! My connection settings for both wired and WiFi have: Edit Connection -> Edit Settings -> IPv6 Settings -> Method = Automatic But, take a look: --- root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra 0 root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra 0 --- So, my IPv6 connection doesn't work. I need to manually re-enable it, by running: --- echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra --- - Then, my IPv6 works again! Everything I reconnect to a network, I need - to "echo 1 > accept_ra" again... Very annoying. + Then, my IPv6 works again! Everytime I reconnect to a network, I need to + "echo 1 > accept_ra" again... Very annoying. Please, help! Thanks in advance... Cheers! Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 15:02:12 2015 EcryptfsInUse: Yes IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2015-05-15 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: - default via 10.0.1.1 dev wlan0 proto static metric 400 - 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 - 169.254.0.0/16 dev wlan0 scope link metric 1000 - 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 + default via 10.0.1.1 dev wlan0 proto static metric 400 + 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 + 169.254.0.0/16 dev wlan0 scope link metric 1000 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. -- 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/1455967 Title: NM disables accept_ra for an IPv6 connection, where it should enable it! Status in network-manager package in Ubuntu: New Bug description: Guys, I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and Network Manager disable the Router Advertisement for my IPv6 connection! My connection settings for both wired and WiFi have: Edit Connection -> Edit Settings -> IPv6 Settings -> Method = Automatic But, take a look: --- root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra 0 root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra 0 --- So, my IPv6 connection doesn't work. I need to manually re-enable it, by running: --- echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra --- Then, my IPv6 works again! Everytime I reconnect to a network, I need to "echo 1 > accept_ra" again... Very annoying. Please, help! Thanks in advance... Cheers! Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 15:02:12 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-15 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 400 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) 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/+sour
[Touch-packages] [Bug 1455967] Re: NM disables accept_ra for an IPv6 connection, where it should enable it!
** Summary changed: - NM disables accept_ra for an IPv6 connection, where it should enabled it! + NM disables accept_ra for an IPv6 connection, where it should enable it! -- 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/1455967 Title: NM disables accept_ra for an IPv6 connection, where it should enable it! Status in network-manager package in Ubuntu: New Bug description: Guys, I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and Network Manager disable the Router Advertisement for my IPv6 connection! My connection settings for both wired and WiFi have: Edit Connection -> Edit Settings -> IPv6 Settings -> Method = Automatic But, take a look: --- root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra 0 root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra 0 --- So, my IPv6 connection doesn't work. I need to manually re-enable it, by running: --- echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra --- Then, my IPv6 works again! Everything I reconnect to a network, I need to "echo 1 > accept_ra" again... Very annoying. Please, help! Thanks in advance... Cheers! Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 15:02:12 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-15 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 400 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) 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/1455967/+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 1455967] Re: NM disables accept_ra for an IPv6 connection, where it should enabled it!
Something is still weird... I created the following NM hook: --- root@ultra:~# cat /etc/NetworkManager/dispatcher.d/pre-up.d/01ipv6ra #! /bin/sh echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/eth0/accept_ra --- But, IPv6 still doesn't work, even after a few reboots...:-/ Other devices of this very same network, have IPv6 working like a charm... But Ubuntu 15.04 doesn't... Sometimes, it works, it is random... -- 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/1455967 Title: NM disables accept_ra for an IPv6 connection, where it should enabled it! Status in network-manager package in Ubuntu: New Bug description: Guys, I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and Network Manager disable the Router Advertisement for my IPv6 connection! My connection settings for both wired and WiFi have: Edit Connection -> Edit Settings -> IPv6 Settings -> Method = Automatic But, take a look: --- root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra 0 root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra 0 --- So, my IPv6 connection doesn't work. I need to manually re-enable it, by running: --- echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra --- Then, my IPv6 works again! Everything I reconnect to a network, I need to "echo 1 > accept_ra" again... Very annoying. Please, help! Thanks in advance... Cheers! Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 15:02:12 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-15 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 400 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) 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/1455967/+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 1455967] [NEW] NM disables accept_ra for an IPv6 connection, where it should enabled it!
Public bug reported: Guys, I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and Network Manager disable the Router Advertisement for my IPv6 connection! My connection settings for both wired and WiFi have: Edit Connection -> Edit Settings -> IPv6 Settings -> Method = Automatic But, take a look: --- root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra 0 root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra 0 --- So, my IPv6 connection doesn't work. I need to manually re-enable it, by running: --- echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra --- Then, my IPv6 works again! Everything I reconnect to a network, I need to "echo 1 > accept_ra" again... Very annoying. Please, help! Thanks in advance... Cheers! Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 15:02:12 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-15 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 400 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) 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 package-from-proposed vivid -- 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/1455967 Title: NM disables accept_ra for an IPv6 connection, where it should enabled it! Status in network-manager package in Ubuntu: New Bug description: Guys, I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and Network Manager disable the Router Advertisement for my IPv6 connection! My connection settings for both wired and WiFi have: Edit Connection -> Edit Settings -> IPv6 Settings -> Method = Automatic But, take a look: --- root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra 0 root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra 0 --- So, my IPv6 connection doesn't work. I need to manually re-enable it, by running: --- echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra --- Then, my IPv6 works again! Everything I reconnect to a network, I need to "echo 1 > accept_ra" again... Very annoying. Please, help! Thanks in advance... Cheers! Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 15:02:12 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-15 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 400 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.36 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) 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/1455967/+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 459730] Re: rsyslog doesn't create /dev/xconsole
This bug is still present in Ubuntu 14.04!
---
May 2 20:50:16 vstuaa-2 rsyslogd: [origin software="rsyslogd"
swVersion="7.4.4" x-pid="20463" x-info="http://www.rsyslog.com";] start
May 2 20:50:16 vstuaa-2 rsyslogd: rsyslogd's groupid changed to 104
May 2 20:50:16 vstuaa-2 rsyslogd: rsyslogd's userid changed to 101
May 2 20:50:16 vstuaa-2 rsyslogd-2039: Could no open output pipe
'/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
---
I'm running Trusty on a KVM Virtual Machine, installed from CD, using
the "Minimul Virtual Machine" flavor.
Come on guys, 6 years and still no fix for this issue? WTF???!!!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
Status in One Hundred Papercuts:
Triaged
Status in rsyslog package in Ubuntu:
Triaged
Bug description:
Binary package hint: rsyslog
Looks like this was missed in the move to upstart.
This function was called in init.d/rsyslog start:
create_xconsole() {
if [ ! -e /dev/xconsole ]
then
mknod -m 640 /dev/xconsole p
chown root:adm /dev/xconsole
[ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
fi
}
I can't find any reference to it now. If this is old school then it should be
re
moved from the config.
rsyslog:
Installed: 4.2.0-2ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+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 1287810] Re: Error at boot: rsyslogd-2039
I seeing the following error at my Ubuntu Trusty, it is a virtual machine (installed from CD, using Minimum Virtual Machine flavor): --- May 2 20:50:16 vstuaa-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="20463" x-info="http://www.rsyslog.com";] start May 2 20:50:16 vstuaa-2 rsyslogd: rsyslogd's groupid changed to 104 May 2 20:50:16 vstuaa-2 rsyslogd: rsyslogd's userid changed to 101 May 2 20:50:16 vstuaa-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ] --- Please guys, fix this! Cheers! Thiago -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1287810 Title: Error at boot: rsyslogd-2039 Status in rsyslog package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 daily build from 3-March Error at boot: rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ] System boots normally but it is annoying seeing this error popup at boot time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 17:18:27 2014 InstallationDate: Installed on 2014-03-03 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140303) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1287810/+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 1431138] Re: [systemd] Unbootable Vivid after poweroutage + file system with errors
BTW, I just upgraded my Vivid running on top of a Macbook Air, with systemd again, it booted really fast! now! Systemd boot isn't slow anymore. I'll try to push my system to a "out of arm" state again, to see what happens. Thanks! -- 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/1431138 Title: [systemd] Unbootable Vivid after poweroutage + file system with errors Status in systemd package in Ubuntu: New Bug description: Guys, I started to use Vivid with systemd yesterday, and today, my system froze due to lack of ram memory (my problem, obviously). I tried to "reboot" it, without success... The reboot command did not succeed. I tried to reboot by clicking on Unity menu, didn't worked either. So, I pressed the power button to turn my machine off. Then, the Ubuntu did not booted anymore... I know that systemd boot takes ages to boot (upstart boots in a 2 seconds) but, this time, 5 minutes passed and nothing. I rebooted my machine again, now, using upstart (Grub -> Advanced Options -> Upstart) and guess what? The plymouth screen (I think), was asking me to "press F" to fix file system errors! That message did not appeared when booting with systemd. Removing "quiet splash" did not helped, I saw only a black screen (when with systemd). Definitively systemd isn't ready for prime time on Ubuntu. I'm using Jessie on another machine, systemd runs just fine there. Regards, Thiago To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431138/+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 1431138] [NEW] [systemd] Unbootable Vivid after poweroutage + file system with errors
Public bug reported: Guys, I started to use Vivid with systemd yesterday, and today, my system froze due to lack of ram memory (my problem, obviously). I tried to "reboot" it, without success... The reboot command did not succeed. I tried to reboot by clicking on Unity menu, didn't worked either. So, I pressed the power button to turn my machine off. Then, the Ubuntu did not booted anymore... I know that systemd boot takes ages to boot (upstart boots in a 2 seconds) but, this time, 5 minutes passed and nothing. I rebooted my machine again, now, using upstart (Grub -> Advanced Options -> Upstart) and guess what? The plymouth screen (I think), was asking me to "press F" to fix file system errors! That message did not appeared when booting with systemd. Removing "quiet splash" did not helped, I saw only a black screen (when with systemd). Definitively systemd isn't ready for prime time on Ubuntu. I'm using Jessie on another machine, systemd runs just fine there. Regards, Thiago ** Affects: systemd (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/1431138 Title: [systemd] Unbootable Vivid after poweroutage + file system with errors Status in systemd package in Ubuntu: New Bug description: Guys, I started to use Vivid with systemd yesterday, and today, my system froze due to lack of ram memory (my problem, obviously). I tried to "reboot" it, without success... The reboot command did not succeed. I tried to reboot by clicking on Unity menu, didn't worked either. So, I pressed the power button to turn my machine off. Then, the Ubuntu did not booted anymore... I know that systemd boot takes ages to boot (upstart boots in a 2 seconds) but, this time, 5 minutes passed and nothing. I rebooted my machine again, now, using upstart (Grub -> Advanced Options -> Upstart) and guess what? The plymouth screen (I think), was asking me to "press F" to fix file system errors! That message did not appeared when booting with systemd. Removing "quiet splash" did not helped, I saw only a black screen (when with systemd). Definitively systemd isn't ready for prime time on Ubuntu. I'm using Jessie on another machine, systemd runs just fine there. Regards, Thiago To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431138/+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 1429143] Re: Slow shutdown after booting with systemd
I just upgraded my Macbook Air running Vivid / OSX. With upstart, it boots in about 2 seconds (SSD disc). With systemd, it takes an eternity to boot! Also, the shutdown is much slower when with systemd = PID1. I prefer upstart, so, I'm removing this systemd-sysv thing out of my site. -- 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/1429143 Title: Slow shutdown after booting with systemd Status in systemd package in Ubuntu: Invalid Bug description: When running vivid booted with systemd kernel, shutdown consistently takes around 90 seconds. With the normal kernel it is about 15 seconds. In the log, shutdown started (from the cog) at 13:50:20, Mar 6th. The purple Ubuntu screen with dots appears after a few seconds and then sits there. It actually powered off at 13:51:55. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-7-generic 3.19.0-7.7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1948 F pulseaudio /dev/snd/controlC1: colinl 1948 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 6 13:54:29 2015 InstallationDate: Installed on 2014-10-21 (135 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 init=/lib/systemd/systemd RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429143/+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 1365752] Re: ubuntu-desktop depends on iBus, which is totally broken
I would like to know why, WHY, for God's sake, that Ubuntu depends on
this totally broken iBus?
Sabotage? I'm starting to believe on this conspiracy theory... :-/
What else can be?!
I'm glad that we still have a choice to remove iBus and use another
solution, like scim, for example...
Out of topic but, can you guys imagine when this systemd-thing starts to
break everything and we have no choice? Crazy times... ;-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1365752
Title:
ubuntu-desktop depends on iBus, which is totally broken
Status in ubuntu-meta package in Ubuntu:
Confirmed
Status in unity-control-center package in Ubuntu:
Confirmed
Status in unity-control-center package in Baltix:
New
Bug description:
Upgrading from Ubuntu 12.04 to 14.04 the package iBus has been
installed in the system and activated by default. This has caused an
amount of pain because it has completely broken the input method
(symptoms: no en-uk keyboard available composite not working, backtick
to be pressed twice). The problems are reported in a number of places;
I've read somewhere I can't remember that Unity has some form of
workaround against ibus but I don't use Unity (using Awesome on some
systems, lubuntu on another one) and other windows managers are
affected.
Even disabling ibus (which has to be done via gnome-language-selector,
instead of the keyboard panel in gnome-control-center, which is an
usability problem that deserves its own bug report) the ibus processes
keep on running. Probably this has no consequence but still there is
no reason to have unwanted running processes. I have no idea where do
these processes start, but I clearly have the idea that they shouldn't
be running where not necessary.
Uninstalling ibus is not straightforward because the ubuntu-desktop
package depends on it. The dependency the core package ubuntu-desktop
on ibus is excessive for a package that is 1) unneeded by many users
and 2) broken for many users.
The best solution to date is to:
ibus exit
sudo mv /usr/lib/ibus{,.bak}
sudo mv /usr/bin/ibus{,.bak}
Please remove the dependency of ubuntu-desktop on ibus and avoid
installing it for european languages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1365752/+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 1101825] Re: IPv6 static default route added incorrectly by network-manager
Hey guys! This problem still exists on Ubuntu Vivid! Come on! Ubuntu Desktop is near useless on a network with IPv6 + SLAAC with Routers in H.A. When the main router dies, the slave router becomes active (radvd) but, all Ubuntu Desktops (Gnome / Unity) doesn't see the new IPv6 router. While Windows, Mac, Ubuntu Servers (without NM) and Enlightenment DE with Econnman are working as expected. Please, fix this! Maybe it is time to bring Network Manager 1.0 to Ubuntu. Right now, on my personal machine, I removed network-manager packages and I'm configuring my IPv6 network directly on /etc/network/interfaces, since NM is useless on an IPv6 + SLAAC network with routers in H.A.. Also, my laptop have Econnman, from Enlightenment project. It works like a charm! But it doesn't have support for proxy settings, then, I'm stucked with manual config.:-/ Thanks, Thiago -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1101825] Re: IPv6 static default route added incorrectly by network-manager
It is unbelievable that this problem was already fixed in `gnome-bugs #692279` and still not fixed here in Ubuntu. This is very, very annoying. Please guys, do something about this. Thanks in advance. - Thiago -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1101825] Re: IPv6 static default route added incorrectly by network-manager
This BUG is still present on Ubuntu 14.10 - upgraded today. -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1101825] Re: IPv6 static default route added incorrectly by network-manager
Guys, This BUG is still present on Ubuntu 14.04.1, look: --- user@desk-1:~$ ip -6 route 2001:129X:2bX:Xfff::/64 dev wlan0 proto kernel metric 256 expires 85937sec fe80::/64 dev wlan0 proto kernel metric 256 default via fe80:::b3ff:fe4b:20f4 dev wlan0 proto static metric 1# WRONG!! default via fe80:::b3ff:fe4b:20f4 dev wlan0 proto ra metric 1024 expires 1337sec --- The first "default" line is definitely wrong. It remains there even after a disabled RA daemon (like in a H.A. for IPv6), which "breaks the IPv6 architecture for router redundancy - as OP said". Trusty needs to be patched ASAP! -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1313774] Re: interfaces man page sucks
BTW, `ifupdown` is terrible to manage IPv6 address, specially when with VLANs... We need a completely new approach to manage IPs on Ubuntu/Debian, the time of `ifupdown` is over. I like the syntax of `interfaces` file but, its implementation (ifupdown) is far from ideal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1313774 Title: interfaces man page sucks Status in “ifupdown” package in Ubuntu: Invalid Bug description: I had a bad time trying to configure wifi on Ubuntu Server 14.04 without graphics installed. 'man interfaces' which appears to be from 2004 doesn't mention wifi and Google returns mostly outdated information on the subject. Apparently /usr/share/doc/wpa_supplicant/README.modes.gz is the place to learn that it's possible to include wifi directives in /etc/interfaces without going online; there is no SEE ALSO man page option. It would be easier if the man page was empty and just said to read the Debian reference manual. It might also be useful if there was a man page with the information contained in README.modes.gz, in my case specifically the wpa-ssid and wpa-psk options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1313774/+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 850566] Re: does not configure ipv6 vlan interfaces due to autoconf sysctl failure
As a great workaround, I stopped using VLAN interfaces like "eth0.X", and now I'm using it like this "vlanX"... It is working better (still no not free of problems). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/850566 Title: does not configure ipv6 vlan interfaces due to autoconf sysctl failure Status in “ifupdown” package in Ubuntu: Fix Released Bug description: upon upgrade to 11.10 the ipv6 vlan interface is not configured correctly, leaves it in a half configured state. ipv4 configured properly, but not ipv6 #/etc/network/interfaces iface eth0.83 inet static address 192.168.83.2 netmask 255.255.255.0 iface eth0.83 inet6 static autoconf 0 address 2002:::53:XXX::: netmask 64 The failure is due to the sysctl calling net.ipv6.conf.eth0.83.autoconf = 0, which is incorrect since the dot is interpreted incorrectly, it should be net.ipv6.conf.eth0/83.autoconf = 0 Fixed in 0.7~beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850566/+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
