We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Thanks in advance.
The issue that you reported is one that should be reproducta
** Changed in: Ubuntu
Status: Needs Info => Confirmed
--
Networking doesn't work in X
https://bugs.launchpad.net/bugs/26332
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://list
Are there any new developments involved with this weirdness anyone would
care to share? Thank you for any responses.
--
Networking doesn't work in X
https://launchpad.net/bugs/26332
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have the same problem, with a laptop asus a6bg16 (realtek 8139 (8139too
module)), bug in Dapper 6.06 LTS but not in Breezy.
A very strange bug, I have to do a networking restart in a terminal when logged
in X.
- The network starts at boot time
- the network is active because ntpupdate work at b