After installing Mate, Firefox no longer open folders with Dolphin, but uses Caja -- even though Dolphin is set as file manager in KDE's configuration "Standard Applications". Is this somehow related to bug 4461 ? Steps: 1. Get Mageia 5 RC3 installed with Xfce and KDE. 2. Search with Google for some file (e.g.: cheatsheet filetype:pdf). 3. Download said file. 4. After the download finishes, click on FF's down arrow and on little folder icon to open folder with downloaded file. 5. Verify that Firefox uses Dolphin to view directory/folder. 6. Install Mate. 7. Open Firefox. 8. Search with Google for some file (e.g.: cheatsheet filetype:pdf). 9. Download said file. 10. After download finishes, click on FF's down arrow and on little folder icon to open folder with downloaded file. Expected: Dolphin would open the desired folder as before. Result: Firefox tries to open Caja to view folder. Please note that -- in Mageia 5 RC3 on KDE -- Caja is not even working now, as per bug 15577 . This can be verified with a terminal window open and running "journalctl -f". For convenience, such messages are reproduced here: === Mar 31 22:56:26 localhost caja[16723]: [N-A] Caja-Actions Tracker 1.7.1 initializing... Mar 31 22:56:27 localhost caja[16723]: [N-A] Caja-Actions Menu Extender 1.7.1 initializing... Mar 31 22:56:27 localhost org.freedesktop.FileManager1[8054]: Initializing caja-open-terminal extension Mar 31 22:56:27 localhost org.freedesktop.FileManager1[8054]: Initializing caja-image-converter extension Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: The program 'caja' received an X Window System error. Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: This probably reflects a bug in the program. Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: The error was 'BadDrawable (invalid Pixmap or Window parameter)'. Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: (Details: serial 7 error_code 9 request_code 53 minor_code 0) Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: (Note to programmers: normally, X errors are reported asynchronously; Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: that is, you will receive the error a while after causing it. Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: To debug your program, run it with the --sync command line Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: option to change this behavior. You can then get a meaningful Mar 31 22:56:28 localhost org.freedesktop.FileManager1[8054]: backtrace from your debugger if you break on the gdk_x_error() function.) === The net result is that FF lost a functionality: no longer opens the download folder.
Funny, in an upstream bug report about this issue, I thought for a second this comment was written by you ;-) : https://bugzilla.mozilla.org/show_bug.cgi?id=258085#c11 The more users comment there that this is a problem for them, too, the more chance it'll be fixed.
CC: (none) => doktor5000, marja11See Also: (none) => https://bugzilla.mozilla.org/show_bug.cgi?id=258085Whiteboard: (none) => UPSTREAM
Keywords: (none) => UPSTREAMWhiteboard: UPSTREAM => (none)
I've seen that before and was looking to add the comment to this bug! But I forgot I probably found it via Google or something and it was nowhere to be found in bugs.mageia... Good catch!
A quick reply for now, the issue should be workaroundable by : mkdir -p ~/.local/share/dbus-1/services cat << EOF > ~/.local/share/dbus-1/services/org.freedesktop.FileManager1.service [D-BUS Service] Name=org.freedesktop.FileManager1 Exec=/usr/bin/false EOF I will comment more in depth on this issue later.
CC: (none) => lmenut
I think in the past they simply called the application associated with inode/directory which is usually the default file manager. Maybe I can find a patch for that in older bugs. Also I think at least for the KDE integrations patches we use this should be fixed. Maybe we can deduce some generic fix from those ... But I'm still curious for Luc's comment ;)
Status: NEW => ASSIGNEDAssignee: bugsquad => doktor5000
> I think in the past they simply called the application associated with inode/directory which is usually the default file manager. Wouldn't that be THE problem? I mean there I am running KDE happy with my life because I got Dolphin to manage files. Then I go and install Mate just because, hey, everybody says Mate is cool, so let's try it. And it changes the inode/directory mime-type associated utility from Dolphin to Caja. Or did the previous KDE patches have a feature to undo this change?
> Wouldn't that be THE problem? Sorry for perhaps an improper language. It was for emphasis, not sarcasm neither did I intend to sound rude.
Per Renato's comments on bug#15604, this also effects Mageia 4 too.
CC: (none) => tarakbumbaWhiteboard: (none) => MGA4TOO
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=15604
This bug is somewhat related to bug 15604. I noticed today that Firefox is again using Dolphin in Cauldron; unfortunately it's not ok yet in Mageia 4 (I just tested in Mageia 4 X86_64).
(In reply to Renato Dali from comment #8) > This bug is somewhat related to bug 15604. > > I noticed today that Firefox is again using Dolphin in Cauldron; > unfortunately it's not ok yet in Mageia 4 (I just tested in Mageia 4 X86_64). No, bug #15604 and this issue is unrelated. Per comment #1 it is an firefox upstream issue.
Hmm, obviously you're right and I confused things. But I'm 100% sure Dolphin was opened when I tested FF in Cauldron last night. Is it possible they got it fixed in FF while we were coincidentally testing Caja's takeover of KDE's desktop? The mind boggles!
Attila, haven't you by chance used Luc's hint in comment 3 and hacked the whole thing into working well even with the upstream bug when you fixed bug 15604? Because, as reported in bug 15832, FF is starting Dolphin in KDE now. So, pending further patches to fix the observed delay, couldn't we consider the present bug fixed -- from the user point of view? I agree it's not the same situation but it's working now -- except for the first-time delay, of course.
On a second thought, Florian's suggestion in comment #4 is even better, because it reuses past knowledge and is independent of Mozilla. Not to make little of them, FF is my bread-and-butter, but they have A LOT to think about (including hardware now!).
(In reply to Luc Menut from comment #3) > A quick reply for now, the issue should be workaroundable by : > mkdir -p ~/.local/share/dbus-1/services > cat << EOF > > ~/.local/share/dbus-1/services/org.freedesktop.FileManager1.service > [D-BUS Service] > Name=org.freedesktop.FileManager1 > Exec=/usr/bin/false > EOF > > I will comment more in depth on this issue later. More commentary appreciated :) Is this because firefox tries to query the default file manager via dbus nowadays?
Well, it's working as expected now... if we don't mind that small eternity on the first call -- more than 26 seconds to call a file manager (bug 15832, comment # 13).
Whiteboard: MGA4TOO => MGA4TOO MGA5TOO
Can this bug report be closed?
Keywords: (none) => NEEDINFOWhiteboard: MGA4TOO MGA5TOO => MGA4TOO
Just to make sure I installed M4.1 again and had all updates installed. It worked the same as Mageia 5 RC: Dolphin was called by Firefox in KDE. Installing Mate also caused a 26+ second delay on the first file manager activation from Firefox. IMHO it can be closed, I don't know why it does not happen anymore; maybe it was solved like Doktor5000 suggests in comment 13... Let's not look a gift-horse in the mouth. :-)
Closing then
Keywords: NEEDINFO => (none)Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
------(In reply to Renato Dali from comment #16) > IMHO it can be closed, I don't know why it does not happen anymore; maybe it > was solved like Doktor5000 suggests in comment 13... I didn't suggest it was solved, I just asked Luc about the commentary he wanted to add. Also the org.freedesktop.FileManager1.service he suggested to create seems to show that there is an underlying bug. But if you prefer to close this ...
> I didn't suggest it was solved Further clarifying, I (the reporter) could no longer reproduce the bug. It lost its raison-d'être... that's why I thought it could be closed. Of course, in detective movies, an investigator would never be bothered with minor details like e.g. a case being closed... ;-P