Bug#1069913: dovecot-imapd: dovecot starts before home directories are available

[Peter Chubb]

Package: dovecot-imapd
Version: 1:2.3.21+dfsg1-3+b1
Severity: normal

Dear Maintainer,

   On my system, home directories are automounted using autofs over NFS.
   It appears that dovecot starts before the autofs daemon is completely
   ready. Thus, it seems to be looking at the (empty) mount point 
   and seeing no mailboxes in people's home directories.

   The workaround is to wait until the system is fully up, log in,
   and restart dovecot.

   It's taken me a while to work out what's going on; it seems to have come 
   when I started using systemd instead of sysV init.  I suspect it's an
   ordering issue, but it's not that obvious how to make dovecot delay
   starting until autofs is ready to mount directories.


-- Package-specific info:

dovecot configuration
-
# 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.21 (f6cd4b8e)
# OS: Linux 6.7.12-amd64 x86_64 Debian trixie/sid 
# Hostname: wombat.chubb.wattle.id.au
first_valid_uid = 130
mail_access_groups = mail
mail_full_filesystem_access = yes
mail_location = mbox:~/Mail/:INBOX=/var/mail/%u:INDEX=/var/indices/%u
mail_nfs_storage = yes
mail_privileged_group = mail
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Spam {
special_use = \Junk
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
  separator = /
}
passdb {
  driver = pam
}
passdb {
  driver = pam
}
protocols = " imap"
ssl_cert = 

Versions of packages dovecot-imapd is related to:
ii  dovecot-core [dovecot-common]  1:2.3.21+dfsg1-3+b1
pn  dovecot-dev
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.3.21+dfsg1-3+b1
pn  dovecot-ldap   
pn  dovecot-lmtpd  
pn  dovecot-managesieved   
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
pn  dovecot-sieve  
pn  dovecot-sqlite 

-- no debconf information

Bug#1014037: mailman3-web: Possible memory leak: uwsgi OOMs after a few weeks

[Peter Chubb]

>>>>> "Pierre-Elliott" == Pierre-Elliott Bécue  writes:


Pierre-Elliott> Having the same kind of setup for the past 6 years, I
Pierre-Elliott> never had such an issue.


Since increasing the size of the VM and the last Mailman3 upgrade, I
haven't seen the issue.

-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

Bug#1068894: dokuwiki: Get error accessing syntax help page.

[Peter Chubb]

Package: dokuwiki
Version: 0.0.20220731.a-2
Severity: normal

Dear Maintainer,

Visiting the 'syntax help' page produces the message,
"TypeError: implode(): Argument #2 ($array) must be of type ?array, 
string given"


This has been reported and fixed upstream at 
https://github.com/dokuwiki/dokuwiki/issues/4087

Packaging the new upstream version would fix this and bug  #1067025



-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dokuwiki depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  javascript-common  11+nmu1
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-cookie12-4
ii  libjs-jquery-ui1.13.2+dfsg-1
ii  libphp-simplepie   1.3.1+dfsg-5
ii  perl   5.36.0-7+deb12u1
ii  php2:8.2+93
ii  php-geshi  1.0.9.1-1
ii  php-phpseclib  2.0.42-1+deb12u1
ii  php-random-compat  2.0.21-1
ii  php-xml2:8.2+93
ii  php8.2 [php]   8.2.7-1~deb12u1
ii  php8.2-xml [php-xml]   8.2.7-1~deb12u1
ii  ucf3.0043+nmu1

Versions of packages dokuwiki recommends:
ii  imagemagick  8:6.9.11.60+dfsg-1.6
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.6
ii  php-ldap 2:8.2+93
ii  php8.2-cli [php-cli] 8.2.7-1~deb12u1
ii  php8.2-ldap [php-ldap]   8.2.7-1~deb12u1
ii  wget 1.21.3-1+b2

Versions of packages dokuwiki suggests:
pn  libapache2-mod-xsendfile  

-- Configuration Files:
/etc/dokuwiki/mime.conf changed [not included]
/etc/dokuwiki/plugins.local.php changed [not included]

-- debconf information:
  dokuwiki/wiki/policy: public
  dokuwiki/wiki/failpass:
* dokuwiki/system/restart-webserver: false
  dokuwiki/wiki/email: webmaster@localhost
* dokuwiki/system/documentroot: /
* dokuwiki/system/accessible: global
* dokuwiki/system/writeconf: true
* dokuwiki/wiki/title: TS Wiki
  dokuwiki/wiki/fullname: DokuWiki Administrator
* dokuwiki/system/writeplugins: true
  dokuwiki/wiki/superuser: admin
* dokuwiki/system/purgepages: false
  dokuwiki/system/localnet: 10.0.0.0/24
* dokuwiki/wiki/acl: true
* dokuwiki/wiki/license: cc-by-sa
* dokuwiki/system/configure-webserver: apache2

Bug#1066888: wl-beta: After emacs upgrade, get spammed with warnings

[Peter Chubb]

Package: wl-beta
Version: 2.15.9+0.20230120-1
Severity: normal

Dear Maintainer,

After a routine apt upgrade, I start seeing lots of messages in the
Emacs *Warnings* buffer.  You can ignore them, and get your work done
reading email etc., but they ought to be fixed.  Here are some of them:

 Warning (comp): wl-draft.el:622:7: Warning: ‘string-as-multibyte’ is an 
