← Back to team overview

touch-packages team mailing list archive

[Bug 285998] Re: mv or rm of any XDG user dir causes its definition to change to wrong, oversimple $HOME/

 

** Description changed:

- Tested in Hardy and Intrepid
+ $ rmdir ~/Videos
+ ...
+ $ mkdir ~/Videos
  
- 1)
- Delete ~/Templates
- Rebooting
- Change in ~/.config/user-dirs.dirs to remove the Templates folder as a link for the shortcut (RightClick > Create Document > Template)
  
- 2)
- Creating  ~/Templates
- Rebooting
- There is no change in ~/.config/user-dirs.dirs even when ~/Templates it present at login, therefore the Template shortcut no longer works
+ Hours later, find apps doing crazy things in home directory.
  
- Is this intentional or a bug?
+ During the elided period between rmdir and mkdir, if the XDG functions
+ were run, the user's intent is forever lost, and its value is set to the
+ user's home directory.
+ 
+ Apps can not rely on XDG functions not to lie about what the user wants. It prefers to say what exists, not now when the app is accessing it, but when the XDG functions ran. It does not provide a file descriptor for an
+ open_at(2) call. It provides a stale, text name of what used to exist on disk, and often not even what the user wanted.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu.
https://bugs.launchpad.net/bugs/285998

Title:
  mv or rm of any XDG user dir causes its definition to change to wrong,
  oversimple $HOME/

Status in Media Scanner v2:
  New
Status in “mediascanner2” package in Ubuntu:
  New
Status in “xdg-user-dirs” package in Ubuntu:
  Confirmed

Bug description:
  $ rmdir ~/Videos
  ...
  $ mkdir ~/Videos

  
  Hours later, find apps doing crazy things in home directory.

  During the elided period between rmdir and mkdir, if the XDG functions
  were run, the user's intent is forever lost, and its value is set to
  the user's home directory.

  Apps can not rely on XDG functions not to lie about what the user wants. It prefers to say what exists, not now when the app is accessing it, but when the XDG functions ran. It does not provide a file descriptor for an
  open_at(2) call. It provides a stale, text name of what used to exist on disk, and often not even what the user wanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mediascanner2/+bug/285998/+subscriptions