forgot to mention that this is on hardy
** Also affects: xen
Importance: Undecided
Status: New
--
xen's xm create fails at losetup stage
https://bugs.launchpad.net/bugs/203649
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
xm create always fails at the losetup stage
$ sudo xm create winxp
[sudo] password for daniel:
Using config file "/etc/xen/winxp".
Error: Device 768 (vbd) could not be connected. losetup /dev/loop0
/var/xen/images/WinXP.img failed
$ sudo losetup -s /dev/loop0
/dev/loop0: [08
manually installing python-xen-3.2 fixes this issue, should the xen-
utils package depend on the python-xen package?
--
xm crashed with ImportError in ()
https://bugs.launchpad.net/bugs/131585
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Reopening as this is happening to me on hardy:
# xm
Traceback (most recent call last):
File "/usr/sbin/xm", line 8, in
from xen.xm import main
ImportError: No module named xen.xm
** Changed in: xen-3.1 (Ubuntu)
Status: Fix Released => New
--
xm crashed with ImportError in ()
https
I had the problem when unmounting an sftp volume after the ssh
connection had hung.
--
nautilus crashed with SIGSEGV in g_drive_eject_finish()
https://bugs.launchpad.net/bugs/198448
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
the fix for hardy is to change the second-to-last line in the
/etc/X11/xorg.conf file to re-enable the composite extension after fglrx
installation. The file previously read:
Section "Extensions"
Option "Composite" "0"
EndSection
when the 0 should be a 1 to enable the composi
this also affects the hardy development branch, in the exact same manner
as described above by the original poster. (composite extension
unavailable after installing the restricted fglrx driver, ok button not
closing warning dialogue box, desktop effects still enabled despite the
warning and inabil
for those following the method of extracting the necessary libwfb file
from the nVidia .run package but can't find the 64bit package for the
relevant version (1.0-9755), the file is located behind the nVidia site
at http://www.nvidia.com/object/linux_display_amd64_1.0-9755.html
--
[nvidia-glx-new
ok, what is the current status of this? the bug was opened on the 29th
of march way before release and now we're in july, a good 3 months
later! This is a showstopper bug for any Geforce 8800 owners like
myself, and should really have been fixed ages ago. the
workaround/explanation of what needs to
Coming from Bug #103050, I can confirm that the proposed workaround here
works also (for my situation) on the amd64 platform (provided you
download the correct package from their site of course).
--
[nvidia-glx-new] NVidia driver missing libwfb
https://bugs.launchpad.net/bugs/98641
You received t
I can confirm that the solution proposed in bug #98641 also works for my
situation on the amd64 platform (core 2 duo)
--
Xorg fails to start requesting libwfb when using nvidia-glx-new
https://bugs.launchpad.net/bugs/103050
You received this bug notification because you are a member of Ubuntu
Bug
Jacques, this fix does not work for the bug I reported above, as the wfb
module is not a kernel module but rather an X11 module, so no amount of
reloading of the nvidia.ko kernel module will resolve the issue
--
Xorg fails to start requesting libwfb when using nvidia-glx-new
https://bugs.launchpa
martin, I believe it was marked as a restricted-manager issue because
the restricted-manager did NOT install the correct package. It installed
nvidia-glx when my system requires the package nvidia-glx-new. manual
usage of nvidia-glx-config has no bearing on the situation. I have not
run nvidia-glx-
yes, you are quite right, I do indeed need the nvidia-glx-new package
instead of the plain nvidia-glx.
$ dpkg -l nvidia-* |grep ii
ii nvidia-glx-new 1.0.9755+2.6.20.5-15.20 NVIDIA binary XFree86
4.x/X.Org 'new' driver
ii nvidia-kernel-common 20051028+1ubuntu7 NVIDIA binary k
I have an nvidia GeForce 8800GTS.
Following a complete reinstall from scratch, a full dist-upgrade to the
latest kernel and reinstall of the nvidia-glx package through the
restricted drivers manager I now have a different symptom in that X now
dies reporting that it can't access /dev/nvidia0 due t
Public bug reported:
Binary package hint: nvidia-glx
with ubuntu 7.04, after installing nvidia-glx and running `nvidia-glx-
config enable` to update the Xorg.conf, X will refuse to start citing
that it needs libwfb. I found a site that mentioned that the official
binary packages direct from nvidi
Public bug reported:
Binary package hint: kleopatra
using file->import certificate and selecting my .p12 certificate file,
kleopatra responds with:
An error occurred while trying to import the certificate mycert.p12: Decryption
Failed
Using the kwatchgnupg tool launched from the kleopatra menu
17 matches
Mail list logo
