Bug#496355: texmacs: Segfaults on file close

2008-09-03 Thread Matthew Woodcraft
I also built 1.0.6.15 from source, but I saw the same crash on file close as in the original report. Now that guile-1.8 1.8.5 has entered Lenny (1.8.5+1-4), I do not see the crash with the (same) locally-built texmacs 1.0.6.15, but I still see it with the Debian build (ie, 1:1.0.6.14-1). -M-

Bug#496355: texmacs: Segfaults on file close

2008-08-24 Thread Matthew Woodcraft
Package: texmacs Version: 1:1.0.6.14-1 Severity: important texmacs usually segfaults when I close a file. I think it may happen exactly when there is more than one buffer open. Steps to reproduce: rm -rf ~/.TeXmacs texmacs File - New File - Close document -- TeXmacs output: Welcome to

Bug#401920: sylpheed-claws-gtk2: doesn't start, crash instead

2007-03-05 Thread Matthew Woodcraft
I can reproduce this bug (still with version 2.6.0-1). Changing my gtk2 theme from 'Delightfully-Smooth' to 'thinice' gets rid of the crash. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (989, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to

Bug#371857: i810 doesn't restore console properly with vga=ext.

2007-07-01 Thread Matthew Woodcraft
Brice Goglin wrote: Is there a chance you try xserver-xorg-core 1.3 (in testing) and xserver-xorg-video-intel 2.0 (in experimental)? The latter is a major rework of the driver for intel graphic chipsets. I tried with the following combination (from today's sid): xserver-xorg-core

Bug#371857: i810 doesn't restore console properly with vga=ext.

2007-07-01 Thread Matthew Woodcraft
I wrote: I'll try with the version from experimental next. I have tried with xserver-xorg-video-intel 2:2.0.0-5 from experimental (and still xorg-server 2:1.3.0.0.dfsg-6) This was not a success. X will not start at all. It says: (II) intel: Driver for Intel Integrated Graphics Chipsets:

Bug#371857: i810 doesn't restore console properly with vga=ext.

2007-07-02 Thread Matthew Woodcraft
Brice Goglin wrote: That's very strange. There should be a full PCI scan in your log before the intel driver is even loaded, right between the lines below. It doesn't appear at all here. (--) using VT number 7 (II) Addressable bus resource ranges are It seems to mean that something

Bug#413959: glark: colons on file names are interpreted as separators

2007-07-04 Thread Matthew Woodcraft
According to the glark manpage, this a feature. You have to specify --no-split-as-path to disable it. -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#371857: i810 doesn't restore console properly with vga=ext.

2007-06-22 Thread Matthew Woodcraft
Brice Goglin wrote: About a year ago, you reported a bug in the Debian BTS regarding the i810 driver not restoring the console properly with vga=ext. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? Yes, I still see exactly the same

Bug#326193: 'Incoming Work Group' not honoured for files named with a leading dot

2005-09-02 Thread Matthew Woodcraft
Package: mailscanner Version: 4.41.3-2 When mailscanner unpacks a message's attachments to make them available to a virus scanner, it is supposed to set each file's group to the configured 'Incoming Work Group'. This works for most attachments, but if an attachment's filename begins with '.', the

Bug#365736: /etc/init.d/slony1 status can falsely claim that daemons are running.

2006-05-02 Thread Matthew Woodcraft
Package: slony1-bin Version: 1.1.5-1 If multiple slon daemon instances are configured, '/etc/init.d/slony1 status' reports that they are all running if any one of them is. I think this is caused by pidofproc() falling back to /bin/pidof when the pidfile for an instance does not exist. -M-

Bug#372740: Sensord won't start with lm85 chip, on current Debian kernels.

2006-06-11 Thread Matthew Woodcraft
Package: sensord Version: 1:2.10.0-5 Sensord fails to start, logging the following messages: sensord: sensord started sensord: Chip: lm85-i2c-0-2e sensord: Adapter: SMBus I801 adapter at 2000 sensord: V1.5: 1.56 sensord: -in0_min: 1.42 sensord: -in0_max: 1.58 sensord: VCore: 1.20

Bug#372740: Sensord won't start with lm85 chip, on current Debian kernels.

2006-06-13 Thread Matthew Woodcraft
Aurelien Jarno wrote: Yes, that's seems to be the problem. As I don't have such a chip, could you please try to add an ignore line for fan1_tach_mode, and also all other lines necessary to make sensord working? Then if you send me those lines, I will be able to fix the pacakge in consequence.

Bug#572775: xserver-xorg-video-radeon: xeyes causes X server to crash

2010-03-13 Thread Matthew Woodcraft
Michel Dänzer wrote: Does this still happen with a newer xserver-xorg-video-radeon, e.g. 1:6.12.5-1 from sid? If so, please try to get a backtrace with gdb, preferably with xserver-xorg-core-dbg and xserver-xorg-video-radeon-dbg installed. This symptom no longer occurs with

Bug#586425: compiz-plugins: Commands plugin doesn't close FDs before executing the command

2010-06-19 Thread Matthew Woodcraft
Package: compiz-plugins Version: 0.8.4-4 Severity: normal The compiz 'commands' plugin doesn't close file descriptors before executing a command. In the setup I'm using, this means all programs (eg, xterms) launched from compiz get the following unwanted open FDs: 3 -

Bug#543506: postgresql-common: pg_upgradecluster doesn't preserve per-database ACLs or configuration parameters

2009-08-25 Thread Matthew Woodcraft
Package: postgresql-common Version: 94lenny1 Severity: normal pg_upgradecluster doesn't preserve the contents of pg_database.datconfig or pg_database.datacl. (That is, it doesn't preserve the results of 'GRANT foo ON DATABASE bar TO baz' or 'ALTER DATABASE name SET foo TO bar'.) I think bug

Bug#625758: 'adduser --disabled-login' does not behave as documented.

2011-05-05 Thread Matthew Woodcraft
Package: adduser Version: 3.112+nmu2 Severity: normal The adduser manpage in squeeze contains the following: --disabled-login Do not run passwd to set the password. The user won't be able to use her account until the password is set. --disabled-password

Bug#613861: 'userv --builtin parameter' fails

2011-02-17 Thread Matthew Woodcraft
Package: userv Version: 1.0.5-0.2 Severity: normal 'userv --builtin parameter' fails. For example, on a clean installation: % userv --builtin parameter calling-user uservd: configuration override data:1: found newline (or comment followed by newline), expected linear whitespace uservd: error

Bug#613862: userv: Breakage with comments inside control structures

2011-02-17 Thread Matthew Woodcraft
Package: userv Version: 1.0.5-0.2 Severity: normal Comments inside 'if/fi' cause problems: they are properly ignored when the condition is true, but they give an error (which stops processing) when the condition is false. For example, with the following configuration file: if glob service

Bug#644788: Bug#654116: RFH: screen -- terminal multiplexor with VT100/ANSI terminal emulation

2012-01-04 Thread Matthew Woodcraft
Axel Beckert a...@debian.org wrote: Simon McVittie wrote: Would it be enough for the your old screen binary is /tmp/screen-yhpoe8r/screen notice to also say if your /tmp is mounted noexec, you might need to copy it elsewhere to run it? That's my current plan -- with the noexec notice just

Bug#683147: ERROR: install script from emacs-goodies-el package failed

2012-08-23 Thread Matthew Woodcraft
This problem no longer occurs with the current emacs-snapshot. The failing code in emacs-goodies-el was the following from eproject.el: (setf (getf (nth 3 (assoc type eproject-project-types)) key) value)) So I assume it was the same as this upstream bug report.

