*** This bug is a duplicate of bug 308903 ***
https://bugs.launchpad.net/bugs/308903
And after detailed reading I think, this isn't duplicate of this bug,
because Ive had installed It without problem. Problem is after start
clients. They find configuration file in wrong path, but in #308903
Public bug reported:
Binary package hint: logwatch
I get the following in the email logwatch 7.3.6-1ubuntu1 sends. The
'Unknown lines' all seem reasonably standard, so I don't really care
about them, so they shouldn't be included.
- dpkg status changes Begin
Here it is:
samba 2:3.2.3-1ubuntu3.4~ppa4 available for testing at
https://launchpad.net/~tcarrez/+archive
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Well I'm not sure how to try it as the initial reporter as I don't have
a network drive, just computers. I am not sure how to get the error
output from smbclient. I have found a work around that works fairly
well though. In Xbuutu using konqueror I changed the address bar to a
normal one for
Do we need upstream to fix it or can I (or someone else) try and create
a patch we can use locally until MIT does its thing?
--
kadmind will not listen on IPv6 ports
https://bugs.launchpad.net/bugs/309339
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Status seems to be Fix released. Where it is? I have tried what
Alessandro wrote above, but still buildconf fails with same error?
--
phpize: configure:8184: error: possibly undefined macro: _LT_SET_OPTIONS
https://bugs.launchpad.net/bugs/262251
You received this bug notification because you are
This patch fixes those unknown lines, as well as capturing re-installed
packages and conf file lines that would normally be put in the Unknown
lines section. Backported from latest logwatch cvs.
** Attachment added: patch for unknown lines from logwatch.org cvs
I forgot to mention that my patch is for the Hardy version, but the bug
occurs in the Jaunty version as well.
--
Unrecognised lines in dpkg output
https://bugs.launchpad.net/bugs/309632
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Hi!
Unfortunately, write does not work, at least with my NAS (Conceptronic).
There's a different behaviour between ppa3 and ppa4: In ppa3, after
starting the copy command in Nautilus, automatically and no disk
space was shown, and now, there's a progress bar (with time remaining,
and so on...)
The attached patch solves the problem for me.
** Attachment added: bash_completion.patch
http://launchpadlibrarian.net/20581220/bash_completion.patch
--
bash get_cword: command not found
https://bugs.launchpad.net/bugs/249337
You received this bug notification because you are a member of
Any time line for of getting this package for jaunty working under
intrepid?
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi
This patch should fix both, the postfix and the umount issue.
** Attachment added: bash_completion_umount-postfix.patch
http://launchpadlibrarian.net/20581801/bash_completion_umount-postfix.patch
--
bash get_cword: command not found
https://bugs.launchpad.net/bugs/249337
You received this
Kai:
The patch does not appear to have changed the behaviour from the
previous patch. An smbclient put of a file from a terminal still
results in the ERRHRD -39 error message (after doing a successful ls
first) and a Nautilus drag and drop of a file from the Desktop into
the open NAS folder still
Kai:
The WinXP SP3 trace for reference. Same file name, text2.txt, and NAS
address //192.168.0.195/public
** Attachment added: winxpsp3_cap.pcap
http://launchpadlibrarian.net/20582319/winxpsp3_cap.pcap
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You
squiggleslash squigglesl...@yahoo.com writes:
Do we need upstream to fix it or can I (or someone else) try and create
a patch we can use locally until MIT does its thing?
I honestly don't know. It depends on how deep into the guts of kadmind
and (particularly) the corresponding libraries the
Public bug reported:
The dovecot package does not include a logrotate configuration. If
dovecot is configured to log to file rather than syslog its log file
will become unmanageable. There is a recommended configuration here:
http://wiki.dovecot.org/Logging
# dovecot SIGUSR1: Re-opens the log
You're completely right, this is not a duplicate. Sorry.
** This bug is no longer a duplicate of bug 308903
The bacula-dir.conf file is not present when installing Bacula
** Changed in: bacula (Ubuntu)
Status: Triaged = New
** Bug watch added: Red Hat Bugzilla #426790
** Changed in: bacula (Fedora)
Status: Unknown = In Progress
--
bad path to configuration file
https://bugs.launchpad.net/bugs/306464
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
--
Ubuntu-server-bugs mailing
** Changed in: mysql-dfsg-5.0 (Ubuntu Hardy)
Status: New = Confirmed
--
File conflict between mysql-client-5.0 and mysql-server-5.0
https://bugs.launchpad.net/bugs/304907
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Sorry, I initially confirmed this for hardy, but on closer inspection
the file conflicts don't appear to apply to any versions of the packages
in the Ubuntu archive; marking invalid instead.
As a workaround, you can forcibly install using dpkg --force-overwrite.
** Changed in: mysql-dfsg-5.0
20 matches
Mail list logo
