@Tom
I might not be good at making my point sometimes, but you clearly sum
things up very good. Way better than I do.
@Aryeh
In Ext3, too many applications use fsync, I think that was from the ext2
day-and-era, where not syncing could lead to corrupt filesystems, not
just empty files. Same with
@helios
I fail to see the fact that this would ever be a KDE bug. fsync only
*helps*, it will never ever make sure that things will be solved
permanently for good. The reason that a rename() is used with a temp
file that *nothing* can get 100% durability (even using fsync). App
developers want
@Hiten
I agree with your comment, I think. I was about to make that same post.
I would even dare to say that fsync(fd) is an evil call that never
should be used by any application. The reason for this is very simple,
it doesn't make a difference: if fsync(fd) needs to write 100MB to disk
and a
I'm still having this problem with all software based X servers. This is
e.g. Xnewt on SunRay 1g (ubuntu 8.04.1 64-bit up to the latest version
except for the kernel). Also the framebuffer X server on the PS3, this
is ubuntu 8.10 ppc64 latest version.
On my desktop PC, with the nvidia card,
Can someone check
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/242562 ?
The problem is IMHO 'in firefox', probably cairo, as that does the
rendering (?!). On software based X servers the problem doesn't go away.
The beta 180.16 drivers from nvidia make the problem dissapear on a
I have exactly the same problem on a SunRay 1g, where the Xnewt X server
is used. I'm using this on ubuntu 8.04.1 64-bit, desktop install. It's
on a quite fast machine: dual quad core 3.2 GHz. After realizing that I
had seen that problem elsewhere before, I realized that that was on my
home PC:
