[Bug 1203765] [NEW] gnuplot still looks for Liberation fonts in older ttf-Liberation directory
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 gnuplot itself or the mechanism whereby gnuplot finds its fonts should be fixed. ** Affects: gnuplot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203765 Title: gnuplot still looks for Liberation fonts in older ttf-Liberation directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnuplot/+bug/1203765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832319] Re: inconsistent USB3 support
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/832319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832319] [NEW] inconsistent USB3 support
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 detected at boot. The drive is mounted and functions perfectly. It is then unmounted and physically disconnected from the USB3 cable. An identical drive is then connected to the same USB3 cable and powered up. This drive is never detected. Errors such as [ 4851.210010] xhci_hcd :02:00.0: Timeout while waiting for a slot [ 4851.210016] hub 8-0:1.0: couldn't allocate port 2 usb_device [ 4851.210022] hub 8-0:1.0: cannot disable port 2 (err = -19) [ 4851.215252] xhci_hcd :02:00.0: Host controller not halted, aborting reset. [ 4851.215289] xhci_hcd :02:00.0: USB bus 8 deregistered [ 4851.215400] xhci_hcd :02:00.0: PCI INT A disabled [ 4866.750131] xhci_hcd :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 4866.750179] xhci_hcd :02:00.0: setting latency timer to 64 [ 4866.750184] xhci_hcd :02:00.0: xHCI Host Controller [ 4866.750318] xhci_hcd :02:00.0: new USB bus registered, assigned bus number 8 [ 4866.755402] xhci_hcd :02:00.0: can't setup [ 4866.755410] xhci_hcd :02:00.0: USB bus 8 deregistered [ 4866.755607] xhci_hcd :02:00.0: PCI INT A disabled [ 4866.755610] xhci_hcd :02:00.0: init :02:00.0 fail, -110 [ 4866.755618] xhci_hcd: probe of :02:00.0 failed with error -110 appear in /var/log/messages. Subsequent reboots of the machine detect this drive approximately half of the time. rmmod xhci takes a few seconds. modprobe xhci afterwards does not allow the machine to see the external USB3 drive. Please note that for the contents of this bug report submitted via ubuntu-bug, I have already performed the rmmod/modprobe steps above. It does not appear that the modprobe step found the USB3 card again. I'll manually attach the results of lspci -vnvn to this report after rebooting. The USB card used here is a Vantec 2-Port SuperSPeed USB 3.0 PCI-e Host Card. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image (not installed) Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zeus 2475 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9dc000 irq 16' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,10280211,00100400' Controls : 30 Simple ctrls : 18 Date: Tue Aug 23 15:50:31 2011 HibernationDevice: RESUME=UUID=d587d6c2-d3c6-44c7-86f2-f8f9d4965ae3 MachineType: Dell Inc. OptiPlex 755 ProcCmdLine: root=UUID=419882ba-beaf-4370-8c51-f24aca1c7d60 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.7 RfKill: SourcePackage: linux dmi.bios.date: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0GM819 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0GM819:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug lucid needs-upstream-testing -- 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/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832319] Re: inconsistent USB3 support
-- 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/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832319] Re: inconsistent USB3 support
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 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/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667834] Re: ipset userspace tools version mismatched to kernel modules
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/667834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820584] Re: [natty] likewise-open problems on laptop systems
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] likewise-open problems on laptop systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/820584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79182] Re: ipset is not useful in ubuntu, because kernel and iptables do not support it.
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 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/listinfo/ubuntu-bugs
[Bug 667834] [NEW] ipset userspace tools version mismatched to kernel modules
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_source apt-cache search ipset apt-cache search ipset | less apt-get install ipset-source m-a prepare m-a build ipset m-a install ipset are a mismatch. ** Affects: ipset (Ubuntu) Importance: Undecided Status: New -- 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667834] Re: ipset userspace tools version mismatched to kernel modules
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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655868] [NEW] FTDI based USB to serial adapter no longer works
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-image (not installed) Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: woodt 2581 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9dc000 irq 16' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,10280211,00100400' Controls : 30 Simple ctrls : 18 Date: Wed Oct 6 13:51:45 2010 HibernationDevice: RESUME=UUID=d587d6c2-d3c6-44c7-86f2-f8f9d4965ae3 MachineType: Dell Inc. OptiPlex 755 ProcCmdLine: root=UUID=419882ba-beaf-4370-8c51-f24aca1c7d60 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.1 RfKill: SourcePackage: linux dmi.bios.date: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0GM819 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0GM819:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid needs-upstream-testing regression-release -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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/listinfo/ubuntu-bugs
[Bug 655868] Re: FTDI based USB to serial adapter no longer works
** 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 https://bugs.launchpad.net/bugs/655868/+attachment/1675521/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675522/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675523/+files/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675524/+files/CurrentDmesg.txt ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675525/+files/IwConfig.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675526/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675527/+files/Lsusb.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675528/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675529/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675530/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675532/+files/ProcModules.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675537/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675541/+files/UdevLog.txt ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/655868/+attachment/1675542/+files/WifiSyslog.txt -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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/listinfo/ubuntu-bugs
[Bug 655868] Re: FTDI based USB to serial adapter no longer works
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 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/listinfo/ubuntu-bugs
[Bug 570692] Re: Ubuntu 10.04 Can't open RFCOMM device: Permission denied
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 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/listinfo/ubuntu-bugs
[Bug 576394] [NEW] virt-manager won't run because of wrong version of python-virtinst
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-manager 0.8.2-2ubuntu8 python-virtinst 0.500.1-2ubuntu6 ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576394] Re: virt-manager won't run because of wrong version of python-virtinst
** 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 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/listinfo/ubuntu-bugs
[Bug 576394] Re: virt-manager won't run because of wrong version of python-virtinst
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576394] Re: virt-manager won't run because of wrong version of python-virtinst
__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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 486790] Re: openvas-server is missing openvas-nvt-sync script
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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459392] Re: update-manager crashed with RuntimeError in module()
** 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 ** Visibility changed to: Public -- update-manager crashed with RuntimeError in module() https://bugs.launchpad.net/bugs/459392 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/listinfo/ubuntu-bugs
[Bug 438454] Re: NetworkManager fails to set IP and route information entered
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 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/listinfo/ubuntu-bugs
[Bug 453457] Re: nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
** 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438454] Re: NetworkManager fails to set IP and route information entered
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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398793] [NEW] usepeerdns option in pppd doesn't work
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 ] || exit 0 which is clearly wrong, as if USEPEERDNS is set, the script exits immediately. The test should be # this variable is only set if the usepeerdns pppd option is being used [ ! $USEPEERDNS ] || exit 0 ** Affects: ppp (Ubuntu) Importance: Undecided Status: New ** Tags: intrepid ** Tags added: intrepid -- usepeerdns option in pppd doesn't work https://bugs.launchpad.net/bugs/398793 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/listinfo/ubuntu-bugs
[Bug 398793] Re: usepeerdns option in pppd doesn't work
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 to the script properly, unlike when starting the ppp daemon via pon. I'll file a separate bug for this error. My apologies. ** Changed in: ppp (Ubuntu) Status: New = Invalid -- usepeerdns option in pppd doesn't work https://bugs.launchpad.net/bugs/398793 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/listinfo/ubuntu-bugs
[Bug 348646] [NEW] SMP is disabled on Dell Optiplex 960 with quad core
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: Ubuntu 8.10 Package: linux-image-2.6.27-11-generic 2.6.27-11.27 ProcCmdLine: User Name=UUID=b0bbaa4c-85db-4010-a3e5-a1546851e584 ro acpi=off ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-11.27-generic SourcePackage: linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- SMP is disabled on Dell Optiplex 960 with quad core https://bugs.launchpad.net/bugs/348646 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/listinfo/ubuntu-bugs
[Bug 348646] Re: SMP is disabled on Dell Optiplex 960 with quad core
** 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 ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/24343892/HalComputerInfo.txt ** Attachment added: LsUsb.txt http://launchpadlibrarian.net/24343894/LsUsb.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/24343895/Lspci.txt ** Attachment added: ProcCpuInfo.txt http://launchpadlibrarian.net/24343896/ProcCpuInfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/24343897/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/24343898/ProcModules.txt -- SMP is disabled on Dell Optiplex 960 with quad core https://bugs.launchpad.net/bugs/348646 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/listinfo/ubuntu-bugs
[Bug 284049] Re: Novatel U727 USB Adapter Boot Problem
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 module is now gone, and most of its remnants scattered amongst other drivers, it seems that the U727 should be supported under option.ko. However, option.ko does not recognize this card, so no ttyUSBx ports are created. This should be a relatively simple fix - add the vendor and product IDs to option.c in the kernel. This may need to be reported upstream. -- Novatel U727 USB Adapter Boot Problem https://bugs.launchpad.net/bugs/284049 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/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
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.net/bugs/304898 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/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
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 for filing this based on my erroneous troubleshooting. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] [NEW] sierra.ko seems not to work with nsupdate
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 devices, such as the USB720 modem from Verizon, over which nsupdate works properly. So the problem is either with the kernel module somehow not handling the nsupdate TSIG packets properly or with Sprint themselves. I have no problems with any of the other networking functions I've tested over Sprint, including http, https, and ssh (inbound and outbound). The only thing that has failed is the TSIG transaction during nsupdate, where it complains about a bad key. That same key pair works across Verizon as well as through eth0 when hardwired to a LAN. Therefore, I don't believe the problem is related to the IP stack or nsupdate themselves. ProblemType: Bug Architecture: i386 Date: Wed Dec 3 13:32:26 2008 Dependencies: DistroRelease: Ubuntu 8.04 Package: linux-image None [modified: /var/lib/dpkg/info/linux-image.list] PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 SourcePackage: linux-meta Uname: Linux 2.6.24-22-generic i686 ** Affects: linux-ports-meta (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
** 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
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 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/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
** 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
** 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
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 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304898] Re: sierra.ko seems not to work with nsupdate
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 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234111] [NEW] network-admin fails to correctly edit /etc/hosts, causes sudo to fail
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 NICs: eth0 is onboard and unused, eth1 is a PCI-based NIC and is the one that is connected to the LAN. /etc/hosts immediately after the installation contains the following (ignoring the IPv6 stuff): 127.0.0.1 localhost 127.0.1.1 boxname I am assuming that boxname is under 127.0.1.1 because eth1 is the active NIC. I am not sure about this. At this point in network-manager under Connections I add the appropriate static IP address to eth1. This works as evidenced by changes made to /etc/network/interfaces and the output from ifconfig -a. Setting the domain name under the general tab in network-admin changes /etc/hosts to the following: 127.0.0.1 localhost boxname.example.com 127.0.1.1 boxname.example.com Any attempts at putting boxname in the hosts file using network-admin's host tab result in boxname.example.com being put in the file instead. Using network-admin, there is no way to add boxname as a non-FQDN name in /etc/hosts as an alias to either localhost (127.0.0.1) or boxname.example.com (127.0.1.1). I consider appending the domain name wrong in this context, in that it only appends the domain name for boxname. Any other host that I define an address for in this manner does not automatically have the domain name appended. Attempting a sudo at this point: sudo: unable to resolve host boxname Any gksudo attempt hangs indefinitely. Checking /etc/resolv.conf shows that it is correct: domain example.com nameserver 10.11.12.13 hostname returns the non-FQDN hostname. pinging the non-FQDN hostname results in ping: unknown host boxname pinging boxname.example.com is successful, however. So is pinging the static IP address I assigned to eth1. I cannot ping any other machines by name or by IP address, however, even though ifconfig eth1 shows that the interface is up. /etc/nsswitch.conf indicates that the hosts file is to be used before DNS for hostname resolution. This works only for hostnames not associated with the loopback addresses. However, pings do not work to these non-local names, even though their addresses are resolved from the hosts file. Another interesting note: eth0 is up, even though it's not configured in my case. There's no way to switch it off (ifconfig down) with network-manager either. Unchecking roaming mode requires some level of configuration be done to the interface, which I don't want/need to do. I merely want it down. My observations are that there are several issues that could be resolved simply by two things: First, assign the FQDN and it's non-FQDN both to the 127.0.0.1 loopback interface, not the 127.0.1.1. Second, any network interface should be able to be disabled via network-manager. My fix in a previous instance for these problems was to disable the unused onboard NIC in the BIOS and fixing /etc/hosts and /etc/network/interfaces to reflect the now single-NIC (eth0) configuration. I'd rather work through a configuration fix for this without the BIOS manipulation. This would probably involve rebooting the machine into recovery mode, hand editing /etc/hosts with the non- FQDN name of the machine associated with 127.0.0.1 (not 127.0.1.1) and possibly hand editing /etc/network/interfaces to make sure that eth0 is down at boot. ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- network-admin fails to correctly edit /etc/hosts, causes sudo to fail https://bugs.launchpad.net/bugs/234111 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/listinfo/ubuntu-bugs
Re: [Bug 133966] Re: NetworkManager fails to finish association to AP
*** This bug is a duplicate of bug 50214 *** https://bugs.launchpad.net/bugs/50214 Matthew, I'm astounded by this whole experience. This doesn't seem to be an easy bug to track down. I've spent a fair amount of time on this myself and don't completely grok the problem, other than I suspect it is some sort of race condition/timing error/insufficient necessary conditions checking between iwconfig actually completing the AP association and ifup bringing up the interface (told you I was confused). This would explain the differences in the behavior of NetworkManager among the network cards - it's the drivers for the cards themselves that differ in this situation. Therein lies the big problem with wireless on Linux in general - too many cards with too many different ways of bringing them to life. You've got everything from completely open source drivers like the Ralink stuff to the Atheros closed source HAL to the fwcutter requirement for the firmware for the Broadcom cards to ndiswrapper for the mongrels. There are a lot of paths here that may need to be explored and eventually need to be consolidated. Frankly, I'm shocked that NetworkManager works as well as it does. That being said, it's just not yet good enough - it doesn't Just Work (tm). I'm probably going to uncloak my AP to get around this right now. With tools like Kismet that's a pretty weak defense anyway. But I have clients that still require cloaked APs as part of their approved security measures. This issue really needs a lot more attention than it's been given over the last year or so. I'm afraid that it's working well enough for most folks that it's dropped off the priority list for the Powers That Be (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: *** 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 that has the same chipset in it as a PCMCIA-based NIC from the same manufacturer (Netgear WG311T is PCI and the PCMCIA is a WG511T). One Broadcom NIC that I have (Linksys WMP54GS) works without a hitch on this network. So do my Orinoco Classic Gold 802.11b-only PCMCIA NICs. And last, but not least, my Broadcom-based Compaq NX9010 (Broadcom BCM4306) works like a charm against this cloaked network under Feisty. Only the WG311T does not work without the ifup/ifdown. Under Feisty and Gutsy, the only two versions I've tried, the WG311T requires the ifup/ifdown trick to work. Maybe that's a good clue to start figuring out what's wrong with NetworkManager, if indeed that is the culprit. To repeat, all my other wireless NICs work fine against my cloaked network under either Edgy or Feisty. Thanks for looking into this, Alexander. It will be fantastic when we finally get to put this one to rest. I'm having this issue with an IPW3945 using WPA on Feisty, so this is not an Atheros bug only. What's disturbing is that the bug has been around for a year and it is still undecided how important it is! -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a direct subscriber of the bug. -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 99157] Re: xchat-gnome momentarily hangs just after connection established
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 can resurrect this system (and I'll try), for which programs do I need to load the -dbg or -dbgsym packages? esound? xchat-gnome? Both? Others too? Thanks! On 9/11/07, Pedro Villavicencio [EMAIL PROTECTED] wrote: Closing this report for now since no more information has been provided, feel free to re open it if you may provide the info we asked for. ** Changed in: esound (Ubuntu) Status: Incomplete = Invalid -- xchat-gnome momentarily hangs just after connection established https://bugs.launchpad.net/bugs/99157 You received this bug notification because you are a direct subscriber of the bug. -- xchat-gnome momentarily hangs just after connection established https://bugs.launchpad.net/bugs/99157 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133966] Re: NetworkManager fails to finish association to AP
*** 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 that has the same chipset in it as a PCMCIA-based NIC from the same manufacturer (Netgear WG311T is PCI and the PCMCIA is a WG511T). One Broadcom NIC that I have (Linksys WMP54GS) works without a hitch on this network. So do my Orinoco Classic Gold 802.11b-only PCMCIA NICs. And last, but not least, my Broadcom-based Compaq NX9010 (Broadcom BCM4306) works like a charm against this cloaked network under Feisty. Only the WG311T does not work without the ifup/ifdown. Under Feisty and Gutsy, the only two versions I've tried, the WG311T requires the ifup/ifdown trick to work. Maybe that's a good clue to start figuring out what's wrong with NetworkManager, if indeed that is the culprit. To repeat, all my other wireless NICs work fine against my cloaked network under either Edgy or Feisty. Thanks for looking into this, Alexander. It will be fantastic when we finally get to put this one to rest. -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 133966] Re: NetworkManager fails to finish association to AP
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 AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a direct subscriber of the bug. -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 133966] Re: NetworkManager fails to finish association to AP
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 Fri, 2007-09-07 at 10:37 +, Alexander Sack wrote: do you have a chance to test this in gutsy? -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137168] hplip needs dependency on python-qt3
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.launchpad.net/bugs/137168 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133966] Re: NetworkManager fails to finish association to AP
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://launchpadlibrarian.net/9109003/nm-nowork.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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133966] Re: NetworkManager fails to finish association to AP
** 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 133966] Re: NetworkManager fails to finish association to AP
I'm not at that machine at the moment, but I can tell you that it's not associated. The two lights on the NetworkManager applet are both gray. As I gather, the bottom one indicates whether the NIC is associated to the AP. And IIRC iwconfig ath0 doesn't indicate that it'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, Aug 31, 2007 at 10:39:10PM -, Tom Wood wrote: 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 interface is not up at this point, at least not the IP stack, but dhclient is still started. The ifdown/ifup trick works to bring the interface truly up, so stages 3-5 finish in short order thereafter. As always, I'll be glad to provide any more details you need. When you are at Aug 31 22:12:48 ubuntu NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. Aug 31 22:12:50 ubuntu avahi-daemon[8042]: Registering new address record for fe80::218:4dff:fe7a:59c0 on ath0.*. you should have about 10 seconds to capture output of iwconfig ath0 Can you do that please? Is it associated at that point? Do you see more of relevance in /var/log/syslog at that point (or before/after)? - Alexander -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a direct subscriber of the bug. -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 133966] Re: NetworkManager fails to finish association to AP
It's absolutely not associated. It hunts around for the correct channel and does find the correct frequency, but it just doesn't go onward to stage 3 and finish the association, unless I time the ifdown/ifup just right. There are no other clues in /var/log/syslog worth mentioning. It'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 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 interface is not up at this point, at least not the IP stack, but dhclient is still started. The ifdown/ifup trick works to bring the interface truly up, so stages 3-5 finish in short order thereafter. As always, I'll be glad to provide any more details you need. When you are at Aug 31 22:12:48 ubuntu NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. Aug 31 22:12:50 ubuntu avahi-daemon[8042]: Registering new address record for fe80::218:4dff:fe7a:59c0 on ath0.*. you should have about 10 seconds to capture output of iwconfig ath0 Can you do that please? Is it associated at that point? Do you see more of relevance in /var/log/syslog at that point (or before/after)? - Alexander -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a direct subscriber of the bug. -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 133966] Re: NetworkManager fails to finish association to AP
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) Importance: Undecided = Medium Status: New = Incomplete -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a direct subscriber of the bug. -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133966] Re: NetworkManager fails to finish association to AP
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 interface is not up at this point, at least not the IP stack, but dhclient is still started. The ifdown/ifup trick works to bring the interface truly up, so stages 3-5 finish in short order thereafter. As always, I'll be glad to provide any more details you need. Thanks! ** Attachment added: daemon.log from affected machine. Interesting stuff starts about line 86. http://launchpadlibrarian.net/9082665/daemon.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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133966] NetworkManager fails to finish association to AP
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 NetworkManager doesn't seem to understand that it can proceed with the association and the rest of its startup process. The reason I state this is that if I run ifdown ath0 and immediately run ifup ath0 at the right time after NetworkManager has started, NetworkManager will finish and ath0 comes up associated with the AP, dhcp'ed address and all. I can't clearly define right time at present. These seems to be a narrow window of opportunity right after the CTRL_IFACE monitor attached log statement from NetworkManager appears to pull off this workaround. If you miss the window, restarting NetworkManager (via /etc/init.d/dbus restart and or directly restarting NetworkManager when running it manually) and getting the timing just right with the ifdown/ifup pair will bring the network up. I will be happy to provide any log files that you wish to see. Please indicate what I can send to help you understand this problem. Items of note: I've already checked /etc/network/interfaces. I've commented out everything except ath0 and wifi0 entries. Those two are auto dhcp. I have no manually defined wpasupplicant.conf. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104371] Re: /etc/lsb-base-logging.sh causes some initscripts to abort if console is unavailable
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 list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99157] Re: xchat-gnome momentarily hangs just after connection established
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_vsyscall () No symbol table info available. #1 0xb754a727 in socket () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0xb6f7e32e in have_ipv6 () from /usr/lib/libesd.so.0 No symbol table info available. #3 0xb6f798d1 in ?? () from /usr/lib/libesd.so.0 No symbol table info available. #4 0xb7d94174 in ?? () from /usr/lib/libgthread-2.0.so.0 No symbol table info available. #5 0x0001 in ?? () No symbol table info available. #6 0xbfecefe8 in ?? () No symbol table info available. #7 0xb76057b4 in g_str_equal () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #8 0xb6f7a6e7 in esd_open_sound () from /usr/lib/libesd.so.0 No symbol table info available. #9 0xb7dd0314 in ?? () from /usr/lib/libgnome-2.so.0 No symbol table info available. #10 0x in ?? () No symbol table info available. (gdb) -- xchat-gnome momentarily hangs just after connection established https://bugs.launchpad.net/bugs/99157 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99157] Re: xchat-gnome momentarily hangs just after connection established
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 conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default These lines are repeated 1200 times (!) in the course of my 1 hour xchat run. And, no, this machine does not have a sound card, which fits perfectly with the trace above. ** Attachment added: gdb backtrace of xchat-gnome http://librarian.launchpad.net/7132331/gdb-xchat-gnome.txt -- xchat-gnome momentarily hangs just after connection established https://bugs.launchpad.net/bugs/99157 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97058] Re: adding non-default route in /etc/network/interfaces doesn't work
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? ** Description changed: 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 static address 10.1.1.123 netmask 255.255.255.0 network 10.1.1.0 broadcast 10.1.1.255 gateway 10.1.1.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.50 dns-search example.com up route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.1.1.2 However, the up route line doesn't get executed. As a separate but related issue, there's no way using System-Administration-Network to add a non-default route either. That - would be a nice RFQ. + would be a nice idea for an enhancement. -- adding non-default route in /etc/network/interfaces doesn't work https://bugs.launchpad.net/bugs/97058 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97058] Re: adding non-default route in /etc/network/interfaces doesn't work
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 are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97058] Re: adding non-default route in /etc/network/interfaces doesn't work
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-default route in /etc/network/interfaces doesn't work https://bugs.launchpad.net/bugs/97058 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99157] xchat-gnome momentarily hangs just after connection established
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 bottom of the screen causes the mouse cursor to disappear while in that box. Any typing in that box is no further displayed, even if you're in the middle of typing in the customary /msg nickserv identify whatever - it simply stops accepting input at the time of the hang. Attempting to kill the process immediately fails, generating the standard Gnome hung application popup. If one is patient enough (~ one minute or so), operation returns to normal. ** Affects: xchat-gnome (Ubuntu) Importance: Undecided Status: Unconfirmed -- 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
[Bug 99157] Re: xchat-gnome momentarily hangs just after connection established
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
[Bug 97058] adding non-default route in /etc/network/interfaces doesn't work
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 static address 10.1.1.123 netmask 255.255.255.0 network 10.1.1.0 broadcast 10.1.1.255 gateway 10.1.1.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.50 dns-search example.com up route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.1.1.2 However, the up route line doesn't get executed. As a separate but related issue, there's no way using System-Administration-Network to add a non-default route either. That would be a nice RFQ. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: Unconfirmed -- adding non-default route in /etc/network/interfaces doesn't work https://launchpad.net/bugs/97058 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48473] Re: WEP Connection cannot be made
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
