Appears to be an interoperability problem between ubuntu and debian versions of
cups.
I have updated the description to reflect this.
To summarize:
Client Server Result
Hardy Etch OK
Intrepid Etch Segfault
Intrepid Lenny OK
** Summary changed:
- Segfault in ppdFindChoice when printing
Hi Johnathon
that's a bit difficult to do without giving you an account on my
companie's VPN (which I can't do)
configuration is aggressive mode with x509 certificates
connection establishment is requested using racoonctl
Martin
--
Racoon 0.7 fails with address already in use
https://bugs.lau
Public bug reported:
Binary package hint: evince
Package: evince
Version: 2.24.1-0ubuntu1
Severity: normal
When printing any PDF evince segfaults.
gdb backtrace is:
#0 0xb493365b in ppdFindChoice () from /usr/lib/libcups.so.2
#1 0xb49623e8 in ?? () from
/usr/lib/gtk-2.0/2.10.0/printbackends/l
** Attachment added: "ipsec-tools-0.7-cvs-iface.patch"
http://launchpadlibrarian.net/22952551/ipsec-tools-0.7-cvs-iface.patch
--
Racoon 0.7 fails with address already in use
https://bugs.launchpad.net/bugs/332606
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
Binary package hint: ipsec-tools
after upgrading from 8.04 to 8.10 (racoon 1:0.6.7-1ubuntu1 to
1:0.7-2.1ubuntu1) ipsec connections fail with these lines in the log:
Feb 21 16:04:15 portableHP racoon: INFO: ISAKMP-SA established
192.168.10.10[4500]-81.80.172.213[4500] spi:05
I'm closing my own bug since it wasn't a bug in Ubuntu but rather in some auto
monitor detection stuff I had done based on
http://ubuntuforums.org/showpost.php?p=2510689
The problem was in fact only occuring at work where I have a KVM switch (just
for the monitor not the keyboard) which was prev
** Attachment added: "lockLogs.tgz"
http://launchpadlibrarian.net/14518881/lockLogs.tgz
--
keyboard freeze at boot after hardy upgrade
https://bugs.launchpad.net/bugs/230399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Public bug reported:
Hi,
I have a Dell Latitude D520 laptop that I've just upgraded from Gutsy to Hardy.
Under Gutsy no problems.
Every boot the keyboard freezes during the gdm login screen (generally I can
enter my username and only a couple of characters of the password before it
freezes)
Wh
I have a work around and the beginning of an analysis at bug
https://bugs.launchpad.net/bugs/183568
I've also marked that bug as a duplicate of this one (since its confirmed)
--
Gusty not shutting down (Deactivating device eth1)
https://bugs.launchpad.net/bugs/156490
You received this bug notifi
*** This bug is a duplicate of bug 156490 ***
https://bugs.launchpad.net/bugs/156490
** This bug has been marked a duplicate of bug 156490
Gusty not shutting down (Deactivating device eth1)
--
Gutsy network-manager causes OS to freeze on system restart or power down
https://bugs.launchpad
Some more details on my setup and investigations.
The problem is 100% reproducable for me on a Dell Latitude D520.
I have narrowed it down as follows:
Boot machine then switch to text console before logging in
Login in text mode as root
/etc/init.d/gdm stop
/etc/dbus-1/event.d/26NetworkManagerDis
The problem appears to be caused when network manager catches the SIGTERM (15)
signal
I have a workaround involving hard killing network manager with SIGKILL:
Modify /etc/dbus-1/event.d/25NetworkManager as follows (just add the
--signal 9 option)
d_stop() {
# Modified MF 11 Feb 2008 To a
12 matches
Mail list logo