obsolete function (as of 26.1); use ‘decode-coding-string’.
⛔ Warning (comp): wl-draft.el:752:55: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-draft.el:752:71: Warning: ‘point-at-eol’ is an obsolete 
function (as of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.
⛔ Warning (comp): wl-draft.el:753:25: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-draft.el:753:46: Warning: ‘point-at-eol’ is an obsolete 
function (as of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.
⛔ Warning (comp): wl-draft.el:2006:40: Warning: ‘point-at-eol’ is an obsolete 
function (as of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.
⛔ Warning (comp): wl-draft.el:2126:51: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-draft.el:2126:65: Warning: ‘point-at-eol’ is an obsolete 
function (as of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.
⛔ Warning (comp): wl-draft.el:2127:21: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-draft.el:2127:39: Warning: ‘point-at-eol’ is an obsolete 
function (as of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.
⛔ Warning (comp): wl-action.el:609:18: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-thread.el:990:16: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-thread.el:1016:16: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-thread.el:1018:21: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-thread.el:1018:36: Warning: ‘point-at-eol’ is an obsolete 
function (as of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.
⛔ Warning (comp): wl-fldmgr.el:110:19: Warning: ‘point-at-bol’ is an obsolete 
function (as of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.
⛔ Warning (comp): wl-fldmgr.el:110:38: Warning: ‘point-at-eol’ is an obsolete 
function (as of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, i386

Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wl-beta depends on:
ii  apel10.8+0.20220720-1
ii  emacsen-common  3.0.5
ii  flim1:1.14.9+0.20230205-1
ii  semi1.14.7~0.20230104-1

Versions of packages wl-beta recommends:
ii  ca-certificates20240203
ii  emacs  1:29.2+1-2
ii  emacs-gtk [emacs]  1:29.2+1-2+b1

Versions of packages wl-beta suggests:
pn  bbdb  
pn  bogofilter | bsfilter | spamassassin  
ii  gnupg 2.2.40-2
ii  gnutls-bin3.8.3-1.1
pn  im
pn  maildir-utils 
pn  mhc   
pn  mu-cite   
pn  namazu2   
pn  notmuch   
ii  openssl   3.1.5-1.1
pn  starttls  
pn  w3m-el
pn  x-face-el 

-- no debconf information

Bug#1063502: snapshot.debian.org: 'Archive-update-in-Progress' since Feb 6

[Peter Chubb]

Package: snapshot.debian.org
Severity: normal

Dear Maintainer,
 http://snapshot.debian.org/archive/debian/20240206T163351Z/
 does not have a Release file, and has a file called
 Archive-Update-in-Progress-sallinen.debian.org
 that was last updated on 2024-02-06 16:33:51 
 
 This makes that snapshot unusable.

 All the other snapshots from 2024 I looked at are in the same state,
 but with different dates.

Peter C

Bug#1053442: gcc-riscv64-unknown-elf: Compiler uses incorrect libraries if flags are given on -march

[Peter Chubb]

Package: gcc-riscv64-unknown-elf
Version: 12.2.0-14+11+b1
Severity: important

Dear Maintainer,

When building for softfloat targets, riscv64-unknown-elf-gcc can pick
the wrong multilib crtbegin.o and libgcc.a, etc.

Compare:
  $ riscv64-unknown-elf-gcc -march=rv64imac -mabi=lp64 --print-file-name 
crtbegin.o
  /usr/lib/gcc/riscv64-unknown-elf/12.2.0/rv64imac/lp64/crtbegin.o

with
  $ riscv64-unknown-elf-gcc -march=rv64imac_zicsr_zfencei -mabi=lp64 
--print-file-name crtbegin.o
  /usr/lib/gcc/riscv64-unknown-elf/12.2.0/crtbegin.o

The second and first should be the same, as the base architecture is
the same.

Symptom is:
   
/usr/lib/gcc/riscv64-unknown-elf/12.2.0/../../../riscv64-unknown-elf/bin/ld: 
/usr/lib/gcc/riscv64-unknown-elf/12.2.0/crtbegin.o: can't link double-float 
modules with soft-float modules

This appears to have been fixed before version 14 upstream.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-riscv64-unknown-elf depends on:
ii  binutils-riscv64-unknown-elf  2.41-4+6
ii  libc6 2.37-11
ii  libgcc-s1 13.2.0-4
ii  libgmp10  2:6.3.0+dfsg-2
ii  libisl23  0.26-3
ii  libmpc3   1.3.1-1
ii  libmpfr6  4.2.1-1
ii  libstdc++613.2.0-4
ii  zlib1g1:1.2.13.dfsg-3

gcc-riscv64-unknown-elf recommends no packages.

gcc-riscv64-unknown-elf suggests no packages.

-- no debconf information

Bug#972192: Has been fixed upstream

[Peter Chubb]

Hi Folks,
This bug is now fixed upstream at
https://sourceforge.net/p/rkhunter/rkh_code/ci/efb203b5008a82798f564da32a589de82a7643e3/

Peter C

Bug#1049452: fail2ban should use nftables by default.

[Peter Chubb]

Package: fail2ban
Version: 1.0.2-2
Severity: wishlist

Dear Maintainer,

iptables is deprecated; fail2ban can use nft instead.
Please make nftables the default banning method in 
/etc/fail2ban/jail.conf, and consider changing the Recommends: 
to a Depends: for nftables.

-- System Information:
Debian Release: 12.1
  APT prefers stable
  APT policy: (1002, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-1-amd64 (SMP w/28 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fail2ban depends on:
ii  python3  3.11.2-1+b1

Versions of packages fail2ban recommends:
ii  nftables   1.0.6-2+deb12u1
ii  python3-pyinotify  0.9.6-2
ii  python3-systemd235-1+b2
ii  whois  5.5.17

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20220412cvs-1
pn  monit
ii  rsyslog [system-log-daemon]  8.2302.0-1
pn  sqlite3  


-- no debconf information

Bug#1019299: Now fixed upstream

[Peter Chubb]

Upstream commit 7e863bb fixes this issue.

Please may we have a new version?
-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

Bug#1033072: mailman3-web: After upgrade, moderation operations are broken

[Peter Chubb]

Package: mailman3-web
Version: 0+20200530-2.1
Severity: normal

Dear Maintainer,

I had a working mailman3 installation.  I did 'apt upgrade' which pulled
in a new python3-hyperkitty and nginx.  Now when trying to manage
'held messages' on a list:
  -- the checkbox next to 'Subject' does not toggle all the checkboxes below it.
  -- Clicking on a held message does not switch to a page where I can manage
 the sender of that message. In fact it does nothing.

I suspect the javascript to run this is broken somehow.
In my bro3wser console when looking at teh javascript I see:

Uncaught TypeError: Bootstrap's JavaScript requires jQuery. jQuery must be 
included before Bootstrap's JavaScript.
at Object.jQueryDetection (bootstrap.min.js:34:98)
at bootstrap.min.js:34:407
at bootstrap.min.js:6:200
at bootstrap.min.js:6:288
main.js:38 Uncaught ReferenceError: $ is not defined
at main.js:38:1
held_messages:445 Uncaught ReferenceError: $ is not defined
at held_messages:445:7
held_messages.js:3 Uncaught ReferenceError: $ is not defined
at loadjs (held_messages.js:3:3)
at held_messages:452:1

The held_messages source file refers to jquery-3.6.0; but 
jquery-1.11.3 is installed in /var/lib/mailman3/web/static/postorius/libs/jquery


I notice that version 3.6 is in
/usr/share/python3-django-postorius/static/postorius/libs/jquery ...
should the nginx snippet in /etc/mailman3 be updated to point here?

For now I deleted /var/lib/mailman3/web/static/postorius and replaced it
with a symlink to /usr/share/python3-django-postorius/static/postorius



-- System Information:
Debian Release: 12.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-6-cloud-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mailman3-web depends on:
ii  dbconfig-sqlite3   2.0.24
ii  debconf [debconf-2.0]  1.5.82
ii  init-system-helpers1.65.2
ii  lsb-base   11.6
ii  python33.11.2-1
ii  python3-django-hyperkitty  1.3.7-1
ii  python3-django-postorius   1.3.8-3
ii  python3-psycopg2   2.9.5-1+b1
ii  python3-whoosh 2.7.4+git6-g9134ad92-7
ii  sysvinit-utils [lsb-base]  3.06-2
ii  ucf3.0043+nmu1
ii  uwsgi-core 2.0.21-5
ii  uwsgi-plugin-python3   2.0.21-5

Versions of packages mailman3-web recommends:
ii  nginx  1.22.1-7

Versions of packages mailman3-web suggests:
ii  postgresql  15+247

-- debconf information:
  mailman3-web/remote/port:
  mailman3-web/dbconfig-upgrade: true
  mailman3-web/missing-db-package-error: abort
* mailman3-web/passwords-do-not-match:
* mailman3-web/superuser-mail: listadmin@sel4.systems
  mailman3-web/pgsql/manualconf:
  mailman3-web/mysql/method: Unix socket
* mailman3-web/db/dbname: mailman3web
  mailman3-web/db/basepath:
* mailman3-web/dbconfig-install: true
  mailman3-web/install-error: abort
  mailman3-web/remove-error: abort
  mailman3-web/upgrade-backup: true
* mailman3-web/db/app-user: mailman3web@localhost
  mailman3-web/pgsql/no-empty-passwords:
  mailman3-web/mysql/admin-user:
* mailman3-web/restart-webserver: true
* mailman3-web/pgsql/method: Unix socket
* mailman3-web/pgsql/admin-user: postgres
* mailman3-web/configure-webserver: none
  mailman3-web/internal/reconfiguring: false
  mailman3-web/mysql/authplugin: default
  mailman3-web/nginx-choice:
  mailman3-web/dbconfig-remove: true
  mailman3-web/upgrade-error: abort
* mailman3-web/emailname: sel4.systems
* mailman3-web/dbconfig-reinstall: true
* mailman3-web/superuser-name: seL4
  mailman3-web/remote/host: localhost
  mailman3-web/purge: false
* mailman3-web/database-type: pgsql
* mailman3-web/pgsql/authmethod-user: ident
  mailman3-web/internal/skip-preseed: false
  mailman3-web/pgsql/changeconf: false
* mailman3-web/pgsql/authmethod-admin: ident
  mailman3-web/remote/newhost:

Bug#1029910: Fixing it

[Peter Chubb]

doing
  sudo service mailman3-web stop
  sudo /usr/share/mailman3-web/manage.py  makemigrations --merge
  sudo -u www-data usr/share/mailman3-web/manage.py  migrate
  sudo -u www-data usr/share/mailman3-web/manage.py  compress
  sudo -u www-data usr/share/mailman3-web/manage.py  collectstatic
  sudo service mailman3-web start

fixed it.
-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

Bug#1029910: python3-django-hyperkitty: Threading not working properly

[Peter Chubb]

Package: python3-django-hyperkitty
Version: 1.3.6-1
Severity: normal

Dear Maintainer,

In our mailman3+hyperkitty instance, at https://lists.sel4.systems/
archived threads don't seem to have the connections needed to see 
an enitre thread.

So visiting https://lists.sel4.systems/hyperkitty/list/devel@sel4.systems/ 
shows no recent threads (there have neen some!)

visiting 
https://lists.sel4.systems/hyperkitty/list/devel@sel4.systems/thread/4N2QCZBPB4CD6WAACHT6U3LM3BYGMECO/
 shows only the first message in a thread.

I'm pretty sure this used to work before the last mailman3+hyperkitty upgrade.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-cloud-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-django-hyperkitty depends on:
ii  fonts-glyphicons-halflings   1.009~3.4.1+dfsg-3
ii  libjs-bootstrap4 4.6.1+dfsg1-4
ii  libjs-sphinxdoc  5.3.0-2
ii  python3  3.11.1-1
ii  python3-dateutil 2.8.2-1
ii  python3-django   3:3.2.16-1
ii  python3-django-compressor2.4.1-2
ii  python3-django-extensions3.2.1-2
ii  python3-django-gravatar2 1.4.4-4
ii  python3-django-haystack  3.2.1-1
ii  python3-django-mailman3  1.3.8-1
ii  python3-django-q 1.3.9-4
ii  python3-djangorestframework  3.14.0-1
ii  python3-elasticsearch7.17.6-1
ii  python3-flufl.lock   5.0.1-4
ii  python3-mailmanclient3.3.3-1
ii  python3-mistune  2.0.4-1
ii  python3-networkx 2.8.8-1
ii  python3-robot-detection  0.4.0-3
ii  python3-tz   2022.7-1

Versions of packages python3-django-hyperkitty recommends:
ii  mailman3-web  0+20200530-2.1

python3-django-hyperkitty suggests no packages.

-- no debconf information

Bug#1028518: Bug is fixed upstream..

[Peter Chubb]

The current mailman3 upstream source is fixed.

https://gitlab.com/mailman/mailman/-/commit/1954815f32fea4d9d920cdc74f63bcc24d3b6c49

fixed python3.11 compatibility.
-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

Bug#1028518: mailman3: lmtp runner does not start: python backtrace in logs.

[Peter Chubb]

Package: mailman3
Version: 3.3.7-3
Severity: important

Dear Maintainer,

After a routine apt upgrade, I see in /var/log/syslog:
 Traceback (most recent call last):
 File "/usr/lib/mailman3/bin/runner", line 33, in 
 sys.exit(load_entry_point('mailman==3.3.7', 'console_scripts', 'runner')())
  ^
   File "/usr/lib/python3/dist-packages/click/core.py", line 1130, in __call__
 return self.main(*args, **kwargs)
^^
   File "/usr/lib/python3/dist-packages/click/core.py", line 1055, in main
 rv = self.invoke(ctx)
  
   File "/usr/lib/python3/dist-packages/click/core.py", line 1404, in invoke
 return ctx.invoke(self.callback, **ctx.params)
^^^
   File "/usr/lib/python3/dist-packages/click/core.py", line 760, in invoke
 return __callback(*args, **kwargs)
^^^
   File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in 
new_func
 return f(get_current_context(), *args, **kwargs)
^
   File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 184, in 
main
 runner = make_runner(*runner_spec, once=once)
  
   File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 55, in 
make_runner
 runner_class = find_name(class_path)
^
   File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, 
in find_name
 module = import_module(module_path)
  ^^
   File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
 return _bootstrap._gcd_import(name[level:], package, level)

   File "", line 1206, in _gcd_import
   File "", line 1178, in _find_and_load
   File "", line 1149, in _find_and_load_unlocked
   File "", line 690, in _load_unlocked
   File "", line 940, in exec_module
   File "", line 241, in _call_with_frames_removed
   File "/usr/lib/python3/dist-packages/mailman/runners/lmtp.py", line 128, in 

 class LMTPHandler:
   File "/usr/lib/python3/dist-packages/mailman/runners/lmtp.py", line 129, in 
LMTPHandler
 @asyncio.coroutine
  ^
 AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 
'coroutines'?


This prevents the LMTP runner from starting, and thus makes 
mailman3 never deliver emails.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-cloud-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mailman3 depends on:
ii  dbconfig-sqlite3 2.0.22
ii  debconf [debconf-2.0]1.5.81
ii  init-system-helpers  1.65.2
ii  logrotate3.21.0-1
ii  lsb-base 11.5
ii  python3  3.11.1-1
ii  python3-aiosmtpd 1.4.3-1
ii  python3-alembic  1.8.1-2
ii  python3-authheaders  0.15.1-1
ii  python3-authres  1.2.0-3
ii  python3-click8.1.3-1
ii  python3-dateutil 2.8.2-1
ii  python3-dnspython2.2.1-2
ii  python3-falcon   3.1.0-3+b1
ii  python3-flufl.bounce 4.0-3
ii  python3-flufl.i18n   3.0.1-3
ii  python3-flufl.lock   5.0.1-4
ii  python3-gunicorn 20.1.0-6
ii  python3-importlib-resources  5.1.2-2
ii  python3-lazr.config  2.2.3-3
ii  python3-passlib  1.7.4-3
ii  python3-psycopg2 2.9.4-2+b1
ii  python3-public   2.3-4
ii  python3-requests 2.28.1+dfsg-1
ii  python3-sqlalchemy   1.4.45+ds1-2
ii  python3-zope.component   5.0.1-3
ii  python3-zope.configuration   4.4.1-1
ii  python3-zope.event   4.4-3
ii  python3-zope.interface   5.5.2-1
ii  sysvinit-utils [lsb-base]3.06-2
ii  ucf  3.0043

Versions of packages mailman3 recommends:
ii  exim4-daemon-heavy [mail-transport-agent]  4.96-12

Versions of packages mailman3 suggests:
pn  lynx | www-browser  
pn  mailman3-doc
ii  postgresql  15+246

-- Configuration Files:
/etc/cron.d/mailman3 changed:
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
0  8 * * *  listif [ -x /usr/bin/mailman ]; then /usr/bin/mailman 
notify; fi
0 12 * * *  listif [ -x /usr/bin/mailman ]; then /usr/bin/mailman 
digests --periodic; fi


-- debconf information:
  mailman3/mysql/authplugin: 

Bug#1027852: sssd not compatible with current python

[Peter Chubb]

Package: python3-sss
Version: 2.8.1-1

A routine apt-get upgrade removed python3-sss because it installed
python3 version 3.11.1-1 and python3-sss has
   Depends:  python3 (<< 3.11)




-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

Bug#1019418: apache2: Content-Location header doesn't escape colons

[Peter Chubb]

Package: apache2
Version: 2.4.54-1~deb11u1
Severity: normal

Dear Maintainer,

We have an apache2 server that serves URLs of the form:
   https://server.com/a/b/foo:phd.html

The Content-Location HTTP response header returned is then
   Content-Location: foo:phd.html

which is invalid because of the colon.  It should return
   Content-Location: ./foo:phd.html
so that the : is not treated as a protocol delimiter.



-- Package-specific info:

-- System Information:
Debian Release: 11.4
  APT prefers stable
  APT policy: (1002, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-13-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.54-1~deb11u1
ii  apache2-data 2.4.54-1~deb11u1
ii  apache2-utils2.4.54-1~deb11u1
ii  dpkg 1.20.11
ii  init-system-helpers  1.60
ii  lsb-base 11.1.0
ii  mime-support 3.66
ii  perl 5.32.1-4+deb11u2
ii  procps   2:3.3.17-5

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.0+nmu1

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.0-6+deb11u1
ii  libaprutil1  1.6.1-5
ii  libaprutil1-dbd-sqlite3  1.6.1-5
ii  libaprutil1-ldap 1.6.1-5
ii  libbrotli1   1.0.9-2+b2
ii  libc62.31-13+deb11u3
ii  libcrypt11:4.4.18-4
ii  libcurl4 7.74.0-1.3+deb11u1
ii  libjansson4  2.13.1-1.1
ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libnghttp2-141.43.0-1
ii  libpcre3 2:8.39-13
ii  libssl1.11.1.1n-0+deb11u3
ii  libxml2  2.9.10+dfsg-6.7+deb11u2
ii  perl 5.32.1-4+deb11u2
ii  zlib1g   1:1.2.11.dfsg-2+deb11u1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2 is related to:
ii  apache2  2.4.54-1~deb11u1
ii  apache2-bin  2.4.54-1~deb11u1

-- no debconf information

Bug#1019299: libapache2-mod-python: SEGFAULTS at random times with python3.9 and 3.10

[Peter Chubb]

Package: libapache2-mod-python
Version: 3.5.0+git20211031.e6458ec
Severity: normal
Tags: patch

Dear Maintainer,

(gdb) bt
#0  raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  
#2  __new_sem_post (sem=0x21) at sem_post.c:36
#3  0x7f38785080f9 in PyThread_release_lock ()
   from /lib/x86_64-linux-gnu/libpython3.9.so.1.0
#4  0x7f3878570be9 in ?? () from /lib/x86_64-linux-gnu/libpython3.9.so.1.0
#5  0x7f38788d4a2a in release_interpreter (idata=0x55da959531c0)
at mod_python.c:306
#6  python_handler (req=0x7f387450d0a0, phase=)
at mod_python.c:1573
#7  0x55da949c4bb0 in ap_run_handler ()
#8  0x55da949c51a6 in ap_invoke_handler ()
#9  0x55da949ddabb in ap_process_async_request ()
#10 0x55da949ddcfe in ap_process_request ()
#11 0x55da949d9bad in ?? ()
#12 0x55da949ce860 in ap_run_process_connection ()
#13 0x7f3878960133 in ?? () from /usr/lib/apache2/modules/mod_mpm_worker.so
#14 0x7f3878c5eea7 in start_thread (arg=)
at pthread_create.c:477
#15 0x7f3878b8edef in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Running with more debugging shows the problem to be an attempt 
to release the currently running thread.

This is reported upstream as https://github.com/grisha/mod_python/issues/100


--- a/src/mod_python.c
+++ b/src/mod_python.c
@@ -303,7 +303,7 @@ static void release_interpreter(interpre
 {
 PyThreadState *tstate = PyThreadState_Get();
 #ifdef WITH_THREAD
-PyThreadState_Clear(tstate);
+//PyThreadState_Clear(tstate);
 if (idata)
 APR_ARRAY_PUSH(idata->tstates, PyThreadState *) = tstate;
 else

--


System Information:
Debian Release: 11.4
  APT prefers stable
  APT policy: (1002, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-13-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libapache2-mod-python depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.54-1~deb11u1
ii  libc6   2.31-13+deb11u3
ii  libpython3.93.9.2-1
ii  python3 3.9.2-3

libapache2-mod-python recommends no packages.

Versions of packages libapache2-mod-python suggests:
pn  libapache2-mod-python-doc  

-- no debconf information

Bug#1014037: mailman3-web: Possible memory leak: uwsgi OOMs after a few weeks

[Peter Chubb]

Package: mailman3-web
Version: 0+20200530-2
Severity: normal

Dear Maintainer,

 I have a mailman3 system backed by PostGRES, exim4, and nginx; 
 and it is set up and works properly.  However, the uwsgi process
 keeps growing and growing until the system OOMs. typically 
 after two to three weeks.

 I added more RAM (the system now has 3Gb) but that postponed 
 but did not fix the problem.  As a workaround I now restart 
 the mailman3 service once a day.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-3-cloud-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mailman3-web depends on:
ii  dbconfig-sqlite3   2.0.21
ii  debconf [debconf-2.0]  1.5.79
ii  init-system-helpers1.63
ii  lsb-base   11.2
ii  python33.9.8-1
hi  python3-django-hyperkitty  1.3.4-4
ii  python3-django-postorius   1.3.5-1
ii  python3-psycopg2   2.9.2-2
ii  python3-whoosh 2.7.4+git6-g9134ad92-5
ii  ucf3.0043
ii  uwsgi-core 2.0.20-4+b2
ii  uwsgi-plugin-python3   2.0.20-4+b2

Versions of packages mailman3-web recommends:
ii  nginx   1.20.2-2
ii  nginx-core [nginx]  1.20.2-2+b1

Versions of packages mailman3-web suggests:
ii  postgresql  14+241

-- debconf information:
* mailman3-web/passwords-do-not-match:
  mailman3-web/nginx-choice:
  mailman3-web/install-error: abort
* mailman3-web/pgsql/authmethod-admin: ident
  mailman3-web/remote/port:
* mailman3-web/db/app-user: mailman3web@localhost
* mailman3-web/superuser-mail: listadmin@sel4.systems
* mailman3-web/configure-webserver: none
  mailman3-web/db/basepath:
* mailman3-web/emailname: sel4.systems
  mailman3-web/upgrade-backup: true
  mailman3-web/dbconfig-upgrade: true
  mailman3-web/pgsql/no-empty-passwords:
  mailman3-web/remove-error: abort
  mailman3-web/mysql/method: Unix socket
* mailman3-web/pgsql/admin-user: postgres
* mailman3-web/pgsql/method: Unix socket
* mailman3-web/pgsql/authmethod-user: ident
* mailman3-web/db/dbname: mailman3web
* mailman3-web/restart-webserver: true
  mailman3-web/internal/reconfiguring: false
* mailman3-web/superuser-name: seL4
  mailman3-web/pgsql/manualconf:
  mailman3-web/dbconfig-remove: true
* mailman3-web/dbconfig-install: true
  mailman3-web/remote/host: localhost
  mailman3-web/missing-db-package-error: abort
  mailman3-web/remote/newhost:
  mailman3-web/pgsql/changeconf: false
  mailman3-web/mysql/admin-user:
  mailman3-web/upgrade-error: abort
  mailman3-web/purge: false
* mailman3-web/dbconfig-reinstall: true
  mailman3-web/mysql/authplugin: default
* mailman3-web/database-type: pgsql
  mailman3-web/internal/skip-preseed: false

Bug#1003242: Versions ...

[Peter Chubb]

I think the issue is that python3-django-hyperkitty 1.3.5-1 has this
change:
Pass the secret archiver key in a HTTP Authorization header
instead of a GET query parameter so it doesn’t appear in
logs. (CVE-2021-35058, Closes #387)

See also:
https://lists.mailman3.org/archives/list/mailman-us...@mailman3.org/thread/WSUEPQL6PX52Y7XVWYSSGJJXC7E3F6FG/

So to upgrade to python3-django-hyperkitty 1.3.5-1 you must also
upgrade python3-mailman-hyperkitty to 1.2.0; version 1.1.10 should
conflict with python3-django-hyperkitty versions < 1.3.5
-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW

Bug#1003242: python3-mailman-hyperkitty: Need a newer version to match mailman core

[Peter Chubb]

Package: python3-mailman-hyperkitty
Version: 1.1.0-10
Severity: important

Dear Maintainer,

Since a routine apt upgrade, hyperkitty has stopped archiving emails.
In the log I see:

  Jan 07 00:36:18 2022 (3203621) Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154
, in _archive_message
url = self._send_message(mlist, msg)
  File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210
, in _send_message
raise ValueError(result.text)
ValueError: Auth required
Authorization RequiredThe archiver key is now
 required to be sent over the Authorization HTTP header.
 You need to upgrade the mailman-hyperkitty package to
 1.2.0 or newer.



looks like there are inconsistent packages. 
-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-mailman-hyperkitty depends on:
ii  debconf [debconf-2.0]   1.5.79
ii  mailman33.3.3-1
ii  python3 3.9.8-1
ii  python3-pkg-resources   59.6.0-1
ii  python3-requests2.25.1+dfsg-2
ii  python3-zope.interface  5.4.0-1+b1
ii  ucf 3.0043

Versions of packages python3-mailman-hyperkitty recommends:
ii  mailman3-web   0+20200530-2
ii  python3-django-hyperkitty  1.3.5-1

python3-mailman-hyperkitty suggests no packages.

-- no debconf information

Bug#1003196: python3-mailman-hyperkitty: postinst should run django-admin migrate

[Peter Chubb]

Package: python3-mailman-hyperkitty
Version: 1.1.0-10
Severity: normal

Dear Maintainer,

After a routine apt-upgrade, archives showed 'server error' instead of an 
archive.

THe issue was that the database schema needed update.

I believe the postinst script should run:
  sudo -u www-data django-admin migrate --pythonpath /usr/share/mailman3-web 
--settings settings 
or ask the user to.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-mailman-hyperkitty depends on:
ii  debconf [debconf-2.0]   1.5.79
ii  mailman33.3.3-1
ii  python3 3.9.8-1
ii  python3-pkg-resources   59.6.0-1
ii  python3-requests2.25.1+dfsg-2
ii  python3-zope.interface  5.4.0-1+b1
ii  ucf 3.0043

Versions of packages python3-mailman-hyperkitty recommends:
ii  mailman3-web   0+20200530-2
ii  python3-django-hyperkitty  1.3.5-1

python3-mailman-hyperkitty suggests no packages.

-- debconf information:
  python3-mailman-hyperkitty/no_archiverkey:

Bug#996508: reportbug: davmail server doesn't start

[Peter Chubb]

>>>>> "Alexandre" == Alexandre Rossi  writes:

Alexandre> Hi, Thanks for your bug report.

>> After upgrading davmail, it did not start.  /usr/bin/davmail is now
>> a jar file; it doesn't run without java.

Alexandre> /usr/bin/davmail is a jar file that gets executable using
Alexandre> jarwrapper.

I worked that out.  The issue is that inside a container,
/proc/fs/binfmt_misc cannot be changed.  So to get it to work,
jarwrapper needs to be installed on the host, as well as in the
container.

To fix, one way is not to rely on /proc/fs/binfmt_misc to be set up,
but invoke jarwrapper directly from the systemd unit file, and/or the
/etc/init.d/davmail script.

Peter C
-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW

Bug#996508: reportbug: davmail server doesn't start

[Peter Chubb]

Package: davmail
Version: 6.0.0.3375-2
Severity: normal

Dear Maintainer,

After upgrading davmail, it did not start.  /usr/bin/davmail is now a jar file; 
it doesn't run without java.

/etc/init.d/davmail start
dows not give any information. (and does not start the server).

I had to do:
  java -jar /usr/bin/davmail -server /etc/davmail/davmail.properties
to start the server.

I'm running davmail in a container, if that makes a difference.
-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages davmail depends on:
ii  adduser   3.118
ii  default-jre-headless [java9-runtime-headless] 2:1.11-72
ii  init-system-helpers   1.60
ii  jarwrapper0.78
ii  libcommons-codec-java 1.15-1
ii  libcommons-httpclient-java3.1-16
ii  libcommons-logging-java   1.2-2
ii  libhtmlcleaner-java   2.24-1
ii  libhttpclient-java4.5.13-3
ii  libjackrabbit-java2.20.3-1
ii  libjcifs-java 1.3.19-2
ii  libjettison-java  1.4.1-1
ii  liblog4j1.2-java  1.2.17-10
ii  libmail-java  1.6.5-1
ii  libservlet-api-java   4.0.1-2
ii  libslf4j-java 1.7.32-1
ii  libstax2-api-java 4.1-1
ii  libwoodstox-java  1:6.2.1-1
ii  logrotate 3.18.1-2
ii  lsb-base  11.1.0
ii  openjdk-11-jre-headless [java9-runtime-headless]  11.0.12+7-2

davmail recommends no packages.

Versions of packages davmail suggests:
pn  default-jre 
pn  libopenjfx-java 
pn  libswt-cairo-gtk-4-jni  

-- Configuration Files:
/etc/davmail/davmail.properties changed:
 DavMail settings, see http://davmail.sourceforge.net/ for documentation
davmail.server=true
davmail.mode=EWS
davmail.url=https://outlook.office365.com/EWS/Exchange.asmx
davmail.caldavPort=8443
davmail.imapPort=1143
davmail.ldapPort=1389
davmail.popPort=1110
davmail.smtpPort=1025
davmail.enableProxy=false
davmail.useSystemProxies=false
davmail.proxyHost=
davmail.proxyPort=
davmail.proxyUser=
davmail.proxyPassword=
davmail.noProxyFor=
davmail.allowRemote=true
davmail.bindAddress=
davmail.clientSoTimeout=
davmail.ssl.keystoreType=PKCS12
davmail.ssl.keystoreFile=/etc/davmail/davmail.p12
davmail.ssl.keystorePass=redacted
davmail.ssl.keyPass=redacted
davmail.server.certificate.hash=
davmail.ssl.nosecurecaldav=false
davmail.ssl.nosecureimap=false
davmail.ssl.nosecureldap=false
davmail.ssl.nosecurepop=false
davmail.ssl.nosecuresmtp=false
davmail.disableUpdateCheck=true
davmail.enableKeepAlive=true
davmail.folderSizeLimit=0
davmail.defaultDomain=
davmail.caldavAlarmSound=
davmail.caldavPastDelay=90
davmail.caldavAutoSchedule=true
davmail.forceActiveSyncUpdate=false
davmail.imapAutoExpunge=true
davmail.imapIdleDelay=
davmail.imapAlwaysApproxMsgSize=
davmail.keepDelay=30
davmail.sentKeepDelay=90
davmail.popMarkReadOnRetr=false
davmail.smtpSaveInSent=true
davmail.logFilePath=/var/log/davmail/davmail.log
davmail.logFileSize=1MB
log4j.logger.davmail=WARN
log4j.logger.httpclient.wire=WARN
log4j.logger.org.apache.commons.httpclient=WARN
log4j.rootLogger=WARN

-- no debconf information

Bug#993746: python3-django-postorius: CVE-2021-40347 New upstream to fix security bug

[Peter Chubb]

Package: python3-django-postorius
Version: 1.3.4-2
Severity: important
Tags: upstream

Dear Maintainer,

There is a new upstream (and patches to this version) available, to address 
security issue CVE-2021-40347.  This vulnerability allows any logged-in-user
to unsubscribe any user from any list.

Version 1.3.5 fixes the issue; plus a patch was posted to the 
mailman3 mailing list.



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-django-postorius depends on:
ii  fonts-glyphicons-halflings  1.009~3.4.1+dfsg-2
ii  libjs-bootstrap44.5.2+dfsg1-8
ii  libjs-jquery3.5.1+dfsg+~3.5.5-7
ii  libjs-sphinxdoc 3.5.4-2
ii  node-html5shiv  3.7.3+dfsg-3
ii  python3 3.9.2-3
ii  python3-cmarkgfm0.4.2-1+b3
ii  python3-django  2:2.2.24-1
ii  python3-django-mailman3 1.3.5-2
ii  python3-mailmanclient   3.3.2-1
ii  python3-readme-renderer 24.0-3
ii  sphinx-rtd-theme-common 0.5.1+dfsg-1

Versions of packages python3-django-postorius recommends:
ii  mailman3-web  0+20200530-2

python3-django-postorius suggests no packages.

-- no debconf information

Bug#992468: Found and fixed the issue

[Peter Chubb]

close 992468

The issue was with content-security policy needing 'unsafe-inline'.

Peter C
-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW

Bug#992468: python3-django-hyperkitty: 'Recent' and 'Popular' buttons hang forever.

[Peter Chubb]

Package: python3-django-hyperkitty
Version: 1.3.4-4
Severity: normal

Dear Maintainer,

I have a mailman3 plus hyperkitty installation, all installed from Debian.
When looking at the archives, I see a spinning wheel, for 'Activity Summary',
and 'Most active posters' on the left hand side, and for 
'Most recent discussions' in the middle.

Looking at the 'By month' lists works properly.

The lists are public, you can see one
at https://lists.sel4.systems/hyperkitty/list/devel@sel4.systems/



-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-django-hyperkitty depends on:
ii  fonts-glyphicons-halflings   1.009~3.4.1+dfsg-2
ii  libjs-bootstrap4 4.5.2+dfsg1-8
ii  libjs-sphinxdoc  3.4.3-2
ii  python3  3.9.2-3
ii  python3-dateutil 2.8.1-6
ii  python3-django   2:2.2.24-1
ii  python3-django-compressor2.4-2
ii  python3-django-extensions3.0.3-3
ii  python3-django-gravatar2 1.4.4-2
ii  python3-django-haystack  3.0-1
ii  python3-django-mailman3  1.3.5-2
ii  python3-django-q 1.2.1-1
ii  python3-djangorestframework  3.12.1-1
ii  python3-elasticsearch7.1.0-3
ii  python3-flufl.lock   5.0.1-1
ii  python3-mailmanclient3.3.2-1
ii  python3-networkx 2.5+ds-2
ii  python3-robot-detection  0.4.0-2
ii  python3-tz   2021.1-1

Versions of packages python3-django-hyperkitty recommends:
ii  mailman3-web  0+20200530-2

python3-django-hyperkitty suggests no packages.

-- no debconf information

Bug#990299: conserver-server: Linux's high baud rates are not recognised

[Peter Chubb]

Package: conserver-server
Version: 8.2.6-2
Severity: wishlist
Tags: patch

Dear Maintainer,

While trying to attach a rockpro64 to the conserver, I discovered that baud
rates in the extended range (above 115200) are not recognised.  The
rockpro64 uses 150 baud as its standard.

The attached patch adds the higher rates, as Linux (and possibly other 
platforms) support them as a POSIX extension.


--- a/conserver/consent.c
+++ b/conserver/consent.c
@@ -86,6 +86,42 @@ BAUD baud[] = {
 {"350", 32},
 {"400", 33},
 #else /* FOR_CYCLADES_TS */
+# if defined(B400)
+{"400", B400},
+# endif
+# if defined(B350)
+{"350", B350},
+# endif
+# if defined(B300)
+{"300", B30},
+# endif
+# if defined(B250)
+{"250", B25},
+# endif
+# if defined(B200)
+{"200", B20},
+# endif
+# if defined(B150)
+{"150", B150},
+# endif
+# if defined(B100)
+{"100", B100),
+#endif
+# if defined(B921600)
+{"921600", B921600},
+#endif
+# if defined(B576000)
+{"576000", B576000},
+#endif
+#if defined(B50)
+{"50", B50},
+#endif
+#if defined(B460800)
+{"460800", B460800},
+#endif
+# if defined(B230400)
+{"230400", B230400},
+#endif
 # if defined(B115200)
 {"115200", B115200},
 # endif


-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages conserver-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.77
ii  init-system-helpers1.60
ii  libc6  2.31-12
ii  libcrypt1  1:4.4.18-4
ii  libgssapi-krb5-2   1.18.3-5
ii  libipmiconsole21.6.6-3
ii  libpam0g   1.4.0-7
ii  libssl1.1  1.1.1k-1
ii  libwrap0   7.6.q-31
ii  lsb-base   11.1.0

conserver-server recommends no packages.

conserver-server suggests no packages.

-- Configuration Files:
/etc/conserver/conserver.cf changed [not included]

-- debconf information excluded

Bug#990298: conserver-server: console type 'ipmi' is not recognised.

[Peter Chubb]

Package: conserver-server
Version: 8.2.6-2
Severity: normal

Dear Maintainer,

   The manpage for conserver.cf says there is a console type 'ipmi'
   to talk directly to an ipmi console.

   It looks as if the version of conserver-server shipped with Debian
   is not linked with libipmiconsole so this does not work.

   I suggest either adding --with-freeipmi to the configure rule, and
   build-dep on libipmiconsole-dev and libfreeipmi-dev; or editing the man page
   to remove references to this (unsupported) console type.

-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages conserver-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.77
ii  init-system-helpers1.60
ii  libc6  2.31-12
ii  libcrypt1  1:4.4.18-4
ii  libgssapi-krb5-2   1.18.3-5
ii  libpam0g   1.4.0-7
ii  libssl1.1  1.1.1k-1
ii  libwrap0   7.6.q-31
ii  lsb-base   11.1.0

conserver-server recommends no packages.

conserver-server suggests no packages.

-- Configuration Files:
/etc/conserver/conserver.cf changed [not included]

-- debconf information excluded

Bug#988747: apache2: README.backtrace gives incorrect instructions

[Peter Chubb]

Package: apache2
Version: 2.4.47-1
Severity: normal

Dear Maintainer,

I'm trying to work out why Apache2 is segfaulting, so want it to
generate a core file.

The instructures in /usr/share/doc/apache2/README.backtrace are no
longer valid: they refer to packages that no longer exist in sid
(apache2-bin-dbgsym libapr1-dbgsym libaprutil1-dbgsym) and assume
SystemV init (not systemd).

Please will you put current instructions on how to get a backtrace
from a Debian-installed apache2 into README.backtrace?

-- Package-specific info:

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.47-1
ii  apache2-data 2.4.47-1
ii  apache2-utils2.4.47-1
ii  dpkg 1.20.9
ii  init-system-helpers  1.60
ii  lsb-base 11.1.0
ii  mime-support 3.66
ii  perl 5.32.1-4
ii  procps   2:3.3.17-5

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.0

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.0-6
ii  libaprutil1  1.6.1-5
ii  libaprutil1-dbd-sqlite3  1.6.1-5
ii  libaprutil1-ldap 1.6.1-5
ii  libbrotli1   1.0.9-2+b2
ii  libc62.31-11
ii  libcrypt11:4.4.18-4
ii  libcurl4 7.74.0-1.2
ii  libjansson4  2.13.1-1.1
ii  libldap-2.4-22.4.57+dfsg-2
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libnghttp2-141.43.0-1
ii  libpcre3 2:8.39-13
ii  libssl1.11.1.1k-1
ii  libxml2  2.9.10+dfsg-6.6
ii  perl 5.32.1-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2 is related to:
ii  apache2  2.4.47-1
ii  apache2-bin  2.4.47-1

-- no debconf information

--1621317442-eximdsn-650277503--

Bug#961484: linkchecker: Linkchecker has new upstream

[Peter Chubb]

Package: linkchecker
Version: 9.4.0-2
Severity: normal

Dear Maintainer,
 the version of linkchecker packaged for Debian comes from
  https://github.com/wummel/linkchecker
 This version hasn't been maintained for years.  It was forked and 
 is now maintained at https://github.com/linkchecker/linkchecker

 The new version runs with Python 3,


-- Systes Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/28 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linkchecker depends on:
ii  libc6 2.28-10
ii  python2.7.16-1
ii  python-dnspython  1.16.0-1
ii  python-requests   2.21.0-1
ii  python-urllib31.24.1-1
ii  python-xdg0.25-5

linkchecker recommends no packages.

Versions of packages linkchecker suggests:
pn  clamav-daemon   
pn  linkchecker-web 
pn  python-argcomplete  
pn  python-cssutils 
pn  python-gconf
pn  python-geoip
pn  python-meliae   

-- no debconf information

Bug#956856: w3m-el fails to install

[Peter Chubb]

Package: w3m-el
Version: 1.4.632+0.20181112-2
Severity: important

Dear Maintainer,

In attempting to install w3m-el I see:
  Install w3m-el for emacs
  install/w3m-el: byte-compiling for emacs, logged in /tmp/elc.9ZAzScQdF0F8
  ERROR: install script from w3m-el package failed
  dpkg: error processing package w3m-el (--configure):
   installed w3m-el package post-installation script subprocess returned error 
exit status 1


In the emacs compile log I see:
emacs -q -no-site-file -batch -l __myinit.el -l w3mhack.el . -f 
w3mhack-generate-load-file
emacs -q -no-site-file -batch -l __myinit.el -f batch-byte-compile 
bookmark-w3m.el w3m-antenna.el w3m-bookmark.el w3m-bug.el w3m-ccl.el 
w3m-cookie.el w3m-dtree.el w3m-ems.el w3m-favicon.el w3m-fb.el w3m-filter.el 
w3m-form.el w3m-hist.el w3m-image.el w3m-lnum.el w3m-mail.el w3m-namazu.el 
w3m-perldoc.el w3m-proc.el w3m-rss.el w3m-save.el w3m-search.el w3m-session.el 
w3m-symbol.el w3m-tabmenu.el w3m-util.el w3m-weather.el w3m.el mime-w3m.el 
octet.el

In toplevel form:
w3m-antenna.el:49:1:Error: Wrong type argument: stringp, nil

In toplevel form:
w3m-bookmark.el:40:1:Error: Wrong type argument: stringp, nil

In toplevel form:
w3m-cookie.el:45:1:Error: Wrong type argument: stringp, nil

In toplevel form:
w3m-dtree.el:35:1:Error: Wrong type argument: stringp, nil

In toplevel form:
w3m-filter.el:40:1:Error: Wrong type argument: stringp, nil
 And so on.

w3m-el-snapshot installs successfully.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages w3m-el depends on:
ii  apel 10.8+0.20120427-21
ii  dpkg 1.19.7
ii  emacs1:26.3+1-1
ii  emacs-lucid [emacs]  1:26.3+1-1
ii  emacsen-common   3.0.4
ii  install-info 6.7.0.dfsg.2-5
ii  w3m  0.5.3-37+b1

Versions of packages w3m-el recommends:
ii  apel  10.8+0.20120427-21
ii  flim  1:1.14.9+0.20120428-24

Versions of packages w3m-el suggests:
ii  bzip21.0.8-2
pn  discount | libtext-markdown-perl | markdown  
ii  imagemagick  8:6.9.10.23+dfsg-2.1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+b2
pn  libmoe1.5
pn  mule-ucs 
pn  namazu2  
pn  perl-doc 
ii  poppler-utils [xpdf-utils]   0.71.0-6
pn  ppthtml  
pn  wv   
pn  xlhtml   

-- no debconf information

Bug#947761: texlive-extra-utils: pdfbook2 ignores --signatures argument

[Peter Chubb]

Package: texlive-extra-utils
Version: 2019.20191208-1
Severity: normal

Dear Maintainer,

pdfbook2 takes a --signatures=INT argument,that is meant to be passed
on to Pdfjam, to say how many pages are in each signature.  It appears
to be ignored.
   I have a 120 page PDF file, formatted for A5 paper, called book.pdf
   I do:
 pdfbook2 --signature=24 book.pdf

   I expext the resulting book-book.pdf file to contain pages 1
   through 24, 25 through 48, 49 through 72, 73 through 98, and 99
   through 120 gathered and formatted.

   Instead the whole file is formatted as a single signature.

   I've tracked this down to pdfpages2 passing --booklet TRUE to
   pdfjam, an argument that overrides the --signature option.

   Debian used to come with pdfbook which didn't have this issue.
   Using pdfbook as a command, tells me to install
 texlive-extra-utils
   which conatins pdfbook2 instead of pdfbook.

   Can pdfbook be packaged in texlive-extra-utils instead of pdfbook2?
   It works better. 


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-rw-r-- 1 root staff 14351 May 23  2016 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 3141 Dec 28 17:51 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Dec  3 21:04 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Dec  9 10:15 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Dec  9 10:15 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 838 Dec 28 17:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Dec  9 10:15 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
-rw-r--r-- 1 root root 158 Mar  4  2016 /etc/texmf/web2c/updmap.cfg
-rw-r--r-- 1 root root 3151 Dec 28 17:51 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 12
-rw-r--r-- 1 root root 283 Jun 26  2011 mktex.cnf
-rw-r--r-- 1 root root 838 Dec 28 17:43 texmf.cnf
-rw-r--r-- 1 root root 158 Mar  4  2016 updmap.cfg
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf
1df66bc319cec731e202eaf39f5d85e1  /etc/texmf/texmf.d/96JadeTeX.cnf

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'oldoldstable'), (500, 'testing'), (500, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 5.5.0-rc3 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages texlive-extra-utils depends on:
ii  libunicode-linebreak-perl  0.0.20190101-1+b2
ii  python 2.7.17-2
ii  tex-common 6.13
ii  texlive-base   2019.20191208-4
ii  texlive-binaries   2019.20190605.51237-3
ii  texlive-latex-base 2019.20191208-4

Versions of packages texlive-extra-utils recommends:
ii  ghostscript   9.50~dfsg-5
ii  libfile-homedir-perl  1.004-1
ii  liblog-log4perl-perl  

Bug#740369: libapache2-mod-python: needs python3 support

[Peter Chubb]

Package: libapache2-mod-python
Version: 3.3.1-11
Followup-For: Bug #740369

Dear Maintainer,

Given that python2 is nearing end-of-life, it's becoming urgent to package a
a version of libapache2-mod-python that supports python3.

Please package up version 3.5 for Debian.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (800, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/28 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libapache2-mod-python depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.41-1
ii  libc6   2.29-2
ii  libpython2.72.7.17-1
ii  python  2.7.17-1

libapache2-mod-python recommends no packages.

Versions of packages libapache2-mod-python suggests:
pn  libapache2-mod-python-doc  

-- no debconf information

Bug#931398: owncloud-client: Dependency issue?

[Peter Chubb]

Package: owncloud-client
Version: 2.5.1.10973+dfsg-1
Severity: normal

Dear Maintainer,

 I did:
   apt-get update
   apt-get instal owncloud-client
   /usr/bin/owncloud

 and see:
   owncloud: error while loading shared libraries: libqt5keychain.so.0: 
cannot open shared object file: No such file or directory

 owncloud-client depends on libqt5keychain1 which installs
 /usr/lib/x86_64-linux-gnu/libqt5keychain.so.1


 Looks like it neeeds rebuilding against the current libraries.
 I did that and all was well.

Peter C  

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages owncloud-client depends on:
ii  libc6 2.28-10
ii  libgcc1   1:8.3.0-7
ii  libowncloudsync0  2.5.1.10973+dfsg-1
ii  libqt5core5a  5.11.3+dfsg1-2
ii  libqt5dbus5   5.11.3+dfsg1-2
ii  libqt5gui55.11.3+dfsg1-2
ii  libqt5keychain1   0.9.1-2
ii  libqt5network55.11.3+dfsg1-2
ii  libqt5sql5-sqlite 5.11.3+dfsg1-2
ii  libqt5webkit5 5.212.0~alpha2-21
ii  libqt5widgets55.11.3+dfsg1-2
ii  libqt5xml55.11.3+dfsg1-2
ii  libstdc++68.3.0-7
ii  owncloud-client-l10n  2.5.1.10973+dfsg-1

Versions of packages owncloud-client recommends:
ii  owncloud-client-doc  2.5.1.10973+dfsg-1

owncloud-client suggests no packages.

-- no debconf information

Bug#922365: openssh-server: dpkg --configure fails

[Peter Chubb]

Package: openssh-server
Version: 1:7.9p1-6
Severity: normal

Dear Maintainer,

During a normal upgrade of ssh, I see:
Restarting OpenBSD Secure Shell server: sshdstart-stop-daemon: matching only on 
non-root pidfile /run/sshd.pid is insecure
invoke-rc.d: initscript ssh, action "restart" failed.

and the package remains `unconfigured' in the database.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.70
ii  dpkg   1.19.4
ii  libaudit1  1:2.8.4-2
ii  libc6  2.28-6
ii  libcom-err21.44.5-1
ii  libgssapi-krb5-2   1.17-1
ii  libkrb5-3  1.17-1
ii  libpam-modules 1.1.8-4
ii  libpam-runtime 1.1.8-4
ii  libpam0g   1.1.8-4
ii  libselinux12.8-1+b1
ii  libssl1.1  1.1.1a-2~20190131152537.8+stretch
ii  libsystemd0240-5
ii  libwrap0   7.6.q-27
ii  lsb-base   10.2018112800
ii  openssh-client 1:7.9p1-6
ii  openssh-sftp-server1:7.9p1-6
ii  procps 2:3.3.15-2
ii  ucf3.0038+nmu1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages openssh-server recommends:
pn  libpam-systemd  
ii  ncurses-term6.1+20181013-1
ii  xauth   1:1.0.10-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  rssh  
pn  ssh-askpass   
pn  ufw   

-- debconf information:
* ssh/use_old_init_script: true
  ssh/encrypted_host_key_but_no_keygen:
* openssh-server/permit-root-login: true
  ssh/disable_cr_auth: false
  openssh-server/password-authentication: true
  ssh/vulnerable_host_keys:

Bug#907862: gtkpod segfaults on startup

[Peter Chubb]

Package: gtkpod
Version: 2.1.5-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

I installed gtkpod, ran gio mount afc://serialnumber then started
gtkpod.  ~/.gtkpod did not exist before I started.  The iPad is
mounted in /run/user/uid/gvfs/afc:serialnumber 

I get an immediate segmentation fault.

GDB shows:
(gdb) r
Starting program: /usr/bin/gtkpod 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe54a1700 (LWP 3285)]
[New Thread 0x7fffe4b5f700 (LWP 3286)]
[New Thread 0x7fffd700 (LWP 3287)]
[New Thread 0x7fffdf7fe700 (LWP 3288)]
[New Thread 0x7fffdedf0700 (LWP 3289)]

(gtkpod:3280): GLib-GObject-CRITICAL **: 20:14:43.209: 
g_value_type_transformable: assertion 'G_TYPE_IS_VALUE (src_type)' failed

(gtkpod:3280): Gtk-WARNING **: 20:14:43.209: 
../../../../gtk/gtkliststore.c:836: Unable to convert from (null) to gchararray

(gtkpod:3280): GLib-GObject-CRITICAL **: 20:14:43.290: 
g_value_type_transformable: assertion 'G_TYPE_IS_VALUE (src_type)' failed

(gtkpod:3280): Gtk-WARNING **: 20:14:43.290: 
../../../../gtk/gtkliststore.c:836: Unable to convert from (null) to gchararray
[New Thread 0x7fffcb57e700 (LWP 3290)]

Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault.
0x7652b57d in g_type_check_value_holds ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
(gdb) bt
#0  0x7652b57d in g_type_check_value_holds ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#1  0x75da5319 in  () at /usr/lib/x86_64-linux-gnu/libgpod.so.4
#2  0x75daa1f3 in itdb_parse ()
at /usr/lib/x86_64-linux-gnu/libgpod.so.4
#3  0x77d6268d in gp_import_itdb ()
at /usr/lib/x86_64-linux-gnu/libgtkpod.so.1
#4  0x77d63268 in gp_load_ipod ()
at /usr/lib/x86_64-linux-gnu/libgtkpod.so.1
#5  0x77d7b64f in  () at /usr/lib/x86_64-linux-gnu/libgtkpod.so.1
#6  0x76c790a0 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#7  0x7622bb73 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7622b0f5 in g_main_context_dispatch ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7622b4c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7622b7d2 in g_main_loop_run ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x77171e85 in gtk_main ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0xc833 in main ()


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.18.0-rc6+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages gtkpod depends on:
ii  gtkpod-data 2.1.5-6
ii  libanjuta-3-0   2:3.28.0-3
ii  libatk1.0-0 2.28.1-1
ii  libatomicparsley0   2.1.5-6
ii  libc6   2.27-5
ii  libcairo-gobject2   1.15.12-1
ii  libcairo2   1.15.12-1
ii  libclutter-1.0-01.26.2+dfsg-4
ii  libclutter-gtk-1.0-01.8.4-3
ii  libcogl-pango20 1.22.2-3
ii  libcogl-path20  1.22.2-3
ii  libcogl20   1.22.2-3
ii  libcurl3-gnutls 7.61.0-1
ii  libdrm2 2.4.94-1
ii  libegl1-mesa18.1.7-1
ii  libflac81.3.2-3
ii  libgbm1 18.1.3-1
ii  libgdk-pixbuf2.0-0  2.36.12-2
ii  libgdl-3-5  3.28.0-1
ii  libglib2.0-02.56.1-2
ii  libgpod40.8.3-12
ii  libgstreamer-plugins-base1.0-0  1.14.2-dmo2
ii  libgstreamer1.0-0   1.14.2-2
ii  libgtk-3-0  3.22.30-1
ii  libgtkpod1  2.1.5-6
ii  libid3tag0  0.15.1b-13
ii  libimobiledevice6   1.2.1~git20180302.3a37a4e-1
ii  libjson-glib-1.0-0  1.4.2-4
ii  libpango-1.0-0  1.42.0-1
ii  libpangocairo-1.0-0 1.42.0-1
ii  libplist3   2.0.0-4
ii  libvorbisfile3  1.3.6-1
ii  libwayland-client0  1.14.0-2
ii  libwayland-cursor0  1.14.0-2
ii  libwayland-egl1 [libwayland-egl1-mesa]  1.15.0-2
ii  libwayland-egl1-mesa18.1.7-1
ii  libwayland-server0

Bug#900045: mirrors: security.debian.org sometimes inaccessible via ipv6

[Peter Chubb]

Package: mirrors
Tags: ipv6

Dear Maintainer,

On ipv6 only machines, apt-get update sometimes fails, because
security.debian.org sometimes redirects to prod.debian.fastly.net
which has an advertised ipv6 address, but does not serve debian
packages from that address.

Peter C

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.17.0-rc6+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Bug#894412: caneda: Crashes with asseriton failure when simulating

[Peter Chubb]

Package: caneda
Version: 0.3.1-1
Severity: normal

Dear Maintainer,

I have ngspice installed, and tried to run an NGspice AC simulation from
10 kHz to 2Mhz.  Caneda crashes with an assertion failure:
ASSERT: "!isEmpty()" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, 
line 345

My circuit is here:









































































































































-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.16.0-rc4+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages caneda depends on:
ii  libc62.27-2
ii  libgcc1  1:8-20180321-1
ii  libqt5core5a 5.9.2+dfsg-12
ii  libqt5gui5   5.9.2+dfsg-12
ii  libqt5printsupport5  5.9.2+dfsg-12
ii  libqt5svg5   5.9.2-3
ii  libqt5widgets5   5.9.2+dfsg-12
ii  libqwt-qt5-6 6.1.3-1
ii  libstdc++6   8-20180321-1

caneda recommends no packages.

Versions of packages caneda suggests:
ii  ngspice  27-1

-- no debconf information

Bug#888711: fail2ban fails to start sshd-ddos filter.

[Peter Chubb]

Package: fail2ban
Version: 0.10.2-1
Severity: normal

Dear Maintainer,

After upgrading fail2ban, it no longer starts.
The error message is:

fail2ban Failed during configuration: Bad value substitution: 
option 'mode' in section 'Definition' contains an interpolation
 key 'ddos' which is not a valid option name. Raw value: '%(ddos)s'

The problem is in /etc/fail2ban/filter.d/sshd-ddos.conf

-- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'oldstable'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=en_AU:en 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages fail2ban depends on:
ii  lsb-base  9.20161125
ii  python3   3.6.4-1

Versions of packages fail2ban recommends:
ii  iptables   1.6.0+snapshot20161117-6
ii  python 2.7.13-2
pn  python3-pyinotify  
pn  python3-systemd
ii  whois  5.3.0

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20160123cvs-4
pn  monit
ii  rsyslog [system-log-daemon]  8.32.0-1
pn  sqlite3  

-- no debconf information

Bug#886892: evince: Prints n^2 copies if multiple copies selected

[Peter Chubb]

Package: evince
Version: 3.26.0-2
Severity: normal

Dear Maintainer,

On some PDF or PS documents, attempting to print more than 10 copies
results in n*n copies being printed instead.  The printer is a Kyocera
network-connected printer; cups says it's driverless.

I suspect that Evince is rewriting the printable file to say print n
times, and also asking CUPS to print n times.

Peter C

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.15.0-rc7+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-2
ii  evince-common3.26.0-2
ii  gsettings-desktop-schemas3.24.1-2
ii  libatk1.0-0  2.26.1-2
ii  libc62.26-1
ii  libcairo-gobject21.15.8-3
ii  libcairo21.15.8-3
ii  libevdocument3-4 3.26.0-2
ii  libevview3-3 3.26.0-2
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.2-5
ii  libgnome-desktop-3-123.26.2-4
ii  libgtk-3-0   3.22.26-2
ii  libnautilus-extension1a  3.26.2-1
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libsecret-1-00.18.5-5
ii  shared-mime-info 1.9-2

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.2-1
ii  dbus-x11 [dbus-session-bus]   1.12.2-1

Versions of packages evince suggests:
ii  gvfs 1.34.1-2
pn  nautilus-sendto  
ii  poppler-data 0.4.8-2
ii  unrar1:5.5.8-1

-- no debconf information

Bug#878826: libapache2-mod-python: Double free in mod_python

[Peter Chubb]

Package: libapache2-mod-python
Version: 3.3.1-11
Severity: important

Dear Maintainer,

 I upgraded from Jessie to Stretch; now my website doesn't work at all. Blank 
pages are returned.

/var/log/apache2/error.log shows:

*** Error in `/usr/sbin/apache2': double free or corruption (!prev): 0x8124f0c8 
***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xb754637a]
/lib/i386-linux-gnu/libc.so.6(+0x6dfb7)[0xb754cfb7]
/lib/i386-linux-gnu/libc.so.6(+0x6e7f6)[0xb754d7f6]
/usr/lib/python2.7/dist-packages/mod_python/_psp.so(+0x3053)[0xb590c053]
/usr/lib/python2.7/dist-packages/mod_python/_psp.so(+0x32ad)[0xb590c2ad]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7d96)[0xb68a57c6]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6667)[0xb68a4097]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x81e)[0xb69ca02e]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(+0x14cf3a)[0xb6946f3a]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x4d)[0xb68eb3fd]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(+0x1758f7)[0xb696f8f7]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x4d)[0xb68eb3fd]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_CallObjectWithKeywords+0x4c)[0xb69c940c]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyInstance_New+0x8b)[0xb697f72b]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x4d)[0xb68eb3fd]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x58a3)[0xb68a32d3]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6667)[0xb68a4097]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6667)[0xb68a4097]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6667)[0xb68a4097]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x81e)[0xb69ca02e]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x656f)[0xb68a3f9f]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x81e)[0xb69ca02e]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(+0x14ce55)[0xb6946e55]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x4d)[0xb68eb3fd]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(+0x1758f7)[0xb696f8f7]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x4d)[0xb68eb3fd]
/usr/lib/i386-linux-gnu/libpython2.7.so.1.0(PyObject_CallMethod+0xb4)[0xb68ec474]
/usr/lib/apache2/modules/mod_python.so(+0x13a4c)[0xb731ba4c]
/usr/sbin/apache2(ap_run_handler+0x47)[0x8011c567]
/usr/sbin/apache2(ap_invoke_handler+0xc7)[0x8011cae7]
/usr/sbin/apache2(ap_process_async_request+0x36f)[0x801342ff]
/usr/sbin/apache2(ap_process_request+0x1f)[0x801343ef]
/usr/sbin/apache2(+0x5c35c)[0x8013035c]
/usr/sbin/apache2(ap_run_process_connection+0x47)[0x80126317]
/usr/lib/apache2/modules/mod_mpm_prefork.so(+0x29c4)[0xb73b89c4]
/usr/lib/apache2/modules/mod_mpm_prefork.so(+0x2c0b)[0xb73b8c0b]
/usr/lib/apache2/modules/mod_mpm_prefork.so(+0x2c81)[0xb73b8c81]
/usr/lib/apache2/modules/mod_mpm_prefork.so(+0x3b97)[0xb73b9b97]
/usr/sbin/apache2(ap_run_mpm+0x4f)[0x800ff61f]
/usr/sbin/apache2(main+0x9c4)[0x800f8034]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xb74f7276]
/usr/sbin/apache2(+0x24166)[0x800f8166]
=== Memory map: 
800d4000-8016e000 r-xp  08:05 7111991/usr/sbin/apache2
8016f000-80171000 r--p 0009a000 08:05 7111991/usr/sbin/apache2
80171000-80173000 rw-p 0009c000 08:05 7111991/usr/sbin/apache2
80173000-80176000 rw-p  00:00 0 
80e85000-80ec1000 rw-p  00:00 0  [heap]
80ec1000-80f34000 rw-p  00:00 0  [heap]
80f34000-8126b000 rw-p  00:00 0  [heap]
b490-b4921000 rw-p  00:00 0 
b4921000-b4a0 ---p  00:00 0 
b4a4d000-b4a69000 r-xp  08:05 14163997   
/lib/i386-linux-gnu/libgcc_s.so.1
b4a69000-b4a6a000 r--p 0001b000 08:05 14163997   
/lib/i386-linux-gnu/libgcc_s.so.1
b4a6a000-b4a6b000 rw-p 0001c000 08:05 14163997   
/lib/i386-linux-gnu/libgcc_s.so.1
b4a74000-b4ab4000 rw-p  00:00 0 
b4ab4000-b4c9d000 r-xp  08:05 7184545
/usr/lib/i386-linux-gnu/libdb-5.3.so
b4c9d000-b4ca2000 r--p 001e8000 08:05 7184545
/usr/lib/i386-linux-gnu/libdb-5.3.so
b4ca2000-b4ca4000 rw-p 001ed000 08:05 7184545
/usr/lib/i386-linux-gnu/libdb-5.3.so
b4ca4000-b4cd r-xp  08:05 7192588
/usr/lib/python2.7/lib-dynload/_bsddb.i386-linux-gnu.so
b4cd-b4cd1000 r--p 0002b000 08:05 7192588
/usr/lib/python2.7/lib-dynload/_bsddb.i386-linux-gnu.so
b4cd1000-b4cd3000 rw-p 0002c000 08:05 7192588
/usr/lib/python2.7/lib-dynload/_bsddb.i386-linux-gnu.so
b4cd3000-b4d54000 rw-p  00:00 0 
b4d54000-b4de r-xp  08:05 7184437
/usr/lib/i386-linux-gnu/libgmp.so.10.3.2
b4de-b4de1000 r--p 0008b000 08:05 7184437
/usr/lib/i386-linux-gnu/libgmp.so.10.3.2
b4de1000-b4de2000 rw-p 0008c000 08:05 7184437
/usr/lib/i386-linux-gnu/libgmp.so.10.3.2
b4de2000-b4e16000 r-xp  08:05 7184559

