[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

[Mark Sapiro]

This bug is back in Ubuntu 20.04 postfix/focal-updates,now
3.4.13-0ubuntu1.2

I'm not certain of my analysis, but I see two services

postfix.service -
[Unit]
Description=Postfix Mail Transport Agent
Conflicts=sendmail.service exim4.service
ConditionPathExists=/etc/postfix/main.cf

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
ExecReload=/bin/true

[Install]
WantedBy=multi-user.target
-
and
postfix@.service 
[Unit]
Description=Postfix Mail Transport Agent (instance %i)
Documentation=man:postfix(1)
PartOf=postfix.service
Before=postfix.service
ReloadPropagatedFrom=postfix.service
After=network-online.target nss-lookup.target
Wants=network-online.target

[Service]
Type=forking
GuessMainPID=no
ExecStartPre=/usr/lib/postfix/configure-instance.sh %i
ExecStart=/usr/sbin/postmulti -i %i -p start
ExecStop=/usr/sbin/postmulti -i %i -p stop
ExecReload=/usr/sbin/postmulti -i %i -p reload

[Install]
WantedBy=multi-user.target
-
It appears the intent of postfix@.service is to delay starting postfix.service 
until after networking is up, but it seems that systemd doesn't accept 
postfix@.service as a valid service

$ sudo systemctl status postfix@.service 
Failed to get properties: Unit name postfix@.service is neither a valid 
invocation ID nor unit name.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519331

Title:
  Postfix cannot resolve DNS if network was unavailable when it was
  started, such as on a laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882660] Re: Mailman and Python 3.8 incompatibility - unable to subscribe a list

[Mark Sapiro]

*** This bug is a duplicate of bug 1877701 ***
https://bugs.launchpad.net/bugs/1877701

** No longer affects: mailman

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882660

Title:
  Mailman and Python 3.8 incompatibility - unable to subscribe a list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1882660/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877701] [NEW] Mailman3 3.2.2-1 is incompatible with Python3 3.8.2-0

[Mark Sapiro]

Public bug reported:

Ubuntu focal (20.04LTS) packages Mailman3 3.2.2-1 with Python3 3.8.2-0.

These are incompatible. Mailman3 < 3.3.0 does not support Python3 >=
3.8.0.

This leads to issues such as discissed in the thread at
https://lists.mailman3.org/archives/list/mailman-
us...@mailman3.org/thread/K65RN3YNZ42T7Z6EOWJIGG6E4AK2YXLK/

** Affects: mailman3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877701

Title:
  Mailman3 3.2.2-1 is incompatible with Python3 3.8.2-0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1877701/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838866] Re: Mailman 2.1: hardcoded site-packages dir prefix doesn't work on some 64 bit filesystem layouts

[Mark Sapiro]

** Changed in: mailman
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838866

Title:
  Mailman 2.1: hardcoded site-packages dir prefix doesn't work on some
  64 bit filesystem layouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1838866/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774226] Re: Latest Ubuntu Squirrelmail package throws deprecation warnings.

[Mark Sapiro]

Sorry for the noise.

It turns out I had local mods which were avoiding some of the
deprecation warnings, and the Ubuntu package update reversed those.

** Changed in: squirrelmail (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774226

Title:
  Latest Ubuntu Squirrelmail package throws deprecation warnings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/1774226/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1803838] Re: Mailman Upgrade to 2.1.29 - Ubuntu 16.04

[Mark Sapiro]

If you want to upgrade the Ubuntu 16.04 package from source, see
https://wiki.list.org/x/17891606.

** Also affects: ubuntu
   Importance: Undecided
   Status: New

** No longer affects: mailman

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803838

Title:
  Mailman Upgrade to 2.1.29 - Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1803838/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677335] Re: Outgoing mail is always windows-1252 encoded by default

[Mark Sapiro]

This should probably be status: Won't Fix.

Mozilla answered the above bug report with a reference to
<-https://bugzilla.mozilla.org/show_bug.cgi?id=1469335#c6> which cites
 as an authoritative reference saying
windows-1252 is the preferred name for iso-8859-1. latin1, etc., and
future releases will remove iso-8859-1 as a choice for 'western'
encoding.

** Bug watch added: Mozilla Bugzilla #1469335
   https://bugzilla.mozilla.org/show_bug.cgi?id=1469335

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677335

Title:
  Outgoing mail is always windows-1252 encoded by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1677335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677335] Re: Outgoing mail is always windows-1252 encoded by default

[Mark Sapiro]

I have just tested with Thunderbird 52.9.1 (64 bit) on Mac OS 10.13.6
and the same issue exists there, so this is not unique to Ubuntu. I have
just reported this to Mozilla at
.

