Bug#1056001: fixed in spamassassin 4.0.0-8

2023-11-26 Thread Martin Schwenke
On Thu, 23 Nov 2023 16:50:06 + Debian FTP Masters
 wrote:
> Source: spamassassin
> Source-Version: 4.0.0-8
> Done: Noah Meyerhans 
> 
> We believe that the bug you reported is fixed in the latest version of
> spamassassin, which is due to be installed in the Debian FTP archive.

Thanks for the quick fix.  I notice that this has made it to testing.

The original bug is in the version in stable:

$ apt policy spamassassin
spamassassin:
  Installed: 4.0.0-6
  Candidate: 4.0.0-6
  Version table:
 4.0.0-7 2
  2 https://deb.debian.org/debian testing/main amd64 Packages
 *** 4.0.0-6 500
500 https://deb.debian.org/debian stable/main amd64 Packages
100 /var/lib/dpkg/status
 3.4.6-1 500
500 https://deb.debian.org/debian oldstable/main amd64 Packages
 3.4.2-1+deb10u3 500
500 https://deb.debian.org/debian oldoldstable/main amd64 Packages

Can we please also have a fixed package in stable-updates?

Thanks...

peace & happiness,
martin



Bug#1056001: spamd: user_prefs include files are only read on the first scan

2023-11-17 Thread Martin Schwenke
On Fri, 17 Nov 2023 21:27:40 -0800, Noah Meyerhans 
wrote:

> Thank you.  Fixed with 
> https://salsa.debian.org/debian/spamassassin/-/commit/5e3d193894de527a22dac427a308a4387dc4d890
> 
> 
> Will upload this to unstable in the not-too-distant future.

Thank you!

Might this fix make it into a bug fix for Debian 12.3?

Thanks again...

peace & happiness,
martin



Bug#1056001: spamd: user_prefs include files are only read on the first scan

2023-11-15 Thread Martin Schwenke
Package: spamd
Version: 4.0.0-6
Severity: normal

Dear Maintainer,

When using spamd and the user_prefs file contains include directives, the
included files are only read on the first scan.  This is because the per-user
rules are cleared on user change, but the list of included files is not
cleared.

This was reported upstream via:

  https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8130

and fixed in the trunk via commit:

  
https://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin.pm?r1=1913789=1913803_format=h

The fix is in /usr/share/perl5/Mail/SpamAssassin.pm, which is in the 
spamassassin package, but I believe the fix only affects the spamd
package.

I have applied the patch by hand, in-place in the above file on my Debian
system and it appears to fix the problem.

It would be excellent if you could apply this fix in the package for
Debian stable.

Thanks...

peace & happiness,
martin

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500, 
'stable'), (500, 'oldstable'), (2, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-23-cloud-amd64 (SMP w/4 CPU threads)
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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages spamd depends on:
ii  init-system-helpers  1.65.2
ii  rsyslog [system-log-daemon]  8.2302.0-1
ii  spamassassin 4.0.0-6

spamd recommends no packages.

spamd suggests no packages.

-- Configuration Files:
/etc/default/spamd changed:
OPTIONS="--create-prefs --max-children 5 --max-spare=3 --helper-home-dir"
PIDFILE="/run/spamd.pid"
[ -z "$1" ] || /etc/init.d/spamd-virtual $1 || true


-- no debconf information



Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

2023-07-06 Thread Martin Schwenke
Adding more data...

I have been seeing this on bookworm (both the machine running "apt
update" and the machine running apt-cacher-ng):

W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: The 
following signatures were invalid: BADSIG 0E98404D386FA1D9 Debian Archive 
Automatic Signing Key (11/bullseye) 
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is 
not signed.

On Fri, 28 Jan 2022 20:45:00 +0530 Pirate Praveen
 wrote:

> I have seen this on another sid chroot. So I had to remove
> /var/lib/apt/* inside the chroot and debrepo/dists directory in
> apt-cacher-ng's cache directory. I'm not sure if it can be fixed in
> apt-cacher-ng.

The above workaround has fixed it for me... for now.

peace & happiness,
martin



Bug#991124: googleapi: Error 403: Only files with binary content can be downloaded

2021-07-14 Thread Martin Schwenke
Package: rclone
Version: 1.53.3-1+b5
Severity: important
Tags: upstream
X-Debbugs-Cc: mar...@meltin.net

Dear Maintainer,

I am using rclone's sync command to maintain a local backup of my
Google Drive.  It worked well until a few days ago but recently
syncing certain files has been failing with an error like this:

  2021/07/15 08:47:06 ERROR : Attempt 3/3 failed with 1 errors and: failed to 
open source object: open file failed: googleapi: Error 403: Only files with 
binary content can be downloaded. Use Export with Docs Editors files., 
fileNotDownloadable

This upstream GitHub issue for rclone appears to address the issue:

  https://github.com/rclone/rclone/issues/5455

The same annoying workaround listed in that issue works sometimes for
me but the problem soon returns after files have been modified.

I downloaded the latest rclone beta
(https://beta.rclone.org/rclone-beta-latest-linux-amd64.zip) and it
fixes the issue.

Can you please consider updating to 1.56.0 when it is released (or
backporting the relevant fix)?  I think this will be needed for stable
because the Google Drive support is quite broken without this fix.

Thanks...

peace & happiness,
martin

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

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 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 /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages rclone depends on:
ii  libc6  2.31-12

rclone recommends no packages.

rclone suggests no packages.

-- no debconf information



Bug#970266: mount: comment=x-gvfs-show not removed from options for non-reoot user

2020-09-24 Thread Martin Schwenke
On Fri, 25 Sep 2020 11:28:06 +1000, Martin Schwenke 
wrote:

> I'm sending a patch for an upstream fix...

Patch is attached.

peace & happiness,
martin
>From 97a071f7f1bf5274c027ee92fc0f6ca629ecdd65 Mon Sep 17 00:00:00 2001
From: Martin Schwenke 
Date: Fri, 25 Sep 2020 11:16:39 +1000
Subject: [PATCH] mount.cifs: ignore comment mount option

mount.cifs currently complains about the "comment" option:

  CIFS: Unknown mount option "comment=foo"

mount(8) on Linux says:

  The command mount does not pass the mount options unbindable,
  runbindable, private, rprivate, slave, rslave, shared, rshared,
  auto, noauto, comment, x-*, loop, offset and sizelimit to the
  mount. helpers.

So if mount.cifs decides to re-read /etc/fstab it should ignore the
comment option.

A lot of online posts say to use comment=x-gvfs-show as an option to
have a Linux file manager display a mountpoint for a user mountable
filesystem.  While the "comment=" part is superfluous when combined
with an x-* option, the problem is still difficult to debug.

Signed-off-by: Martin Schwenke 
---
 mount.cifs.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/mount.cifs.c b/mount.cifs.c
index 4feb397..5d43c00 100644
--- a/mount.cifs.c
+++ b/mount.cifs.c
@@ -777,6 +777,8 @@ static int parse_opt_token(const char *token)
 		return OPT_BKUPGID;
 	if (strcmp(token, "nofail") == 0)
 		return OPT_NOFAIL;
+	if (strcmp(token, "comment") == 0)
+		return OPT_IGNORE;
 	if (strncmp(token, "x-", 2) == 0)
 		return OPT_IGNORE;
 	if (strncmp(token, "snapshot", 8) == 0)
-- 
2.28.0



Bug#970266: mount: comment=x-gvfs-show not removed from options for non-reoot user

2020-09-24 Thread Martin Schwenke
On Thu, 24 Sep 2020 17:45:25 +0200, Chris Hofstaedtler
 wrote:

> It appears mount.cifs somehow re-adds a comment=... option from
> /etc/fstab when calling mount(), for "user"-style mounts.
> 
> $ strace -ttf -bexecve -s3 mount /mnt
>  execve("/sbin/mount.cifs", ["/sbin/mount.cifs", "//x/y", "/mnt", "-o", 
> "rw,noexec,nosuid,nodev,username=ch,user"], 0x7ffc40273cb0 /* 42 vars */) = 0
> 
> In a root-strace of mount.cifs, you'll see:
>  mount("//x/y$", ".", "cifs", MS_NOSUID|MS_NODEV, 
> "ip=10.100.0.52,unc=x\\y,noauto,comment=foo,uid=1000,gid=1000,user=ch,pass=yolo")
>  = -1 EINVAL (Invalid argument)
> 
> Doesn't appear to be a util-linux/mount problem to me.

Right.  It turns out that mount.cifs doesn't trust the options passed
by a user so it re-reads them and neglects to ignore the comment
option.

I'm sending a patch for an upstream fix...

Thanks for working this out!

peace & happiness,
martin



Bug#970266: mount: comment=x-gvfs-show not removed from options for non-reoot user

2020-09-14 Thread Martin Schwenke
On Mon, 14 Sep 2020 08:45:04 +0200, Chris Hofstaedtler
 wrote:

> * Martin Schwenke  [200914 01:48]:
> [..]
> > I add this to /etc/fstab:
> > 
> >   //digby/flac/mnt/flac   cifs
> > noauto,user,username=guest,password=,ro,soft,vers=3,comment=x-gvfs-show 
> >  0   0
> > 
> > "mount /mnt/flac" as root works without a problem.
> >   
> [..]
> > /var/log/kern.log shows:
> > 
> >   Sep 14 09:38:05 kloof kernel: [183360.156767] CIFS: Attempting to mount 
> > //digby/flac
> >   Sep 14 09:38:05 kloof kernel: [183360.156809] CIFS: Unknown mount option 
> > "comment=x-gvfs-show"
> > 
> > So it appears that the comment is being passed to the helper, which
> > does not follow the documentation.  
> 
> Please be so kind and run this on your machine:
> 
> $ strace -ttf -bexecve -s3 mount /mnt/flac
> 
> And look for the execve() line, probably something like this:
> 
> pid 1687840] 06:42:51.534769 execve("/sbin/mount.cifs", 
> ["/sbin/mount.cifs", "/mnt/flac", "-o", ... 
> 
> Please check if comment=x-gvfs-show actually appears there.
> In my limited testing I found mount does not pass a comment=...
> option to mount.cifs.

Wow!  Correct:

  [pid 267848] 17:03:57.171924 execve("/sbin/mount.cifs",
  ["/sbin/mount.cifs", "//digby/flac", "/mnt/flac", "-o", 
"ro,noexec,nosuid,nodev,username=guest,password=,soft,vers=3,user"], 
0x7ffd9d0a9fa0 /* 42 vars */strace: Process 267848 detached

So the question is how does that option get passed to the kernel?
Surely mount.cifs doesn't re-read /etc/fstab?  Also, the problem does
not occur for root.

I might try wrapping /sbin/mount.cifs in a script to log invocations,
including arguments and parent process.  Perhaps there's a surprise I'm
not expecting (e.g. systemd?).

Wow...

peace & happiness,
martin



Bug#970266: mount: comment=x-gvfs-show not removed from options for non-reoot user

2020-09-13 Thread Martin Schwenke
Package: mount
Version: 2.36-3
Severity: normal

Dear Maintainer,

I'm trying to mount a CIFS share as a non-root user.  I would like to
be able to do this via the file manager so I add a
"comment=x-gvfs-show" option to the relevant line in /etc/fstab.  The
mount command fails because "comment=x-gvfs-show" is an unknown mount
option.

mount(8) says:

   The command mount does not pass the mount options unbindable,
   runbindable, private, rprivate, slave, rslave, shared, rshared,
   auto, noauto, comment, x-*, loop, offset and sizelimit to the
   mount. helpers.  All other options are used in a comma-
   separated list as an argument to the -o option.

I add this to /etc/fstab:

  //digby/flac/mnt/flac   cifs
noauto,user,username=guest,password=,ro,soft,vers=3,comment=x-gvfs-show  0  
 0

"mount /mnt/flac" as root works without a problem.

However, as a normal user I see:

  $ mount /mnt/flac
  mount error(22): Invalid argument
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg)

/var/log/kern.log shows:

  Sep 14 09:38:05 kloof kernel: [183360.156767] CIFS: Attempting to mount 
//digby/flac
  Sep 14 09:38:05 kloof kernel: [183360.156809] CIFS: Unknown mount option 
"comment=x-gvfs-show"

So it appears that the comment is being passed to the helper, which
does not follow the documentation.

If I use the "x-gvfs-show" option (without "comment=") the the mount
succeeds as a non-root user.

I expect the "comment" option to work the same way for both root and
non-root users.

Thanks!

peace & happiness,
martin


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

Kernel: Linux 5.7.0-3-amd64 (SMP w/8 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mount depends on:
ii  libblkid1  2.36-3
ii  libc6  2.31-3
ii  libmount1  2.36-3
ii  libsmartcols1  2.36-3
ii  util-linux 2.36-3

mount recommends no packages.

Versions of packages mount suggests:
ii  nfs-common  1:1.3.4-4

-- no debconf information



Bug#939906: python3-spf-engine: policyd-spf produces Python stack trace on DNS timeout

2019-09-09 Thread Martin Schwenke
Package: python3-spf-engine
Version: 2.9.0-4
Severity: normal

Dear Maintainer,

When policyd-spf from postfix-policyd-spf-python times out during
a DNS request a Python traceback is printed:

Sep 10 07:11:18 bilbo policyd-spf[21475]:   File "/usr/bin/policyd-spf", line 
11, in #012load_entry_point('spf-engine==2.9.0', 'console_scripts', 
'policyd-spf')()
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/spf_engine/policyd_spf.py", line 102, in 
main#012peruser, peruserconfigData)
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/spf_engine/__init__.py", line 545, in 
_spfcheck#012res = heloquery.check()
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/spf.py", line 591, in check#012spf = 
self.dns_spf(self.d)
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/spf.py", line 1160, in dns_spf#012a = [t 
for t in self.dns_txt(domain) if RE_SPF.match(t)]
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/spf.py", line 1210, in dns_txt#012dns_list 
= self.dns(domainname, rr,ignore_void=ignore_void)
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/spf.py", line 1354, in dns#012for k, v in 
DNSLookup(name, qtype, self.strict, timeout):
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/spf.py", line 131, in DNSLookup_dnspython#012   
 answers = dns.resolver.query(name, qtype)
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/dns/resolver.py", line 1102, in query#012
lifetime)
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/dns/resolver.py", line 992, in query#012
timeout = self._compute_timeout(start, lifetime)
Sep 10 07:11:18 bilbo policyd-spf[21475]:   File 
"/usr/lib/python3/dist-packages/dns/resolver.py", line 799, in 
_compute_timeout#012raise Timeout(timeout=duration)
Sep 10 07:11:18 bilbo policyd-spf[21475]: dns.exception.Timeout: The DNS 
operation timed out after 30.000346899032593 seconds

