Bug#303687: Dumps core on start

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 dir

Bug#303764: Not Ready for Sarge

Package: rails Version: 0.11.1-2 Severity: serious Rails is under development and will have (could have) a lot of changes before the 1.x milestone. It should not be added to Sarge at this time. Rails is an arch all package and should have all its dependencies satisfied in Sarge for some time. If

Bug#303687: Should be fixed

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

Bug#303687: Dumps core on start

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:

Bug#303687: Should be fixed

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

Bug#303687: Should be fixed

On Apr 8, 2005 2:15 PM, Steve Langasek <[EMAIL PROTECTED]> wrote: > The fix was in the libgconf11 binary package, not the gconf binary package. > Do you have the latest version of libgconf11 installed as well? I can verify now that with new libgconf11 installed, gnucash 1.8.10-11 does not crash on

Bug#307663: PostgreSQL Character Conversion and tsearch2 Module Vulnerabilities

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

Bug#307663: PostgreSQL Character Conversion and tsearch2 Module Vulnerabilities

> 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 annouc

Bug#308272: Cannot distribute in Debian

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 distribution

Bug#308855: Privilege escalation in ELF core dump (fs/binfmt_elf.c)

Package: kernel-source-2.6.8 Version: 2.6.8-15 Severity: critical Tags: security patch >From Secunia advisory http://secunia.com/advisories/15341/ DESCRIPTION: Paul Starzetz has reported a vulnerability in the Linux kernel, which can be exploited by malicious, local users to gain escalated privil

Bug#308855: reassign

reassign 308855 kernel thanks I probably shoud reassign this to the kernel pseudo-package since it applies to ALL of the kernels.. According to iSec, there is a quick workaround for the problem, "A hotfix for this vulnerability is to disallow processes to drop core. This can be accomplishe

Bug#303991: Huh?

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]

Bug#852532: olvwm: source code not 64-bit clean, SIGSEGV everywhere

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 c

Bug#852532: Acknowledgement (olvwm: source code not 64-bit clean, SIGSEGV everywhere)

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: st_insert(

Bug#442946: *.debian.pool.ntp.org do not exist on 4 of 5 pool.ntp.org name servers

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 [a-e].ntpns

Bug#571779: dvi2ps: FATAL-- cannot open fontdesc file "bikan-mor2"

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: \documentcl

Bug#571779: closed by OHURA Makoto (Bug#571779: fixed in dvi2ps 4.1j-3)

> 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]