** Bug watch added: Mozilla Bugzilla #1477357
   https://bugzilla.mozilla.org/show_bug.cgi?id=1477357

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677335

Title:
  Outgoing mail is always windows-1252 encoded by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1677335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677335] Re: Outgoing mail is always windows-1252 encoded by default

[Mark Sapiro]

This is still an issue with Ubuntu 16.04 and Thunderbird 52.9.1(64 bit)

The location of the setting is changed. It is now Edit -> Preferences ->
Display -> Formatting -> Fonts & Colors -> Advanced -> Text Encoding,
but when the

Text Encoding
  Set the default text encoding for sending and receiving mail
Outgoing Mail:

setting is Western (ISO-8859-1) as in the attached screenshot, outgoing
plain text messages are still encoded as Windows-1252

** Attachment added: "Fonts & Encodings screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1677335/+attachment/5165447/+files/Screenshot%20from%202018-07-19%2020-35-44.png

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677335

Title:
  Outgoing mail is always windows-1252 encoded by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1677335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774226] [NEW] Latest Ubuntu Squirrelmail package throws deprecation warnings.

[Mark Sapiro]

Public bug reported:

It is well known the squirrelmail with PHP 5 triggers various
deprecation messages. See
https://sourceforge.net/p/squirrelmail/bugs/2784/ for example.

For some time, the  Ubuntu Squirrelmail package did not issue these
messages, but the current squirrelmail:all
2:1.4.23~svn20120406-2+deb8u2ubuntu0.16.04.3 is once again issuing
messages like

 PHP Deprecateds: 3
 Methods with the same name as their class will not be constructors in a future 
version of PHP; ContentType has a deprecated constructor in 
/usr/share/squirrelmail/class/mime/ContentType.class.php on line 25 1 Time(s)
 Methods with the same name as their class will not be constructors in a future 
version of PHP; Disposition has a deprecated constructor in 
/usr/share/squirrelmail/class/mime/Disposition.class.php on line 24 1 Time(s)
 Methods with the same name as their class will not be constructors in a future 
version of PHP; Language has a deprecated constructor in 
/usr/share/squirrelmail/class/mime/Language.class.php on line 24 1 Time(s)

** Affects: squirrelmail (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774226

Title:
  Latest Ubuntu Squirrelmail package throws deprecation warnings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/1774226/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573801] Re: glom: error while loading shared libraries: libboost_python-py34.so.1.58.0: cannot open shared object file: No such file or directory

[Mark Sapiro]

My workaround appeared to work, but there were multiple issues in actual
use, so I don't recommend it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573801

Title:
  glom: error while loading shared libraries: libboost_python-
  py34.so.1.58.0: cannot open shared object file: No such file or
  directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glom/+bug/1573801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573801] Re: glom: error while loading shared libraries: libboost_python-py34.so.1.58.0: cannot open shared object file: No such file or directory

[Mark Sapiro]

I just ran into the same thing after installing glom on Ubuntu 16.04. I
am trying this

cd /usr/lib/x86_64-linux-gnu/
sudo ln -s libboost_python-py35.so.1.58.0 libboost_python-py34.so.1.58.0

as a workaround. I don't know if it will be effective, but it allows
glom to start and create a database.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573801

Title:
  glom: error while loading shared libraries: libboost_python-
  py34.so.1.58.0: cannot open shared object file: No such file or
  directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glom/+bug/1573801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

[Mark Sapiro]

The fix is http://bazaar.launchpad.net/~mailman-
coders/mailman/2.1/revision/1714

I don't think it's a priority. I never saw an issue due to this before
this report. Also, in the case of Debian/Ubuntu, if the site takes the
postfix_to_mailman.py option (something which I don't recommend - see
https://wiki.list.org/x/15564817 - but which the Debian/Ubuntu package
seems to encourage), this is not relevant at all.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696066

Title:
  Postfix module - Mailman wrapper - Couldn't write data/aliases.db and
  data/virtual-mailman.db files

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1696066/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

[Mark Sapiro]

** Changed in: mailman
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696066

Title:
  Postfix module - Mailman wrapper - Couldn't write data/aliases.db and
  data/virtual-mailman.db files

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1696066/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1695610] Re: Test missing in lists_lists leading to wrong listing when using -V option

[Mark Sapiro]

** Changed in: mailman
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695610

Title:
  Test missing in lists_lists leading to wrong listing when using -V
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1695610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1251495] Re: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception.

[Mark Sapiro]

To reproduce the error you need to enable topics for a list, create a
topic and send a post that matches that topic.

You can do the enable/create by putting these two lines

topics_enabled = 1
topics = [('Match_all', '.', 'Topic matches anything for testing', False)]

