[Bug 411941] Re: f-spot.exe crashed with signal 5 in _XError()

2009-10-29 Thread Sebastien Bacher
** Package changed: f-spot (Ubuntu) => gnome-themes-ubuntu (Ubuntu) ** Package changed: gnome-themes-ubuntu (Ubuntu) => f-spot (Ubuntu) ** Package changed: f-spot (Ubuntu) => gnome-themes-ubuntu (Ubuntu) ** Summary changed: - f-spot.exe crashed with signal 5 in _XError() + f-spot.exe crashes wh

[Bug 411941] Re: f-spot.exe crashed with signal 5 in _XError()

2009-08-25 Thread Tristan Tarrant
It is a problem with the gtk theme. With New Wave it crashes, but with other themes such as Dust, Human it works. -- f-spot.exe crashed with signal 5 in _XError() https://bugs.launchpad.net/bugs/411941 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is su

[Bug 411941] Re: f-spot.exe crashed with signal 5 in _XError()

2009-08-24 Thread Pako
same happens here : $ f-spot --debug ** Running f-spot in Debug Mode ** ** Running Mono with --debug ** [Info 02:11:34.198] Initializing DBus [Debug 02:11:34.549] DBusInitialization took 0.318159s [Info 02:11:34.549] Initializing Mono.Addins [Debug 02:11:34.975] Mono.Addins Initialization took

[Bug 411941] Re: f-spot.exe crashed with signal 5 in _XError()

2009-08-12 Thread Andrei Zhekov
It happens every time I start f-spot -- f-spot.exe crashed with signal 5 in _XError() https://bugs.launchpad.net/bugs/411941 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lis

[Bug 411941] Re: f-spot.exe crashed with signal 5 in _XError()

2009-08-12 Thread Andrei Zhekov
and...@om:~$ f-spot --debug ** Running f-spot in Debug Mode ** ** Running Mono with --debug ** [Info 17:25:35.501] Initializing DBus [Debug 17:25:35.732] DBusInitialization took 0,211451s [Info 17:25:35.732] Initializing Mono.Addins [Debug 17:25:36.038] Mono.Addins Initialization took 0,305726s

[Bug 411941] Re: f-spot.exe crashed with signal 5 in _XError()

2009-08-11 Thread Iain Lane
Hi, I'm afraid your bug does not have the information we need to try to fix it. Does the crash happen every time? Can you try running from a terminal with "f-spot --debug" and pasting/attaching the entire output to the bug if it crashes. Thanks in advance. Iain ** Visibility changed to: Public