Please could you post a test case that can be reproduced by others? Once
done, please change the bug status to New. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1018315
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I can reproduce the behaviour you have described in 12.04. If you use
sudo aptitude --safe-resolver install apache2 php5 libapache2-mod-php5
mysql-server, then this should work non-interactively. Or just accept
** Changed in: cobbler (Ubuntu)
Status: New = Triaged
** Changed in: cobbler (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/1092598
** Changed in: cobbler (Ubuntu)
Status: New = Triaged
** Changed in: cobbler (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/1092595
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This appears already fixed in the current development release, so I'm
marking this Fix Released.
If you'd like this fixed in Precise, then I think this is a reasonable
candidate for a stable release update, but
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Both Ubuntu Raring and Debian sid are currently on 1.10.1+dfsg-3, so
this needs to be addressed with the new upstream release in Debian
first, and then Ubuntu will be able to sync.
If you need a backport to an
Considering it's such an easy patch, no reason not to apply it though.
For the development release, it adds extra work to whoever does merges
in the future, and introduces the risk of an accidental regression if
not everything through to upstream has updated before Ubuntu. But if you
get the
Since you now have a patch that appears to work, I presume this can be
marked Triaged?
** Changed in: multipath-tools (Ubuntu)
Status: New = Triaged
** Changed in: multipath-tools (Ubuntu Quantal)
Status: New = Triaged
--
You received this bug notification because you are a
** Changed in: autofs (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1084178
Title:
auto.net does not handle mutliple mount points from a
** Changed in: squid3 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1094944
Title:
squid3 remove doesn't delete logrotate conf file
To
** Changed in: puppet (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1093934
Title:
puppetmaster-passenger fails to run
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I regret that I cannot understand your report. Please could you clarify?
In particular, please could you post precise steps to reproduce your
bug, exactly what you expect to see, and exactly what is happening
Public bug reported:
Also affects genshi 0.6-3 in sid, which should be able to be synced as
the entire Ubuntu delta has been taken up in Debian.
The problem is that raring's python2.7 incorporates changeset
http://hg.python.org/cpython/rev/eb7ea51e658e/ which changed the
definition of
Public bug reported:
In raring, some library functions are returning longs instead of ints.
This is different from behaviour in quantal. This is causing an FTBFS in
genshi due to doctest failures.
Building from upstream source exhibits correct behaviour, including from
upstream orig tarballs and
Second cause of this FTBFS is a possible Python regression in bug
1097783.
** Tags added: ftbfs raring
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
https://bugs.launchpad.net/bugs/1097776
Title:
genshi
=66712c23388e93e5c518ebc8515140fa0c807348.
** Affects: nagios-plugins (Ubuntu)
Importance: High
Assignee: Robie Basak (racb)
Status: In Progress
** Tags: ftbfs raring
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https
** Bug watch added: SourceForge.net Tracker #3600122
http://sourceforge.net/support/tracker.php?aid=3600122
** Also affects: nagios-plugins via
http://sourceforge.net/support/tracker.php?aid=3600122
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Patch added: nagios-plugins.debdiff
https://bugs.launchpad.net/nagios-plugins/+bug/1097848/+attachment/3478295/+files/nagios-plugins.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
** Attachment added: nagios-plugins_1.4.15-5ubuntu5_amd64.build
https://bugs.launchpad.net/nagios-plugins/+bug/1097848/+attachment/3478296/+files/nagios-plugins_1.4.15-5ubuntu5_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I've checked that this now builds and that a resulting binary
(check_apt) appears to work.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1097848
Title:
nagios-plugins
#20 is exactly what happens in the MAAS QA lab every day. I don't
believe that this bug has been seen there.
Regardless of that, I'd really like to see a tcpdump of all DHCP, ARP
and ICMP traffic as requested in #15.
--
You received this bug notification because you are a member of Ubuntu
)
Importance: High
Assignee: Robie Basak (racb)
Status: In Progress
** Tags: ftbfs raring
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/1098162
Title:
mailman 1:2.1.15-1
** Also affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/1098162
Title:
mailman 1:2.1.15-1 FTBFS on amd64 in raring
To
Based on the distutils documentation, I think that calling
distutils.sysconfig.get_python_inc() is a more appropriate way of
determining the location of Python.h. It seems to work both after and
before the transition that broke Raring. Is this appropriate for
upstream as well?
** Patch added:
** Attachment added: mailman_2.1.15-1ubuntu1_amd64.build
https://bugs.launchpad.net/mailman/+bug/1098162/+attachment/3479075/+files/mailman_2.1.15-1ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in
@Mark Sapiro
This also affects the upstream Mailman project, since the pristine
upstream tarball also will also fail to build on Ubuntu after the next
release. What's the reason you removed the bug task?
** Also affects: mailman
Importance: Undecided
Status: New
--
You received this
No problem. Thanks for the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/1098162
Title:
mailman 1:2.1.15-1 FTBFS on amd64 in raring
To manage notifications about this
** Changed in: squid3 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1098641
Title:
visible_hostname defaults to hostname of first
Assuming Triaged because Russ says so. Thanks Russ!
** Changed in: kerberos-configs (Ubuntu)
Status: New = Triaged
** Changed in: kerberos-configs (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Confirmed, and I've found the fix. This is
https://bugs.php.net/bug.php?id=61413 fixed in http://git.php.net/?p
=php-src.git;a=commit;h=270a406ac94b5fc5cc9ef59fc61e3b4b95648a3e and
released upstream in 5.3.14.
This is due to i remaining uninitialised in the case of input data of
zero size.
I
If this doesn't qualify as security issue then I think we should SRU
this instead.
Build log attached from my test.
** Attachment added: php5_5.3.10-1ubuntu3.5_amd64.build
Thank you for your report.
Please can you specify exactly what you mean by ...it can no longer
access shares on main.? What method are you using to access shares?
What happens when it works, and what happens when it doesn't?
If you aren't already, then please also use smbclient to try and access
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I couldn't reproduce this on amavisd-new 1:2.7.1-2ubuntu3 on raring:
$ stat /etc/spamassassin/sa-update-hooks.d/amavisd-new
File: ‘/etc/spamassassin/sa-update-hooks.d/amavisd-new’
Size: 710
** Changed in: etckeeper (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1039627
Title:
etckeeper init with git gives error
To
Thanks. I've successfully reproduced this on 1:2.6.5-0ubuntu3.2
(precise-updates). It looks like the root cause was fixed in 1:2.7.0-1,
so that includes quantal and raring. But there is still an upgrade path
problem, so users installing precise who then upgrade will still be
affected.
I've
Sorry, wrong bug.
** Bug watch added: Debian Bug tracker #698446
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698446
** Also affects: php5 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698446
Importance: Unknown
Status: Unknown
** No longer affects: php5
Debian has 2.3~rc1-1 in experimental (2.2.1-8). So we could
theoretically merge from experimental, or wait for sid.
** Tags added: upgrade-software-version
** Changed in: openvpn (Ubuntu)
Status: New = Triaged
** Changed in: openvpn (Ubuntu)
Importance: Undecided = Wishlist
--
You
reporting (Closes: 571163)
-- Willi Mann Fri, 06 Apr 2012 21:11:23 +0200
** Affects: logwatch (Ubuntu)
Importance: Wishlist
Assignee: Robie Basak (racb)
Status: In Progress
** Tags: raring upgrade-software-version
--
You received this bug notification because you are a member
** Patch added: new_debian_to_new_ubuntu.debdiff
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1102414/+attachment/3492195/+files/new_debian_to_new_ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch
** Attachment added: old_ubuntu_to_new_ubuntu.debdiff.gz
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1102414/+attachment/3492196/+files/old_ubuntu_to_new_ubuntu.debdiff.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
)
Assignee: Robie Basak (racb) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
https://bugs.launchpad.net/bugs/1102414
Title:
Please merge logwatch 7.4.0+svn20120502rev103-1 (main) from Debian
unstable
To answer questions about getting an update into 12.04, we need (from
https://wiki.ubuntu.com/StableReleaseUpdates):
An impact statement which explains who this bug affects (use cases), why this
is a problem and why we need an update in 12.04 for it.
A test case with exact steps to reproduce the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please could you clarify exactly which Ubuntu package versions of
openldap are affected by this bug? Has this been reported and/or fixed
upstream, and if so could you please provide appropriate links? And
could
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I think it's reasonable to request that bind9 have an upstart job, in
order to permit better dependency management for services that depend on
bind9.
But I'm not sure about making the squid3 depend on bind9. I
The ubuntu-server list is a suitable venue to consult others on the
squid3 job depending on bind9, if you want to take it up there?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Maybe it could depend on some other well-known event that bind9
could emit...
But nothing would be there to emit that on a system that doesn't do its
own DNS. This is why the only reasonable answer I can give is to expect
sysadmins who need this kind of complex setup to add overrides to their
*** This bug is a duplicate of bug 625023 ***
https://bugs.launchpad.net/bugs/625023
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 625023, so it is being marked as such. Please look
Thank you for your detailed investigation into this. I appreciate the
time you've spent on this.
Marking as medium importance, since a workaround is available (which I
believe is to fix the cipher suite string to something valid, right?)
If the Ubuntu OpenLDAP developers and users can confirm
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I think this needs attention, so setting Importance to High. Usually SRU
policy generally frowns on this kind of update, but it may make sense
given that the kernel is being bumped. I appreciate you bringing it
The cron job you posted should not be able to cause a system reboot. As
this hasn't been confirmed by any other user, and there is surely a huge
number of other users running that same cron job, I think it is more
likely than not that this is either a hardware fault or some local
corruption or
Bug 1097783 is now fixed in raring, so just this issue remains. I've
updated upstream and am waiting to hear back from them. Unless they have
a better suggestion or an objection, hardcoding the old definition of
PseudoToken in a patch makes sense to me.
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
From your stack trace, it looks likely to me that the crash is in libtdb
rather than winbind itself, unless winbind is corrupting memory somehow.
Can you check all tdb files for corruption using tdbtool (I
** Changed in: bind9 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1101002
Title:
Frequently stops working for 15-30 seconds at a time on
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1078699
Title:
winbind won't start at boot
To manage notifications about
** Changed in: zookeeper (Ubuntu)
Status: New = Triaged
** Changed in: zookeeper (Ubuntu)
Importance: Undecided = Wishlist
** Tags added: upstream
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It seems likely that this bug might apply to the upstream project also,
so the next step is to test the latest upstream source and report the
bug upstream if applicable. Are you able to do this for us, please?
Fix attached. This includes a merge which drops the previous Ubuntu
delta since both previous patches have been adopted in Debian and these
are Debian's only changes. But this fix introduces a new one.
** Patch added: debian_ubuntu.debdiff
** Patch added: ubuntu_ubuntu.debdiff
https://bugs.launchpad.net/ubuntu/+source/genshi/+bug/1097776/+attachment/3504604/+files/ubuntu_ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
** Attachment added: genshi_0.6-3ubuntu1_amd64.build
https://bugs.launchpad.net/ubuntu/+source/genshi/+bug/1097776/+attachment/3504605/+files/genshi_0.6-3ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in
Please could you take a copy of /etc/resolv.conf, attach it, and report
the output of the following three commands? Please do all of this at the
time when you're having the problem.
Command 1: sudo netstat --inet -nlp|grep :53
Command 2: dig something.dev a @127.0.0.1
Command 3: dig something.dev
PS. you might have to install the dnsutils package to get the dig
command.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1101002
Title:
Frequently stops working for 15-30 seconds at
Thanks for the extra information. Based on these logs, bind9 is behaving
as expected, but your system is querying the dnsmasq and not bind, so
this is why it's not working for you. Since this isn't a bug in bind9,
I'm marking this bug as invalid in bind9.
The instructions you've followed need to
genshi successfully rebuilt in 0.6-3ubuntu1 using the fixed Python.
** Changed in: genshi (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
Confirmed fixed in raring on 1:9.9.2.dfsg.P1-2.
** Changed in: bind9 (Ubuntu Raring)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1090593
** Description changed:
+ [Impact]
+
+ named may use the wrong server for D.ROOT-SERVERS.NET on startup, as the
+ IP address is changing. This will cause a startup delay as it times out
+ and bootstraps from another root server instead. In the worst case, a
+ malicious actor on the old IP could
I wasn't happy to ask for sponsorship for SRUs directly from LaMont's
changes, since they included some autotools noise and updated the entire
db.root file instead of just changing the IP of D.ROOT-SERVERS.NET. For
example, they added new IPv6 entries in older releases that weren't
there before.
** Patch added: hardy.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508775/+files/hardy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: lucid.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508776/+files/lucid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: oneiric.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508777/+files/oneiric.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508778/+files/precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508779/+files/quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I've confirmed this and found that it affects Debian too. I've filed a
bug in Debian: http://bugs.debian.org/699450
** Bug watch added: Debian Bug tracker #699450
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It doesn't seem likely to me that Ubuntu could have introduced this bug
in the delta against Debian, so it would be best to verify and file a
bug in Debian.
Alternatively, patches welcome!
** Changed in: autofs
This was fixed upstream in 3.6.8 with commit
02c4886863e9a4066b89f2dcb8ff853bfbda7e86. Raring is on 2:3.6.9-1ubuntu1
so already contains the fix.
It looks like it'll be trivial to backport a fix to 12.04 if anybody
needs this. But for this to happen, we need a well-defined test case and
other
*** This bug is a duplicate of bug 625023 ***
https://bugs.launchpad.net/bugs/625023
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 625023, so it is being marked as such. Please look
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This was fixed in Debian 2.7.18-2, but Raring is on 2.7.18-1ubuntu1. It
seems likely that we just need to merge or cherry-pick.
** Changed in: puppet (Ubuntu)
Status: New = Triaged
** Changed in: puppet
Ah, we have a catch. I apologise for not noticing this before.
I've verified that /usr/lib/x86_64-linux-
gnu/sssd/modules/libsss_autofs.so is provided by sssd. So your patch
would require a new build dependency on sssd. However, sssd is in
universe, and autofs is in main, so we can't depend on it
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I appreciate the problem you are facing, and that the latest version
fixed the issue. Unfortunately, there isn't enough information here to
be able to figure out if there is a valid bug in 2.2.1-8ubuntu1, if this
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like this was fixed in
http://nagiosplug.git.sourceforge.net/git/gitweb.cgi?p=nagiosplug/nagiosplug;a=commit;h=f091d59e0f9abec9304d9d230fafc2dec001baba
and
** Changed in: krb5 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1119465
Title:
credential verification failed: KDC has no support for
I've uploaded a test fix to my experimental PPA
(https://launchpad.net/~racb/+archive/experimental). Since I can't
verify the fix myself, please can you test the package available from
here before I request an archive upload? Once this is checked, I will
request the fix be uploaded officially. The
I've uploaded a test fix to my experimental PPA
(https://launchpad.net/~racb/+archive/experimental). Since I can't
verify the fix myself, please can you test the package available from
here before I request an archive upload? Once this is checked, I will
request the fix be uploaded officially. The
Debdiff for precise-proposed attached.
** Patch added: nagios-plugins.debdiff
https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1119145/+attachment/3523767/+files/nagios-plugins.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Attachment added: nagios-plugins_1.4.15-5ubuntu3.1_amd64.build
https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1119145/+attachment/3523768/+files/nagios-plugins_1.4.15-5ubuntu3.1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server
$ rmadison -sprecise php5-cli php5-dev
php5-cli | 5.3.10-1ubuntu3 | precise | amd64, armel, armhf, i386,
powerpc
php5-dev | 5.3.10-1ubuntu3 | precise | amd64, armel, armhf, i386,
powerpc
$ rmadison -sprecise-updates php5-cli php5-dev
php5-cli | 5.3.10-1ubuntu3.5 |
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like this bug is the same as this Debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692013 and this has
been fixed in Raring.
As a workaround in previous releases, you can edit
** Changed in: openssh (Ubuntu)
Status: New = Triaged
** Changed in: openssh (Ubuntu Precise)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
From attached logs:
Setting up squid3 (3.1.20-1ubuntu1.1) ...
Creating Squid HTTP proxy 3.x spool directory structure
2013/02/11 17:02:24| cache_cf.cc(381) parseOneConfigFile: squid.conf:42
unrecognized: '0#'
dpkg: error processing squid3 (--configure):
subprocess installed post-installation
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Invalid.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
If you believe that this is really a bug, then you
** Changed in: postfix (Ubuntu)
Importance: Undecided = Medium
--
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/1122946
Title:
Log file is missing entries
To manage notifications
For apport-collect, try running:
https_proxy=http://1.2.3.4:5678/ apport-collect 1100787
If your proxy needs authentication, then:
https_proxy=http://username:password@1.2.3.4:5678/ apport-collect 1100787
(change 1.2.3.4:5678 to your proxy IP address and port number of course)
--
You
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Just to check that I understand. You have ld.so.conf and/or ld.so.conf.d
entries that point into autofs-mounted directories, and during a package
upgrade, since autofs unmounts, then ldconfig runs by other package
Thanks Thomas.
It looks like this exists in the Ubuntu delta only, introduced in the
fix for bug 246203. If we used the same lock file, I think we'd get a
deadlock again.
Is there a specific operational problem here? The current arrangement
does seem messy, but I'm reluctant to touch it if it
Thank you for reporting this issue and helping to make Ubuntu better.
Unfortunately, with few exceptions, we don't modify stable releases with
new features, including the LTS, since this position is exactly why
people use the LTS release.
Ubuntu LTS 12.04.1 is still shipped with php 5.3 for
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
You haven't reported the version of whois that you are using.
Please execute the following command, as it will automatically gather
debugging information, in a terminal:
apport-collect 1132526
When reporting
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I agree with Bryan; I don't think that making the change you suggest
will really help. Please could you explain in more detail what behaviour
you're expecting and what change you'd like made, and then change the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please could you attach a test case - an example minimal exim
configuration and sample email which exhibit the problem? Then we can
quickly use that to figure out which versions are affected, if the
problem exists
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like the problem stems from this line:
W: Failed to fetch
http://ppa.launchpad.net/nijaba/ubuntu/dists/quantal/main/binary-
amd64/Packages 404 Not Found
Please could you explain the presence of this
1 - 100 of 12229 matches
Mail list logo
