Re: [Ubuntu-x-swat] [Bug 738066] Re: [i945gm] Something crashed when first logging into freshly installed amd64 Macbook 2, 1 With daily 11.04

Sorry Bryce ( darn autocorrect ) I'll see if I can gather the information when I get home tonight. Cheers Sent from my iPhone On 22/03/2011, at 11:35 AM, Bryce Harrington 738...@bugs.launchpad.net wrote: On Sun, Mar 20, 2011 at 09:02:24AM -, zigford wrote: Hi Brain, Who? I have since

Re: [Bug 738066] Re: [i945gm] Something crashed when first logging into freshly installed amd64 Macbook 2, 1 With daily 11.04

Hi Brain, I have since run all available updates as of this email and I'm still getting the application crash (Not that I can tell what it is/does), Anything else I can submit to find out more? Cheers On Sat, Mar 19, 2011 at 9:51 PM, Bryce Harrington 738...@bugs.launchpad.net wrote: Fairly

[Bug 738066] [NEW] [i945gm] Something crashed when first logging into freshly installed amd64 Macbook 2, 1 With daily 11.04

Public bug reported: Binary package hint: xserver-xorg-video-intel Subsequent logging or restarting causes the crash. At this point, I dont know what the package does, so cant comment if its a real issue or not. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel

[Bug 738066] Re: [i945gm] Something crashed when first logging into freshly installed amd64 Macbook 2, 1 With daily 11.04

-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738066 Title: [i945gm] Something crashed when first logging into freshly installed amd64 Macbook 2,1 With daily 11.04 -- ubuntu-bugs mailing list

[Bug 80900] Re: problems resolving fully qualified domain names on Kubuntu feisty

I renamed my internal DNS to avoind the conflict. Others may still have the problem though. -- problems resolving fully qualified domain names on Kubuntu feisty https://bugs.launchpad.net/bugs/80900 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 80900] Re: problems resolving fully qualified domain names on Kubuntu feisty

I have this same problem on 7.04 beta. Avahi uses the .local as its SOA. Because you use it internally avahi causes conflict. What should happen is that avahi should warn you that you are using .local as part of yout fqdn and offer to disable itself in a bubble. For now, I have changed my

Re: [Bug 98763] Re: avahi did not warn .local SOA in use

At this stage I have changed my domain to jspeed.private, so I can't troubleshoot this anymore. I can change it back quickly though to follow up on the bug report. Will do this tomorrow when I get the chance. Jesse On 30/03/2007, at 11:52 AM, Trent Lloyd wrote: Hrm, 7.04 beta according to

[Bug 98763] Re: avahi did not warn .local SOA in use

** Attachment added: Network Diagram http://librarian.launchpad.net/7049492/LocalNetwork.jpg -- avahi did not warn .local SOA in use https://launchpad.net/bugs/98763 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 80900] Re: problems resolving fully qualified domain names on Kubuntu feisty

Okay, I have changed to jspeed.private as my tld When I go host -t soa private I get: chichi:~ harrisj$ host -t soa private Host private not found: 3(NXDOMAIN) chichi:~ harrisj$ When I go host -s soa jspeed.private I get: chichi:~ harrisj$ host -t soa jspeed.private jspeed.private has SOA

[Bug 98763] Re: avahi did not warn .local SOA in use

*** This bug is a duplicate of bug 80900 *** ** This bug has been marked a duplicate of bug 80900 problems resolving fully qualified domain names on Kubuntu feisty -- avahi did not warn .local SOA in use https://launchpad.net/bugs/98763 -- ubuntu-bugs mailing list

[Bug 80900] Re: problems resolving fully qualified domain names on Kubuntu feisty

Rod, Michael, Can you run host -t soa local and post back the results? -- problems resolving fully qualified domain names on Kubuntu feisty https://launchpad.net/bugs/80900 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 98763] avahi did not warn .local SOA in use

Public bug reported: Binary package hint: avahi-daemon http://ubuntuforums.org/showthread.php?p=2372962#post2372962 I use jspeed.local as my internal DNS. With Avahi running, I could not contact any internal FQDN's. ie couldn't access my proxy server which uses wpad. What it should do: Warn