Can someone please tell me how to implement this fix step by step. I have no idea what to do with the code very new to linux. Thanks so much.
I donât understand why you donât update Caja? Why this is still not fixed? It is so annoying to work, open Downloads in Firefox and then the whole system freezes. These sort of things show which Linux distributions you can rely on and it doesnât look good for Ubuntu Mate.
1 Like
I understand your trouble. Itâs also annoying for me. But my âworkaroundâ is to open the Downloads-Folder direct in Caja. You have to know, Ubuntu MATE 17.04 is âonlyâ a Short Term Support Version. For a stable version you should use 16.04. But i agree, itâs irritating. Further there seems to be a fix for this which is not available
1 Like
I would understand if there would be bugs, and the staff would investigate and they wouldnât be able to provide a solution. But to have a bug that can freeze the system, and then, luckily, come up with a fix that works, but chose to not deliver it through the update system, itâs so strange for me.
Why would they fix a bug if they donât intend to share it with the world?!?!?! I bet there are users out there that experienced the bug and have no idea about this topic. Maybe they think that Ubuntu Mate is not stable, and that it randomly crashes. They would be right to think that. Except that it isnât random, the developers know why it happens, but they refuse to fix it for the non-tech users.
For me, this attitude is so disappointing.
@Etamuk, I know 17.04 is a Short Term Support Version, but it is still in support. Itâs the latest version, and it is supposed to be stable. Which it isnât for the most users that click on Downloads in Firefox.
1 Like
I would like to remind you, @xandor, that fixing bugs takes time.
The bug is now fixed upstream in caja version 1.18.3.
In order for an update to make it into Ubuntu MATE 17.04, it has to first undergo the Stable Release Update process. Furthermore because Ubuntu is based off of Debian, there might be another layer to go through before an update can reach Ubuntu.
Please stop assuming stuff like:
or
I would further remind you that our leader has a life, including a family, and that maintaining Ubuntu MATE is not his job. It is something he does in his free time for no profit.
2 Likes
From my point of view, this is not a regular bug. This is a critical bug, and in my mind that means that these kind of bugs would be fixed much faster. Firefox is the default browser in Ubuntu Mate, and if users click on Downloads, the system would freeze. The bug has been confirmed and a solution now exists. But not for me + most of the other users. I guess, if I forget, and click downloads, I should just get used with the system freeze. But hey, it seems that I donât get it, and the proper way to deal with this, is just accept the freezes.
So you are implying that the project depends on only one person? Of course is normal if he doesnât have time, but I would think that other people would have to deal with the critical bugs when the main developer canât.
1 Like
[quote=âxandor, post:27, topic:12630â]This is a critical bug, and in my mind that means that these kind of bugs would be fixed much faster.[/quote]Personally, I feel youâre kind of driving the point home a bit excessively. Yes, it is a severe bug but it is not that critical.
First of all, there is a very simple workaround. Secondly, Firefox may be the default browser but it is far from the most used browser. Firefoxâs day in the spotlight has come⌠and gone. Servo (the new backend in development by Mozilla) might see it return to that spotlight. Eventually.
The fact it is default mostly has to do with the license and development model of Firefox.
And lastly, bugs do take time to fix. It has been said before but it is not something you should ignore. Take the recent WannaCrypt outbreak for example. That used an exploit in the Windows operating system to spread itself. It was fixed but not before the outbreak actually was able to do some damage.
And there weâre talking about Microsoft. A massive commercial entity whose influence actually outreaches a great number of countries. And even in that case it still took time. And the bug/exploit in question was far, far, far more severe. This crashbug in FF isnât going to create the next WannaCrypt outbreak. It is just going to annoy a few users, nothing more.
Patience is a virtue and with a very easy workaround available to you, I would personally find it embarassing to exaggerate the severity of this situation.
I have no idea how to fix it. It wouldnât be wise to asume that everyone is experienced in Linux and have the same tech level. Am I alone? Look at @figarow in this thread, what was your response guys? You ignored him.
This is true when it comes to Win and Mac. On Linux, Firefox is still probably the most used browser. [quote=â1Q7FE6zp, post:28, topic:12630â]
And lastly, bugs do take time to fix.
[/quote]
I understand that it takes time to fix bugs, but once a fix has been developed, it would make sense to see it implemented through the official channels. Yeah, WannaCrypt was more dangerous, but it was fixed asap once a solution was found. In the firefox case, the bug has been fixed 21 days ago, but still hasnât been delivered through the update system.
A severe bug, for me, it would be when only an app would be affected. But when the whole system is not responding anymore, I would think this is a really serious issue, and should be treated as a critical bug.
" I canât use my laptop anymore, but hey, itâs just a regular bug, donât worry. I feel much better now, mate. Thanks for the support."
Indeed patience is a virtue, but it would be stupid to think it applies to all situations.
1 Like
This is true when it comes to Win and Mac. On Linux, Firefox is still probably the most used browser.[/quote]Given the incredibly low market share globally, Iâd say â Probably not.
See: https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#Summary_tables[quote=âxandor, post:29, topic:12630â]
Yeah, WannaCrypt was more dangerous, but it was fixed asap once a solution was found. In the firefox case, the bug has been fixed 21 days ago, but still hasnât been delivered through the update system.[/quote]Unlike the team behind the MATE desktop, behind Ubuntu, Microsoft actually has far more money and far, far more influence. And, far more responsibility. For Microsoft it was incredibly important that a fix be implemented and released as soon as possible. For Ubuntu (MATE or otherwise), fixing and releasing this bug isnât on the highest tier of importance. Nor should it be. There literally are more important matters that might take precedence. Do not ask for examples, please. Youâre still exaggerating the severity of this situation. Greatly exaggerating it.[quote=âxandor, post:29, topic:12630â]
Indeed patience is a virtue, but it would be stupid to think it applies to all situations.[/quote]I donât even know how to respond to this without sounding like a total jerk. But Iâll try â In ANY situation patience is a virtue. Both in real life as well as online and even in software. Why in software? We create the software, we humans that is. As such, we create the bugs. Want to know a common cause for bugs? Haste. Being a gamer I can guarantee you this much. Assassinâs Creed: Unity, anyone? That one was released well before it actually had seen rigorous Q&A. Because the shareholders were impatient. And the consequence? A product that single handedly killed the franchise.
And being a married man, I can assure you that even in real life and in a relationship, patience is a virtue. And having been the victim of nasty, possibly life threatening incidents and complications I can tell you â even THEN patience is a virtue. This one time I literally had to crawl for 8 hours to reach a phone to save my own life. Impatience mightâve made me give up.
Patience is ALWAYS a virtue.
Yeah, Ubuntu Mate has limited resources, and therefore, they can fix fast only important bugs. Iâm glad that they are not wasting their time for fixing a bug that only crashes the system. I mean, people should just continue to use their OS even when it isnât responding anymore. No big deal. I applaud Ubuntu Mateâs determination to provide excellent support.
I started using Ubuntu Mate after it became an official Ubuntu flavor. I considered that they would have access to more resources and they would be able to offer better support and I was happy with the OS until now. For me, this is clearly a bug that should be fixed fast once there is a solution. I guess I had the wrong expectations about this distribution.
But it took action to crawl to reach a phone. It would of been much easier to wait, to be patient hoping for the best. Iâm glad that you choose to do something instead of be patient.
In the end, I will fix this bug by changing the distribution. Itâs not just about this bug, but the attitude: âJust donât click on that button and open the folder manuallyâ. It seems that Ubuntu Mate is focused more on good workarounds instead of providing a stable system.
Itâs also a question of responsibility. Mistakes can happen, we are all humans, but once we commit errors, the proper response shouldnât be to correct them?
1 Like
Hi All,
Just thought Iâd my 2 cents as this bug has been affecting me quite a bit. I canât count the number of times Iâve accidentally frozen my system now. My usual way of working is to click show in folder in Firefox after a download. It takes a fair bit of re-training to change a habit of many years, so I donât think the workaround is really all that fantastic. If it was something as simple as a Firefox crash, leaving the system responsive then it wouldnât be much of a deal. But here we a have a complete desktop freeze, with the only remedy to either go to a different tty and kill the process or step away and put the kettle on while it sorts itself out.
Given that Firefox is the default browser in Ubuntu Mate, and itâs such a commonly used function, I canât understand why it was not noticed in pre-release testing. Itâs a severe bug, and a fix should have really worked its way into the repos by now. Itâs not a show stopper, but its close enough in my opinion.
On the other side of the coin I can understand this is not a big commercial project like Windows. It has limited resources, and this is also not an LTS release. 17.10 is not that far away and I assume the fix will have trickled down to that release by then. So we can all upgrade then and put this one to bed.
Iâm new to Mate, having been previously a long time Xubuntu user, which I only left due to the bluebird theme never being updated for GTK3. Mate is perfect, the themes are great and once youâve got it configured, feels just like XFCE except much more modern. Itâs a great desktop, long may it continue. And this bug, while really annoying is not the end of the world 
1 Like
If you really canât wait for the update to trickle downstream, I have just tested a procedure to deploy the caja update on my system.
Note: I donât recommend doing the same thing if youâre worried about the purity of your system, or potential instability. It is very possible doing this is gonna break something somewhere. I have not noticed any breakage yet but that doesnât mean there arenât any.
Note: Tested only for amd64 and Ubuntu MATE 17.04. If youâre using a 32-bit install you need to adapt the procedure.
- Download the binary package versions for caja 1.18.3 and dependencies:
wget https://launchpad.net/ubuntu/+source/caja/1.18.3-0ubuntu1/+build/12567337/+files/caja-common_1.18.3-0ubuntu1_all.deb
wget https://launchpad.net/ubuntu/+source/caja/1.18.3-0ubuntu1/+build/12567337/+files/libcaja-extension1_1.18.3-0ubuntu1_amd64.deb
wget https://launchpad.net/ubuntu/+source/caja/1.18.3-0ubuntu1/+build/12567337/+files/caja_1.18.3-0ubuntu1_amd64.deb
- Then install the dependencies and caja:
sudo dpkg -i caja-common_1.18.3-0ubuntu1_all.deb
sudo dpkg -i libcaja-extension1_1.18.3-0ubuntu1_amd64.deb
sudo dpkg -i caja_1.18.3-0ubuntu1_amd64.deb
- Finally, reboot
3 Likes
The reason for that is that we donât really have enough testers.
Weâve been discussing how to grow our testing base and test coverage but itâs not trivial.
Also, Ubuntu has a fixed release cycle so even if the bug had been spotted, it doesnât mean the release would have been held until the bug was fixed.
Thereâs a very limited number of official tests done on the Ubuntu releases, and most of them concern the install process, not desktop usage.
http://iso.qa.ubuntu.com/qatracker/milestones/375/builds/145756/testcases
1 Like
Hello everyone! A âsimpleâ Workaround with a firefox extension
https://youtu.be/sDqWJ1_Ita8
Firefox extension
https://addons.mozilla.org/en-US/firefox/addon/local-filesystem-links/?src=userprofile
or
https://addons.mozilla.org/en-US/firefox/addon/magic-open-download-folder-but/?src=userprofile
1 Like
Very nice! Thank you for share it.
Iâm running Fridayâs daily of 17.10 on bare metal and it does seem to have been fixed --so far.
Interesting information on how the release testing works. Good to understand how it works behind the scenes a little better.
Iâve installed the updated packages you posted. Fixes the bug and no regressions found so far. Thanks so much for this!
I thought that you guys had the control of updating Caja anytime because it is the default file manager in Mate. And given the fact that some apps(Firefox, Chromium, etc) receive multiple updates through the official updating process, I wrongly assumed that it was the same with Caja. Iâm sorry about what I said before.
1 Like
I just wanted confirm for others that after following @ouroumovâs instructions laid out here I have had zero issues with Caja and agree this 100% solves the problem. Put simply, if you must have this now run the six commands and reboot and your day will improve. Many thanks to @ouroumov for taking the time to suss that out for the rest of us.
Ouroumov,
Thank you very much for providing these steps and thanks to @monsta for providing the fix itself. I had to use 17.04 for Ryzen support and was hitting this issue a bit too often.
Your efforts are greatly appreciated.
1 Like