Bugzilla – Bug 105806
bug buddy locking up ...
Last modified: 2008-08-14 20:43:36 UTC
So - this may be related to the www.gnome.org downage currently - perhaps it's accepting a connection but then not being helpful or somethign - either way - when something crashes I hit 'Inform developers' and it then (apparently) hangs -doing some network thing: stack trace: (gdb) bt #0 0xffffe410 in ?? () #1 0xbfcf3188 in ?? () #2 0x4021c964 in ?? () from /opt/gnome/lib/libgnomevfs-2.so.0 #3 0xbfcf3150 in ?? () #4 0x40bf9681 in connect () from /lib/tls/libpthread.so.0 #5 0x401eb3a9 in gnome_vfs_inet_connection_create_from_address () from /opt/gnome/lib/libgnomevfs-2.so.0 #6 0x4385573d in ne_sock_connect () from /opt/gnome/lib/gnome-vfs-2.0/modules/libhttp.so #7 0x43849517 in ne_get_session () from /opt/gnome/lib/gnome-vfs-2.0/modules/libhttp.so #8 0x4384a4ba in ne_request_dispatch () from /opt/gnome/lib/gnome-vfs-2.0/modules/libhttp.so #9 0x4384a08f in ne_begin_request () from /opt/gnome/lib/gnome-vfs-2.0/modules/libhttp.so #10 0x43847198 in vfs_module_shutdown () from /opt/gnome/lib/gnome-vfs-2.0/modules/libhttp.so #11 0x43847793 in vfs_module_shutdown () from /opt/gnome/lib/gnome-vfs-2.0/modules/libhttp.so #12 0x401e273f in gnome_vfs_open_uri_cancellable () from /opt/gnome/lib/libgnomevfs-2.so.0 #13 0x401fa4a1 in gnome_vfs_open_uri () from /opt/gnome/lib/libgnomevfs-2.so.0 #14 0x401fa501 in gnome_vfs_open () from /opt/gnome/lib/libgnomevfs-2.so.0 #15 0x080552e2 in load_bugzillas () #16 0x08051427 in main () I guess that should be asynchronous or somesuch (prolly best to punt to gnome bugzilla as/when it's back I guess ;-)
ne_* is likely "neon" so yes, network op. Its likely trying to update the database of product information.
http://bugzilla.gnome.org/show_bug.cgi?id=340453 Resolved LATER.
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(
Update resolution to UPSTREAM.