While not the focus of this bug, (and I can't speak for anyone else
here) I have used resolvconf (actually openresolv) with dnsmasq to
properly handle dns for VPN connections. I have a home network with
internal DNS (there is several machines on the network), when I connect
(via VPNC) to my office
Add me to the list of those bitten by this on Hardy. I was about to try
backporting 2.2.7 from Intrepid, but figured I would give the official
channels a couple days to sort it out first.
--
Test for installed packages in cfengine is broken
https://bugs.launchpad.net/bugs/232450
You received
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/24357220/BootDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24357221/Dependencies.txt
** Attachment added: HalComputerInfo.txt
http://launchpadlibrarian.net/24357222/HalComputerInfo.txt
**
Public bug reported:
When resuming from memory-suspend my system sometimes sends me back to a
login screen (losing all my application state and any active data). This
happens about 50% of the time.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
I have been testing 195.30 from https://launchpad.net/~nvidia-
vdpau/+archive/ppa and so far this has resolved the issues for me.
External display now resumes from power save cleanly. I did not try
190.53 though.
--
Primary monitor doesn't wake up out of power save mode
I have the same issue although with gnome-screensaver. If I re-attach to
my session via the switch user option, I am able to re-authenticat. So
obviously it's something related to how the screensaver's are configured
to interact with pam/ccreds. I should also report that this config was
working
After some digging on the nvidia site, it appears that it was an earlier
version of version 185 that contained the fix. There is several mentions
of the issue on the nvidia forums as well. I am going to try running the
190 drivers on my machine, though I don't know when exactly I will be
able to
I can report this as well, though in my configuration it is a laptop
with a Quadro FX770M chip. The laptop display will resume from a power
save, the attached external display (via DisplayPort) does not. After
power cycling the external display, visibility is restored, but it's
extremely
Mathias:
While I appreciate the need to move forward, is it not possible to
release the fix for the current stable version (ie. Karmic) as well?
Especially if the fix is just installing one file with setuid
permissions.
--
ccreds_chkpwd miss setuid
https://bugs.launchpad.net/bugs/480106
You