I would expect a warning to be logged but not a Python traceback.  I am
guessing that spf_engine should be catching the exception.

Perhaps this should be minor instead of normal, but this makes
monitoring logs via logcheck much harder because the stack traces
dominate the logs.

Thanks...

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 python3-spf-engine depends on:
ii  python3  3.7.3-1
ii  python3-authres  1.2.0-1
ii  python3-spf  2.0.13-1

python3-spf-engine recommends no packages.

python3-spf-engine suggests no packages.

-- no debconf information



Bug#931604: /usr/sbin/dovecot: Logged fix for SSL configuration issue is potentially useless

2019-07-08 Thread Martin Schwenke
Package: dovecot-core
Version: 1:2.3.4.1-5
Severity: important
File: /usr/sbin/dovecot

Dear Maintainer,

During upgrade from stretch to buster the following was logged:

  Jul  6 22:06:27 digby dovecot: config: Warning: please set 
ssl_dh= /etc/dovecot/dh.pem

I did a variation of this (using /etc/dovecot/private/dh.pem instead).

After this, when attempting to connect to imaps, I got:

  Jul  6 22:06:27 digby dovecot: imap-login: Error: Failed to initialize SSL 
server context: Can't load DH parameters: error:1408518A:SSL 
routines:ssl3_ctx_ctrl:dh key too small: user=<>, rip=192.168.20.32, 
lip=192.168.20.5, session=

It was very difficult to find any information about the "dh key too small"
message.  :-(

I ended up looking here:

  https://wiki.dovecot.org/SSL/DovecotConfiguration

and this recommended using:

  openssl dhparam 4096 > dh.pem

After I did this the "dh key too small" messages stopped and I was able
to connect.

The recommended command that was logged was not useful.  The
ssl-parameters.dat file was last updated some time in 2015 and is
probably out of date.  So, I guess that either the ssl-parameters.dat
file needs to be somehow updated or the log message should provide
a more foolproof hint, perhaps a pointer to the wiki.

Thanks...

peace & happiness,
martin


-- Package-specific info:

dovecot configuration
-
# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 ()
# OS: Linux 4.19.0-5-amd64 x86_64 Debian 10.0 
# Hostname: digby.PRIVATE-DOMAIN-ELIDED
mail_location = maildir:~/Maildir
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 {
  args = scheme=CRYPT username_format=%u /etc/dovecot/users
  driver = passwd-file
}
plugin {
  sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = " imap"
ssl_cert = 
ii  dovecot-imapd 1:2.3.4.1-5
pn  dovecot-ldap  
pn  dovecot-lmtpd 
pn  dovecot-lucene
pn  dovecot-managesieved  
pn  dovecot-mysql 
pn  dovecot-pgsql 
pn  dovecot-pop3d 
ii  dovecot-sieve 1:2.3.4.1-5
pn  dovecot-solr  
pn  dovecot-sqlite
pn  dovecot-submissiond   
ii  ntp   1:4.2.8p12+dfsg-4

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

-- no debconf information



peace & happiness,
martin



Bug#900936: Appeared in testing with the last version of geoclue-2.0

2018-08-22 Thread Martin Schwenke
On Sun, 19 Aug 2018 11:49:52 +0200 =?UTF-8?Q?Arnaud_Court=c3=a8s?=
 wrote:
> I run Debian Testing on my computer and before geoclue-2.0 upgrade on 
> 2018-08-17, Redshift worked perfectly fine with geoclue in version 2.4.7.
> 
> Now, everytime Redshift is launched, I have the following error : 
> "Unable to start GeoClue client: 
> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' 
> disallowed, no agent for UID 1000.
> Unable to connect to GeoClue."
> 
> I tried the little trick by modifying the geoclue.conf file and adding a 
> specific section for Redshift but it doesn't work for me and doesn't 
> change anything in the error.
> 
> Maybe something more to do on geoclue-2.0 package ? Something else to 
> try on my side ? Redshift is buggy ?

Same problem here.  :-(

So far the workarounds seem to assume knowledge of how all of this fits
together.  Right!  I have it working.  Here are some simple steps:

1. Install geoclue-2-demo

2. If you don't want to be asked if redshift can do geolocation, make
   the configuration change mentioned in message #25

   If you don't do this then there will be a pop-up each time
   redshift-gtk is started asking if redshift should be allowed to do
   geolocation.

3. Either logout+login to start the demo agent or run the demo agent by
   hand:

 /usr/lib/geoclue-2.0/demos/agent &

4. Now redshift-gtk (and, I suppose, redshift) should be able to
   connect to the demo agent when started.

peace & happiness,
martin



Bug#901594: DE-agnostic agent

2018-08-22 Thread Martin Schwenke
On Fri, 15 Jun 2018 11:33:56 +0200 Valentin Blot
 wrote:
> I don't use a DE. Maybe the "demo" agent should be renamed and enhanced
> into a "default" agent for all the people who don't use a DE?

That sounds like an excellent idea...

peace & happiness,
martin



Bug#892275: redshift: Unable to connect to GeoClue.

2018-08-16 Thread Martin Schwenke
On Mon, 02 Jul 2018 14:23:31 +0530 Ritesh Raj Sarraf 
wrote:
> On Sat, 2018-06-23 at 22:26 +, byanbyanroryan wrote:
> > ryan@pocketwee:~$ systemctl --user status redshift
> > ● redshift.service - Redshift display colour temperature adjustment
> >Loaded: loaded (/usr/lib/systemd/user/redshift.service; disabled;
> > vendor preset: enabled)
> >Active: inactive (dead)
> >  Docs: http://jonls.dk/redshift/
> 
> 
> Please enable it. That should solve the problem.

I have enabled the service and started it via:

  systemctl --user enable redshift
  systemctl --user start redshift

However, redshift-gtk still refuses to start.  :-(

Will downgrade geoclue-2.0 as per other suggestion...

peace & happiness,
martin



Bug#856485: Done: xpra: terminating xpra server destroys current X session

2018-08-07 Thread Martin Schwenke
I'm still seeing this with xpra 2.3.2+dfsg1-2+b1 on testing.

peace & happiness,
martin



Bug#884824: etckeeper: daily autocommit is run even though AVOID_DAILY_AUTOCOMMITS=1

2017-12-19 Thread Martin Schwenke
Following a suggestion, I found that if I run:

  systemctl stop etckeeper.timer

Then it is no longer listed by "systemctl list-units".

I should have spent more time reading systemctl(1):

  delete
   ...

   This command implicitly reloads the system manager configuration
   after completing the operation. Note that this command does not
   implicitly stop the units that are being disabled. If this is
   desired, either combine this command with the --now switch, or
   invoke the stop command with appropriate arguments later.

peace & happiness,
martin



Bug#884824: etckeeper: daily autocommit is run even though AVOID_DAILY_AUTOCOMMITS=1

2017-12-19 Thread Martin Schwenke
Package: etckeeper
Version: 1.18.7-1
Severity: normal

Dear Maintainer,

Some time ago I disabled daily autocommits for my /etc/ directory:

  commit 1e123419c83f254aa27b831f8b268a8f575211dc
  Author: Martin Schwenke <mar...@meltin.net>
  Date:   Tue Sep 8 10:51:19 2015 +1000

  etckeeper: Be less automatic

  diff --git a/etckeeper/etckeeper.conf b/etckeeper/etckeeper.conf
  index 2aec35e..fd9cfb8 100644
  --- a/etckeeper/etckeeper.conf
  +++ b/etckeeper/etckeeper.conf
  @@ -18,7 +18,7 @@ DARCS_COMMIT_OPTIONS="-a"

   # Uncomment to avoid etckeeper committing existing changes
   # to /etc automatically once per day.
  -#AVOID_DAILY_AUTOCOMMITS=1
  +AVOID_DAILY_AUTOCOMMITS=1

   # Uncomment the following to avoid special file warning
   # (the option is enabled automatically by cronjob regardless).
   @@ -27,7 +27,7 @@ DARCS_COMMIT_OPTIONS="-a"
   # Uncomment to avoid etckeeper committing existing changes to 
   # /etc before installation. It will cancel the installation,
   # so you can commit the changes by hand.
  -#AVOID_COMMIT_BEFORE_INSTALL=1
  +AVOID_COMMIT_BEFORE_INSTALL=1

   # The high-level package manager that's being used.
   # (apt, pacman-g2, yum, dnf, zypper etc)

This has worked until recently.

Now I see daily autocommits again.  When I check /var/log/syslog I
see:

  Dec 18 16:06:26 rover systemd[1]: Starting Autocommit of changes in /etc 
directory...
  Dec 18 16:06:27 rover systemd[1]: Started Autocommit of changes in /etc 
directory.

It appears that a systemd job is active:

  $ systemctl list-units | grep etckeeper
  etckeeper.timer   
loaded active waiting   Daily autocommit of changes in /etc 
directory  

However, the comment in /etc/etckeeper/etckeeper.conf.dpkg-dist says:

  # Etckeeper includes both a cron job and a systemd timer, which each
  # can commit exiting changes to /etc automatically once per day.
  # To enable the systemd timer, run: systemctl enable etckeeper.timer
  # The cron job is enabled by default; to disable it, uncomment this next line.
  #AVOID_DAILY_AUTOCOMMITS=1

I certainly haven't enabled the the systemd timer.

Note that I don't seem to be able to disable the systemd timer:

  root@rover:/etc# systemctl disable etckeeper.timer
  root@rover:/etc# systemctl list-units | grep etckeeper
  etckeeper.timer   
loaded active waiting   Daily autocommit of changes in /etc 
directory   

Clearly, I'm not smart enough to use something as excellent as
systemd.  ;-)

I think that, as documented, the systemd job should not be enabled by
default.

Alternatively, /etc/etckeeper/daily could be modified to honour
AVOID_DAILY_AUTOCOMMITS=1.  Then it would not matter if the systemd
job is active and is immortal.  In that case a Linux user with over 20
years experience would still be able to disable the daily autocommit
in an expected way.  ;-)

Thanks...

peace & happiness,
martin


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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 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/dash
Init: systemd (via /run/systemd/system)

Versions of packages etckeeper depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  git1:2.15.1-1

Versions of packages etckeeper recommends:
ii  cron [cron-daemon]  3.0pl1-128.1

Versions of packages etckeeper suggests:
ii  sudo  1.8.21p2-2

-- Configuration Files:
/etc/etckeeper/etckeeper.conf changed:
VCS="git"
GIT_COMMIT_OPTIONS=""
HG_COMMIT_OPTIONS=""
BZR_COMMIT_OPTIONS=""
DARCS_COMMIT_OPTIONS="-a"
AVOID_DAILY_AUTOCOMMITS=1
AVOID_COMMIT_BEFORE_INSTALL=1
HIGHLEVEL_PACKAGE_MANAGER=apt
LOWLEVEL_PACKAGE_MANAGER=dpkg
PUSH_REMOTE=""


-- debconf information:
  etckeeper/purge: true



Bug#880950: shellcheck: Incorrect parsing of default value in variable

2017-11-05 Thread Martin Schwenke
Package: shellcheck
Version: 0.4.6-1
Severity: normal
Tags: upstream patch

Dear Maintainer,

Here's a snippet or screenshot that shows the problem:

#!/bin/sh
b=$(d=$(dirname "$0") ; cd -P "$d" || exit ; dirname "$PWD")
bar="${FOOBAR:-${b}/foobar.d}"
echo "$bar"

Here's what shellcheck currently says:

In foo.sh line 2:
b=$(d=$(dirname "$0") ; cd -P "$d" || exit ; dirname "$PWD")
^-- SC2030: Modification of d is local (to subshell caused by $(..)
expansion).

In foo.sh line 3:
bar="${FOOBAR:-${b}/foobar.d}"
^-- SC2031: d was modified in a subshell. That change might be lost.

Here's what I wanted or expected to see:

Nothing!

For more details please see shellcheck issue #950 at:

  https://github.com/koalaman/shellcheck/issues/950

This is fixed upstream though there is no release yet.  The patch is
at:

  
https://github.com/koalaman/shellcheck/commit/807d899f3b6139a61b644420d3f74b21bb0fb272

This is a regression to version 0.4.4, so I'm wondering if you could
apply this patch to fix the regression until there's a new shellcheck
release.

Thanks!

peace & happiness,
martin

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 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/dash
Init: systemd (via /run/systemd/system)

Versions of packages shellcheck depends on:
ii  libc6 2.24-17
ii  libffi6   3.2.1-6
ii  libgmp10  2:6.1.2+dfsg-1.1

shellcheck recommends no packages.

shellcheck suggests no packages.

-- no debconf information



Bug#875677: devscripts: mk-build-deps creates the build-dep package in the wrong directory

2017-10-31 Thread Martin Schwenke
On Wed, 13 Sep 2017 21:03:14 -0400 James McCoy 
wrote:
> Control: reassign -1 equivs 2.1.0
> Control: affects -1 + devscripts
> 
> On Wed, Sep 13, 2017 at 02:26:55PM +0200, Jiri Palecek wrote:
> > while making a build-dep package, mk-build-deps writes:
> > 
> > dpkg-deb: vytvářím balík ,,kwin-build-deps" v 
> > ,,../kwin-build-deps_5.10.5-2_i386.deb".
> > 
> > The package has been created.
> > Attention, the package has been created in the current directory,
> > not in ".." as indicated by the message above!
> > 
> > However, the generated package is not in the current directory as
> > stated, nor in the parent directory, but in $TMP. Please fix that, or
> > the message.
> 
> That message is generated by equivs-build.  That equivs-build actually
> honors $TMPDIR now is a recent change, which isn't documented in the man
> page and isn't reflected in the output, as noted above.

Right.  The real question is why build in $TMPDIR if not building
in /tmp when TMPDIR is unset?

I think you want the resulting package to end up in the current
directory.  This is an obvious result, as evidenced by the output of
the equivs-build command.

My opinion is that the "fix" for bug #660765 is a regression and should
be reverted.

peace & happiness,
martin



Bug#840570: xfce4-power-manager: Attempts to suspend again after opening lid

2016-10-21 Thread Martin Schwenke
On Thu, 13 Oct 2016 07:35:52 +1100 Martin Schwenke <mar...@meltin.net>
wrote:

> I suspend my laptop by closing the lid.  When I resume, by opening the
> lid, I then unlock the screen and I am greeted with a dialog saying:
> 
>   Authentication is required for suspending the system.
> 
> I can cancel this without any issues, except a notification saying:
> 
>   Power manager
> 
>   GDBus.Error.org.freedesktop.DBus.Error.NoReply: Method call timed out
> 
> This is slightly better than the situation before my last reboot,
> where the laptop re-suspended as soon as it had resumed after opening
> the lid.  I then had to press the Fn key to get it to resume again.

Thankfully, this has stopped happening.  Perhaps a useful update to some
related package came through.

Please cancel this bug... sorry for the false alarm...


peace & happiness,
martin



Bug#840570: xfce4-power-manager: Attempts to suspend again after opening lid

2016-10-12 Thread Martin Schwenke
Package: xfce4-power-manager
Version: 1.4.4-4
Severity: important

Dear Maintainer,

I suspend my laptop by closing the lid.  When I resume, by opening the
lid, I then unlock the screen and I am greeted with a dialog saying:

  Authentication is required for suspending the system.

I can cancel this without any issues, except a notification saying:

  Power manager

  GDBus.Error.org.freedesktop.DBus.Error.NoReply: Method call timed out

This is slightly better than the situation before my last reboot,
where the laptop re-suspended as soon as it had resumed after opening
the lid.  I then had to press the Fn key to get it to resume again.

I can see that xfce4-power-manager has not been updated for over a
year on my system.  Therefore, I assume that xfce4-power-manager
hasn't been updated to deal with recent changes in systemd.  Or should
I file this bug against systemd?

Thanks...

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

Kernel: Linux 4.7.0-1-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.24-3
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.10-1
ii  libdbus-glib-1-2  0.108-1
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libglib2.0-0  2.50.0-2
ii  libgtk2.0-0   2.24.31-1
ii  libnotify40.7.6-2
ii  libpango-1.0-01.40.3-2
ii  libpangocairo-1.0-0   1.40.3-2
ii  libupower-glib3   0.99.4-4
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxfce4ui-1-04.12.1-2
ii  libxfce4util7 4.12.1-2
ii  libxfconf-0-2 4.12.0-3
ii  libxrandr22:1.5.0-1
ii  upower0.99.4-4
ii  xfce4-power-manager-data  1.4.4-4

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   231-9
ii  xfce4-power-manager-plugins  1.4.4-4

xfce4-power-manager suggests no packages.

-- no debconf information

peace & happiness,
martin



Bug#821295: exfalso: fails to start - missing dependency on gir1.2-soup-2.4

2016-09-27 Thread Martin Schwenke
On Sun, 17 Apr 2016 13:21:37 +0100 Neil Williams 
wrote:
> Package: exfalso
> Version: 3.6.1-2
> Severity: important

> Installing gir1.2-soup-2.4 allows exfalso to start.

This is still an issue in exfalso 3.7.0-1.

peace & happiness,
martin



Bug#834790: [Aptitude-devel] Bug#834790: aptitude hangs at "Loading cache" when unable to download package list

2016-08-23 Thread Martin Schwenke
On Tue, 23 Aug 2016 20:23:10 +1000, Martin Schwenke <mar...@meltin.net>
wrote:

> So, the new behaviour does bother me!  I want "broken" sources.list
> lines to continue to generate a warning, allowing me to continue, rather
> than generating a "fatal" error... ;-)

Actually, there seems to be a workaround.  I can just quit aptitude
while it is displaying the "Loading cache" message.  When I re-run it,
it doesn't know that an error has occurred and it displays packages,
allowing me to upgrade packages as usual.

That alone seems to suggest that the error should not be fatal...

peace & happiness,
martin



Bug#834790: [Aptitude-devel] Bug#834790: aptitude hangs at "Loading cache" when unable to download package list

2016-08-23 Thread Martin Schwenke
I'm seeing this too.  I have a source that is only visible when my
laptop is on a particular network...

On Mon, 22 Aug 2016 11:11:17 +0100 "Manuel A. Fernandez Montecelo"
 wrote:

> Actually, I am not sure what to say about the new behaviour being good
> or not.  If it happened to me, I would quit aptitude and fix all the
> errors before wanting to proceed with any package viewing or
> installation, so the fact that it doesn't show any packages /after/
> showing errors wouldn't bother me.
> 
> I can see how other people can think otherwise (and thanks for reporting
> it, by the way), but in any case, my point was that at least it happens
> /after/ errors being shown (and not randomly in the absence of errors,
> or not showing packages but not showing errors either), people can
> associate the lack of packages in the screen with the previous errors,
> and it will occur to them that by fixing the source of the errors
> aptitude will be able to work fine.

Ahhh! But the old behaviour was convenient!  I could use the same
sources.list and happily ignore the failure when updating from a
network where the source is not accessible.  Now I will need to edit my
source.list to enable/disable that source when I switch networks.

So, the new behaviour does bother me!  I want "broken" sources.list
lines to continue to generate a warning, allowing me to continue, rather
than generating a "fatal" error... ;-)

