Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

I'm sorry @hrvooje - it worked for me.
But I have now risked upgrading my main laptop from 16.10 to 17.04 and it
appears to be working perfectly without the necessity for tweaks or
workaronds or alternative of 8.8.8.8 , etc, etc. I guess the latest in-situ
upgrade contained its own bugfix.
David

On 24 April 2017 at 18:24, hrvooje <1654...@bugs.launchpad.net> wrote:

> @David I did what you told and it happend to me again. However, my
> message from sudo systemd-resolved returned REFUSED error with that
> domain I tried to open. My systemd is 232-21ubuntu3 and when IP address
> is set to automatic it why it didn't try different one when first
> refused?
>
> Poettering fixed this here
> https://github.com/systemd/systemd/issues/4264
>
> ** Bug watch added: github.com/systemd/systemd/issues #4264
>https://github.com/systemd/systemd/issues/4264
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1654918
>
> Title:
>   No Internet access with default of  Automatic (DHCP)
>
> Status in Linux:
>   New
> Status in NetworkManager:
>   New
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Fresh 17.04 install, wireless router connects without any issue but
> there is no internet connection/access.
>   This continues thru disconnecting, reconnecting, rebooting ect, Nothing..
>
>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
> only & manually add Google DNS nameservers: then internet is enabled.
> screen attached
>   Note this also affects ethernet, not just wireless
>   Hardware is:
>   description: Wireless interface
>  product: Wireless 7260
>  vendor: Intel Corporation
>  physical id: 0
>  bus info: pci@:08:00.0
>  logical name: wlp8s0
>  version: 73
>  serial: 
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
>  configuration: broadcast=yes driver=iwlwifi
> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>  resources: irq:32 memory:c240-c2401fff
>
>   To note: this hardware works perfectly in 14.04 > 16.04
>   Add. note; issue doesn't arise with 4.11.x kernel
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: network-manager 1.4.2-2ubuntu4
>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>   Uname: Linux 4.9.0-11-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jan  8 22:08:26 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>   IpRoute:
>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
> metric 600
>   NetworkManager.conf:
>[main]
>plugins=ifupdown,keyfile
>
>[ifupdown]
>managed=false
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-dev:
>DEVICE  TYPE  STATEDBUS-PATH
>   CONNECTION  CON-UUID  CON-PATH
>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  /org/freedesktop/
> NetworkManager/ActiveConnection/0
>enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
> --  ----
>lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
> --  ----
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.4.2connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

OK - complete solution/workaround is to be found here... But you must read
the whole lot before doing anything at all because the last edit makes the
first part redundant...
http://www.hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues/
The issue involves systemd within which the developers have turned on some
dns security aspect which had been turned off in earlier versions of
Ubuntu. But the author finds a way for users to keep it turned on but to
solve the problem at the same time via something called 'unbound'.
Anyway - read and try. Worked for me.
Best
David

On 23 April 2017 at 22:57, hrvooje <1654...@bugs.launchpad.net> wrote:

> For me:
> work-wire OK
> work-wifi OK
> home-wifi FAIL
> I don't use a wire at home so I didn't try
>
> Then I do sudo service network-manager restart and I can surf again. In
> that time while I can't sufr the internet I get ping 8.8.8.8 and other
> IP's. Torrent dowloading is also working in that time. So, this is
> obviously a dns and network-manager issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1654918
>
> Title:
>   No Internet access with default of  Automatic (DHCP)
>
> Status in Linux:
>   New
> Status in NetworkManager:
>   New
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Fresh 17.04 install, wireless router connects without any issue but
> there is no internet connection/access.
>   This continues thru disconnecting, reconnecting, rebooting ect, Nothing..
>
>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
> only & manually add Google DNS nameservers: then internet is enabled.
> screen attached
>   Note this also affects ethernet, not just wireless
>   Hardware is:
>   description: Wireless interface
>  product: Wireless 7260
>  vendor: Intel Corporation
>  physical id: 0
>  bus info: pci@:08:00.0
>  logical name: wlp8s0
>  version: 73
>  serial: 
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
>  configuration: broadcast=yes driver=iwlwifi
> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>  resources: irq:32 memory:c240-c2401fff
>
>   To note: this hardware works perfectly in 14.04 > 16.04
>   Add. note; issue doesn't arise with 4.11.x kernel
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: network-manager 1.4.2-2ubuntu4
>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>   Uname: Linux 4.9.0-11-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jan  8 22:08:26 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>   IpRoute:
>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
> metric 600
>   NetworkManager.conf:
>[main]
>plugins=ifupdown,keyfile
>
>[ifupdown]
>managed=false
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-dev:
>DEVICE  TYPE  STATEDBUS-PATH
>   CONNECTION  CON-UUID  CON-PATH
>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  /org/freedesktop/
> NetworkManager/ActiveConnection/0
>enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
> --  ----
>lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
> --  ----
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.4.2connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