Bug#873064: dovecot-imapd: Can't connect from older MacOSX and iOS devices to imap 993

[Peter Chubb]

Package: dovecot-imapd
Version: 1:2.2.31-1
Severity: normal

Dear Maintainer,

After upgrading dovecot, MacOSX El Capitan and IOS versions below 8 can 
no longer connect.  The error in the log is:
 SSL_accept() failed: error:1417D18C:SSL 
routines:tls_process_client_hello:version too low, session=...

How can I reenable TLSv1 ?  The obvious
ssl_protocols = TLSv1, TLSv1.1, TLSv1.2, !SSLv2, !SSLv4
doesn't work for me.

-- Package-specific info:

dovecot configuration
-
# 2.2.31 (65cde28): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.19 (e5c7051)
# OS: Linux 4.10.0-rc4+ x86_64 Debian buster/sid 
first_valid_uid = 130
mail_access_groups = mail
mail_location = mbox:~/Mail/:INBOX=/var/mail/%u:INDEX=/var/indices/%u
mail_privileged_group = mail
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  driver = pam
}
protocols = " imap"
ssl_cert = 

Versions of packages dovecot-imapd is related to:
ii  dovecot-core [dovecot-common]  1:2.2.31-1
pn  dovecot-dbg
pn  dovecot-dev
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.2.31-1
pn  dovecot-ldap   
pn  dovecot-lmtpd  
pn  dovecot-managesieved   
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
pn  dovecot-sieve  
pn  dovecot-sqlite 