peace & happiness,
martin



Bug#810295: WARNING: Serious error when reading debug info

2016-07-14 Thread Martin Schwenke
On Sun, 19 Jun 2016 17:50:14 + Max Dmitrichenko
 wrote:
> Package: valgrind
> Version: 1:3.11.0-1
> Followup-For: Bug #810295
> 
> Please find a debdiff in attachment. Backported from the upstream.

Thanks, this seems to work for me!

Is anyone able to build and upload?

Thanks...

peace & happiness,
martin



Bug#810295: WARNING: Serious error when reading debug info

2016-01-07 Thread Martin Schwenke
Package: valgrind
Version: 1:3.11.0-1
Severity: important

When I run valgrind against anything, I see warnings like this:

$ valgrind -q /bin/echo
--14923-- WARNING: Serious error when reading debug info
--14923-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.21.so:
--14923-- Ignoring non-Dwarf2/3/4 block in .debug_info
--14923-- WARNING: Serious error when reading debug info
--14923-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.21.so:
--14923-- Last block truncated in .debug_info; ignoring
--14923-- WARNING: Serious error when reading debug info
--14923-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.21.so:
--14923-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--14923-- WARNING: Serious error when reading debug info
--14923-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.21.so:
--14923-- Ignoring non-Dwarf2/3/4 block in .debug_info
--14923-- WARNING: Serious error when reading debug info
--14923-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.21.so:
--14923-- Last block truncated in .debug_info; ignoring
--14923-- WARNING: Serious error when reading debug info
--14923-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.21.so:
--14923-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4

This might not actually be a valgrind bug...

  $ dwarfdump -i 
/usr/lib/debug/.build-id/1c/3104f034cf1caf07cdc1c4a5f342610146ebe5.debug

  .debug_info
  dwarfdump ERROR:  attempting to print .debug_info:  DW_DLE_CU_LENGTH_ERROR 
(47) (47)
  attempting to continue.

  $ dpkg -S 
/usr/lib/debug/.build-id/1c/3104f034cf1caf07cdc1c4a5f342610146ebe5.debug
  libc6-dbg:amd64: 
/usr/lib/debug/.build-id/1c/3104f034cf1caf07cdc1c4a5f342610146ebe5.debug

So it might be a libc6 bug.

However, I'm only seeing it causes problems in valgrind so, I guess,
this seems a good place to start...  :-)

Thanks...

peace & happiness,
martin

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

Kernel: Linux 4.3.0-1-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages valgrind depends on:
ii  libc6  2.21-6
ii  libc6-dbg  2.21-6

Versions of packages valgrind recommends:
ii  gdb   7.10-1
pn  valgrind-dbg  

Versions of packages valgrind suggests:
pn  alleyoop  
pn  kcachegrind   
pn  valgrind-mpi  
pn  valkyrie  

-- no debconf information

peace & happiness,
martin



Bug#774328: [Pkg-samba-maint] Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.

2015-01-28 Thread Martin Schwenke
On Wed, 28 Jan 2015 15:52:11 +0100, Mathieu Parent
math.par...@gmail.com wrote:

 I use dh_systemd with overrides:
 http://anonscm.debian.org/cgit/pkg-samba/ctdb.git/tree/debian/rules
 
 ctdb.postinst (in the .deb) ends up with only:
 
 if [ -x /etc/init.d/ctdb ]; then
 update-rc.d ctdb defaults /dev/null || exit $?
 fi
 
 and /etc/init.d/ctdb is indeed executable (Is it on your machine Martin?).

Yes, it is executable.

peace  happiness,
martin


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



Bug#774328: [Pkg-samba-maint] Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.

2015-01-27 Thread Martin Schwenke
Hi Mathieu,

