not installable
If I knew where and how to fix and submit, I would do so.
Thanks for making Ubuntu better.
Jeff Hatfield
--
[jaunty] vlc dependency error
https://bugs.launchpad.net/bugs/325720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I tried to add/enable 3D... in edgy. Got that working ok, but then X
started locking up. Even back to stock ati driver (which was used no
matter 3D or not) Anyway, some of error files. I have to login
terminal or ssh into same ... Nothing good works for video while logged
into Gnome.
Good luck
Yes. This issue is still around. The correction method I used where I
blacklist the apgart and intel driver modules still works with Karmic.
Jeff
Leann Ogasawara wrote:
> Hi Jeff,
>
> Is this reproducible manually doing a suspend/resume cycle (ie not using
> the automated test suite)? Is the wor
Public bug reported:
System suspended properly, but failed to resume. In Jaunty I had to
modify modprobe.d/blacklist to make suspend/resume work with the Nvidia
video card - added lines blacklist intel_agp, blacklist agpgart
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USERPID
** Attachment added: "karmic_suspend-resume.tar"
http://launchpadlibrarian.net/32078032/karmic_suspend-resume.tar
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32078033/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/32078034/
Public bug reported:
System suspended properly, but failed to resume. In Jaunty I had to
modify modprobe.d/blacklist to make suspend/resume work with the Nvidia
video card - added lines blacklist intel_agp, blacklist agpgart
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USERPID
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32078012/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/32078014/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/32078015/ArecordDevices.t
I concur... this is a problem that should have been fixed by now. When I
run "export SSH_AUTH_SOCK=0 on the host machine, I have no problem
connecting to the target system after placing the key in the
authorized_keys2 file (on target).
Note: This must be done for each and every shell opened on the
