Jan: In #6 and #15 you state SSL is working, but your installation
stopped working after the dist upgrade as well. What did you do to get
proftpd to work again?
Stefano: The SSL error message and proftpd not starting after a dist
upgrade appear to be related. I have not seen any indication
Yunosh and Stefanor initially indicated proftpd would not start, but
then seem to indicate that proftpd does start for them but generates an
error message. Are some servers starting and others not? Without the
work-around I mentioned before, I could not get proftpd to start at all,
and I see no
My non-SFTP server would not start after the upgrade without changes;
Zeon's SFTP installation would not start without changes. The issue
appears to be that any Ubuntu system with a working proftpd setup will
be broken by an 11.10 distribution upgrade.
I mentioned SFTP only because that feature
ProFTP does not start on server upgraded to 11.10 because of this error.
Remarked out following lines in /etc/proftpd/modules.conf as work-
around:
LoadModule mod_tls.c
LoadModule mod_sftp.c
LoadModule mod_sftp_pam.c
ProFTP starts, but those SSL-dependent services/modules won't work of
course.
I wonder if the problem you observe is the same as the problem I
observe.
Motion in Ubuntu 9.10 (3.2.11-1) will not view BTTV cameras properly on
the first try, either as daemon on a reboot or just starting manually in
shell, or starting daemon manually after a system has been up for a
while.
I, too, have this same problem in 9.10 Karmic 64-bit. Workstation is a
fresh install, and notification is turned on, but I never get a warning
icon when updates are available.
--
kpackagekit update notification tray icons disappear after only a few seconds
https://bugs.launchpad.net/bugs/342017
CGI programs stopped working after upgrade of working 8.10 server to
9.04. Subsequent upgrade to 9.10 did not fix. Complete fresh 9.10
server install on server previously upgraded will still not run CGI
programs.
Can reproduce problem on a second vanilla 64-bit test install of Kubuntu
9.10 (in
Under Related Problem above I meant to say that trying to set the
server.bind option at all fails with the error I listed. The
configuration that works has the server.bind option commented out (the
commented-out example is localhost), which is the default configuration.
In that configuration the
I would like to respectfully request this bug be classified as high
importance, with the hope that it will be addressed soon. The fact is
that Putty is nearly useless without tunneling support, meaning the
package is effectively broken. This bug, as identified here, is now
well over a year old;
My testing also indicates tunneling in Putty is broken. This is true of
32-bit 6.06 LTS test system and 64-bit 6.10 test system. Both appear to
use Putty 0.58-4 version. I also got Windows version to run on same
6.06 LTS 32-bit test system under Wine.
Tunneling is an important feature of
10 matches
Mail list logo
