I too have this on my Acer Aspire One running Ubuntu Desktop.
--
Udev worker error during boot "worker [XX] did not accept message -1
(Connection refused), kill it
https://bugs.launchpad.net/bugs/647404
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Trey's right, it never was fixed.
Although I have fortunately not suffered from any permanent hardware
problems, the bug resurfaces every now and then. I have worked around it by
editing /lib/udev/rules.d/80-udisks.rules and commenting out this line:
# ATA disks driven by libata
#KERNEL=="sd*[!0
The workaround did the trick for me too. I hadn't suffered any
corruption but I was comsidering going back to Jaunty and I am pleased
not to have to.
Simon
Sent from My iPhone
On 16 Dec 2009, at 14:28, Gav Mack wrote:
> @Andrew Simpson: Many thanks for the instructions. The workaround ha
I can confirm that upgrading from the stock SSD with Karmic already
installed to a Super Talent SSD produced this error which had not
previously been present.
Simon
Sent from My iPhone
On 7 Dec 2009, at 06:31, Andrew Simpson
wrote:
> The upstream bug report has asked whether anyone has t
I have the same computer and SSD (Acer Aspire One and SUPER TALENT
FEM32GF13M) as well as the same symptoms as Raf above.
--
SSD stall during boot
https://bugs.launchpad.net/bugs/445852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Me too. My machine is fully up to date as I type and Sticky Notes now
appears to work completely as expected. Synaptic reports version 2.28.0.
Simon
2009/10/21 Jonathan Nielsen (mudi)
> Odd, it did start working for me. Perhaps change the preference sizes
> manually (in gconf-editor? Don't
this is .
Thanks for stepping in and offering to collate this information Jonathan -
it's very helpful.
lotus49
2008/11/13 Jonathan Ernst <[EMAIL PROTECTED]>
> @Hobgoblin
> Your device is a very interesting test case to show that the approach
> adopted upstream cannot
It is quite clear the developer is behaving decidedly irrationally (not
to mention aggressively) on this one and is insisting, for reasons best
known to himself, that users should not be permitted to enter their own
PIN and each device's hard-coded PIN should be hard-coded into the
source. His arg
Same for me. I am trying to pair with a BT-Q880 GPS receiver and
obviously, there is no way to enter a PIN so bluetooth in Intrepid is
now useless for anything except keyboards.
What is surprising about this bug is that keyboards and phones are the
only bluetooth devices on which you can normally
Same for me. I am trying to pair with a BT-Q880 GPS receiver and
obviously, there is no way to enter a PIN so bluetooth in Intrepid is
now useless for anything except keyboards.
What is surprising about this bug is that keyboards and phones are the
only bluetooth devices on which you can normally
I too have had this problem with a clean install from the 8.04 alternate
install CD.
My systems boots fine but eventually I am dumped into busybox. If I
boot into recovery mode I see:
cryptsetup: Source disk /dev/disk/by-uuid/ not found
Rebooting with c-a-d does not help. I have also tried run
11 matches
Mail list logo