Temporary workaround which seems to work most of the time (though, 
'timing' - as you are suggesting - sometimes is an issue, requiring a 
couple of 'sudo apt update' attempts in Terminal to successfully resolve 
all repositories) enter 8.8.8.8 (Google's DNS) into the relevant 
'alternate DNS' in IPV4 box. I agree, it is most puzzling how the issue 
seems to come and go, despite (eventually) successfully receiving and 
deploying all updates to date . I'm still not confident enough to move 
from 16.10 to 17.04 on my main machine.
(Sigh...)
David

On 22/04/2017 16:46, Jacek Misiurewicz wrote:
> Regarding my previous post (#24)...
>
>   Seems that everything is back to abnormal. After logging out and re-
> logging again bug was back. This time soft disconnecting and
> reconnecting network (from NManager) helped to regain access to network,
> but this was not always the remedy.
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

On second thoughts, despite 'dnsutils' and 'bind9-host' updates 17.04 is
still buggy on my two Toshiba laptops (one ancient, one less so). Can take
up to three attempts to resolve all repositories with 'sudo apt update'
after boot. Alternatively, on first attempts, browsers (Firefox, Chromium)
do not connect to sites - but then, after a while do so. Bizarre.
Been using Ubuntu since 9.x - never encountered this irritation before. So
it's not because I'm using USB stick installations. However, I am, as ever
using copper wire at 16-20 Mbit/s - but that's never beena problem before...
To actually receive the updates I needed to use the Google DNS 8.8.8.8 on
IPV4 - thereafter deleting this.
I'm now using two (full install, not 'live) USB sticks with 17.04 booting
to them on either laptop - but am holding off upgrading from 16.10 on my
main (newer uefi) machine until the issue is fully resolved.

On 18 April 2017 at 10:22, David Oser <mirmos...@gmail.com> wrote:

> Fortunately I had retained 17.04 full installation on a USB stick.
> Downloaded new update via Google DNS on IPV4, then deleted 8.8.8.8 and
> tested. Seems to be working. So far so good Thanks for the heads-up
> hrvooje!
> Best
> David
>
> On 18 April 2017 at 07:09, hrvooje <1654...@bugs.launchpad.net> wrote:
>
>> This morning I got dnsutils and bind9-host updates. Could this be the
>> fix? So far so good, no disconecting last hour.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1654918
>>
>> Title:
>>   No Internet access with default of  Automatic (DHCP)
>>
>> Status in Linux:
>>   New
>> Status in NetworkManager:
>>   New
>> Status in network-manager package in Ubuntu:
>>   Confirmed
>>
>> Bug description:
>>   Fresh 17.04 install, wireless router connects without any issue but
>> there is no internet connection/access.
>>   This continues thru disconnecting, reconnecting, rebooting ect,
>> Nothing..
>>
>>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
>> only & manually add Google DNS nameservers: then internet is enabled.
>> screen attached
>>   Note this also affects ethernet, not just wireless
>>   Hardware is:
>>   description: Wireless interface
>>  product: Wireless 7260
>>  vendor: Intel Corporation
>>  physical id: 0
>>  bus info: pci@:08:00.0
>>  logical name: wlp8s0
>>  version: 73
>>  serial: 
>>  width: 64 bits
>>  clock: 33MHz
>>  capabilities: pm msi pciexpress bus_master cap_list ethernet
>> physical wireless
>>  configuration: broadcast=yes driver=iwlwifi
>> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
>> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>>  resources: irq:32 memory:c240-c2401fff
>>
>>   To note: this hardware works perfectly in 14.04 > 16.04
>>   Add. note; issue doesn't arise with 4.11.x kernel
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 17.04
>>   Package: network-manager 1.4.2-2ubuntu4
>>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>>   Uname: Linux 4.9.0-11-generic x86_64
>>   ApportVersion: 2.20.4-0ubuntu1
>>   Architecture: amd64
>>   CurrentDesktop: Unity
>>   Date: Sun Jan  8 22:08:26 2017
>>   IfupdownConfig:
>># interfaces(5) file used by ifup(8) and ifdown(8)
>>auto lo
>>iface lo inet loopback
>>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>>   IpRoute:
>>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
>> metric 600
>>   NetworkManager.conf:
>>[main]
>>plugins=ifupdown,keyfile
>>
>>[ifupdown]
>>managed=false
>>   NetworkManager.state:
>>[main]
>>NetworkingEnabled=true
>>WirelessEnabled=true
>>WWANEnabled=true
>>   SourcePackage: network-manager
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   nmcli-dev:
>>DEVICE  TYPE  STATEDBUS-PATH
>> CONNECTION  CON-UUID  CON-PATH
>>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
>> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f
>> /org/

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

Fortunately I had retained 17.04 full installation on a USB stick.
Downloaded new update via Google DNS on IPV4, then deleted 8.8.8.8 and
tested. Seems to be working. So far so good Thanks for the heads-up
hrvooje!
Best
David

On 18 April 2017 at 07:09, hrvooje <1654...@bugs.launchpad.net> wrote:

> This morning I got dnsutils and bind9-host updates. Could this be the
> fix? So far so good, no disconecting last hour.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1654918
>
> Title:
>   No Internet access with default of  Automatic (DHCP)
>
> Status in Linux:
>   New
> Status in NetworkManager:
>   New
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Fresh 17.04 install, wireless router connects without any issue but
> there is no internet connection/access.
>   This continues thru disconnecting, reconnecting, rebooting ect, Nothing..
>
>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
> only & manually add Google DNS nameservers: then internet is enabled.
> screen attached
>   Note this also affects ethernet, not just wireless
>   Hardware is:
>   description: Wireless interface
>  product: Wireless 7260
>  vendor: Intel Corporation
>  physical id: 0
>  bus info: pci@:08:00.0
>  logical name: wlp8s0
>  version: 73
>  serial: 
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
>  configuration: broadcast=yes driver=iwlwifi
> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>  resources: irq:32 memory:c240-c2401fff
>
>   To note: this hardware works perfectly in 14.04 > 16.04
>   Add. note; issue doesn't arise with 4.11.x kernel
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: network-manager 1.4.2-2ubuntu4
>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>   Uname: Linux 4.9.0-11-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jan  8 22:08:26 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>   IpRoute:
>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
> metric 600
>   NetworkManager.conf:
>[main]
>plugins=ifupdown,keyfile
>
>[ifupdown]
>managed=false
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-dev:
>DEVICE  TYPE  STATEDBUS-PATH
>   CONNECTION  CON-UUID  CON-PATH
>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  /org/freedesktop/
> NetworkManager/ActiveConnection/0
>enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
> --  ----
>lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
> --  ----
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.4.2connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

Yup... Me, I'm reverting back to 16.10
D

On 17 Apr 2017 15:51, "harry brijs"  wrote:

> i installed from iso file
> internet is avail upon goodwill of the system
> or whatever.
> It comes but most of the time it does not stay.
> I did not yet correlate this behaviour
> 2
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1654918
>
> Title:
>   No Internet access with default of  Automatic (DHCP)
>
> Status in Linux:
>   New
> Status in NetworkManager:
>   New
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Fresh 17.04 install, wireless router connects without any issue but
> there is no internet connection/access.
>   This continues thru disconnecting, reconnecting, rebooting ect, Nothing..
>
>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
> only & manually add Google DNS nameservers: then internet is enabled.
> screen attached
>   Note this also affects ethernet, not just wireless
>   Hardware is:
>   description: Wireless interface
>  product: Wireless 7260
>  vendor: Intel Corporation
>  physical id: 0
>  bus info: pci@:08:00.0
>  logical name: wlp8s0
>  version: 73
>  serial: 
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
>  configuration: broadcast=yes driver=iwlwifi
> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>  resources: irq:32 memory:c240-c2401fff
>
>   To note: this hardware works perfectly in 14.04 > 16.04
>   Add. note; issue doesn't arise with 4.11.x kernel
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: network-manager 1.4.2-2ubuntu4
>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>   Uname: Linux 4.9.0-11-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jan  8 22:08:26 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>   IpRoute:
>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
> metric 600
>   NetworkManager.conf:
>[main]
>plugins=ifupdown,keyfile
>
>[ifupdown]
>managed=false
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-dev:
>DEVICE  TYPE  STATEDBUS-PATH
>   CONNECTION  CON-UUID  CON-PATH
>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  /org/freedesktop/
> NetworkManager/ActiveConnection/0
>enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
> --  ----
>lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
> --  ----
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.4.2connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

Actually there seem to be two related or unrelated issues. One seems to be
purely DNS and the other Network Manager... Dunno.  My original issue was
Network Manager. Now ok for no reason i can see. The more sticky one with
my latest upgrade was no problem linking to my WiFi but no internet when
linked. Using Google's 8.8.8.8 address in IPV4 solved that, which seemed to
be caused by resolvconf solutions or workarounds have been posted but turn
out to be temporary fixes that then become unfixed again ... On reboot...
And sometimes even without reboot.
Ho ... Hum...

On 16 Apr 2017 23:35, "Doug McMahon" <1654...@bugs.launchpad.net> wrote:

> Another 'fix' suggested is to
> Open
> /etc/NetworkManager/NetworkManager.conf
>
> add lines
> [device]
> wifi.scan-rand-mac-address=no
>
> then
> sudo service network-manager restart
>
> I'm fine with just changing the nameservers as previously mentoned, in
> any event users shouldn't have to do anything. (even with a limited
> support period release like 17.04
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1654918
>
> Title:
>   No Internet access with default of  Automatic (DHCP)
>
> Status in Linux:
>   New
> Status in NetworkManager:
>   New
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Fresh 17.04 install, wireless router connects without any issue but
> there is no internet connection/access.
>   This continues thru disconnecting, reconnecting, rebooting ect, Nothing..
>
>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
> only & manually add Google DNS nameservers: then internet is enabled.
> screen attached
>   Note this also affects ethernet, not just wireless
>   Hardware is:
>   description: Wireless interface
>  product: Wireless 7260
>  vendor: Intel Corporation
>  physical id: 0
>  bus info: pci@:08:00.0
>  logical name: wlp8s0
>  version: 73
>  serial: 
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
>  configuration: broadcast=yes driver=iwlwifi
> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>  resources: irq:32 memory:c240-c2401fff
>
>   To note: this hardware works perfectly in 14.04 > 16.04
>   Add. note; issue doesn't arise with 4.11.x kernel
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: network-manager 1.4.2-2ubuntu4
>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>   Uname: Linux 4.9.0-11-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jan  8 22:08:26 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>   IpRoute:
>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
> metric 600
>   NetworkManager.conf:
>[main]
>plugins=ifupdown,keyfile
>
>[ifupdown]
>managed=false
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-dev:
>DEVICE  TYPE  STATEDBUS-PATH
>   CONNECTION  CON-UUID  CON-PATH
>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  /org/freedesktop/
> NetworkManager/ActiveConnection/0
>enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
> --  ----
>lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
> --  ----
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.4.2connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

Regret to inform that an upgrade from 16.04 is also displaying the bug.
Reduced to using Google DNS on ipv4 (8.8.8.8) in order to work around it
David

On 14 Apr 2017 14:11, "David Oser" <1654...@bugs.launchpad.net> wrote:

I'm also experiencing this exact bug.
Upgrading from 16.10 to 17.04 did not display the problem, but fresh
install of Ubuntu 17.04 does

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  New
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there
is no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
only & manually add Google DNS nameservers: then internet is enabled.
screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:08:00.0
 logical name: wlp8s0
 version: 73
 serial: 
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet
physical wireless
 configuration: broadcast=yes driver=iwlwifi
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
latency=0 link=ye s multicast=yes wireless=IEEE 802.11
 resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
metric 600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  /org/freedesktop/
NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
--  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

I'm also experiencing this exact bug. 
Upgrading from 16.10 to 17.04 did not display the problem, but fresh install of 
Ubuntu 17.04 does

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918

Title:
  No Internet access with default of  Automatic (DHCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1633839] Re: No symbol table. Press any key to continue

[David Oser]

Thanks Yu Lou - in the end I did a fresh install. That was OK.
David

On 19 Nov 2016 02:00, "Yu Lou" <1633...@bugs.launchpad.net> wrote:

> I have a dual system of Ubuntu and Windows 7 and encountered the same
> problem after in place upgrade from 16.04 to 16.10. I tried boot-repair
> before but it didn't work. Just a moment ago I tried this command and it
> worked:
>
> sudo grub-install /dev/sda
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
>   No symbol table. Press any key to continue
>
> Status in grub2 package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 16.10. shows "error: no symbol table. Press any key to
>   continue..." after Kernel boot and before login screen. After pressing
>   a key or waiting a few seconds, the boot process continues and login
>   screen appears.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.8.0-22-generic 4.8.0-22.24
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:     7722 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 13:25:22 2016
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
>   InstallationDate: Installed on 2013-10-28 (1083 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   MachineType: LENOVO 23255B2
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
>   RelatedPackageVersions:
>linux-restricted-modules-4.8.0-22-generic N/A
>linux-backports-modules-4.8.0-22-generic  N/A
>linux-firmware1.161
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
>   dmi.bios.date: 03/03/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ETA6WW (2.66 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23255B2
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: CS023589
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
> pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 23255B2
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/
> 1633839/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633839

Title:
  No symbol table. Press any key to continue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1633839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1633839] Re: No symbol table. Press any key to continue

[David Oser]

As other replies Joseph. The only thing I didn't try was an upstream
kernel. But in the end I've just done a completely fresh install - so
someone else will need to try the upstream kernel approach.. But I'm
intrigued that two people found their solution via a new grub install,
while I didn't
David

On 19 Oct 2016 19:31, "Joseph Salisbury" 
wrote:

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1633839

Title:
  No symbol table. Press any key to continue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:
cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633839

Title:
  No symbol table. Press any key to continue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1633839] Re: No symbol table. Press any key to continue

[David Oser]

I have tried 'boot-repair' in normal and advanced mode and have tried 
reinstalling grub via sudo grub-install /dev/sda1 (then sda2, and finally 
simply sda). All of these approaches have reported 'success' in bash/terminal 
etc - but none have actually solved my problem.
Actually I'm wondering where my 'working' grub is actually installed. I have a 
UEFI machine which originally came with Windows 8. On installing Ubuntu I did 
what was necessary to allow Ubuntu 14.04 to be installed successfully instead 
of Windows, and have 3 partitions: sda1 is allegedly my boot partition (Fat 
32), sda2 my main partition and finally there is a sda3 - for Linux-Swap. I 
suppose it is possible I have two grubs installed, one in sda1 and the other in 
sda2. Is it possible that a delay in reaching the 'working' grub (say in sda2) 
is provoking the 'no symbol table found' error in Ubuntu 16.10? 
I wonder what would happen if I deleted partition sda1, expanded sda2 into its 
space and then tried boot-repair via usb? Or maybe kept all 3 partitions but 
converted sda1 to ext4. However, I'm reluctant to risk these approaches for 
fear of not being able to recover my system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633839

Title:
  No symbol table. Press any key to continue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1633839] Re: No symbol table. Press any key to continue

