[Bug 634839] Re: package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2010-09-14 Thread firebird
excuse me chuck but why would this be invalid? do you consider postfix to behave properly if it just crashes over a non existing /etc/aliases? I am just saying that it requires about one line of code to fix this, something like if [! test -f /etc/aliases]; touch /etc/aliases; ... (or so i am

[Bug 634839] Re: package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2010-09-14 Thread firebird
Hi Clint! Fair enuff, thanks for your explanations, new informatins will follow briefly! Your's, firebug -- package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/634839 You received this

[Bug 634839] Re: package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2010-09-13 Thread firebird
Hi Clint! Nope, none of the above, /etc has completely normal acces/ownership attributes and no hardening, no SELinux or what so ever. Bad thing is I have been tinkering around so much meanwhile that i don't recall with 100% certainty if it was due to the file not existing at the time... If i

[Bug 634839] [NEW] package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2010-09-10 Thread firebird
Public bug reported: Binary package hint: postfix Hi guys! This is what console said: Running newaliases postalias: fatal: open database /etc/aliases.db: Permission denied dpkg: error processing postfix (--configure): subprocess installed post-installation script returned error exit status 1

[Bug 634839] Re: package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2010-09-10 Thread firebird
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/634839/+attachment/1565446/+files/Dependencies.txt ** Attachment added: Df.txt https://bugs.launchpad.net/bugs/634839/+attachment/1565447/+files/Df.txt ** Attachment added: Dmesg.txt

[Bug 383084] Re: autofs doesn't start on boottime and ghost option is being ingnored on HP machines

2010-03-19 Thread firebird
Dear Chuck! Here's what i can do for you: As mentioned above i put a line /etc/init.d/autofs start into /etc/rc.local but this did not work anymore since some updates last week, so I put a echo 'ifconfig` /tmp/bla.txt infront of that line and i saw from that that the ethernet interface did

[Bug 383084] Re: autofs doesn't start on boottime and ghost option is being ingnored on HP machines

2010-03-12 Thread firebird
Dear Chuck! As I am still interested in finding a solution to this I would very much like to help you in solving this, but unfortunately I cannot quite understand how I am supposed to reproduce he failure with a live cd as the malfunction occurs during startup and I seriously don't want to

[Bug 383084] Re: autofs doesn't start on boottime and ghost option is being ingnored on HP machines

2009-10-16 Thread firebird
Hi Chuck! All of these machines run Ubuntu Jaunty Jackalope 9.04 and are configured to use dhcp ips where the lease is configured to never expire and the machines also have a reserved ip, meaning always the same one. So from a technical point of view it is dhcp but practically the ips are

[Bug 383084] Re: autofs doesn't start on boottime and ghost option is being ingnored on HP machines

2009-10-14 Thread firebird
Hi Chuck! Yes, unfortunately nothing has changed so far, problem still persists... Faithfully, firebug -- autofs doesn't start on boottime and ghost option is being ingnored on HP machines https://bugs.launchpad.net/bugs/383084 You received this bug notification because you are a member of

[Bug 347788] Re: OpenVPN client does not recognize WLAN connections

2009-10-11 Thread firebird
Hi Chuck! As I can see somebody still cares about this so I wanted to let you know that this woks now! I have no idea what has been changed but I tried it once more the other day and it works now, so from my point of wiev this thread can be closed. Your's, firebug -- OpenVPN client does not

[Bug 347788] Re: OpenVPN client does not recognize WLAN connections

2009-03-25 Thread firebird
ok, i am starting to understand, what you meant by more information on the configuration: i have defined the LAN connection during installation of intrepid, and of course i can see it in network-manager as eth0. checkbox system setting is enabled there. the vpn is not configured in

[Bug 347788] Re: OpenVPN client does not recognize WLAN connections

2009-03-25 Thread firebird
err yes, as far as i can see with tail -f on /var/log/daemon.log nothing is being inserted there if i start the vpn via openvpngui, so heres another log from the openvpn output window. i believe these two lines to be the interesting ones: Wed Mar 25 10:17:01 2009 TLS Error: TLS key negotiation

[Bug 347788] [NEW] OpenVPN client does not recognize WLAN connections

2009-03-24 Thread firebird
Public bug reported: Binary package hint: openvpn Hi folks! This seems to be a common sight according to several threads i found on google, and btw. since several Ubuntu versions: OpenVPN client connects perfectly as long as there is a cable attached to the computer. If you try to use the WLAN

[Bug 347788] Re: OpenVPN client does not recognize WLAN connections

2009-03-24 Thread firebird
uh, one thing i missed; i added the keyword float to the config right below the line with the remote keyword, as an error on first connection attempt tells me to do so. -- OpenVPN client does not recognize WLAN connections https://bugs.launchpad.net/bugs/347788 You received this bug notification

[Bug 347788] Re: OpenVPN client does not recognize WLAN connections

2009-03-24 Thread firebird
sure, whatever you need! Intrepid's network setup is an out of the box setup, i didn't change anything there, exept that i configured a static ip instead of a dynamic one for the wired connection. ** Attachment added: That woiuld be the client configuration