This is the old ROX web-site. Please use the new website instead.
Please read the Report Bug instructions.
For some unknown reason, KDE defaults to debug-level logging. To stop it printing all that stuff, run kdebugdialog and turn all the options off.
The messages are actually displayed by ROX-Session, but are sent by other applications. Since error messages mean that something has gone wrong, you should report a bug against the program producing them (NOT against ROX-Session!).
You can set how long the messages are displayed for from ROX-Session's Options box, and you can see a log of old messages there too. You can also see the log by right-clicking on the messages as they're shown, which is useful if you need more time to read them, or if you want to copy-and-paste into a bug report.
If you really need to disable messages (because some application is just too noisy), you can do this in its AppRun file:
exec some_app "$@" 2>&1
The extra 2>&1 at the end of the exec line causes errors to be treated as normal (non-error) output, so ROX-Session won't display them.
To hide messages from your window manager, create a script containing:
#!/bin/sh exec window_manager "$@" 2>&1
Then use the name of that script in the ROX-Session Session Settings box.
Note that we do not provide any way to supress all error messages from all applications (despite frequent requests). Ignoring errors is never the right thing to do, and providing this option to users would be irresponsible. Although you may think that the warnings you see are harmless, the same bug could be causing serious trouble to other users. The developers may spend weeks trying to track down the problem, when the message you saw would have located the problem instantly.
The filer tries to preserve file permissions when copying files, but some filesystems don't support them and you may get an error from the 'cp' command (although not all systems are affected). The 'quiet' mount option can be used in /etc/fstab to stop the message being displayed.
Some older window managers don't support features needed by the panel. However, you can turn on the 'Override window manager' option in the Compatibility section of the Options box.
The filer needs to be run using the 'rox' shell script, not by running the ROX-Filer binary directly. Some systems try to implement a primitive form of session management (without using XSMP, which the filer supports) and fail to restart it correctly.
This is a gnome-terminal bug. You need to run gnome-terminal with the --disable-factory option, otherwise it starts in the same directory which the existing gnome-terminal process started in.
Probably not. We use gdk-pixbuf to load images, so you should first
report the bug there.
If you have used Show Thumbnails, and the window has (Thumb) in the title bar, but some image files do not show thumbnails then
it could be that ROX-Filer doesn't think that the files are images. This is common when using DOS or Windows filesystems, where most
files show as executable files, using an icon such as 
.
Try using the option Types=>Ignore eXecutable bit for known extensions (removed in ROX-Filer 2.3, which should be better at
guessing the type correctly).
See also File Types.
Kristian Rink suggests
"Playing around while trying to get rox to work with avfs for quite some time, I never had success while running my machines on reiserfs, but now that I switched to ext3 it suddenly works perfect. Just to let you know. :)
This message is usually from sawfish, and is harmless. XINERAMA support allows you to spread your desktop over several monitors.
Failed to create symlink and my file icons are all question marksROX-Filer is having trouble with the icon theme. Try choosing another one.
If you have not set a theme then it cannot locate the default theme. Try removing the link ~/.icons/ROX, e.g.
mv ~/.icons/ROX ~/.icons/ROX.broken rox -n