[David Oser]

Thanks Alex
I had tried 'boot-repair' to no avail, although success was reported.
But I tried your solution twice by using dev/sda1 (the current efi FAT32
boot partition) and /dev/sda2 ( the main ext4 partition). Neither solved
the problem although there were no error messages only 'successful' report
in bash/command line.
Ahem...Then I read the link you kindly supplied (!) and found I should just
have used dev/sda. But unfortunately this also did not work to solve my
problem, although it also reported 'success' in bash.
I'm beginning to wonder if I shouldn't remove the separate FAT32 boot
partition which was probably a legacy from when I first installed Ubuntu on
this UEFI machine which used to run Windows, as I suspect this might be
what's causing the problem.
I'm fully backed up, but reluctant to go through the palava of a complete
reinstall of Ubuntu if I fully borked the system by removing the separate
boot partition.
Ho hum... I think I'll live with the issue for the time being.
Best
David

On 18 October 2016 at 21:31, Alex N. <1633...@bugs.launchpad.net> wrote:

> That made me think about grub, so i reinstalled grub as described here
> https://help.ubuntu.com/community/Grub2/Installing#
> Reinstalling_GRUB_2_from_a_Working_System
>
> sudo grub-install /dev/sdX
> sudo update-grub
> sudo reboot
>
> and voila, the error message is gone.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
>   No symbol table. Press any key to continue
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 16.10. shows "error: no symbol table. Press any key to
>   continue..." after Kernel boot and before login screen. After pressing
>   a key or waiting a few seconds, the boot process continues and login
>   screen appears.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.8.0-22-generic 4.8.0-22.24
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:     7722 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 13:25:22 2016
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
>   InstallationDate: Installed on 2013-10-28 (1083 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   MachineType: LENOVO 23255B2
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
>   RelatedPackageVersions:
>linux-restricted-modules-4.8.0-22-generic N/A
>linux-backports-modules-4.8.0-22-generic  N/A
>linux-firmware1.161
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
>   dmi.bios.date: 03/03/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ETA6WW (2.66 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23255B2
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: CS023589
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
> pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 23255B2
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1633839/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633839

Title:
  No symbol table. Press any key to continue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1633839] Re: No symbol table. Press any key to continue

[David Oser]

Thanks Michka
I had tried the boot-repair option, to no avail.
But this time I made sure I had the latest version (I do) by completely
removing boot-repair and reinstalling, including repository, and tried
'advanced' option. 'Successful' but didn't solve the problem.
Then I tried default version of boot-repair. Likewise, 'successful', but
didn't solve the problem.
I don't have a dual-boot system since I long ago removed Windows. But it is
a UEFI machine and I have a separate sda1 FAT 32 boot partition, then a
main sda2 ext4 partition, then a swap partition.
I'm wondering if I should remove the sda1 efi FAT 32 partition, which may
be causing the difficulty (even though in boot-repair 'advanced' option I
had ensured that grub would be 'additionally' be reinstalled in sda1)?
I'm a 'fiddler' rather than an expert so I'm reluctant to risk doing that
as I do have a working system right now, even though it is slightly
compromised at boot since the upgrade to 16.10.
What do you think?
By the way, Alex N's solution also did not work for me. Though I have not
tried simply using /dev/sda rather than sda1 or sda2.
Best
David

On 18 October 2016 at 21:11, Michka Popoff <1633...@bugs.launchpad.net>
wrote:

> I had the same problem. Updating from 16.04 to 16.10 in place.
>
> I ran boot-repair, but the tool had not been updated during the
> migration (the update 16.10 removed the boot-repair ppa from the
> sources.list). Running the repair completely botched my grub.cfg files
> (update-grub was complaining about syntax errors). After a (painful)
> manual restart through the grub command line, I was able to boot.
>
> The I did:
> sudo add-apt-repository ppa:yannubuntu/boot-repair
> sudo apt-get update
> sudo apt-get upgrade
>
> Using the new boot-repair (version 4ppa38, instead of the old 4ppa35), I
> ran the repair tool, setup grub again, rebooted, and the "error: no
> symbol table. Press any key to continue..." was gone.
>
> People looking for a solution may update boot-repair to 4ppa38, run it,
> and see if it fixes it. Make sure to backup your data first, it worked
> for me but I can't guarantee that it will work for you.
>
> I am attaching the boot-repair report done with 4ppa35, which may be of
> interest for people trying to debug this.
>
> ** Attachment added: "boot-repair output"
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1633839/+attachment/4763425/+files/Boot-info.txt
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
>   No symbol table. Press any key to continue
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 16.10. shows "error: no symbol table. Press any key to
>   continue..." after Kernel boot and before login screen. After pressing
>   a key or waiting a few seconds, the boot process continues and login
>   screen appears.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.8.0-22-generic 4.8.0-22.24
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:     7722 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 13:25:22 2016
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
>   InstallationDate: Installed on 2013-10-28 (1083 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   MachineType: LENOVO 23255B2
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
>   RelatedPackageVersions:
>linux-restricted-modules-4.8.0-22-generic N/A
>linux-backports-modules-4.8.0-22-generic  N/A
>linux-firmware1.161
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
>   dmi.bios.date: 03/03/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ETA6WW (2.66 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23255B2
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: CS023589
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
> pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 23255B2
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1633839/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633839

[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)

[David Oser]

@Brian Rogers
Many thanks - I'd just like to report that your patch 
(linux-image-2.6.34-v9patch-generic) appears to be working perfectly for me, 
with my i855 HP Compaq Nx5000. I'm not trying anything fancy regarding video - 
but can report that the system now starts normally, no freeze during boot, and 
- so far - no odd messages. Further, using Cheese with my (equally) ancient 
webcam does not crash the system either, which happened with previous attempts 
at fixes. It is also remaining stable with advanced visual effects selected via 
desktop background. Only thing I haven't tried is suspend - but that is because 
I need to press down on the casing of my old machine near the power input to 
get it to power up at all with any OS - and I always had problems with suspend, 
anyway (go figure...). So I have removed the 10.04  rc7 Mainline kernel at 
last!! I'll report back if I get any problems.
Best
David

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)

[David Oser]

@Brian Rogers
Edit to above - no Ubuntu splash on subsequent restarts (any visual effects 
setting), though there was on the first - but I wasn't getting the splash with 
the Mainline kernel, either, so I don't miss it anyway.
Best
David

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)

[David Oser]

@Thoer (#162 etc/usw). 
Many, many thanks for that effort. 

Slight bug initially evident on my i8xx machine, in that application (eg
Firefox) may open without showing the app bar at the top containing its
minimize, maximize and close symbols, and closing under file-close still
leaves the app showing in the bottom Ubuntu toolbar, and that app
manifestation cannot be gotten rid of without a complete restart.

However, this problem has now disappeared with today's
ppa.launchpad.net/glasen source update. Brilliant!! No rigorous testing
done by me, however.

I do have this query... what happens long term, as this (altered
kernel?) gets replaced via normal (official) updates. Will I need,
eventually, to modify my grub to ensure this unofficial version is the
one that loads?

Still - mustn't complain. Ubuntu is now a joy to use once more...
David

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)

[David Oser]

@Brian Rogers (#145) - I may be misunderstanding the word 'distro', but 
Peppermint Linux (otherwise ugh-for-me) is not affected (kernel 2.6.32-22, if I 
remember correctly) and rcs 5,6.7 of Mainline Lucid version is also not 
affected - at least, they work fine with my i855 display.
@Steve Langasek (#152) - the same basic symptom is evident on a number of intel 
display chipsets. Does it make sense to file them under separate bug numbers? I 
know programming is an iterative process, but sometimes it makes sense to take 
an overview.

Now for a bit of a rant, if you'll forgive me. Just a glance through the
normal forums indicates that there are many many ordinary people
affected by this bug... to the extent that they cannot upgrade from the
excellent 9.10 version without very complicated (for normal people)
workarounds, nor install Lucid cleanly for the first time. I really
think the release of Lucid before these bugs were fixed (and they
certainly were not evident in the excellent early Lucid alphas - so we
are talking of regression, here) was a serious mistake. I know open
source development is a labour of love, and many people have devoted
enormous numbers of hours to Ubuntu Lucid, without any financial reward
for their efforts. I certainly do not blame them at all, as some are
still hard at work trying to solve this particular problem. But somebody
made a decision to respect some 'magic date' for full release, and, in
my opinion, that someone made a serious error. This kind of thing tends
to bring the concept of open-source software into disrepute. Is it
intended for the masses, or just a geeky few?

Best
David

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 568779] Re: [i855] 10.04 rc boots into black/blank screen

[David Oser]

*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511

Yes that's my experience with the mainline kernel. Wish I knew what it
was, though. Information on what it represents seems hard to come by if
you are not a fully fledged geek.

-- 
[i855] 10.04 rc boots into black/blank screen
https://bugs.launchpad.net/bugs/568779
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)

[David Oser]

Or... Hat tip to Alban #54 over at
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/568779 ... but slightly modified because it's now rc6. If you
have some kind of Lucid desktop, you won't need 1-4, so start at 5.


Alban wrote:
1. After power on your PC, press shift (keep press) until see boot loader 
menu. Choose a recovery mode option.
2. On next step select start failsafeX session.
3. Choose OK when advert for poor resolution.
4. Login in, your are now on your desktop
5. Open a terminal command line (Application  Accessories - terminal)
6. Type this command and press enter (without quotes):
sudo -i and enter your password.
7. Type this command and press enter (without quotes):
cd /tmp
8. Type this command and press enter (without quotes):
wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc6-lucid/linux-image-2.6.34-020634rc5-generic_2.6.34-020634rc6_i386.deb;
9. Type this command and press enter (without quotes):
dpkg -i linux-image-2.6.34-020634rc6-generic_2.6.34-020634rc6_i386.deb
10. Type this command and press enter (whitout quotes):
apt-get update  apt-get upgrade
11 . Type this command and press enter (whitout quotes):
init 6

Your computer restarts with new kernel and intel driver updated and,
hopefully, works without freeze. 

... And it does!

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)

