Bug#559632: leaves lock file in home directory
Peter Eisentraut
petere at debian.org
Sat Dec 5 21:57:57 UTC 2009
Package: gksu
Version: 2.0.2-2+b1
Severity: minor
After every use, a file ~/.gksu.lock is left in the home directory. Presumably,
a lock file should be cleaned up when the program that created it exits.
Alternatively, if that is not how it is supposed to work, please add
documentation about this file somewhere.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gksu depends on:
ii gnome-keyring 2.28.1-2 GNOME keyring services (daemon and
ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra
ii libfontconfig1 2.6.0-4 generic font configuration library
ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib
ii libgconf2-4 2.28.0-1 GNOME configuration database syste
ii libgksu2-0 2.0.13~pre1-1 library providing su and sudo func
ii libglib2.0-0 2.22.2-2 The GLib library of C routines
ii libgnome-keyring0 2.28.1-2 GNOME keyring services library
ii libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface
ii libpango1.0-0 1.26.1-1 Layout and rendering of internatio
ii libstartup-notification0 0.10-1 library for program launch feedbac
ii sudo 1.7.2p1-1 Provide limited super user privile
gksu recommends no packages.
gksu suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list