As this happened to me on both my systems (which have quite a different configuration) and I found several people complaining about Nautilus’ low performance, there could be a connection to the problem I experienced, so this is why I am posting it here.
Yesterday I installed Intrepid Ibex amd64 on both of my systems. Later that day I experienced annoying slowdowns when using Nautilus as a file manager (in fact it’s a nice programs, but this really made the fun factor of using it go down to zero :S). Booting the Live Image again i noticed there were absolutely no problems when using Nautilus there, not even when browsing the device where it was so damned slow in the installed version.
So what caused this problem? As you might know, when installing Ubuntu you will get some “nice” standard directories in your home dir. These can be configured in ~/.config/user-dirs.dirs, and this is what I did: I just changed the paths there to the according directories in my file system. In previous versions, this caused absolutely no problems, but now it obviously does. Keeping these paths set to their default the problem is not there. Also, changing them just to $HOME causes no problem (just if you want to get rid of the annoying standard folders you do not want to use ;)). Other settings may or may not cause problems, at least they did for me. So if you experience similar issues, try remembering if you changed those settings (which in fact belong to xdg-user-dirs) and change them back to their default to see if it helps.
Interestingly, the slowdowns remained even when xdg-user-dirs was uninstalled – anybody knows if that file is used by another application?
Wer hat sich’s nicht schonmal gefragt: “Wie groß muss mein Programm eigentlich sein, um eine bestimmte Ausgabe erzeugen zu können?”
Wie…Kolmogorov? Ja? Wer noch? Was? Sonst niemand? Soso…
(Dieser Eintrag wurde Ihnen präsentiert von: morgiger (bzw. mittlerweile heutiger) Vortrag mit Hauptthema “On the Length of Programs for Computing Finite Binary Sequences”)
Yesterday I wanted to check the Netbeans tutorial on “Converting and Validating Data in Visual Web JSF Applications” to gain some basic knowledge on this topic (again – as you might already think to yourself – this is due to an assignment ;)). But just like last time, problems were lying ahead: Testing the most basic application one could think of, Firefox (3, that is) refused to render properly when I first built the project. A quick reload of the page fixed this, so I thought “Well, maybe that will NOT happen again!”. At least i hoped so. Playing around with that application, about ten to twenty percent of the page loads led to a totally fucked up (!) page rendering.
I was really willing to blame Netbeans or Woodstock for that, but then I tried another browser and it worked perfectly. Still, the solution to this problem is not a browser change, but just installing the latest Woodstock components (as described here) fixes the issue, though I don’t know the exact cause of it. Ok, to be honest, it was completely satisfactory to me that I got it to work properly :P
Hope this is helpful to someone :)
Da ich gerade meine ganzen Papers ein wenig organisiere (unter Verwendung von JabRef), gucke ich auch ab und zu auf CiteSeer. Dort habe ich zu “Triangle: Engineering a 2D Quality Mesh Generator and Delaunay Triangulator” von Jonathan R. Shewchuk folgenden BibTeX-Eintrag gefunden:
@MISC{Triangulator_triangle:engineering,
author = {Delaunay Triangulator and Jonathan Richard Shewchuk},
title = {Triangle: Engineering a 2D Quality Mesh Generator},
year = {}
}
Lol? :S
Da dieser Eintrag für lustige Netbeans+Linux-Nutzer von allgemeinem Interesse sein könnte, verfasse ich ihn mal auf Englisch.
Ever wondered why Netbeans is so incredibly slow on your machine with chipset graphics like i945GM?
This afternoon, when I wanted to start working on a tiny web project due to an assignment, I noticed that Netbeans was unusually slow on my laptop after I installed the latest Ubuntu release, “Intrepid Ibex”. Remembering that I had problems like this before, I was willing to find a solution now as it was really bugging me this time. The problem was not only that Netbeans was just “slow”…even the pull down menus took several seconds to show up sometimes. Comparing this behaviour with the one on a fellow student’s machine with an older chipset, it appeared that the problem did not exist there. So it seems like it could be limited to that i945GM.
So what I figured out should probably work for all people using the above configuration or something similar: Here it is reported that the Java Plugin in Firefox is causing massive CPU load when using the default EXA acceleration method in xorg.conf (it doesn’t necessarily show up there, it’s just the default if nothing else is stated). As for this bug, my problems also disappeared when I changed the acceleration method to “XAA” in xorg.conf. This simply means that in Intrepid the default “Device” section, which looks like this:
Section "Device"
Identifier "Configured Video Device"
EndSection
…should be changed to the following:
Section "Device"
Identifier "Configured Video Device"
Driver "intel" # may not be necessary
Option "AccelMethod" "XAA"
Option "XaaNoOffscreenPixmap" "on"
EndSection
This solved all my problems and resulted in a vast performance improvement: Netbeans is usable again! :)
Note: This may concern other Java-based applications as well as I also remember Eclipse having similar problems. Though, I’m not sure about that having the same reason.
Recent Comments