Cleaning up ~/.gksu.lock
Bug #1338028 reported by
Removed by request
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libgksu (Ubuntu) |
In Progress
|
Undecided
|
Unassigned | ||
Bug Description
I'm using Ubuntu 14.10 dev with gksu 2.0.2-6ubuntu2. If a gksu instance is started the file ~/.gksu.lock will be created but it is not cleaned up after gksu is exited. Maybe directly before unlocking the file descriptor gksu can remove this file to keep the user directory more clean.
Related branches
lp:~filip-sohajek-deactivatedaccount/ubuntu/utopic/libgksu/fix-for-1338028
- Łukasz Zemczak: Needs Fixing
- Ubuntu branches: Pending requested
-
Diff: 25 lines (+7/-1)2 files modifieddebian/changelog (+6/-0)
libgksu/libgksu.c (+1/-1)
| Changed in gksu (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Filip Sohajek (filip-sohajek) |
| affects: | gksu (Ubuntu) → libgksu (Ubuntu) |
Revision history for this message
| Łukasz Zemczak (sil2100) wrote | #1 |
To post a comment you must log in.
The author still needs to work a bit on getting the proper fix, but this might be anyway blocked by us needing a Debian merge for libgksu (because of a FTBFS seen currently) - as per merge request comment.