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-
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
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
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
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:
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
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]
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
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
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-
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
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.
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
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 -
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
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
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
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
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
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.
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
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
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
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!
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
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.
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
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-
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"
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
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
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;
-
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
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
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
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
Package: micro
Version: 2.0.6-2~bpo10+1
Severity: wishlist
Please could you register /usr/bin/micro for the 'editor' alternative?
The description is in policy 11.4
-M-
37 matches
Mail list logo
