yep, thats sorted it thankyou
--
package mysql-server-5.0 (not installed) failed to install/upgrade: subprocess
new pre-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/492790
You received this bug notification because you are a member of Ubuntu
Server Team,
For the record:
http://www.squid-cache.org/ menu link: Getting Squid - /Download/
http://www.squid-cache.org/Download/ links: Official source code release -
/Versions/
http://www.squid-cache.org/Versions/ links: langpack - /Versions/langpack/
(was one clicks deeper off the versions
Hi
I'm sorry this was a stupid problem caused by myself. I started the
daemon twice and the second one couldn't connect to the UPS.
Greets Thomas
--
megatec_usb problem (did not claim interface)
https://bugs.launchpad.net/bugs/504897
You received this bug notification because you are a
Another episode of this happened last night, about 4.5 hours after
rebooting to install the new kernel. This is a much shorter timeframe
between episodes. I don't know if this is a fluke or something else.
Same pattern though: the exact same line in the exact same file on the
same site. Again,
I had tried autofs5 before to try and resolve without success.
This time I purged autofs first.
I kept the delivered version of auto.master and added my one line to it (the
difference from my previous attempt was not to remove the +auto.master line).
Restarted and the mount umounted after the
Public bug reported:
Binary package hint: likewise-open
Sorry - Plasma Workspace
KDEINIT could not launch /usr/bin/kdesu
whereby .. the existing binary located at
/usr/bin/kdesu_stub
/usr/bin/kdesudo
** Affects: likewise-open (Ubuntu)
Importance: Undecided
Status: New
--
I currently don't have winbind installed, so there's nothing relevant in
syslog (as far as I can see, which isn't very far!). Which steps should
I follow?
Install winbind, get the syslog, or
install winbind, start the service, get the syslog, or
install winbind, start the service, try using
This bug was fixed in the package samba - 2:3.4.0-3ubuntu5.3
---
samba (2:3.4.0-3ubuntu5.3) karmic-proposed; urgency=low
* debian/samba.if-up: allow NetworkManager as a recognized address
family... it's obviously /not/ an address family, but it's what gets
sent when using
+1. The diff looks good to me.
--
apparmor HOMEDIRS not adjusted for likewise
https://bugs.launchpad.net/bugs/274350
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to likewise-open in ubuntu.
--
Ubuntu-server-bugs mailing list
This bug was fixed in the package likewise-open - 5.4.0.39949-3
---
likewise-open (5.4.0.39949-3) lucid; urgency=low
* add /etc/apparmor.d/tunables/home.d/likewise-open to adjust HOMEDIRS.
- add debian/apparmor.homedirs
- debian/rules: install apparmor.homedirs
-
*** This bug is a duplicate of bug 463684 ***
https://bugs.launchpad.net/bugs/463684
This bug was fixed in the package ubuntu-docs - 10.04.1
---
ubuntu-docs (10.04.1) lucid; urgency=low
* First upload for lucid
* General:
- Refresh pot files
- Changed 'Text Editor'
*** This bug is a duplicate of bug 463684 ***
https://bugs.launchpad.net/bugs/463684
This bug was fixed in the package ubuntu-docs - 10.04.1
---
ubuntu-docs (10.04.1) lucid; urgency=low
* First upload for lucid
* General:
- Refresh pot files
- Changed 'Text Editor'
** Tags added: jaunty
--
quota only displays the first automounted file-system
https://bugs.launchpad.net/bugs/120490
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quota in ubuntu.
--
Ubuntu-server-bugs mailing list
Public bug reported:
ssh-add -D seems to NOT remove my identities, even though it says it
did.
Also, why are all possible identities auto-added right away (on start?)
ra...@lcwood(22:11:48)~$ ssh-add -l
8192 d1:50:43:64:52:7d:a0:61:ad:e2:bb:17:35:0d:7f:7d rafal1-ra...@lcwood (RSA)
8192
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/37658272/XsessionErrors.txt
--
ssh-add -D deleting all identities does not work. Also, why are all identities
auto-added?
https://bugs.launchpad.net/bugs/505278
You received this bug notification because you are a member
Confirming:
cer...@xango:~/Can$ ssh-add -l
2048 7d:01:74:bd:a6:7f:58:3f:57:e0:1b:da:a0:31:a8:ae hg...@xango2 (RSA)
cer...@xango:~/Can$ ssh-add -D
All identities removed.
cer...@xango:~/Can$ ssh-add -l
cer...@xango:~/Can$ apt-cache policy openssh-client
openssh-client:
Installed:
Somehow I overwrote part of the above. The test is here:
cer...@xango:~/Can$ ssh-add -l
2048 7d:01:74:bd:a6:7f:58:3f:57:e0:1b:da:a0:31:a8:ae hg...@xango2 (RSA)
cer...@xango:~/Can$ ssh-add -D
All identities removed.
cer...@xango:~/Can$ ssh-add -l
2048
Public bug reported:
Binary package hint: clamav
I am using Jaunty. I get the following messages when I try to Add/Remove
software:
E: clamav-base: subprocess post-installation script returned error exit status
1
E: clamav-freshclam: dependency problems - leaving unconfigured
E: clamav:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37659861/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/37659862/DpkgTerminalLog.txt
--
package clamav-base 0.95.3+dfsg-1ubuntu0.09.04 failed to install/upgrade:
subprocess
Public bug reported:
Client: Ubuntu 9.10
Server: Debian Lenny
This may be a bug in ubuntu client or in debian server.
SSH pubkey was working normally.
I today tried to passwd -l one of the users. After that time I noticed ssh
pubkey login stoped working.
New account was crated on server (new
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/37660051/XsessionErrors.txt
--
pubkey login stoped working
https://bugs.launchpad.net/bugs/505301
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
Thanks for your report.
From the log:
Setting up clamav-base (0.95.3+dfsg-1ubuntu0.09.04) ...
id: clamav: No such user
chown: invalid user: `clamav:clamav'
chown: invalid user: `clamav:clamav'
install: invalid user `clamav'
It looks like you've lost the clamav user. That's quite odd. Any idea
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
after chmod 700 /home/userfoo/.ssh/ ; /etc/init.d/ssh restart still
identical problem
--
pubkey login stoped working
https://bugs.launchpad.net/bugs/505301
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Solved, /home perms where wrong.
It would be nice to have openssh say a bit more about this problem in
logs on DEBUG3, then just
Jan 10 00:54:16 vz1947 sshd[32763]: debug1: trying public key file
/home/userfoo/.ssh/authorized_keys
Jan 10 00:54:16 vz1947 sshd[32763]: debug1: restore_uid: 0/0
--
** Changed in: squid (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: squid (Ubuntu)
Status: New = Confirmed
--
Loop with moved_temporarily and when using storeurl
https://bugs.launchpad.net/bugs/503777
You received this bug notification because you are a member of Ubuntu
Indeed this kind of error does not have a distinctive message for noone
** Summary changed:
- pubkey login stoped working
+ openssh server should warn that .ssh/authorized_keys is not accessible
(causing ssh pubkey authentication to fail silently)
** Changed in: openssh (Ubuntu)
Status:
please do nor confirm your own bugs.
** Changed in: openssh (Ubuntu)
Status: Confirmed = New
--
openssh server should warn that .ssh/authorized_keys is not accessible (causing
ssh pubkey authentication to fail silently)
https://bugs.launchpad.net/bugs/505301
You received this bug
** Visibility changed to: Private
** Visibility changed to: Public
--
openssh server should warn that .ssh/authorized_keys is not accessible (causing
ssh pubkey authentication to fail silently)
https://bugs.launchpad.net/bugs/505301
You received this bug notification because you are a member
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
OpenSSH does not log failed attempts when key authentication is used
https://bugs.launchpad.net/bugs/501956
You received this bug notification because you are a
** Bug watch added: OpenSSH Portable Bugzilla #1554
https://bugzilla.mindrot.org/show_bug.cgi?id=1554
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=1554
Importance: Unknown
Status: Unknown
--
openssh server should warn that .ssh/authorized_keys is not
On second thought, this isn't the correct upstream as the reported here
is asking for /var/log/auth.log logging and according to upstream that
should already be done. The upstream bug was for client notification of
the issue which isn't really possible as described upstream.
** Changed in:
** Changed in: openssh
Importance: Undecided = Unknown
** Changed in: openssh
Status: New = Unknown
** Changed in: openssh
Remote watch: None = OpenSSH Portable Bugzilla #1554
--
openssh server should warn that .ssh/authorized_keys is not accessible (causing
ssh pubkey
** Bug watch added: OpenSSH Portable Bugzilla #974
https://bugzilla.mindrot.org/show_bug.cgi?id=974
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=974
Importance: Unknown
Status: Unknown
--
OpenSSH does not log failed attempts when key authentication
To get rid of the bayes: synced databases from journal emails reported
in comment 2, try this patch to /usr/bin/sa-learn. It turns off verbose
mode (forced on by --sync) which is what causes the output.
** Attachment added: Patch to turn off verbose mode when sa-learn --sync is
run
Yes.
2010-01-09 01:00:15 Backup failed on localhost
http://localhost/backuppc/index.cgi?host=localhost (Tar exited with
error 512 () status)
I do get email messages
Message 27:
From backu...@venus.ls.net Thu Jan 7 01:00:05 2010
X-Original-To: backuppc
To: backu...@venus.ls.net
cc:
Subject:
The attached trivial patch applies the wish I described above,
it informs more why authorized_keys is not being used.
The patch is tested for all error conditions it should report, both with
default LogLevel INFO, as well as with DEBUG3.
Below detaild explanation what it does - and results of
Updating upstream bug
** Bug watch added: OpenSSH Portable Bugzilla #1694
https://bugzilla.mindrot.org/show_bug.cgi?id=1694
** Changed in: openssh
Remote watch: OpenSSH Portable Bugzilla #1554 = OpenSSH Portable Bugzilla
#1694
--
openssh server should warn that .ssh/authorized_keys is not
Marking this Triaged as we have an upstream bug. Thank you Limcore for
upstreaming this.
** Changed in: openssh (Ubuntu)
Status: New = Triaged
--
openssh server should warn that .ssh/authorized_keys is not accessible (causing
ssh pubkey authentication to fail silently)
Created new upstream bug because bugzilla 1554 was for something a bit
different
** Bug watch added: OpenSSH Portable Bugzilla #1694
https://bugzilla.mindrot.org/show_bug.cgi?id=1694
--
openssh server should warn that .ssh/authorized_keys is not accessible (causing
ssh pubkey authentication
** Changed in: xsensors (Debian)
Importance: Undecided = Unknown
** Changed in: xsensors (Debian)
Status: Fix Released = Unknown
** Changed in: xsensors (Debian)
Remote watch: None = Debian Bug tracker #460170
--
[hardy] Error opening config file: /etc/sensors.conf
41 matches
Mail list logo
