Your message dated Fri, 15 Dec 2006 23:38:18 +0100 with message-id <200612152338.27815.debian@pusling.com> and subject line Closing moreinfo bugs has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: kdm_greet (and other programs) are creating lock files in /etc/qt3
- From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
- Date: Thu, 20 May 2004 13:36:41 +0000
- Message-id: <E1BQniz-0002m3-Ng@lkcl.net>
Package: kdm Version: 3.2.2 Severity: normal i am using Debian 2.6.6 kernel compiled with SE/Linux support. it therefore audits pretty much evveeerrrything. i note that kdm_greet attempts to create a file /etc/qt3/.qtrc_lock, when doing something as simple as logging in as an ordinary user. no programs are, as far as i am aware, allowed to write to /etc except configuring programs. surely the lock file should be created in /var/lock/qt3 (i note no such directory exists) don't worry, there are other programs doing the same thing: krootimage attempts to create a file /etc/qt3/.kstylerc.lock too :) eek, _and_ /etc/qt3/.qt_plugins_3.2rc.lock in fact, checking further, it looks like both programs kdm_greet and krootimage are _both_ attempting to write to all of these files. basically, none of this should be happening: they should be either in the home directory of the user (i note the existence of ~/.qt/.qtrc_lock) or in /var/lock/qt3. hope this helps, l. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux highfield 2.6.6-selinux1 #5 Tue May 18 16:33:29 GMT 2004 i686 Locale: LANG=C, LC_CTYPE=C
--- End Message ---
--- Begin Message ---
- To: 283890-done@bugs.debian.org, 295559-done@bugs.debian.org, 347148-done@bugs.debian.org, 358838-done@bugs.debian.org, 392037-done@bugs.debian.org, 291116-done@bugs.debian.org, 289238-done@bugs.debian.org, 369854-done@bugs.debian.org, 283505-done@bugs.debian.org, 271401-done@bugs.debian.org, 266144-done@bugs.debian.org, 264814-done@bugs.debian.org, 264781-done@bugs.debian.org, 264592-done@bugs.debian.org, 257286-done@bugs.debian.org, 250034-done@bugs.debian.org, 217689-done@bugs.debian.org, 200214-done@bugs.debian.org, 191858-done@bugs.debian.org, 256823-done@bugs.debian.org, 341687-done@bugs.debian.org, 342457-done@bugs.debian.org, 349285-done@bugs.debian.org, 369777-done@bugs.debian.org, 385563-done@bugs.debian.org, 390267-done@bugs.debian.org, 398409-done@bugs.debian.org, 280776-done@bugs.debian.org, 360624-done@bugs.debian.org
- Subject: Closing moreinfo bugs
- From: Sune Vuorela <debian@pusling.com>
- Date: Fri, 15 Dec 2006 23:38:18 +0100
- Message-id: <200612152338.27815.debian@pusling.com>
Version: 4:3.5.5-1 Hi! No information from submitter in 4 weeks. Closing bug. If they still occur, please send a mail to control@bugs.debian.org where the first line of the mail is "found nnn version" where nnn is the bug number and version is the version you have found the bug in. Please also write a mail to nnn@bugs.debian.org explaining exactly how to reproduce. /Sune -- Man, how may I do for configuring a provider? You neither should ever enable a editor, nor ever need to telnet to the GUI to log in the serial port to the parallel editor.Attachment: pgpQOMIzMa9dd.pgp
Description: PGP signature
--- End Message ---