/etc/gnome/defaults.list claims to be user-modified, but I sure didn't do it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
scratch (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Quantal |
Won't Fix
|
Low
|
Unassigned |
Bug Description
I fired off an upgrade from quantal to raring, using do-release-upgrade -d -c (probably should have used update-manager, but server habits die hard). I then had one of my weekly quantal compiz crashes kill my ability to interact with the system. I waited until all disk activity stopped, rebooted, and started a dist-upgrade going.
The very first thing I was posed with was a dialog telling me that I or a script had changed /etc/gnome/
When filing this with ubuntu-bug, it also told me that I'd changed this file (but I said "yes" to the package manager! Doesn't that reset this?) and asked if I wanted to attach it to the bug. So sure, here it is.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: desktop-file-utils 0.21-0ubuntu3
ProcVersionSign
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
Date: Tue Mar 19 15:23:41 2013
EcryptfsInUse: Yes
MarkForUpload: True
SourcePackage: desktop-file-utils
UpgradeStatus: Upgraded to raring on 2013-03-19 (0 days ago)
mtime.conffile.
thank you for your bug report, the difference seems to be
"+application/ x-scratch- project= scratch. desktop"
the issue is with "scratch" which does: x-scratch- project= scratch. desktop" >> $DEFAULTS"
"debian/postinst: echo "application/
that's buggy, they shouldn't be changing conffiles from the postinst this way but rather get desktop-file-utils patched with the default added there