cfp
June 30th, 2008, 08:52 PM
A computer I maintain was upgraded to Hardy Heron without my presence, and there are now a number of problems I'm working through. The most concrete one is that F-spot isn't loading and is giving the error:
:~$ f-spot
Starting new FSpot server
Unrecognized deviceID 258a
The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 381 error_code 11 request_code 159 minor_code 3)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Evolution is requiring password entrance on first open to unlock the key-ring, opening Nautilus windows is incredibly slow (even the home folder, though "browsing" using the terminal and ls is fine), and there's bizarre screen corruption across a block of the screen (not a hardware problem as started with the upgrade). The f-spot, key ring and Nautilus problems could perhaps all be explained by messed up file permissions?? though quite what files are missing what permissions I'm not sure.
Any help would be much appreciated,
Thanks in advance,
Tom
:~$ f-spot
Starting new FSpot server
Unrecognized deviceID 258a
The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 381 error_code 11 request_code 159 minor_code 3)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Evolution is requiring password entrance on first open to unlock the key-ring, opening Nautilus windows is incredibly slow (even the home folder, though "browsing" using the terminal and ls is fine), and there's bizarre screen corruption across a block of the screen (not a hardware problem as started with the upgrade). The f-spot, key ring and Nautilus problems could perhaps all be explained by messed up file permissions?? though quite what files are missing what permissions I'm not sure.
Any help would be much appreciated,
Thanks in advance,
Tom