in a file and running Mailman's bin/config_list like

bin/config_list -i path/to/file/with/lines list_name

Then, a post to that list should be delivered normally and contain a
header 'X-Topics: Match_all', but the bug will cause the post to be
shunted.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251495

Title:
  Lists with topics enabled can throw unexpected keyword argument
  'Delete' exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

[Mark Sapiro]

There is another issue not mentioned in the original report and that is
that aliases.db must be owned by the Mailman user so Postfix runs the
pipe as the Mailman user and group.

bin/check_perms would check/fix this and also ensure the mode is at
least 0660, but I've gone a step further and now ensure these things at
the time the postalias and postmap commands are run and also ensure the
mode is at least 0664 so Postfix doesn't need to be in Mailman's group.

** Changed in: mailman
   Importance: Undecided => Medium

** Changed in: mailman
   Status: New => Fix Committed

** Changed in: mailman
Milestone: None => 2.1.25

** Changed in: mailman
 Assignee: (unassigned) => Mark Sapiro (msapiro)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696066

Title:
  Postfix module - Mailman wrapper - Couldn't write data/aliases.db and
  data/virtual-mailman.db files

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1696066/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1695610] Re: Test missing in lists_lists leading to wrong listing when using -V option

[Mark Sapiro]

** Changed in: mailman
   Importance: Undecided => Low

** Changed in: mailman
   Status: New => Fix Committed

** Changed in: mailman
Milestone: None => 2.1.25

** Changed in: mailman
 Assignee: (unassigned) => Mark Sapiro (msapiro)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695610

Title:
  Test missing in lists_lists leading to wrong listing when using -V
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1695610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

[Mark Sapiro]

** Changed in: mailman
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694384

Title:
  Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

[Mark Sapiro]

** Changed in: mailman
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694384

Title:
  Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

[Mark Sapiro]

Thanks for your report. I will fix the mailman-owner@VIRTUAL_DOMAIN
issue. I will also address exposing the (mildly obfuscated) list owner
addresses in the web page footer ( see the thread at
<https://mail.python.org/pipermail/mailman-
developers/2017-May/026047.html>).

Regarding exposing the site list address on the admin and listinfo
overview pages, we can't expose a list owner address here because we
don't have a list context so the alternative is to expose nothing. I do
not plan to change this at this point.

** Changed in: mailman
   Importance: Undecided => Medium

** Changed in: mailman
   Status: New => In Progress

** Changed in: mailman
Milestone: None => 2.1.24

** Changed in: mailman
 Assignee: (unassigned) => Mark Sapiro (msapiro)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694384

Title:
  Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1685946] Re: Mismatch between declared and actual encoding in mail notifications and web pages

[Mark Sapiro]

This is not a GNU mailman bug. It is a Debian/Ubuntu issue. See
 including comment #6
and the list posts linked from there.

Note that in current Debian/Ubuntu packages there is Debian
91_utf8.patch (available, e.g. in
)

Among other things, this patch redefines the add_language() function to
ignore the third argument and force the encoding to UTF-8.

Your issue is one or both of two things:

You may have custom 'de' templates that are latin-1 encoded (Debian's
patch recodes all the standard templates to utf-8).

You have strings in list attributes that are latin-1 encoded (Definitely
in 'description' attributes. This is the part that Debian completely
overlooked. The recode_list script mentioned at
 and the
mailman-users list thread also mentioned in that comment may help.

There also seems to be another issue in your case. The boilerplate at
the top of  comes
from translated strings in messages/de/LC_MESSAGES/mailman.mo. Debian's
patch recodes all these to utf-8 in its distribution, but for some
reason your compiled German message catalog contains latin-1 strings.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685946

Title:
  Mismatch between declared and actual encoding in mail notifications
  and web pages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1685946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1685946] Re: Mismatch between declared and actual encoding in mail notifications and web pages

[Mark Sapiro]

** No longer affects: mailman

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685946

Title:
  Mismatch between declared and actual encoding in mail notifications
  and web pages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1685946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677335] [NEW] Outgoing mail is always windows-1252 encoded by default

[Mark Sapiro]

Public bug reported:

Thunderbird 45.8.0
Ubuntu 16.04

When composing or replying in Thunderbird, the default encoding is
Western (Windows-1252) regardless of the setting of Edit -> Preferences
-> Display -> Advanced -> Text Encoding.

It doesn't matter that the setting for Outgoing Mail: is "Western
(ISO-8859-1)" or "Western (Windows-1252)", either way the outgoing
message is windows-1252 encoded.

If the setting for Outgoing Mail: is "Unicode (UTF-8)", then the
outgoing message is utf-8 encoded, so that works. It is only "Western
(ISO-8859-1)" that doesn't work.

