I retract "SIGSEGV everywhere". If I compile client.c with -O0, then
the third SIGSEGV is avoided, and I don't see any others.
Summary: olvwm runs on my system only if I make all three of these
changes, each of which avoids a SIGSEGV:
In cursors.c, remove (int) from this line:
Package: olvwm
Version: 4.4.3.2p1.4-28.2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The latest version (4.4.3.2p1.4-28.2) immediately crashes with SIGSEGV
on my x86_64 system. I tried building it from source with debug
symbols, and discovered that it is not 64-bit
Source: dvi2ps
Source-Version: 4.1j-3
We believe that the bug you reported is fixed in the latest version of
dvi2ps,
I installed that version, and now instead of getting an error message
(dvi2ps: FATAL-- cannot open fontdesc file bikan-mor2) I get a
SIGSEGV:
kernel: [8930844.284122]
Package: dvi2ps
Version: 4.1j-2
Severity: grave
Justification: renders package unusable
Whenever I run 'dvi2ps foo' I get the following error message (and
nothing else):
dvi2ps: FATAL-- cannot open fontdesc file bikan-mor2
This used to work. It happens even for a trivial foo.tex:
Package: ntp
Version: 1:4.2.4p3+dfsg-1
Severity: grave
Justification: renders package unusable
Of the five name servers for pool.ntp.org, four of them claim there is no
such host as 1.debian.pool.ntp.org, etc. To investigate this:
dig -t ns pool.ntp.org
# Shows the name servers to be
Why are you uploading dbmail2? Why not just upload dbmail 2.x as dbmail?
I mean, you are uploading dbmail2 and having dbmail removed? This
doesn't make any sense.. sorry.
- Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: unrar-nonfree
Severity: serious
It appears that the copyright does not permission distribution in
Debian without a written permission, yet I find no such permission in
debian/copyright. More specifically,
3. The unRAR utility may be freely distributed, provided the
Package: postgresql
Severity: grave
Tags: security sarge
From:
http://secunia.com/advisories/15217/
Workarounds (aka, fixes :)
http://www.postgresql.org/about/news.315
DESCRIPTION:
Two vulnerabilities have been reported in PostgreSQL, which can be
exploited by malicious users to
Thanks for the report. I already uploaded a new package into Sid which
fixes this and spoke with the release and security team. The new
version will enter Sarge in two days (usual urgency=high upload),
release team approved Sarge inclusion.
Thanks. I see you also read the PostgreSQL
On Apr 8, 2005 3:56 AM, Josselin Mouette [EMAIL PROTECTED] wrote:
Could you please tell us whether gnucash still crashes for you with the
latest (1.0.9-7) gconf packages?
No, gnucash -11 with gconf 1.0.9-7 does not work. I get the same error
as before,
gtkhtml-ERROR **: gconf error: Failed to
On Apr 8, 2005 12:43 AM, Thomas Bushnell BSG [EMAIL PROTECTED] wrote:
severity 303687 normal
reassign 303687 gconf2
thanks
Adam M. [EMAIL PROTECTED] writes:
Package: gnucash
Version: 1.8.10-11
Severity: grave
gnucash dumps core on startup after the latest update
Ahh but now I can't test it until Monday morning... I will verify the
fix for i386 on Monday if no one beats me to it.
- Adam
On Fri, 8 Apr 2005 12:15:16 -0700, Steve Langasek [EMAIL PROTECTED] wrote:
On Fri, Apr 08, 2005 at 12:27:13PM -0500, Adam M wrote:
On Apr 8, 2005 3:56 AM, Josselin
Package: gnucash
Version: 1.8.10-11
Severity: grave
gnucash dumps core on startup after the latest update.
open(/home/adamm/.gconfd/lock/ior, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/usr/share/locale/en_CA.UTF-8/LC_MESSAGES/gconf1.mo, O_RDONLY) =
-1 ENOENT (No such file or
13 matches
Mail list logo