Bug#659474: spamassassin: sa-compile problem on upgrade

2012-02-11 Thread Matthew Woodcraft
Package: spamassassin Version: 3.3.2-2 Severity: normal I recently upgraded from Squeeze to testing, and the spamassassin upgrade (to version 3.3.2-2) didn't go smoothly. I have sa-compile enabled. I got the following error when dpkg tried to configure spamassassin: Running sa-compile (may take

Bug#697402: bzr-gtk: causes crash in pydoc -k when python-gtk2 is also installed

2013-01-26 Thread Matthew Woodcraft
Debian has in the past contained Python packages which have side-effects when imported which are worse than just crashing the calling process (for example, I've had pydoc crash my window manager). Arguably all such cases are bugs in those packages, but it seems likely that such bugs will appear

Bug#739369: joe-jupp: ^W (cut) often broken in jmacs if '-marking' is enabled

2014-02-17 Thread Matthew Woodcraft
Package: joe-jupp Version: 3.1.26-1 Severity: normal If I use jmacs with 'marking' in the configuration, often (but not always) ^W (cut) fails. Also, sometimes the 'region' highlighting fails to appear, and this seems to correspond to the times when ^W doesn't fail. To reproduce: cat

Bug#741512: clamav-base configure error ('/usr/share/doc/clamav-base/examples/clamd.conf does not exist!')

2014-03-13 Thread Matthew Woodcraft
Package: clamav Version: 0.98.1+dfsg-1+deb6u1 Severity: normal Upgrade to clamav 0.98.1+dfsg-1+deb6u1 (from squeeze-updates) failed with the following error: Setting up clamav-base (0.98.1+dfsg-1+deb6u1) ... Error: The new file /usr/share/doc/clamav-base/examples/clamd.conf does not exist!

Bug#741512: clamav-base configure error ('/usr/share/doc/clamav-base/examples/clamd.conf does not exist!')

2014-03-13 Thread Matthew Woodcraft
On 2014-03-13 12:31, Andreas Cadhalpun wrote: I couldn't reproduce this in a virtual machine: * install squeeze 6.0.9 * install clamav 0.97.8+dfsg-1~squeeze1 * update clamav to 0.98.1+dfsg-1~squeeze1 From which version did you upgrade? 0.97.8+dfsg-1~squeeze1 The following was

Bug#867715: openssl: "unknown group" error messages from 'openssl speed' ECDSA and ECDH

2017-07-08 Thread Matthew Woodcraft
Package: openssl Version: 1.1.0f-3 Severity: normal Running 'openssl speed', I see error messages from ECDSA and ECDH: ECDSA failure. 4146407744:error:100AE081:elliptic curve routines:EC_GROUP_new_by_curve_name:unknown group:../crypto/ec/ec_curve.c:3100: amd ECDH failure.

Bug#865378: guake: WM_CLASS is unhelpful ("Main.py")

2017-06-20 Thread Matthew Woodcraft
Package: guake Version: 0.8.8-1 Severity: normal In Jessie (guake 0.4.4), guake's WM_CLASS X property (according to xprop) was: WM_CLASS(STRING) = "guake", "Guake" In Stretch, it's the less informative WM_CLASS(STRING) = "guake", "Main.py" This makes it less convenient to configure window

Bug#872868: debian-policy: section numbers missing

2017-11-06 Thread Matthew Woodcraft
For what it's worth, I've submitted a Sphinx patch which implements section numbering in plain text: https://github.com/sphinx-doc/sphinx/pull/4218 I haven't interacted with Sphinx upstream before so I don't know whether they're likely to respond quickly. -M-

Bug#884134: python-rpy: Incompatible with the version of R in stretch

2017-12-11 Thread Matthew Woodcraft
Package: python-rpy Version: 1.0.3-30 Severity: grave Installing and importing the stretch version of python-rpy fails with the stretch version of R: « apt install python-rpy python Python 2.7.13 (default, Nov 24 2017, 17:33:09) [GCC 6.3.0 20170516] on linux2 Type "help", "copyright", "credits"

Bug#492901: please suppress the edns-disabled log category

2018-05-30 Thread Matthew Woodcraft
I think it would be better to leave the edns-disabled category enabled. Nowadays these messages are much rarer in normal circumstances, so they're less of a problem (also, Debian's default logcheck rules make logcheck ignore them). Last week my employer's ISP did something which broke many

