No, that's the contrary, they reply too fast, in a sense. If you look at
the log I posted, dnsmasq does receive some kind of reply from the
unreachable nameservers. I don't know whether this is a crafted reply by
the firewall or whether the query actually reached the nameserver but it
replied with
What I meant is that DNS resolution always fails at first, and then
after lots of tries, it starts to work. But now that I look at the logs,
it may just have been a fluke: it eventually works because one of the
reachable nameservers happens to reply fast enough.
--
You received this bug notificat
Here is what I get when routing to the DNS servers goes through the
wrong interfaces. See bug #979067 for additional details on my setup.
Jun 25 12:50:51 dnsmasq[3799]: reading /var/run/dnsmasq/resolv.conf
Jun 25 12:50:51 dnsmasq[3799]: using nameserver yy.yy.36.37#53
Jun 25 12:50:51 dnsmasq[3799]
See below for the results of various commands. Prefix xx.xx is the
Ethernet network while yy.yy is the wireless network. Both of them are
in the public IP range (in case it matters). I also added the result of
the dig command, without and with specifying a DNS server. Notice that
directly querying
Public bug reported:
My computer happens to be connected to two networks through eth0 and
wlan0. NetworkManager connects to both of them automatically and use
DHCP for both of them. Both networks are protected from the outside by
firewalls and they are lots of DNS servers (obtained automatically).
Public bug reported:
When running world of warcraft under wine1.3 (1.3.28-0ubuntu1) on
oneiric, wine first complains about missing direct rendering and the
game then crashes at the time it enumerates displays. Reverting to
ia32-libs 20090808ubuntu21 fixes the issue.
This might be related to bug #
On 2011/4/4, David Henningsson wrote:
> Thanks for your bug report. I'm quite certain that the fix is on its way
> with this commit. Would you mind checking after the next kernel is
> upload for Natty, just to verify?
The kernel update caused the "Side 3" channel to disappear. So
hopefully the bug
With compiz version 1:0.9.4git20110322-0ubuntu5, the desktop is unusable
due to black squares appearing all over the place. Using version
1:0.9.4git20110322-0ubuntu6+r2723+201103301010 from ppa:unity/daily does
fix it. This makes unity usable with fglrx.
--
You received this bug notification beca
After running alsamixer, I noticed there was an extra channel called
"Side 3" that was set to 0 (and it was the only one set to 0). Once I
set it to 100, sound started working fine. I don't know whether this
channel existed in maverick and whether it was set to 100 there. So
sound works fine, it's
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/748527
Title:
[EX58-UD5, Realtek ALC889A, Grey Line Out, Rear] No sound at all
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Public bug reported:
I just updated to 11.04 and I don't have sound anymore. It was working
fine with 10.10, both with the stock kernel and a 2.6.37 kernel. I also
tried the other output line but it doesn't make a difference.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: alsa-base 1.0.24+
Yes it is.
--
Lua support disabled on 64-bit architectures
https://bugs.launchpad.net/bugs/584446
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/
It didn't change anything (though the irq were back to their old
values).
I also tried to disable msi globally, but it didn't help either. In
fact, disabling msi globally seemed to cause the issue to appear much
sooner, so the bug is perhaps somewhere else in the kernel.
For now, I have gone back
No, it didn't help. I'm using 2-channel output (the profile is called
"analog stereo duplex").
During the last occurrence of the issue, pulseaudio -k didn't bring back
the system in a completely workable state. The system would stop until I
had pressed a few keys, then it would work for a short ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687590/+files/ProcCpuinfo.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug notification because
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687589/+files/PciMultimedia.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug notification bec
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687588/+files/CurrentDmesg.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug notification becau
apport information
** Attachment added: "Card1.Codecs.codec.0.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687587/+files/Card1.Codecs.codec.0.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug no
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687586/+files/Card0.Codecs.codec.2.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug no
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687585/+files/Card0.Amixer.values.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug noti
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687584/+files/BootDmesg.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug notification because you
apport information
** Attachment added: "ArecordDevices.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687583/+files/ArecordDevices.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug notification b
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.edge.launchpad.net/bugs/659030/+attachment/1687582/+files/AplayDevices.txt
--
Hang when playing sounds (82801JI) after upgrading to maverick
https://bugs.launchpad.net/bugs/659030
You received this bug notification becau
apport information
** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu)
** Tags added: apport-collected
** Description changed:
Binary package hint: pulseaudio
I've recently upgraded from Lucid to Maverick and the sound system does
not work properly anymore. After a few minu
Public bug reported:
Binary package hint: pulseaudio
I've recently upgraded from Lucid to Maverick and the sound system does
not work properly anymore. After a few minutes playing sounds, the sound
output will stutter then stop, and the system will become sluggish. If
I'm fast enough in killing p
** Patch added: "Fix message about maintainer mode"
http://launchpadlibrarian.net/49521439/maintainer.patch
--
Incorrect check message for maintainer mode
https://bugs.launchpad.net/bugs/588475
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
When putting AM_MAINTAINER_MODE([enable]) into a configure.ac file, the
configure message is
checking whether to disable maintainer-specific portions of Makefiles...
$USE_MAINTAINER_MODE
Notice the "disable" part of the message; it is plain wrong. The
AM_MAINTAINER_MODE macr
** Patch added: "Change logging level from DEBUG to WARNING"
http://launchpadlibrarian.net/48957170/debug.patch
--
Debugging flood when using gedit
https://bugs.launchpad.net/bugs/584462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: gedit-latex-plugin
Someone forgot to disable debugging display in package 0.2rc3-2. This
makes using gedit a bit painful due to the constant console flood. (The
Latex plugin is always active, even when no documents are related to
Latex.) The attached patc
It is worse for me. Absolutely no applications, be they C++ or C, are
linked properly. Consider this small example:
#include
#include
__attribute__((noinline))
int f(const char *a, const char *b) { return strcmp(a, b); }
int main() { printf("%x\n", f("foo", "bar")); }
If you compile it dynami
Public bug reported:
Binary package hint: scite
In 2008, Lua support was disabled due to a FTBFS. I don't know how
limiting a change it was for version 1.76, but for version 2, it makes
Scite completely useless (at least for me) since it relies heavily on
Lua. I have successfully built the packag
31 matches
Mail list logo
