[Bug 1811122] Re: Cannot use xrdp to login to sesman-Xvnc after 0.6.1-2ubuntu0.1
I can confirm that the 0.6.1-2ubuntu0.3 version from the security- proposed PPA works on my test 16.04 system, both as an upgrade from 0.6.1-2, and as an upgrade from 0.6.1-2ubuntu0.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811122 Title: Cannot use xrdp to login to sesman-Xvnc after 0.6.1-2ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1811122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811122] Re: Cannot use xrdp to login to sesman-Xvnc after 0.6.1-2ubuntu0.1
I tried installing 0.6.1-2ubuntu0.2 from the ubuntu-security-proposed PPA, but the new version appears to have the same sort of problem as 0.6.1-2ubuntu0.1: the connection between the session manager and Xvnc fails with the "password failed", "error - problem connecting" messages in the connection log window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811122 Title: Cannot use xrdp to login to sesman-Xvnc after 0.6.1-2ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1811122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I have the same problem as William Jojo (w-jojo) reported in #54. The Shibboleth authentication package (libapache2-mod-shib2) in Bionic Universe depends on libcurl3 (via libxmltooling7). I'm told in bug #1776489 that this is because upstream Shibboleth hasn't yet released a version that works with OpenSSL 1.1, so it genuinely needs libcurl3/libssl1.0.0. Even when Shibboleth 3 is released by upstream, presumably it will not appear in Bionic, except perhaps as a backport? So we need a solution for proper libcurl3 / libcurl4 co-existence in Bionic, if the Shibboleth SSO stack is going to work in the current LTS cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776489] [NEW] libxmltooling7 depends on libcurl3, which has been replaced by libcurl4 in Bionic
Public bug reported: I am attempting to make use of libapache2-mod-shib2 on Ubuntu 18.04 LTS. Shibboleth installs and works as expected on top of a minimal Ubuntu install. However it has a dependency on libcurl3 (via libxmltooling7). Almost all of the other libcurl using packages on Ubuntu 18.04 depend on libcurl4. libcurl4 is declared to conflict with libcurl3. Therefore, almost no other libcurl using packages in 18.04 can co-exist with the Shibboleth packages. ** Affects: xmltooling (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776489 Title: libxmltooling7 depends on libcurl3, which has been replaced by libcurl4 in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmltooling/+bug/1776489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570472] Re: Set systemd as default service provider
Upstart is still installed on desktop Xenial systems, even on a fresh installation; the unity-greeter package depends on it. Attempting to "apt-get remove upstart" also offers to remove the "ubuntu-desktop", "unity", and "unity-greeter" packages, along with the "upstart" package. So this bug prevents the use of Puppet from correctly managing any services on a Xenial desktop system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570472 Title: Set systemd as default service provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564748] Re: Xvnc does not support open gl
I observe the same problem on Lucid, with vnc4server-4.1.1+xorg4.3.0-37ubuntu2. -- Xvnc does not support open gl https://bugs.launchpad.net/bugs/564748 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409438] Re: Multi-user sec=krb5 NFSv4 client blocks when one user has an expired ticket
I have recently set up an Ubuntu 9.10 release candidate system for testing, and I am able to reproduce this problem there, too. My new test system does not us the automounter - I encounter the same problem with a statically (fstab) mounted NFS4 sec=krb5 home directory tree and two kerberised login accounts. It seems to to affect a wide range of kernel versions, both i386 and amd64 architectures, and be observable/reproducible on any system using pam-krb5 for authentication/ticket acquisition and kerberised NFS4 home directories. -- Multi-user sec=krb5 NFSv4 client blocks when one user has an expired ticket https://bugs.launchpad.net/bugs/409438 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409438] [NEW] Multi-user sec=krb5 NFSv4 client blocks when one user has an expired ticket
Public bug reported: I have an Ubuntu 08.04.3 NFSv4 server and a number of NFSv4 clients, also running Ubuntu 08.04.3. The clients use autofs to mount user home directories from the server. I use Kerberos to authenticate the users logging into the clients (using pam_krb5), and require Kerberos authentication of NFS traffic via the sec=krb5 export and mount options. Things seem to work normally on a workstation used by only one user - people can log in, get, valid kerberos tickets from the KDC and their home directory mounts automatically. However, a problem arises on multi-user systems: if one user (say user A) has successfully logged in and left themselves logged in such that their Kerberos TGT has expired, then a second user (user B) attempts to log into the same system then the attempt to access the home directory of user B blocks indefinately. If user A subsequently obtains a new Kerberos TGT then the login attempt belonging to user B unblocks and runs to a successful completion. While B is blocked, the kernel logs the following error message over and over again, at a very high rate (3000-6000 times a second): Aug 5 11:37:14 ulf kernel: [3099781.024499] Error: state recovery failed on NFSv4 server 163.1.248.155 with error 13 Aug 5 11:37:14 ulf kernel: [3099781.025007] Error: state recovery failed on NFSv4 server 163.1.248.155 with error 13 Aug 5 11:37:14 ulf kernel: [3099781.025483] Error: state recovery failed on NFSv4 server 163.1.248.155 with error 13 The symptoms that I am observing sound exactly like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446238 To be clear: I expect user A's access to NFS mounted filesystems to fail when their Kerberos tickets have expired, but I don't expect user B's access to the same filesystems to depend on user A. ProblemType: Bug Architecture: amd64 Date: Wed Aug 5 17:09:42 2009 Dependencies: DistroRelease: Ubuntu 8.04 Package: linux None [modified: /var/lib/dpkg/info/linux.list] PackageArchitecture: amd64 ProcEnviron: PATH=/opt/mricron:/nfs4/willis.dpag.ox.ac.uk/software/unix/matlab/2009a/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta Uname: Linux 2.6.24-24-generic x86_64 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug krb5 nfs4 -- Multi-user sec=krb5 NFSv4 client blocks when one user has an expired ticket https://bugs.launchpad.net/bugs/409438 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212485] Re: kernel bug rpc nfs client
For the record, I have been running linux-image-2.6.24-24-generic version 2.6.24-24.54 from hardy-proposed on my primary x86-64 workstation for the last two weeks. In that time I haven't experienced any of the NFSv4 hang-ups that I was previously observing, and no instances of the kernel BUG backtrace appear in the logs. -- kernel bug rpc nfs client https://bugs.launchpad.net/bugs/212485 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81242] Re: postfix-ldap is linked against gnuTLS
I'm setting up some servers and workstations using Hardy, and just got bitten by this problem - default configuration of postfix is chrooted, postfix-ldap will not work against an LDAP server using SSL/TLS because the /dev/random and /dev/urandom devices are not present in the chroot, which prevents gnutls from initializing an SSL connection. It took me ages to find out what was wrong and how to work around it. Should the postfix package not be updated to mknod suitable devices in /var/spool/postfix/dev on installation? -- postfix-ldap is linked against gnuTLS https://bugs.launchpad.net/bugs/81242 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