[David Oser]

 Woops! My error - where you see  'rc5' still in 8. above, replace
with 'rc6'

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 568779] Re: [i855] 10.04 rc boots into black/blank screen

[David Oser]

*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511

The problem appears to have been resolved with the latest kernel available via 
'proposed updates' lucid-proposed. It least - it has for me, so now I have 
undone as many of the workarounds as I can recall applying...Still works... 
Yipeee!!
David

-- 
[i855] 10.04 rc boots into black/blank screen
https://bugs.launchpad.net/bugs/568779
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 568779] Re: [i855] 10.04 rc boots into black/blank screen

[David Oser]

*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511

Spoke too soon (see #80). Cheese Webcam Booth crashes the system with my 
particular webcam - whereas it didn't with the workarounds (eg xx.x .20 kernel 
and 'mainline' kernel - or was that 'mainstream', I forget)... ho hum... Still, 
at least it's (as proposed) now a bootable system, if not perfect
David

-- 
[i855] 10.04 rc boots into black/blank screen
https://bugs.launchpad.net/bugs/568779
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)

[David Oser]

Sorry - commented in the duplicate bug... Latest proposed update 
(lucid-proposed) seems to fix the main problem of non-bootability due to black 
screen; but it does not fix the (associated?) problem of Cheese Webcam Booth 
crashing the system. At least Lucid Linux version xx.x.22 is now usable without 
workarounds for those of us with this particular type of display chipset
David

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 568779] Re: [i855] 10.04 rc boots into black/blank screen

