[Expired for f-spot (Ubuntu) because there has been no activity for 60
days.]
** Changed in: f-spot (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/601807
si...@ltsp:~$ f-spot --sync
[Info 09:43:07.193] Initializing DBus
[Info 09:43:07.337] Initializing Mono.Addins
[Info 09:43:07.530] Starting new FSpot server (f-spot 0.6.1.5)
[Info 09:43:09.135] Starting BeagleService
[Info 09:43:09.154] Hack for gnome-settings-daemon engaged
(f-spot:18567):
** Attachment added: f-spot --debug f-spot-debug.txt
http://launchpadlibrarian.net/51449507/f-spot-debug.txt
--
f-spot crashes on LTSP-client
https://bugs.launchpad.net/bugs/601807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
any chance to run f-spot with gdb as:
gdb f-spot
(gdb) break gdk_x_error
(gdb) run --sync
reproduce the crash and
(gdb) thread apply all bt
then attach that resulting log file to the report? thanks in advance.
--
f-spot crashes on LTSP-client
https://bugs.launchpad.net/bugs/601807
You
si...@ltsp:~$ gdb /usr/bin/f-spot
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51402014/Dependencies.txt
--
f-spot crashes on LTSP-client
https://bugs.launchpad.net/bugs/601807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same problem with full-screen and dia-show.
--
f-spot crashes on LTSP-client
https://bugs.launchpad.net/bugs/601807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks for the report Simon, could you run f-spot as : f-spot --debug
f-spot-debug.txt ; reproduce the bug and attach that resulting log file
to the report? Thanks in advance.
** Changed in: f-spot (Ubuntu)
Importance: Undecided = Medium
** Changed in: f-spot (Ubuntu)
Status: New =
