** Changed in: f-spot
Status: Invalid = Unknown
** Changed in: f-spot
Importance: Unknown = Critical
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Jerzyo which video driver are you using there?
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
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
I have a problem in lucid
After clicking on Import:
f-spot
[Info 23:11:18.434] Initializing DBus
[Info 23:11:18.553] Initializing Mono.Addins
[Info 23:11:18.724] Starting new FSpot server (f-spot 0.6.1.5)
[Info 23:11:20.198] Starting BeagleService
[Info 23:11:20.220] Hack for
upstream says the issue is a video driver one, is somebody still having
the bug on lucid and using what driver?
** Changed in: f-spot (Ubuntu)
Status: Triaged = Incomplete
** Changed in: f-spot (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
--
f-spot crash at
** Changed in: f-spot
Status: New = Invalid
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 17:59:40.115] Initializing DBus
[Debug 17:59:41.286] DBusInitialization took 1,085223s
[Info 17:59:41.286] Initializing Mono.Addins
[Debug 17:59:43.524] Mono.Addins Initialization took 2,236911s
[Info
** Changed in: f-spot
Status: Unknown = New
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Indeed - I changed to fglrx and f-spot is running fine!
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Confirming the idea that it is linked to the driver one is using:
Crash happens only if I use radeon or radeonhd drivers.
Using fglrx driver, f-spot works perfectly.
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because
If i connect via ssh -X and start f-spot remotely, making it draw its screen on
the laptop i'm connecting from, it does not crash.
(Hoping this is helpful, sorry if it's is a redundant remark.)
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this
This is slightly embarrassing... :-} but after some rather tortuous
struggles with an entirely different problem (trying the fglrx driver
and reverting to the open source radeon one after finding the former
couldn't handle my 2 monitor setup), f-spot once more works for me.
Another app that was
I won't also confirm it, then. Let me know if you want more info or have
a patch that needs testing.
When i set the values in gconf-editor (as suggested by Shanta Schelfhout
on 2008-11-24), f-spot still fails to start but the line Message:
gtk_window_resize: assertion `width 0' failed does not
** Attachment added: backtrace.log
http://launchpadlibrarian.net/20137878/backtrace.log
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
There's no need to reconfirm bugs if the state is Triaged and they have
an upstream task, thanks.
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm this bug!
System: Linux lokarabia 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC
2008 i686 GNU/Linux (Ubuntu Intrepid 8.10)
** Attachment added: debug_output.log
http://launchpadlibrarian.net/20137547/debug_output.log
--
f-spot crash at startup AMD64 Ubuntu 8.10
** Attachment added: strace.log
http://launchpadlibrarian.net/20137568/strace.log
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: f-spot (Ubuntu)
Status: Confirmed = Triaged
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I don't think this is a 64-bit or AMD issue. Running 32-bit:
: samhain_pmurphy; uname -a
Linux samhain 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux
: samhain_pmurphy; cat /proc/cpuinfo | grep ^model\ name
model name : Intel(R) Pentium(R) M processor 1.86GHz
:
I have added the above mentioned main_window* entries via gconf-editor,
error is still the same
$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 20:08:11.267] Initializing DBus
[Debug 20:08:11.570] DBusInitialization took 0,262519s
[Info 20:08:11.570]
Set to confirmed as 2 people reported to still have the problem and
debug information is provided.
** Changed in: f-spot (Ubuntu)
Status: Incomplete = Confirmed
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because
I have the same error (Ubuntu 8.10, 32bit on AMD Athlon), but at least
for me the f-spot window opens for a split of a second after the
'Starting new FSport server' line, then closes and the error message is
displayed.
I added keys main_window_width and main_window_height with gconf-editor.
Error
[EMAIL PROTECTED]:~$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 11:02:40.741] Initializing DBus
[Debug 11:02:40.878] DBusInitialization took 0.122129s
[Info 11:02:40.879] Initializing Mono.Addins
[Debug 11:02:41.097] Mono.Addins Initialization took
From the upstream bugreport:
launch gconf-editor
navigate on the left to apps/f-spot/ui
on the right you should find
main_window_width
main_window_height
set them to something, like 100. if they don't exist create them, as integer.
What output do you get after changing these?
**
my comment from the duplicate bug:
Could not reproduce on a 32-bit system using the same Ubuntu and f-spot
version.
This appears in my terminal:
(f-spot:7157): Gtk-CRITICAL **: gtk_window_resize: assertion `width 0' failed
item ImportCommand+SourceItem
cleanup context
--
The error was
Hi,
got the same after upgrade 8.4 to 8.10 on Intel.
$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 21:13:54.326] Initializing DBus
[Debug 21:13:54.595] DBusInitialization took 0,244245s
[Info 21:13:54.595] Initializing Mono.Addins
[Debug
I have the same bug in Ubuntu 8.10 on Intel.
GNOME f-spot 0.5.0.3
This is new since I upgraded from 8.4 to 8.10
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have no idea!
** Attachment added: buglog
http://launchpadlibrarian.net/19622978/gdb-f-spot.txt
--
f-spot crash at startup AMD64 Ubuntu 8.10
https://bugs.launchpad.net/bugs/297406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: f-spot (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) =
28 matches
Mail list logo
