[Bug 1169984] Re: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV
Ubuntu keeps releasing new kernels, and every one re-breaks my HDMI sound. Thank goodness for Fabrizio and his comment #8. Although applying it over and over again is becoming tedious. Security is an important thing, but it is not the only important thing. Do any Linux distros actually care about working audio? (Just asking for, um, a friend.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169984 Title: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1169984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174948] [NEW] ZRTP support not enabled
Public bug reported: The current Ubuntu build of linphone packages (3.5.2-10) does not include ZRTP support for secure communications. It does include SRTP, but that mode sends encryption keys in the clear, which kind of defeats the purpose. (Unless you use TCP/TLS for the SIP connection... But even that is not entirely secure from man-in-the- middle attacks.) The current version of linphone does support ZRTP, provided the libzrtpcpp library is available at compilation time. This is clearly a good feature to have for security and also for interoperation with other ZRTP-enabled IP telephony clients. Please fix the packaging to compile in ZRTP support for linphone. Thanks. ** Affects: linphone (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/1174948 Title: ZRTP support not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linphone/+bug/1174948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174948] Re: ZRTP support not enabled
Er, make that: ...provided the libzrtpcpp-dev package is installed and --enable-zrtp is passed to the 'configure' script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174948 Title: ZRTP support not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linphone/+bug/1174948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940063] Re: Add iscan configuration to Jockey
The current Jockey repository has moved to download.ebz.epson.net, so the /etc/apt/souces.list.d/jockey.list file you want is: deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main This has more recent versions than the repository at linux.avasys.jp. See http://download.ebz.epson.net/faq/linux/faq_li_00027.html Also, the current version of iscan is 2.29.1, but I have only been able to download it via http://download.ebz.epson.net/dsc/search/01/search/ (select Linux for the OS and then enter any Epson printer model, e.g. NX110) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940063 Title: Add iscan configuration to Jockey To manage notifications about this bug go to: https://bugs.launchpad.net/jockey/+bug/940063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597068] Re: Missing Myricom 10GigE firmware
Unfortunately, I no longer have an Ubuntu system with a Myricom card. (The original system was a prototype for work, since dismantled.) So I will be unable to test this package. Unless you can find someone else to test, you might want to close this bug. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/597068 Title: Missing Myricom 10GigE firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/597068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882274] Re: Community engagement is broken
All I want is to move the d@#% launch bar to a different side of the screen. I can do this with Windows. I can do this with OS X. I can do this with GNOME. I cannot do this with Unity, because some billionaire says it does not fit with his vision. Remind me again why I use open source software? Oh, right, because it puts me in control... Utterly ludicrous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882274 Title: Community engagement is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/882274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668415] Re: Movement of Unity launcher
My left-side monitor is an HDTV. I normally keep it (a) set to a different input and (b) turned off. So, with 11.10, in order to launch an application I have to: Turn on the HDTV Select the computer as input source on the HDTV Open the launcher and launch the application Change the input back on the HDTV Turn off the HDTV For the love of all that is sane in user interface design, PLEASE RE- OPEN THIS BUG. There is a fine line between providing user-friendly defaults and taking away user control. This decision crosses over that line. Way, way over. I have been using Ubutnu since Dapper. It would take a lot to force me to change distributions. But this will do it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668415 Title: Movement of Unity launcher To manage notifications about this bug go to: https://bugs.launchpad.net/null/+bug/668415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262751] Re: Webalizer package needs updated to current release.
Two years and counting... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/262751 Title: Webalizer package needs updated to current release. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604137] [NEW] mounted-varrun.conf has wrong path for sendsigs.omit.d
Public bug reported: Binary package hint: mountall /etc/init/mounted-varrun.conf has the following line: mkdir -p /var/run/sendsigs.omit.d But the /etc/init.d/sendsigs script (from the initscripts package) -- which reads this directory -- expects to find it in /lib/init/rw/sendsigs.omit.d. All other init scripts -- like /etc/init/portmap.conf, /etc/init.d/open- iscsi, and /etc/init.d/wpa-ifupdown -- also expect this directory to exist under /lib/init/rw. The result is several subtle bugs afflicting both Lucid and Maverick. For example, my machine that uses open-iscsi hangs every time I try to reboot it: https://bugs.launchpad.net/bugs/603760 Someone needs to figure out whether sendsigs.omit.d belongs under /var/run or under /lib/init/rw, and fix the other scripts. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: mountall 2.15 ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3 Uname: Linux 2.6.35-6-generic x86_64 Architecture: amd64 Date: Sat Jul 10 15:29:15 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100602.2) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mountall ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- mounted-varrun.conf has wrong path for sendsigs.omit.d https://bugs.launchpad.net/bugs/604137 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 604137] Re: mounted-varrun.conf has wrong path for sendsigs.omit.d
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/51697361/Dependencies.txt -- mounted-varrun.conf has wrong path for sendsigs.omit.d https://bugs.launchpad.net/bugs/604137 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 603760] Re: Nobody creates /lib/init/rw/sendsigs.omit.d
Addendum: I changed my mind; this is not necessarily a bug in initscripts. It could be a bug in mountall, which creates sendsigs.omit.d under /var/run: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/604137 The bug is that the various init scripts are not in agreement. Please make up your minds where the sendsigs.omit.d directory belongs and then fix all init scripts to be consistent about it. Until then, anybody using open-iscsi cannot even reboot their systems. Thanks. -- Nobody creates /lib/init/rw/sendsigs.omit.d https://bugs.launchpad.net/bugs/603760 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 603760] [NEW] Nobody creates /lib/init/rw/sendsigs.omit.d
Public bug reported: Binary package hint: sysvinit Release: lucid Version: 2.87dsf-4ubuntu17 /etc/init.d/sendsigs reads the /lib/init/rw/sendsigs.omit.d directory for a list of files containing PIDs to omit when killing all processes during shutdown/reboot. Some init scripts (e.g., open-iscsi and wpa-ifupdown) attempt to use this directory to protect themselves from being killed. But on a stock Lucid system, nobody creates this directory. Consequently, there are problems. For example, any system using open- iscsi is unable to shut down or reboot: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/541512 This is clearly a bug in the initscripts package. Since the sendsigs script is the only consumer of the /lib/init/rw/sendsigs.omit.d directory, it ought to be responsible for creating it; or at least, some other mechanism in the initscripts package should be responsible for doing so. ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- Nobody creates /lib/init/rw/sendsigs.omit.d https://bugs.launchpad.net/bugs/603760 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 541512] Re: open-iscsi shutdown failure due to missing dir
I can confirm that the patch in Bug 567143 (mkdir -p /lib/init/rw/sendsigs.omit.d in /etc/init.d/open-iscsi) works around this issue. But open-iscsi is not the only init script that relies on /lib/init/rw/sendsigs.omit.d, so it is not open-iscsi's job to create it. This is clearly a bug in the initscripts package (source package sysvinit), and I have opened a bug against that package: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/603760 -- open-iscsi shutdown failure due to missing dir https://bugs.launchpad.net/bugs/541512 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 597068] Re: Missing Myricom 10GigE firmware
On Mon, Jun 28, 2010 at 1:09 PM, Chase Douglas chase.doug...@canonical.com wrote: Please test the attached linux-firmware package. ** Attachment added: linux-firmware_1.38~test1_all.deb http://launchpadlibrarian.net/51059111/linux-firmware_1.38%7Etest1_all.deb Unfortunately, this did not work... It installs the firmware files, but they do not get loaded at boot. However, if I move the files up one directory level -- sudo mv /lib/firmware/myricom/* /lib/firmware -- then they are found. Does the driver need to request myricom/myri10ge_whatever.dat instead of myri10ge_whatever.dat? -- Missing Myricom 10GigE firmware https://bugs.launchpad.net/bugs/597068 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 597068] Re: Missing Myricom 10GigE firmware
WHOOPS! My mistake. I tested the new package on Lucid and it did not work... But on Maverick, it fixes the problem perfectly. I apologize for the screw-up. Thank you! -- Missing Myricom 10GigE firmware https://bugs.launchpad.net/bugs/597068 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 597068] [NEW] Missing Myricom 10GigE firmware
Public bug reported: Binary package hint: linux-firmware Maverick Meercat includes the myri10ge driver, but it is missing the associated firmware. Current firmware package is available from the vendor: http://www.myri.com/scs/download-Myri10GE-firmware-only.html Without these firmware files, the system logs messages like the following at boot: [5.434041] myri10ge :07:00.0: firmware: requesting myri10ge_eth_z8e.dat [5.434889] myri10ge :07:00.0: Unable to load myri10ge_eth_z8e.dat firmware image via hotplug [5.434894] myri10ge :07:00.0: hotplug firmware loading failed [5.434967] myri10ge :07:00.0: Successfully adopted running firmware [5.434971] myri10ge :07:00.0: Using firmware currently running on NIC. For optimal [5.434975] myri10ge :07:00.0: performance consider loading optimized firmware [5.434978] myri10ge :07:00.0: via hotplug ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-firmware 1.37 ProcVersionSignature: Ubuntu 2.6.34-5.13-generic 2.6.34 Uname: Linux 2.6.34-5-generic x86_64 Architecture: amd64 Date: Mon Jun 21 17:06:44 2010 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100602.2) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-firmware ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Missing Myricom 10GigE firmware https://bugs.launchpad.net/bugs/597068 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 597068] Re: Missing Myricom 10GigE firmware
Addendum: Note that the file name requested by the driver is myri10ge_eth_z8e.dat, while the file name in the vendor package is just eth_z8e.dat. The vendor package contains four .dat files corresponding to different cards. They are all used by the myri10ge driver, and they all need to have myri10ge_ prepended to their names when deposited under /lib/firmware. -- Missing Myricom 10GigE firmware https://bugs.launchpad.net/bugs/597068 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 204850] Re: gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start()
Thank you, Dmitry! Your patch works great (modulo one problem; see
below).
In case anybody else wants to fix this for themselves, here are a step-
by-step instructions to apply the patch:
- Download Dmitry's patch from the link above
- Become root
- Edit /etc/apt/sources.list to ensure you have a deb-src line matching your
deb line for the main Ubuntu archive
$ apt-get update # (necessary if you modified sources.list)
$ apt-get build-dep gnome-settings-daemon
$ apt-get source gnome-settings-daemon
$ cd gnome-settings-daemon-2.22.1
$ cp /path/to/09_extra_touchpad_options_fix.patch ./debian/patches
$ ./debian/rules binary
$ dpkg -i ../gnome-settings-daemon_2.22.1-0ubuntu1_amd64.deb
That's it. To ensure your custom package does not get replaced when you
apply updates, you might want to run aptitude hold gnome-settings-
manager.
Now, the problem. Although this fixes the segfault, it exposes the next
issue, which is that whenever I close any window, the gnome-settings-
manager dies with an X error. I worked around this by applying the
patch below and rebuilding, but this is almost certainly the wrong
fix, breaks something when not being used in a VNC session, etc. I am
only including it because a) it works for me and b) it might help an
expert locate and fix the issue for real.
Thank you again, Dmitry. The blinking cursor in gnome-terminal was
driving me nuts. :-)
diff -u -r
gnome-settings-daemon-2.22.1-orig/plugins/keyboard/gsd-keyboard-xkb.c
gnome-settings-daemon-2.22.1/plugins/keyboard/gsd-keyboard-xkb.c
--- gnome-settings-daemon-2.22.1-orig/plugins/keyboard/gsd-keyboard-xkb.c
2008-03-27 06:11:19.0 -0700
+++ gnome-settings-daemon-2.22.1/plugins/keyboard/gsd-keyboard-xkb.c
2008-08-25 10:57:46.0 -0700
@@ -279,7 +279,7 @@
GdkEvent * event)
{
XEvent *xevent = (XEvent *) xev;
-xkl_engine_filter_events (xkl_engine, xevent);
+/*xkl_engine_filter_events (xkl_engine, xevent);*/
return GDK_FILTER_CONTINUE;
}
--
gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start()
https://bugs.launchpad.net/bugs/204850
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 119982] Re: amd64 vncconfig crashes
Thankfully, since nothing has changed in vnc4server, Dossy Shiobara's Gutsy patch (above) also works just fine for Hardy. I followed a slightly different procedure: - Download Dossy's vnc4-amd64-vncconfig-bug-119982.patch above - Become root - Make sure /etc/apt/sources.list has a deb-src line to match its deb line for the main Ubuntu archive, including the universe label. For example: deb-src http://us.archive.ubuntu.com/ubuntu/ hardy universe main restricted $ apt-get update # (necessary if you modified sources.list) $ apt-get build-dep vnc4server $ apt-get source vnc4server # (runs dpkg-source -x automagically) $ patch -p0 /path/to/vnc4-amd64-vncconfig-bug-119982.patch $ cd vnc4-4.1.1+xorg1.0.2 $ debian/rules binary $ dpkg -i ../vnc4server_4.1.1+xorg1.0.2-0ubuntu7_amd64.deb -- amd64 vncconfig crashes https://bugs.launchpad.net/bugs/119982 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 119982] Re: amd64 vncconfig crashes
Ditto. This is (still!) broken on amd64 Hardy. Even though the bug was diganosed and fixed in Fedora in Oct 2006 and on this ticket Oct 2007. Does Ubuntu have a VNC maintainer? -- amd64 vncconfig crashes https://bugs.launchpad.net/bugs/119982 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 204850] Re: gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start()
Same issue here. On amd64, under Xvnc4, when I run gnome-settings- daemon, I get: ** (gnome-settings-daemon:1422): WARNING **: The X Server does not support the XRandR extension. Runtime resolution changes to the display size are not available. ** (gnome-settings-daemon:1422): WARNING **: numlock: XkbQueryExtension returned an error ** (gnome-settings-daemon:1422): WARNING **: Neither XKeyboard not Xfree86's keyboard extensions are available, no way to support keyboard autorepeat rate settings Shutdown failed or nothing to shut down. Xlib: extension XInputExtension missing on display :17.0. Segmentation fault (core dumped) The core file produces the same backtrace (gsd_mouse_manager_start) described in this bug. -- gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start() https://bugs.launchpad.net/bugs/204850 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 62751] Re: Upstart doesn't activate luks volumes (also non luks) in cryptsetup
What version of Ubuntu are you using? On mine (7.10 aka. Gutsy), /etc/init.d/urandom already propagates the random seed across reboots in /var/lib/urandom/random-seed. This should make /dev/urandom very safe to use, assuming that file itself is never compromised. -- Upstart doesn't activate luks volumes (also non luks) in cryptsetup https://bugs.launchpad.net/bugs/62751 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 62751] Re: Upstart doesn't activate luks volumes (also non luks) in cryptsetup
It's a long story that depends on how you define random and secure. And this is really the wrong forum for this question and answer. But I'll give it a whack anyway. :-) /dev/random never hands out more bits than it has entropy available. (It collects entropy from the timings of keyboard interrupts, mouse interrupts, and the like; and it tries to conservatively estimate how many bits of randomness each event adds to the pool.) If the entropy estimator is conservative -- which its creators believe but which is impossible to prove -- then /dev/random is perfectly random and perfectly secure, in the sense that, from an attacker's point of view, any one of the 2^N possible strings of N bits is equally likely to be output. /dev/urandom hands out as many bits as you ask for, using the truly random state of /dev/random as a seed for a cryptographic pseudo-random number generator (PRNG). So even if the /dev/random entropy pool only has (say) 256 bits of entropy, /dev/urandom will gladly give you 1000, 1 million, or 1 billion bits of output. In this example, since there are only 256 bits of entropy, there are only 2^256 possible outputs, so each of the 2^1000, 2^(1 million) or 2^(1 billion) possible outputs from /dev/urandom is NOT equally likely. In this sense, /dev/urandom is less secure than /dev/random. If the PRNG is cryptographically strong -- which its creators believe but which is impossible to prove (at present) -- then there is no *practical* way to distinguish the output of /dev/random from that of /dev/urandom... Because for practical purposes, 2^256 might as well be 2^1000. The point of preserving the entropy pool across reboots is to give the entropy pool an initial state that is unknown to any attacker. In other words, even if the attacker knows a lot about your system -- like what state it is in when you first turn it on -- he will not know anything about your entropy pool as long as he does not know what is in the saved state file. Does this help? -- Upstart doesn't activate luks volumes (also non luks) in cryptsetup https://bugs.launchpad.net/bugs/62751 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 62751] Re: Upstart doesn't activate luks volumes (also non luks) in cryptsetup
/dev/random blocks until it has enough entropy to guarantee randomness. That is probably why wiggling the touchpad gets things going again. If you have /dev/hwrandom, you can use that... Otherwise, you can use /dev/urandom to avoid blocking, but theoretically this could give up some security (since the random generator's internal state could be predictable at boot). -- Upstart doesn't activate luks volumes (also non luks) in cryptsetup https://bugs.launchpad.net/bugs/62751 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 151169] Re: do-release-upgrade to gutsy disables eth0
I strongly agree do-release-upgrade should be supported for the desktop. What is Ubuntu's official policy on this question, and how would one go about changing it? -- do-release-upgrade to gutsy disables eth0 https://bugs.launchpad.net/bugs/151169 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 149665] Re: when returning from suspend my laptop tries to hibernate
I have the same configuration as Michael Elkins (Dell Latitude D610), and I am experiencing the same problem. I reported it as Bug #152735, before I realized (a) it only happens when gnome-power-manager suspends the machine, not when I do it by hand; and (b) the system is hibernating, not shutting down. (I use an encrypted swap partition, so hibernation does not actually work... Which is why I thought the machine was shutting down.) -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 152735] Re: Dell D610 shuts down after resume
*** This bug is a duplicate of bug 149665 *** https://bugs.launchpad.net/bugs/149665 OK the machine is hibernating, not shutting down. I use an encrypted swap partition, so hibernation does not actually work... Which is why I thought the machine was shutting down. Marking as duplicate of Bug #149665. ** This bug has been marked a duplicate of bug 149665 when returning from suspend my laptop tries to hibernate -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 157842] No sound after upgrade to Gutsy
Public bug reported: I have a Dell Latitude D610 laptop (Intel ICH6 sound device). Sound works fine in Windows. It worked fine in Feisty. After upgrading to Gutsy, I can hear no sounds at all. I am in the audio group. My User Privileges include Use Audio Devices. All volume controls are turned up. Upgrading to Gutsy broke the sound, period. I am attaching the output of alsa-info.sh. Let me know if you want additional information. ** Affects: ubuntu Importance: Undecided Status: New -- No sound after upgrade to Gutsy https://bugs.launchpad.net/bugs/157842 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 157842] Re: No sound after upgrade to Gutsy
** Attachment added: alsa-info.txt http://launchpadlibrarian.net/10187524/alsa-info.txt -- No sound after upgrade to Gutsy https://bugs.launchpad.net/bugs/157842 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 157811] Re: can't upgrade from feisty to gutsy
I do not believe apt is a supported upgrade tool for Ubuntu. See http://www.ubuntu.com/getubuntu/upgrading for upgrade instructions. -- can't upgrade from feisty to gutsy https://bugs.launchpad.net/bugs/157811 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 78552] Re: /sbin/update-grub complains about being run instead of /usr/sbin/update-grub
Me too Since the installer created kernel-img.conf, and since update-manager is the only supported upgrade path for Ubuntu, update-manager should fix the broken configuration file. In my opinion. But regardless, the kernel-img.conf file is broken following an upgrade to Gutsy. From my end-user point of view, I don't care whose fault it is, I just think it needs to be fixed... -- /sbin/update-grub complains about being run instead of /usr/sbin/update-grub https://bugs.launchpad.net/bugs/78552 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 152735] Re: Dell D610 shuts down after resume
That certainly sounds plausible. How can I confirm that what I am seeing is hibernation? -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 152735] Dell D610 shuts down after resume
Public bug reported: Binary package hint: linux-source-2.6.22 Running pre-release of Gutsy, I suspend the machine. When I resume, X comes back up, I type my password to unlock the screensaver, I can even work in Firefox or gnome-terminal for about five seconds... Then the system switches back to the text console showing a bunch of messages like this: [ 4904.012000] usb_device usbdev5.1: PM: suspend 0-2, parent usb5 already 2 [ 4904.012000] usb_endpoint usbdev5.1_ep81: PM: suspend 0-2, parent 5-0:1.0 already 2 [ 4904.012000] hub 5-0:1.0: PM: suspend 2-2, parent usb5 already 2 [ 4904.012000] usb_endpoint usbdev5.1_ep00: PM: suspend 0-2, parent usb5 already 2 [ 4904.012000] usb_device usbdev4.1: PM: suspend 0-2, parent usb4 already 2 [ 4904.012000] usb_endpoint usbdev4.1_ep81: PM: suspend 0-2, parent 4-0:1.0 already 2 [ 4904.012000] hub 4-0:1.0: PM: suspend 2-2, parent usb4 already 2 [ 4904.012000] usb_endpoint usbdev4.1_ep00: PM: suspend 0-2, parent usb4 already 2 [ 4904.012000] usb_device usbdev3.1: PM: suspend 0-2, parent usb3 already 2 [ 4904.012000] usb_endpoint usbdev3.1_ep81: PM: suspend 0-2, parent 3-0:1.0 already 2 [ 4904.012000] hub 3-0:1.0: PM: suspend 2-2, parent usb3 already 2 [ 4904.012000] usb_endpoint usbdev3.1_ep00: PM: suspend 0-2, parent usb3 already 2 [ 4904.012000] usb_device usbdev1.1: PM: suspend 0-2, parent usb1 already 2 [ 4904.012000] usb_endpoint usbdev1.1_ep81: PM: suspend 0-2, parent 1-0:1.0 already 2 [ 4904.012000] hub 1-0:1.0: PM: suspend 2-2, parent usb1 already 2 [ 4904.012000] usb_endpoint usbdev1.1_ep00: PM: suspend 0-2, parent usb1 already 2 Then the hard drive starts grinding and the machine is totally non- responsive (e.g., Alt+Fxx does not do anything). After about 20 seconds, the power turns off. This does not happen every time I suspend/resume, but it's close. Apart from the usual attachments, I am attaching my kern.log file. There are several examples therein, the most recent being Oct 14 11:58:17. Let me know if there is any additional information I can provide. ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 152735] Re: Dell D610 shuts down after resume
** Attachment added: uname-a.log http://launchpadlibrarian.net/9981042/uname-a.log -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 152735] Re: Dell D610 shuts down after resume
** Attachment added: version.log http://launchpadlibrarian.net/9981043/version.log -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 152735] Re: Dell D610 shuts down after resume
** Attachment added: dmesg.log http://launchpadlibrarian.net/9981044/dmesg.log -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 152735] Re: Dell D610 shuts down after resume
** Attachment added: lspci-vvn.log http://launchpadlibrarian.net/9981045/lspci-vvn.log -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 152735] Re: Dell D610 shuts down after resume
** Attachment added: kern.log http://launchpadlibrarian.net/9981047/kern.log -- Dell D610 shuts down after resume https://bugs.launchpad.net/bugs/152735 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 68461] Re: Wishlist: Xft/Freetype support
Ubuntu's official emacs-snapshot package has (to the best of my knowledge) always been identical to mine and thus never supported Xft. Yes we know, and it kind of sucks. This bug report is a plea for someone to fix it. Emacs is the only tool on the system that looks like garbage. It would take approximately five minutes to fix. Therefore it will be roughly six years before it actually happens... :-) -- Wishlist: Xft/Freetype support https://bugs.launchpad.net/bugs/68461 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 110263] Re: VNC package vnc4server has broken XFIXES extension, breaking GTK apps
I can confirm this problem with Feisty. Can anyone suggest a (simple?) workaround, short of downloading and compiling my own copy of the VNC server? Thanks! -- VNC package vnc4server has broken XFIXES extension, breaking GTK apps https://bugs.launchpad.net/bugs/110263 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 110263] Re: VNC package vnc4server has broken XFIXES extension, breaking GTK apps
Aha: https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/78887 -extension XFIXES does the trick. Thanks, Peter! -- VNC package vnc4server has broken XFIXES extension, breaking GTK apps https://bugs.launchpad.net/bugs/110263 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 68461] Re: Wishlist: Xft/Freetype support
This may be a stupid question but... Why? I mean, the only reason I tried installing an obscure package called emacs-snapshot was to see if the font rendering had progressed beyond 1995. What other purpose could emacs-snapshot possibly have? :-) More seriously, with a name ending in -snapshot, what difference does it make whether it is built from the trunk or from a branch? Anybody who installs such a package is trying to trade stability for features anyway, right? Otherwise, they can just use the emacs package. If this is the choir, to whom should I be preaching? (Sorry if I am being obnoxious, but I upgraded to Feisty and now my Emacs looks like crap again. Annoying.) -- Wishlist: Xft/Freetype support https://bugs.launchpad.net/bugs/68461 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 102661] Re: pam-keyring incompatible with gnome-password
The most problematic symptom: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/92032/ ...has been fixed in a different way. So this bug is no longer as important, and arguably does not need to be fixed at all... Thanks! -- pam-keyring incompatible with gnome-password https://bugs.launchpad.net/bugs/102661 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 105235] received packet without ExtIV flag repeating messages
Public bug reported: I recently upgraded to Feisty beta on my Dell Latitude D610. Network driver is ipw2200. My WPA network connection seems to work, but every 1-3 seconds the following kernel message is logged: CCMP: received packet without ExtIV flag from xx:xx:xx:xx:xx:xx ...where the MAC address is my wireless access point (a Linksys WRT54GS running dd-wrt). The connection does seem to be working, but I am wondering what these messages are trying to convey and what I should do about them. ** Affects: ieee80211 (Ubuntu) Importance: Undecided Status: Unconfirmed -- received packet without ExtIV flag repeating messages https://bugs.launchpad.net/bugs/105235 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 102656] Still cannot change master password on keyring
Public bug reported: Binary package hint: gnome-keyring Even though this bug was marked as fixed in Edgy last July: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/38483 ...I do not see any way to change the master password on the keyring. I did find this discussion, where the most recent responses say I have to DELETE THE ENTIRE KEYRING AND CREATE A NEW ONE in order to change the password: http://ubuntuforums.org/showthread.php?t=157808 That is not what I would call fixed. Fixed would mean letting me change the master password without losing all of my keys. I cannot believe somebody implemented a security feature without providing a way to change the password. Mind-boggling. Or did I miss something? ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: Unconfirmed -- Still cannot change master password on keyring https://bugs.launchpad.net/bugs/102656 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 102661] pam-keyring incompatible with gnome-password
Public bug reported: Subject says it all. One symptom is this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/92032/ If pam-keyring cannot interact with unlocking the screen saver, then it is pretty much useless... I want to locksuspend my machine when I leave, and type ONE password when I come back. Can I do that with Feisty, or not? ** Affects: pam-keyring (Ubuntu) Importance: Undecided Status: Unconfirmed -- pam-keyring incompatible with gnome-password https://bugs.launchpad.net/bugs/102661 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 102661] Re: pam-keyring incompatible with gnome-password
Thank you for the suggestion. Yes, I tried adding @include common- pamkeyring to /etc/pam.d/gnome-screensaver. It does not work because pam_keyring.so spawns a new instance of gnome-keyring-daemon instead of unlocking the running daemon already present. In my opinion, this should not only work, but it should be the default configuration for Ubuntu. Having to type my keyring password over and over is extremely annoying, especially when I already type it to unlock the screensaver. Very few people are going to be able to figure out how to install the pam-keyring package and edit files under /etc/pam.d. And that is even if it actually worked. :-) -- pam-keyring incompatible with gnome-password https://bugs.launchpad.net/bugs/102661 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 78282] Re: vnc4server does not start Desktop environment after security update
Ditto. Please fix this bug or revert the upgrade. Current vnc4server is unusable. -- vnc4server does not start Desktop environment after security update https://launchpad.net/bugs/78282 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68461] Re: Wishlist: Xft/Freetype support
A kind Ubuntu hacker in India has made Xft versions of emacs-snapshot packages available via apt: http://g33k.wordpress.com/2006/11/06/gnu-emacs-with-xft-goodness/ The difference in fonts is like night and day. I agree with Hans. You can label this importance wishlist... But seriously, every time I start Emacs I have to double-check the calendar to remind myself what year it is. And it can be fixed just by rebuilding emacs-snapshot with Xft support enabled. Pretty please? -- Wishlist: Xft/Freetype support https://launchpad.net/bugs/68461 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 3593] Re: Xvnc4 (package vnc4server) unable to find fixed font in Breezy
This is definitely broken again in Edgy. Plus the old Dapper workaround (-fp ...) broke because the fonts moved from /usr/share/X11/fonts to /usr/share/fonts/X11. Just repeating what has already been said, adding my voice to the chorus. Would be nice to see this fixed in the underlying Xvnc4 program. -- Xvnc4 (package vnc4server) unable to find fixed font in Breezy https://launchpad.net/bugs/3593 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67607] Re: rt61pci driver fails with Airlink101 AWLH5026
Well, after a few hours, the wireless card locked up. I was unable even to ping my router. Rebooting did not help; I had to power-cycle to get my network back. This driver is obviously not ready for prime time. I gave up and bought a D-Link WDA-1320 (Atheros chipset), which seems to be working much better. -- rt61pci driver fails with Airlink101 AWLH5026 https://launchpad.net/bugs/67607 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67607] Re: rt61pci driver fails with Airlink101 AWLH5026
Another addendum for others trying to get this card working in Edgy: With just a little manual configuration, this card is functioning fine with the current drivers in Edgy. First I configured it in network-admin. Then I edited /etc/network/interfaces to add these lines to the iface wlan0 ... stanza: post-up iwlist scan post-up iwconfig wlan0 ap XX:XX:XX:XX:XX:XX (where XX:XX:XX:XX:XX:XX is the address of my access point) That's all. In total, my wlan0 stanza in /etc/network/interfaces looks like this: iface wlan0 inet static wireless-essid my SSID address 192.168.1.37 # my IP address netmask 255.255.255.0 gateway 192.168.1.1 post-up iwlist scan post-up iwconfig wlan0 ap my access point address ...with only the post-up lines having been added by hand. I suspect a DHCP configuration could be made to work similarly. So this is not as bad as I thought at first. Still, it would be better if this hardware could work automagically... -- rt61pci driver fails with Airlink101 AWLH5026 https://launchpad.net/bugs/67607 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66577] Re: cryptdisks-early and crypdisks scripts don't wait for password
I can confirm this problem in Edgy on x86. My /etc/crypttab has this line: crypt /dev/hda6 Dapper used to stop during boot and wait for the passphrase. Edgy does not. When I boot without splash, I can see the failure message: Starting early crypto disks... Enter passphrase: Command failed: Key reading error After the system comes up, I can run /etc/init.d/cryptdisks (or cryptdisks-early) by hand and it works fine; it waits for the passphrase and starts the encrypted device. -- cryptdisks-early and crypdisks scripts don't wait for password https://launchpad.net/bugs/66577 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67607] rt61pci driver fails with Airlink101 AWLH5026
Public bug reported: My wireless adapter is an Airlink101 AWLH5026. lspci identifies it as vendor ID 1814, device ID 0401 (Ralink RT2600 802.11 MIMO). Current release of Edgy correctly loads the rt61pci module. Network Settings shows both wmaster0 and wlan0 devices, and it lets me configure and activate wlan0. I am not using any encryption. But the wireless does not work. DHCP does not acquire a lease, and I am unable to ping the router even if I use a static IP address. iwconfig wlan0 shows Not-Associated. HOWEVER: When I run iwlist scan, I can see my access point. If I use iwconfig wlan0 ap xx:xx:xx:xx:xx:xx to set the access point manually, the wireless starts working; I can ping my access point and access the Internet. I am using it now to submit this bug. :-) But the setup is fragile. If I attempt to switch to DHCP in Network Settings, the association breaks (goes back to Not-Associated) and I have trouble re-associating even manually. I am willing to debug this further if an expert will tell me how to proceed. I was hoping this card would just work in Edgy... I had to follow the embarrassingly hairy instructions at http://ubuntuforums.org/showthread.php?t=132980 to get it working in Dapper. Ubuntu should be better than this, and I would like to help. Thank you! ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: Unconfirmed -- rt61pci driver fails with Airlink101 AWLH5026 https://launchpad.net/bugs/67607 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67607] Re: rt61pci driver fails with Airlink101 AWLH5026
Addendum: Apparently, I have rediscovered the procedure documented in the README for the rt61pci driver. http://rt2400.cvs.sourceforge.net/rt2400/source/rt2x00/README?revision=1.39 - After the client interface has been brought up, scanning can be performed to check if the desired AP is being detected. Note that it is currently mandatory to scan at least once before starting an association attempt. # $ iwlist wlan0 scan - To start an association attempt, the AP address should be set: # $ iwconfig wlan0 ap mybssid Does this behavior (mandatory scan after ifconfig bring-up) mean that this hardware can never work out-of-the-box with Ubuntu? -- rt61pci driver fails with Airlink101 AWLH5026 https://launchpad.net/bugs/67607 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
