I have the same issue (though my startup warnings refer to blkid's). I'm
attaching a bootchart that shows the effect. I found that if I disabled
fsck in the /etc/fstab file, boot was much quicker. But that seems
unsafe...
** Attachment added: "zephyr-karmic-20091104-2.png"
http://launchpadlibra
I'm running 9.10 (Karmic 32-bit, kernel 2.6.31-20-generic-pae). My
experience of this problem is that removing and reloading the STA module
(wl) reliable yields kernel panics within 10 s - 5 minutes. This appears
only to happen if the driver has been used (i.e., I've connected to a
network) prior t
In Karmic, kernel 2.6.31-17 and the wl wireless kernel module (BCM4328),
I still have this problem. I find that removing and re-inserting the
module (sudo rmmod wl; sudo modprobe wl) enables NetworkManager to work
properly, but then the system inevitably freezes within a few minutes.
--
NetworkMa
If I use the command "sudo iwlist scanning", which I think uses the
driver to report networks, the network in question is _not_ reported.
--
NetworkManager attempts to connect to unavailable previously connected network
when resuming from suspend
https://bugs.launchpad.net/bugs/379201
You receiv
I also updated to 11.10, and have had to drop down to a console window
to kill chrome twice now. For me, all keyboard and mouse clicks are not
(apparently) registered. Perhaps something with fglrx?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: unity
I recently noticed that some keyboard shortcuts (for example Alt-F2 to
open the dash) don't work immediately after a program exits. For
example: run gedit, close using Alt-F4, press Alt-F2. Ideally, the dash
should open so that I can run another pro
It appears this was actually a consequence of conky running on the
desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779732
Title:
keyboard shortcuts don't work immediately after app closes
--