** Affects: thunderbird (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677335

Title:
  Outgoing mail is always windows-1252 encoded by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1677335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

@penalvch Since you have asked me to not make further changes I won't,
but Invalid as defined in https://wiki.ubuntu.com/Bugs/Bug%20statuses
certainly does not apply to this bug either, and I don't really see why
Fix Released does not apply. Granted, I wasn't able to pinpoint a
specific package version between 4.4.0-21 and 4.4.0-38 in which it was
fixed, but it is fixed in 4.4.0-38.

Also it is still applicable to 3.19.0-18 and subsequent releases in that
series so it probably should be nominated for that series per "Warning
/!\ If the bug stills affects an older Ubuntu release, please nominate
it for that series. Otherwise people won't know it isn't fixed there!".

In any case, the politics of this doesn't interest me so I will leave it
to others to do the right thing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

** Changed in: linux (Ubuntu)
   Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

I have been running for a few days with MTU=automatic (1500) on Ubuntu
16.04 with kernel 4.4.0-38-generic with no overrun errors. I didn't try
with any kernels between 4.4.0-21 and 4.4.0-38, so I don't know at which
update it would have begun to work, but it appears to be fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1602608] Re: mailman crash for subscription in webinterface

[Mark Sapiro]

I see how this can occur if you have your own page that POSTs to the
subscribe CGI with no post data or post data consisting of all blank
values, but I don't see how it occurs with a post from the listinfo
subscribe form.

Can you explain exactly what the scenario is that triggers this error?

** Package changed: mailman (Ubuntu) => mailman

** Changed in: mailman
   Status: New => Incomplete

** Changed in: mailman
 Assignee: (unassigned) => Mark Sapiro (msapiro)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602608

Title:
  mailman crash for subscription in webinterface

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1602608/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

I spoke too soon. I eventually ran into overrun errors with MTU=2100.
I'm now trying 4100. (I previously ran for quite some time w/o errors
with MTU=7168)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

Regarding the MTU workaround, I've experimented and with Ubuntu 16.04
and kernel 4.4.0-21, it is not necessary to set the MTU nearly as high
as 8192. It still fails for me with MTU set to auto or 1500 or 2000, but
with MTU = 2100, it seems to work OK with no overruns. I haven't tried
to narrow it further, but I suspect 2048 is a magic number.

MTU = 2100 seems to avoid the SSH issues I was sometimes seeing with a
much larger MTU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492146] Re: igb Detected Tx Unit Hang

[Mark Sapiro]

My server has now been running on this kernel (3.16.0-56-generic) for
over 48 hours with no recurrence of the igb Tx Unit Hang.

I think we can say it's working for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146

Title:
  igb Detected Tx Unit Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492146] Re: igb Detected Tx Unit Hang

[Mark Sapiro]

My server has been running on this kernel (3.16.0-56-generic) for almost
24 hours now with no recurrence of the igb Tx Unit Hang.

I'm still monitoring, but it looks like this kernel is stable on my
server.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146

Title:
  igb Detected Tx Unit Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492146] Re: igb Detected Tx Unit Hang

[Mark Sapiro]

I have installed linux-
image-3.16.0-56-generic_3.16.0-56.75~14.04.1_amd64.deb and linux-image-
extra-3.16.0-56-generic_3.16.0-56.75~14.04.1_amd64.deb from
http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/

It's been running without issues for significantly longer than the
versions with problems ever did. I will continue to monitor and will
report again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146

Title:
  igb Detected Tx Unit Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492146] Re: igb Detected Tx Unit Hang

[Mark Sapiro]

Sorry to report that I have the same issue after installing linux-
image-3.16.0-55-generic_3.16.0-55.74~14.04.1_amd64.deb and linux-image-
extra-3.16.0-55-generic_3.16.0-55.74~14.04.1_amd64.deb from
http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146

Title:
  igb Detected Tx Unit Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492146] Re: igb Detected Tx Unit Hang

[Mark Sapiro]

I spoke too soon. It took about 20 minutes for the issue to develop, but
it has reappeared just as before with the new kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146

Title:
  igb Detected Tx Unit Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492146] Re: igb Detected Tx Unit Hang

[Mark Sapiro]

I have installed

linux-image-3.16.0-52-generic_3.16.0-52.71~14.04.1_amd64.deb and
linux-image-extra-3.16.0-52-generic_3.16.0-52.71~14.04.1_amd64.deb

from http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/
and rebooted and I do not see the issue reported in this bug. It appears
at least for me that the above kernel does not have the regression.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146

Title:
  igb Detected Tx Unit Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492146] Re: igb Detected Tx Unit Hang

