Public bug reported:
See Bug #505310.
In the course of trying to find out why choice of DVI port should affect
the ability of 9.10 to boot, I was asked to run 'apport-collect -p xorg
505310'. All I got was the message 'unable to find server at
edge.launchpad.net.'
I was then asked to run 'ifconfig' and got:
eth0 Link encap:Ethernet HWaddr 00:1d:09:0c:75:1f
inet6 addr: fe80::21d:9ff:fe0c:751f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:492 (492.0 B)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
When I changed DVI outlets (9.10 loaded normally) and then ran ifconfig,
this is what I got:
t...@ted-desktop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1d:09:0c:75:1f
inet addr:10.1.1.10 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::21d:9ff:fe0c:751f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1850 (1.8 KB) TX bytes:5259 (5.2 KB)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
t...@ted-desktop:~$
Somehow changing the DVI outlet is affecting how the network installs!
Ted
** Affects: ubuntu
Importance: Undecided
Status: New
--
In Karmic Koala choice of DVI port affects network
https://bugs.launchpad.net/bugs/511476
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
