editor crashes regularly, loosing all data since last save

1 msg	Re: [SECURITY] [DSA 922-1] New Linux 2.6.8 pack...
1 msg	Weihnachts-Angebot: Loesungen fuers Leben
1 msg	Byteventure Impulse 12/2005
6 msg	Mailman DoS CVE-2005-3573, debbug #339095
1 msg	Re: [SECURITY] [DSA 920-1] New ethereal package...

editor crashes regularly, loosing all data sinc...
\ Johannes Wiedersich (12 Dec 2005)

1 msg	You Need This Debian-russian-request
3 msg	help
1 msg	curl 7.13.2-2sarge4 fixes #342339 for sarge and...
1 msg	Re: [SECURITY] [DSA 918-1] New osh packages fix...
1 msg	Harder...Harder atnCth
1 msg	Highly Recommended Cailis ph
3 msg	Re: Re: Clear screen question
2 msg	gtk+2.0 2.6.4-3.1 (DSA 911-1)-- patch for CVE-2...
1 msg	Buyer beware - Penis patches!
3 msg	Question about iptables
4 msg	iptable: --seconds
2 msg	pb de livraison
1 msg	Avviso
1 msg	Error 554.5.0.0 - Resolve

Subject:	editor crashes regularly, loosing all data since last save
Group:	Debian-security
From:	Johannes Wiedersich
Date:	12 Dec 2005

I'm sorry, if I'm just too bad at looking at the documentation or
searching the archives.

I am missing information as to what is a bug that would warrant a fix in
stable. I filed two bug reports (#340699 and #325588) but nothing
appears to be happening in order to get things fixed.

Short summary:
- kile (editor) regularly crashes in default configuration, loosing data
entered since last save. (NB: Does this fall under the category 'data
loss' for release-critical bugs?)

- firestarter breaks nis in default configuration. There is no way to
configure firestarter (gui tool for a firewall) in a manner to work with
debian's default settings for nis; workaround is to manually tweak nis
to work with firestarter.

I would like to get both fixed in sarge, since both problems are serious
(data loss, loss of network functionality) and were rather difficult to
trace down (at least to me). I guess that quite a few people out there
will be affected as well and and encounter similar problems as myself.

Is there a way I could contribute to speed things up; apart from
sitting, waiting and seeing that nothing appears to be happening?

(In one case the maintainer sent a request for further information to
the bug tracking system without cc-ing me; I only accidentially found
his message on the web page.)

To sum it up: It would be nice and add to the transparency of the
process, if there was a web page on www.debian.org or bugs.debian.org
explaining to general users:

- what kind of bugs will be fixed for stable; which ones will only be
fixed for etch...

- what is the 'normal' procedure for the first category, the second
category and for security fixes.

- if a bug is release-critical for sarge, will there be a security
update for sarge? What is the time line for this?

Thanks for your help.

Johannes

--
To UNSUBSCRIBE, email to debian-security-REQUEST
with a subject of "unsubscribe". Trouble? Contact listmaster