[David Oser]

*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511

Maybe you didn't hold shift down early enough Vilius? Works for me. I
can then choose from two kernels. I choose the earlier one, and not the
recovery mode options. Choosing a recovery mode option means I then have
to further select a recovery display (I forget what that subsequent
option was called) to get a less good display resolution, whereas if I
just select a previous kernel (only two are on offer to me) I eventually
get to my best display (after some heart-stopping messages about cannot
mount, and doesn't exist, and then nothing, and then finally a screenful
of scrolling text, before a decent launch of 10.04).

Be nice if they do eventually manage to fix this, but I can work with
it, sort of... with my Intel 855 card

-- 
[i855] 10.04 rc boots into black/blank screen
https://bugs.launchpad.net/bugs/568779
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 536654] [NEW] [i855] GPU lockup f7711baaec99d519329573a7384c4bef

[David Oser]

Public bug reported:

Binary package hint: xserver-xorg-video-intel

No further information

ProblemType: Crash
Architecture: i386
Chipset: i855
Date: Wed Mar 10 11:55:22 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: f7711baaec99d519329573a7384c4bef
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
MachineType: Hewlett-Packard Compaq nx5000 (DU305T#ABU)
Package: xserver-xorg-video-intel 2:2.9.1-1ubuntu12
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic 
root=UUID=9b889000-48d8-4bc5-872b-e328bbcad464 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:
 
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: xserver-xorg-video-intel
Title: [i855] GPU lockup f7711baaec99d519329573a7384c4bef
Uname: Linux 2.6.32-16-generic i686
UserGroups:
 
dmi.bios.date: 08/30/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68BCU Ver. F.0E
dmi.board.name: 08BC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 33.0D
dmi.chassis.asset.tag: CNU4150LHJ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68BCUVer.F.0E:bd08/30/2006:svnHewlett-Packard:pnCompaqnx5000(DU305T#ABU):pvrF.0E:rvnHewlett-Packard:rn08BC:rvrKBCVersion33.0D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: Compaq nx5000 (DU305T#ABU)
dmi.product.version: F.0E
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename:   lucid
 architecture:   i686
 kernel: 2.6.32-16-generic

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash freeze i386 lucid

-- 
[i855] GPU lockup f7711baaec99d519329573a7384c4bef
https://bugs.launchpad.net/bugs/536654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 536654] Re: [i855] GPU lockup f7711baaec99d519329573a7384c4bef

[David Oser]

** Attachment added: BootDmesg.txt
   http://launchpadlibrarian.net/40693180/BootDmesg.txt

** Attachment added: CurrentDmesg.txt
   http://launchpadlibrarian.net/40693181/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/40693182/Dependencies.txt

** Attachment added: GdmLog.txt
   http://launchpadlibrarian.net/40693183/GdmLog.txt

** Attachment added: GdmLog1.txt
   http://launchpadlibrarian.net/40693184/GdmLog1.txt

** Attachment added: GdmLog2.txt
   http://launchpadlibrarian.net/40693185/GdmLog2.txt

** Attachment added: IntelGpuDump.txt
   http://launchpadlibrarian.net/40693186/IntelGpuDump.txt

** Attachment added: Lspci.txt
   http://launchpadlibrarian.net/40693187/Lspci.txt

** Attachment added: Lsusb.txt
   http://launchpadlibrarian.net/40693188/Lsusb.txt

** Attachment added: PciDisplay.txt
   http://launchpadlibrarian.net/40693189/PciDisplay.txt

** Attachment added: ProcAttrCurrent.gz
   http://launchpadlibrarian.net/40693190/ProcAttrCurrent.gz

** Attachment added: ProcCpuinfo.txt
   http://launchpadlibrarian.net/40693191/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   http://launchpadlibrarian.net/40693192/ProcInterrupts.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/40693193/ProcMaps.txt

** Attachment added: ProcModules.txt
   http://launchpadlibrarian.net/40693194/ProcModules.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/40693195/ProcStatus.txt

** Attachment added: RelatedPackageVersions.txt
   http://launchpadlibrarian.net/40693196/RelatedPackageVersions.txt

** Attachment added: UdevDb.txt
   http://launchpadlibrarian.net/40693197/UdevDb.txt

** Attachment added: UdevLog.txt
   http://launchpadlibrarian.net/40693198/UdevLog.txt

** Attachment added: XorgLog.txt
   http://launchpadlibrarian.net/40693199/XorgLog.txt

** Attachment added: XorgLogOld.txt
   http://launchpadlibrarian.net/40693200/XorgLogOld.txt

** Attachment added: Xrandr.txt
   http://launchpadlibrarian.net/40693201/Xrandr.txt

** Attachment added: glxinfo.txt
   http://launchpadlibrarian.net/40693202/glxinfo.txt

** Attachment added: i915_error_state.txt
   http://launchpadlibrarian.net/40693203/i915_error_state.txt

** Attachment added: setxkbmap.txt
   http://launchpadlibrarian.net/40693204/setxkbmap.txt

** Attachment added: xdpyinfo.txt
   http://launchpadlibrarian.net/40693205/xdpyinfo.txt

** Attachment added: xkbcomp.txt
   http://launchpadlibrarian.net/40693206/xkbcomp.txt

-- 
[i855] GPU lockup f7711baaec99d519329573a7384c4bef
https://bugs.launchpad.net/bugs/536654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 535312] [NEW] [i855] GPU lockup bde775a3c9602485047915eeabf64f1f

[David Oser]

Public bug reported:

DK

ProblemType: Crash
Architecture: i386
Chipset: i855
Date: Tue Mar  9 19:24:45 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: bde775a3c9602485047915eeabf64f1f
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
MachineType: Hewlett-Packard Compaq nx5000 (DU305T#ABU)
Package: xserver-xorg-video-intel 2:2.9.1-1ubuntu10
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic 
root=UUID=9b889000-48d8-4bc5-872b-e328bbcad464 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:
 
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
SourcePackage: nvidia-graphics-drivers
Title: [i855] GPU lockup bde775a3c9602485047915eeabf64f1f
Uname: Linux 2.6.32-16-generic i686
UserGroups:
 
XorgLogOld:
 
dmi.bios.date: 08/30/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68BCU Ver. F.0E
dmi.board.name: 08BC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 33.0D
dmi.chassis.asset.tag: CNU4150LHJ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68BCUVer.F.0E:bd08/30/2006:svnHewlett-Packard:pnCompaqnx5000(DU305T#ABU):pvrF.0E:rvnHewlett-Packard:rn08BC:rvrKBCVersion33.0D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: Compaq nx5000 (DU305T#ABU)
dmi.product.version: F.0E
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename:   lucidarchitecture:   i686kernel: 
2.6.32-16-generic

** Affects: nvidia-graphics-drivers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash freeze i386 lucid

-- 
[i855] GPU lockup bde775a3c9602485047915eeabf64f1f
https://bugs.launchpad.net/bugs/535312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 535312] Re: [i855] GPU lockup bde775a3c9602485047915eeabf64f1f

[David Oser]

** Attachment added: BootDmesg.txt
   http://launchpadlibrarian.net/40635202/BootDmesg.txt

** Attachment added: CurrentDmesg.txt
   http://launchpadlibrarian.net/40635203/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/40635204/Dependencies.txt

** Attachment added: IntelGpuDump.txt
   http://launchpadlibrarian.net/40635205/IntelGpuDump.txt

** Attachment added: Lspci.txt
   http://launchpadlibrarian.net/40635206/Lspci.txt

** Attachment added: Lsusb.txt
   http://launchpadlibrarian.net/40635208/Lsusb.txt

** Attachment added: PciDisplay.txt
   http://launchpadlibrarian.net/40635209/PciDisplay.txt

** Attachment added: ProcAttrCurrent.gz
   http://launchpadlibrarian.net/40635210/ProcAttrCurrent.gz

** Attachment added: ProcCpuinfo.txt
   http://launchpadlibrarian.net/40635211/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   http://launchpadlibrarian.net/40635212/ProcInterrupts.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/40635213/ProcMaps.txt

** Attachment added: ProcModules.txt
   http://launchpadlibrarian.net/40635214/ProcModules.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/40635216/ProcStatus.txt

** Attachment added: RelatedPackageVersions.txt
   http://launchpadlibrarian.net/40635217/RelatedPackageVersions.txt

** Attachment added: UdevDb.txt
   http://launchpadlibrarian.net/40635218/UdevDb.txt

** Attachment added: UdevLog.txt
   http://launchpadlibrarian.net/40635219/UdevLog.txt

** Attachment added: XorgLog.txt
   http://launchpadlibrarian.net/40635220/XorgLog.txt

** Attachment added: Xrandr.txt
   http://launchpadlibrarian.net/40635221/Xrandr.txt

** Attachment added: glxinfo.txt
   http://launchpadlibrarian.net/40635222/glxinfo.txt

** Attachment added: i915_error_state.txt
   http://launchpadlibrarian.net/40635223/i915_error_state.txt

** Attachment added: setxkbmap.txt
   http://launchpadlibrarian.net/40635224/setxkbmap.txt

** Attachment added: xdpyinfo.txt
   http://launchpadlibrarian.net/40635225/xdpyinfo.txt

** Attachment added: xkbcomp.txt
   http://launchpadlibrarian.net/40635226/xkbcomp.txt

-- 
[i855] GPU lockup bde775a3c9602485047915eeabf64f1f
https://bugs.launchpad.net/bugs/535312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs