from:"Marco van Zwetselaar"

[Bug 2062960] Re: ubuntu 24.04 mailman3-web fails install on clean system

2024-04-26 Thread Marco van Zwetselaar

Can confirm this also occurs when upgrading from mantic to noble.

The issue appears to be caused by a breaking change introduced in
version 1.3.10 (2023-10-21)[1], which is the version of python3-django-
postorius in noble.

Adding "allauth.account.middleware.AccountMiddleware" to the MIDDLEWARE
list in /usr/share/mailman3/settings.py fixes the issue, but I then run
into other incompatibility errors.  First there is this:

   File 
"/opt/mailman/mm/venv_rel/lib/python3.9/site-packages/hyperkitty/lib/renderer.py",
 line 6, in 
from mistune.plugins.extra import plugin_url
   ModuleNotFoundError: No module named 'mistune.plugins.extra'

which appears to be an upstream issue[2] that is harder to solve on our
end because it requires a downgrade to of python-mistune to 2.x, whereas
noble ships with 3.0.2.

I briefly tested with the referencing code (in /usr/lib/python3/dist-
packages/hyperkitty/lib/renderer.py) patched out.  The mailman3 web
application then does come up, but now spews periodic errors to the log
that suggest that a database migration should have run:

10:11:10 [Q] ERROR Could not create task from schedule
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 
89, in _execute
return self.cursor.execute(sql, params)
   
psycopg2.errors.UndefinedColumn: column 
django_q_schedule.intended_date_kwarg does not exist
LINE 1: ..._schedule"."task", "django_q_schedule"."cluster", "django_q_...

Here is where I stopped chasing this down, but there may be light at the
end of the tunnel: the Debian maintainer yesterday committed a snapshot
of the latest upstream[3], which is supposed to fix the allauth issue[4]
as well as several others.

For now, I'll try rolling back to the mantic packages, which worked
great (with patches for #2060293, #2060276, and #2060753).  Owww this
package could really use some TLC :).

Cheers
Marco

[1] https://pypi.org/project/django-mailman3/
[2] https://gitlab.com/mailman/hyperkitty/-/issues/437
[3] 
https://salsa.debian.org/mailman-team/mailman-suite/-/commit/edf7873dce29e102c03a2be01133a6c00f8994c0
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062707.


** Bug watch added: gitlab.com/mailman/hyperkitty/-/issues #437
   https://gitlab.com/mailman/hyperkitty/-/issues/437

** Bug watch added: Debian Bug tracker #1062707
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062707

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

Title:
  ubuntu 24.04 mailman3-web fails install on clean system

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


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

[Bug 2062542] Re: systemd-resolved stub gives SERVFAIL for DNSSEC negative response

2024-04-20 Thread Marco van Zwetselaar

This is on mantic, systemd-resolved 253.5-1ubuntu6.1

** Tags added: mantic

** Description changed:

- This issue surface when researching the issue that Postfix on my system
+ This issue surfaced when researching the issue that Postfix on my system
  (with DANE enabled) deferred mail deliveries with 100s of this warning
  in the log:
  
- Warning: DANE TLSA lookup problem: Host or domain name not found.
+ Warning: DANE TLSA lookup problem: Host or domain name not found.
  Name service error for name=_25._tcp.cluster5.us.messagelabs.com
  type=TLSA: Host not found, try again
  
  The DNS resolver on my machine was pointing at the systemd-resolved
  stub:
  
- $ cat /etc/resolv.conf | grep nameserver
- nameserver 127.0.0.53
+ $ cat /etc/resolv.conf | grep nameserver
+ nameserver 127.0.0.53
  
