Removing dconf leaves dangling symlinks: "run-parts: failed to stat component /etc/cron.weekly/dconf: No such file or directory"
Bug #804188 reported by
Axel Beckert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dconf (Debian) |
Fix Released
|
Unknown
|
|||
dconf (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
/etc/cron.
run-parts: failed to stat component /etc/cron.
Please either
a) remove that symlink and make a shell script out of it which first checks, if /usr/bin/dconf exists and only then calls it, or
b) remove that symlink in the postrm script on removal already.
I'd prefer a) as it's the cleaner way.
Changed in dconf (Debian): | |
status: | Unknown → New |
Changed in dconf (Ubuntu): | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
Changed in dconf (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Some more details:
It can not be reproduced by just installing the package and removing it, as the symlink is created when dconf runs the first time.
The postrm script does delete the symlink, but only on "purge", not on "remove" (as experienced before).