This has stopped failing.  While that's obviously excellent, I wish I
could explain it.  :-(

Perhaps a systemd update did something magic?  I've only just seen
Cameron Norman's suggestion from 2015-01-02 to try systemctl
daemon-reload.  That would have been a nice idea.  Not sure why I
didn't get an email from the bug system for Cameron's comment.  :-(
This was happening on my laptop where reboots are uncommon... so I
suppose a reboot could have fixed it too.

Do packages that provide systemd init need to set some sort of trigger
that causes a systemctl daemon-reload?  I just tried installing
proftpd-basic (random choice of daemon that I've never had installed
before), it starts and stops fine and I can't find any evidence of a
trigger like that, so that theory seems bogus.  :-(

Answers to questions below...

On Tue, 27 Jan 2015 14:51:46 +0100, Mathieu Parent
math.par...@gmail.com wrote:

 2015-01-16 9:20 GMT+01:00 Martin Schwenke mar...@meltin.net:

  Anything relevant in /var/log/{syslog,ctdb/log.ctdb}? journalctl -u
  ctdb.service?
 
  No, nothing at all.  It looks like it is failing somewhere in systemd.
 
 It's /var/log/ctdb/log.ctdb. Have you checked it too?

Yes, I had checked it and it was always empty, unless I ran
ctdbd_wrapper directly.  That's why I assumed a systemd problem.

Now it logs the expected failure due to broken configuration.  I'm
happy with that because I know enough if I want to configure CTDB from
this point...  :-)

 What journalctl --unit ctdb.service says ?
 
 Is there any red line in systemctl list-units?

Yeah, given that it now works I see the CTDB-specific failure.

Sorry that this was a waste of time and we couldn't work out why it was
happening.  :-(

peace  happiness,
martin


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



Bug#774328: [Pkg-samba-maint] Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.

2015-01-16 Thread Martin Schwenke
On Tue, 13 Jan 2015 11:26:48 +0100, Mathieu Parent
math.par...@gmail.com wrote:

 2014-12-31 23:16 GMT+01:00 Martin Schwenke mar...@meltin.net:

  # systemctl start ctdb
  Failed to start ctdb.service: Unit ctdb.service failed to load: No such 
  file or directory.
 [...]
 
 Couldn't reproduce here. But I need to test again in a clean VM.

Yikes!  :-(

 Anything relevant in /var/log/{syslog,ctdb/log.ctdb}? journalctl -u
 ctdb.service?

No, nothing at all.  It looks like it is failing somewhere in systemd.

Well, I do get this from selinux:

  Jan 16 18:52:20 rover kernel: audit: type=1107 audit(1421394740.536:41175): 
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='Unknown permission start for class system exe=/lib/systemd/systemd 
sauid=0 hostname=? addr=? terminal=?'

However, I am running in *permissive* mode, so selinux shouldn't be
getting in the way:

  # sestatus | grep -i mode
  Current mode:   permissive
  Mode from config file:  permissive

My gut is telling me that this has something to do with the selinux
message... but how can this happen in permissive mode?

 Was this machine migrated from wheezy? Do you have rsyslog installed?

Yes, this machine was probably upgraded from wheezy.  I have rsyslog
installed.

Do you know if there's a way of getting some debug out of systemd?

peace  happiness,
martin


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



Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.

2014-12-31 Thread Martin Schwenke
Package: ctdb
Version: 2.5.4+debian0-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

# systemctl start ctdb
Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or 
directory.
# ls -l /lib/systemd/system/ctdb.service
-rw-r--r--. 1 root root 306 Dec 15 04:30 /lib/systemd/system/ctdb.service

This is after a fresh install of the ctdb package.

I can't find anything useful logged anywhere.  Perhaps I need to
reboot to get systemd into a useful state?

However, I can restart other things:

  # systemctl restart wicd
  # systemctl restart dnsmasq
  #

So I guess this is a problem in the CTDB package.

I can make more progress by doing this:

  /usr/sbin/ctdbd_wrapper /run/ctdb/ctdbd.pid start

so I don't think No such file or directory is coming from the CTDB
startup.  It doesn't seem to get that far.  :-(

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500,
'stable'), (300, 'unstable') Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages ctdb depends on:
ii  iproute23.16.0-2
ii  libc6   2.19-13
ii  libpopt01.16-10
ii  libtalloc2  2.1.1-2
ii  libtdb1 1.3.1-1
ii  libtevent0  0.9.21-1
ii  lsb-base4.1+Debian13+nmu1
ii  psmisc  22.21-2
ii  sudo1.8.10p3-1
ii  tdb-tools   1.3.1-1
ii  time1.7-25

Versions of packages ctdb recommends:
ii  ethtool  1:3.16-1

Versions of packages ctdb suggests:
pn  libctdb-dev  none
ii  logrotate3.8.7-1+b1
ii  lsof 4.86+dfsg-1

-- Configuration Files:
/etc/sudoers.d/ctdb [Errno 13] Permission denied: u'/etc/sudoers.d/ctdb'

-- no debconf information

peace  happiness,
martin


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



Bug#773016: ctdb: Starting CTDB fails with Unable to open /var/lib/run/ctdb/.socket_lock

2014-12-13 Thread Martin Schwenke
Package: ctdb
Version: 2.5.4+debian0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

CTDB can't be started as packaged.

Shouldn't:

  --localstatedir=/var/lib

in debian/rules be:

  --localstatedir=/var

instead?

That would put the socket and the lock file in the right place
(/var/run/ctdb/).

Thanks...

peace  happiness,
martin

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (300, 
'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages ctdb depends on:
ii  iproute23.16.0-2
ii  libc6   2.19-13
ii  libpopt01.16-10
ii  libtalloc2  2.1.1-2
ii  libtdb1 1.3.1-1
ii  libtevent0  0.9.21-1
ii  lsb-base4.1+Debian13+nmu1
ii  psmisc  22.21-2
ii  sudo1.8.10p3-1
ii  tdb-tools   1.3.1-1
ii  time1.7-25

Versions of packages ctdb recommends:
ii  ethtool  1:3.16-1

Versions of packages ctdb suggests:
pn  libctdb-dev  none
ii  logrotate3.8.7-1+b1
ii  lsof 4.86+dfsg-1

-- Configuration Files:
/etc/default/ctdb changed [not included]
/etc/sudoers.d/ctdb [Errno 13] Permission denied: u'/etc/sudoers.d/ctdb'

-- 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#773016: closed by Jelmer Vernooij jel...@debian.org (Bug#773016: fixed in ctdb 2.5.4+debian0-2)

2014-12-13 Thread Martin Schwenke
On Sat, 13 Dec 2014 16:09:23 +, ow...@bugs.debian.org (Debian Bug
Tracking System) wrote:

 This is an automatic notification regarding your Bug report
 which was filed against the ctdb package:
 
 #773016: ctdb: Starting CTDB fails with Unable to open 
 /var/lib/run/ctdb/.socket_lock
 
 It has been closed by Jelmer Vernooij jel...@debian.org.
 
 Their explanation is attached below along with your original report.
 If this explanation is unsatisfactory and you have not received a
 better one in a separate message then please contact Jelmer Vernooij 
 jel...@debian.org by
 replying to this email.

Why not --localstatedir=/var ?  To me that looks like the simplest and
most correct fix.  It defaults to PREFIX/var and the standard thing to
do when building packages to install in /usr is to set
--localstatedir=/var.

Thanks...

peace  happiness,
martin


pgpktTmxLO5Iy.pgp
Description: OpenPGP digital signature


Bug#769977: auctex: Enabling bib-cite-minor-mode fails with (void-function make-local-hook)

2014-11-18 Thread Martin Schwenke
On Tue, 18 Nov 2014 18:00:31 +0100, Davide G. M. Salvetti
sa...@linux.it wrote:

 MS Probably already fixed in unstable.  However, I wanted to try to
 MS make sure that this gets fixed for jessie.  :-)
 
 I confirm that 11.88-1 already contains this patch.
 
 About fixing it for Jessie, I don't think that we can get an unblock on
 this issue given Jessie Freeze Policy guidelines
 https://release.debian.org/jessie/freeze_policy.html#guidelines-changes:
 
   - this bug severity level looks like normal to me, rather than
 important;
   - even if its severity level was important, the fix could not be done
 via unstable, because unstable already has 11.88-1;
   - fixes done via testing-proposed-updates need to be targeted for
 release critical bugs.
 
 If you think that the freeze policy allows an upload fixing this issue,
 please let me know: [...]

It doesn't look like it, does it?  :-(

Oh well, if I need auctex on a Jessie system then I'll use the
backport.  I'll jump to the next testing release on my main
machine anyway.

Thanks for educating me about the policy, preparing the patch... and for
maintaining the auctex package!  :-)

peace  happiness,
martin


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



Bug#769977: auctex: Enabling bib-cite-minor-mode fails with (void-function make-local-hook)

2014-11-17 Thread Martin Schwenke
Package: auctex
Version: 11.87-3
Severity: normal
Tags: upstream patch

Known bug here:

  https://www.mail-archive.com/bug-auctex@gnu.org/msg01999.html

Patch here:

  
http://git.savannah.gnu.org/cgit/auctex.git/commit/bib-cite.el?id=9e0fae3919ba0fcd1ed2923f14574780db42174a

Probably already fixed in unstable.  However, I wanted to try to make
sure that this gets fixed for jessie.  :-)

Thanks...


-- Package-specific info:

Content of '/usr/share/emacs/site-lisp/auctex'

d41d8cd98f00b204e9800998ecf8427e  /usr/share/emacs/site-lisp/auctex/.nosearch
3366a99dd44e27fa57e0bcc130c4fa1c  /usr/share/emacs/site-lisp/auctex/bib-cite.el
6674b961058a19d2ff2f15c9d6d39272  
/usr/share/emacs/site-lisp/auctex/context-en.el
f5ed983cd477814f04e4a63affd4f323  
/usr/share/emacs/site-lisp/auctex/context-nl.el
0cbe483d1a5567ea46a104f4f1cd7784  /usr/share/emacs/site-lisp/auctex/context.el
b133f33d0c97e1ac061d9e5c88774781  
/usr/share/emacs/site-lisp/auctex/font-latex.el
f176261b5a5511cbe1401ee72ffb8947  
/usr/share/emacs/site-lisp/auctex/images/amstex.xpm
d33121019448617a3ad3bcafdeb8db40  
/usr/share/emacs/site-lisp/auctex/images/bibtex.xpm
1a43d6438010bceb374ab0a5f2bd05a8  
/usr/share/emacs/site-lisp/auctex/images/dropdown.xpm
41f1ae0341ae2e307d92a7b8b815f868  
/usr/share/emacs/site-lisp/auctex/images/dvipdf.xpm
2e4b8669b0168f32247411be3f999437  
/usr/share/emacs/site-lisp/auctex/images/dvips.xpm
55f7600cadc3a209e94bacf6bbc42a7c  
/usr/share/emacs/site-lisp/auctex/images/error.xpm
c29ad797273fd27201a40bd939a95fe0  
/usr/share/emacs/site-lisp/auctex/images/exec.xpm
79b958849511c67d6b13ef9f5b3673e8  
/usr/share/emacs/site-lisp/auctex/images/execbibtex.xpm
a8570e26e9f96b6f527cdbe218d6c55f  
/usr/share/emacs/site-lisp/auctex/images/execdvips.xpm
e647bc601aef2dc71b134a989df1adff  
/usr/share/emacs/site-lisp/auctex/images/execerror.xpm
4610ec6133f89ceb441c43dfee077361  
/usr/share/emacs/site-lisp/auctex/images/execpdftex.xpm
c9cd1fc9fe4fd122cbf900fae654a67b  
/usr/share/emacs/site-lisp/auctex/images/exectex.xpm
6a6b9af945d4735f048ea8e475f8d9b8  
/usr/share/emacs/site-lisp/auctex/images/execviewdvi.xpm
466466f6d1867510b058a9c184ffce5d  
/usr/share/emacs/site-lisp/auctex/images/execviewpdf.xpm
39d8ccaffb40b0c118e000f45272db05  
/usr/share/emacs/site-lisp/auctex/images/execviewps.xpm
6767e2583c668dcb47495197b9e8cb65  
/usr/share/emacs/site-lisp/auctex/images/gv.xpm
ff9c61ef5148a0cacd5422d7c0d99396  
/usr/share/emacs/site-lisp/auctex/images/jumpdvi.xpm
ece6608586b591f50f20d17cdb316a1c  
/usr/share/emacs/site-lisp/auctex/images/ltx-symb-turn-off.xpm
b1f10de33dcf1b5ca9ac6155c13683a3  
/usr/share/emacs/site-lisp/auctex/images/ltx-symb-turn-on.xpm
44e35faa18ab34f3c13ac3b0082bcc47  
/usr/share/emacs/site-lisp/auctex/images/pdftex.xpm
84673eb20ac3be7bf0eb4e84e23e828f  
/usr/share/emacs/site-lisp/auctex/images/prverr16.xpm
59e6a0dddb00ab16c4209a2e4c6e283d  
/usr/share/emacs/site-lisp/auctex/images/prverr20.xpm
30dc2ada41625cb24ea459bd62f7386c  
/usr/share/emacs/site-lisp/auctex/images/prverr24.xbm
225929f8131bdd7b9b8207494a59619a  
/usr/share/emacs/site-lisp/auctex/images/prverr24.xpm
0dac3d8eb00c902037cc5fa6a03e53e3  
/usr/share/emacs/site-lisp/auctex/images/prvtex-cap-up.xpm
40feb30f80d3606f32ba54b57ba18af5  
/usr/share/emacs/site-lisp/auctex/images/prvtex12.xbm
e1b3c9d6a6eb6fb6f096736cdfc059cf  
/usr/share/emacs/site-lisp/auctex/images/prvtex12.xpm
32406fc4b893b48d2996c424f61ea238  
/usr/share/emacs/site-lisp/auctex/images/prvtex16.xbm
cc4101ee6a3ab6a1f4e9991b91b3ff0b  
/usr/share/emacs/site-lisp/auctex/images/prvtex16.xpm
d4dbe057a8d3b2facd61cf7583c1e97c  
/usr/share/emacs/site-lisp/auctex/images/prvtex20.xpm
f25ba1b984b095c9c561e5443f3d77a3  
/usr/share/emacs/site-lisp/auctex/images/prvtex24.xbm
28ac0855d853f606dd91e3cfacaa8a14  
/usr/share/emacs/site-lisp/auctex/images/prvtex24.xpm
6ce704103821329336489e990bc6f267  
/usr/share/emacs/site-lisp/auctex/images/prvwrk12.xpm
5607f4e8bc0eb555206e6a3542205f45  
/usr/share/emacs/site-lisp/auctex/images/prvwrk14.xpm
878a72cde3bb6f0ea6d586cff56e619c  
/usr/share/emacs/site-lisp/auctex/images/prvwrk16.xpm
41811748a97673381115957d42a6529b  
/usr/share/emacs/site-lisp/auctex/images/prvwrk20.xpm
254fc07db6a03a8a24f762135a403433  
/usr/share/emacs/site-lisp/auctex/images/prvwrk24.xbm
9690511307f3693e6f28e4db93fdc58c  
/usr/share/emacs/site-lisp/auctex/images/prvwrk24.xpm
e30a80ecb0711ceb42a2ca966ad74bbb  
/usr/share/emacs/site-lisp/auctex/images/pspdf.xpm
5cc696e2c69ae401c0c223d84d013c8e  
/usr/share/emacs/site-lisp/auctex/images/sep.xpm
861fc288565e624ce8b34c1fc42e3496  
/usr/share/emacs/site-lisp/auctex/images/tex.xpm
338158cc358b16daf9b58ee54bd14bad  
/usr/share/emacs/site-lisp/auctex/images/view.xpm
8147722e0061799437edf36d4466e5ab  
/usr/share/emacs/site-lisp/auctex/images/viewdvi.xpm
67d7ed652615a027038610f8370ba172  

Bug#755234: [Pkg-xfce-devel] Bug#755234: Bug#755234: a more complete patch for xfce4-power-manager 1.2.0-5, a problem with refreshing of battery status

2014-08-21 Thread Martin Schwenke
On Fri, 22 Aug 2014 08:23:46 +0900, Norbert Preining
prein...@logic.at wrote:

  The upower-0.99 port of xfpm 1.3 (in experimental) seems to take a
 
 BTW, *why* not simply build xfpm 1.3 for sid?
 
 I now downgraded the build-deps to 4.10 instead of 4.11, rebuild
 the package, installed them, and everything works as expected!
 
 Also the README does *not* indicate that xfce = 4.11 is needed,
 it says = 4.10, so that would be the best, easiest, and safest
 solution?

I just tried this and would like to confirm that works fine.

It seems like an excellent solution!  :-)

peace  happiness,
martin


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



Bug#750593: xsltproc: bus error on some architectures

2014-08-18 Thread Martin Schwenke
On Wed, 4 Jun 2014 22:27:03 +0200 Ivo De Decker ivo.dedec...@ugent.be
wrote:

 On some architectures (like i386), xsltproc fails with Bus error when running
 /usr/bin/xsltproc --nonet -o smb.conf.5 man.xsl smb.conf.5.tmp.xml
 with the attached version of man.xsl and smb.conf.5.tmp.xml.
 
 This is done during the samba build. It fails on armel, armhf and i386, but
 doesn't fail on other architectures.

I'm also seeing it fail on i386.  Bizarrely, it doesn't fail when run
under valgrind or gdb, so unable to get any clues that way.  :-(

peace  happiness,
martin


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



Bug#755234: a more complete patch for xfce4-power-manager 1.2.0-5, a problem with refreshing of battery status

2014-08-09 Thread Martin Schwenke
On Fri, 08 Aug 2014 17:24:18 +0200 Rafal fatwild...@gmail.com wrote:

 My previous patch fixes only updates of battery charge level. But, for 
 example, when AC cord is plugged in, the power manager still insists 
 that computer is on battery (although states also that battery is 
 charged). The patch below fixes the problem. It fixes also a problem 
 with messages like
  (xfce4-power-manager:31539): GLib-CRITICAL **: Source ID 73 was not 
 found when attempting to remove it

Interesting!  With the previous patch, at least on my laptop, xfpm
notices when the power is plugged in and I don't see any of those
messages in .xsession-errors...

Weird...

Whatever the case, thanks for trying to fix this madness!  :-)