-- no debconf information

Bug#873051: exim4: Exim dumps binary into logfile for DKIM i= field.

[Peter Chubb]

Package: exim4
Version: 4.89-5
Severity: normal

Dear Maintainer,

I'm seeing lines like this in /var/log/exim4/mainlog:

2017-08-23 10:43:51 1dkJlu-0002RD-3Z DKIM: d=reply.shoppingexpress.com.au 
s=key2 c=relaxed/relaxed a=rsa-sha256 b=1024 
i=<8C><99>T<<9D>^F^L
^Wx>4F^Z b=1024

When viewed in my MUA, the i= line is more sane:
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=key2; 
d=reply.shoppingexpress.com.au; 
h=To:Subject:From:MIME-Version:List-Id:List-Unsubscribe:Content-Type:Message-ID:Date;
 i=promot...@reply.shoppingexpress.com.au; 
bh=wRB+kyVA7TzcttnzAPNgRyPwu8OYE/zPGMY7ztfyo4s=; 
b=lGwQjIsqH+OXjC2IKD6+Ok7LtTnm8rU4BrZnQvqoCiybFnGY7SAUfzyddaUfb6rvJEHlBvb/19ur  
 wrlXjhtS9Vs0OUHYMBvvWtZjO2IRcg2o7C/UItzHETvUcKT/pFFbcSWVN+YppdcG2Y8njYaiw9pA   
z1bJrbqzr3O/2DawMQg=

I expect the i= line in the logs to be the same as the i= line in the
DKIM header.

-- Package-specific info:
Exim version 4.89 #2 built 10-Aug-2017 08:17:05
Copyright (c) University of Cambridge, 1995 - 2017
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2017
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM DNSSEC Event 
OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to replace
# the DEBCONFsomethingDEBCONF strings in the configuration template files.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='smarthost'
dc_other_hostnames='wombat.cf:numbat.tk:chubb.wattle.id.au:wombat:wombat.chubb.wattle.id.au:smtp.chubb.wattle.id.au:mail.chubb.wattle.id.au:mail:smtp'
dc_local_interfaces=''
dc_readhost='chubb.wattle.id.au'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets='192.168.77.0/24 ; 192.168.77.80/24 ; 2001:0388:d000::/48'
dc_smarthost='mx3.chubb.wattle.id.au::587'
#dc_smarthost='mail.optusnet.com.au'
CFILEMODE='644'
dc_use_split_config='true'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:wombat.chubb.wattle.id.au
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP /var/run/exim4/exim.pid
SMTPLISTENEROPTIONS='-oX 25:586:587 -oP /var/run/exim4/exim.pid'

