The origin of the timeout messages must have been other processes. Today there are none.
[QUOTE=mikewillis;27805]I’ve never heard of or encountered such a limit.
I just created 3000 files and put them in to Trash and I can open Trash fine.
You could try running
$ gnome-open trash:///
The response to the command was analogous to that using nautilus. After quite a long time waiting in the end no content was shown.
That’s a step towards of a solution. I had a look in Trash/files. Nothing seemed extraordinary except two red-coloured links. Using nautilus I successfully emptied Trash. Its subdirectories files, info, and expunged contained no more items. Then I started testing. With exactly one test file everything worked fine, Trash content looked as expected and I could restore the file. But Trash failed working with more than one file or with directories: I could not open Trash any more! No matter even if the directory I moved to Trash was empty or not.
Strange. No actual error messages in /var/log/warn. I had a closer look at earlier error messages today and discovered, that, every time a gnome login session starts, there are error messages
May 10 16:48:02 letta gdm-session-worker: WARNING: gdm_session_settings_load: lang = (null)
May 10 16:48:08 letta checkproc: checkproc: can not get session id for process 6735!
May 10 16:48:13 letta gnome-session: WARNING: Could not launch application '10d87900a2513cbbf9143126644483272600000065770025.desktop': Unable to start application: Kindprozess Â»slabÂ« konnte nicht ausgefÃ¼hrt werden (Datei oder Verzeichnis nicht gefunden)
Translation of the last words: “child process Â»slabÂ« could not be executed (file or directory not found)”.
Similar messages are logged independent of the user who opens a gnome session. Locale for some user is set to LANG=de_DE for example.
There are other peculiarities concerning gnome sessions which might help finding a solution for Trash too. For example after I switched to text mode (strg-alt-f1) sometimes alt-f7 offered a black screen instead of switching back. I had to invoke alt-f8 to switch back to graphical display. Another example for malfunctioning is the gnome screen saver. Long time ago I disabled it because instead of screen saving a bug buddy report concerning gnome-screensaver-helper locked the session and I had to switch to text mode and manually kill the session before I could go on. I forwarded the report to the respective developer group.
May be there is a general gnome installation or configuration problem?
Thank you for help and hint.