peace  happiness,
martin


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



Bug#755234: reload logind

2014-08-06 Thread Martin Schwenke
On Thu, 7 Aug 2014 00:48:52 +0900, Norbert Preining prein...@logic.at
wrote:

 one more thing:
   systemctl restart systemd-logind
 should give you the effect you want without rebooting.

Thanks, that seems to have worked!

 And yes, it is not documented in logind.conf ;-) It is systemd,
 thus pain inflicted onto everyone.

Hmmm...  ;-)

peace  happiness,
martin


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



Bug#755234: [Pkg-xfce-devel] Bug#755234: reload logind

2014-08-06 Thread Martin Schwenke
On Wed, 06 Aug 2014 18:30:09 +0200, Yves-Alexis Perez
cor...@debian.org wrote:

 On jeu., 2014-08-07 at 00:48 +0900, Norbert Preining wrote:

  one more thing:
  systemctl restart systemd-logind
  should give you the effect you want without rebooting.
 
 But would break permissions for the current session, aiui. So it seems
 the best is still to restart the session, unfortunately.

My session permissions broke some time ago, so I searched the web and
decided to do this:

  # cat /etc/polkit-1/localauthority/50-local.d/custom-actions.pkla 
  [Local actions]
  Identity=unix-group:adm
  
Action=org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.udisks.*;org.freedesktop.udisks2.*;org.freedesktop.login1.*
  ResultAny=yes
  ResultInactive=no
  ResultActive=yes

For whatever reason, I also had to put the same thing in
/var/lib/polkit-1/localauthority/50-local.d/custom-actions.pkla.  I
also had to update this with the login1.* when systemd took over.

As per Norbet's comment, with current patch (for battery notification)
I also can close the lid now and it no longer suspends (correct
behaviour for my configuration on AC, incorrect on battery).
Hopefully I'll notice this late in the day after I close the lid but
before I put my laptop in my bag...  ;-)

peace  happiness,
martin


signature.asc
Description: PGP signature


Bug#755234: [Pkg-xfce-devel] Bug#755234: Fix only 1/2 works... :-(

2014-08-04 Thread Martin Schwenke
On Mon, 04 Aug 2014 08:03:26 +0200, Yves-Alexis Perez
cor...@debian.org wrote:

 I guess you're using systemd as init system? Then it's logind handling
 the suspend part. Try to configure /etc/systemd/logind.conf to hands off
 suspend.

Thanks, I've now tried that.

Now for the rant that's not aimed at you.  I'll keep it to a
minimum  :-)

rant
I've tried everything I can think of, including systemctl
daemon-reload but nothing seems to reload the settings.  I would have
thought that logind.conf(5) would tell me how to reload the file after
it is modified.  I can't believe that in 2014 I would have to logout
and/or reboot to reload the configuration for a modern piece of
software.  Stunning...

Beyond that, I'm speechless at the way systemd is taking over
functionality that doesn't belong in an init system.

Anyway, that's enough... sorry...
/rant

There's a patch here:

  https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1222021

so that xfce4-power-manager can inhibit systemd from handling suspend
and related events.  However, I can't get it to build.  :-(  

peace  happiness,
martin


signature.asc
Description: PGP signature


Bug#755234: [Pkg-xfce-devel] Bug#755234: Fix only 1/2 works... :-(

2014-08-04 Thread Martin Schwenke
On Mon, 04 Aug 2014 13:04:00 +0200, Yves-Alexis Perez
cor...@debian.org wrote:

 On lun., 2014-08-04 at 20:56 +1000, Martin Schwenke wrote:
  On Mon, 04 Aug 2014 08:03:26 +0200, Yves-Alexis Perez
  cor...@debian.org wrote:
  
   I guess you're using systemd as init system? Then it's logind handling
   the suspend part. Try to configure /etc/systemd/logind.conf to hands off
   suspend.
  
  Thanks, I've now tried that.
 
 And does it work?

I'm not sure.  As I mentioned in my rant, it doesn't seem possible to
reload logind.conf without some sort of restart.  I can't logout at the
moment because I have a lot of context (i.e. state of unfinished work)
in my current session.

So, either:

* no - my attempts to reload logind.conf worked but for another reason
  my laptop still suspends when I close the lid; or

* yes - but I'll only confirm that when I get a chance to
  logout/restart.

The following seems to suggest that logind.conf hasn't been reloaded:

  # loginctl show-user | grep HandleLidSwitch
  HandleLidSwitch=suspend

[Why is show-user overloaded to show the daemon configuration?  That
 was stupidly hard to find...]

so it looks like the 2nd possibility.  I might get a chance to
logout/restart some time in the next week - I usually only do so about
once a month - when I do then I'll update this bug...

Thanks again...

peace  happiness,
martin


signature.asc
Description: PGP signature


Bug#755234: Fix only 1/2 works... :-(

2014-08-03 Thread Martin Schwenke
The fix in message #15 makes xfce4-power-manager correctly update the
battery status.

However, in preferences I have On AC - Actions - When laptop lid is
closed set to Nothing.  When I close the lid the laptop suspends.

So there is still an issue...  :-(

peace  happiness,
martin


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



Bug#755426: upower: unable to suspend/hibernate laptop from KDE after upgrade

2014-07-20 Thread Martin Schwenke
Same here with XFCE.

The big hint is that the following shows nothing:

  pkaction | grep upower

Reverting makes upower items appear again.

peace  happiness,
martin


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



Bug#751361: apache2: SNI not working correctly when certificate is defined in global scope

2014-06-11 Thread Martin Schwenke
Package: apache2
Version: 2.4.9-1
Severity: normal

Dear Maintainer,

SSL certificates in virtual hosts are being ignored.  The certificate
configured in global scope is used for all virtual hosts.

Please see this Apache bug:

  https://issues.apache.org/bugzilla/show_bug.cgi?id=56353

It has a patch. :-)

-- Package-specific info:

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

Kernel: Linux 3.12-1-amd64 (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/bash

Versions of packages apache2 depends on:
ii  apache2-bin   2.4.9-1
ii  apache2-data  2.4.9-1
ii  lsb-base  4.1+Debian12
ii  mime-support  3.56
ii  perl  5.18.2-4
ii  procps1:3.3.9-5

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.34

Versions of packages apache2 suggests:
ii  apache2-doc  2.4.9-1
pn  apache2-suexec-pristine | apache2-suexec-custom  none
ii  apache2-utils2.4.9-1
ii  elinks [www-browser] 0.12~pre6-4
ii  links [www-browser]  2.8-2
ii  lynx-cur [www-browser]   2.8.8pre5-1
ii  w3m [www-browser]0.5.3-15

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.1-2
ii  libaprutil1  1.5.3-2
ii  libaprutil1-dbd-sqlite3  1.5.3-2
ii  libaprutil1-ldap 1.5.3-2
ii  libc62.19-1
ii  libldap-2.4-22.4.39-1
ii  liblua5.1-0  5.1.5-5
ii  libpcre3 1:8.31-5
ii  libssl1.0.0  1.0.1g-4
ii  libxml2  2.9.1+dfsg1-3
ii  perl 5.18.2-4
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages apache2-bin suggests:
ii  apache2-doc  2.4.9-1
pn  apache2-suexec-pristine | apache2-suexec-custom  none
ii  elinks [www-browser] 0.12~pre6-4
ii  links [www-browser]  2.8-2
ii  lynx-cur [www-browser]   2.8.8pre5-1
ii  w3m [www-browser]0.5.3-15

Versions of packages apache2 is related to:
ii  apache2  2.4.9-1
ii  apache2-bin  2.4.9-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#709553: anacron: cron.daily jobs are not run after boot as planned

2013-05-23 Thread Martin Schwenke
Package: anacron
Version: 2.3-19
Severity: important

Dear Maintainer,

I have a fresh wheezy install and there are several items in
/etc/cron.daily/:

  root@spot:/home/martins# ls -l /etc/cron.daily/
  total 56
  -rwxr-xr-x 1 root root   311 May 23  2012 0anacron
  -rwxr-xr-x 1 root root 14985 Mar 14 18:18 apt
  -rwxr-xr-x 1 root root   314 Nov  7  2012 aptitude
  -rwxr-xr-x 1 root root   355 Jun 11  2012 bsdmainutils
  -rwxr-xr-x 1 root root   256 Mar 18 16:52 dpkg
  -rwxr-xr-x 1 root root   583 Jun  3  2012 etckeeper
  -rwxr-xr-x 1 root root89 May 17  2012 logrotate
  -rwxr-xr-x 1 root root  1365 Jun 19  2012 man-db
  -rwxr-xr-x 1 root root   606 Sep 25  2010 mlocate
  -rwxr-xr-x 1 root root   249 May 26  2012 passwd
  -rwxr-xr-x 1 root root   632 May 15 16:12 z-local

When the system boots I see this in syslog:

  May 24 07:37:42 spot anacron[2372]: Anacron 2.3 started on 2013-05-24
  May 24 07:37:42 spot anacron[2372]: Will run job `cron.daily' in 5 min.
  May 24 07:37:42 spot anacron[2372]: Jobs will be executed sequentially

However, the job does not run.  If I check for an anacron process
shortly after boot there isn't one.  It looks like anacron exits
without running cron.daily.

Later, I do service anacron start and I see this in syslog:

  May 24 09:35:07 spot anacron[3650]: Anacron 2.3 started on 2013-05-24
  May 24 09:35:07 spot anacron[3650]: Will run job `cron.daily' in 5 min.
  May 24 09:35:07 spot anacron[3650]: Jobs will be executed sequentially
  May 24 09:40:07 spot anacron[3650]: Job `cron.daily' started
  May 24 09:40:07 spot anacron[3989]: Updated timestamp for job `cron.daily' to 
2013-05-24

So clearly the job can be run by anacron.  There doesn't look to be a
misconfiguration anywhere.  systemd is not installed.  This is a
desktop system that is never on battery power.

Thanks for any clues...

peace  happiness,
martin


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 anacron depends on:
ii  debianutils  4.3.2
ii  libc62.13-38
ii  lsb-base 4.1+Debian8

Versions of packages anacron recommends:
ii  cron 3.0pl1-124
ii  rsyslog [system-log-daemon]  5.8.11-3

Versions of packages anacron suggests:
ii  postfix [mail-transport-agent]  2.9.6-2
ii  powermgmt-base  1.31

-- no debconf information



peace  happiness,
martin


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



Bug#668065: Remove drupal6 in favour of drupal7?

2012-04-20 Thread Martin Schwenke
Upgrading from D6 to D7 can be difficult.  The main reason is the use
of 3rd party modules:

* Some of the 3rd party modules for D6 got included in D7 core, but with
  variations or only partial functionality...  so data doesn't
  necessarily transfer easily.

* Similarly, some of the in-core D6 functionality got migrated to these
  new modules in D7 but the upgrade path isn't clean and bug-free.

* Some common D6 3rd party modules and themes don't yet have a stable D7
  release.

I spent a whole day a couple of weeks ago trying to upgrade a
complicated site from D6 to D7 but I had to roll back when I couldn't
find a way forward.  More research and thinking means that I think I
know a way past the thing that blocked me...  but that doesn't mean
I'll be able to get all the way through next time.  I might still need
to roll back.  So it would be nice to have D6 around.  :-)

Looking at Drupal bugs suggests that I'm not the only one in this
situation...  :-(

peace  happiness,
martin



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



Bug#570764: dovecot-common: sieve should allow Return-path header for address test

2010-02-21 Thread Martin Schwenke
Package: dovecot-common
Version: 1:1.2.10-1
Severity: normal


I attempt to compile the following sieve script...

mart...@bilbo:~/tmp$ cat test.sieve 
if address :is Return-path owner-cip...@inka.de {
keep;
}

[Yes, it is useless - a minimal example to illustrate the bug.  :-) ]

... and I get the following error:

mart...@bilbo:~/tmp$ sievec test.sieve
test: line 1: error: specified header 'Return-path' is not allowed for the 
address test.
test: error: validation failed.
Error: failed to compile sieve script 'test.sieve'

This test is included in an example in the Dovecot sieve documentation at:

  http://wiki.dovecot.org/LDA/Sieve#Mail_filtering_by_various_headers

That seems to suggest that it should work!

peace  happiness,
martin

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

