Public bug reported:
Binary package hint: mantis
A)Install mantis
B)The debconf utility will eventually ask you to supply a password for the
administrator
C)The supplied password is completly ignored and the default username and
password of administrator and root are used.
** Affects: mantis (
** Summary changed:
- Debconf does not set administrator password
+ Debconf does not set mantis administrator password
--
Debconf does not set mantis administrator password
https://launchpad.net/bugs/50622
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
** Changed in: clamav (Ubuntu)
Status: Unconfirmed => Confirmed
--
ClamAV-Daemon Out of date
https://launchpad.net/bugs/53856
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Using always_direct allow all, in most cases defeats the purpose of
using a proxy. I have pinned to dapper for squid until this is fixed.
--
squid transparent proxy is broken
https://launchpad.net/bugs/68818
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
This bug occurs in Feisty.
--
[Feisty] upgrade breaks network in roaming mode
https://bugs.launchpad.net/bugs/152994
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Public bug reported:
Binary package hint: network-manager
Applying the latest updates since the Release Candidate ISO was released
causes nm-applet to show that no networks are detected.
Workaround: Disable roaming mode and configure network interface
manually
Installed in VMWare 6, with VMWare
** Summary changed:
- upgread breaks network in roaming mode
+ [Feisty] upgrade breaks network in roaming mode
--
[Feisty] upgrade breaks network in roaming mode
https://bugs.launchpad.net/bugs/152994
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
The bug occurs in Feisty.
Alexander Sack wrote:
> Gutsy or feisty?
>
> ** Changed in: network-manager (Ubuntu)
>Status: New => Incomplete
>
>
--
[Feisty] upgrade breaks network in roaming mode
https://bugs.launchpad.net/bugs/152994
You received this bug notification because you are a memb
Requested information supplied. If further information is required,
please do not hesitate to comment.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
[Feisty] upgrade breaks network in roaming mode
https://bugs.launchpad.net/bugs/152994
You received this bug notifica
I'll have to apologise, the release was in fact Gutsy, guess I've been used
to using the Feisty codename for so long eh ;)
I have attached the required files, and included output from ifconfig -a
also.
On 15/10/2007, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> please attach your /etc/lsb-relea
/etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"
/etc/network/interfaces
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"
--
[Gutsy] upgrade breaks network in roaming mode
https://bugs.
/etc/network/interfaces
auto lo
iface lo inet loopback
iface eth0 inet dhcp
auto eth0
--
[Gutsy] upgrade breaks network in roaming mode
https://bugs.launchpad.net/bugs/152994
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
That's the problem,
Doing so causes the network not to be detected according to the nm-applet
I'm using the non-roaming mode as a workaround to get network access.
Alexander Sack wrote:
> well ... that setup doesn't capture "roaming mode". Please either remove
> the iface eth0 file from /etc/networ
The following output was produced:
Oct 16 12:23:11 defiant NetworkManager: nm_signal_handler(): Caught
signal 15, shutting down normally.
Oct 16 12:23:11 defiant NetworkManager: Caught terminiation signal
Oct 16 12:23:11 defiant NetworkManager: [1192533791.612324]
nm_print_open_socks(): O
As a workaround until the bug is fixed, you can disable roaming mode on the
VMware wired adapter and specify dhcp configuration.
That should at least keep you online until a fix released.
--
[vmware] nm-applet "No Network Devices Have Been Found" error
https://bugs.launchpad.net/bugs/153635
You
No, This worked fine in the Gutsy beta release iso. It broke on update
from there.
--
[vmware] nm-applet "No Network Devices Have Been Found" error
https://bugs.launchpad.net/bugs/153635
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Setting the following in squid.conf before starting squid will reproduce
this bug.
httpd_accel_host virtual
httpd_accel_port 80
httpd_accel_with_proxy on
httpd_accel_uses_host_header on
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
This happening for me too
--
Internal Error, Could not perform immediate configuration (2) on libpam0g
https://bugs.launchpad.net/bugs/217435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can confirm that this now works. I have installed the version in
edgy-proposed and the transparent option now works.
Martin Pitt wrote:
| Can someone please test this? Martin OConnor?
|
| This SRU is very old, and if it does not get verified I&#x
squid 2.6.1-3ubuntu1.6 from edgy-proposed works as required as a
transparent proxy
** Tags added: verification-done
** Tags removed: verification-needed
--
squid transparent proxy is broken
https://bugs.launchpad.net/bugs/68818
You received this bug notification because you are a member of Ubun
Public bug reported:
Binary package hint: squid
In package 2.6.1-3ubuntu1 , the transparent option in squid.conf is
broken in Squid upstream version 2.6.RELEASE1. This has been fixed in
2.6.RELEASE2.
Recommend 2.6.RELEASE2 be added to edgy-backports.
** Affects: squid (Ubuntu)
Importance:
** Bug watch added: Squid Bugzilla #1650
http://www.squid-cache.org/bugs/show_bug.cgi?id=1650
** Also affects: squid (upstream) via
http://www.squid-cache.org/bugs/show_bug.cgi?id=1650
Importance: Unknown
Status: Unknown
--
squid transparent proxy is broken
https://launchpad.net/
Remember this is an upstream bug that was broken and has also been fixed
upstream. Ideally, the upstream version of squid this package uses
should be updated to a more recent version where the fix has been
applied.
--
squid transparent proxy is broken
https://launchpad.net/bugs/68818
--
ubuntu-
Public bug reported:
In Ubuntu 10.04, any environment variables assigned in ~/.pam_environment do
not seem to be applied.
for example if I have a ~/.pam_environment as follows
MY_VARIABLE="SOMETHING"
after restarting and starting a shell I would expect
echo $MY_VARIABLE
to respond with
SOMETH
24 matches
Mail list logo
