The same issue is described here:
http://www.unchartedbackwaters.co.uk/pyblosxom/debian_ubuntu_dns_resolution_delays
I can confirm that removing mdns4 makes the problem go away. So it's
really https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/94940,
please merge.
--
There are actually
Public bug reported:
Binary package hint: putty
If you launch putty from the 2nd monitor and select text by click
dragging, then putty immediately crashes. A work-around is to launch
putty once from the 1st monitor. If you do this subsequent putty
sessions on the 2nd monitor won't crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750661
Title:
If Putty is running on the 2nd monitor selecting text causes an
immediate crash
--
ubuntu-bugs mailing list
To add detail this happens if each monitor is a separate instance of X
Windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750661
Title:
If Putty is running on the 2nd monitor selecting text
Public bug reported:
If you use ping from the command line and the host you are pinging does
not have a rDNS entry, then ping pauses for 5 seconds or more between
packets. Since there's no output on the terminal it looks as if the host
is down, but when you press Ctrl-C, you get a line about the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737959
Title:
ping waits 5 seconds between packets if RDNS is not present
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It's a valid hostname (numeric sub-domains are allowed in DNS), but it's
not a valid FQDN. However I'm not convinced that newaliases should fail
like this. Shouldn't it just create an empty alias database? Should
Postfix be policing which TLD's are valid? It seems like that should be
up to the
It's a valid hostname (numeric sub-domains are allowed in DNS), but it's
not a valid FQDN. However I'm not convinced that newaliases should fail
like this. Shouldn't it just create an empty alias database? Should
Postfix be policing which TLD's are valid? It seems like that should be
up to the
Public bug reported:
Binary package hint: postfix
When upgrading from 8.04 to 10.04 the postfix alone failed.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: postfix 2.7.0-1
ProcVersionSignature: Ubuntu 2.6.24-28.77-server
Uname: Linux 2.6.24-28-server x86_64
Architecture: amd64
Date:
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/658795/+attachment/1686411/+files/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
https://bugs.launchpad.net/bugs/658795/+attachment/1686412/+files/VarLogDistupgradeAptlog.gz
** Attachment added:
Okay, I took a closer look. The problem is that my hostname is tosh.0.
Somehow this makes something think that my hostname is numeric. Here's
the text:
Setting up postfix (2.7.0-1) ...
Postfix configuration was not changed. If you need to make changes, edit
/etc/postfix/main.cf (and others) as
** Attachment added: This is the file that postfix was dying on
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/658795/+attachment/1686445/+files/main.cf
--
package postfix 2.7.0-1 failed to install/upgrade:
https://bugs.launchpad.net/bugs/658795
You received this bug notification
Public bug reported:
Binary package hint: postfix
When upgrading from 8.04 to 10.04 the postfix alone failed.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: postfix 2.7.0-1
ProcVersionSignature: Ubuntu 2.6.24-28.77-server
Uname: Linux 2.6.24-28-server x86_64
Architecture: amd64
Date:
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/658795/+attachment/1686411/+files/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
https://bugs.launchpad.net/bugs/658795/+attachment/1686412/+files/VarLogDistupgradeAptlog.gz
** Attachment added:
Okay, I took a closer look. The problem is that my hostname is tosh.0.
Somehow this makes something think that my hostname is numeric. Here's
the text:
Setting up postfix (2.7.0-1) ...
Postfix configuration was not changed. If you need to make changes, edit
/etc/postfix/main.cf (and others) as
** Attachment added: This is the file that postfix was dying on
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/658795/+attachment/1686445/+files/main.cf
--
package postfix 2.7.0-1 failed to install/upgrade:
https://bugs.launchpad.net/bugs/658795
You received this bug notification
Just got around to testing with 10.4 Beta 2 and the problem doesn't
present at all. In fact the mtrr: no more MTRRs available message
doesn't show up at all. So it's safe to say this is completely fixed.
--
mtrr: no more MTRRs available makes X lock up when running Firefox with ATI
driver
Public bug reported:
Binary package hint: nautilus
When trying to move icons on the second monitor (Screen 1), Nautilus
will sometimes crash. Also, icons can't be moved from one screen to
another. When restarting Nautilus via nautilus , I get this crash
info:
The program 'nautilus' received an
** Attachment added: Current xorg.conf
http://launchpadlibrarian.net/39755436/xorg.conf
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39755437/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/39755438/XsessionErrors.txt
**
Public bug reported:
Binary package hint: xserver-xorg-video-mach64
On a HP Proliant DL380 G3 server with 6Gb of memory running Karmic with
the pae kernel these messages show up every time X is started. The X
session then becomes unresponsive. This wouldn't be such a big deal,
except that vmware
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36615491/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/36615492/XsessionErrors.txt
--
mtrr: no more MTRRs available makes X lock up when running Firefox with ATI
driver
Public bug reported:
Binary package hint: xserver-xorg-video-mach64
On a HP Proliant DL380 G3 server with 6Gb of memory running Karmic with
the pae kernel these messages show up every time X is started. The X
session then becomes unresponsive. This wouldn't be such a big deal,
except that vmware
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36615489/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/36615490/XsessionErrors.txt
--
mtrr: no more MTRRs available makes X lock up when running Firefox with ATI
driver
Public bug reported:
Binary package hint: tightvncserver
I'm running tightvnc to keep the regular X server from starting (see
#494358, #494359 -- sorry, I wasn't sure which set of output was
needed). However, whenever I connect with a VNC client (I've tried
RealVNC tightvnc under Win32 and
I need to use the hardware, so I went back to Hardy and the Xserver
works fine without any tweaking. I'll be keeping the system at 8.04
while it runs vmware2, but I'll be happy to boot live CD's if someone
wants me too.
BTW, a similar message appears in the dmesg:
[ 76.092016] mtrr: no more
Hello,
I stopped using Evolution a while back and so I forgot about this bug. I
can confirm that it is fixed in 8.11
Thanks,
Jason M.
Pedro Villavicencio wrote:
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
The issue went away for me w/ Intrepid (I was only running Hardy for a
minutes before upgrading again due to some file system corruption
issues). I'm running 2.6.27-10-server. What's your kernel version? If
you don't know please post the output of uname -a. Thanks.
--
dell dimension 9200 -
The importance on this needs to be raised. ping is essentially broken
with certain IP addresses, DNS servers, and negative responses. Maybe
the problem isn't in ping but is in the resolver library? I can't do the
code myself, and it's not a problem for me to remember to do ping -n.
However, this
Andy Whitcroft wrote:
That is unexpected as the headers are generated from the same source as
the kernel in theory, and both should have been built from the same
version of utsrelease.h and thus have the same value.
Checking the flavour specific headers those are (as expected) flavour
** Description changed:
Description:
When the user is doing ping -f myhostname.tld, ping does a ipaddr-hostname
request at EACH packet. Which is quite a lot when used with a -f option.
Moreover it is quite useless as when used with -f, ping doesnt display the
result of the
Public bug reported:
Binary package hint: linux-headers-2.6.27-10-server
Just as the summary says. utsrelease.h says the version is 2.6.27-7 (or
something very close), rather than saying 2.6.27-10-server. This
confuses the VMWare 2.0 installer to the point where it won't function.
The complaint
I'll confirm that the bug is still present in gutsy Desktop release. I'm
recompiling a 2.6.22 kernel now (to add PAE support). I'll add a note if
that causes any change.
--
dell dimension 9200 - reboot doesn't work
https://bugs.launchpad.net/bugs/131292
You received this bug notification because
Actually, I made the prompt go away by changing the Auto completion
preferences for the Exchange account. Go to the Edit menu, choose
Preferences. In the window that pop up, choose AutoCompletion and
uncheck Global Address List under your Exchange account.
--
Always prompted for Exchange
Here's a screen shot of the window I'm talking about (with my Exchange
email address blacked out).
** Attachment added: Evolution Screen Shot
http://launchpadlibrarian.net/10307981/Screenshot-Evolution%20Preferences.png
--
Always prompted for Exchange password when composing new mail; never
I did some research and I have a solution (but it's somewhat ugly). The
first part is to specify a server in the Global Catalog list/ Active
Directory box. That's under the Edit menu. Preferences, select the
Exchange account, select Edit, then click the Receiving options tab. The
ugly part is that
One more thing. This bug happens even if you create a message in another
account in Evolution. It really only makes sense to pull up the Active
Directory user list if you're going to be using Exchange to send the
message.
--
Always prompted for Exchange password when composing new mail; never
36 matches
Mail list logo