[Mark Sapiro]

I have the same issue with similar kern.log entries after upgrading to
kernel 3.16.0-48. Removing that and falling back to 3.16.0-46 fixed it
for me.

** Attachment added: "Excerps from kern.log, lshw, ifconfig"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+attachment/4457713/+files/log_lshw_ifconfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146

Title:
  igb Detected Tx Unit Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

On 06/20/2015 10:24 AM, Bachi wrote:
 
 There is a workaround: In Network manager, set the ethernet connection's
 MTU value from automatic to 8192. This worked fine for me (from
 https://bugzilla.kernel.org/show_bug.cgi?id=70761).


Thank you. This workaround is working for me.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

On 05/31/2015 07:16 PM, Christopher M. Penalver wrote:
 Mark Sapiro, the Ubuntu kernel 3.19.0-20.20 in Proposed is based on
 3.19.8. Hence, feel free to test that and advise to the results.


Where do I find it?

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

I have tried various upstream kernel packages. I tried v4.1-rc5, v4.0.4,
and v4.0, none of which installed correctly because of conflicts with
nvidia-304.125. I did not try removing this driver.

I also tried v3.19 and v3.19.8, both of which installed correctly and
neither of which exhibits the issue I have with 3.19.0-18

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.19 kernel-
fixed-upstream-3.19.8

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

I have tried 3.19.0-20.20 and I have the same issue.

Here is uname-a and partial ifconfig with 3.19.0-20.20

mark@msapiro:~$ uname -a
Linux msapiro 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
mark@msapiro:~$ ifconfig
eth0  Link encap:Ethernet  HWaddr 70:54:d2:97:05:11  
  inet addr:10.211.115.100  Bcast:10.211.115.255  Mask:255.255.255.0
  inet6 addr: 2602:306:bdbc:1bcf:7254:d2ff:fe97:511/64 Scope:Global
  inet6 addr: fe80::7254:d2ff:fe97:511/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:866 errors:339 dropped:0 overruns:339 frame:0
  TX packets:947 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:179466 (179.4 KB)  TX bytes:109344 (109.3 KB)
  Interrupt:17 

Note the errors/overruns on the interface as with 3.19.0-18. Compare to
3.19.8 below with more packets/data and no errors.

mark@msapiro:~$ uname -a
Linux msapiro 3.19.8-031908-generic #201505110938 SMP Mon May 11 13:39:59 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
mark@msapiro:~$ ifconfig
eth0  Link encap:Ethernet  HWaddr 70:54:d2:97:05:11  
  inet addr:10.211.115.100  Bcast:10.211.115.255  Mask:255.255.255.0
  inet6 addr: 2602:306:bdbc:1bcf:7254:d2ff:fe97:511/64 Scope:Global
  inet6 addr: fe80::7254:d2ff:fe97:511/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1138 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1286 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:333226 (333.2 KB)  TX bytes:156585 (156.5 KB)
  Interrupt:17 


** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

I have updated the bios. I have a windows partition on the machine and I
booted windows and downloaded the bios update from http://support.hp.com
/us-en/drivers/selfservice/HP-Pavilion-HPE-h8-1300-Desktop-PC-
series/5258496/model/5261720 and installed it under windows. (this broke
grub, but I can deal with that)

I still have the same issue - ethernet works if I fall back to
3.19.0-16-generic, but not with 3.19.0-18

mark@msapiro:~$ sudo dmidecode -s bios-version  sudo dmidecode -s 
bios-release-date
8.21
10/20/2014
mark@msapiro:~$ 


** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458208] [NEW] AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Mark Sapiro]

Public bug reported:

Partial lshw output:

  *-network
   description: Ethernet interface
   product: AR8161 Gigabit Ethernet
   vendor: Qualcomm Atheros
   physical id: 0
   bus info: pci@:04:00.0
   logical name: eth0
   version: 08
   serial: 70:54:d2:97:05:11
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=alx duplex=full 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
   resources: irq:30 memory:f710-f713 ioport:d000(size=128)

Partial ifconfig output:
eth0  Link encap:Ethernet  HWaddr 70:54:d2:97:05:11  
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1276 errors:609 dropped:0 overruns:609 frame:0
  TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:230131 (230.1 KB)  TX bytes:142978 (142.9 KB)
  Interrupt:17 

The ethernet adapter stopped working on upgrade from linux
3.19.0-16-generic to 3.19.0-18-generic. Upon inital system start, I can
successfully ping a remote server, but once I try any TCP connection,
even ping fails.

If I fallback to 3.19.0-16, everything is working OK.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-18-generic 3.19.0-18.18
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  mark   2611 F pulseaudio
 /dev/snd/controlC1:  mark   2611 F pulseaudio
 /dev/snd/controlC0:  mark   2611 F pulseaudio
