[Touch-packages] [Bug 1510098] Re: /etc/network/interfaces ipv6 static gateway not set
This is still valid on all Ubuntu versions when ifupdown is used, and an RA exists on the network - there is a race in assigning the default gateway. See the associated Debian bug for additional details. ** Bug watch added: Debian Bug tracker #805445 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805445 ** Also affects: ifupdown (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805445 Importance: Unknown Status: Unknown ** Changed in: ifupdown (Ubuntu) Status: Invalid => Confirmed -- 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/1510098 Title: /etc/network/interfaces ipv6 static gateway not set Status in ifupdown package in Ubuntu: Confirmed Status in ifupdown package in Debian: Unknown Bug description: After installing 15.10 ipv6 gateway not set on start up. In 15.04 it worked fine andrej@nikel:~$ cat /etc/network/interfaces auto lo enp4s0 iface lo inet loopback iface enp4s0 inet manual iface enp4s0 inet6 static address :200:8221::--- netmask 64 gateway 198:20- andrej@nikel:~$ ip -6 route ---0:8221::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev lxcbr0 proto kernel metric 256 pref medium fe80::/64 dev docker0 proto kernel metric 256 pref medium 3: enp4s0: mtu 9000 qdisc pfifo_fast state UP group default qlen 1000 link/ether --7:98 brd ff:ff:ff:ff:ff:ff inet 10.0.4.1/8 brd 10.255.255.255 scope global enp4s0 valid_lft forever preferred_lft forever inet6 200:8221::--/64 scope global valid_lft forever preferred_lft forever inet6 -15:17ff:fe9e:b798/64 scope global mngtmpaddr dynamic valid_lft 83024sec preferred_lft 11024sec inet6 fe80::215:17ff:fe9e:b798/64 scope link valid_lft forever preferred_lft forever andrej@nikel:~$ cat /etc/sysctl.conf net.ipv4.conf.default.rp_filter= 1 net.ipv4.conf.all.rp_filter= 1 net.ipv4.tcp_syncookies= 1 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 net.ipv6.conf.enp4s0.use_tempaddr = 2 andrej@nikel:/proc/sys/net/ipv6/conf/enp4s0$ for i in *; do echo -n "$i: " ; cat $i ; done accept_dad: 1 accept_ra: 0 accept_ra_defrtr: 1 accept_ra_from_local: 0 accept_ra_mtu: 1 accept_ra_pinfo: 1 accept_ra_rt_info_max_plen: 0 accept_ra_rtr_pref: 1 accept_redirects: 1 accept_source_route: 0 autoconf: 0 dad_transmits: 1 disable_ipv6: 0 force_mld_version: 0 force_tllao: 0 forwarding: 0 hop_limit: 64 max_addresses: 16 max_desync_factor: 600 mc_forwarding: 0 mldv1_unsolicited_report_interval: 1 mldv2_unsolicited_report_interval: 1000 mtu: 1500 ndisc_notify: 0 proxy_ndp: 0 regen_max_retry: 3 router_probe_interval: 60 router_solicitation_delay: 1 router_solicitation_interval: 4 router_solicitations: 3 cat: stable_secret: Permission denied stable_secret: suppress_frag_ndisc: 1 temp_prefered_lft: 86400 temp_valid_lft: 604800 use_tempaddr: 2 Maybe related: https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1510047 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ifupdown 0.7.54ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 26 14:41:55 2015 JournalErrors: No journal files were found. -- No entries -- SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098/+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 1781699] Re: DHCPv6 server crashes regularly (bionic)
I have the packages in for testing, though repro may take some time to occur organically. I also think it might be prudent to add a Restart =on-failure directive to the systemd units regardless of whether the fix for this issue is effective, so that future bugs don't take down users' networks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in DHCP: Unknown Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Bionic: In Progress Status in isc-dhcp source package in Cosmic: In Progress Status in isc-dhcp source package in Disco: Fix Released Status in isc-dhcp source package in Eoan: Fix Released Status in isc-dhcp package in Debian: New Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1781699/+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 1781699] Re: DHCPv6 server crashes regularly (bionic)
@radek-zajic I'm not running the patch currently, but I only saw that crash while running with the patch. If I rebuild using the patch again I'll grab a stack trace (I've just replaced the machine running DHCP). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp package in Debian: New Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1781699/+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 1781699] Re: DHCPv6 server crashes regularly (bionic)
Yes, the problem is certainly exacerbated by the service not having a Restart parameter, but this needs some real attention. The quick-and- dirty-patch does reduce the crashes, but results in a different crash (albeit less frequently). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp package in Debian: New Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1781699/+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 1485316] Re: dnsmasq breaks DNS, if not used as DNS server
Possible duplicate of #1042275 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1485316 Title: dnsmasq breaks DNS, if not used as DNS server Status in dnsmasq package in Ubuntu: New Bug description: I use dnsmasq mainly as a TFTP/DHCP combination and disable the part of the dns-resolver. So i use port=0 to disable the DNS part. But the init- script always rewrites the resolv.conf, no matter if DNS is actually used. Could you add an option to the defaults-file, which the init-script checks and dependent on this, rewrites the config-file? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1485316/+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 1592386] Re: [SRU] add links for obtaining management and support, fix documentation link in 10-help-text
Advertising commercial products/services in base-files really sucks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1592386 Title: [SRU] add links for obtaining management and support, fix documentation link in 10-help-text Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Bug description: Add links for obtaining management and support in 10-help-text, and fix the documentation link. Should look very simple, concise, and clean, like this: * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage == SRU == [Impact] This impacts command line users of Ubuntu server (and desktop) systems. When logging into an Ubuntu console (tty, ssh), pam displays a dynamically generated MOTD (message of the day). The current message of the day on Ubuntu servers has a broken link for documentation. We need to fix that. We should also add simple, clean, friendly links on how to obtain support and remotely manage the system. [Test Case] Upgrade the base-files package, and then regenerate the MOTD using 'sudo update-motd'. The new motd should be printed to screen. [Regression Potential] None. This change affects one simple shell script in /etc/update- motd.d/10-help-text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1592386/+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 1501041] Re: No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up
I believe this may be a kernel regression. I can repro on 15.04 with sddm by installing any 4.x series kernel, haven't done any bisecting, and can't find anything interesting in dmesg (when I can switch to a vc sucessfully after X starts but fails to output anything), but with a single change from 3.19 to any of the mainline PPA 4.x kernels, the problem is immediately evident, and occasinally CPU locks up (SKL), but only when both GPUs are enabled (I have a BIOS hardware mux that I can use to force Nvidia only, which is what I'm doing currently to have a usable system and avoid recompiling iwl 8260 drivers for 3.19 every kernel update). -- 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/1501041 Title: No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Triaged Status in unity-greeter package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Incomplete Bug description: ** this appears to be that the display is blanked/asleep at greeter & login. Forcing or waiting for screen to blank/sleep then waking up restores display See comments 8 & 10 for further info, demonstrations ** Please note that this bug is being filed on a recent 15.10 Ubuntu image install but from a gnome session In a nutshell - Once nividia drivers are installed & used from nvidia-prime there is no longer a visible display in unity-greeter nor in an ubuntu session once logged in. (a blind log in successfully loads an ubuntu session. Everything in the ubuntu session works fine, there are no errors & all the related logs look ok, there is just no visible display. I can open apps, run commands, copy/create logs, play music, play videos, just no display so has to be done blindly from keyboard. On the other hand if I install gnome-shell & log in (blindly) to a gnome session from greeter then all is well & I get a visible display. The same behaviour is seen on an Xubuntu image install, once nvidia is installed & switched to, no visible display. Again there installing & logging into a gnome session works fine with visible display nvidia driver version doesn't matter, exact same is seen with current 15.10 versions & the one I'm currently using (355) from drivers ppa. ** this appears to be that the display is blanked/asleep at greeter & login. Forcing or waiting for screen to blank/sleep then waking up restores display See comment 8 for further info ** ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-core 2:1.17.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Sep 29 16:15:21 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.2.0-11-generic, x86_64: installed nvidia-355, 355.11, 4.2.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev ff) (prog-if ff) InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150928) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed root=UUID=3712249e-a4c8-4b29-9ffb-f9f9e7d5259a ro quiet splash vt.handoff=7 SourcePackage: xorg-server UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1
[Touch-packages] [Bug 1371833] [NEW] dhclient is unable to parse zero-length option values (breaks DHCPv6)
Public bug reported: Description:Ubuntu 14.04.1 LTS Release:14.04 isc-dhcp-client: Installed: 4.2.4-7ubuntu12 Candidate: 4.2.4-7ubuntu12 Version table: *** 4.2.4-7ubuntu12 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Any option with a zero-length value, ie the common DHCPv6 option: option dhcp6.reconf-accept ; with isc-dhcp-client_4.2.4 produces a parser failure: dhclient: /var/lib/NetworkManager/dhclient6-...-wlan0.lease line 35: semicolon expected. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Affects: dhcp (Fedora) Importance: Unknown Status: Unknown ** Patch added: Patch from Fedora tracker https://bugs.launchpad.net/bugs/1371833/+attachment/4209343/+files/0022-Parse-zero-length-option-values-successfully.patch ** Bug watch added: Red Hat Bugzilla #633318 https://bugzilla.redhat.com/show_bug.cgi?id=633318 ** Also affects: dhcp (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=633318 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1371833 Title: dhclient is unable to parse zero-length option values (breaks DHCPv6) Status in “isc-dhcp” package in Ubuntu: New Status in “dhcp” package in Fedora: Unknown Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 isc-dhcp-client: Installed: 4.2.4-7ubuntu12 Candidate: 4.2.4-7ubuntu12 Version table: *** 4.2.4-7ubuntu12 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Any option with a zero-length value, ie the common DHCPv6 option: option dhcp6.reconf-accept ; with isc-dhcp-client_4.2.4 produces a parser failure: dhclient: /var/lib/NetworkManager/dhclient6-...-wlan0.lease line 35: semicolon expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1371833/+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 1371833] Re: dhclient is unable to parse zero-length option values (breaks DHCPv6)
Patch resolves the issue for me locally -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1371833 Title: dhclient is unable to parse zero-length option values (breaks DHCPv6) Status in “isc-dhcp” package in Ubuntu: New Status in “dhcp” package in Fedora: Unknown Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 isc-dhcp-client: Installed: 4.2.4-7ubuntu12 Candidate: 4.2.4-7ubuntu12 Version table: *** 4.2.4-7ubuntu12 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Any option with a zero-length value, ie the common DHCPv6 option: option dhcp6.reconf-accept ; with isc-dhcp-client_4.2.4 produces a parser failure: dhclient: /var/lib/NetworkManager/dhclient6-...-wlan0.lease line 35: semicolon expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1371833/+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 1255592] Re: IPv6 Automatic, only DHCP configuration results in no default route
*** This bug is a duplicate of bug 1193205 *** https://bugs.launchpad.net/bugs/1193205 ** This bug has been marked a duplicate of bug 1193205 dhcp IPv6 sets accept_ra to 0 and doesn't get IPv6 route -- 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/1255592 Title: IPv6 Automatic, only DHCP configuration results in no default route Status in “network-manager” package in Ubuntu: Triaged Bug description: The local network uses SLAAC configuration (with the OtherConfig-Bit in the RA set) as default configuration for devices. Some devices however should use a different IPv6 address assigned by statefull dhcp. Obviously, the ManagedConfiguration bit in the RA is not set, as this would break the SLAAC clients. When choosing Automatic, only DHCP for IPv6 configuration in the network manager (which translates into method=dhcp or NM_SETTING_IP6_CONFIG_METHOD_DHCP), the IPv6 address and the IPv6 DNS Servers are successfully assigned, but there is no ipv6 default route. This is because NM_SETTING_IP6_CONFIG_METHOD_DHCP reconfigures sysctl to drop all RAs (accept_ra=0), but DHCPv6 still has no option to set the gateway IPv6 address (neither its link-local or globally valid address). So I currently cannot have only some clients use statefull DHCPv6, which is what I want. Solution: either a) add an option to set sysctl accept_ra=1, autoconf=0 ; so the client will not use a SLAAC address but still add a default route based on RA or b) add a gateway option to DHCPv6. This bug is to change network manager so the solution a) gets implemented, as this can be implemented in NetworkManager. Solution b) would need to be implemented in isc-dhcp-client and might need an updated RFC, but would allow for different use cases (i.e. http://www.ietf.org/mail-archive/web/ipv6/current/msg08684.html). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.4 ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51 Uname: Linux 3.2.0-56-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 27 17:25:05 2013 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 141.24.40.126 dev eth0 proto static 141.24.40.64/26 dev eth0 proto kernel scope link src 141.24.40.77 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: lono wireless extensions. eth0 no wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-09-19 (434 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Kabelnetzwerkverbindung 1 a32a6fb7-ed99-432f-acc8-c97cc3834e76 802-3-ethernet1385569506 Mi 27 Nov 2013 17:25:06 CETyes no /org/freedesktop/NetworkManager/Settings/1 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1255592/+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 936712] Re: NetworkManager should put IPv6 DNS servers before IPv4 DNS servers in dnsmasq configuration (and possibly resolv.conf)
Please re-open - this is confirmed broken again in 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/936712 Title: NetworkManager should put IPv6 DNS servers before IPv4 DNS servers in dnsmasq configuration (and possibly resolv.conf) Status in “network-manager” package in Ubuntu: Fix Released Bug description: In cases where you are indeed on a dual-stack network and received DNS information from either SLAAC or DHCPv6, these should be used before any equivalent IPv4 data (usually a fallback/compatibility layer in such environment). As an example, here's my generated /run/nm-dns-dnsmasq.conf on an up to date 12.04 system: server=172.17.20.30 server=172.17.25.30 server=172.16.20.32 server=2001:470:c364:1020:e084:d1ff:fe38:c4f5 server=2001:470:c364:1025:8837:98ff:fe43:90e6 server=2001:470:b4e9:1020:218:51ff:fe5a:9949 The result is that dnsmasq will only use the IPv6 dns servers if all 3 IPv4 dns servers are marked as failed. As dnsmasq is perfectly able to detect and avoid broken DNS servers, favoritizing IPv6 servers shouldn't cause any damage even in environment where the information received by NM is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/936712/+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
