** Changed in: simple-scan (Ubuntu)
Status: Expired = Confirmed
** Changed in: simple-scan (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
workaround:
- install up to date fglrx from AMD
- boot with nosplash verbose debug no_console_suspend nomodeset
** Changed in: fglrx-installer (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Note I have no longer access to the hardware in question, so inquiries
for further testing are vain endeavour. Please see to that you ask
further questions for bug reports in a timely manner. Until then, I'm
setting the bug report back to Confirmed due to lack of other
evidence.
** Changed in:
I won't be able to comment on the Epsons, as the hardware/software combination
is no longer existent.
This is again a case where a slow response to bug reports made it the whole
effort nearly worthless.
I hope to test on the HP L7680 this weekend.
--
You received this bug notification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899356
Title:
readline() on closed filehandle FILES at /usr/sbin/popularity-contest
line 104.
To manage notifications about this bug go to:
Public bug reported:
The popularity-contest cron job spams my logcheck email messages with
dozens of the error lines below the /etc/cron.daily/ file name line:
/etc/cron.daily/popularity-contest:
readline() on closed filehandle FILES at /usr/sbin/popularity-contest line 104.
readline() on closed
I'm not upgrading just to see if someone got around to fixing the bug in
a new release while the old release is still supported -- the Desktops
in Ubuntu are going in the wrong direction.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm not upgrading just to see if someone got around to fixing the bug in
a new release while the old release is still supported -- the Desktops
in Ubuntu are going in the wrong direction.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The bug report is for maverick, which continues to be supported into
2012.
Even if the bug were fixed on natty it would persist on maverick, so
there's no point in wasting time testing natty or oneiric betas.
** Changed in: gconf (Ubuntu)
Status: Expired = Confirmed
--
You received this
Mike, this is a separate bug, please file separately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823347
Title:
Outbox mail stuck with SMTP errors not displayed
To manage notifications about
this = yours
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823347
Title:
Outbox mail stuck with SMTP errors not displayed
To manage notifications about this bug go to:
Public bug reported:
http://library.gnome.org/users/evolution/stable/b1a4ol61.html.en
documents:
Debug Logs
Evolution 2.30 User Guide
Advanced Configuration
Evolution allows you to view the error logs and set the display duration
for the error messages that appear in the statusbar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823343
Title:
evolution lacks documented debug feature
To manage notifications about this bug go to:
Public bug reported:
Assume I have an email with four recipients, one of them invalid.
Evolution is configured to use SMTP to send email. Authentication is not
required (LAN IP is sufficient on the SMTP server).
Now, during the SMTP dialog (as evidenced from Postfix logs), one of the
recipients
** Changed in: evolution (Ubuntu)
Status: New = Confirmed
** Summary changed:
- Mail stuck with SMTP errors not displayed
+ Outbox mail stuck with SMTP errors not displayed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Am 06.08.2011 17:05, schrieb Clint Byrum:
I think we can also close the task on Postfix, since this is a glibc
issue, unless there is something we can do to postfix to fix this.
Postfix is one of the few software packages whose default configuration
(in newer Postfix versions) triggers this
Public bug reported:
During installation of bison-doc on natty:
...
ignoring install-info called from maintainer script
The package bison-doc should be rebuilt with new debhelper to get trigger
support.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bison-doc 1:2.4.1-1
Am 06.08.2011 17:05, schrieb Clint Byrum:
I think we can also close the task on Postfix, since this is a glibc
issue, unless there is something we can do to postfix to fix this.
Postfix is one of the few software packages whose default configuration
(in newer Postfix versions) triggers this
On my computer, 2.6.38-10-generic (regular update kernel) + uswsusp
works now. Note I had purged uswsusp some time ago when testing; so
possibly people need to reinstall uswsusp. Note also that uswsusp may
be useless on computers with other mainboards.
--
You received this bug notification
The report is valid as it stands (i. e. -9 is b0rked and regresses on
suspend on my hardware), I merely described a workaround (-10 + uswsusp)
that's viable for me---but not necessarily for others.
So no, this is NOT an excuse to close the bug, in case you considered
that.
--
You received this
** Changed in: eglibc (Ubuntu Natty)
Status: New = Confirmed
** Changed in: postfix (Ubuntu Natty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
** Changed in: eglibc (Ubuntu Natty)
Status: New = Confirmed
** Changed in: postfix (Ubuntu Natty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/777855
Title:
confirmed #34, can someone mark this as affecting adobereader-deu and
adobereader-enu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769866
Title:
tab completion no longer escapes filenames and
Public bug reported:
My alsamixer interface offers a Headphone volume control, and a
Independent Headphone binary switch. If the latter switch is flipped,
the Headphone control slider does not change state (enabled vs. greyed
out) until I quit and restart alsamixer.
Expected behaviour: flipping
** Description changed:
My alsamixer interface offers a Headphone volume control, and a
Independent Headphone binary switch. If the latter switch is flipped,
the Headphone control slider does not change state (enabled vs. greyed
out) until I quit and restart alsamixer.
+
+ Expected
Marked Confirmed
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
--
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/807153
Title:
named does not shut down after service
Marked Confirmed
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807153
Title:
named does not shut down after service bind9 stop
To
Will try to reproduce, thanks for replying at all.
--
Matthias Andree
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/674612
Title:
gconfd trashes configuration when disk is full
To manage
--
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/807153
Title:
named does not shut down after service bind9 stop
To manage notifications about this bug go to:
Public bug reported:
I am running the standard natty BIND9 package in an IPv6- and DNSSEC-
enabled configuration as a resolver. The zones are unaltered.
After service bind9 stop (or equivalently service bind9 restart),
named receives and logs the control command, but remains running. I have
to
Public bug reported:
I am running the standard natty BIND9 package in an IPv6- and DNSSEC-
enabled configuration as a resolver. The zones are unaltered.
After service bind9 stop (or equivalently service bind9 restart),
named receives and logs the control command, but remains running. I have
to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807153
Title:
named does not shut down after service bind9 stop
To manage notifications about this bug go to:
Public bug reported:
/etc/network/if-up.d/gogoc contains inconsistencies that subvert the
advertised purpose, and, more importantly, breaks ifup:
$ sudo ifup sixxs
Tunnel Information for T98765:
POP Id : deabc01
IPv6 Local : 2001:abcd:ef01:2345::2/64
IPv6 Remote : 2001:abcd:ef01:2345::1/64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802759
Title:
/etc/network/if-up.d/gogoc breaks ifup post-up scripts
To manage notifications about this bug go to:
Am 18.06.2011 03:39, schrieb Christian Kastner:
As I mentioned earlier, I have a fix in mind for the next release which
should resolve the issue in a manner not conflicting with the other goals.
next release doesn't help those running LTS...
--
Matthias Andree
--
You received this bug
Am 18.06.2011 03:19, schrieb Christian Kastner:
On 06/07/2011 06:13 PM, Matthias Andree wrote:
Note that while the trigger is cron starting before the respective user
database (NIS, LDAP, whatever), cron should really re-check each time to
be resilient to temporary network hicc-ups
-
--
Matthias Andree
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
message and skipping jobs for all LDAP/NIS
/bugzilla/show_bug.cgi?id=430
--
Matthias Andree
** Bug watch added: Sourceware.org Bugzilla #430
http://sourceware.org/bugzilla/show_bug.cgi?id=430
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs
but can happen in
triaging already.
- there is a certain fixed in future-release habit that leaves LTS
users standing in the rain with critical bugs.
--
Matthias Andree
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https
** Attachment added: log from LC_ALL=C banshee --redirect-log, with CD
inserted
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/786524/+attachment/2159032/+files/log
** Changed in: banshee (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are
Note the log does not seem to contain useful information. There is no
CDDB data for this disc.
However, Aqualung, icedax -toc dev=/dev/sr0 (or /dev/dvd), k3b, are able
to read the CD-Text info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: cron
cron ignores /etc/default/cron (which is part of the cron package). The
cause is that the new /etc/init/cron.conf doesn't read it.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: cron 3.0pl1-106ubuntu5
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794082
Title:
cron ignores /etc/default/cron
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Please backport the fix to all affected and supported releases.
** Summary changed:
- cron daemon starts before LDAP client, causing ORPHAN message for all
LDAP-defined users
+ cron daemon starts before LDAP/NIS client, causing ORPHAN message for all
LDAP/NIS-defined users
--
You received
Same problem applies to NIS configurations. cron starts early and checks
users' existence before dhclient has even acquired the IP. Same symptoms
on Lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
*** This bug is a duplicate of bug 27520 ***
https://bugs.launchpad.net/bugs/27520
** Description changed:
Binary package hint: cron
Ubuntu 10.04.2 LTS
cron 3.0pl1-106ubuntu5
Problem: After a reboot, cron does not start cronjobs that have been created
by NIS users. Instead
*** This bug is a duplicate of bug 27520 ***
https://bugs.launchpad.net/bugs/27520
** This bug has been marked a duplicate of bug 27520
cron daemon starts before LDAP/NIS client, causing ORPHAN message for all
LDAP/NIS-defined users
--
You received this bug notification because you are
*** This bug is a duplicate of bug 27520 ***
https://bugs.launchpad.net/bugs/27520
** This bug has been marked a duplicate of bug 27520
cron daemon starts before LDAP/NIS client, causing ORPHAN message for all
LDAP/NIS-defined users
--
You received this bug notification because you are
Note that while the trigger is cron starting before the respective user
database (NIS, LDAP, whatever), cron should really re-check each time to
be resilient to temporary network hicc-ups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Also note that ORPHAN may not show up until you edit /etc/init/cron.conf
to start cron -L2... the Upstart conversion is incomplete and causes the
cron service to ignore /etc/default/cron.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- cron daemon starts before LDAP/NIS client, causing ORPHAN message for all
LDAP/NIS-defined users
+ cron daemon caches user-non-existent lookup results, causing ORPHAN message
and skipping jobs for all LDAP/NIS-defined users
--
You received this bug notification because
Public bug reported:
Binary package hint: cron
Please backport the fix for LP: #27520 to all supported releases. It
breaks, among others, on lucid.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: cron 3.0pl1-106ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
** Changed in: cron (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794141
Title:
cron needs to re-lookup users when trying to run a job
--
ubuntu-bugs
Jamie, you don't know what is in inbound or outbound fax queues of the
device at the time. It needs to be power-cycled after the fact.
Please do NOT unmark the bug as non-security relevant until it is proven
that the bug does not cause the loss of, say, another user's fax.
--
You received this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/792387
Title:
Install of fglrx hides plymouth splash cryptroot prompt
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
New installation of the fglrx driver causes the plymouth splash screen
and the included cryptroot password prompt to not appear at the next
boots. Workaround: remove quiet splash vt.handoff=7 from GRUB command
line.
To reproduce, install Ubuntu 11.04 on a system with AMD
Public bug reported:
Binary package hint: banshee
banshee does not display titles from CD TEXT information, although
icedax is able to extract it with the same DVD-writer, from the same
disc.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: banshee 2.0.0-2ubuntu1
ProcVersionSignature:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/786524
Title:
banshee does not display CD TEXT
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: compiz
I have several issues with compiz under Ubuntu Classic, what I attribute
to be Unity bugs.
Often, the screen flickers for a short time, for instance, when the
software updater window appears. Then, grabbing a window to move it
actually often
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785053
Title:
unity-window-decorator moves wrong windows, steals focus, and creates
invisible bogus windows
--
ubuntu-bugs mailing list
Guys, can we please stop distracting with lame excuses for not going for
bugfix releases, or backports of another feature release?
This particular regression was already fixed by the upstream maintainers
in a particular bugfix-only release series of Postfix (2.7.1 is 2.7.0 +
fixes), so any any
make that 2.7.4. Admittedly even 2.7.1 was past the lucid release, but
the upstream has fixed this regression one full year and four days ago.
Can we now start the fixing?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in
** Summary changed:
- mupdf .desktop file broken
+ mupdf .desktop file broken: invalid MIME type (typo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784742
Title:
mupdf .desktop file broken:
Public bug reported:
Binary package hint: mupdf
$ sudo update-desktop-database /usr/share/applications
Error in file /usr/share/applications/mupdf.desktop: pplication/x-pdf is an
invalid MIME type (pplication is an unregistered media type)
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package:
Guys, can we please stop distracting with lame excuses for not going for
bugfix releases, or backports of another feature release?
This particular regression was already fixed by the upstream maintainers
in a particular bugfix-only release series of Postfix (2.7.1 is 2.7.0 +
fixes), so any any
make that 2.7.4. Admittedly even 2.7.1 was past the lucid release, but
the upstream has fixed this regression one full year and four days ago.
Can we now start the fixing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/783950
Title:
simple-scan crashes EPSON Office ADF scanners, fails with hp ADF
scanners
--
ubuntu-bugs mailing
patches, a backport is less tested, thus
more dangerous, than just reviewing the point-release patch.
Anyways, I don't care how Ubuntu will choose to fix this regression, but
I do care that it happens soon.
--
Matthias Andree
--
You received this bug notification because you are a member
patches, a backport is less tested, thus
more dangerous, than just reviewing the point-release patch.
Anyways, I don't care how Ubuntu will choose to fix this regression, but
I do care that it happens soon.
--
Matthias Andree
--
You received this bug notification because you are a member
Apparent upstream fix:
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f87dfb1f11c01f2ccdc40d81e134cd06b32e28e8;hp=47c3cd7a74e8c089d60d603afce6d9cf661178d6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
My computer hangs if I try to suspend via the GNOME menu if I use this
kernel:
linux-image-2.6.38-9-generic:
Installiert: 2.6.38-9.43
Kandidat:2.6.38-9.43
Versionstabelle:
*** 2.6.38-9.43 0
500 http://de.archive.ubuntu.com/ubuntu/ natty-proposed/main amd64
** Attachment added: output of lspci -vnvn on the WORKING -8 kernel (from the
base repo, not from -proposed)
https://bugs.launchpad.net/bugs/779033/+attachment/2118258/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
My computer hangs if I try to suspend via the GNOME menu if I use this
(currently running) kernel:
linux-image-2.6.38-9-generic:
Installiert: 2.6.38-9.43
Kandidat: 2.6.38-9.43
Versionstabelle:
*** 2.6.38-9.43 0
500 http://de.archive.ubuntu.com/ubuntu/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779036
Title:
natty-proposed kernel regression breaks suspend (to RAM, ACPI S3)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ubuntu-bug linux attachments for the working kernel can be found, for
reference, in (invalid) Bug #779033. This report, however, is a re-
report with the broken kernel running so that the various .txt files can
be diffed if necessary.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 779036 ***
https://bugs.launchpad.net/bugs/779036
To avoid confusion, I am re-reporting the bug with the broken kernel
running, to resolve confusion.
** Changed in: linux (Ubuntu)
Status: New = Invalid
** This bug has been marked a duplicate of bug
Fix appears to be in
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f87dfb1f11c01f2ccdc40d81e134cd06b32e28e8
and slated to appear in glibc 2.14. Not sure about eglibc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: postfix
I have a particular Postfix relay configuration where I need to forward
SMTP to an SSH tunnel, and configure a relayhost_maps (sender_dependent
actually) as [localhost]:12345.
This worked in maverick, but fails in natty. The new Postfix 2.8
--
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/777868
Title:
Postfix smtp can no longer resolve localhost - regression from
maverick.
--
Ubuntu-server-bugs mailing list
No improvement in 2.8.2-1ubuntu2 from -updates, and with a fundamentally
different cause, so removing duplicate mark.
** This bug is no longer a duplicate of bug 764096
DNS hostname lookups fail in chroot after natty upgrade
--
You received this bug notification because you are a member of
Additional remark: Bug #764096 is about an incomplete chroot setup caused by
the start script.
To differentially diagnose this, I had ruled a broken chroot setup out in my
testing by forcing smtp(8) outside the chroot per master.cf.
This bug is fundamentally a resolver bug, exhibited through a
Public bug reported:
The eglibc resolver is broken and doesn't attempt DNS queries for
hostnames without dots if the RES_DEFNAMES option gets stripped from the
_res.options (resolver options).
This breaks security-sensitive applications (I'd first observed it with
Postfix) trying to resolve, for
** Bug watch added: Novell/SUSE Bugzilla #691967
https://bugzilla.novell.com/show_bug.cgi?id=691967
** Also affects: glibc (openSUSE) via
https://bugzilla.novell.com/show_bug.cgi?id=691967
Importance: Unknown
Status: Unknown
** Also affects: glibc
Importance: Undecided
Please forward this upstream to Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/777855
Title:
resolver failures without even sending queries, break Postfix
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: postfix
I have a particular Postfix relay configuration where I need to forward
SMTP to an SSH tunnel, and configure a relayhost_maps (sender_dependent
actually) as [localhost]:12345.
This worked in maverick, but fails in natty. The new Postfix 2.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/777868
Title:
Postfix smtp can no longer resolve localhost - regression from
maverick.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
No improvement in 2.8.2-1ubuntu2 from -updates, and with a fundamentally
different cause, so removing duplicate mark.
** This bug is no longer a duplicate of bug 764096
DNS hostname lookups fail in chroot after natty upgrade
--
You received this bug notification because you are a member of
Additional remark: Bug #764096 is about an incomplete chroot setup caused by
the start script.
To differentially diagnose this, I had ruled a broken chroot setup out in my
testing by forcing smtp(8) outside the chroot per master.cf.
This bug is fundamentally a resolver bug, exhibited through a
Public bug reported:
Binary package hint: postfix
/usr/share/doc/postfix/RELEASE_NOTES.gz references a RELEASE_NOTES-2.6
documentation file that isn't installed, neither as part of postfix, nor
postfix-doc. Please add this file.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: postfix
--
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/777033
Title:
installation lacks RELEASE_NOTES-2.6 documentation file
--
Ubuntu-server-bugs mailing list
Public bug reported:
Binary package hint: postfix
I've been bitten by a Postfix SMTP/LMTP implementation defect that has
been fixed in one of the upstream patch-level releases 2.7.X.
Basically Postfix sends XFORWARD PORT=unknown ... to amavsid via LMTP.
Amavisd later returns the same attribute
** Summary changed:
- [fixed upstream] Postfix smtp does not skip unknown XFORWARD attributes,
causing SMTP syntax errors
+ [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD
attributes, causing SMTP syntax errors
** Tags added: regression
** Tags added:
Public bug reported:
Binary package hint: apport
The Binary Package Hint: created by this version of ubuntu-bug (or
apport) is wrong and identical to the source package. To verify this,
install a binary package where the source package name is different (for
instance, courier-authdaemon), and
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/777068
Title:
ubuntu-bug misdetects binary package hints and uses source instead
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 102947 ***
https://bugs.launchpad.net/bugs/102947
Public bug reported:
Binary package hint: courier-authlib
The /etc/init.d/courier-authdaemon creates $RUNDIR with improper
permissions, namely, 0750, rather than world-readable. The problem is
that if
*** This bug is a duplicate of bug 102947 ***
https://bugs.launchpad.net/bugs/102947
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/777060
Title:
/etc/init.d/courier-authdaemon creates $RUNDIR
*** This bug is a duplicate of bug 102947 ***
https://bugs.launchpad.net/bugs/102947
Note ubuntu-bug misfiled the binary package (courier-authdaemon, not
-authlib).
** This bug has been marked a duplicate of bug 102947
ERR: authdaemon: s_connect() failed: No such file or directory
* You
Re https://bugs.launchpad.net/ubuntu/+source/courier-
authlib/+bug/102947/comments/17 the underlying problem is that
/var/run/courier/authdaemon gets created with wrong permissions so that
unprivileged agents cannot access the .../socket in that directory.
Linking a duplicate bug here.
--
You
Note that this has been restated several times before, see comment #15.
See https://bugs.launchpad.net/ubuntu/+source/courier-
authlib/+bug/777060 for additional details. It might be advisable to
make maildrop depend on courier-authdaemon.
Josip, note that it is NOT fetchmail BUT getmail that
Please don't patch authlib - it's too silent already, and maildrop's
can't connect is hard enough to find - namely non-existent if run from
Postfix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
201 - 300 of 529 matches
Mail list logo
