Ohh, also update-initramfs failed, giving a "read-only media" error. If
this happens to you, do the following to replace the running version of
update-initramfs and try again
mv /usr/sbin/update-initramfs /usr/sbin/update-initramfs.old
ln -s /rofs/usr/sbin/update-initramfs /usr/sbin/update-initram
Just wanted to add this also happened to me during the lucid release
cycle. I followed Mark's instructions above.
1. Boot from ubuntu livecd (preferably the same version as you were running)
2. sudo apt-get install mdadm
3. sudo mdadm --assemble --scan
4. sudo mkdir /md0
5. sudo mount /dev/md0 /md
This has been broken again by the 2.6.31-14-generic kernel - can anyone
else confirm this? I am not able to reboot the machine that often, but I
did reboot to update to what is probably the final version of karmic
today. Doing so installed the kernel above and subsequently broke the
monitor sleepin
@BassKozz,
yes, karmic comes with these drivers. I did not do any third party installation.
dpkg -l nvidia-glx-185
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/
Just to add to above. After removing the old version as stefano
mentioned, I did this:
sudo dkms build -m vboxdrv -v 3.0.6 -k 2.6.31-11-generic
sudo dkms install -m vboxdrv -v 3.0.6 -k 2.6.31-11-generic
This rebuilt the module (which was needed for me because of the kernel
upgrade), then installe
I too have this problem. Both with the karmic version and the deluge PPA
version. I tried clearing my config, and I think that fixed it once, but
know it's freezing again. Reinstalling made it work, but only if I run
it from the command line, like so:
deluge --ui=gtk
I believe it's a python issue
OK - this "magically" started working again, as it did before I upgraded
to Karmic months ago. I'm running 2.6.31-11-generic kernel. That was the
only real change I can attribute. After rebooting from updating it
started working. I did add this to my Xorg, but it didn't work under the
old kernel.
I too fall victim to this. However, it only started occurring after I
upgraded to Karmic (in advance of the official release). I think I was
avoiding it because I had installed my own nividia drivers, and I
switched to using ubuntu's during the upgrade? I'm not sure as I have
been using twinview fo
Since this an "easy" bug, I will attempt to fix. After all it's only 2
days late already :-) Has anyone else looked into it, or could give
guidance on which module needs changed for this?
--
Suggested output when printing a file to PDF is technical and generic
"~/output.pdf"
https://bugs.launchp
*** This bug is a duplicate of bug 195782 ***
https://bugs.launchpad.net/bugs/195782
Oddly enough this "magically" started working for me after I installed
libsane-extras.. Try it
sudo apt-get install libsane-extras
--
Detected scanner fails to load with "Invalid Argument"
https://bugs.laun
yes - I confirm this same behavior with .14.5 from the ubuntu repo, as
well as .14.7 from upstream. Typing gourmet in the terminal appears to
make it load, but it doesn't work correctly, and generates errors in the
terminal session.
--
gourmet does not start on jaunty
https://bugs.launchpad.net/b
I fixed this by doing the following. This happened because during the
netinstall, my wireless network was used. Therefore network manager was
not managing the connection. I edited /etc/network/interfaces to remove
auto eth0. I then killed network manager and restarted it.
sudo nano /etc/network/in
I still seem to get this problem, though it's happening when I try and
install firestarter. This is on a Tribe 5? gutsy straight install,
updated by update manager to stay current.
sudo apt-get install firestarter
Reading package lists... Done
Building dependency tree
Reading state informat
graphics driver has nothing to do with it - tried on different pc with
vesa driver
--
bouncy crashes on startup
https://bugs.launchpad.net/bugs/144160
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
Public bug reported:
Binary package hint: bouncy
The bug is described in this upstream debian bug report.
http://www.nabble.com/Bug-436178:-bouncy:-crashes-on-
startup-t4221904.html
Using nvidia driver version 1.0-9639 and GForce FX 5500. Trying to run
bouncy, results in a crash and this text.
Public bug reported:
Binary package hint: openoffice.org-draw
Just wondering why openoffice-draw, though installed by default, is not
found in the office menu, nor enabled? It is found in the graphics
menu, but only if you use alacarte to enable it. Why would you disable
the desktop application
Well - not sure if it helps, but this issue magically went away after I
did this. I'm not sure which one worked, but one of these apt installs
fixed the issue. I was trying to pay attention, but i must have missed
it. Ubuntu-desktop, ubuntu-minimal and ubuntu-standard where already
installed. Perha
sorry last comment - trying to be helpful - before I did all those
things, I updated and added all the edgy sources - so universe,
multiverse, which are not enabled in the default install. Update and
trying a dist-upgrade then did not fix the issue. But installing all
those packages - something was
It would appear there's some special character in your apt that python
doesn't like. I found this in relation to the bug. Hope it helps.
"Python's character set support is horrid. Unfortunately, Python assumes
that everything is ASCII by default, rather than a more sensible choice
like UTF-8. This
here's the dist-upgrade log - as I said this is a straight install from
the dapper live cd, boot into dapper, and dist-upgrade. I should clarify
that I kept my home directory from the previous installation. My upgrade
to feisty hosed the system partition, via the AOpen kernel bug.
** Attachment ad
Public bug reported:
Binary package hint: gnome-app-install
This is a recent issue, as I've upgrade on this same pc, and others from
dapper to edgy numerous times before. I would guesstimate this is as
recent as sometime this year. Here's the details.
Setting up gnome-app-install (0.2.21) ...
Ca
21 matches
Mail list logo