CurrentDesktop: Unity
Date: Sat May 23 10:21:44 2015
HibernationDevice: RESUME=UUID=b4733b71-2c28-4a85-8450-6f330135cfe4
InstallationDate: Installed on 2013-04-24 (758 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
MachineType: Hewlett-Packard h8-1360t
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=578349d7-ca6f-4750-b977-7674ad95c763 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-18-generic N/A
 linux-backports-modules-3.19.0-18-generic  N/A
 linux-firmware 1.143.1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-05-20 (3 days ago)
dmi.bios.date: 07/02/2012
dmi.bios.vendor: AMI
dmi.bios.version: 7.15
dmi.board.name: 2AD5
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.03
dmi.chassis.asset.tag: 2MD3140FD9
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr7.15:bd07/02/2012:svnHewlett-Packard:pnh8-1360t:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: h8-1360t
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458208

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1408369] Re: No apache2.4 config

[Mark Sapiro]

This affects the Debian/Ubuntu mailman package. It does not affect the
GNU Mailman project.

** Project changed: mailman = mailman (Ubuntu)

-- 
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/1408369

Title:
  No apache2.4 config

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1408369/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1408369] Re: No apache2.4 config

[Mark Sapiro]

This affects the Debian/Ubuntu mailman package. It does not affect the
GNU Mailman project.

** Project changed: mailman = mailman (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408369

Title:
  No apache2.4 config

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1408369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1266288] Re: cannot install permissions correctly

[Mark Sapiro]

In the upstream Debian package, these entries in /var/lib/mailman are
actually symlinks as

lrwxrwxrwx  1 root root   20 Jul 17  2012 bin - /usr/lib/mailman/bin/
lrwxrwxrwx  1 root root   24 Jul 17  2012 cgi-bin - /usr/lib/cgi-bin/mailman/
lrwxrwxrwx  1 root root   21 Jul 17  2012 cron - /usr/lib/mailman/cron/
lrwxrwxrwx  1 root root   25 Jul 17  2012 icons - /usr/share/images/mailman/
lrwxrwxrwx  1 root root   17 Jul 17  2012 locks - /var/lock/mailman/
lrwxrwxrwx  1 root root   16 Jul 17  2012 logs - /var/log/mailman/
lrwxrwxrwx  1 root root   21 Jul 17  2012 mail - /usr/lib/mailman/mail/
lrwxrwxrwx  1 root root   24 Jul 17  2012 Mailman - /usr/lib/mailman/Mailman/
lrwxrwxrwx  1 root root   24 Jul 17  2012 scripts - /usr/lib/mailman/scripts/
lrwxrwxrwx  1 root root   12 Jul 17  2012 templates - /etc/mailman/

check_perms is not designed to handle symlinks. It looks at the
ownership and mode of the symlink itself and complains and then, if
requested, fixes the target. Thus, it never fixes the symlink which it
can't do anyway.

Other than the complaint from check_perms, this is not a problem as the
ownership and mode of the symlink itself is irrelevant in practice.

-- 
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/1266288

Title:
  cannot install permissions correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1266288/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1266288] Re: cannot install permissions correctly

[Mark Sapiro]

I have looked at this a bit more deeply, and while all I said in comment
2 is correct, there is another issue. Essentially all the issues
reported by check_perms are innocuous and just reflect differences
between the Debian way and standard GNU Mailman, these fixes

/var/lib/mailman/archives/private bad group (has: www-data, expected list) 
(fixing)
/var/lib/mailman/archives/private/mailman.mbox bad group (has: www-data, 
expected list) (fixing)
/var/lib/mailman/archives/private/mailman bad group (has: www-data, expected 
list) (fixing)
/var/lib/mailman/archives/private/mailman/index.html bad group (has: www-data, 
expected list) (fixing)

will break public archive access. This is because the standard
recommended ownership and mode for /var/lib/mailman/archives/private
would be

drwxrws---   www-data list

but the Debian way is

drwxrws---   list www-data

While this might work, check_perms will change it to

drwxrws---   list list

which won't allow the web server to access public archives. See the
Warning at http://www.list.org/mailman-install/node9.html for more
detail.

The bottom line is the standard check_perms should not be run against
the Debian/Ubuntu package. Debian should either drop check_perms from
the package or fix it to follow the Debian way.

-- 
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/1266288

Title:
  cannot install permissions correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1266288/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1266288] Re: cannot install permissions correctly

[Mark Sapiro]

In the upstream Debian package, these entries in /var/lib/mailman are
actually symlinks as

