Created attachment 9860 [details] enable media insertion options Description of problem: Management options of inserted media of caja-file-management-properties command are ignored. It has already been fixed by mate developers, see: https://github.com/mate-desktop/caja/issues/807 https://github.com/mate-desktop/caja/commit/d3b66148f9b914fa0451508c6ddb075d0fab8fdb Version-Release number of selected component (if applicable): caja-1.18.3-1 How reproducible: Introduce a USB key, wait for it to mount, and nothing else happens (no opening of caja file browser). The same happens using camera, blank CD, etc. I did fix it using the small attached patch and a rebuilt of the caja rpm.
Assigning to the caja maintainer.
Assignee: bugsquad => tarakbumbaCC: (none) => marja11Keywords: (none) => PATCH
Thank you reporting. I have updated caja to upstream bugfix version which should fix this issue along with several ones. Please test and report back.Greetings. Suggested advisory: ======================== Updated caja packages fix several issues: - Wrong behaviour with key "enter" while renaming files in list view (upstream #698) - When renaming files in Caja, pressing Shift+Del does not "cut the selected part of the name;instead, it works as if you wanted to "permanently delete" the file (upstream #509) - High cpu usage while loading background image (upstream #606) - Enable mousewheel scrolling like it was with GTK+2 on pathbar ( upstream #779) - Browse media after mounting is broken (mga #22279 and upstream #807 ) - "Open With" dialog "Open" button's text misaligned (upstream #828) References: https://github.com/mate-desktop/caja/issues/698 https://github.com/mate-desktop/caja/issues/509 https://github.com/mate-desktop/caja/issues/606 https://github.com/mate-desktop/caja/issues/779 https://github.com/mate-desktop/caja/issues/828 https://github.com/mate-desktop/caja/issues/807 https://bugs.mageia.org/show_bug.cgi?id=22279 https://github.com/mate-desktop/caja/compare/v1.18.3...v1.18.5 ======================== Updated packages in core/updates_testing: ======================== caja-1.18.5-1.mga6 libcaja-extension1-1.18.5-1.mga6 libcaja-gir2.0-1.18.5-1.mga6 libcaja-extension-devel-1.18.5-1.mga6 caja-schemas-1.18.5-1.mga6 SRPMS: ======================== caja-1.18.5-1.mga6.src.rpm
Re-assigning to QA Team to test caja-1.18.5-1.mga6 update.
Assignee: tarakbumba => qa-bugs
Mageia 6 :: x86_64 Not a caja user but updated it and tried out the issues listed. 698 appears to be fixed 509 is still a problem 606 looks fine. F5 refreshed the desktop and there were no rogue process spawned. 779 Probably not fixed. If the 'location bar' is the one showing the current position in the directory tree then scrolling has no effect. 828 has not been fixed - Open is still justified left 807 not fixed - medium appears in the list and an icon appears on the desktop Over to you Atilla.
CC: (none) => tarazed25
Please see Len's comment 4 Atilla
CC: (none) => tarakbumba
Thanks Claire. re comment 4: Had a thought. On 64-bit machines we usually try 'lib64' first. Tried installing lib packages where available and ran test 807 again. This time the autorun function worked - a new caja window popped up after a USB key was plugged in. With updates testing enabled libcaja-extension1 pulled in a whole slew of i586 libraries including libwayland-egl1 from tainted. 1/27: libatk1.0_0 2/27: libwayland-egl1 3/27: libxcursor1 4/27: libepoxy0 5/27: libmount1 6/27: libgio2.0_0 7/27: libxft2 8/27: libdatrie1 9/27: libthai0 10/27: libxrandr2 11/27: libusb1.0_0 12/27: libgusb2 13/27: libxinerama1 14/27: libxcomposite1 15/27: libwayland-cursor0 16/27: libjasper1 17/27: libgdk_pixbuf2.0_0 18/27: liblcms2_2 20/27: libpixman1_0 21/27: libcairo2 22/27: libpango1.0_0 23/27: libatspi0 24/27: libatk-bridge2.0_0 25/27: libgtk+3_0 26/27: libcaja-extension1 27/27: libglib-networking-gnutls $ urpmq --requires-recursive caja | sort -u lists 64-bit libraries and 32-bit (presumably noarch) so it looks like the fault may be mine. Looks like I shall have to tighten up my testing procedures. Testing the issues again shows that all have been fixed. Good for 64 bits and under our new policy (?) of restricting tests to x86_64 could probably be validated.
Whiteboard: (none) => MGA6-64-OK
Thank you for testing Len. But caja should not pull i586 libs on a 64 bit system. Would you mind to re-test with only caja-1.18.5-1.mga6, lib64caja-extension1-1.18.5-1.mga6, lib64caja-gir2.0-1.18.5-1.mga6 and caja-schemas-1.18.5-1.mga6 please? May be there were mirror issues when you first tried.
re comment 7: Not a problem Atilla. Sometime this morning hopefully.
Testing again on Mageia 6, x86_64, on another machine. Checked the issues - could reproduce them. Updated the packages: caja-1.18.5-1.mga6 caja-schemas-1.18.5-1.mga6 lib64caja-extension1-1.18.5-1.mga6 lib64caja-extension-devel-1.18.5-1.mga6 lib64caja-gir2.0-1.18.5-1.mga6 Killed the running caja process, which respawned a new one. Removed the rogue process from the previous F5 refresh test. Checked each of the issues listed and found that all had been fixed. This is definitely OK now. Validating.
Whiteboard: MGA6-64-OK => MGA6-64-OKKeywords: (none) => validated_updateCC: (none) => sysadmin-bugs
@Len: Thank you once again for your persistance in testing. Advisory done.
Keywords: (none) => advisoryCC: (none) => lewyssmith
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0010.html
Status: NEW => RESOLVEDResolution: (none) => FIXED