kuser: this bug was closed, please open another one.
When a server program does not start you can usually get useful information
from the log files (/var/log/syslog, and for samba /var/log/samba/log.*). Could
you attach the relevant error messages you found there to that new bug ? Thanks.
--
Apparently you are not the only one experiencing problems to interact
with that specific kind of NAS box.
See
http://www.iomegasupportforums.com/phpbb2/viewtopic.php?t=11672
or
In Jaunty it doesn't segfault anymore, it just fails miserably. I'm
closing this as Fix Released in the development release.
However, I agree that the most things won't work message is an
understatement, and that PANIC/BACKTRACE messages are not exactly the
best way to handle some very common
Any testers?
--
Current eBox packages in intrepid don't work at all
https://bugs.launchpad.net/bugs/273486
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
strace output of sftp session, pressing ä at the sftp prompt:
[...]
write(1, sftp ..., 6sftp )= 6
read(0, \303..., 1) = 1
read(0, \244..., 1) = 1
write(1, \7..., 1)= 1
read(0,
** Changed in: openssh (Ubuntu)
Adrien, since you reported the bug, your feedback about the packages in
-proposed is highly appreciated as well. Does it fix the issue for you,
and does the package still work for you?
--
getent group crashes winbindd on domain controller
https://bugs.launchpad.net/bugs/328874
You received this
My main concern is to get feedback about regressions. Upstream certainly
knows what they are doing, and the patch might fix the bug, but it is
important to get feedback from other users whether their system still
works (misbuild, using different toolchain version than last build of
the package,
There are two problems in this bug. First one is an easy one (I attached
a patch for dovecot for it) - dovecot-postfix postinst script should
restart dovecot *after* the certificate links are created, not before.
The second one is about postfix - If you check out DpkgTerminaLog.gz,
you'll notice:
Ok, that happened cause user selected No configuration for postfix.
dovecot-postfix should be aware of that situation and shouldn't just
fail to install. This patch solves the issue.
** Attachment added: dovecot-postfix.debdiff
http://launchpadlibrarian.net/25534312/dovecot-postfix.debdiff
--
Public bug reported:
This happens with update manager.
Even when i try to reconfigure Postfix it gives me following error:
/usr/sbin/dpkg-reconfigure: postfix is broken or not fully installed.
I have upgraded to 9.04 and it hass given me this problem.
** Affects: postfix (Ubuntu)
Could you run 'DEBCONF_DEBUG=developer dpkg --configure -a'? This
might give you more information.
--
Not able to fix while update - crashes - /usr/sbin/dpkg-reconfigure: postfix is
broken or not fully installed
https://bugs.launchpad.net/bugs/362344
You received this bug notification because
** Changed in: dovecot (Ubuntu)
Status: Confirmed = Fix Committed
--
fatal errors during install
https://bugs.launchpad.net/bugs/360891
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
--
Ubuntu-server-bugs
Public bug reported:
Spent all night to understand why public key ssh auth doesn't work. It
seems to me that issue only affects Jaunty. Please have a look at the
details below.
So, the configuration is:
1. Client
- lsb_release: Ubuntu 8.10 intrepid
- ssh-client: OpenSSH_5.1p1 Debian-3ubuntu1,
** Attachment added: ssh -
http://launchpadlibrarian.net/25547970/ssh-client.txt
--
Public key ssh auth doesn't work in Jauny
https://bugs.launchpad.net/bugs/362427
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in
Please try public key ssh auth with Jaunty server and confirm. It seems
to me this is an important issue.
--
Public key ssh auth doesn't work in Jauny
https://bugs.launchpad.net/bugs/362427
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Do you use encrypted home directories on the server?
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
Public key ssh auth doesn't work in Jauny
https://bugs.launchpad.net/bugs/362427
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Yes, I do. You can find some information related to encryptfs in sshd
log.
** Summary changed:
- Public key ssh auth doesn't work in Jauny
+ Public key ssh auth doesn't work in Jaunty
--
Public key ssh auth doesn't work in Jaunty
https://bugs.launchpad.net/bugs/362427
You received this bug
Okej, sorry, I guess I didn't read the logs as carefully as I should
have.
Anyhow, I'm rather sure your encrypted home directory is the reason why
you can't use public key ssh auth. Considering that encryptfs decrypts
your home directory, using your login password, at login time. Hence,
when
Hmm.. Well, sound like it's not a bug. Thank you for explanation!
But are there any solution or workaround to use public key auth with
encrypted home dir?
--
Public key ssh auth doesn't work in Jaunty
https://bugs.launchpad.net/bugs/362427
You received this bug notification because you are a
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=6090
Importance: Unknown
Status: Unknown
--
cifs mounts: unable to move dangling symlinks (case of svn ceckout with
symlinks)
https://bugs.launchpad.net/bugs/117727
You received this bug notification because you
Public bug reported:
Source package: openssh_5.1p1.orig.tar.gz + openssh_5.1p1-5ubuntu1.diff.gz
Ubuntu Release: Jaunty
Package Version: openssh-server_5.1p1-5ubuntu1
When using OpenSSH's ForceCommand sshd_config directive to launch its
internal-sftp, it is not possible to pass arguments to the
** Attachment added: Taken from
https://bugzilla.mindrot.org/show_bug.cgi?id=1527 and adjusted for ubuntu
source package
http://launchpadlibrarian.net/2232/openssh_forcecommand.patch
--
force-command unable to pass arguments along to internal-sftp
https://bugs.launchpad.net/bugs/362511
*** This bug is a duplicate of bug 362511 ***
https://bugs.launchpad.net/bugs/362511
Public bug reported:
Source package: openssh_5.1p1.orig.tar.gz + openssh_5.1p1-5ubuntu1.diff.gz
Ubuntu Release: Jaunty
Package Version: openssh-server_5.1p1-5ubuntu1
When using OpenSSH's ForceCommand
I think it's a bug, but not related to openssh.
I fixed the issue by adding this to sshd_config:
AuthorizedKeysFile /etc/.ssh/%u/authorized_keys
--
Public key ssh auth doesn't work in Jaunty
https://bugs.launchpad.net/bugs/362427
You received this bug notification because you are a member
The attached patch is taken from the first of the above links and
adjusted to patch the openssh_5.1p1-5ubuntu1 source package.
** Attachment removed: Taken from
https://bugzilla.mindrot.org/show_bug.cgi?id=1527 and adjusted for ubuntu
source package
I'm setting this bug as confirmed based on upstream report, as well on
some quick testing of my own.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
** Bug watch added: OpenSSH Portable Bugzilla #1527
https://bugzilla.mindrot.org/show_bug.cgi?id=1527
** Also affects: openssh
@Carsten: By the way, thanks for supplying the modified patch.
Right now Jaunty is in FinalFreeze, but after Release I'll take a look
at it and see if I can create a debdiff to be upload. Just not sure if
it will be important enough for a SRU, or if it will have to wait for
Karmic.
** Changed in: openssh
Status: Unknown = Fix Released
--
force-command unable to pass arguments along to internal-sftp
https://bugs.launchpad.net/bugs/362511
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Unfortunately I didn't think of the RC-Release/FinalFreeze, otherwise I'd have
published that bug report earlier.
Anyhow, I seriously doubt that too many users will miss this feature in Jaunty,
since it has only been introduced in OpenSSH 4.8p1 and is available in Ubuntu
since Intrepid. I for
@Carsten: You'r probably right about it not being important enough for a
SRU. Unless somehow disagree and actually makes it happen, feel free to
ping this bug when the Karmic development has started.
Might also be a good idea to report this bug to the Debian BTS. Do you
want to do it, or shall I?
Blueprint changed by Dustin Kirkland:
Assignee: Dustin Kirkland = Scott James Remnant
--
Support Swapfiles at Installation
https://blueprints.edge.launchpad.net/ubuntu/+spec/swapfile-in-the-installer
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
Okay, so your public key is locked away in encryption, if you're not
already logged into the system.
You can work around this by accessing your un-mounted (ie,
not-encrypted) home directory, and putting your public key there.
$ /sbin/ecryptfs.umount_private cd /sbin/ecryptfs.mount_private
$
@Andreas: I'd like to report it myself. Thanks for both the hint and the
offer, though. I just want to repay both Debian and Ubuntu a tiny part
of what I owe both of them. ;)
--
force-command unable to pass arguments along to internal-sftp
https://bugs.launchpad.net/bugs/362511
You received this
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
--
net-snmp
This bug was fixed in the package amavisd-new - 1:2.6.2-2ubuntu2
---
amavisd-new (1:2.6.2-2ubuntu2) jaunty; urgency=low
* fix default config to not send bounce mail to sender for
banned filenames in mail (LP: #360689)
- debian/etc/conf.d/21-ubuntu_defaults
-- Imre Gergely
35 matches
Mail list logo