- $ resolvectl status
- Global
- Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported
- resolv.conf mode: stub
+ $ resolvectl status
+ Global
+ Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported
+ resolv.conf mode: stub
  
  Note DNSSEC is enabled (else Postfix couldn't be doing DANE). Now if I
  query the TLSA record for the messagelab server, I get a SERVFAIL from
  the stub resolver:
  
- $ delv +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA
- ;; resolution failed: SERVFAIL
+ $ delv +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA
+ ;; resolution failed: SERVFAIL
  
  Whereas if I query my upstream DNS or Google DNS, I get a DNSSEC
  validated (negative) response:
  
- $ delv @8.8.8.8 +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA
- ;; resolution failed: ncache nxrrset
- ; negative response, fully validated
- ; _25._tcp.cluster5.us.messagelabs.com. 299 IN \-TLSA ;-$NXRRSET
- ; _25._tcp.cluster5.us.messagelabs.com. RRSIG NSEC ...
- ; _25._tcp.cluster5.us.messagelabs.com. NSEC 
\000._25._tcp.cluster5.us.messagelabs.com. A PTR HINFO MX TXT RP  SRV NAPTR 
SSHFP RRSIG NSEC SVCB HTTPS SPF IXFR AXFR CAA
- ; messagelabs.com. SOA ns-1714.awsdns-22.co.uk. 
awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
- ; messagelabs.com. RRSIG SOA ...
+ $ delv @8.8.8.8 +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA
+ ;; resolution failed: ncache nxrrset
+ ; negative response, fully validated
+ ; _25._tcp.cluster5.us.messagelabs.com. 299 IN \-TLSA ;-$NXRRSET
+ ; _25._tcp.cluster5.us.messagelabs.com. RRSIG NSEC ...
+ ; _25._tcp.cluster5.us.messagelabs.com. NSEC 
\000._25._tcp.cluster5.us.messagelabs.com. A PTR HINFO MX TXT RP  SRV NAPTR 
SSHFP RRSIG NSEC SVCB HTTPS SPF IXFR AXFR CAA
+ ; messagelabs.com. SOA ns-1714.awsdns-22.co.uk. 
awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
+ ; messagelabs.com. RRSIG SOA ...
  
  I assume Postfix (with smtp_tls_security_level = dane i.e.
  "Opportunistic DANE") deals with the negative response by downgrading to
  "encrypt", whereas the SERVFAIL response makes it refuse to connect
  altogether.
  
  My workaround was to switch from the systemd-resolved stub resolver to
  the upstream servers. In /etc/systemd/resolved.conf set:
  
- DNS=... your upstream servers if not already given through DHCP ...
- DNSStubListener=no
+ DNS=... your upstream servers if not already given through DHCP ...
+ DNSStubListener=no
  
  Then restart the service and restart Postfix if it is chrooted (so the
  new /etc/resolv.conf gets copied into the chroot):
  
- systemctl restart systemd-resolved
- systemctl restart postfix
+ systemctl restart systemd-resolved
+ systemctl restart postfix
  
  I am not sure if this could be considered a Postfix bug as well (it
  could consider a SERVFAIL on a TLSA record the same as a negative), but
  surely it seems to me the systemd-resolved stub resolver should not
  return the SERVFAIL here.
  
  For more background on this bug report, please see
  https://serverfault.com/a/1158198/299950

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

Title:
  systemd-resolved stub gives SERVFAIL for DNSSEC negative response

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


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

[Bug 2062542] [NEW] systemd-resolved stub gives SERVFAIL for DNSSEC negative response

2024-04-19 Thread Marco van Zwetselaar

Public bug reported:

This issue surface when researching the issue that Postfix on my system
(with DANE enabled) deferred mail deliveries with 100s of this warning
in the log:

Warning: DANE TLSA lookup problem: Host or domain name not found.
Name service error for name=_25._tcp.cluster5.us.messagelabs.com
type=TLSA: Host not found, try again

The DNS resolver on my machine was pointing at the systemd-resolved
stub:

$ cat /etc/resolv.conf | grep nameserver
nameserver 127.0.0.53

$ resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported
resolv.conf mode: stub

Note DNSSEC is enabled (else Postfix couldn't be doing DANE). Now if I
query the TLSA record for the messagelab server, I get a SERVFAIL from
the stub resolver:

$ delv +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA
;; resolution failed: SERVFAIL

Whereas if I query my upstream DNS or Google DNS, I get a DNSSEC
validated (negative) response:

$ delv @8.8.8.8 +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA
;; resolution failed: ncache nxrrset
; negative response, fully validated
; _25._tcp.cluster5.us.messagelabs.com. 299 IN \-TLSA ;-$NXRRSET
; _25._tcp.cluster5.us.messagelabs.com. RRSIG NSEC ...
; _25._tcp.cluster5.us.messagelabs.com. NSEC 
\000._25._tcp.cluster5.us.messagelabs.com. A PTR HINFO MX TXT RP  SRV NAPTR 
SSHFP RRSIG NSEC SVCB HTTPS SPF IXFR AXFR CAA
; messagelabs.com. SOA ns-1714.awsdns-22.co.uk. 
awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
; messagelabs.com. RRSIG SOA ...

I assume Postfix (with smtp_tls_security_level = dane i.e.
"Opportunistic DANE") deals with the negative response by downgrading to
"encrypt", whereas the SERVFAIL response makes it refuse to connect
altogether.

My workaround was to switch from the systemd-resolved stub resolver to
the upstream servers. In /etc/systemd/resolved.conf set:

DNS=... your upstream servers if not already given through DHCP ...
DNSStubListener=no

Then restart the service and restart Postfix if it is chrooted (so the
new /etc/resolv.conf gets copied into the chroot):

systemctl restart systemd-resolved
systemctl restart postfix

I am not sure if this could be considered a Postfix bug as well (it
could consider a SERVFAIL on a TLSA record the same as a negative), but
surely it seems to me the systemd-resolved stub resolver should not
return the SERVFAIL here.

For more background on this bug report, please see
https://serverfault.com/a/1158198/299950

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

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

Title:
  systemd-resolved stub gives SERVFAIL for DNSSEC negative response

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


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

[Bug 2060753] [NEW] mailman3-web needs DEFAULT_AUTO_FIELD setting

2024-04-09 Thread Marco van Zwetselaar

Public bug reported:

Installation of mail3man-web (0+20200530-2.1) in mantic produces a list
of 14 warnings that look like this:

WARNINGS:
django_mailman3.MailDomain: (models.W042) Auto-created primary key used 
when not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the 
DjangoMailman3Config.default_auto_field attribute to point to a subclass of 
AutoField, e.g. 'django.db.models.BigAutoField'.

This would only be a minor nuisance, except that the application sends
this list of warnings in an email to the site administrator _once every
minute_.

The issue can be resolved by adding this line to
/usr/share/mailman3-web/settings.py (patch attached):

DEFAULT_AUTO_FIELD='django.db.models.AutoField'

** Affects: mailman-suite (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "auto_field.patch"
   
https://bugs.launchpad.net/bugs/2060753/+attachment/5763076/+files/auto_field.patch

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

Title:
  mailman3-web needs DEFAULT_AUTO_FIELD setting

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


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

[Bug 2060276] [NEW] mailman3-web 0+20200530-2.1 fails to install

2024-04-06 Thread Marco van Zwetselaar

Public bug reported:

Installing mailman3-web on mantic fails with:

  File "/usr/share/mailman3-web/urls.py", line 20, in 
from django.conf.urls import include, url
ImportError: cannot import name 'url' from 'django.conf.urls' 
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
dpkg: error processing package mailman3-web (--configure):
 installed mailman3-web package post-installation script subprocess returned 
error exit status 1

The error is due to deprecation of url in django.conf.urls, see here:
https://github.com/Tivix/django-rest-auth/issues/659

The fix is to replace it with re_path from django.urls. Patch for
/usr/share/mailman3-web/urls.py is attached.

** Affects: mailman-suite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: mantic patch

** Patch added: "mailman3-web.patch"
   
https://bugs.launchpad.net/bugs/2060276/+attachment/5761631/+files/mailman3-web.patch

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

Title:
  mailman3-web 0+20200530-2.1 fails to install

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


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

[Bug 2060293] [NEW] mailman3-web needs Q_CLUSTER retry setting

2024-04-06 Thread Marco van Zwetselaar

Public bug reported:

Installation of mailman3-web (0+20200530-2.1) on mantic produces this
warning:

Creating config file /etc/mailman3/mailman-web.py with new version  

   
/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and 
timeout are misconfigured. Set retry larger than timeout,
failure to do so will cause the tasks to be retriggered before 
completion.
See https://django-q.readthedocs.io/en/latest/configure.html#retry 
for details.

This refers to the 'retry' and 'timeout' fields of the Q_CLUSTER
dictionary configured in /usr/share/mailman3-web/settings.py.

That file sets 'timeout' to 300, but has no setting for retry.  The
documentation linked above states that the built-in default is 60
seconds.

Though Django reports this as a warning, clearly this configuration will
cause bugs such as tasks being executed multiple times (up to 5 retries
could be started while previous tasks may still finish).

The fix is to add a 'retry' setting to the settings file.  Assuming that
the 300s timeout was deliberately chosen upstream, then setting the
retry interval to 360 would be sensible (= retry one minute after
timeout).  A patch is attached.

** Affects: mailman-suite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: mantic

** Patch added: "Add retry setting to settings.py"
   
https://bugs.launchpad.net/bugs/2060293/+attachment/5761692/+files/settings.patch

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

Title:
  mailman3-web needs Q_CLUSTER retry setting

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


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

[Bug 2060293] Re: mailman3-web needs Q_CLUSTER retry setting

2024-04-06 Thread Marco van Zwetselaar

Fixed patch (previous patch had retry setting 450)

** Patch added: "settings.patch"
   
https://bugs.launchpad.net/ubuntu/+source/mailman-suite/+bug/2060293/+attachment/5761693/+files/settings.patch

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

Title:
  mailman3-web needs Q_CLUSTER retry setting

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


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

[Bug 2060276] Re: mailman3-web 0+20200530-2.1 fails to install

2024-04-05 Thread Marco van Zwetselaar

There is an even less invasive fix, namely to use 'import as' and import
re_path as url:

--- /usr/share/mailman3-web/urls.py.orig2024-04-05 07:56:38.119113883 
+   

 
+++ /usr/share/mailman3-web/urls.py 2024-04-05 08:09:09.912489281 +
@@ -17,7 +17,8 @@
 # Postorius.  If not, see .


-from django.conf.urls import include, url
+from django.conf.urls import include
+from django.urls import re_path as url
 from django.contrib import admin
 from django.urls import reverse_lazy
 from django.views.generic import RedirectView

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

Title:
  mailman3-web 0+20200530-2.1 fails to install

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


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

[Bug 2060276] Re: mailman3-web 0+20200530-2.1 fails to install

2024-04-05 Thread Marco van Zwetselaar

** Patch added: "mailman3-web-2.patch"
   
https://bugs.launchpad.net/ubuntu/+source/mailman-suite/+bug/2060276/+attachment/5761632/+files/mailman3-web-2.patch

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

Title:
  mailman3-web 0+20200530-2.1 fails to install

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


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

[Bug 1976364] [NEW] Circos requires liblist-moreutils-perl

2022-05-31 Thread Marco van Zwetselaar

Public bug reported:

When running circos in Jammy without liblist-moreutils-perl installed,
it gives this error:

*** REQUIRED MODULE(S) MISSING OR OUT-OF-DATE ***

You are missing one or more Perl modules, require newer versions, or
some modules failed to load. Use CPAN to install it as described in this
tutorial

http://www.circos.ca/documentation/tutorials/configuration/perl_and_modules

missing List::MoreUtils

Installing liblist-moreutils-perl fixes the issue.

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


** Tags: jammy

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

Title:
  Circos requires liblist-moreutils-perl

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


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

[Bug 1934944] Re: power-profiles-daemon package conflicts with TLP

2021-09-12 Thread Marco van Zwetselaar

Well spotted and diagnosed by the initial bug reporter, and many thanks
to the maintainers working on this.

Just to make this bug report more easy to find, as its title doesn't
give this away: the TLP service fails to start on Ubuntu Hirsute 21.04
due to issue #1934944.

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

Title:
  power-profiles-daemon package conflicts with TLP

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934944/+subscriptions


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

[Bug 1942074] [NEW] Deja-Dup notifications appear in German

2021-08-30 Thread Marco van Zwetselaar

Public bug reported:

Thank you for maintaining this useful piece of software.

The issue: notifications from Deja Dup appear in German, whereas my
system and user locale are set to en_GB.  Deja dup's UI language is
correctly English.  It appears to be just the notifications that pop up
which are in German.

This is on a plain vanilla Ubuntu 21.04, with Deja Dup 42.7-1ubuntu1.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: deja-dup 42.7-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 30 14:01:29 2021
InstallationDate: Installed on 2020-11-13 (289 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to hirsute on 2021-05-07 (115 days ago)
modified.conffile..etc.logrotate.d.apport: [modified]
mtime.conffile..etc.logrotate.d.apport: 2020-11-14T00:02:50.449077

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  Deja-Dup notifications appear in German

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1942074/+subscriptions


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

[Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

2021-06-07 Thread Marco van Zwetselaar

Confirming that gnome-shell 3.38.4-1ubuntu3~21.04.1 resolves the issue.
Thank you for your work, it is much appreciated.

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions

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

[Bug 1875227] [NEW] dogtag-ipa-renew-agent-submit on freeipa-client fails to find pwdfile.txt

2020-04-26 Thread Marco van Zwetselaar

Public bug reported:

Since upgrade to 20.04, these two lines are logged every 6 hours on my
FreeIPA client machines:

Running enrollment/cadata helper 
"/usr/lib/certmonger/dogtag-ipa-renew-agent-submit".
Error opening "/etc/apache2/nssdb/pwdfile.txt": No such file or directory.

It appears to be looking for pwdfile.txt in the wrong directory.  There
is a pwdfile.txt in /etc/ipa/nssdb.

As I could not find a way to configure dogtag-ipa-renew-agent-submit
(its man page only mentions the host property in /etc/ipa/default.conf),
I have symlinked /etc/ipa/nssdb to /etc/apache2/nssdb as a temporary
workaround.

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


** Tags: focal

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

Title:
  dogtag-ipa-renew-agent-submit on freeipa-client fails to find
  pwdfile.txt

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

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

[Bug 1875217] [NEW] /usr/lib/tmpfiles.d/certmonger.conf references path below legacy directory /var/run/

2020-04-26 Thread Marco van Zwetselaar

Public bug reported:

The systemd-tmpfiles service (on 20.04) logs this line in syslog:

Apr 26 14:36:55 mysystem systemd-tmpfiles[94920]:
/usr/lib/tmpfiles.d/certmonger.conf:3: Line references path below legacy
directory /var/run/, updating /var/run/certmonger → /run/certmonger;
please update the tmpfiles.d/ drop-in file accordingly.

Changing the line to read "d /run/certmonger 0755 root root" resolves
the issue.

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


** Tags: focal

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

Title:
  /usr/lib/tmpfiles.d/certmonger.conf references path below legacy
  directory /var/run/

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

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

[Bug 1773843] Re: cannot upgrade freeipa-server

2019-09-05 Thread Marco van Zwetselaar

> there is no dogtag-pki in 19.04, so you can't do that

I'm aware.  I built the package from Disco sources with the server
packages enabled (ONLY_CLIENT=0), thinking that would be the closest to
what will go into 20.04 LTS.

As I'm rolling out a fresh deployment, I could either go with Bionic and
upgrade a live deployment to 20.04 LTS next year, or "slide into it"
from pre-release packages while considering my deployment tentative (and
possibly having to restart from scratch).

I'd like to go for the second, but I suppose starting from Disco source
isn't the way to do this?

BTW, just did a fresh install of the Disco 4.7.2 (+ server) packages,
and they work just fine.  The issue is/was in the upgrade.

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

Title:
  cannot upgrade freeipa-server

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

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

[Bug 1773843] Re: cannot upgrade freeipa-server

2019-09-04 Thread Marco van Zwetselaar

Just tried upgrade from current Bionic (4.7.0~pre1+git20180411-2ubuntu2)
to a local build from Disco sources (4.7.2-1ubuntu1).  Commented out
ONLY_CLIENT=1 in debian/rules to build the server packages.

After fixing some minor issues*, the upgrade goes through until
"RemoteRetrieveError: Failed to authenticate to CA REST API" happens at
the step "Migrating certificate profiles to LDAP".

I've looked all over but couldn't find a fix or workaround. Has this
been solved? Can I help?

BTW: suggest retitling this bug to "cannot upgrade freeipa-server:
Failed to authenticate to CA REST API.

*) Will report separately, with patches.

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

Title:
  cannot upgrade freeipa-server

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

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

[Bug 1830825] Re: /usr/lib/tiger/systems/default/config misspells "export" as "expot"

2019-08-05 Thread Marco van Zwetselaar

This bug also occurs on Bionic.

Additionally, the same line that misspells 'export' also misspells
'MAILER' as 'MAILE'.  Seems the upstream maintainer had a bad R-day.

I'm somewhat surprised that a package aimed at improving system security
would have these bugs.  Is this something the security team should take
a look at?


** Tags added: bionic

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

Title:
   /usr/lib/tiger/systems/default/config misspells "export" as "expot"

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

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

[Bug 1816887] [NEW] clBLAS aborts with OpenCL Error -11 in makeGemmKernel

2019-02-20 Thread Marco van Zwetselaar

Public bug reported:

Executing any of the clblas.gemm functions in libclBLAS.so.2.12.0
(libclblas2 2.12-1build1 on bionic) aborts the calling program with this
error message:

OpenCL error -11 [...] clblas-2.12/src/library/blas/xgemm.cc:244: void
makeGemmKernel(_cl_kernel**, cl_command_queue, const char*, const char*,
const unsigned char**, size_t*, const char*): Assertion `false' failed.

The error occurs when the backend is an OpenCL 1.1 device.  This
includes all GPUs supported by libclc through mesa-opencl-icd (Clover),
that is effectively all AMD GPUs.

The error can be easily reproduced by running the example from the
upstream README.md[1] on a machine with an AMD GPU, with environment
entry OCL_ICD_VENDORS=mesa.icd.

This bug also affects all BLAS functionality in libarrayfire-opencl3, as
can be seen by running e.g.  examples/benchmarks/blas or any of the
lin_algebra examples from the libarrayfire-doc package.

The good news is, there is a fix :-)  I have submitted this PR[2]
upstream, and am attaching a dquilt-ready patch as upstream releases
(and even pulls to master) are very infrequent.

[1] https://github.com/clMathLibraries/clBLAS#example
[2] https://github.com/clMathLibraries/clBLAS/pull/342

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

** Patch added: "Patch removes the -cl-std kernel build option"
   
https://bugs.launchpad.net/bugs/1816887/+attachment/5240444/+files/remove-cl-std-build-option

** Description changed:

  Executing any of the clblas.gemm functions in libclBLAS.so.2.12.0
  (libclblas2 2.12-1build1 on bionic) aborts the calling program with this
  error message:
  
  OpenCL error -11 [...] clblas-2.12/src/library/blas/xgemm.cc:244: void
  makeGemmKernel(_cl_kernel**, cl_command_queue, const char*, const char*,
  const unsigned char**, size_t*, const char*): Assertion `false' failed.
  
  The error occurs when the backend is an OpenCL 1.1 device.  This
  includes all GPUs supported by libclc through mesa-opencl-icd (Clover),
  that is effectively all AMD GPUs.
  
  The error can be easily reproduced by running the example from the
  upstream README.md[1] on a machine with an AMD GPU, with environment
- entry OCL_ICD_VENDORS set to mesa.icd.
+ entry OCL_ICD_VENDORS=mesa.icd.
  
  This bug also affects all BLAS functionality in libarrayfire-opencl3, as
  can be seen by running e.g.  examples/benchmarks/blas or any of the
  lin_algebra examples from the libarrayfire-doc package.
  
- The good news is, the fix is simple.  I have submitted this PR[2]
+ The good news is, there is a fix :-)  I have submitted this PR[2]
  upstream, and am attaching a dquilt-ready patch as upstream releases
  (and even pulls to master) are very infrequent.
  
  [1] https://github.com/clMathLibraries/clBLAS#example
  [2] https://github.com/clMathLibraries/clBLAS/pull/342

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

Title:
  clBLAS aborts with OpenCL Error -11 in makeGemmKernel

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

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

[Bug 1797553] Re: file-roller extract and replace does not replace

2018-10-12 Thread Marco van Zwetselaar

Sorry about that, this is 18.04 bionic.  Have tagged the bug.

** Tags added: bionic

** Description changed:

  When extracting a file over an existing file, clicking "Replace" in the
  dialog that asks to confirm overwriting a file, does not replace the
  file.
  
- Reproduce: 
+ Reproduce:
  - Open any archive (I've tested zip and 7z)
  - Right click a file and extract
  - Edit the extracted file so you can see that it will not be replaced
- - Right click the and extract the file again, to the same file name
+ - Right click and extract the file again, to the same file name
  - In the dialog asking whether to replace the file, click "Replace".
- - File confirms extraction, however the file was *not* replaced by the copy 
from the archive
+ - File roller confirms extraction, however the file was *not* replaced by the 
copy from the archive

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

Title:
  file-roller extract and replace does not replace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1797553/+subscriptions

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

[Bug 1797553] [NEW] file-roller extract and replace does not replace

2018-10-12 Thread Marco van Zwetselaar

Public bug reported:

When extracting a file over an existing file, clicking "Replace" in the
dialog that asks to confirm overwriting a file, does not replace the
file.

Reproduce: 
- Open any archive (I've tested zip and 7z)
- Right click a file and extract
- Edit the extracted file so you can see that it will not be replaced
- Right click the and extract the file again, to the same file name
- In the dialog asking whether to replace the file, click "Replace".
- File confirms extraction, however the file was *not* replaced by the copy 
from the archive

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  file-roller extract and replace does not replace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1797553/+subscriptions

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

[Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

2018-08-14 Thread Marco van Zwetselaar

Added gnome-shell to affected packages, as the issue is independent of
gnome-power-manager.

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847001/+subscriptions

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

[Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

2018-08-14 Thread Marco van Zwetselaar

Adding some more information. Running the following as root in a gnome
terminal:

   SYSFILE=/sys/class/backlight/intel_backlight/brightness
   OLD_VAL=$(cat $SYSFILE)
   NEW_VAL=$((OLD_VAL + 100))

   T0=$(date +%N)
   time echo $NEW_VAL  | tee $SYSFILE
   T1=$(date +%N)

   echo "Total time (millis): $(((T1 - T0)/1000))"

Gives the following:

   real0m0.002s
   user0m0.002s
   sys 0m0.001s
   Total time (millis): 3502

In other words, the write to sysfs returns in 2ms (and indeed,
brightness changes instantly), but it takes 3502ms for control to get
back to the prompt.

During that time, the system seems to hang, but keypresses are
collected: they are all echoed to the terminal right after the command
returns.  So the question then is: where are the 3 seconds spent?

I'm happy to experiment if someone has instructions.

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847001/+subscriptions

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

[Bug 828296] Re: [Latitude E6220/E6420] Brightness hotkeys are sluggish

2018-08-14 Thread Marco van Zwetselaar

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

** This bug has been marked a duplicate of bug 847001
   Adjusting display brightness is very slow on several Dell laptops

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

Title:
  [Latitude E6220/E6420] Brightness hotkeys are sluggish

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

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

[Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

2018-08-14 Thread Marco van Zwetselaar

Bug reappeared in 18.04.

Dell Precision M4800, running the standard Ubuntu Gnome shell desktop
(on Xorg), Intel Graphics.  No issues in 16.04 (or perhaps a tiny
delay?), but unworkable in 18.04.

Both Fn-Up/Down and `echo value | sudo tee brightness` exhibit the delay
(~2-3 seconds normally). Notable is that the brightness seems to change
*immediately* after echoing into sysfs, so all the delay occurs in the
return of the call back to the prompt.

In /sys/class/backlight I have only intel_backlight. No difference with
or without Backlight option in xorg.conf, nor with the
acpi_backlight=vendor kernel param.

Also notable: when performing the brightness change in a virtual
terminal, it is *instantaneous*.  The issue only occurs in the graphical
VT running the desktop environment.

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847001/+subscriptions

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

[Bug 1775672] Re: virtualbox-dkms installation hangs in 18.04 (with secure boot)

2018-07-20 Thread Marco van Zwetselaar

The problem is that the DKMS hook in virtualbox-dkms starts a whiptail
dialog explaining that a new signing key will be enrolled in the MOK
database, but this dialog does not get displayed, which is why the
system appears to hang.

Below is the output of 'pstree' showing the stack of commands and the
whiptail content.

Secondary issue (with DKMS): I have a signing key in the MOK database
already (like commenter #4), with which I have always used signed the
vbox drivers, so I do not want to enrol a _new_ signing key. So even if
I would see the dialog, it does not present the appropriate option.

I have tried this with aptitude, apt, dpkg --configure, both inside and
outside of a 'screen' session (to make sure I was on a plain console),
but the dialog does not show up in any of these cases.

This is the pstree output:

└─aptitude,5796
   ├─sh,11827 -c DPKG_NO_TSTP=1 dpkg --configure -a
   └─dpkg,11828 --configure -a
   └─virtualbox-dkms,11829 /var/lib/dpkg/info/virtualbox-dkms.postinst 
configure 5.2.10-dfsg-6ubuntu18.04.1
  └─common.postinst,11830 /usr/lib/dkms/common.postinst virtualbox 
5.2.10 /usr/share/virtualbox-dkms  5.2.10-dfsg-6ubuntu18.04.1
 └─dkms,12103 /usr/sbin/dkms build -m virtualbox -v 5.2.10 -k 
4.15.0-24-generic
└─dkms,12120 /usr/sbin/dkms build -m virtualbox -v 5.2.10 -k 
4.15.0-24-generic
   └─frontend,15868 -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
  ├─update-securebo,15882 
/usr/sbin/update-secureboot-policy --enroll-key
  └─whiptail,15897 --backtitle Package configuration 
--title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Y our system 
has UEFI Secure Boot enabled.\012\012UEFI Secure Boot requires additional 
configuration to work with third-party drivers.\012\012The system will assist 
you in configuring UEFI Secure Boot. To permit the use of third-party drivers, 
a new Machine-Owner Key (MOK) has been generated. This key now needs to be 
enrolled in your system's \012firmware.\012\012To ensure that this change is 
being made by you as an authorized user, and not by an attacker, you must 
choose a password now and then confirm the change after reboot using the same 
password, in both the\012"Enroll MOK" and "Change Secure Boot state" menus that 
will be presented to you when this system reboots.\012\012If you proceed but do 
not confirm the password upon reboot, Ubuntu will still be able to boot on your 
system but any hardware that requires third-party drivers to work correctly may 
not be usable. 17 208

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

Title:
  virtualbox-dkms installation hangs in 18.04 (with secure boot)

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

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

[Bug 1775672] Re: virtualbox-dkms installation hangs in 18.04 (with secure boot)

2018-07-20 Thread Marco van Zwetselaar

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

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

Title:
  virtualbox-dkms installation hangs in 18.04 (with secure boot)

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

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

[Bug 1749646] [NEW] suggests docker but should be docker.io

2018-02-14 Thread Marco van Zwetselaar

Public bug reported:

The htcondor package suggests the 'docker' package, whereas the
intention is to suggest the 'docker.io' package.

The docker package contains a window manager component that is unrelated
to HTCondor.  The docker.io package has the container manager that
HTCondor provides specific support for.

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


** Tags: artful

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

Title:
  suggests docker but should be docker.io

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

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

[Bug 1633251] Re: Crashes when installing on Ubuntu 16.10

2018-01-26 Thread Marco van Zwetselaar

Problem still exists with Ubuntu 17.10 server.  Segfault during standard
install of gridengine-master.

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

Title:
  Crashes when installing on Ubuntu 16.10

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

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

[Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

2017-07-05 Thread Marco van Zwetselaar

I actually spent time tracking down this 'bug' because on my upgrade
17.04 servers I kept seeing:

  * Ubuntu 16.10 will reach end of life on Thursday, July 20, 2017
 How to upgrade from 16.10 to 17.04:
 - https://ubu.one/upgY2Z

making me wonder if my upgrade was botched or something.  I have little
against the feature in general (though I would certainly make it opt-in
rather than opt-out), but this motd is confusing.

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

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

[Bug 1685802] Re: ownership on /var/spool/sms directories incorrect

2017-04-24 Thread Marco van Zwetselaar

Setting smsd's effective group to 'smsd' (in /etc/default/smstools)
seems to me the better option.  That way users can be given access to
the smstools spool directories (by adding them to group 'smsd') without
granting them access to the "raw" modems (which would happen if they
were added to 'dialout').

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

Title:
  ownership on /var/spool/sms directories incorrect

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

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

[Bug 1685802] [NEW] ownership on /var/spool/sms directories incorrect

2017-04-24 Thread Marco van Zwetselaar

Public bug reported:

As installed out of the box on Ubuntu, the primary group of smsd is
smsd.  It is also member of group dialout.  This makes sense because
smsd needs access to modem devices, which normally are crw-rw for
root:dialout.

As configured in /etc/default/smstools, smsd runs with effective group
dialout.  Though this makes sense, it is not strictly necessary, given
that smsd is a member of group dialout.

Smsd's spool directories (/var/spool/sms/*) are rwxrwsr-t for smsd:smsd.
Thus to give a user permission to send SMS it suffices to add them to
group smsd.  This gives them write access to /var/spool/sms/outgoing.
Additionally, due to the setgid when they put a file there, it will be
owned user:smsd.

So far, so good.  Smsd has ownership of the outgoing directory, so can
read and r(re)move the file.  However, it gives the error "Cannot handle
/var/spool/sms/outgoing/somefile.sms: Access denied. Check the file and
directory permissions."

As is apparent from the files in the sent and failed spools (when smsd
is run with effective group smsd instead of dialout), what smsd is
trying to do is to *take ownership* of the file.  This however it cannot
do: it is not a privileged user and its effective user nor group match
the files owner or group.

There are two solutions: chown the /var/spool/sms directories to
smsd:dialout (while keeping effective group dialout), or set smsd's
effective group in /etc/default/smstools to smsd (while keeping
/var/spool/sms owned smsd:smsd).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: smstools 3.1.15-1.2
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 24 13:32:23 2017
InstallationDate: Installed on 2015-12-04 (507 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: smstools
UpgradeStatus: Upgraded to xenial on 2016-04-25 (364 days ago)

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


** Tags: amd64 apport-bug xenial

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/smstools/+bug/1685802/+attachment/4867336/+files/JournalErrors.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/smstools/+bug/1685802/+attachment/4867335/+files/Dependencies.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/smstools/+bug/1685802/+attachment/4867337/+files/ProcEnviron.txt

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

Title:
  ownership on /var/spool/sms directories incorrect

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

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

[Bug 1143282] Re: Unable to add podcasts in rhythmbox

2017-03-22 Thread Marco van Zwetselaar

This problem still persists in Xenial (16.04), but I may have spotted
the cause.  Checking my apt log, a libc upgrade had taken place before I
tried to update my podcast feeds, and I hadn't since rebooted.  Libc
upgrades prompt for a system reboot - which I usually defer.  As for #3,
a reboot fixed the problem.

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

Title:
  Unable to add podcasts in rhythmbox

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

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

[Bug 1573221] Re: Regression on 4.3.8 upgrade: clients fail to connect

2016-05-05 Thread Marco van Zwetselaar

Original reporter here: the issue is resolved, with the qualification
that at my site (AD configuration) this required the installation of
winbind. Installing winbind was necessary and sufficient to resolve the
issue both in 4.3.8 and 4.3.9.

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1573221] Re: Regression on 4.3.8 upgrade: clients fail to connect

2016-04-26 Thread Marco van Zwetselaar

@mmaurice Have you checked that winbindd is actually running?

IIRC between 4.1 and 4.2 the parameter for winbindd in the 'server
services =' line in /etc/samba/smb.conf changed from 'winbind' to
'winbindd'. This will have been picked up automatically if the line only
had "+" and "-" entries, or was absent altogether. However if you
explicitly specified the services, then if 'winbind' was there, you'll
need to change it to 'winbindd'.

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1573221] Re: Regression on 4.3.8 upgrade: clients fail to connect

2016-04-25 Thread Marco van Zwetselaar

Confirming that installing winbind resolves the issue. Thank you @bernd-
eg.

I would propose that winbind be upgraded to a Recommends rather than a
Suggests for the Samba package.

** Tags added: regression-update

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1572301] Re: Regression with 4.3.8 upgrade, Mac OS X machines can't connect

2016-04-25 Thread Marco van Zwetselaar

The other bug #1573221 was resolved by installing winbind (which is a
Suggests of the Samba package). You may want to try if this resolves
this bug as well.

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

Title:
  Regression with 4.3.8 upgrade, Mac OS X machines can't connect

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

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

[Bug 1573221] Re: Regression on 4.3.8 upgrade: clients fail to connect

2016-04-22 Thread Marco van Zwetselaar

I just downgraded back to 4.1.6, hoping to get our domain controllers
operational again, but the samba-ad-dc service fails to start with:
Unknown process model 'standard'.

In the smbd log file (attached) I note entries "msg: schema: metadata
tdb not initialized at
../source4/dsdb/samdb/ldb_modules/schema_load.c:117". This seems to
suggest a backwards-incompatible database change from 4.1.6 to 4.3.8
makes reverting impossible?

Is there a way to return to a working situation while this bug is being
fixed? These are production domain controllers ...


** Attachment added: "downgraded 4.1.6 smbd log"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573221/+attachment/4642493/+files/downgraded.smbd.log

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1573221] Re: Regression on 4.3.8 upgrade: clients fail to connect

2016-04-22 Thread Marco van Zwetselaar

Attaching smbclient debug output at log level 10

** Attachment added: "smbclient debug log"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573221/+attachment/4642469/+files/smbclient.log

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1573221] Re: Regression on 4.3.8 upgrade: clients fail to connect

2016-04-22 Thread Marco van Zwetselaar

Attaching the smbd log file at debuglevel 10.

** Attachment added: "smbd log file"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573221/+attachment/4642461/+files/smbd.log

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1573221] Re: Regression on 4.3.8 upgrade: clients fail to connect

2016-04-21 Thread Marco van Zwetselaar

** Description changed:

  Since the upgrade from 4.1.6 to 4.3.8 on our Samba domain controllers on
  Ubuntu 14.04, clients fail to connect. Tested with Windows 7, Windows
  Server 12 and Samba clients.
  
  $ smbclient -L dc01 -U Administrator
  session setup failed: NT_STATUS_OBJECT_NAME_NOT_FOUND
  
+ In the server logs I see:
+ > smbd[20632]: [2016/04/21 21:05:43.093606,  1] 
../source3/smbd/sesssetup.c:281(reply_sesssetup_and_X_spnego)
+ > smbd[20632]:   Failed to generate session_info (user and group token) for 
session setup: NT_STATUS_OBJECT_NAME_NOT_FOUND
+ 
  The Windows clients cannot access shares and (quite critically) the RSAT
  tools such as ADUC can't be used to manage the domain.
  
  May be related to bug #1572301 where issues from other client platforms
  are reported.

** Description changed:

  Since the upgrade from 4.1.6 to 4.3.8 on our Samba domain controllers on
  Ubuntu 14.04, clients fail to connect. Tested with Windows 7, Windows
  Server 12 and Samba clients.
  
  $ smbclient -L dc01 -U Administrator
  session setup failed: NT_STATUS_OBJECT_NAME_NOT_FOUND
  
  In the server logs I see:
- > smbd[20632]: [2016/04/21 21:05:43.093606,  1] 
../source3/smbd/sesssetup.c:281(reply_sesssetup_and_X_spnego)
- > smbd[20632]:   Failed to generate session_info (user and group token) for 
session setup: NT_STATUS_OBJECT_NAME_NOT_FOUND
+ smbd[20632]: [2016/04/21 21:05:43.093606,  1] 
../source3/smbd/sesssetup.c:281(reply_sesssetup_and_X_spnego)
+ smbd[20632]:   Failed to generate session_info (user and group token) for 
session setup: NT_STATUS_OBJECT_NAME_NOT_FOUND
  
  The Windows clients cannot access shares and (quite critically) the RSAT
  tools such as ADUC can't be used to manage the domain.
  
  May be related to bug #1572301 where issues from other client platforms
  are reported.

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1572301] Re: Regression with 4.3.8 upgrade, Mac OS X machines can't connect

2016-04-21 Thread Marco van Zwetselaar

@Marc Deslauriers have filed comment #4 as new bug #1573221.

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

Title:
  Regression with 4.3.8 upgrade, Mac OS X machines can't connect

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

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

[Bug 1573221] [NEW] Regression on 4.3.8 upgrade: clients fail to connect

2016-04-21 Thread Marco van Zwetselaar

Public bug reported:

Since the upgrade from 4.1.6 to 4.3.8 on our Samba domain controllers on
Ubuntu 14.04, clients fail to connect. Tested with Windows 7, Windows
Server 12 and Samba clients.

$ smbclient -L dc01 -U Administrator
session setup failed: NT_STATUS_OBJECT_NAME_NOT_FOUND

The Windows clients cannot access shares and (quite critically) the RSAT
tools such as ADUC can't be used to manage the domain.

May be related to bug #1572301 where issues from other client platforms
are reported.

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

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

Title:
  Regression on 4.3.8 upgrade: clients fail to connect

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

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

[Bug 1572301] Re: Regression with 4.3.8 upgrade, Mac OS X machines can't connect

2016-04-21 Thread Marco van Zwetselaar

Also affects smbclient, Windows 12 Server, Windows 7 clients.

$ smbclient -L //dc01 -U Administrator
session setup failed: NT_STATUS_OBJECT_NAME_NOT_FOUND

Critical issue for shops running Samba as AD domain controller:
management of the domain is now impossible as the RSAT tools (ADUC, etc)
stop working.

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

Title:
  Regression with 4.3.8 upgrade, Mac OS X machines can't connect

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-03-15 Thread Marco van Zwetselaar

Confirming that kernel 4.2.0-34.39 in current Wily does not have the
bug.

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-03-13 Thread Marco van Zwetselaar

Confirming that 4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603091448
works fine here too. @jsalisbury thanks for going after this bug.

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-03-07 Thread Marco van Zwetselaar

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603071309 has the bug,
sorry :-/

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-03-03 Thread Marco van Zwetselaar

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603031453 has the bug.

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-03-03 Thread Marco van Zwetselaar

Just tested 4.2.8-040208ckt2.201603021201 and it exhibits the bug.

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-03-03 Thread Marco van Zwetselaar

Ah, spotted the (probable) directory now: 
http://kernel.ubuntu.com/~jsalisbury/lp1549967/ 
That's a s/88/99/ and the bug is totally unrelated. Downloading kernel and 
headers now.

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-03-03 Thread Marco van Zwetselaar

@jsalisbury I think you copied the files to the wrong directory. I
guessed from timestamps that they might be in
http://kernel.ubuntu.com/~jsalisbury/lp1498667/ . I am now running
without issues on kernel 4.1.0-040100.201603021615 from that directory.
However I didn't install the headers deb so I guess that I'm running
with any DKMS modules.

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-02-29 Thread Marco van Zwetselaar

Confirming this bug: up to date plain vanilla 15.10, not on VMWare. Kernel 
4.2.0-27 was and is fine. Kernel 4.2.0-30: 
- hangs after typing password in graphical login, no response to keyboard or 
mouse (haven't checked ssh, but machine seems to be still alive)
-can login on text console via Ctl-Alt-F1 on graphical login, but hangs when 
returning to graphical screen with Alt-F7.

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

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

[Bug 1504531] [NEW] apt show gibberish in package description

2015-10-09 Thread Marco van Zwetselaar

Public bug reported:

I am not sure whether to report this bug against apt, the vim-snipmate
package, or as a translation bug. It seems to be located in the en_GB
translation of the package description for vim-snipmate.

On my Ubuntu Vivid (locale en_GB) the output of "apt show vim-snipmate"
contains this section:

--- snip ---
 for (i = 0; i < count; i++) {
 .
 Project-Id-Version: ddtp-ubuntu
 Report-Msgid-Bugs-To: FULL NAME 
 POT-Creation-Date: 2014-09-03 08:41+0200
 PO-Revision-Date: 2014-05-06 13:30+
 Last-Translator: FULL NAME 
 Language-Team: English (United Kingdom) 
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: 8bit
 X-Launchpad-Export-Date: 2014-09-04 23:31+
 X-Generator: Launchpad (build 17196)
 .
 To go to the next item in the loop, simply  over to it; if there is
--- snip ---

The middle part starting with "Project-Id-Version" upto "X-Generator"
doesn't belong here. I have checked and it isn't present in the
"DEBIAN/control" file in vim-snipmate_0.87-2_all.deb. Instead the
control file contains the expected single '}' character at that
location.

Grepping through /var/lib/apt I have found the injected bit in the vim-snipmate 
description in
/var/lib/apt/lists/partial/tz.archive.ubuntu.com_ubuntu_dists_vivid_universe_i18n_Translation-en%5fGB.bz2
It is not present in the vim-snipmate description in 
/var/lib/apt/lists/partial/tz.archive.ubuntu.com_ubuntu_dists_vivid_universe_i18n_Translation-en.bz

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apt 1.0.9.7ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct  9 15:01:02 2015
InstallationDate: Installed on 2013-09-28 (740 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: apt
UpgradeStatus: Upgraded to vivid on 2015-05-27 (135 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  apt show gibberish in package description

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

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

[Bug 1476199] [NEW] rsync rule in logcheck database needs update

2015-07-20 Thread Marco van Zwetselaar

Public bug reported:

This rule in /etc/logcheck/ignore.d.server/rsync:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyncd\[[0-9]+\]: (wrote|sent)
[0-9]+ bytes  (read|received) [0-9]+ bytes  total size [0-9]+$

does not match rsync output, as rsync uses the comma as a thousands
separator in the byte counts. Suggested:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyncd\[[0-9]+\]: (wrote|sent)
[0-9,]+ bytes  (read|received) [0-9,]+ bytes  total size [0-9,]+$

or strictly:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyncd\[[0-9]+\]: (wrote|sent)
[0-9]{1,3}(,[0-9]{3})* bytes  (read|received) [0-9]{1,3}(,[0-9]{3})*
bytes  total size [0-9]{1,3}(,[0-9]{3})*$

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

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

Title:
  rsync rule in logcheck database needs update

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

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

[Bug 1476199] [NEW] rsync rule in logcheck database needs update

2015-07-20 Thread Marco van Zwetselaar

Public bug reported:

This rule in /etc/logcheck/ignore.d.server/rsync:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyncd\[[0-9]+\]: (wrote|sent)
[0-9]+ bytes  (read|received) [0-9]+ bytes  total size [0-9]+$

does not match rsync output, as rsync uses the comma as a thousands
separator in the byte counts. Suggested:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyncd\[[0-9]+\]: (wrote|sent)
[0-9,]+ bytes  (read|received) [0-9,]+ bytes  total size [0-9,]+$

or strictly:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyncd\[[0-9]+\]: (wrote|sent)
[0-9]{1,3}(,[0-9]{3})* bytes  (read|received) [0-9]{1,3}(,[0-9]{3})*
bytes  total size [0-9]{1,3}(,[0-9]{3})*$

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

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

Title:
  rsync rule in logcheck database needs update

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

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

[Bug 1434525] Re: Router solicitation blocked, makes network-manager complain

2015-07-01 Thread Marco van Zwetselaar

Confirming that the patch in #2 solves the issue.

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

Title:
  Router solicitation blocked, makes network-manager complain

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

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

[Bug 1357471] Re: Samba4 AD DC randomly dies, error: Did not manage to negotiate mandetory feature SIGN for dcerpc auth_level 6.

2015-03-30 Thread Marco van Zwetselaar

My two Samba AD DCs run in an environment with frequent network
interruptions due to power cuts. It seems that even very brief network
interruptions trigger this issue, which then doesn't resolve itself when
connectivity is restored.

After most network interruptions, the following three messages repeat in 
log.samba every 5 seconds, and 'sudo samba-tool drs showrepl' shows failures. A 
'sudo service samba-ad-dc restart' is required to get everything working again.
- Update failed:  Miscellaneous failure (see text): Matching credential 
(GC/{other-dc}.{domain}/{domain}@{DOMAIN}) not found
- Did not manage to negotiate mandetory feature SIGN for dcerpc auth_level 6
- Failed to bind to uuid {uuid-1} for 
{uuid-1}@ncacn_ip_tcp:{uuid-2}._msdcs.{domain}[1024,seal,krb5] 
NT_STATUS_ACCESS_DENIED.

In a country with on average 12 powercuts *per day*, which despite a
huge arsenal of stabilisers and UPS-es do cause brief network
interruptions, you can imagine that this issue is a major pain in the
behind :-/

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

Title:
  Samba4 AD DC randomly dies, error: Did not manage to negotiate
  mandetory feature SIGN for dcerpc auth_level 6.

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

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

[Bug 1357471] Re: Samba4 AD DC randomly dies, error: Did not manage to negotiate mandetory feature SIGN for dcerpc auth_level 6.

2015-03-30 Thread Marco van Zwetselaar

My two Samba AD DCs run in an environment with frequent network
interruptions due to power cuts. It seems that even very brief network
interruptions trigger this issue, which then doesn't resolve itself when
connectivity is restored.

After most network interruptions, the following three messages repeat in 
log.samba every 5 seconds, and 'sudo samba-tool drs showrepl' shows failures. A 
'sudo service samba-ad-dc restart' is required to get everything working again.
- Update failed:  Miscellaneous failure (see text): Matching credential 
(GC/{other-dc}.{domain}/{domain}@{DOMAIN}) not found
- Did not manage to negotiate mandetory feature SIGN for dcerpc auth_level 6
- Failed to bind to uuid {uuid-1} for 
{uuid-1}@ncacn_ip_tcp:{uuid-2}._msdcs.{domain}[1024,seal,krb5] 
NT_STATUS_ACCESS_DENIED.

In a country with on average 12 powercuts *per day*, which despite a
huge arsenal of stabilisers and UPS-es do cause brief network
interruptions, you can imagine that this issue is a major pain in the
behind :-/

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

Title:
  Samba4 AD DC randomly dies, error: Did not manage to negotiate
  mandetory feature SIGN for dcerpc auth_level 6.

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

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

[Bug 1389595] [NEW] Error installing nagios3-doc: All `Format' sections are invalid.

2014-11-05 Thread Marco van Zwetselaar

Public bug reported:

Upon 'apt-get install nagios3-doc' in Ubuntu 14.10, I get this error:

Preparing to unpack .../nagios3-doc_3.5.1-1ubuntu2_all.deb ...
Unpacking nagios3-doc (3.5.1-1ubuntu2) ...
Processing triggers for doc-base (0.10.6) ...
Processing 1 added doc-base file...
Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
Note: `install-docs --verbose --check file_name' may give more details about 
the above error.

The output of 'install-docs --verbose --check /usr/share/doc-base/nagios3':
Warning in `/usr/share/doc-base/nagios3', line 9: file 
`/usr/share/nagios3/htdocs/docs/index.html' does not exist.
Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
/usr/share/doc-base/nagios3: Fatal error found, the file won't be registered.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: nagios3-doc 3.5.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov  5 12:27:51 2014
Dependencies:
 
InstallationDate: Installed on 2013-09-28 (402 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: nagios3
UpgradeStatus: Upgraded to utopic on 2014-10-30 (5 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  Error installing nagios3-doc: All `Format' sections are invalid.

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

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

[Bug 1389595] Re: Error installing nagios3-doc: All `Format' sections are invalid.

2014-11-05 Thread Marco van Zwetselaar

** Description changed:

  Upon 'apt-get install nagios3-doc' in Ubuntu 14.10, I get this error:
  
  Preparing to unpack .../nagios3-doc_3.5.1-1ubuntu2_all.deb ...
  Unpacking nagios3-doc (3.5.1-1ubuntu2) ...
  Processing triggers for doc-base (0.10.6) ...
  Processing 1 added doc-base file...
  Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
  Note: `install-docs --verbose --check file_name' may give more details about 
the above error.
  
  The output of 'install-docs --verbose --check /usr/share/doc-base/nagios3':
  Warning in `/usr/share/doc-base/nagios3', line 9: file 
`/usr/share/nagios3/htdocs/docs/index.html' does not exist.
  Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
  /usr/share/doc-base/nagios3: Fatal error found, the file won't be registered.
  
+ Looking in /usr/share/doc/nagios3-doc, there is a softlink html pointing to 
+ /usr/share/nagios3/htdocs/docs/. That directory contains only a directory 
+ images, which is empty.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nagios3-doc 3.5.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  5 12:27:51 2014
  Dependencies:
-  
+ 
  InstallationDate: Installed on 2013-09-28 (402 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: nagios3
  UpgradeStatus: Upgraded to utopic on 2014-10-30 (5 days ago)

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

Title:
  Error installing nagios3-doc: All `Format' sections are invalid.

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

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

[Bug 1389595] [NEW] Error installing nagios3-doc: All `Format' sections are invalid.

2014-11-05 Thread Marco van Zwetselaar

Public bug reported:

Upon 'apt-get install nagios3-doc' in Ubuntu 14.10, I get this error:

Preparing to unpack .../nagios3-doc_3.5.1-1ubuntu2_all.deb ...
Unpacking nagios3-doc (3.5.1-1ubuntu2) ...
Processing triggers for doc-base (0.10.6) ...
Processing 1 added doc-base file...
Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
Note: `install-docs --verbose --check file_name' may give more details about 
the above error.

The output of 'install-docs --verbose --check /usr/share/doc-base/nagios3':
Warning in `/usr/share/doc-base/nagios3', line 9: file 
`/usr/share/nagios3/htdocs/docs/index.html' does not exist.
Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
/usr/share/doc-base/nagios3: Fatal error found, the file won't be registered.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: nagios3-doc 3.5.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov  5 12:27:51 2014
Dependencies:
 
InstallationDate: Installed on 2013-09-28 (402 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: nagios3
UpgradeStatus: Upgraded to utopic on 2014-10-30 (5 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  Error installing nagios3-doc: All `Format' sections are invalid.

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

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

[Bug 1389595] Re: Error installing nagios3-doc: All `Format' sections are invalid.

2014-11-05 Thread Marco van Zwetselaar

** Description changed:

  Upon 'apt-get install nagios3-doc' in Ubuntu 14.10, I get this error:
  
  Preparing to unpack .../nagios3-doc_3.5.1-1ubuntu2_all.deb ...
  Unpacking nagios3-doc (3.5.1-1ubuntu2) ...
  Processing triggers for doc-base (0.10.6) ...
  Processing 1 added doc-base file...
  Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
  Note: `install-docs --verbose --check file_name' may give more details about 
the above error.
  
  The output of 'install-docs --verbose --check /usr/share/doc-base/nagios3':
  Warning in `/usr/share/doc-base/nagios3', line 9: file 
`/usr/share/nagios3/htdocs/docs/index.html' does not exist.
  Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are 
invalid.
  /usr/share/doc-base/nagios3: Fatal error found, the file won't be registered.
  
+ Looking in /usr/share/doc/nagios3-doc, there is a softlink html pointing to 
+ /usr/share/nagios3/htdocs/docs/. That directory contains only a directory 
+ images, which is empty.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nagios3-doc 3.5.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  5 12:27:51 2014
  Dependencies:
-  
+ 
  InstallationDate: Installed on 2013-09-28 (402 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: nagios3
  UpgradeStatus: Upgraded to utopic on 2014-10-30 (5 days ago)

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

Title:
  Error installing nagios3-doc: All `Format' sections are invalid.

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

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

62 matches

Mail list logo