My eee is now booting with the -8 kernel after the latest updates.
Thanks!
--
udev repeatedly generates "change" events for the same block device(s)
https://bugs.launchpad.net/bugs/332270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
This is still happening in intrepid alpha 4 (IBM Thinkpad R61, 32 bit
intrepid)
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Doing a clean install from the intrepid alternate iso (32 bit, alpha 4)
knetworkmanager can be started and it will find and connect to wifi
networks. Since an update sometime around Tuesday (19th Aug) this no
longer happens. It still shows the network, but seems to make no att
I'm getting what appears to be this problem on my eee running jaunty
with an encrypted disk. Using the -7 kernel it will boot, using -8 it
won't. If I boot using -7 then restart udev the CPU utilisation reduces
for a while, but then goes back up later on. The volume was created
using the alternate
This has now happened to me on a second laptop that I upgraded. I'll see
if I can work out a set of steps to reproduce this on a VM tomorrow if I
get time.
--
Karmic series kernel won't load encrypted main disk after upgrade from jaunty
https://bugs.launchpad.net/bugs/40
You received this bug
I have an HP LaserJet 1000 and a HP DeskJet 3845. Both just feed blank
paper when printing. Error log for the 1000 is attached.
** Attachment added: "cups.log"
http://launchpadlibrarian.net/30100015/cups.log
--
poppler 0.11.2 produces blank pages with cups
https://bugs.launchpad.net/bugs/4099
I had a go at reproducing this. I can't get a successful install from
the alpha 2 jaunty installer any more so that didn't help. I also wasn't
able to install from any of the kubuntu jaunty ISO images -- they always
gave me corrupt file errors. The standard GNOME installer seemed to
upgrade fine, a
Public bug reported:
After upgrading a laptop from Jaunty to Karmic the encrypted main disk
won't mount when loading the current Karmic kernel (2.6.31-5).
The disk was encrypted using the Jaunty installer (earliest kernel is
2.6.26-5, from memory it was probably a pre-release one, and probably
th
After I couldn't reproduce this with a fresh install on a VM I gave up
and re-installed both machines. Did you also install from a pre-release
version of Jaunty? That might be the common aspect.
--
Karmic series kernel won't load encrypted main disk after upgrade from jaunty
https://bugs.launchpa
I'm seeing this on karmic kubuntu (my laptop) on a disk that has been
working fine up until now. It works fine on my desktop machine (also
running karmic, but with the newer KDE from backports).
--
"special device /dev/dm-0 does not exist" when mounting an encrypted drive
https://bugs.launchpad.n
Something in the latest updates has fixed this for me. I'm no longer
affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448445
Title:
plasma-nm causes kded5 to segfault
To manage notification
stdarg.h also seems to be affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198123
Title:
clang cannot find stddef.h
To manage notifications about this bug go to:
https://bugs.launchpad.net/
The following seems to work as a workaround for me:
cd /usr/lib/clang/3.2/
sudo ln -s /usr/lib/llvm-3.2/lib/clang/3.2/include
It looks like there's a mismatch between where the include files are
installed to and where clang expects to find them
Diagnosed with the help of:
echo '#include ' | cla
Public bug reported:
KDE on Ubuntu 15.04 causes kded5 to crash (every few seconds) and plasma
to crash (intermittently).
It's a duplicate of this stack tracke:
https://bugs.kde.org/show_bug.cgi?id=346556
This has apparently been fixed upstream for some time:
https://bugs.kde.org/show_bug.cgi?id=
14 matches
Mail list logo