lrwxrwxrwx  1 root root   20 Jul 17  2012 bin - /usr/lib/mailman/bin/
lrwxrwxrwx  1 root root   24 Jul 17  2012 cgi-bin - /usr/lib/cgi-bin/mailman/
lrwxrwxrwx  1 root root   21 Jul 17  2012 cron - /usr/lib/mailman/cron/
lrwxrwxrwx  1 root root   25 Jul 17  2012 icons - /usr/share/images/mailman/
lrwxrwxrwx  1 root root   17 Jul 17  2012 locks - /var/lock/mailman/
lrwxrwxrwx  1 root root   16 Jul 17  2012 logs - /var/log/mailman/
lrwxrwxrwx  1 root root   21 Jul 17  2012 mail - /usr/lib/mailman/mail/
lrwxrwxrwx  1 root root   24 Jul 17  2012 Mailman - /usr/lib/mailman/Mailman/
lrwxrwxrwx  1 root root   24 Jul 17  2012 scripts - /usr/lib/mailman/scripts/
lrwxrwxrwx  1 root root   12 Jul 17  2012 templates - /etc/mailman/

check_perms is not designed to handle symlinks. It looks at the
ownership and mode of the symlink itself and complains and then, if
requested, fixes the target. Thus, it never fixes the symlink which it
can't do anyway.

Other than the complaint from check_perms, this is not a problem as the
ownership and mode of the symlink itself is irrelevant in practice.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1266288

Title:
  cannot install permissions correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1266288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1266288] Re: cannot install permissions correctly

[Mark Sapiro]

I have looked at this a bit more deeply, and while all I said in comment
2 is correct, there is another issue. Essentially all the issues
reported by check_perms are innocuous and just reflect differences
between the Debian way and standard GNU Mailman, these fixes

/var/lib/mailman/archives/private bad group (has: www-data, expected list) 
(fixing)
/var/lib/mailman/archives/private/mailman.mbox bad group (has: www-data, 
expected list) (fixing)
/var/lib/mailman/archives/private/mailman bad group (has: www-data, expected 
list) (fixing)
/var/lib/mailman/archives/private/mailman/index.html bad group (has: www-data, 
expected list) (fixing)

will break public archive access. This is because the standard
recommended ownership and mode for /var/lib/mailman/archives/private
would be

drwxrws---   www-data list

but the Debian way is

drwxrws---   list www-data

While this might work, check_perms will change it to

drwxrws---   list list

which won't allow the web server to access public archives. See the
Warning at http://www.list.org/mailman-install/node9.html for more
detail.

The bottom line is the standard check_perms should not be run against
the Debian/Ubuntu package. Debian should either drop check_perms from
the package or fix it to follow the Debian way.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1266288

Title:
  cannot install permissions correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1266288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1098162] Re: mailman 1:2.1.15-1 FTBFS on amd64 in raring

[Mark Sapiro]

** Changed in: mailman
   Status: Fix Committed = Fix Released

** Changed in: mailman
Milestone: 2.1.16 = 2.1.16rc1

-- 
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 bug go to:
https://bugs.launchpad.net/mailman/+bug/1098162/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1098162] Re: mailman 1:2.1.15-1 FTBFS on amd64 in raring

[Mark Sapiro]

** Changed in: mailman
   Status: Fix Committed = Fix Released

** Changed in: mailman
Milestone: 2.1.16 = 2.1.16rc1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098162

Title:
  mailman 1:2.1.15-1 FTBFS on amd64 in raring

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1098162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1098162] Re: mailman 1:2.1.15-1 FTBFS on amd64 in raring

[Mark Sapiro]

** No longer affects: mailman

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1098162/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1098162] Re: mailman 1:2.1.15-1 FTBFS on amd64 in raring

[Mark Sapiro]

I looked too quickly the first time and thought it was strictly a
Debian/Ubuntu packaging issue and didn't look closely at your comment #1

** Changed in: mailman
   Importance: Undecided = Low

** Changed in: mailman
   Status: New = Fix Committed

** Changed in: mailman
Milestone: None = 2.1.16

** Changed in: mailman
 Assignee: (unassigned) = Mark Sapiro (msapiro)

-- 
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 bug go to:
https://bugs.launchpad.net/mailman/+bug/1098162/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1098162] Re: mailman 1:2.1.15-1 FTBFS on amd64 in raring

[Mark Sapiro]

** No longer affects: mailman

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098162

Title:
  mailman 1:2.1.15-1 FTBFS on amd64 in raring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1098162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1098162] Re: mailman 1:2.1.15-1 FTBFS on amd64 in raring

[Mark Sapiro]

I looked too quickly the first time and thought it was strictly a
Debian/Ubuntu packaging issue and didn't look closely at your comment #1

