Comment 17 for bug 286544

Hey guys.

This did the trick for me:

sudo apt-get remove --purge xorg-driver-fglrx

Don't ask me why

On Sat, Feb 7, 2009 at 9:38 AM, fleiber <email address hidden> wrote:

> Tried with radeon / radeonhd drivers, with an integrated Radeon 1250
> card, and both crash.
>
> I'm just surprised this bug is only rated "medium", since like many
> other people, my parents only use this computer for internet / mails,
> movies and pictures, and loosing one of the three makes them a bit...
> loud ^^
>
> --
> The program 'f-spot' received an X Window System error
> https://bugs.launchpad.net/bugs/286544
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "f-spot" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: f-spot
>
> At the moment I can't open F-Spot at all. Same ultimate error if I move my
> ~/.gnome2/f-spot folder.
>
> Version: 0.5.0.3-0ubuntu1
>
> andrew:~ f-spot --debug -v Desktop/virus.png
> ** Running f-spot in Debug Mode **
> ** Running Mono with --debug **
> [Info 14:05:22.563] Initializing DBus
> [Debug 14:05:22.804] DBusInitialization took 0.195818s
> [Info 14:05:22.805] Initializing Mono.Addins
> [Debug 14:05:23.164] Mono.Addins Initialization took 0.359255s
> [Info 14:05:23.179] Starting new FSpot server
> uri = file:///home/andrew/Desktop/virus.png
> The program 'f-spot' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadRequest (invalid request code or no such operation)'.
> (Details: serial 436 error_code 1 request_code 143 minor_code 19)
> (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.)
>
> andrew:~ f-spot --debug
> ** Running f-spot in Debug Mode **
> ** Running Mono with --debug **
> [Info 14:10:30.604] Initializing DBus
> [Debug 14:10:30.844] DBusInitialization took 0.218779s
> [Info 14:10:30.844] Initializing Mono.Addins
> [Debug 14:10:31.200] Mono.Addins Initialization took 0.3552s
> [Info 14:10:31.214] Starting new FSpot server
> [Debug 14:10:31.745] Db Initialization took 0.418179s
> [Debug 14:10:32.606] QueryToTemp took 0.102026s : SELECT id, time, uri,
> description, roll_id, default_version_id, rating, md5_sum FROM photos ORDER
> BY time DESC
> [Debug 14:10:33.033] PhotosPerMonth took 0.144338s
> [Debug 14:10:33.036] TimeAdaptor REAL Reload took 0.356263s
> [Debug 14:10:33.143] Query took 0.030657s : SELECT * FROM photoquery_temp_0
> LIMIT 100 OFFSET 0
> The program 'f-spot' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadRequest (invalid request code or no such operation)'.
> (Details: serial 332 error_code 1 request_code 143 minor_code 19)
> (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.)
>

--
Regards,
Neville Grech