Public bug reported:
Binary package hint: linux-image
nsupdate fails with TSIG error claiming BADKEY over a PPP connection
using a Sierra Wireless Compass 597 USB EVDO modem from Sprint. This
modem uses the sierra.ko module instead of the more generic usbserial.ko
module for some other similar d
** Attachment added: "Release info"
http://launchpadlibrarian.net/20187957/lsb_release.log
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
As I am running off the Verizon connection at the moment, I will switch
over to the Sprint modem and then run the relevant diagnostics and
attach those logs along with the failed nsupdate TSIG info.
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received t
** Attachment added: "dmesg output"
http://launchpadlibrarian.net/20188217/dmesg.log
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "lspci -vnvn results"
http://launchpadlibrarian.net/20188244/lspci-vnvn.log
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "lsusb -vvv results"
http://launchpadlibrarian.net/20188256/lsusb-vvv.log
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
** Attachment added: "uname -a results"
http://launchpadlibrarian.net/20188271/uname-a.log
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Attachment added: "/proc/version_signature"
http://launchpadlibrarian.net/20188284/version.log
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "nsupdate log showing TSIG error - BADKEY"
http://launchpadlibrarian.net/20188302/nsupdate_tsig_badkey.log
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which
There seems to be no upstream bug associated with this. Filing this bug
upstream. Will link this bug upstream.
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad.net/bugs/304898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Upstream bug filed and this bug is now tracking.
** Bug watch added: Linux Kernel Bug Tracker #12150
http://bugzilla.kernel.org/show_bug.cgi?id=12150
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12150
Importance: Unknown
Status: Unknown
--
sierra.ko seem
http://www.sierrawireless.com/resources/support/Software/Linux/v1.3.1b_Kernel2.6.24.zip
is the the updated version of this driver from Sierra Wireless (current
version is 1.2.5b as reported by "modinfo sierra"). Any chance of
getting this rolled in?
--
sierra.ko seems not to work with nsupdate
h
I just tested the same scenario against Intrepid with the 2.6.27-9
kernel and get the same results.
Please ignore comment above with sierrawireless.com link. According to
upstream bugzilla entry, this code is already mainlined.
--
sierra.ko seems not to work with nsupdate
https://bugs.launchpad
Please close this bug - the problem lies with Sprint in that they
transparently proxy all DNS requests and redirect them to their own
servers, regardless of client computer configuration. They even spoof
the address of the server you've chosen in the replies - nasty behavior
indeed.
My apologies
Public bug reported:
Binary package hint: gnome-system-tools
Note: I have encountered these problems on each machine on which I've
installed Hardy where I have a dual-NIC machine and I elect to use the
eth1 as the only active NIC.
These problems occur on a freshly installed Hardy box with two N
Similar issue here. U727 recognized under Hardy, not recognized
properly under Intrepid. It seems that the USB storage side works well
enough, but I get the same sorts of errors and behaviors as two comments
up. However, this card used to be supported with the airprime driver.
Since the airprime
Public bug reported:
Standard install of 8.10 with the exception of requiring "acpi=off" -
kernel won't finish booting otherwise. Now I have a quad core machine
booted but with only one active core. This occurs with both 2.6.27-7
and 2.6.27-11.
ProblemType: Bug
Architecture: amd64
DistroRelease
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24343889/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24343890/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24343891/Dependencies.txt
** A
Public bug reported:
Binary package hint: ppp
Setting option "usepeerdns" in pppd should set the USEPEERDNS variable
for /etc/ppp/ip-up.d/usepeerdns. The test in usepeerdns is the
following:
# this variable is only set if the usepeerdns pppd option is being used
[ "$USEPEERDNS" ] || ex
Please close this bug. It does not accurately represent my problem. My
debugging was faulty. The problem is not the usepeerdns script - it
is indeed correct as packaged. The problem is that when the ppp
interface is started from /etc/network/interfaces, the USEPEERDNS
variable is not passed
Same problem with Atheros based card Netgear WG511T.
--
WEP Connection cannot be made
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Since you asked me to test this in gutsy, that's all I've been testing
on. All of my input since your request for gutsy has been from a gutsy
machine. I install gutsy tribe 5 on the affected machine and have been
running updates against it every day. The problem still exists.
Thanks!
Tom
On
Yeah, it's cloaked. I explicitly declare the SSID to nm-applet when
connecting. Search for "woodintlinc" - that's the SSID.
On 9/9/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> For the log ... is that a hidden AP you try to connect to?
>
> --
> NetworkManager fails to finish association to A
*** This bug is a duplicate of bug 50214 ***
https://bugs.launchpad.net/bugs/50214
Color me confused. This has now been marked as a dupe of bug # 50214.
What I find most interesting is that with any other wireless NIC that I
have, this is *not* a problem, just with this Atheros PCI-based NIC
(tm). It
really needs to be pushed through to completion.
Tom
On 9/10/07, Matthew Carpenter <[EMAIL PROTECTED]> wrote:
>
> *** This bug is a duplicate of bug 50214 ***
> https://bugs.launchpad.net/bugs/50214
>
> On Monday 10 September 2007, Tom Wood wrote:
> > ***
Sorry I didn't get back to you on this bug sooner. 4.5 months passed
between when I provided the initial backtrace and your request for a better
stacktrace.. Unfortunately, I no longer have that particular hardware
configuration (no sound card), so I can't provide what's needed.
Just in case I c
Public bug reported:
Binary package hint: network-manager
With a completely updated Feisty install, NetworkManager fails to
associate to my AP running WPA2. My network card is an Atheros-based
AR5212 PCI NIC from Netgear (model WG311T).
This seems to be a timing/race condition problem whereby N
I'll give it a shot with gutsy.
Thanks,
Tom
On 8/31/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> can you please test if you see the same issue with gutsy tribe 5? if you
> don't want to upgrade, please try the live-cd.
>
> Thanks,
>
> - Alexander
>
> ** Changed in: network-manager (Ubuntu)
Same problem with gutsy tribe 5.
I'll attach the relevant portion of the daemon.log that shows the entire
process stalling after stage 2 (device configure) in NetworkManager.
However, dhclient fires right after this and before stage 3 (IP
configure start) even starts. Unless I'm mistaken, the int
's associated either -
at least the error is consistent.
I'll double-check this and answer the rest of your questions when I get back
to that machine either later today or tomorrow.
Thanks for the help!
Tom
On 8/31/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> On Fri, A
#x27;s the same
stuff that's in the daemon.log.
Thanks!
Tom
On 8/31/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> On Fri, Aug 31, 2007 at 10:39:10PM -, Tom Wood wrote:
> > Same problem with gutsy tribe 5.
> >
> > I'll attach the relevant port
Public bug reported:
Binary package hint: hplip
This occurs in Gutsy Tribe 5 as of 9/3/2007 2245 GMT. hplip,
specifically, the hp-toolbox, requires python-qt3.
** Affects: hplip (Ubuntu)
Importance: Undecided
Status: New
--
hplip needs dependency on python-qt3
https://bugs.launc
I will attach two NetworkManager log files. The first, nm-nowork.log.
is the case where I wait out the initial failure. The second, nm.log,
is where I issue the "ifdown ath0; ifup ath0" and get the network to
come up properly.
** Attachment added: "NetworkManager log of the failure"
http://la
** Attachment added: "NetworkManager log of the successful association after
ifdown/ifup"
http://launchpadlibrarian.net/9109004/nm.log
--
NetworkManager fails to finish association to AP
https://bugs.launchpad.net/bugs/133966
You received this bug notification because you are a member of Ubu
This also occurs in 6.06 LTS.
--
/etc/lsb-base-logging.sh causes some initscripts to abort if console is
unavailable
https://bugs.launchpad.net/bugs/104371
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Public bug reported:
Binary package hint: xchat-gnome
After starting xchat-gnome, as the server output reaches the point where
it asks for nickserv authentication, xchat-gnome hangs for a short
while. While it is hung, it doesn't respond normally to anything.
Mousing over the text box at the bot
This is in feisty, updated fully 3/30/2007 at approximately 1900 GMT.
--
xchat-gnome momentarily hangs just after connection established
https://launchpad.net/bugs/99157
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
After booting, the "up route ..." line is not run, as evidenced by
"netstat -r" not showing the route specified. However, running
"/etc/init.d/networking stop" followed by "/etc/init.d/networking start"
after boot runs the "up route ..." line. Race condition of some sort,
perhaps, at boot time?
Changed package to reflect actual source of the problem.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: ifupdown => network-manager
--
adding non-default route in /etc/network/interfaces doesn't work
https://bugs.launchpad.net/bugs/97058
You received this bug notification because you
Tracked the problem down to NetworkManager. Implementing the steps
necessary to turn off NetworkManager as referenced in bug # 82335
alleviates the problem.
As stated in bug # 82335, NetworkManager really needs not to cause this
conflict on a purely statically addressed machine.
--
adding non-d
Public bug reported:
Binary package hint: ifupdown
As I understand it, the proper way to introduce a non-default route at
boot time is to add a "up route add -net ..." line to the network
interface in question to the /etc/network/interfaces file in the
interface stanza, like so:
iface eth0 inet
Here's the interesting section of the backtrace:
ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver
returned error: No such device
ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings
ALSA lib
Below is all text from gdb after Ctrl-C when text input freezes.
Program received signal SIGINT, Interrupt.
[Switching to Thread -1227814224 (LWP 32159)]
0xe410 in __kernel_vsyscall ()
(gdb) thread apply all bt full
Thread 1 (Thread -1227814224 (LWP 32159)):
#0 0xe410 in __kernel_vsyscal
Public bug reported:
Binary package hint: virt-manager
Starting virt-manager from command line generates the attached popup
window containing the error information.
Ubuntu Lucid x86_64 fully updated as of the time of this bug report.
Note that this is an upgrade installation from 8.04 LTS.
virt
** Attachment added: "Screenshot-Error starting Virtual Machine Manager.png"
http://launchpadlibrarian.net/47933145/Screenshot-Error%20starting%20Virtual%20Machine%20Manager.png
--
virt-manager won't run because of wrong version of python-virtinst
https://bugs.launchpad.net/bugs/576394
You r
virtinst is installed and is version 0.500.1-2ubuntu6 .
--
virt-manager won't run because of wrong version of python-virtinst
https://bugs.launchpad.net/bugs/576394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
__version__ = "0.500.1"
--
virt-manager won't run because of wrong version of python-virtinst
https://bugs.launchpad.net/bugs/576394
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.co
It's not in these files. Please include in openvas-server.
--
openvas-server is missing openvas-nvt-sync script
https://bugs.launchpad.net/bugs/486790
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Static route still not honored on a fully updated Karmic system. Have
to still issue "route add default gw x.y.a.b" at root prompt.
--
NetworkManager fails to set IP and route information entered
https://bugs.launchpad.net/bugs/438454
You received this bug notification because you are a member o
** Visibility changed to: Public
--
nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/453457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Exactly what's the purpose behind the setting "Use this connection only
for resources on its own network"? I just don't see the necessity of
having this setting.
--
NetworkManager fails to set IP and route information entered
https://bugs.launchpad.net/bugs/438454
You received this bug notificat
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34283264/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/34283265/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/34283266/ProcStatus.txt
** Visibil
Public bug reported:
On 12.04 Server x86_64, gnuplot still expects to find Liberation fonts
at
/usr/share/fonts/truetype/ttf-liberation
but instead the fonts-liberation package now installs them to
/usr/share/fonts/truetype/liberation
instead.
A quick symlink works around the problem, but gnu
Public bug reported:
Any USB3 connected hard drive may or may not function. A drive may or
may not be seen as attached at boot time. It may or may not be detected
by removing and reinserting the USB3 cable. The behavior is very
inconsistent.
Example:
A 1TB Western Digital drive is correctly d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832319
Title:
inconsistent USB3 support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/832319/+subsc
My apologies. I have this issue with two separate machines, and I got
the two confused in my head when I commented earlier that the USB3 card
didn't appear in the "lspci -vnvn" run. It's there as the last entry in
the above Lspci.txt file.
--
You received this bug notification because you are a
Any chances of getting ipset built into the distributed kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/667834
Title:
ipset userspace tools version mismatched to kernel modules
To manage not
The problem doesn't exist when running the generic testing kernel
2.6.32-0206324519-generic #201108171012.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832319
Title:
inconsistent USB3 support
To m
Same issue with having to wait to login for a minute or so after GDM
starts. It seems to have to do with some delay in lsassd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/820584
Title:
[natty] li
Public bug reported:
FTDI based USB to serial adapter now generates errors in dmesg
("ftdi_sio ttyUSB0: Unable to write latency timer: -32") and fails to
properly utilize data control lines. Previous kernel (2.6.32-24) worked
properly.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/655868/+attachment/1675519/+files/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/655868/+attachment/1675520/+files/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
htt
Problem manifested itself working with a device that requires hardware
flow control. Previous kernel worked fine with this device. This
kernel, however, will not allow for communications with this device.
--
FTDI based USB to serial adapter no longer works
https://bugs.launchpad.net/bugs/655868
The above steps in #13 do not fix the problem for 10.04 LTS. This is
quite a useful feature for firewalls such as shorewall to leverage quick
and easy changes to blacklists.
--
ipset is not useful in ubuntu, because kernel and iptables do not support it.
https://bugs.launchpad.net/bugs/79182
You
Public bug reported:
Binary package hint: ipset
ipset -H ipmap generates
ipset v4.1: Kernel ip_set module is of protocol version 2.I'm of protocol
version 4.
Please upgrade your kernel and/or ipset(8) utillity.
This indicates that the kernel modules installed apt-get install ipset
ipset_sourc
Forgot to mention this is for version 10.04 fully updated as of
10/28/2010.
--
ipset userspace tools version mismatched to kernel modules
https://bugs.launchpad.net/bugs/667834
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
A workaround is to run "rfcomm connect X" as root, where X is the
desired channel (4 in your case, 0 for me, for examples). /dev/rfcommX
will then be created, to which you can then connect.
--
Ubuntu 10.04 Can't open RFCOMM device: Permission denied
https://bugs.launchpad.net/bugs/570692
You rec
66 matches
Mail list logo