Kernel: Linux 2.6.26-2-amd64 (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/bash

Versions of packages dovecot-common depends on:
ii  adduser3.112 add and remove users and groups
ii  libbz2-1.0 1.0.5-4   high-quality block-sorting file co
ii  libc6  2.10.2-2  GNU C Library: Shared libraries
ii  libcomerr2 1.41.9-1  common error description library
ii  libdb4.8   4.8.26-1  Berkeley v4.8 Database Libraries [
ii  libgssapi-krb5-2   1.8+dfsg~alpha1-5 MIT Kerberos runtime libraries - k
ii  libk5crypto3   1.8+dfsg~alpha1-5 MIT Kerberos runtime libraries - C
ii  libkrb5-3  1.8+dfsg~alpha1-5 MIT Kerberos runtime libraries
ii  libldap-2.4-2  2.4.17-2.1OpenLDAP libraries
ii  libmysqlclient16   5.1.41-3  MySQL database client library
ii  libpam-runtime 1.1.1-1   Runtime support for the PAM librar
ii  libpam0g   1.1.1-1   Pluggable Authentication Modules l
ii  libpq5 8.4.2-2   PostgreSQL C client library
ii  libsqlite3-0   3.6.22-1  SQLite 3 shared library
ii  libssl0.9.80.9.8k-8  SSL shared libraries
ii  openssl0.9.8k-8  Secure Socket Layer (SSL) binary a
ii  ucf3.0025Update Configuration File: preserv
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

dovecot-common recommends no packages.

Versions of packages dovecot-common suggests:
ii  ntp 1:4.2.4p8+dfsg-1 Network Time Protocol daemon and u

-- 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#552813: rrdcgi also failing

2009-12-08 Thread Martin Schwenke
I'm seeing something very similar in rrdcgi on armel:

  *** glibc detected *** /usr/bin/rrdcgi: free(): invalid pointer: 0x000b9838 
***
  [Wed Dec 09 09:54:52 2009] [error] [client 192.168.20.31] Premature end of 
script headers: temperature.cgi

A different script on the same box produces a different
error:

  *** glibc detected *** /usr/bin/rrdcgi: munmap_chunk(): invalid pointer: 
0x0009f010 ***
  [Wed Dec 09 10:07:54 2009] [error] [client 192.168.20.31] Premature end of 
script headers: index.cgi

Interestingly these scripts were working for me yesterday and nothing
on the box has been upgraded.

OK, I see.  My filesystem is full.  So librrd deals very poorly with a
full filesystem. 

Could this explain other people's problems in this bug report?

peace  happiness,
martin




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



Bug#549436: [05395e1] Fix for Bug#549436 committed to git

2009-11-14 Thread Martin Schwenke
This looks like a good fix.  Thanks for committing it.

The only problem is that it looks like it implicitly disallows '-',
'_' and international characters in hostnames.  I'm wondering if it
would be sufficient to simply disallow '/', since that character is
needed to allow directory traversal?

peace  happiness,
martin




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



Bug#549436: wordpress: Fix for 500295 is too restrictive

2009-10-03 Thread Martin Schwenke
Package: wordpress
Version: 2.8.4-2
Severity: important


The fix for bug 500295 is too restrictive.  It disables a completely
reasonable way of configuring wordpress.  Using symlinks is probably
the only way of allowing trusted users to manage their wordpress
configuration without having to be root (other than to create the symlink).
We use this type of configuration, given that we have users that we trust.
The proposed additional solution of adding a list of directories that can
contain configuration files is messy - there must be a better solution!

One problem with the fix is that the nature of the possible attack isn't
actually explained in the bug.  Can someone please explain it?  Then we
could help to try and find a better solution.

Does the attack involved having special characters/substrings like '/' and
.. in HTTP_HOST, which then possibly allows them to run code in files
in the uploads area?  If so, why not just disallow '/' in HTTP_HOST?  That
would seem to be a simpler and less restrictive fix...

There must be a fix that doesn't impose the restrictions that realpath()
imples...

Note, we haven't yet installed version 2.8.4-2 because we'd like to
make sure we have a workaround/solution that allows us to have users
manage their own configurations and minimise the amount of root access
they require.

peace  happiness,
martin


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

Kernel: Linux 2.6.30-1-amd64 (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/bash

Versions of packages wordpress depends on:
ii  apache22.2.13-2  Apache HTTP Server metapackage
ii  apache2-mpm-prefork [h 2.2.13-2  Apache HTTP Server - traditional n
ii  libapache2-mod-php55.2.10.dfsg.1-2.2 server-side, HTML-embedded scripti
ii  libjs-jquery   1.3.3-2   JavaScript library for dynamic web
ii  libjs-prototype1.6.1-1   JavaScript Framework for dynamic w
ii  libjs-scriptaculous1.8.2-2   JavaScript library for dynamic web
ii  libphp-phpmailer   2.1-1 full featured email transfer class
ii  libphp-snoopy  1.2.4-1   Snoopy is a PHP class that simulat
ii  mysql-client-5.0 [virt 5.0.51a-24+lenny2 MySQL database client binaries
ii  php5   5.2.10.dfsg.1-2.2 server-side, HTML-embedded scripti
ii  php5-gd5.2.10.dfsg.1-2.2 GD module for php5
ii  php5-mysql 5.2.10.dfsg.1-2.2 MySQL module for php5
ii  tinymce3.2.6-1   platform independent web based Jav

wordpress recommends no packages.

Versions of packages wordpress suggests:
hi  mysql-server-5.0 [virt 5.0.51a-24+lenny1 MySQL database server binaries

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/wordpress/wp-includes/pluggable.php (from 
wordpress package)



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



Bug#521288: Patch to avoid reporting core Drupal new releases

2009-07-20 Thread Martin Schwenke
I agree that Gunnar's patch is a reasonable idea.

I definitely don't want to turn off the update_status module for 3rd
party modules.  I have about 20 extra modules installed and
update_status is invaluable for making sure I keep them up-to-date.

peace  happiness,
martin




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



Bug#508666: Couldn't debian/rules just run makeManifest.pl

2008-12-29 Thread Martin Schwenke
It looks like the gallery2 Debian packaging contains a patch to the
MANIFEST file.  That seems to suggest that these sorts of problems
will always occur because someone will forget to update the MANIFEST
file.

How about doing something like this in debian/rules to rebuild the
MANIFEST file?

  cd `pwd`/debian/${package}/usr/share/gallery2  updateManifest.pl

I do something similar in a private package I've built that contains a
custom gallery2 theme...  seems to work!  :-)

peace  happiness,
martin




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



Bug#480463: anacron prints spurious debug message

2008-05-10 Thread Martin Schwenke
Package: anacron
Version: 2.3-13.1
Severity: minor

I assume that when anacron is run from the command line and there are no
problems encountered then it should produce no output. However, if
there's a @monthly entry in the anacrontab, then anacron prints a
message like:

  Checking against 0 with 30

This looks a lot like a debug message and should probably be removed.

The offending line of code is introduced by
anacron_2.3-13.1.diff.gz into anacron-2.3/lock.c:consider_job()
and looks like:

  printf (Checking against %d with %d\n, day_delta, period);

I'm running with this option:

 -d Don't fork to the background. In this mode, Anacron will output
informational messages to standard error, as well as to syslog.
The output of jobs is mailed as usual.

(among others), which only mentions output to stderr, not stdout.

However, in this case the message is confusing because the user has no
real idea of its context, so it probably should not be made to go
to stderr but should probably be removed altogether.

I thought I had reported this previously, but can't find it anywhere.
:-(

peace  happiness,
martin

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

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

Versions of packages anacron depends on:
ii  debianutils   2.28.4 Miscellaneous utilities specific t
ii  libc6 2.7-10 GNU C Library: Shared libraries
ii  lsb-base  3.1-24 Linux Standard Base 3.1 init scrip

Versions of packages anacron recommends:
ii  cron  3.0pl1-104 management of regular background p
ii  postfix [mail-transport-agent 2.5.1-1High-performance mail transport ag
ii  sysklogd [system-log-daemon]  1.5-2  System Logging Daemon



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#403705: squirrelmail: Confusing error message when delivery to a local recipient fails

2007-01-07 Thread Martin Schwenke
Hi Thijs,

 Thijs == Thijs Kinkhorst [EMAIL PROTECTED] writes:

Thijs I have changed this now a bit to read the following (in
Thijs upstream cvs). 

Thijs ERROR:
Thijs Message not sent. Server replied: 
Thijs Requested action not taken: mailbox unavailable
Thijs 550 [EMAIL PROTECTED]: Recipient address rejected: User 
unknown
Thijs in virtual alias table

Thijs Is this acceptable to you?

That's much clearer.  Thanks for making the change!

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#403705: squirrelmail: Confusing error message when delivery to a local recipient fails

2006-12-18 Thread Martin Schwenke
Package: squirrelmail
Version: 2:1.4.9a-1
Severity: normal


Assuming the local domain is example.com, attempting to send email to
myself [EMAIL PROTECTED] and a broken local address
testing.broken.addresses.in.squirrelmail results in the following
error message:

ERROR:
Requested action not taken: mailbox unavailable
Server replied: 550 5.1.1 
[EMAIL PROTECTED]: Recipient 
address rejected: User unknown in local recipient table

This error message is confusing.  It is unclear whether delivery only
failed for the broken address or whether the delivery was aborted for
all recipients.

Can you guess what the outcome was?  ;-)

In this case the email was not delivered to anyone.

It would be clearer to print a message that explicitly states that the
email was not delivered to any recipients.

Thanks...

peace  happiness,
martin

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages squirrelmail depends on:
ii  apache [httpd]1.3.34-4   versatile, high-performance HTTP s
ii  libapache-mod-php46:4.4.4-8  server-side, HTML-embedded scripti
ii  perl  5.8.8-6.1  Larry Wall's Practical Extraction 
ii  php4  6:4.4.4-8  server-side, HTML-embedded scripti
ii  php4-cgi  6:4.4.4-8  server-side, HTML-embedded scripti
ii  php5  5.2.0-7server-side, HTML-embedded scripti
ii  php5-cgi  5.2.0-7server-side, HTML-embedded scripti

Versions of packages squirrelmail recommends:
ii  ispell  3.1.20.0-4.3 International Ispell (an interacti
ii  squirrelmail-locales1.4.8-20060903-1 Translations for the SquirrelMail 

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401143: debianutils: savelog -d -j can cause spurious warning messages

2006-11-30 Thread Martin Schwenke
Package: debianutils
Version: 2.17
Severity: normal


Running:

  savelog -t -q -j -d -c 99 yip

causes an error like this to be printed:

  bzip2: Input file yip.20061001030006.bz2 already has .bz2 suffix.

if there are previously compressed and rotated versions of the file 
already there.

The problem is at about line 250 of /usr/bin/savelog:

# compress the old uncompressed log if needed
if test -n $datum  test -n $COMPRESS; then
$COMPRESS -- $newname.[0-9]*[0-9]
fi

This code is trying to compress old dated files but also catches files 
ending in [0-9]*.bz2.

Possible solutions, from hackiest to best, include:

* Pass -q to $COMPRESS.  This will stop the warning appearing.

  However, if the compression scheme is changed from gzip to bzip2 
  (or vice-versa) between uses of savelog, this will still allow gzipped 
  files to be recompressed with bzip2. 

* Only try to compress files ending in 2 consecutive digits.  This will 
  fix the current problem but will no doubt fail in the future.

* Since the value of $DATUM will always contain 14 digits then only 
  compress files ending in 14 digits.  I'm not sure this is locale-safe.

* Generate a list of files to compress, removing any that end in $DOT_Z.
  This is pretty good but still allows recompression of files if the 
  compression scheme is changed.

* As above but filter out anything that looks like a compressed 
  filename.

Thanks...

peace  happiness,
martin


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages debianutils depends on:
ii  coreutils5.97-5  The GNU core utilities
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  mktemp   1.5-2   Makes unique filenames for tempora

debianutils recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#373390: python-tmda needs to be rebuilt since python version is now = 2.4

2006-08-16 Thread Martin Schwenke
Package: python-tmda
Version: 1.0.3-1
Followup-For: Bug #373390

My system wants to uninstall python-tmda because python is now going
up to version 2.4.3-11 and python-tmda requires python  2.4.  Can
python-tmda be rebuilt to work with python = 2.4 or is it all over?

Thanks...

peace  happiness,
martin

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages python-tmda depends on:
hi  python2.3.5-11   An interactive high-level object-o

python-tmda recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#376149: revelation: Here's a workaround...

2006-07-03 Thread Martin Schwenke
Package: revelation
Version: 0.4.7-2
Followup-For: Bug #376149


dpkg -P --force-depends python-gnome2-extras
dpkg -i --force-depends python2.3-gnome2-extras_2.12.1-2.1_i386.deb

It's a bit nasty and probably causes breakage elsewhere but at least
you can get to your passwords.

It would be nice if revelation was better documented.  For example, it
seems possible that ccrypt might be able to decode the file if the
format was documented somewhere (other than the code).

Thanks...

peace  happiness,
martin

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.14
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages revelation depends on:
ii  cracklib22.7-19  pro-active password checker librar
ii  gconf2   2.14.0-1GNOME configuration database syste
ii  gnome-icon-theme 2.14.2-1GNOME Desktop icon theme
ii  libbonoboui2-0   2.14.0-3The Bonobo UI library
ii  libglib2.0-0 2.10.3-2The GLib library of C routines
ii  libgnomeui-0 2.14.1-2The GNOME 2 libraries (User Interf
ii  libgtk2.0-0  2.8.18-1The GTK+ graphical user interface 
ii  libpanel-applet2-0   2.14.2-1library for GNOME 2 panel applets
ii  python   2.3.5-11An interactive high-level object-o
ii  python-crypto2.0.1+dfsg1-1.2 cryptographic algorithms and proto
hi  python-gnome22.12.3-2Python bindings for the GNOME desk
pn  python-gnome2-extras none  (no description available)
hi  python-gtk2  2.8.2-3 Python bindings for the GTK+ widge
ii  python-xml   0.8.4-5 XML tools for Python
ii  python2.32.3.5-14An interactive high-level object-o
ii  shared-mime-info 0.17-2  FreeDesktop.org shared MIME databa

revelation recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#373277: Rhythmbox no longer releases audio device when paused

2006-06-26 Thread Martin Schwenke
Hi Sven,

 Sven == Sven Arvidsson [EMAIL PROTECTED] writes:

Sven I assume this issue isn't specific to Rhythmbox then? Maybe
Sven it would be better to reassign it to one of the alsa
Sven packages, perhaps alsa-base?

Sure.  However, I'll let the maintainer do that.  I'm not sure how...
probably should learn but pushed for time right now...

Sven (By the way, I'm not a maintainer, I just help out with some
Sven of the bug reports :) )

Oh, OK...  Thanks for your help!  :-)

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#373277: Rhythmbox no longer releases audio device when paused

2006-06-24 Thread Martin Schwenke
 Sven == Sven Arvidsson [EMAIL PROTECTED] writes:

Sven   Are you using ALSA with dmix?

Sven   http://alsa.opensrc.org/index.php?page=DmixPlugin

Sven   gstreamer (and hence rhythmbox) will use dmix if it is
Sven   setup and should allow multiple sources using the
Sven   sound card.

Combined with this text on the above page:

  NOTE: For ALSA 1.0.9rc2 and higher you don't need to setup
  dmix. Dmix is enabled as default for soundcards which don't support
  hw mixing.

and a whole bunch of time to check things out, it appears the answer
is yes.  It seems I don't have a choice.

Before this I didn't even know what dmix was.  I still don't care
though - I just want my system to behave sensibly!

[So, now my rant is no longer directed at you as Debian maintainer of
 rhythmbox...  :-]

Sven   The problem is likely your other apps that are the
Sven   problem not rhythmbox/gstreamer, some proprietary apps
Sven   like Skype use the old OSS interface which
Sven   hogs/steals the sound card.  Not much that alsa can
Sven   do about that, see: [...]

I don't use Skype and I don't even have OSS compatibility in my kernel!

If I could understand what value I'm getting from dmix I might be
happy using it.  However, at the moment all I want to be able to do it
play a single audio stream.

This suggests that my sound card (ICH6) can only do 48KHz natively:

  $ grep Hz /proc/asound/card0/codec97#0/ac97#0-0
  PCM front DAC: 48000Hz
  PCM ADC  : 48000Hz

Does dmix resample for me so I can play my 44.1KHz OGG files?  This is
pretty unclear to me...

Thanks...

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#373277: Rhythmbox no longer releases audio device when paused

2006-06-13 Thread Martin Schwenke
Package: rhythmbox
Version: 0.9.4.1-6
Severity: normal


Back in August 2003 the NEWS file for Rhythmbox 0.5.2 said:

* Release audio device on pause [Benjamin Otte (GStreamer) Bastien
  Nocera (xine)]

This no longer happens.  I pause Rhythmbox and the audio device is
kept open by Rhythmbox.  If I quit Rhythmbox the device is no longer
listed as open by any process.  I'm using the ALSA gstreamer backend.

This is an important change in behaviour so it should be considered a
regression.  On a laptop with dodgy sound driver it is often necessary
to remove the relevant module(s) when suspending so that sound will
work after resuming.  If Rhythmbox keeps the device open then the
module(s) can not be removed before suspending.

I'm not sure when the change happened...

Thanks...

peace  happiness,
martin

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.14
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages rhythmbox depends on:
ii  dbus   0.61-6simple interprocess messaging syst
ii  gconf2 2.14.0-1  GNOME configuration database syste
ii  gstreamer0.10-alsa [gstrea 0.10.8-1  GStreamer plugin for ALSA
ii  gstreamer0.10-gnomevfs 0.10.8-1  GStreamer plugin for GnomeVFS
ii  gstreamer0.10-plugins-base 0.10.8-1  GStreamer plugins from the base 
ii  gstreamer0.10-plugins-good 0.10.3-2  GStreamer plugins from the good 
ii  gstreamer0.10-plugins-ugly 0.10.3-1  GStreamer plugins from the ugly 
ii  libart-2.0-2   2.3.17-1  Library of functions for 2D graphi
ii  libatk1.0-01.11.4-2  The ATK accessibility toolkit
ii  libaudiofile0  0.2.6-6   Open-source version of SGI's audio
ii  libavahi-client3   0.6.10-1  Avahi client library
ii  libavahi-common3   0.6.10-1  Avahi common library
ii  libavahi-glib1 0.6.10-1  Avahi glib integration library
ii  libbonobo2-0   2.14.0-1  Bonobo CORBA interfaces library
ii  libbonoboui2-0 2.14.0-2  The Bonobo UI library
ii  libc6  2.3.6-15  GNU C Library: Shared libraries
ii  libcairo2  1.0.4-2   The Cairo 2D vector graphics libra
ii  libdbus-1-20.61-6simple interprocess messaging syst
ii  libdbus-glib-1-2   0.61-6simple interprocess messaging syst
ii  libesd-alsa0 [libesd0] 0.2.36-3  Enlightened Sound Daemon (ALSA) - 
ii  libexpat1  1.95.8-3.2XML parsing C library - runtime li
ii  libfontconfig1 2.3.2-7   generic font configuration library
ii  libfreetype6   2.2.1-2   FreeType 2 font engine, shared lib
ii  libgconf2-42.14.0-1  GNOME configuration database syste
ii  libgcrypt111.2.2-1   LGPL Crypto library - runtime libr
ii  libglade2-01:2.5.1-2 library to load .glade files at ru
ii  libglib2.0-0   2.10.3-1  The GLib library of C routines
ii  libgnome-keyring0  0.4.9-1   GNOME keyring services library
ii  libgnome2-02.14.1-2  The GNOME 2 library - runtime file
ii  libgnomecanvas2-0  2.14.0-2  A powerful object-oriented display
ii  libgnomeui-0   2.14.1-1  The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 2.14.2-1  GNOME virtual file-system (runtime
ii  libgnutls131.3.5-1.1 the GNU TLS library - runtime libr
ii  libgpg-error0  1.2-1 library for common error values an
ii  libgpod0   0.3.2-1   a library to read and write songs 
ii  libgstreamer0.10-0 0.10.8-2  Core GStreamer libraries and eleme
ii  libgtk2.0-02.8.18-1  The GTK+ graphical user interface 
ii  libhal10.5.7-2   Hardware Abstraction Layer - share
ii  libice61:1.0.0-3 X11 Inter-Client Exchange library
ii  libjpeg62  6b-13 The Independent JPEG Group's JPEG 
ii  liblircclient0 0.8.0-5   LIRC client library
ii  libmusicbrainz4c2a 2.1.2-5   Second generation incarnation of t
ii  libnautilus-burn2  2.12.3-2  Nautilus Burn Library - runtime ve
ii  libnotify1 0.4.0-1   sends desktop notifications to a n
ii  liborbit2  1:2.14.0-1.1  libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0  1.12.3-1  Layout and rendering of internatio
ii  libpng12-0 1.2.8rel-5.1  PNG library - runtime
ii  libpopt0   1.10-2lib for parsing cmdline parameters
ii  libsexy1   0.1.6-2+b1collection of additional GTK+ widg
ii  libsm6 1:1.0.0-4 X11 Session Management library
ii  

Bug#340113: Acknowledgement (stunnel4: stunnel fails to run)

2006-04-30 Thread Martin Schwenke
Somewhere /usr/sbin/stunnel4 got moved to /usr/bin/stunnel4, but
/usr/bin/stunnel still points to /usr/sbin/stunnel4.  Whoops!

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340113: Acknowledgement (stunnel4: stunnel fails to run)

2006-03-26 Thread Martin Schwenke
This has happened again.  Seeing a package upgraded for a 2nd time so
that it creates fork bombs is more than a little disconcerting.  :-(

stunnel4 (2:4.150-1) unstable; urgency=low

  * New upstream release

 -- Julien Lemoine [EMAIL PROTECTED]  Sun, 12 Mar 2006 21:30:08 +0100


If it is not possible to ensure that the stunnel3-compatibility script
is correct then it may be better to remove it from that package...

Thanks...

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#344357: sweep doesn't seem to support ALSA

2006-01-05 Thread Martin Schwenke
Hi Anand,

 Anand == Anand Kumria [EMAIL PROTECTED] writes:

Anand Well, after speaking with upstream even they haven't been
Anand running ALSA with it yet.  So, I've done an upload into
Anand experimental (after converting myself to use ALSA -- and
Anand finding a few bugs in esound).

Wow, even Conrad isn't using the ALSA support?  He needs to get with
the program! Those OSS compatibility modules are a crutch!  :-)

More seriously, the main reason I got rid of them is to make it harder
for random crud (like the flash plugin) to open a device and stop me
unloading the sounds modules at suspend time.

I stopped using esound.  I couldn't get rid of distortion on my new
laptop.  :-(

Anand Yup, it is the way of the future but it'll need brave souls
Anand like yourself to test things out and confirm they are
Anand working for you.

Anand If you could try out sweep in experimental (just add
Anand experimental into your source list) and then do:

Anand  'apt-get install sweep/experimental'

Anand And report any issues that arise.

I've briefly tested playback and it seems solid.  I can drag scrubby
around to my heart's content and it seems fine.  Sound quality is
good.  Recording seems to work, although I've only tested it
briefly...

Thanks for your efforts!

Anand PS: Happy New Year

... and the same to you.  See you at LCA?

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#344470: gnome-panel: clock-applet drop-down calendar starts week on Saturday

2005-12-22 Thread Martin Schwenke
Package: gnome-panel
Version: 2.10.2-1
Severity: normal

My clock-applet's drop-down calendar now has Saturday listed as the
first day.  I have no idea how this might have happened - I don't
believe I did any preferences tweaking (via either Clock Preferences
or gconf-editor).  Perhaps I hit some odd, undocumented keystroke?
Whatever the case, I can't find a way to change it back...

A counter-intuitive calender, where you have to read the column
headings before decoding it, isn't very useful...

Any ideas?

Thanks...

peace  happiness,
martin

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gnome-panel depends on:
ii  gnome-about  2.10.2-1The GNOME about box
ii  gnome-control-center 1:2.10.2-1  utilities to configure the GNOME d
ii  gnome-desktop-data   2.10.2-1Common files for GNOME 2 desktop a
ii  gnome-menus  2.10.2-1an implementation of the freedeskt
ii  gnome-panel-data 2.10.2-1common files for GNOME 2 panel
ii  libart-2.0-2 2.3.17-1Library of functions for 2D graphi
ii  libatk1.0-0  1.10.3-1The ATK accessibility toolkit
ii  libbonobo2-0 2.10.1-1Bonobo CORBA interfaces library
ii  libbonoboui2-0   2.10.1-1The Bonobo UI library
ii  libc62.3.5-9 GNU C Library: Shared libraries an
ii  libecal1.2-2 1.2.3-8 Client library for evolution calen
ii  libedataserver1.2-4  1.2.3-8 Utily library for evolution data s
ii  libgconf2-4  2.10.1-6GNOME configuration database syste
ii  libglade2-0  1:2.5.1-2   library to load .glade files at ru
ii  libglib2.0-0 2.8.4-2 The GLib library of C routines
ii  libgnome-desktop-2   2.10.2-1Utility library for loading .deskt
ii  libgnome-menu0   2.10.2-1an implementation of the freedeskt
ii  libgnome2-0  2.10.1-1The GNOME 2 library - runtime file
ii  libgnomeui-0 2.10.1-1The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0   2.10.1-5The GNOME virtual file-system libr
ii  libgtk2.0-0  2.8.9-2 The GTK+ graphical user interface 
ii  liborbit21:2.12.4-1  libraries for ORBit2 - a CORBA ORB
ii  libpanel-applet2-0   2.10.2-1library for GNOME 2 panel applets
ii  libpango1.0-01.10.1-2Layout and rendering of internatio
ii  libpopt0 1.7-5   lib for parsing cmdline parameters
ii  libwnck162.10.3-1Window Navigator Construction Kit 
ii  libx11-6 6.8.2.dfsg.1-11 X Window System protocol client li
ii  xlibs6.8.2.dfsg.1-11 X Window System client libraries m

Versions of packages gnome-panel recommends:
ii  gnome-applets 2.10.1-5   Various applets for GNOME 2 panel 
ii  gnome-session 2.10.0-8   The GNOME 2 Session Manager

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#344357: sweep doesn't seem to support ALSA

2005-12-21 Thread Martin Schwenke
Package: sweep
Version: 0.8.4-2
Severity: wishlist

As a modern, forward-thinking person, I've banished support for OSS
devices from my system.  However, the Debian sweep package doesn't
seem to have ALSA support, even though sweep appears to have had ALSA
support for about 2.5 years.

Anand!  Mate!  Isn't ALSA the way and the light?  Can't you make it
so?  :-)

Thanks...

peace  happiness,
martin


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages sweep depends on:
ii  libc62.3.5-9 GNU C Library: Shared libraries an
ii  libglib1.2   1.2.10-10   The GLib library of C routines
ii  libgtk1.21.2.10-18   The GIMP Toolkit set of widgets fo
ii  libmad0  0.15.1b-2.1 MPEG audio decoder library
ii  libogg0  1.1.2-1 Ogg Bitstream Library
ii  libsamplerate0   0.1.1-2 audio rate conversion library
ii  libsndfile1  1.0.12-3Library for reading/writing audio 
ii  libspeex11.1.11.1-1  The Speex Speech Codec
ii  libvorbis0a  1.1.0-1 The Vorbis General Audio Compressi
ii  libvorbisenc21.1.0-1 The Vorbis General Audio Compressi
ii  libvorbisfile3   1.1.0-1 The Vorbis General Audio Compressi
ii  libx11-6 6.8.2.dfsg.1-11 X Window System protocol client li
ii  libxext6 6.8.2.dfsg.1-11 X Window System miscellaneous exte
ii  libxi6   6.8.2.dfsg.1-11 X Window System Input extension li
ii  xlibs6.8.2.dfsg.1-11 X Window System client libraries m

Versions of packages sweep recommends:
ii  cmt [ladspa-plugin]   1.15-3 Computer Music Toolkit (cmt) a col
pn  fil-plugins   none (no description available)
ii  mcp-plugins   0.3.0-3LADSPA plugins designed for Alsa M
ii  swh-plugins [ladspa-plugin]   0.4.14-1   Steve Harris's LADSPA plugins
ii  tap-plugins [ladspa-plugin]   0.7.0-2Tom's Audio Processing LADSPA plug

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#343659: udev no longer reliably renames network interfaces

2005-12-17 Thread Martin Schwenke
 Marco == Marco d'Itri [EMAIL PROTECTED] writes:

Marco On Dec 17, Martin Schwenke [EMAIL PROTECTED] wrote:

 Until about a month ago (note: I upgrade Debian unstable every
 few days) udev used to reliably rename my network interfaces,
 but no longer does so.  When I boot the machine my 2 network
 interfaces have

Marco Try adding this before the other rules:

Marco ACTION==add, SUBSYSTEM==net, WAIT_FOR_SYSFS=address

Thanks.  That works like a charm.  Double-checking the release notes I
see why this is needed...

Would it be a terrible idea to just add: 

  WAIT_FOR_SYSFS=address

to each rule?  That'd just make my ruleset a little more compact?  I
guess adding it before the rules just adds it to each rule anyway...

Thanks again... and thanks for your excellent work maintaining the
Debian udev package and for keeping the upstream udev guys in line...
:-)

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#343659: udev no longer reliably renames network interfaces

2005-12-16 Thread Martin Schwenke
Package: udev
Version: 0.076-6
Severity: normal


Until about a month ago (note: I upgrade Debian unstable every few
days) udev used to reliably rename my network interfaces, but no
longer does so.  When I boot the machine my 2 network interfaces have
their default names of eth0 and eth1 rather than my preference of lan0
and wlan0.  A similar thing happens when I suspend (and unload
modules) and resume (and reload modules).  Later, if I remove a single
module (tg3 or ipw2200) manually and reload it then the relevant
interface is correctly renamed.  This points to a race condition,
since the machine is more heavily loaded at boot or resume time.

My rules look like this:

  /etc/udev/rules.d/z00_local.rules:

  ACTION==add, SUBSYSTEM==net, SYSFS{address}==00:12:f0:81:05:d3, \
NAME=wlan0
  #ACTION==add, SUBSYSTEM==net, SYSFS{address}==00:11:25:15:a7:ba, \
  #   NAME=lan0
  #KERNEL=eth*, SYSFS{address}=00:12:f0:81:05:d3, NAME=wlan0
  KERNEL=eth*, SYSFS{address}=00:11:25:15:a7:ba, NAME=lan0

As you can see, I have 2 different styles of rules, but neither style
works reliably.  I'm pretty sure this file used to have a different
name that put it at the end of the list of rules.  However, I renamed
it while trying to solve the current problems.

Since udev is supposed to be able to do interface renaming, and has
done it reliably in the past, I'd like to get it working again instead
of installing some other package to do the job.

Thanks for any idea...

peace  happiness,
martin


-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 8
lrwxrwxrwx 1 root root  20 Apr 11  2005 020_permissions.rules - 
../permissions.rules
lrwxrwxrwx 1 root root  19 Oct 12 09:09 025_libgphoto2.rules - 
../libgphoto2.rules
lrwxrwxrwx 1 root root  16 Oct 31 10:54 025_libsane.rules - ../libsane.rules
lrwxrwxrwx 1 root root  22 Dec  7 11:04 025_logitechmouse.rules - 
../logitechmouse.rules
lrwxrwxrwx 1 root root  12 Oct 24 12:20 050_hal-plugdev.rules - ../hal.rules
lrwxr-xr-x 1 root root  19 Dec  6  2004 cd-aliases.rules - ../cd-aliases.rules
lrwxr-xr-x 1 root root  13 Jun 22  2004 udev.rules - ../udev.rules
-rw-r--r-- 1 root root 721 Dec 16 17:21 z00_local.rules
lrwxrwxrwx 1 root root  19 Aug 20 12:17 z20_persistent.rules - 
../persistent.rules
lrwxrwxrwx 1 root root  12 Jul  7 09:40 z50_run.rules - ../run.rules
lrwxrwxrwx 1 root root  16 Oct 11 17:23 z55_hotplug.rules - ../hotplug.rules
lrwxrwxrwx 1 root root  19 Aug  5 04:34 z60_alsa-utils.rules - 
../alsa-utils.rules
lrwxrwxrwx 1 root root  15 Sep 22 13:11 z60_hdparm.rules - ../hdparm.rules
lrwxrwxrwx 1 root root  17 Jul  7 09:40 z70_hotplugd.rules - ../hotplugd.rules

-- /sys/:
/sys/block/sda/dev
/sys/block/sda/sda1/dev
/sys/block/sda/sda2/dev
/sys/block/sda/sda3/dev
/sys/block/sda/sda5/dev
/sys/block/sda/sda6/dev
/sys/block/sda/sda7/dev
/sys/block/sda/sda8/dev
/sys/block/sr0/dev
/sys/class/input/event0/dev
/sys/class/input/event1/dev
/sys/class/input/event2/dev
/sys/class/input/mice/dev
/sys/class/input/mouse0/dev
/sys/class/misc/agpgart/dev
/sys/class/misc/psaux/dev
/sys/class/misc/rtc/dev
/sys/class/scsi_generic/sg0/dev
/sys/class/scsi_generic/sg1/dev
/sys/class/sound/controlC0/dev
/sys/class/sound/pcmC0D0c/dev
/sys/class/sound/pcmC0D0p/dev
/sys/class/sound/pcmC0D1c/dev
/sys/class/sound/pcmC0D2c/dev
/sys/class/sound/pcmC0D3c/dev
/sys/class/sound/pcmC0D4p/dev
/sys/class/sound/timer/dev
/sys/class/usb_device/usbdev1.1/dev
/sys/class/usb_device/usbdev2.1/dev
/sys/class/usb_device/usbdev3.1/dev
/sys/class/usb_device/usbdev4.1/dev
/sys/class/usb_device/usbdev4.2/dev
/sys/class/usb_device/usbdev5.1/dev

-- Kernel configuration:
 isapnp_init not present.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages udev depends on:
ii  initscripts   2.86.ds1-6 Standard scripts needed for bootin
ii  libc6 2.3.5-8.1  GNU C Library: Shared libraries an
ii  libselinux1   1.26-1 SELinux shared libraries
ii  lsb-base  3.0-12 Linux Standard Base 3.0 init scrip
ii  makedev   2.3.1-79   creates device files in /dev
ii  sed   4.1.4-5The GNU sed stream editor

udev recommends no packages.

-- debconf information:
  udev/devfs-warning:
* udev/reboot-warning:



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340113: stunnel4: stunnel fails to run

2005-11-20 Thread Martin Schwenke
Package: stunnel4
Version: 2:4.140-1
Severity: grave
Justification: renders package unusable


stunnel loops for a long time trying to find library files and finally
terminates with:

Can't locate strict.pm in @INC (@INC contains: /etc/perl 
/usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 /usr/lib/perl5 
/usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl 
.) at /usr/share/perl/5.8/AutoLoader.pm line 3.
BEGIN failed--compilation aborted at /usr/share/perl/5.8/AutoLoader.pm line 3.
Compilation failed in require at /usr/lib/perl/5.8/POSIX.pm line 7.
BEGIN failed--compilation aborted at /usr/lib/perl/5.8/POSIX.pm line 7.
Compilation failed in require at /usr/sbin/stunnel line 26.
BEGIN failed--compilation aborted at /usr/sbin/stunnel line 26.

However, this message is misleading.  strace tells us:

...
open(/usr/share/perl/5.8/strict.pm, O_RDONLY|O_LARGEFILE) = 1022
...
open(/usr/share/perl/5.8/strict.pm, O_RDONLY|O_LARGEFILE) = 1023
...
open(/usr/local/lib/site_perl/strict.pm, O_RDONLY|O_LARGEFILE) = -1 EMFILE 
(Too many open files)
...

So the problem is really that something is looping.

Oh dear...

$stunnel_bin='/usr/sbin/stunnel';

That ain't right!  Shouldn't that be /usr/sbin/stunnel4?

Hmmm...

peace  happiness,
martin


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages stunnel4 depends on:
ii  adduser   3.78   Add and remove users and groups
ii  libc6 2.3.5-8GNU C Library: Shared libraries an
ii  libssl0.9.8   0.9.8a-4   SSL shared libraries
ii  libwrap0  7.6.dbs-8  Wietse Venema's TCP wrappers libra
ii  netbase   4.23   Basic TCP/IP networking system
ii  openssl   0.9.8a-4   Secure Socket Layer (SSL) binary a
ii  perl-modules  5.8.7-8Core Perl modules
ii  zlib1g1:1.2.3-8  compression library - runtime

stunnel4 recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#312937: gksudo works badly for commands with NOPASSWD

2005-06-10 Thread Martin Schwenke
Package: gksu
Version: 1.2.5-3
Severity: normal


I add an item to /etc/sudoers so I can run it without a password:

  martins ALL=(ALL) NOPASSWD: /usr/X11R6/bin/xterm

I then run it under gksudo:

  gksudo /usr/X11R6/bin/xterm

I get the following weird behaviour:

  1. The xterm window opens without requiring a password.  Yay!  I
 close the xterm.

  2. The password dialog appears.  :-(

 If I click OK or press the Enter key the password dialog
 disappears and another xterm window opens.

 If I click Cancel I don't get another xterm.

The password dialog should not reappear!

I also see the following error each time an xterm opens:

  Warning: Tried to connect to session manager, Authentication Rejected, reason 
: None of the authentication protocols specified are supported and host-based 
authentication failed

I don't get this error if I run sudo instead of gksudo.

Thanks...

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-rc4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gksu depends on:
ii  libatk1.0-0 1.10.1-2 The ATK accessibility toolkit
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libgksu1.2-01.2.6-3  library providing su and sudo func
ii  libgksuui1.0-0  1.0.4-3  a graphical fronted to su library
ii  libglib2.0-02.6.4-1  The GLib library of C routines
ii  libgtk2.0-0 2.6.7-2  The GTK+ graphical user interface 
ii  libpango1.0-0   1.8.1-1  Layout and rendering of internatio
ii  sudo1.6.8p7-1.1  Provide limited super user privile

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#307588: logcheck-database: Patterns in /etc/logcheck/ignore.d.workstation/udev are too strict

2005-05-03 Thread Martin Schwenke
Package: logcheck-database
Version: 1.2.39
Severity: minor


The patterns for udev are a bit too strict.  In particular, they don't
match this sort of thing:

  May  4 12:10:34 localhost udev[5851]: configured rule in 
'/etc/udev/rules.d/udev.rules[59]' applied, 'pcmC0D0c' becomes 'snd/%k'
  May  4 12:10:34 localhost udev[5851]: creating device node '/dev/snd/pcmC0D0c'

Problems include:

* Failure to match mixed alphanumeric device names like pcmC0D0c.

* Failure to match subdirectory in front of %k.

I'm using these:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ udev\[[0-9]+\]: (creating|removing) device 
node '/dev(/[[:alpha:]][[:alnum:]]*)+'$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ udev\[[0-9]+\]: configured rule in 
'[\./:[:alnum:]-]+\[[0-9]+\]' applied, (added symlink 
'[[:alnum:]]+'|'[[:alpha:]][[:alnum:]]*' becomes 
'([[:alpha:]][[:alnum:]]*/)+%k')$

and they seem to match all the relevant udev output.

Thanks...

peace  happiness,
martin

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.12-rc3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages logcheck-database depends on:
ii  debconf [debconf-2.0] 1.4.48 Debian configuration management sy

-- debconf information:
* logcheck-database/rules-directories-note:
  logcheck-database/standard-rename-note:
  logcheck-database/conffile-cleanup: false



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#280368: gnuserv: dtemacs should not start emacs iconified

2005-01-24 Thread Martin Schwenke
Hi Richard,

 Richard == Richard Lewis [EMAIL PROTECTED] writes:

 If you run dtemacs without any arguments, doesn't the
 invocation of gnuclient on the last line cause a second frame
 to appear that isn't iconified?  It does for me.

Richard hmm, it didn't do that for me, possibly because I had
Richard (gnuserv-start) at the end of .emacs.  I've now removed
Richard that and it does open a new frame.  However if you tell
Richard dtemacs to evaluate some code that calls yes-or-no-p then
Richard the question is asked in the minimised frame, so you have
Richard to unminimise that.  But i suppose there is nothing you
Richard can do about that?

Ahhh, that's a race condition!

If you call gnuserv-start from your .emacs and from the command-line
gnuserv starts, stops and starts again.  Sometimes dtemacs will catch
it when it is stopped.  If the performance of your machine is quite
consistent, things might always happen that way.  It took me ages to
work this out when it was happening to me...  :-)

I should document it...

True, certain things will try to operate on the minimised frame.  I
guess the thing to do if you're asking gnuserv to evaluate interactive
code is to make sure it has popped up a new, visible frame.  There
isn't much else you can do...

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#280368: gnuserv: dtemacs should not start emacs iconified

2005-01-10 Thread Martin Schwenke
Hi Richard,

Benjamin, the Debian gnuserv maintainer forwarded me your bug report.

By the way Benjamin, I've released gnuserv-3.12.7, which just contains
small updates from a more recent XEmacs and some updates to the
README.  I can't remember if it is important enough to include in
Debian...  :-)

 Richard == Richard Lewis [EMAIL PROTECTED] writes:

Richard Package: gnuserv
Richard Version: 3.12.6-1
Richard Severity: wishlist
Richard Tags: patch

Richard If emacs is not running, the dtemacs script starts it
Richard iconified.  But surely if you ran dtemacs you want to
Richard actually use emacs, and would prefer it to get the focus?

If you run dtemacs without any arguments, doesn't the invocation of
gnuclient on the last line cause a second frame to appear that isn't
iconified?  It does for me.  The idea is that everything but the last
line ensures there's an Emacs process to talk to, and the last line
then talks to that Emacs.

This is a case of swings and roundabouts.  That particular dtemacs
script was written for a bunch of university students to use via a
GUI.  The original version had some smarts to avoid the iconfied
frame and bring up the requested file (or perform the requested
action) in the original Emacs frame (if there wasn't an Emacs process
already contactable).  However, a student they edited a single file
they would often then close the frame when done, thus exiting Emacs
and negating a good part of the use of gnuserv.  There might have been
an are you sure question, but it didn't work well.  Adding the
iconfied frame helped this enormously, once they got used to it (and
stopped closing it).  It lowered the load on the student servers a
great deal...  :-)

Better than this would be to have Emacs run without an initial frame
at all.  I think XEmacs supports this via an -unmapped option.  I
mentioned a desire for a similar GNU Emacs option to RMS in April
2002, but I don't think it has happened.

Oh well...

peace  happiness,
martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]