I just upgraded to Foxconn's BIOS version 515F1P55.
The problem went away, and the system is stable now with ACPI turned on.
I have marked this bug "Invalid", since it seems to have been fixed by
Foxconn, so it was probably a bug in their BIOS.
** Changed in: linux (Ubuntu)
Status: New =>
I just tried it with 8.10, Intrepid Ibex, and the problem still exists.
It's important to note, however, that there is absolutely no problem if
I install with acpi=off, so it seems related to a kernel bug with
handling acpi.
** Changed in: ubuntu
Status: Invalid => Incomplete
** Changed i
Public bug reported:
When booting off Ubuntu Gutsy 7.10 Live CD, my computer quickly locks
up, usually before it is completely booted. The furthest I have been
successful in booting is about 10-20 seconds past the point where the
initial GNOME desktop appears.
If I use the alternate CD, I can suc
I have precisely the same problem (including Caps Lock flashing) on my
Toshiba Satellite L355 (x86_64 architecture) using the built-in Wireless
WiFi Link 5100. Again, wired Internet works flawlessly.
The difference is that I've been using Jaunty for a while with no
problems. So kernels 2.6.28-11 a
Update: I found a workaround.
I reverted to kernel version 2.6.28-15 and it seems to work for me. I
can now select the correct kernel in grub during the boot process. If
I'm hooked up to wired network, I select kernel 2.6.31. For a stable
machine during wireless network access, I use 2.6.28. To in
I experienced the same problem on my 1GHz Pentium III PC. Therefore it
was not just a problem with non-Intel processors as stated above.
However, the problem was fixed with the latest daily-live CD (20091020),
and I'm now happily running 9.10.
--
ubiquity crash on partitionning step when ubiquit
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
kde hangs with nfs directories mounted and wireless enabled
https://bugs.launchpad.net/bugs/501246
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
I should mention that I have flaky wireless connectivity in my laptop.
Due to some intermittent bug that I can't reliably reproduce, I am have
to re-enter the WPA key to reconnect rather than just using the key
stored in KDE Wallet. Since I was not aware of the limitation in this
bug, I just though
Public bug reported:
I have a couple of NFS directories mounted on /share/ via a wireless
connection. If I log out of GNOME and log back into GNOME, it works
fine. However, if I log out of GNOME and the wireless connection in KDE
is not set to "Connect Automatically" or if it has the incorrect
I don't think this problem has been fixed yet. I'm running Maverick
10.10 with the updated ntp, but the problem is still occurring:
Jan 8 04:05:01 pgfs ntpd[2608]: synchronized to 91.189.94.4, stratum 2
Jan 8 04:05:01 pgfs ntpd[2608]: kernel time sync status change 2001
Jan 8 04:05:42 pgfs ntpd
Public bug reported:
Binary package hint: ntp
I believe this is a duplicate of bug
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/569919, which has a status
of "Fix Released"
But I have the fix, and the problem still occurs.
Every 5 minutes, ntpd complains about being unable to create a so
Public bug reported:
Binary package hint: syslog-ng
System: Ubuntu 10.10 Maverick
Package syslog-ng Version: 3.1.2-1
After installing syslog-ng (sudo apt-get install syslog-ng), the file
/var/log/error filled up with the following errors:
Jan 11 10:49:33 pgfs syslog-ng[3363]: Error opening file
The problem does not resolve for me. I still get the following errors
(uptime is >3 days):
Apr 27 22:01:44 pgfs ntpd[2535]: bind() fd 24, family AF_INET6, port 123, scope
4, addr fe80::217:31ff:fef8:f63f, mcast=0 flags=0x11 fails: Cannot assign
requested address
Apr 27 22:01:44 pgfs ntpd[2535]:
I have had the same bug. I did some troubleshooting and it only occurs
when I am doing heavy disk activity (potentially on another volume).
Whenever this occurs, if I try to issue a "sync" it also hangs for a
very long time.
Maybe dpkg tries to sync the discs?
In any case, if I wait until the dis
As a workaround, I'll bet if you typed "sync" before you ran dpkg, and
waited for it to complete, it would work. That works for me.
--
dpkg in uninterruptible sleep
https://bugs.launchpad.net/bugs/606341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
15 matches
Mail list logo
