3130 2012-09-18 15:54:16 +0000 Go menu in File Manager gives "operation not supported" 2017-11-07 11:39:09 +0000 1 1 6 Yocto Project Subprojects Sato sato svn x86 Multiple RESOLVED WONTFIX Low normal Future 1 corneliux.stoicescu maxin.john sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 25365 0 corneliux.stoicescu 2012-09-18 15:54:16 +0000 Selecting the Trash folder in the File Manager utility gives an "operation not supported" error. Please note that if you use right-click to open a new tab in the File Manager, the error is not shown untill restart of the utility. Build: core-image-sato-qemux86 Commit: e5c3513ca8abb21eb5e9b8c19d1b9199b14ae07c The nightly build: http://autobuilder.yoctoproject.org/pub/nightly/20120916-2 I will test this on other builds as well and come back with feedback. 25373 1 ross.burton 2012-09-18 18:03:25 +0000 At a hunch, the trash support hasn't been built (because it's GPLv3). 25462 2 corneliux.stoicescu 2012-09-20 13:50:05 +0000 Same error apprears when using "Menu > Go > Trash Can" and other options in the "Go" menu like "My Comouter" and "Network Drives". 29822 3 ross.burton 2013-02-14 16:39:18 +0000 pcmanfm is missing dependencies on gvfs, but as we don't build that (yet) there's not a lot we can do about that. Low priority. 58244 4 ross.burton 2016-01-26 16:26:13 +0000 Reassigning to Jussi as he's now the Lord of Sato. Considering this bug is years old it clearly needs retesting first! 76937 5 ross.burton 2017-09-18 18:04:08 +0000 Maxin, can you spend a minute replicating this on a recent image? 76968 6 maxin.john 2017-09-19 14:32:16 +0000 (In reply to comment #5) > Maxin, can you spend a minute replicating this on a recent image? Yes, It still happens in the master branch. It can be triggered using "Menu > Go > Trash Can" "Menu > Go > Devices" "Menu > Go > Network" 77517 7 maxin.john 2017-10-11 13:32:41 +0000 As Ross suggested, RDEPENDS on "gvfs" helps here. The "operation not supported" error goes away after including "gvfs". However,bringing "gvfs" to oe-core will be difficult as it depends on the below listed packages in meta-oe (ie: bringing gvfs means, bringing these packages to oe-core as well): 1. gnome-common 2. gphoto2 3. gvfs 4. libatasmart 5. mozjs 6. polkit 7. udisks Reasonable approach will be to build and include gvfs in the image from it's present location: "meta-openembedded/meta-gnome" 78018 8 maxin.john 2017-11-07 11:39:09 +0000 Including "gvfs" package in the image from "meta-gnome" fixes this error. Moving "gvfs" package to oe-core is not feasible.