If I upgrade to 24.04 which just came out today with the 6.8 kernel,
would that also fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060919
Title:
cifs: Copying file to same directory
I have the same problem. After installing the mrtg package on a fresh
Ubuntu 15.04 install, I am missing the mrtg-traffic-sum script so my
monthly stat summary script is failing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After installing postfix/natty-proposed, my problem with the relayhost
requiring the port has also been fixed. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/764096
Title:
After installing postfix/natty-proposed, my problem with the relayhost
requiring the port has also been fixed. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764096
Title:
DNS hostname
I'm on x86_64, not amd64. Here's my master.cf, nothing out of the
ordinary, haven't touched it in a while.
#
# Postfix master process configuration file. For details on the format
# of the file, see the master(5) manual page (command: man 5 master).
#
# Do not forget to execute postfix reload
*** This bug is a duplicate of bug 764096 ***
https://bugs.launchpad.net/bugs/764096
The patch to /etc/init.d/postfix referred to in #764096 worked for me.
I was able to remove the port from my relayhost parameter. Thanks!
--
You received this bug notification because you are a member of
I'm on x86_64, not amd64. Here's my master.cf, nothing out of the
ordinary, haven't touched it in a while.
#
# Postfix master process configuration file. For details on the format
# of the file, see the master(5) manual page (command: man 5 master).
#
# Do not forget to execute postfix reload
*** This bug is a duplicate of bug 764096 ***
https://bugs.launchpad.net/bugs/764096
The patch to /etc/init.d/postfix referred to in #764096 worked for me.
I was able to remove the port from my relayhost parameter. Thanks!
--
You received this bug notification because you are a member of
Here's mine (some custom values removed):
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
disable_vrfy_command = yes
inet_interfaces = all
mailbox_command = procmail -a $EXTENSION
mailbox_size_limit = 0
Here's mine (some custom values removed):
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
disable_vrfy_command = yes
inet_interfaces = all
mailbox_command = procmail -a $EXTENSION
mailbox_size_limit = 0
I agree but can't seem to figure out what it is. It has to be related to
postfix not being able to read the services file, but I've confirmed my
chroot permissions (for /var/spool/postfix/etc/) seem to be correct and
smtp/tcp is in the file. I've tried turning off the chroot jail and the
same
I agree but can't seem to figure out what it is. It has to be related to
postfix not being able to read the services file, but I've confirmed my
chroot permissions (for /var/spool/postfix/etc/) seem to be correct and
smtp/tcp is in the file. I've tried turning off the chroot jail and the
same
I started having the same problem with postfix after upgrading from
Maverick to Natty. I tried the suggestion of adding the port to my
relayhost in main.cf and that fixed it, but is that a valid fix? Or,
like Scott says, there's something else wrong?
--
You received this bug notification because
I'm seeing a similar 'magic number' error when trying to start Calibre
after the upgrade from Maverick to Natty:
Traceback (most recent call last):
File /usr/bin/calibre-server, line 18, in module
from calibre.library.server.main import main
File
I started having the same problem with postfix after upgrading from
Maverick to Natty. I tried the suggestion of adding the port to my
relayhost in main.cf and that fixed it, but is that a valid fix? Or,
like Scott says, there's something else wrong?
--
You received this bug notification because
Ugh, I'd rather not have to do a fresh install of Natty. I'll keep
digging ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691608
Title:
calibre does not start
--
ubuntu-bugs mailing list
Hey hey! Removing calibre and re-installing it fixed the problem, no
need to re-install Natty. Phew!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691608
Title:
calibre does not start
--
Same thing for me. After my Lucid box ran weekly updates I started
seeing the Searching for Suckit rootkit... Warning: /sbin/init
INFECTED message from chkrootkit.
--
False positive for SucKit
https://bugs.launchpad.net/bugs/454566
You received this bug notification because you are a member of
Same thing for me. After my Lucid box ran weekly updates I started
seeing the Searching for Suckit rootkit... Warning: /sbin/init
INFECTED message from chkrootkit.
--
False positive for SucKit
https://bugs.launchpad.net/bugs/454566
You received this bug notification because you are a member of
Both patches worked for me as well, great!
--
libusb_get_report: error sending control message: Operation not permitted
https://bugs.launchpad.net/bugs/572262
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
Both patches worked for me as well, great!
--
libusb_get_report: error sending control message: Operation not permitted
https://bugs.launchpad.net/bugs/572262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm having this same problem since upgrading to Lucid this afternoon and
would like to try out this fix.
--
libusb_get_report: error sending control message: Operation not permitted
https://bugs.launchpad.net/bugs/572262
You received this bug notification because you are a member of Ubuntu
I'm having this same problem since upgrading to Lucid this afternoon and
would like to try out this fix.
--
libusb_get_report: error sending control message: Operation not permitted
https://bugs.launchpad.net/bugs/572262
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm having the same problem with Nagios 3.1.0 after upgrading from 8.10
to 9.04. The nohup trick didn't work for me. If I run nagios straight
from the command-line, without the daemon (-d) switch, I get this. Could
it be related? I don't know what stack smashing is.
Nagios 3.1.0
Copyright (c)
24 matches
Mail list logo
