This also fixes the issue with `bbdb' function being not autoloaded. :)
(The function definition is void in `bbdb_2.35.cvs20080316-4_all'.)
--
vvv
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I apologize for misleading xorg.conf -- I've reverted back to vesa in
order to use X server after reboot. The /proper/ xorg.conf - that made
Xorg hang - looks like this:
$ sed -re 's/(Driver\t+)vesa/\1nv/' \
-e '/^Section Monitor/,/^EndSection/ d' \
-e 's/^#.*//'
Package: pdnsd
Version: 1.2.7-par-1
Severity: serious
pdnsd stopped responding to requests from tap0 interface after the
package was updated. It appears to be a direct result of Debian policy
violations.
10.7.2 Location
Any configuration files created or used by your package must reside
in
Package: libghc6-pandoc-dev
Version: 0.44
Severity: serious
/var/lib/dpkg/info/libghc6-pandoc-dev.postinst fails unless
`libghc6-xhtml-dev' package is already present.
# aptitude install libghc6-pandoc-dev
[...]
Errors were encountered while processing:
libghc6-pandoc-dev
E: Sub-process
Package: vlock
Version: 2.0-4
Severity: serious
When locking terminal with `xscreensaver-command -lock', no screensaver
is run. Instead, the console becomes black and any keyboard input is
displayed in unreadable way. Computer is unusable until rebooted.
Downloading vlock to 1.3-10 fixes the
On 9/11/07, Alexander Wirt [EMAIL PROTECTED] wrote:
I don't understand you problem. xcreensaver-command has nothing to do with
vlock (at least not per default). So when gots vlock called with which
parameters?
I use it with xautolock here: xautolock -locker 'vlock -a -n'. Which works
fine.
6 matches
Mail list logo
