https://bugs.launchpad.net/ubuntu/+source/virtualbox-
ose/+bug/811097/comments/2
Worked for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/811097
Title:
package virtualbox-ose 4.0.4-dfs
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/51670325/AptOrdering.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/51670326/Dependencies.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/51670327/Dmesg.txt
** Attachment
Public bug reported:
na
ProblemType: Package
Architecture: amd64
Date: Sat Jul 10 11:30:38 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit
status 1
Package: nfs-common 1:1.2.0-2ubuntu8
ProcVersionSignature: Ubuntu 2.6.31-20.58-gener
I've just tested with the current daily kernel (after removing the
/etc/modprobe.d/options I had added to set the max_speed parameter for
the sbp2 module). The disk becomes read-only just as it does with the
stock kernel. I forgot to mention that the disk has an ext4 filesystem
on it.
This is the
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/51481289/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/51481290/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/51481291/BootDmesg.txt
** Att
Public bug reported:
Running faubackup on this 64-bit Toshiba Satellite laptop (model
p305d-s8900), saving backups to a 320-GB Acomdata E5 external firewire
hard drive (model HD320FE5-72), causes the drive to become read-only in
a few minutes. Simple Backup causes the same behavior. Adding the
o
Without xorg.conf, I get the same result--the highest screen resolution
is set at 1024 x 768.
Here is the Xorg.0.log file from booting with the "nomodeset" option.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/45846924/Xorg.0.log
--
screen resolution wrong with Riva TNT2 vi
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/45213780/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/45213781/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45213782/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-nouveau
Lucid release candidate, Nividia Riva TNT2 video card, Dell 1905FP LCD
monitor: nouveau driver sets the highest screen resolution at 1024 x 768
when the highest (and optimal) resolution is 1280 x 1024. The nv driver
set the res
** Visibility changed to: Public
--
evolution crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/507972
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Possibly related: I'm running 9.10. I have one machine with two user
accounts. I set gdm to autologin user "mark." Now user "mark" does not
have any external drives automounted. Resetting gdm to the default login
screen did not change this behavior. The other user "latin" has
external drives au
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: kdm
Hi,
I'm running the Koala latest, since the Koala Beta.
I'm experiencing issues where 1 in 5 times the KDM does not present a username
and password box. Instead, I still see the previous scree
The i5 support seems to be a little behind, even on the latest from
Koala beta (which I went for having seen the same Phoronix article
explaining that the 2.6.31 Kernel was required for compatibility).
In addition to the Turbo Boosting not working, I have also found
performance to be on par or bel
I'd still argue that this was a bug and not a question?
Wiz's workaround fixes the problem, until the system is rebooted and the /sys
file system is regenerated.
Hope that helps,
MG
--
CPU Frequency locked at maximum
https://bugs.launchpad.net/bugs/359559
You received this bug notification bec
Hi,
I am getting the same issue.
Seems to me that the
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq file is set
incorrectly to the highest value.
Hope the below is of use.
---
m...@titanic:~$ cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
2793000 266 252700
Hi,
I am getting the same issue.
Seems to me that the
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq file is set
incorrectly to the highest value.
Hope the below is of use.
---
m...@titanic:~$ cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
2793000 266 252700
I am running the 64bit Karmic Beta on an Intel i5.
This message appears almost randomly every few hours.
Happy to supply further information if requested.
MG
--
npviewer.bin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/141613
You received this bug notification because you are a member of
Hi,
I'm running the 9.10 Kubuntu beta.
I had the same issue.
Added a HP Business Inkjet 1100d over the network using the KDE tool - all
worked fine. Printed a test page, worked great.
Tried to print from okular and nothing happened. Running okular from the
command line revealed "lpr: Bad job-
I can confirm that this is present in the beta.
I have a Raid 0 setup, and installed the AMD64 beta.
Thanks,
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
19 matches
Mail list logo
