Bug 517561 - [2.23] should migrate trash from the old location to the new one
[2.23] should migrate trash from the old location to the new one
Status: NEW
Product: gnome-session
Classification: Core
Component: gnome-session
git master
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2008-02-19 22:26 UTC by Sebastien Bacher
Modified: 2008-04-07 22:45 UTC (History)
4 users (show)

See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Sebastien Bacher 2008-02-19 22:26:25 UTC 
The trash location changed in gio, gnome-session should migrate datas which are still in the trash on upgrade
Comment 1 Sebastien Bacher 2008-02-19 22:26:48 UTC 
setting gnome target
Comment 2 Lucas Rocha 2008-03-31 19:08:10 UTC 
Hey Sebastien, maybe this is more suitable for a gnome-settings-daemon plugin? Hardcoding this in gnome-session is a no-go.
Comment 3 Dan Winship 2008-03-31 19:33:07 UTC 
Or maybe we should have a "gnome-migration" package, which would install a script that would run at startup and do various migrationy things if it's your first time logging in to a new GNOME version? (IIRC openSUSE does something like this.) I got annoyed that the setting of the old "don't blink the cursor in gnome-terminal" gconf key didn't automatically get migrated to the new "don't blink the cursor anywhere" gconf key...
Comment 4 Sebastien Bacher 2008-04-01 10:08:18 UTC 
I've no strong opinion on where a such migration code should go, vincent said that using gnome-session to open the bug was ok, you can reassign if you want though. Having migration code in the autostart directory might be easier
Comment 5 Vincent Untz 2008-04-07 22:45:38 UTC 
I've committed some migration code to gnome-2-22. Like Dan, I wanted to have a gnome-migration package. Maybe something we'll be able to do for 2.24...

Keeping open for trunk since we'll need to fix it there too, and I don't want the hack there for now.
Note You need to log in before you can comment on or make changes to this bug.