-- System Information:
Debian Release: buster/sid
  APT prefers oldstable
  APT policy: (990, 'oldstable'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages exim4 depends on:
ii  debconf 1.5.63
ii  exim4-base  4.89-5
ii  exim4-daemon-light  4.89-5

exim4 recommends no packages.

exim4 suggests no packages.

-- debconf information:
  exim4/drec:

Bug#863756: libpam-modules: /etc/security/group.conf doesn't like groups with a dot in their names

[Peter Chubb]

Package: libpam-modules
Version: 1.1.3-7.1
Severity: normal

Dear Maintainer,
  We have a system where group names are derived from Active 
  Directory -- I have no control over their names.  Some have a full-stop
  in their names.

  pam_group.so parses a group with a full-stop in its name as two separate
  group names.

  So a line like:
 *;*;%Lab.All;Al-2400;www-data

 in /etc/security/group.conf generates lines like:

May 31 14:01:42 stage sshd[32597]: pam_group(sshd:setcred): bad group: Lab
May 31 14:01:42 stage sshd[32597]: pam_group(sshd:setcred): bad group: All

  in /var/log/auth.log


-- System Information:
Debian Release: 7.11
  APT prefers oldstable
  APT policy: (990, 'oldstable')
Architecture: ia64

Kernel: Linux 2.6.32-5-vserver-mckinley (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-modules depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6.12.13-38+deb7u10
ii  libdb5.1   5.1.29-5
ii  libpam-modules-bin 1.1.3-7.1
ii  libpam0g   1.1.3-7.1
ii  libselinux12.1.9-5

libpam-modules recommends no packages.

libpam-modules suggests no packages.

-- Configuration Files:
/etc/security/access.conf changed [not included]
/etc/security/group.conf changed [not included]
/etc/security/limits.conf changed [not included]

-- debconf information excluded

Bug#848205: ntpdc: can't talk to server

[Peter Chubb]

Package: ntp
Version: 1:4.2.8p9+dfsg-2
Severity: normal

Dear Maintainer,

 I do:
   ntpdc
   ntpdc> peers

   and ntpdc times out trying to talk to the server on localhost.
   Installing the ntp version from Jessie without changing
   /etc/ntp.conf fixes the problem.
   thus:
apt-get install -t jessie ntp/jessie

  ntpq works with both versions.

  ntpdc no longer quits on control-D either.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 3.10.101-0-pine64-longsleep (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ntp depends on:
ii  adduser3.115
ii  dpkg   1.18.15
ii  libc6  2.24-8
ii  libcap21:2.25-1
ii  libedit2   3.1-20160903-2
ii  libopts25  1:5.18.12-3
ii  libssl1.1  1.1.0c-2
ii  lsb-base   9.20161125
ii  netbase5.3

Versions of packages ntp recommends:
pn  perl:any  

Versions of packages ntp suggests:
pn  ntp-doc  

-- Configuration Files:
/etc/ntp.conf changed:
driftfile /var/lib/ntp/ntp.drift
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
pool pool.ntp.csiro.au
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
restrict 127.0.0.1
restrict ::1
restrict source notrap nomodify noquery


-- no debconf information

Bug#842443: abiword under XFCE4 displays all documents as black on black

[Peter Chubb]

Package: abiword
Version: 3.0.2-1
Severity: important

Dear Maintainer,

Every time I open a word document in ABIWord it displays as black on
black, and so is unreadable.  Clicking anywhere on the page briefly
shows the text, but only for a fraction of a second.

In the dialogs, the background for the pages is white, as I expect,
but it is displayed as black.

This makes abiword unusable for me.

Libreoffice correctly displays the same documents.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.9.0-rc2+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages abiword depends on:
ii  abiword-common  3.0.2-1
ii  gsfonts 1:8.11+urwcyr1.0.7~pre44-4.3
ii  libabiword-3.0  3.0.2-1
ii  libc6   2.24-5
ii  libdbus-1-3 1.10.12-1
ii  libdbus-glib-1-20.108-1
ii  libgcc1 1:6.2.0-9
ii  libgcrypt20 1.7.3-2
ii  libglib2.0-02.50.1-1
ii  libgnutls30 3.5.5-2
ii  libgoffice-0.10-10  0.10.32-1
ii  libgsf-1-1141.14.40-1
ii  libgtk-3-0  3.22.1-1
ii  libjpeg62-turbo 1:1.5.1-2
ii  libloudmouth1-0 1.5.3-2
ii  libots0 0.5.0-2.3
ii  libpng16-16 1.6.25-2
ii  librdf0 1.0.17-1+b1
ii  libreadline77.0-1
ii  librevenge-0.0-00.0.4-6
ii  libsoup2.4-12.56.0-1
ii  libstdc++6  6.2.0-9
ii  libtelepathy-glib0  0.24.1-1.1
ii  libtidy51:5.2.0-2
ii  libwmf0.2-7 0.2.8.4-10.5+b1
ii  libwpd-0.10-10  0.10.1-5
ii  libwpg-0.3-30.3.1-3
ii  libxml2 2.9.4+dfsg1-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages abiword recommends:
ii  abiword-plugin-grammar 3.0.2-1
ii  aspell-en [aspell-dictionary]  2016.06.26-0-0.1
ii  fonts-liberation   1:1.07.4-2
ii  poppler-utils  0.44.0-3

abiword suggests no packages.

-- no debconf information

Bug#841982: ssh: Allow StrictModes inside a Match User block

[Peter Chubb]

Package: ssh
Version: 1:6.7p1-5+deb8u3
Severity: wishlist

Dear Maintainer,

It'd be really nice to be able to turn StrictModes off in sshd_config only 
for particular users.  But currently, StrictModes is not permitted inside 
a Match User block.

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ssh depends on:
ii  dpkg1.17.27
ii  openssh-client  1:6.7p1-5+deb8u3
ii  openssh-server  1:6.7p1-5+deb8u3

ssh recommends no packages.

ssh suggests no packages.

-- no debconf information

Bug#841881: util-vserver: vserver-info faults with illegal instruction

[Peter Chubb]

Package: util-vserver
Version: 0.30.216-pre3054-1~bpo70+1
Severity: important

Dear Maintainer,
When trying to install util-vserver from wheezy-backports on Itanium/McKinley
the installation fails with an illegal instruction fault in vserver-info.

gdb vserver-info
(gdb) r
Starting program: /usr/sbin/vserver-info 
Versions:
   Kernel: 2.6.32-5-vserver-mckinley
   VS-API: 
Program received signal SIGILL, Illegal instruction.
0x40006512 in ?? ()
(gdb) bt
#0  0x40006512 in ?? ()
#1  0x40002a60 in ?? ()
#2  0x49d0 in ?? ()
#3  0x4c30 in ?? ()
#4  0x40001600 in ?? ()
#5  0x4510 in ?? ()
#6  0x40007f30 in ?? ()
#7  0x4800 in ?? ()
#8  0x40002a60 in ?? ()
#9  0x in ?? ()

-- System Information:
Debian Release: 7.11
  APT prefers oldstable
  APT policy: (990, 'oldstable')
Architecture: ia64

Kernel: Linux 2.6.32-5-vserver-mckinley (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages util-vserver depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  iproute20120521-3+b4
ii  libbeecrypt7   4.2.1-4
ii  libc6.12.13-38+deb7u10
ii  make   3.81-8.2
ii  net-tools  1.60-24.2
ii  util-linux 2.20.1-5.3

Versions of packages util-vserver recommends:
ii  binutils 2.22-8+deb7u2
ii  debootstrap  1.0.48+deb7u4
ii  python   2.7.3-4+deb7u1

Versions of packages util-vserver suggests:
pn  htop 
pn  iotop
ii  iptables 1.4.14-3.1
ii  linux-image-2.6.32-5-vserver-mckinley [linux-image-2.6]  2.6.32-48squeeze1
ii  module-init-tools9-3
ii  procps   1:3.3.3-3
ii  vlan 1.9-3
ii  wget 1.13.4-3+deb7u2
pn  yum  

-- Configuration Files:
/etc/init.d/util-vserver changed:
DEBIANCONFIG=/etc/default/util-vserver
if [ -f $DEBIANCONFIG ]
then
. $DEBIANCONFIG
fi
mkdir -p /var/run/vservers
mkdir -p /var/run/vservers.rev
mkdir -p /var/run/vshelper
: ${UTIL_VSERVER_VARS:=/usr/lib/util-vserver/util-vserver-vars}
test -e "$UTIL_VSERVER_VARS" || 
   {
echo "Can not find util-vserver installation (the file 
'$UTIL_VSERVER_VARS' is expected); aborting..." >&2
exit 1
   }
. "$UTIL_VSERVER_VARS"
PIDFILE=/var/run/rebootmgr.pid
LOCKFILE=$MARK
vprocunhide_lockfile=/var/run/vprocunhide
export MARK NUMPARALLEL LOCKFILE
TMPLEGACYTEST=$(find /etc/vservers/ -name "*.conf")
if [ -n "$TMPLEGACYTEST" ]
then
legacy=yes
fi
is_true() {
if [ "x$1" = "xtrue" -o "x$1" = "xyes" ] ; then
return 0
else
return 1
fi
}
sortserver(){
(
cd $__CONFDIR
for serv in *.conf
do
test -f "$serv" || continue
PRIORITY=100
. $serv
test "$ONBOOT" || continue
printf "%03d %s\n" $PRIORITY `basename $serv .conf`
done
) | sort $* | (while read a b; do echo $b; done)
}
startservers(){
cd $__CONFDIR
for name in `sortserver`
do
ONBOOT=
. $name.conf
if is_true "$ONBOOT" ; then
echo "Starting Linux-VServer guests..."
$_VSERVER_LEGACY $name start
else
echo "virtual server $name not configured for on boot 
start"
fi
done
}
start()
{
# First set vserver related attributes for /proc, this
# makes some necessary /proc entries visible in vservers
if [ -e /proc/self/vinfo ]
then
# Check for vc_set_iattr feature, if its not detected, then we are 
probably running a 
# 2.4 kernel where all of /proc is unhidden by default
$_VSERVER_INFO - FEATURE iattr
if [ $? -eq 0 ]
then
echo -n "Fixing visibility of /proc entries for Linux-VServer 
guests..."
$_VPROCUNHIDE
if [ $? -ne 0 ]
then
echo "Error in setting Linux-VServer related attributes 
for /proc"
else
touch "$vprocunhide_lockfile"
echo "done."
fi
fi
# Remove barrier on / if it exists
if [ -e /proc/self/vinfo ]
then
showattr -d / | awk '{print $1'} | grep -q B
if [ $? -eq 0 ]
then
setattr --~barrier /
fi
fi
# Then set the chroot barrier
for vserver in `ls 

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Peter Chubb]

Package: cups-daemon
Version: 2.2.1-1
Severity: important

Dear Maintainer,

Recently cupsd has started to use 100% CPU most of the time.
  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
20471 root  20   0  109684  31140   6232 R 100.0  0.2   9:49.86
  cupsd
  
stracing the process it looks as if it's continuously polling the
available printers.

All my (approx 50) printers are network connected via another CUPS
server (version 1.4.4) over which I have no control.

cups-browsed is installed, and has

  BrowseRemoteProtocols dnssd cups
  BrowsePoll remote-cups-server-address:631

in it.  All other settings are the defaults.

strace output -- this scrolls almost continuously:
write(6, "W [17/Oct/2016:08:32:26 +1100] C"..., 147) = 147
sendmsg(8, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="l\1\0\1\231\0\0\0005\3\0\0\235\0\0\0\1\1o\0\35\0\0\0/org/fre"...,
 iov_len=176}, {iov_base="\24\0\0\0blockhouse-p1-CMYK..\0\0\0\0\4\0\0\0"..., 
iov_len=153}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 329
poll([{fd=8, events=POLLIN}], 1, 5000)  = 1 ([{fd=8, revents=POLLIN}])
recvmsg(8, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="l\3\1\0015\0\0\0\30\f\0\0f\0\0\0\10\1g\0\1s\0\0\4\1s\0*\0\0\0"...,
 iov_len=2048}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_CMSG_CLOEXEC) = 173
recvmsg(8, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 20
connect(20, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = 0
sendto(20, "\2\0\0\0\2\0\0\0\4\0\0\0adm\0", 16, MSG_NOSIGNAL, NULL, 0) = 16
poll([{fd=20, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 1 ([{fd=20, 
revents=POLLIN|POLLHUP}])
read(20, "\2\0\0\0\1\0\0\0\4\0\0\0\2\0\0\0\4\0\0\0\0\0\0\0", 24) = 24
read(20, "adm\0x\0", 6) = 6
close(20)   = 0
write(6, "W [17/Oct/2016:08:32:26 +1100] C"..., 147) = 147
sendmsg(8, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="l\1\0\0010\1\0\0006\3\0\0\235\0\0\0\1\1o\0\35\0\0\0/org/fre"...,
 iov_len=176}, {iov_base="\22\0\0\0cups-blockhouse-p1\0\0\4\0\0\0temp"..., 
iov_len=304}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 480
poll([{fd=8, events=POLLIN}], 1, 5000)  = 1 ([{fd=8, revents=POLLIN}])
recvmsg(8, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="l\2\1\1=\0\0\0\35\f\0\0.\0\0\0\10\1g\0\1o\0\0\5\1u\0006\3\0\0"...,
 iov_len=2048}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_CMSG_CLOEXEC) = 125
recvmsg(8, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
open("/etc/cups/ppd/blockhouse-p1.ppd", O_RDONLY) = 20
fcntl(20, F_GETFD)  = 0
fcntl(20, F_SETFD, FD_CLOEXEC)  = 0
read(20, "*PPD-Adobe: \"4.3\"\n*FormatVersion"..., 4096) = 4096
read(20, "ole):  \"\"\n*KOPunch PK521+ZU606-4"..., 4096) = 4096
read(20, "unched false >> \n /KMOptions /Pr"..., 4096) = 4096
read(20, ") /KMMediaColor (None) /KMMediaW"..., 4096) = 4096
read(20, "setKMoptions get exec\"\n*End\n*Med"..., 4096) = 4096
read(20, "/FullBleed false >> /KMOptions /"..., 4096) = 4096
read(20, "deMode false /FullBleed false >>"..., 4096) = 4096
read(20, "rue >> /KMOptions /ProcSet findr"..., 4096) = 4096
read(20, "lfFold/Half-Fold:  \"<< /Collate "..., 4096) = 4096
read(20, ":  \"<< /Collate true >> setpaged"..., 4096) = 4096
read(20, "xec\"\n*AutoTrapping True/On:  \"<<"..., 4096) = 4096
read(20, "PickOne\n*OrderDependency: 10 Any"..., 4096) = 4096
read(20, "Moptions get exec\"\n*End\n*PageReg"..., 4096) = 4096
read(20, "FullBleed false >> /KMOptions /P"..., 4096) = 4096
read(20, " /WideMode true /FullBleed true "..., 4096) = 4096
read(20, "Area 8K/8K:  \"12 12 753 1093\"\n*I"..., 4096) = 4096
read(20, "ze EnvC4\n*UIConstraints: *InputS"..., 4096) = 4096
read(20, "nvChou3\n*UIConstraints: *InputSl"..., 4096) = 4096
read(20, "User4(2nd)\n*UIConstraints: *Inpu"..., 4096) = 4096
read(20, "MediaType Thick1(2nd) *Fold Half"..., 4096) = 4096
read(20, "Thick3(2nd) *Staple 1Staple(Left"..., 4096) = 4096
read(20, "ard\n*UIConstraints: *MediaType T"..., 4096) = 4096
read(20, "diaType Transparency *PageSize L"..., 4096) = 4096
read(20, "6_PostCard\n*UIConstraints: *Medi"..., 4096) = 4096
read(20, "nputSlot Tray2\n*UIConstraints: *"..., 4096) = 4096
read(20, "d) *Fold ZFold1\n*UIConstraints: "..., 4096) = 4096
read(20, "e 220mmx330mm *MediaType TAB\n*UI"..., 4096) = 4096
read(20, " *PageSize EnvISOB5 *Combination"..., 4096) = 4096
read(20, "vChou3 *Punch 4holes\n*UIConstrai"..., 4096) = 4096
read(20, "Size EnvKaku1 *Punch 2holes\n*UIC"..., 4096) = 4096
read(20, "Constraints: *PageSize Env10 *Of"..., 4096) = 4096
read(20, "ageSize A4Extra *Fold TriFold\n*U"..., 4096) = 4096
read(20, "diaType User2(2nd)\n*UIConstraint"..., 4096) = 4096
read(20, "1 *Fold Stitch\n*UIConstraints: *"..., 4096) = 4096
read(20, "raints: *Combination Booklet *Pa"..., 4096) = 4096
read(20, 

Bug#840694: gcc: /usr/bin/gcc should use /etc/alternatives

[Peter Chubb]

Package: gcc
Version: 4:6.1.1-1
Severity: wishlist

Dear Maintainer,

I currently have gcc versions 4.7, 5.0 and 6.0 installed.  I'd
like to be able to switch between them on a regular basis.  The
simplest way to do this would be to use update-alternatives to
switch, but currently /usr/bin/gcc and its friends
are direct symlinks to /usr/bin/gcc-6

By `friends' I mean cpp, c++, c89 c99 gcc-ar gcc-ranlib gcc-nm etc.

The same goes for the various cross compilers (arm-linux-gnueabi-gcc etc)


-- 
Dr Peter Chubb Tel: +61 2 9490 5852  http://ts.data61.csiro.au/
Trustworthy Systems Group   Data61 (formerly NICTA)

Bug#840374: binutils-arm-linux-gnueabi: ld.bfd segfaults when attempting to include binary blob

[Peter Chubb]

Package: binutils-arm-linux-gnueabi
Version: 2.27-8
Severity: normal

Dear Maintainer,
My build system uses LD with a linker script to include a binary blob
in an elf file.  arm-linux-gnueabi-ld.bfd segfaults, but
arm-linux-gnueabi-ld.gold works correctly.

To reproduce:
  dd if=/dev/zero of=blob bs=1k count=1

  cat  > linkscript.ld <

-- no debconf information

Bug#833205: libcrypto++6: Assertion fails in cmac.cpp line 60

[Peter Chubb]

Package: libcrypto++6
Version: 5.6.3-6
Severity: important
Tags: patch

Dear Maintainer,

The code in cmac.cpp CMAC_Base::Update() has an assertion that fails
if a zero-length section is passed into it.  Zero is meant to work:
there's a guard for zero length just after the assertion.


Swapping the assertion and the guard allows correct behaviour.

diff -u -r libcrypto++-5.6.3/cmac.cpp libcrypto++-5.6.3-local/cmac.cpp
--- libcrypto++-5.6.3/cmac.cpp  2015-11-14 00:04:22.0 +1100
+++ libcrypto++-5.6.3-local/cmac.cpp2016-08-02 10:49:51.659422114 +1000
@@ -57,9 +57,9 @@
 
 void CMAC_Base::Update(const byte *input, size_t length)
 {
-   assert((input && length) || !(input || length));
if (!length)
return;
+   assert((input && length) || !(input || length));
 
BlockCipher  = AccessCipher();
unsigned int blockSize = cipher.BlockSize();


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.7.0-rc6 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libcrypto++6 depends on:
ii  libc6   2.22-9
ii  libgcc1 1:6.1.1-3
ii  libstdc++6  6.1.1-3

libcrypto++6 recommends no packages.

libcrypto++6 suggests no packages.

-- no debconf information

Bug#803929: Seems fixed in 2.0.0-1

[Peter Chubb]

I'm not seeing the problem in the new version 2.0.0-1.

Peter C
-- 
Dr Peter Chubb Tel: +61 2 8306 0552  http://www.data61.csiro.au
http://www.ssrg.nicta.com.au   Software Systems Research Group/NICTA/Data61

Bug#803929: darktable: File export is broken

[Peter Chubb]

Package: darktable
Version: 1.6.9-1
Severity: normal

Dear Maintainer,

When I try to export a set of files, I see

[imageio_storage_disk] could not export to file: `/tmp/darktable/IMG_0001.jpg'!

The export file pattern is $(FILE_DIRECTORY)/darktable/IMG_$(SEQUENCE)



 


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.3.0-rc7+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages darktable depends on:
ii  gtk2-engines  1:2.20.2-3
ii  libatk1.0-0   2.18.0-1
ii  libc6 2.19-22
ii  libcairo2 1.14.2-2
ii  libcolord21.2.11-1
ii  libcurl3-gnutls   7.44.0-1
ii  libexiv2-14   0.25-2.1
ii  libflickcurl0 1.25-3
ii  libgcc1   1:5.2.1-16
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libgl1-mesa-glx [libgl1]  11.0.4-1
ii  libglib2.0-0  2.46.1-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgomp1  5.2.1-16
ii  libgphoto2-6  2.5.8-3
ii  libgphoto2-port12 2.5.8-3
ii  libgtk2.0-0   2.24.28-1
ii  libice6   2:1.0.9-1+b1
ii  libilmbase6v5 1.0.1-6.2
ii  libjpeg62-turbo   1:1.4.1-2
ii  libjs-prototype   1.7.1-3
ii  libjs-scriptaculous   1.9.0-2
ii  libjson-glib-1.0-01.0.4-2
ii  liblcms2-22.6-3+b3
ii  liblensfun0   0.2.8-2
ii  liblua5.2-0   5.2.4-1
ii  libopenexr6v5 1.6.1-8.1+b2
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpng12-01.2.50-2+b2
ii  librsvg2-22.40.11-1
ii  libsdl1.2debian   1.2.15-11
ii  libsm62:1.2.2-1+b1
ii  libsoup2.4-1  2.52.1-1
ii  libsqlite3-0  3.9.1-2
ii  libstdc++65.2.1-16
ii  libtiff5  4.0.5-1
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.2+zdfsg1-4
ii  libxrandr22:1.5.0-1
ii  zlib1g1:1.2.8.dfsg-2+b1

darktable recommends no packages.

darktable suggests no packages.

-- no debconf information

Bug#803929: darktable: File export is broken

[Peter Chubb]

>>>>> "Roman" == Roman Lebedev <lebedev...@gmail.com> writes:

Roman> On Tue, Nov 3, 2015 at 1:13 PM, Peter Chubb
Roman> <peter.ch...@nicta.com.au> wrote:
>> Package: darktable Version: 1.6.9-1 Severity: normal
>> 
>> Dear Maintainer,
>> 
>> When I try to export a set of files, I see
>> 
>> [imageio_storage_disk] could not export to file:
>> `/tmp/darktable/IMG_0001.jpg'!
Roman> This looks like a Debian BTS#792209

It does, but that was meant to have been fixed before the version I'm
using.


>> The export file pattern is
>> $(FILE_DIRECTORY)/darktable/IMG_$(SEQUENCE)
Roman> I would think it means that you do not have necessary
Roman> permissions for /tmp/darktable directory.  And that would also
Roman> mean that you did not provide all the nessesary output, in
Roman> particular there should have been following line just above:
Roman> [imageio_storage_disk] could not write to directory:
Roman> `/tmp/darktable'

That line does not appear.

s = ?5, exposure = ?6, aperture = ?7, iso = ?8, focal_length = ?9, 
focus_distance = ?10, film_id = ?11, datetime_taken = ?12, flags = ?13, crop = 
?14, orientation = ?15, raw_parameters = ?16, group_id = ?17, longitude = ?18, 
latitude = ?19, color_matrix = ?20, colorspace = ?21, raw_black = ?22, 
raw_maximum = ?23 WHERE id = ?24"
[sql] prepare "select imgid, formid, form, name, version, points, points_count, 
source from mask where imgid = ?1"
[sql] prepare "select imgid, num, module, operation, op_params, enabled, 
blendop_params, blendop_version, multi_priority, multi_name from history where 
imgid = ?1 order by num"
[sql] prepare "SELECT id FROM styles WHERE name=?1 ORDER BY id DESC LIMIT 1"
[imageio_storage_disk] could not export to file: `/tmp/IMG_0001.jpg'!


If I strace the program, the last few lines are

4354  write(1, "[sql] prepare \"select imgid, num"..., 177) = 177
4354  getrusage(RUSAGE_SELF, {ru_utime={13, 69950}, ru_stime={0, 852577}, ...}) 
= 0
4354  mmap(NULL, 96260096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0x7f2c82f18000
4354  mmap(NULL, 96260096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0x7f2c7d34b000
4354  write(1, "[sql] prepare \"SELECT id FROM st"..., 77) = 77
4354  write(6, "\1\0\0\0\0\0\0\0", 8 
4352  <... poll resumed> )  = 1 ([{fd=6, revents=POLLIN}])
4354  <... write resumed> ) = 8
4352  recvmsg(5, 0x7ffe490e51e0, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
4354  write(2, "[imageio_storage_disk] could not"..., 70) = 70


This is *not* a permissions problem, as far as I can tell.  In this
run, I removed darktable from the export path, so it's trying to
create /tmp/IMG_0001.jpg

/tmp is globally writable, and the file does not yet exist there.

Peter C
-- 
Dr Peter Chubb   http://www.data61.csiro.au
http://www.ssrg.nicta.com.au   Software Systems Research Group/NICTA/Data61

Bug#803929: darktable: File export is broken

[Peter Chubb]

> "Roman" == Roman Lebedev  writes:
Roman> Please run dt without any  -d ???  command line arguments like this:
Roman> $ darktable
Roman> And paste ALL the output, without cutting out anything, starting with
Roman> $ darktable.

Just Darktable on its own imports no files.
I generally give it some jpegs to work on.

Here's the total output, including the command line.

peterc@Diprotodon:/media/peterc/AAD7-4CE2/DCIM/100_1001$ darktable *
[imageio_storage_disk] could not export to file: `/tmp/IMG_0001.jpg'!

Peter C

Bug#793172: pavucontrol spams console with GLib-GObhect-WARNING messages

[Peter Chubb]

Package: pavucontrol
Version: 3.0-3
Severity: minor

Dear Maintainer,

When I do
 pavucontrol 
I see:
(pavucontrol:15877): GLib-GObject-WARNING **: The property GtkMisc:xpad is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(pavucontrol:15877): GLib-GObject-WARNING **: The property GtkMisc:ypad is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(pavucontrol:15877): GLib-GObject-WARNING **: The property 
GtkAlignment:bottom-padding is deprecated and shouldn't be used anymore. It 
will be removed in a future version.

(pavucontrol:15877): GLib-GObject-WARNING **: The property 
GtkAlignment:left-padding is deprecated and shouldn't be used anymore. It will 
be removed in a future version.

(pavucontrol:15877): GLib-GObject-WARNING **: The property 
GtkAlignment:right-padding is deprecated and shouldn't be used anymore. It will 
be removed in a future version.

(pavucontrol:15877): GLib-GObject-WARNING **: The property 
GtkContainer:resize-mode is deprecated and shouldn't be used anymore. It will 
be removed in a future version.

(pavucontrol:15877): GLib-GObject-WARNING **: The property GtkImage:stock is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(pavucontrol:15877): GLib-GObject-WARNING **: The property GtkButton:xalign is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.1.0-rc8+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages pavucontrol depends on:
ii  libatk1.0-0  2.16.0-2
ii  libatkmm-1.6-1   2.22.7-2.1
ii  libc62.19-19
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libcairomm-1.0-1 1.10.0-1.1
ii  libcanberra-gtk3-0   0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libgcc1  1:5.1.1-14
ii  libgdk-pixbuf2.0-0   2.31.4-2
ii  libglib2.0-0 2.44.1-1.1
ii  libglibmm-2.4-1c2a   2.44.0-1
ii  libgtk-3-0   3.16.5-1
ii  libgtkmm-3.0-1   3.16.0-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangomm-1.4-1 2.36.0-1
ii  libpulse-mainloop-glib0  6.0-2
ii  libpulse06.0-2
ii  libsigc++-2.0-0c2a   2.4.1-1
ii  libstdc++6   5.1.1-14
ii  libx11-6 2:1.6.3-1

Versions of packages pavucontrol recommends:
ii  pulseaudio  6.0-2

pavucontrol suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#787048: libapache2-mod-gnutls missing from Jessie

[Peter Chubb]

Package: libapache2-mod-gnutls
Version: 0.5.10-1.1+deb7u1
Severity: important

Dear Maintainer,



The version of this module I have installed is from oldstable, and is
not compatible with the Apache2 binary in Jessie -- it suffers from
bug #710986

Can a newer version be made available in the Jessie distribution, please?
-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: unable to detect

Versions of packages libapache2-mod-gnutls depends on:
ii  libapr-memcache0  0.7.0-3
ii  libc6 2.19-18
ii  libgnutls26   2.12.20-8+deb7u3

libapache2-mod-gnutls recommends no packages.

libapache2-mod-gnutls suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#774673: xfig crashes with stack smash detected when attempting to change arrow size

[Peter Chubb]

Package: xfig
Version: 1:3.2.5.c-3+b1
Severity: normal

Dear Maintainer,

Start xfig from a terminal, then select the `arrow' tool, then attempt to
change arrow characteristics by clicking on the `thickness' button.

I see in the terminal:
$ xfig
*** stack smashing detected ***: xfig terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7303f)[0x7ff37e6d303f]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7ff37e756147]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7ff37e756110]
xfig(+0xabd31)[0x7ff37fe81d31]
xfig(+0xb1481)[0x7ff37fe87481]
/usr/lib/x86_64-linux-gnu/libXt.so.6(XtDispatchEventToWidget+0x484)[0x7ff37f06f174]
/usr/lib/x86_64-linux-gnu/libXt.so.6(+0x2287d)[0x7ff37f06f87d]
/usr/lib/x86_64-linux-gnu/libXt.so.6(XtDispatchEvent+0xc9)[0x7ff37f06f959]
xfig(+0x1de38)[0x7ff37fdf3e38]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7ff37e681b45]
xfig(+0x1e1bc)[0x7ff37fdf41bc]
=== Memory map: 
7ff37c99-7ff37c9a6000 r-xp  08:04 2226197268 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ff37c9a6000-7ff37cba5000 ---p 00016000 08:04 2226197268 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ff37cba5000-7ff37cba6000 rw-p 00015000 08:04 2226197268 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ff37cba6000-7ff37cbab000 r-xp  08:04 151697559  
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7ff37cbab000-7ff37cdaa000 ---p 5000 08:04 151697559  
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7ff37cdaa000-7ff37cdab000 r--p 4000 08:04 151697559  
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7ff37cdab000-7ff37cdac000 rw-p 5000 08:04 151697559  
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7ff37cdac000-7ff37cdb5000 r-xp  08:04 150835319  
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7ff37cdb5000-7ff37cfb4000 ---p 9000 08:04 150835319  
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7ff37cfb4000-7ff37cfb5000 r--p 8000 08:04 150835319  
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7ff37cfb5000-7ff37cfb6000 rw-p 9000 08:04 150835319  
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7ff37cfb6000-7ff37cfc r-xp  08:04 150835322  
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7ff37cfc-7ff37d1bf000 ---p a000 08:04 150835322  
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7ff37d1bf000-7ff37d1c r--p 9000 08:04 150835322  
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7ff37d1c-7ff37d1c1000 rw-p a000 08:04 150835322  
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7ff37d1c1000-7ff37d1c6000 r-xp  08:04 149510812  
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7ff37d1c6000-7ff37d3c5000 ---p 5000 08:04 149510812  
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7ff37d3c5000-7ff37d3c6000 rw-p 4000 08:04 149510812  
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7ff37d3c6000-7ff37d3c9000 r-xp  08:04 152719354  
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7ff37d3c9000-7ff37d5c8000 ---p 3000 08:04 152719354  
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7ff37d5c8000-7ff37d5c9000 r--p 2000 08:04 152719354  
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7ff37d5c9000-7ff37d5ca000 rw-p 3000 08:04 152719354  
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7ff37d5ca000-7ff37d5ce000 r-xp  08:04 2305127154 
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7ff37d5ce000-7ff37d7cd000 ---p 4000 08:04 2305127154 
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7ff37d7cd000-7ff37d7ce000 r--p 3000 08:04 2305127154 
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7ff37d7ce000-7ff37d7cf000 rw-p 4000 08:04 2305127154 
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7ff37d7cf000-7ff37d7d2000 r-xp  08:04 2253906567 
/lib/x86_64-linux-gnu/libdl-2.19.so
7ff37d7d2000-7ff37d9d1000 ---p 3000 08:04 2253906567 
/lib/x86_64-linux-gnu/libdl-2.19.so
7ff37d9d1000-7ff37d9d2000 r--p 2000 08:04 2253906567 
/lib/x86_64-linux-gnu/libdl-2.19.so
7ff37d9d2000-7ff37d9d3000 rw-p 3000 08:04 2253906567 
/lib/x86_64-linux-gnu/libdl-2.19.so
7ff37d9d3000-7ff37d9f4000 r-xp  08:04 149130112  
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0
7ff37d9f4000-7ff37dbf3000 ---p 00021000 08:04 149130112  
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0
7ff37dbf3000-7ff37dbf4000 r--p 0002 08:04 149130112  
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0
7ff37dbf4000-7ff37dbf5000 rw-p 00021000 08:04 149130112  
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0
7ff37dbf5000-7ff37dc06000 r-xp  08:04 154789414  

Bug#768910: Missed one timer arg

[Peter Chubb]

If wl-biff-use-idle-timer is non-nil, there's another place that needs
to be switched from a bool to an integer.

Updated patch attached.

--- wl-beta-2.15.9+0.20141019/wl/wl-util.el 2014-10-19 19:07:15.0 
+1100
+++ wl-beta-fixed/wl/wl-util.el 2014-11-11 08:52:13.764418131 +1100
@@ -774,11 +774,11 @@
   (if wl-biff-use-idle-timer
  (if (get 'wl-biff 'timer)
  (progn (timer-set-idle-time (get 'wl-biff 'timer)
- wl-biff-check-interval t)
+ wl-biff-check-interval 
wl-biff-check-interval)
 (timer-activate-when-idle (get 'wl-biff 'timer)))
(put 'wl-biff 'timer
 (run-with-idle-timer
- wl-biff-check-interval t 'wl-biff-event-handler)))
+ wl-biff-check-interval wl-biff-check-interval 
'wl-biff-event-handler)))
(if (get 'wl-biff 'timer)
(progn
  (timer-set-time (get 'wl-biff 'timer)

-- 
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768910: wl-beta: Error running Timer message with emacs24

[Peter Chubb]

Package: wl-beta
Version: 2.15.9+0.20141019-2
Severity: normal
Tags: patch


Dear Maintainer,
 I keep seeing timer errors from wl-biff:
 
 Error running timer `wl-biff-event-handler':
(wrong-type-argument number-or-marker-p t)

This is because t is passed to timer-set-idle-time instead of a number
of seconds.

Here is a patch to fix it:

--- wl-beta-2.15.9+0.20141019/wl/wl-util.el 2014-10-19 19:07:15.0 
+1100
+++ wl-beta-fixed/wl/wl-util.el 2014-11-10 13:26:54.162330803 +1100
@@ -774,7 +774,7 @@
   (if wl-biff-use-idle-timer
  (if (get 'wl-biff 'timer)
  (progn (timer-set-idle-time (get 'wl-biff 'timer)
- wl-biff-check-interval t)
+ wl-biff-check-interval 
wl-biff-check-interval)
 (timer-activate-when-idle (get 'wl-biff 'timer)))
(put 'wl-biff 'timer
 (run-with-idle-timer


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf
armel

Kernel: Linux 3.18.0-rc2+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wl-beta depends on:
ii  apel   10.8+0.20120427-13
ii  dpkg   1.17.21
ii  emacs24 [emacsen]  24.4+1-4
ii  emacsen-common 2.0.8
ii  flim   1:1.14.9+0.20120428-9
ii  install-info   5.2.0.dfsg.1-5
ii  semi   1.14.7~0.20120428-14

wl-beta recommends no packages.

Versions of packages wl-beta suggests:
ii  bbdb  2.36-4
pn  bitmap-mule   none
ii  bogofilter1.2.4+dfsg1-3
pn  easypgnone
ii  gnupg 1.4.18-4
ii  gnutls-bin3.3.8-3
pn  imnone
pn  maildir-utils none
pn  mhc   none
pn  mu-cite   none
pn  mule-ucs  none
pn  namazu2   none
pn  notmuch   none
ii  openssl   1.0.1j-1
pn  starttls  none
ii  w3m-el-snapshot [w3m-el]  1.4.538+0.20141022-1
pn  x-face-el none

-- no debconf information

-- 
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767994: cross-gcc-4.9-armhf: Will not build arm-linux-gnueabihf-4.9.

[Peter Chubb]

 Wookey == Wookey  woo...@wookware.org writes:

Wookey What version of gcc-4.9-source do you have installed. This
Wookey dependency is not versionned in the current package and
Wookey clearly should be as it needs 4.9.1-19 due to incompatible
Wookey changes vs. previous 4.9.1 versions. I've fixed that in local
Wookey git.

dpkg -l gcc-4.9-source
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  gcc-4.9-source 4.9.1-19 all  Source of the GNU Compiler Collec

I tried sanitising my environment before compiling, with
  env PATH=/bin:/usr/bin debuild -b

I get the same error as before.

In the end, just to get things to compile to completion, I did
 cd /usr/src
 sudo ln -s . debug


--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767994: cross-gcc-4.9-armhf: Will not build arm-linux-gnueabihf-4.9.

[Peter Chubb]

Source: cross-gcc-4.9-armhf
Version: 0.8
Severity: important

Dear Maintainer,

I do:
  apt-get build-deb cross-gcc-4.9-armhf
  cd cross-gcc-4.9-armhf
  echo armel armhf  debian/targetlist
  debuild -b

I expect to get gcc packages to install.

I actually get:
  ... lots of make output suppressed ...
  
  make[10]: Entering directory 
'/usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/arm-linux-gnueabihf/libstdc++-v3/src/debug'
/bin/sh ../../libtool --tag CXX   --mode=compile 
/usr/src/debug/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/./gcc/xgcc 
-shared-libgcc -B/usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/./gcc 
-nostdinc++ 
-L/usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/arm-linux-gnueabihf/libstdc++-v3/src
 
-L/usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/arm-linux-gnueabihf/libstdc++-v3/src/.libs
 
-L/usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/arm-linux-gnueabihf/libstdc++-v3/libsupc++/.libs
 -B/usr/arm-linux-gnueabihf/bin/ -B/usr/arm-linux-gnueabihf/lib/ -isystem 
/usr/arm-linux-gnueabihf/include -isystem /usr/arm-linux-gnueabihf/sys-include 
-isystem /usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/sys-include 
-I/usr/src/debug/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/arm-linux-gnueabihf/libstdc++-v3/include/arm-linux-gnueabihf
 
-I/usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/build/arm-linux-gnueabihf/libstdc++-v3/include
 -I/usr/src/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/src/libstdc++-v3/libsupc++  -fPIC 
-D
 PIC -fno-implicit-templates  -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi  
-fdiagnostics-show-location=once   -ffunction-sections -fdata-sections  
-frandom-seed=compatibility.lo -gdwarf-4 -g3 -O0  -c -o compatibility.lo 
../../../../../src/libstdc++-v3/src/c++98/compatibility.cc

make[10]: *** No rule to make target 
'/usr/src/debug/cross-gcc-4.9-armhf-0.8/gcc-4.9.1/src/libstdc++-v3/config/abi/pre/gnu.ver',
 needed by 'libstdc++-symbols.ver'.  Stop.


Where does that /usr/src/debug come from ?

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf
armel

Kernel: Linux 3.18.0-rc2+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765537: chromium: Silent change: java plugin no longer works

[Peter Chubb]

Package: chromium
Version: 38.0.2125.101-2
Severity: important
Tags: upstream

Dear Maintainer,

 After a routine apt-get upgrade, chromium java support stopped.
 There was no changelog entry to suggest this would happen --
 apparently upstream has removed support for the NPAPI that the
 java plugin uses.

 I'd appreciate at least a changelog entry, or a warning or
 something, so that I could avoid upgrading chromium beyond
 version 37.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf

Kernel: Linux 3.16.0 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libc62.19-11
ii  libcairo21.12.16-5
ii  libcap2  1:2.24-6
ii  libcups2 1.7.5-4
ii  libdbus-1-3  1.8.8-2
ii  libexpat12.1.0-6
ii  libfontconfig1   2.11.0-6.1
ii  libfreetype6 2.5.2-2
ii  libgdk-pixbuf2.0-0   2.31.1-2
ii  libglib2.0-0 2.42.0-2
ii  libgnome-keyring03.12.0-1
ii  libgtk2.0-0  2.24.25-1
ii  libharfbuzz0b0.9.35-1
ii  libjpeg8 8d1-2
ii  libnspr4 2:4.10.7-1
ii  libnspr4-0d  2:4.10.7-1
ii  libnss3  2:3.17.1-1
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-6
ii  libspeex11.2~rc1.2-1
ii  libsrtp0 1.4.5~20130609~dfsg-1.1
ii  libstdc++6   4.9.1-16
ii  libudev1 215-5+b1
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1
ii  libxdamage1  1:1.1.4-2
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2
ii  libxi6   2:1.7.4-1
ii  libxml2  2.9.1+dfsg1-4
ii  libxrandr2   2:1.4.2-1
ii  libxrender1  1:0.9.8-1
ii  libxslt1.1   1.1.28-2+b1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1
ii  xdg-utils1.1.0~rc1+git20111210-7.1

chromium recommends no packages.

Versions of packages chromium suggests:
ii  chromium-inspector  38.0.2125.101-2
pn  chromium-l10n   none

-- Configuration Files:
/etc/chromium/default changed:
CHROMIUM_FLAGS=--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so


-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#756572: Forgot to say...

[Peter Chubb]

The open files are all for https over ipv6 connections.  Netstat shows
them in state FIN_WAIT2.

--
Dr Peter Chubb  peter DOT chubb AT nicta.com.au
http://www.ssrg.nicta.com.au Software Systems Research at NICTA
A university is a non-profit organisation only in the sense that it
spends everything it gets  ... Luca Turin.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#756572: Found the issue

[Peter Chubb]

I've finally caught polipo while it's still alive.  It has 1022 open
sockets in state FIN_WAIT2 from itself to various ipv6 clients.

This could be a kernel isssue then... there doesn't seem to be a
fin_wait timeout parameter for ipv6 in the kernel.

--
Dr Peter Chubb  peter DOT chubb AT nicta.com.au
http://www.ssrg.nicta.com.au Software Systems Research at NICTA
A university is a non-profit organisation only in the sense that it
spends everything it gets  ... Luca Turin.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757538: Patch to add do-othing -a

[Peter Chubb]

 Tags: PATCH

 The attafhed patch adds a do-nothing -a option.  As fsck.f2fs always
 tries automatically to fix problems.

---
 fsck/main.c |5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

Index: f2fs-tools-1.3.0/fsck/main.c
===
--- f2fs-tools-1.3.0.orig/fsck/main.c   2014-09-04 11:16:04.281639599 +1000
+++ f2fs-tools-1.3.0/fsck/main.c2014-09-04 11:17:11.306108542 +1000
@@ -20,6 +20,7 @@ void fsck_usage()
MSG(0, \nUsage: fsck.f2fs [options] device\n);
MSG(0, [options]:\n);
MSG(0,   -d debug level [default:0]\n);
+MSG(0,   -a [no-op for compatibility with other fsck]\n);
exit(1);
 }
 
@@ -42,11 +43,13 @@ void f2fs_parse_options(int argc, char *
char *prog = basename(argv[0]);
 
if (!strcmp(fsck.f2fs, prog)) {
-   const char *option_string = d:t;
+   const char *option_string = d:ta;
 
config.func = FSCK;
while ((option = getopt(argc, argv, option_string)) != EOF) {
switch (option) {
+case 'a':
+break;
case 'd':
config.dbg_lv = atoi(optarg);
MSG(0, Info: Debug level = %d\n, 
config.dbg_lv);

-- 
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA

Bug#759611: android-tools-fastboot: fastboot fails to detect device over USB3.0

[Peter Chubb]

Package: android-tools-fastboot
Version: 4.2.2+git20130529-3
Severity: normal

Dear Maintainer,

I'm trying to use fastboot with an Odroid XU3, that has a USB3.0 OTG
port.  If I connect to a USB3.0 host port, I see from u-boot on the
Odroid's serial console:
 USB cable Connected![CH-1]
 Super speed enumeration success   

but fastboot hangs
 fastboot flash bootloader u-boot.bin
  waiting for device 

It all works properly if I plug into a USB2.0 port.

lsusb -v gives on the USB3.0 port:
Bus 002 Device 010: ID 18d1:0002 Google Inc. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 9
  idVendor   0x18d1 Google Inc.
  idProduct  0x0002 
  bcdDevice   ff.ff
  iManufacturer   2 (error)
  iProduct3 (error)
  iSerial 4 (error)
  bNumConfigurations  1
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   79
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xc0
  Self Powered
MaxPower  126mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface  1 (error)
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst  15
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst  15
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass 66 
  bInterfaceProtocol  1 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03  EP 3 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
Device Status: 0x0001
  Self Powered


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf

Kernel: Linux 3.16.0 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages android-tools-fastboot depends on:
ii  libc62.19-10
ii  libselinux1  2.3-1
ii  zlib1g   1:1.2.8.dfsg-2

android-tools-fastboot recommends no packages.

android-tools-fastboot suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759611: [PATCH] Skip endpoint superspeed companion descriptors

[Peter Chubb]

The problem is that USB3 can add a `superspeed' companion descriptor
to each endpoint.  This patch skips over such descriptors in adb and
fastboot.

Signed-off-by: Peter Chubb peter.ch...@nicta.com.au

diff -ur android-tools-4.2.2+git20130529/core/adb/usb_linux.c 
android-tools-local/core/adb/usb_linux.c
--- android-tools-4.2.2+git20130529/core/adb/usb_linux.c2013-05-30 
06:16:54.0 +1000
+++ android-tools-local/core/adb/usb_linux.c2014-08-29 13:57:08.063089767 
+1000
@@ -137,6 +137,7 @@
 DIR *busdir , *devdir ;
 struct dirent *de;
 int fd ;
+int is_usb3;
 
 busdir = opendir(base);
 if(busdir == 0) return;
@@ -195,6 +196,7 @@
 vid = device-idVendor;
 pid = device-idProduct;
 DBGX([ %s is V:%04x P:%04x ]\n, devname, vid, pid);
+is_usb3 = device-bcdUSB == 0x0300;
 
 // should have config descriptor next
 config = (struct usb_config_descriptor *)bufptr;
@@ -237,8 +239,12 @@
 // looks like ADB...
 ep1 = (struct usb_endpoint_descriptor *)bufptr;
 bufptr += USB_DT_ENDPOINT_SIZE;
+if (is_usb3  bufptr[1] == USB_DT_SS_ENDPOINT_COMP)
+bufptr += USB_DT_SS_EP_COMP_SIZE;
 ep2 = (struct usb_endpoint_descriptor *)bufptr;
 bufptr += USB_DT_ENDPOINT_SIZE;
+if (is_usb3  bufptr[1] == USB_DT_SS_ENDPOINT_COMP)
+bufptr += USB_DT_SS_EP_COMP_SIZE;
 
 if (bufptr  devdesc + desclength ||
 ep1-bLength != USB_DT_ENDPOINT_SIZE ||
diff -ur android-tools-4.2.2+git20130529/core/fastboot/usb_linux.c 
android-tools-local/core/fastboot/usb_linux.c
--- android-tools-4.2.2+git20130529/core/fastboot/usb_linux.c   2013-05-30 
06:16:54.0 +1000
+++ android-tools-local/core/fastboot/usb_linux.c   2014-08-29 
14:03:41.189491186 +1000
@@ -217,6 +217,11 @@
 len -= ept-bLength;
 ptr += ept-bLength;
 
+if (check(ptr, len, USB_DT_SS_ENDPOINT_COMP, 
USB_DT_SS_EP_COMP_SIZE ) == 0) {
+len -= USB_DT_SS_EP_COMP_SIZE;
+ptr += USB_DT_SS_EP_COMP_SIZE;
+}
+
 if((ept-bmAttributes  0x03) != 0x02)
 continue;
 

-- 
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757748: openocd: Flyswatter config file out of date

[Peter Chubb]

Package: openocd
Version: 0.8.0-1
Severity: normal

Dear Maintainer,

When I try to use openocd with a flyswatter from tin-can-tools, I see:
Error: The specified debug interface was not found (ft2232)
The following debug interfaces are available:
1: parport
2: dummy
3: ftdi
4: usb_blaster
5: amt_jtagaccel
...

I believe that /usr/share/openocd/scripts/interface/flyswatter.cfg
needs to be updated to use the ftdi interface, instead of the ft2332
interface which no longer exists.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf

Kernel: Linux 3.15.0-rc3 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openocd depends on:
ii  libc6  2.19-7
ii  libhidapi-hidraw0  0.8.0~rc1+git20140201.3a66d4e+dfsg-3
ii  libusb-0.1-4   2:0.1.12-24
ii  libusb-1.0-0   2:1.0.19-1

openocd recommends no packages.

openocd suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757538: f2fs-tools: fsck.f2fs doesn't understand -a

[Peter Chubb]

Package: f2fs-tools
Version: 1.3.0-1
Severity: normal

Dear Maintainer,

If you have an f2fs partition that is to be mounted at boot, the init
scripts call fsck.f2fs -a on it.  But fsck.f2fs doesn't understand -a

fsck.f2fs also doesn't have a man page (separate issue) so I don't
know what options it *does* support.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages f2fs-tools depends on:
ii  libc6 2.19-3
ii  libuuid1  2.24.1-1

f2fs-tools recommends no packages.

f2fs-tools suggests no packages.

-- no debconf information

--


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#756724: cups-browsed: Can't see remote printers in print dialogs

[Peter Chubb]

Package: cups-browsed
Version: 1.0.55-1
Severity: normal

Dear Maintainer,

Since updating to 1.0.55-1 I no longer see remote printers in print
dialogs.

cups-browsed --debug reports

cups-browsed: browsed queue name is vrl-lvl1-p1
cups-browsed: Found CUPS queue: vrl-lvl1-p1 on host PRINT_SERVER_IP
cups-browsed: Remote CUPS queue vrl-lvl1-p1 on host PRITN_SERVER_IP is raw, 
ignored.

If I downgrade to Jessie's cups-browsed (1.0.54-3.b1) everything works
as expected.

The print server is running cups version 1.4.4

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf

Kernel: Linux 3.15.0-rc3 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cups-browsed depends on:
ii  init-system-helpers  1.20
ii  libavahi-client3 0.6.31-4
ii  libavahi-common3 0.6.31-4
ii  libavahi-glib1   0.6.31-4
ii  libc62.19-7
ii  libcups2 1.7.4-4
ii  libglib2.0-0 2.40.0-3

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.6.31-4

cups-browsed suggests no packages.

-- Configuration Files:
/etc/cups/cups-browsed.conf changed:
BrowseRemoteProtocols CUPS
BrowseProtocols CUPS
BrowsePoll PRINTSERVER_NAME


-- no debconf information

-- 
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#756572: polipo: Polipo dies after a few days with `Too many open files'

[Peter Chubb]

Package: polipo
Version: 1.1.1-1
Severity: normal

Dear Maintainer,

Every few days polipo dies.  Just before it dies, I see many entries in the log:

Couldn't establish listening socket: Too many open files
Refusing client connections for one second.

While this is going on, clients cannot connect until I start polipo again.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages polipo depends on:
ii  libc6 2.19-7
ii  lsb-base  4.1+Debian13

polipo recommends no packages.

polipo suggests no packages.

-- Configuration Files:
/etc/polipo/config changed [not included]
/etc/polipo/options changed [not included]

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#747050: update-mime should not quote %s

[Peter Chubb]

Package: mime-support
Version: 3.54

/etc/mailcap is generated by /usr/sbin/update-mime from files in
/usr/lib/mime/packages.   Currently, update-mime adds single quotes
around %s entries.

Well-behaved clients of /etc/mailcap already protect spaces, quotes,
etc., in file names.
For example the flim emacs package calls `shell-quote-argument' when
formatting the file name.  Mutt also does the `right thing'.

The consequence is that if soemone sends me an attachment called
fred's docs.pdf mutt invokes xpdf 'fred\'s\ docs.pdf` which
correctly quotes the embedded quotation mark, but adds an extra level
of quoting to the space.

Please can this behaviour be fixed?  It's probably best not to have
quotation marks around %s in /etc/mailcap, and make all mailcap
clients do proper quoting.

I'm aware of #723708 and #745141 --- which confuses me
This is my suggested patch.

--- update-mime~2014-05-05 14:44:15.715803351 +1000
+++ update-mime 2014-05-05 14:44:33.819919965 +1000
@@ -95,7 +95,7 @@
print STDERR$_\n;
$priority=$defpriority;
}
-   
s/([^\s;]\s+)(?![\'\])([^\s;]*)%s([^\s;]*)/$1'$2%s$3'/g;
+#  
s/([^\s;]\s+)(?![\'\])([^\s;]*)%s([^\s;]*)/$1'$2%s$3'/g;
$entries{$counter} = $_;
push @{$packages{$pkg}},$counter;
push @{$priorities{$priority}},$counter;



--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#658254: Fixed upstream -- can we have a new version please?

[Peter Chubb]

Hi,
Upstream is a 1.0.3, and has this bug fixed.  Debian is still
on 1.0.1 (from three years ago!) even in Sid.

Can we have a new version, please?

Peter C
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737150: Upstream version 2.24.1 has support for F2FS

[Peter Chubb]

Upstream is now 4 versions ahead of Debian unstable at 2.24.1

Upstream has support for F2FS, and a number of other
fixes/imporvements.

Can Debian please move forward, at least in Experimental or Testing?

Peter C
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#736902: qemu: multiboot header always sets mem_upper as 0k

[Peter Chubb]

 Michael == Michael Tokarev m...@tls.msk.ru writes:

Michael 28.01.2014 08:17, Peter Chubb wrote:
 Package: qemu Version: 1.7.0+dfsg-3 Severity: important
 
 Dear Maintainer, Our operating system no longer boots on
 qemu-system-i386 because the multiboot header is no longer set up
 correctly.
 
 To check, run the multiboot tests inside the source tree.
 
 I see the same thing upstream on the standard branch, but the
 linaro branch works OK.

Michael Thank you for a very detailed bugreport.

Michael However, can we please know what is this our operating
Michael system, which source tree to use to run tests, and which
Michael linaro branch you're talking about?

Which OS is not important, but if you want to know, it's seL4.

The Linaro branch is from git://git.linaro.org/qemu/qemu-linaro.git
The main upstream branch is at git://git.qemu.org/qemu.git


But to test you can do:

  apt-get source qemu
  cd qemu-1.7.0+dfsg
  debuild -b
  cd tests/multiboot
  QEMU=../../debian/qemu-system-x86/usr/bin/qemu-system-x86_64 ./run_test.sh

Hope this helps!
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#736902: qemu: multiboot header always sets mem_upper as 0k

[Peter Chubb]

Package: qemu
Version: 1.7.0+dfsg-3
Severity: important

Dear Maintainer,
  Our operating system no longer boots on qemu-system-i386 because the
  multiboot header is no longer set up correctly.

  To check, run the multiboot tests inside the source tree.

  I see the same thing upstream on the standard branch, but the linaro
  branch works OK.

  This is what I see:

FAIL mmap (exit code 69)
FAIL mmap (output difference)
--- mmap.out2014-01-28 14:46:29.648461373 +1100
+++ test.log2014-01-28 14:59:34.252755481 +1100
@@ -4,25 +4,24 @@
 === Running test case: mmap.elf  ===

   
 Lower memory: 639k
-Upper memory: 130040k
+Upper memory: 0k
 
 e820 memory map:
 0x0 - 0x9fc00: type 1 [entry size: 20]
 0x9fc00 - 0xa: type 2 [entry size: 20]
 0xf - 0x10: type 2 [entry size: 20]
-0x10 - 0x7ffe000: type 1 [entry size: 20]
-0x7ffe000 - 0x800: type 2 [entry size: 20]
-0xfffc - 0x1: type 2 [entry size: 20]
+0x10 - 0x118000: type 1 [entry size: 20]
+0x118000 - 0x11a000: type 2 [entry size: 20]
 
 mmap start:   0x9000
-mmap end: 0x9090
-real mmap end:0x9090
+mmap end: 0x9078
+real mmap end:0x9078
 
 
 === Running test case: mmap.elf -m 1.1M ===
 
 Lower memory: 639k
-Upper memory: 96k
+Upper memory: 0k
 
 e820 memory map:
 0x0 - 0x9fc00: type 1 [entry size: 20]
@@ -30,64 +29,58 @@
 0xf - 0x10: type 2 [entry size: 20]
 0x10 - 0x118000: type 1 [entry size: 20]
 0x118000 - 0x11a000: type 2 [entry size: 20]
-0xfffc - 0x1: type 2 [entry size: 20]
 
 mmap start:   0x9000
-mmap end: 0x9090
-real mmap end:0x9090
+mmap end: 0x9078
+real mmap end:0x9078
 
 
 === Running test case: mmap.elf -m 2G ===
 
 Lower memory: 639k
-Upper memory: 2096120k
+Upper memory: 0k
 
 e820 memory map:
 0x0 - 0x9fc00: type 1 [entry size: 20]
 0x9fc00 - 0xa: type 2 [entry size: 20]
 0xf - 0x10: type 2 [entry size: 20]
-0x10 - 0x7fffe000: type 1 [entry size: 20]
-0x7fffe000 - 0x8000: type 2 [entry size: 20]
-0xfffc - 0x1: type 2 [entry size: 20]
+0x10 - 0x118000: type 1 [entry size: 20]
+0x118000 - 0x11a000: type 2 [entry size: 20]
 
 mmap start:   0x9000
-mmap end: 0x9090
-real mmap end:0x9090
+mmap end: 0x9078
+real mmap end:0x9078
 
 
 === Running test case: mmap.elf -m 4G ===
 
 Lower memory: 639k
-Upper memory: 3668984k
+Upper memory: 0k
 
 e820 memory map:
 0x0 - 0x9fc00: type 1 [entry size: 20]
 0x9fc00 - 0xa: type 2 [entry size: 20]
 0xf - 0x10: type 2 [entry size: 20]
-0x10 - 0xdfffe000: type 1 [entry size: 20]
-0xdfffe000 - 0xe000: type 2 [entry size: 20]
-0xfffc - 0x1: type 2 [entry size: 20]
-0x1 - 0x12000: type 1 [entry size: 20]
+0x10 - 0x118000: type 1 [entry size: 20]
+0x118000 - 0x11a000: type 2 [entry size: 20]
 
 mmap start:   0x9000
-mmap end: 0x90a8
-real mmap end:0x90a8
+mmap end: 0x9078
+real mmap end:0x9078
 
 
 === Running test case: mmap.elf -m 8G ===
 
 Lower memory: 639k
-Upper memory: 3668984k
+Upper memory: 0k
 
 e820 memory map:
 0x0 - 0x9fc00: type 1 [entry size: 20]
 0x9fc00 - 0xa: type 2 [entry size: 20]
 0xf - 0x10: type 2 [entry size: 20]
-0x10 - 0xdfffe000: type 1 [entry size: 20]
-0xdfffe000 - 0xe000: type 2 [entry size: 20]
-0xfffc - 0x1: type 2 [entry size: 20]
-0x1 - 0x22000: type 1 [entry size: 20]
+0x10 - 0x118000: type 1 [entry size: 20]
+0x118000 - 0x11a000: type 2 [entry size: 20]
 
 mmap start:   0x9000
-mmap end: 0x90a8
-real mmap end:0x90a8
+mmap end: 0x9078
+real mmap end:0x9078



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages qemu depends on:
ii  qemu-system  1.7.0+dfsg-3
ii  qemu-user1.7.0+dfsg-3
ii  qemu-utils   1.7.0+dfsg-3

qemu recommends no packages.

Versions of packages qemu suggests:
ii  qemu-user-static  1.7.0+dfsg-3

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735360: kexec-tools: Multiboot mem_lower is always zero after kexec

[Peter Chubb]

Hi Khalid,
   FYI: The patch has now been applied upstream, too.

Peter C
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735360: kexec-tools: Multiboot mem_lower is always zero after kexec

[Peter Chubb]

Package: kexec-tools
Version: 1:2.0.4-1
Severity: normal
Tags: upstream, patch

Dear Maintainer,
 I'm trying to use kexec to boot a multiboot image.  My image
 relies on mbi-mem_lower being correct, but the current code
 combined with a stock debian kernel always fills this field in
 with zero.

 The problem is that the debian stock kernel protects the first
 few pages (from physical address zero) so they don't appear in
 /proc/iomem -- so the test in kexec-multiboot-x86.c to
 find the low memory fails -- there's never any visible memroy at
 location zero in /proc/iomem.

 My suggested fix is attached.

---
 kexec/arch/i386/kexec-multiboot-x86.c |   14 +++---
 1 file changed, 11 insertions(+), 3 deletions(-)

Index: kexec-tools-2.0.4/kexec/arch/i386/kexec-multiboot-x86.c
===
--- kexec-tools-2.0.4.orig/kexec/arch/i386/kexec-multiboot-x86.c
2013-03-14 18:45:16.0 +1000
+++ kexec-tools-2.0.4/kexec/arch/i386/kexec-multiboot-x86.c 2014-01-15 
10:21:02.138172304 +1000
@@ -261,10 +261,18 @@ int multiboot_x86_load(int argc, char **
mmap[i].length_high= length  32;
if (range[i].type == RANGE_RAM) {
mmap[i].Type = 1; /* RAM */
-   /* Is this the low memory? */
-   if ((range[i].start == 0)
-(range[i].end  mem_lower))
+   /*
+ * Is this the low memory?  Can't just test
+ * against zero, because Linux protects (and
+ * hides) the first few pages of physical
+ * memory.
+ */
+
+   if ((range[i].start = 64*1024)
+(range[i].end  mem_lower)) {
+range[i].start = 0;
mem_lower = range[i].end;
+}
/* Is this the high memory? */
if ((range[i].start = 0x10)
 (range[i].end  mem_upper + 0x10))



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-rc8 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kexec-tools depends on:
ii  debconf [debconf-2.0]  1.5.52
ii  libc6  2.17-97

kexec-tools recommends no packages.

kexec-tools suggests no packages.

-- debconf information:
* kexec-tools/load_kexec: true
  kexec-tools/use_grub_config: false


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#733909: quodlibet: Segfaults when trying to play audio/x-alac files

[Peter Chubb]

 Christoph == Christoph Reiter reiter.christ...@gmail.com writes:

Christoph 2014/1/2 Peter Chubb peter.ch...@nicta.com.au:
 
 Quodlibet puts up a popup and segfautls.

Christoph Does it crash after closing the popup?

No, beforehand.  You're left with `Segmentation fault' in the xterm I
started quodlibet from, and a popup in the middle of the screen.

 The popup says:
 
 Invalid Commandline The parameters passed to the application had an
 invalid format. Please file a bug!
 
 The parameters were: gstreamer|1.0|quodlibet|Apple Lossless Audio
 (ALAC) decoder|decoder-audio/x-alac, samplesize=(int)16
 
 
 The file plays fine with $ gst-launch playbin
 uri=file://`pwd`/28-01-Prelude.m4a

Christoph Please try with gst-launch-1.0, gst-launch is part of
Christoph GStreamer 0.10 which QL doesn't use anymore.

Ahah --- it segfaults.

$ gst-launch-1.0 playbin uri=file://`pwd`/28-01\ Suite\ For\ Lute\ BWV\ 995\ 
G\ Minor\ -\ Prelude.m4a 
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Caught SIGSEGV
#0  0x7f4d6857a95d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4d68aad194 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4d68aad5fa in g_main_loop_run ()
#3  0x7f4d68fef8a4 in gst_bus_poll (bus=bus@entry=0xa476b0, 
#4  0x004045a8 in event_loop (pipeline=0xa50110, 
#5  0x004036b7 in main (argc=3, argv=0x7fff09e4d738)
Spinning.  Please run 'gdb gst-launch-1.0 28190' to continue debugging, Ctrl-C 
to quit, or Ctrl-\ to dump core.

If I start with GDB I can get a more meaningful stack dump:

#0  gst_ffmpegauddec_frame (ffmpegdec=0x, 
ffmpegdec@entry=0x7fffe4098b30, data=data@entry=0x7fffe4003150  , 
size=0, size@entry=32, got_data=0x0, got_data@entry=0x7fffeef67a28, 
ret=ret@entry=0x7fffeef67a2c) at gstavauddec.c:641
#1  0x7fffe2057271 in gst_ffmpegauddec_handle_frame (
decoder=0x7fffe4098b30, inbuf=0x70020b50) at gstavauddec.c:754
#2  0x75dd2a03 in gst_audio_decoder_push_buffers (
dec=dec@entry=0x7fffe4098b30, force=force@entry=0)
at gstaudiodecoder.c:1307
#3  0x75dd2ddb in gst_audio_decoder_chain_forward (
dec=dec@entry=0x7fffe4098b30, buffer=0x0, buffer@entry=0x70020b50)
at gstaudiodecoder.c:1410
#4  0x75dd3ec6 in gst_audio_decoder_chain (pad=optimized out, 
parent=0x7fffe4098b30, buffer=0x70020b50) at gstaudiodecoder.c:1678
#5  0x77b39ac8 in gst_pad_chain_data_unchecked (data=0x70020b50, 
type=4112, pad=0x7e1a70) at gstpad.c:3711
#6  gst_pad_push_data (pad=0x7e1610, type=type@entry=4112, 
data=optimized out, data@entry=0x70020b50) at gstpad.c:3941
#7  0x77b405f6 in gst_pad_push (pad=optimized out, 
buffer=buffer@entry=0x70020b50) at gstpad.c:4044
#8  0x75020888 in gst_single_queue_push_one (object=0x70020b50, 
sq=0x7fffe4007110, mq=0x7fffe4006080) at gstmultiqueue.c:1083
#9  gst_multi_queue_loop (pad=optimized out) at gstmultiqueue.c:1332


 $ file 28-01-Prelude.m4a 28-01-Prelude.m4a: ISO Media, MPEG v4
 system, iTunes AAC-LC

Christoph Can you send me the file via mail, dropbox etc.?

Sure.  Separate email.
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#733909: quodlibet: Segfaults when trying to play audio/x-alac files

[Peter Chubb]

Package: quodlibet
Version: 3.0.2-3
Severity: normal

Dear Maintainer,

I have some .m4a files that I want to play with quodlibet.

Quodlibet puts up a popup and segfautls.

The popup says:

  Invalid Commandline
  The parameters passed to the application had an invalid
  format. Please file a bug! 

  The parameters were:
  gstreamer|1.0|quodlibet|Apple Lossless Audio (ALAC) 
decoder|decoder-audio/x-alac, samplesize=(int)16


The file plays fine with
$ gst-launch playbin uri=file://`pwd`/28-01-Prelude.m4a

$ file 28-01-Prelude.m4a 
28-01-Prelude.m4a: ISO Media, MPEG v4 system, iTunes AAC-LC


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-rc5+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages quodlibet depends on:
ii  exfalso  3.0.2-3
ii  gir1.2-gst-plugins-base-1.0  1.2.2-1
ii  gir1.2-gstreamer-1.0 1.2.2-1
ii  gstreamer1.0-plugins-base1.2.2-1
ii  gstreamer1.0-plugins-good1.2.2-1
ii  gstreamer1.0-plugins-ugly1.2.2-1
ii  gstreamer1.0-pulseaudio  1.2.2-1
ii  python   2.7.5-5

Versions of packages quodlibet recommends:
ii  gir1.2-gtksource-3.0  3.8.2-1
pn  gir1.2-keybinder-3.0  none
ii  libgpod4  0.8.3-1.1
ii  media-player-info 19-1
ii  python-dbus   1.2.0-2+b1
ii  python-feedparser 5.1.3-1
ii  udisks1.0.4-8+b1

Versions of packages quodlibet suggests:
ii  gstreamer1.0-plugins-bad  1.2.2-1
ii  quodlibet-plugins 1:3.0.2-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711135: unable to reproduce

[Peter Chubb]

 dann == dann frazier da...@dannf.org writes:
dann Can you attach your elilo.conf? I'm mostly trying to confirm you
dann are specifying relocatable, but also curious about other
dann settings.

It's the one in the d-i netboot.tgz --- extracted here for your convenience.
-
chooser=textmenu
default=install
delay=20
prompt

message=boot-screens/elilo_menu.msg
f1=boot-screens/general.msg
f2=boot-screens/params.msg

relocatable

image=vmlinuz
label=install
description=Install
initrd=initrd.gz
append=--
read-only

image=vmlinuz
label=expert
description=Install [Expert mode]
initrd=initrd.gz
append=priority=low --
read-only

image=vmlinuz
label=rescue
description=Rescue
initrd=initrd.gz
append=rescue/enable=true --
read-only


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711135: unable to reproduce

[Peter Chubb]

 dann == dann frazier da...@dannf.org writes:
dann Can you attach your elilo.conf? I'm mostly trying to confirm you
dann are specifying relocatable, but also curious about other
dann settings.

It's the one in the d-i netboot.tgz --- extracted here for your convenience.
-
chooser=textmenu
default=install
delay=20
prompt

message=boot-screens/elilo_menu.msg
f1=boot-screens/general.msg
f2=boot-screens/params.msg

relocatable

image=vmlinuz
label=install
description=Install
initrd=initrd.gz
append=--
read-only

image=vmlinuz
label=expert
description=Install [Expert mode]
initrd=initrd.gz
append=priority=low --
read-only

image=vmlinuz
label=rescue
description=Rescue
initrd=initrd.gz
append=rescue/enable=true --
read-only
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711135: unable to reproduce

[Peter Chubb]

 dann == dann frazier da...@debian.org writes:

dann I've got a zx6000 here, but I'm unable to reproduce. Are we
dann using the same versions of firmware/elilo? I'm using the serial
dann console.

I'm using the serial console via the HP iLO system.
I collected today's snapshot fo jessie's netboot.tgz, unpacked it on
our tftp server, and booted via DHCP:

EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]

Please select a boot option

EFI Shell [Built-in]
CDROm   
DHCP Boot (Gigabit) 
Debian  
Boot Option Maintenance Menu
System Configuration Menu   


Use ^ and v to change option(s). Use Enter to select an option
Loading.: DHCP Boot (Gigabit)   
Running LoadFile()

CLIENT MAC ADDR: 00 30 6E F3 7E AF 
CLIENT IP: 10.13.0.38  MASK: 255.255.254.0  DHCP IP: 10.13.0.1
GATEWAY IP: 10.13.0.1 

TSize.Running LoadFile()

Starting: DHCP Boot (Gigabit)
ELILO v3.14 for EFI/IA-64
..
Uncompressing Linux... done
Loading file /gelato/debian-installer/ia64/initrd.gz...done
Uncompressing Linux... done
***
* ROM Version : 02.31
* ROM Date: 03/11/2004
* BMC Version :  01.52
***


--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711135: Still present in Jessie

[Peter Chubb]

I just tested the netboot image from
http://d-i.debian.org/daily-images/ia64/20130526-00:16/netboot/netboot.tar.gz 

The bug is still present in this Jessie install.

--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#725849: dhclient script

[Peter Chubb]

I've discovered the source has a dhclient script that does the right
magic; it just needs to be packaged into the Debian package.

Peter C
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#726271: pxe-kexec should whitelist Jessie/Sid

[Peter Chubb]

Package: pxe-kexec
Version: 0.2.4-3

When on Unstable I run pxe-kexec it tells me:
  
  You Linux distribution 'Debian' in version 'jessie/sid' doesn't have kexec
  in the reboot script. Please read pxe-kexec(8) for more information. You
  can overwrite the check with '--ignore-whitelist'.

Quite apart from the typo (s/You/Your/) Sid *can* have kexec installed
and set up for use during reboot.  The test is incorrect -- it would be
better to see if /etc/init.d/kexec is present and active.

Peter C
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#725849: pxe-kexec should depend on dhcpcd or should create /var/lib/pxe-kexec

[Peter Chubb]

Package: pxe-kexe
Version:  0.2.4-3

pxe-kexec searches /var/lib/dhcpcd/dhcpcd-if.info to find a tftp
server.  This file is installed by dhcpcd.  There are at least three
different dhcp clients available in Debian; only one has this file.

I do:
# pxe-kexec --ignore-whitelist
No TFTP server specified and also no DHCP server in the DHCP info file
(/var/lib/dhcpcd/dhcpcd-if.info).

My dhcp client creates /var/lib/dhcp/dhclient.if.leases

From reading the source, I discovered that if I do:
 mkdir -p /var/lib/pxe-kexec;
 cd /var/lib/pxe-kexec
 ln -s ../dhcp/dhclient.eth1.leases eth1

I can get it to work.

--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#724549: rhythmbox-ampache: Python traceback on activation.

[Peter Chubb]

Package: rhythmbox-ampache
Version: 0.11.1+svn34-0.1
Severity: important

Dear Maintainer,
I installed rhythmbox and rhythmbox-ampache, and started rhythmbox
from an xterm.
I clicked on the gear icon in the top right corner, and selected
plugins.
I enabled the Ampache plugin -- an icon apeared under the `library'
pane.

I clicked the ampache icon.

I see this traceback in the xterm I started rhythmbox from:
$ rhythmbox

(rhythmbox:26981): Gtk-WARNING **: Failed to register client: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
Traceback (most recent call last):
  File /usr/lib/rhythmbox/plugins/ampache/ampache.py, line 65, in do_activate
manager = shell.props.ui_manager
AttributeError: 'gi._gobject.GProps' object has no attribute 'ui_manager'

(rhythmbox:26981): Rhythmbox-WARNING **: Unable to grab media player keys: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SettingsDaemon was not provided by any .service files
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Traceback (most recent 
call last):
  File /usr/lib/rhythmbox/plugins/ampache/AmpacheBrowser.py, line 412, in 
do_selected
self.do_activate()
  File /usr/lib/rhythmbox/plugins/ampache/AmpacheBrowser.py, line 387, in 
do_activate
self.__popup = shell.props.ui_manager.get_widget('/AmpacheSourceViewPopup')
AttributeError: 'gi._gobject.GProps' object has no attribute 'ui_manager'

I expect to see the list of musical items on the Ampache server.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-rc6+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages rhythmbox-ampache depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.16.1-1
ii  libglade2-0  1:2.6.4-1
ii  python-gconf 2.28.1+dfsg-1
ii  python-gobject   3.8.3-1
ii  python-gtk2  2.24.0-3+b1
ii  rhythmbox-plugins2.99.1-3

rhythmbox-ampache recommends no packages.

rhythmbox-ampache suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#720127: [php-maint] Bug#720127: php5: Maximum execution time exceeded immediately...

[Peter Chubb]

 Ondřej == Ondřej Surý ond...@debian.org writes:


Ondřej could you try that with some simple script?

Simple scripts don't seem to show the problem.  I see it on Owncloud
and on Ampache.

My *guess* as to what's happening is that there's some other timeout
using SIGPROF, that triggers the Execution Time Exceeded message.

Try this:

?php
   date_default_timezone_set('UTC');
   @set_time_limit(3600);
   @ini_set('max_execution_time', 3600);
   @ini_set('max_input_time', -1);
   while (1)  {
echo date(DATE_RFC822) ;
echo \n;
   }
?


The output I see is:

Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
Tue, 20 Aug 13 10:27:04 +
PHP Fatal error:  Maximum execution time of 3600 seconds exceeded in 
/home/peterc/xxx.php on line 7
PHP Stack trace:
PHP   1. {main}() /home/peterc/xxx.php:0
PHP   2. date() /home/peterc/xxx.php:7


--
Peter C


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#720127: php5: Maximum execution time exceeded immediately...

[Peter Chubb]

Package: php5
Version: 5.5.1+dfsg-2
Severity: normal

Dear Maintainer,
php5 seems to throw a maximum execution time exceeded immediately.
I see this on owncloud and ampache.

I've set the default timeout to 3600 (1 hour), but the error that time
limit is exceeded comes almost immediately.

Here's an example backtrace with timestamps.  By my reading that's 
about a tenth of a second before the excepton is thrown.

If I up the timelimit to 10 hours, the process succeeds.  

( ! ) Fatal error: Maximum execution time of 3600 seconds exceeded in 
/usr/share/php/php-gettext/streams.php on line 113
Call Stack
#   TimeMemory  FunctionLocation
1   0.0004  229952  {main}( )   ../login.php:0
2   0.0565  1471984 require( 
'/usr/share/ampache/www/templates/show_login_form.inc.php' )   ../login.php:176
3   0.0570  1472488 T_( )   ../show_login_form.inc.php:66
4   0.0570  1472520 __( )   ../gettext.inc:406
5   0.0570  1472568 _gettext( ) ../gettext.inc:285
6   0.0580  1483624 gettext_reader-translate( )../gettext.inc:278
7   0.0580  1484208 gettext_reader-load_tables( )  ../gettext.php:254
8   0.1082  1986656 FileReader-read( ) ../gettext.php:161


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10.0-rc4+ (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5 depends on:
ii  libapache2-mod-php5  5.5.1+dfsg-2
ii  php5-common  5.5.1+dfsg-2

php5 recommends no packages.

php5 suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#720127: More on environment

[Peter Chubb]

For what it's worth I'm using apache's mpm_prefork module, to avoid
multi-thread issues, and libapache2-mod-php5 to handle PHP requests.

I'm also running the php server over ssl.
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717297: [Pkg-xfce-devel] Bug#717297: lightdm: pam.d/lightdm-greeter doesn't use system settings for pam

[Peter Chubb]

 Yves-Alexis == Yves-Alexis Perez cor...@debian.org writes:


Yves-Alexis Can you tell us what exactly is broken by this? As far as
Yves-Alexis I know this pam file is only for the greeter, not for
Yves-Alexis session run from them (they're handled by
Yves-Alexis /etc/pam.d/lightdm which correctly includes the common
Yves-Alexis debian files.

People who authenticate only via ldap --- for whom pam_unix.so doesn't
work --- cannot log in, because username and password are not know to
pam_unix.so only to either pam_ldap.so or pam_sssd.so.  I imagine
other authentication mechanisms will also fail.

What's more if there's any other policy set in common-account or
common-session, it's not obeyed (e.g., time-of-use or group membership
restrictions)


--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717297: lightdm: pam.d/lightdm-greeter doesn't use system settings for pam

[Peter Chubb]

Package: lightdm
Version: 1.6.0-3
Severity: normal

Dear Maintainer,
We're running in an environment that authenticates via ldap, using sssd
locally.  But pam.d/lightdm-greeter doesn't use common-session etc., so
the updates that sssd's installation did to pam.d/common-xxx don't apply.

I think that pam-greeter should use all the appropriate common-xxx files
in pam.d to manage authentication and so on, so that whatever the admin
has set up for authentication is obeyed by lightdm.  As can be seen from
the attached file, I `fixed' it for now by manually adding an appropriate
pam_sssd line.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lightdm depends on:
ii  adduser3.113+nmu3
ii  consolekit 0.4.5-3.1
ii  dbus   1.6.12-1
ii  debconf [debconf-2.0]  1.5.50
ii  libc6  2.17-7
ii  libgcrypt111.5.2-3
ii  libglib2.0-0   2.36.3-3
ii  libpam0g   1.1.3-9
ii  libxcb11.9.1-3
ii  libxdmcp6  1:1.1.1-1
ii  lightdm-gtk-greeter [lightdm-greeter]  1.6.0-1

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+3

Versions of packages lightdm suggests:
ii  accountsservice  0.6.34-1
ii  upower   0.9.20-2

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[SeatDefaults]
xserver-allow-tcp=false
greeter-session=lightdm-greeter
greeter-hide-users=true
user-session=xfce
session-wrapper=/etc/X11/Xsession
[XDMCPServer]
[VNCServer]

/etc/pam.d/lightdm-greeter changed:
auth  required pam_env.so envfile=/etc/default/locale
auth  required pam_permit.so
account   required pam_permit.so
password  required pam_deny.so
session   required pam_unix.so
session   optional pam_sssd.so


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717298: debian-installer: After installing xfce environment, don't see xfce

[Peter Chubb]

Package: debian-installer
Version: Jessie
Severity: normal

Dear Maintainer,
I did a clean install using the netboot.tar.gz +pxe method, 
selecting the XFCE desktop environment.  But when the machine booted, 
it presented a Gnome desktop environment.  I expected to see XFCE.


XFCE is present, and I was able to modify /etc/lighdm.conf to make it 
be the default.  However, I expected it to be this way out of the box, 
and for gnome not to be installed at all.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#714976: gcc-4.8-source: FTBFS cross-compiler for armel

[Peter Chubb]

Package: gcc-4.8-source
Version: 4.8.1-5
Severity: normal

Dear Maintainer,
I'm trying to build a cross-compiler using gcc-4.8-source, 
following the instructions in debian/README.cross.

I do:
echo armel  debian/target
debian/rules control

dpkg-buildpackage -rfakeroot

and things churn away for fifteen mini=utes or so, then:
dh_link -plibgcc-4.8-dev-armel-cross /usr/arm-linux-gnueabi/lib/libssp.so.0 
/usr/lib/gcc-cross/arm-linux-gnueabi/4.8/libssp.so
mv debian/tmp/usr/arm-linux-gnueabi/lib/libssp_nonshared.a 
debian/libgcc-4.8-dev-armel-cross/usr/lib/gcc-cross/arm-linux-gnueabi/4.8/;
mv: cannot stat 'debian/tmp/usr/arm-linux-gnueabi/lib/libssp_nonshared.a': No 
such file or directory
make[1]: *** [stamps/08-binary-stamp-libgcc-dev] Error 1
make[1]: Leaving directory `/scratch/peterc/gcc-4.8'
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

-- Peter C

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armel

Kernel: Linux 3.8-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.8-source depends on:
ii  autoconf2.64  2.64-3
ii  gawk  1:4.0.1+dfsg-2.1
ii  make  3.81-8.2
ii  patchutils0.3.2-2
ii  quilt 0.60-8

gcc-4.8-source recommends no packages.

gcc-4.8-source suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#710203: Can't install firmware from USB stick using PXE boot, amd64 wheezy

[Peter Chubb]

 Petter == Petter Reinholdtsen p...@hungry.com writes:

Petter [Peter Chubb]
 It's more than that -- cat /proc/partitions doesn't show the stick
 at all.  I suspect that the USB stick wasn;t recognised when it was
 plugged in.

Petter Right.  Then it probably is a kernel issue.  Is there anything
Petter useful printed to dmesg when you plug it in?  Is USB working
Petter on the machine after installation?


After installation, yes.  But nothing got printed by dmesg during the
installation when I plug in the USB stick.  And (from mempry, the
machine is now in production so I can't fiddle) lsmod didn't show all
the necessary modules --- after full installation I see:

ehci_pci   12472  0 
uhci_hcd   26976  0 
ehci_hcd   40464  1 ehci_pci

I think ehci-pci,ko is missing from the initrd.

--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#710203: Can't install firmware from USB stick using PXE boot, amd64 wheezy

[Peter Chubb]

 Petter == Petter Reinholdtsen p...@hungry.com writes:

Petter [Peter Chubb]
 2.  This system uses broadcom NICs that need firmware.  I put the
 firmware onto a FAT-formatted USB stick, but the machine does not
 recognise the stick when plugged in.  lsmod on the console does not
 show usb_storage in the list of loaded modules after a failed
 attempt.

Petter Could the problem be that the installer do not understand FAT
Petter file systems?  Can you try with ext3 on the USB stick?

It's more than that -- cat /proc/partitions doesn't show the stick at
all.  I suspect that the USB stick wasn;t recognised when it was
plugged in.
--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711469: Can we have libslapi-dev back please:

[Peter Chubb]

Package: libldap2-dev
Version: 2.4.31-1+nmu

I can no longer compile my old slapi plugins.  Can we please have
slapi-dev back in some form?

It's been gone since this comment:
openldap2.3 (2.4.7-2) unstable; urgency=low

  * Temporarily drop slapi-dev from the package to get through NEW; this
functionality should be readded later, either by restoring the slapi-dev
package or by moving it to libldap2-dev, depending on the outcome of
discussion with the ftp-masters.

Slapd still provides libslapi but there are no header files or
development libraries.

--
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org