Bug#890946: debian-policy: Editor policy is inconsistent with sensible-editor's behaviour

2018-02-20 Thread Matthew Woodcraft
Package: debian-policy Version: 4.1.3.0 Severity: normal Policy 11.4 describes the mechanism for determining the user's preferred editor: - check the EDITOR environment variable and use it if set; - (optionally): check the VISUAL environment variable and use it if set; - otherwise, use

Bug#891795: /usr/bin/sensible-editor: The select-editor mechanism should be removed

2018-02-28 Thread Matthew Woodcraft
Package: sensible-utils Version: 0.0.11 Severity: normal Background: Policy 11.4 describes the mechanism for determining the user's preferred editor: - check the EDITOR environment variable and use it if set; - (optionally): check the VISUAL environment variable and use it if set; -

Bug#890946: debian-policy: Editor policy is inconsistent with sensible-editor's behaviour

2018-02-28 Thread Matthew Woodcraft
Ian Jackson wrote: I think #482274 should probably simply be reverted. From the POV of the policy package: I think existing policy is correct. A bug should be filed against sensible-editor saying that #482274 should be reverted so that programs which use sensible-editor conform to policy. I

Bug#893569: barman: Mail from /etc/cron.d/barman should be delivered to root

2018-03-19 Thread Matthew Woodcraft
Package: barman Version: 2.1-1 Severity: normal The barman package installs /etc/cron.d/barman, which runs a command as user barman. At present the package doesn't take any special action to control where mail from cron is sent, so if there is any error output it will normally end up in

Bug#891976: localechooser: Unhelpful modifications to /root/.profile when locale "C" is chosen

2018-03-03 Thread Matthew Woodcraft
Package: localechooser Version: 2.69 Severity: normal Tags: d-i If I install Stretch using Debian-Installer and select language 'C' ('no localisation'), and default locale 'C', then I end up with the following lines at the end of /root/.profile: # Installed by Debian Installer: # no

Bug#922641: postgresql-common: pg_upgradecluster doesn't preserve ownership of the public schema

2019-02-18 Thread Matthew Woodcraft
Package: postgresql-common Version: 199.pgdg90+1 Severity: normal If I upgrade a cluster from v10 to v11 using pg_upgradecluster (in its dump-and-restore variant), in the new cluster each database has a public schema owned by user 'postgres', no matter who owned it before. Further, in databases