** Changed in: mailman
   Importance: Undecided = Low

** Changed in: mailman
   Status: New = Fix Committed

** Changed in: mailman
Milestone: None = 2.1.16

** Changed in: mailman
 Assignee: (unassigned) = Mark Sapiro (msapiro)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098162

Title:
  mailman 1:2.1.15-1 FTBFS on amd64 in raring

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1098162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 985845] Re: About use sox in Linux Educational, brazilian distribution for elementary school teather

[Mark Sapiro]

** Project changed: mailman = sox (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985845

Title:
  About use sox in Linux Educational, brazilian distribution for
  elementary school teather

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sox/+bug/985845/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 426979] Re: Mistakes in mailman strings.

[Mark Sapiro]

** Changed in: mailman
Milestone: None = 2.1.14

-- 
Mistakes in mailman strings.
https://bugs.launchpad.net/bugs/426979
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 426979] Re: Mistakes in mailman strings.

[Mark Sapiro]

** Changed in: mailman
   Status: In Progress = Fix Committed

** Branch linked: lp:mailman/2.1

-- 
Mistakes in mailman strings.
https://bugs.launchpad.net/bugs/426979
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 426979] Re: Mistakes in mailman strings.

[Mark Sapiro]

** Changed in: mailman
Milestone: None = 2.1.14

-- 
Mistakes in mailman strings.
https://bugs.launchpad.net/bugs/426979
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 426979] Re: Mistakes in mailman strings.

[Mark Sapiro]

I have made some changes and ignored others for the 2.1.14 release.
Here's a summary.


 _('''You have regular list members but non-digestified mail is
 turned off. They will receive mail until you fix this
 problem.'''), tag=_('Warning: '))

changed to

 _('''You have regular list members but non-digestified mail is
 turned off.  They will receive non-digestified mail until you
 fix this problem.'''), tag=_('Warning: '))

 Label(_('Send welcome messages to new subscribees?')),

not changed per comment #1.

 _('Sender discarded message via web.'))

not changed. It's terse, but OK I think.

 doc.AddItem(Header(3,_(Can't have empty html page.)))

not changed. It's terse, but OK I think.

 table.AddRow([_(This page allows you as the list owner, to permanent
 remove this mailing list from the system. strongThis action is not

changed to

 table.AddRow([_(This page allows you as the list owner, to permanently
 remove this mailing list from the system. strongThis action is not

 'You can access your personal options via the following url:')

not changed.

 _('''An introductory description - a few paragraphs - about the
 list. It will be included, as html, at the top of the listinfo
 page. Carriage returns will end a paragraph - see the details
 for more info.'''),

not changed.

 _(When a new member is subscribed to this list, their initial
 set of options is taken from the this variable's setting.)),

changed to

 _(When a new member is subscribed to this list, their initial
 set of options is taken from this variable's setting.)),

 pWhen personalization is enabled, a few more expansion
 variables that can be included in the a
 href=?VARHELP=nondigest/msg_headermessage header/a and
 a href=?VARHELP=nondigest/msg_footermessage footer/a.

changed to

 pWhen personalization is enabled, a few more expansion
 variables can be included in the a
 href=?VARHELP=nondigest/msg_headermessage header/a and
 a href=?VARHELP=nondigest/msg_footermessage footer/a.

 libuser_optionsurl/b - The url to the user's option

not changed.

 _(When a message is posted to the list, a series of
 moderation steps are take to decide whether the a moderator must
 first approve the message or not. This section contains the
 controls for moderation of both member and non-member postings.

This was changed to

 _(When a message is posted to the list, a series of
 moderation steps are taken to decide whether a moderator must
 first approve the message or not. This section contains the
 controls for moderation of both member and non-member postings.

in Mailman 2.1.12 per bug # 309757

 If you spell the list name as just `mylist', then the email hostname will be
 taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as
 defined in your Defaults.py file or overridden by settings in mm_cfg.py).

not changed.

 When you scrub attachments, they are stored in archive
 area and links are made in the message so that the member can
 access via web browser. If you want the attachments totally
 disappear, you can use content filter options.

changed to

 When you scrub attachments, they are stored in the archive
 area and links are made in the message so that the member can
 access them via a web browser. If you want the attachments to
 totally disappear, you can use content filtering options.

-- 
Mistakes in mailman strings.
https://bugs.launchpad.net/bugs/426979
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 426979] Re: Mistakes in mailman strings.

[Mark Sapiro]

** Changed in: mailman
   Status: In Progress = Fix Committed

** Branch linked: lp:mailman/2.1

-- 
Mistakes in mailman strings.
https://bugs.launchpad.net/bugs/426979
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs