After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 531442 - NULL string comparison under http_follow_redirect
NULL string comparison under http_follow_redirect
Status: RESOLVED NOTGNOME
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-04 21:21 UTC by Gilles Dartiguelongue
Modified: 2008-12-21 19:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Gilles Dartiguelongue 2008-05-04 21:21:01 UTC 
Version: 2.22.1.3

What were you doing when the application crashed?
Tried to access a webdav share from the Places menu.


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.22.1 2008-04-12 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-gentoo-r1 #2 SMP Mon Apr 28 22:22:25 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Unity
Icon Theme: gnome-alternative

Memory status: size: 100425728 vsize: 100425728 resident: 26578944 share: 16191488 rss: 26578944 rss_rlim: 4294967295
CPU usage: start_time: 1209926098 rtime: 10077 utime: 9504 stime: 573 cutime:250 cstime: 23 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal]
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e896c0 (LWP 6557)]
[New Thread 0xb4ca3b90 (LWP 9180)]
0xb80c2424 in __kernel_vsyscall ()

+ Trace 196867

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
  • #8 <signal handler called>
  • #9 *__GI___strcasecmp
    at strcasecmp.c line 65
  • #10 ne_uri_defaultport
    at ne_uri.c line 70
  • #11 ne_uri_unparse
    at ne_uri.c line 310
  • #12 http_follow_redirect
    at http-neon-method.c line 1792
  • #13 http_get_file_info
    at http-neon-method.c line 1853
  • #14 do_get_file_info
    at http-neon-method.c line 2921
  • #15 gnome_vfs_get_file_info_uri_cancellable
    at gnome-vfs-cancellable-ops.c line 202
  • #16 gnome_vfs_get_file_info_uri
    at gnome-vfs-ops.c line 332
  • #17 gnome_vfs_get_file_info
    at gnome-vfs-ops.c line 309
  • #18 _gnome_vfs_get_slow_mime_type_internal
    at gnome-vfs-mime.c line 960
  • #19 gnome_vfs_url_show_with_env
    at gnome-vfs-utils.c line 2166
  • #20 gnome_url_show_with_env
    at gnome-url.c line 75
  • #21 gnome_url_show_on_screen
    at gnome-multiscreen.c line 112
  • #22 activate_uri
    at panel-menu-items.c line 129
  • #23 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #27 IA__g_signal_emit
    at gsignal.c line 2243
  • #28 IA__gtk_widget_activate
    at gtkwidget.c line 4709
  • #29 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 1150
  • #30 gtk_menu_shell_button_release
    at gtkmenushell.c line 674
  • #31 gtk_menu_button_release
    at gtkmenu.c line 2725
  • #32 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #33 g_type_class_meta_marshal
    at gclosure.c line 567
  • #34 IA__g_closure_invoke
    at gclosure.c line 490
  • #35 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #36 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #37 IA__g_signal_emit
    at gsignal.c line 2243
  • #38 gtk_widget_event_internal
    at gtkwidget.c line 4678
  • #39 IA__gtk_propagate_event
    at gtkmain.c line 2336
  • #40 IA__gtk_main_do_event
    at gtkmain.c line 1556
  • #41 gdk_event_dispatch
    at gdkevents-x11.c line 2351
  • #42 IA__g_main_context_dispatch
    at gmain.c line 2009
  • #43 g_main_context_iterate
    at gmain.c line 2642
  • #44 IA__g_main_loop_run
    at gmain.c line 2850
  • #45 IA__gtk_main
    at gtkmain.c line 1163
  • #46 main
    at main.c line 95 


----------- .xsession-errors (3061 sec old) ---------------------
gnome-mount 0.6
/dev/sde2 monté sur « /media/ClearStore »
** (gnome-mount:9274): WARNING **: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_91a873fa_df91_4260_9be9_8ddbc75e8261
org.freedesktop.Hal.Device.Volume.AlreadyMounted : Device /dev/sde4 is already mounted.
(gnome-mount:9274): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(gnome-mount:9274): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gnome-mount:9274): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(gnome-mount:9274): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
/dev/sde3 monté sur « /media/Musique »
--------------------------------------------------
Comment 1 Philip Withnall 2008-05-04 23:30:00 UTC 
Looks like a GnomeVFS bug.
Comment 2 palfrey 2008-12-16 16:49:04 UTC 
It's a bug in libneon (used by gnome-vfs for http parsing) which according to their subversion repository (http://svn.webdav.org/repos/projects/neon/trunk/src/ne_uri.c) looks like to have now been fixed.
Comment 3 Gilles Dartiguelongue 2008-12-21 14:27:26 UTC 
actually the problem is that gnome-vfs includes a snapshot of neon and doesn't allow building against system's neon. It's not a recent snapshot as well. It'd be nice to have this snapshot updated or something to fix it because gnomevfs is still used by lots of apps that didn't migrated to gio yet.
Comment 4 palfrey 2008-12-21 19:48:58 UTC 
(In reply to comment #3)
> actually the problem is that gnome-vfs includes a snapshot of neon and doesn't
> allow building against system's neon. It's not a recent snapshot as well. It'd
> be nice to have this snapshot updated or something to fix it because gnomevfs
> is still used by lots of apps that didn't migrated to gio yet.

Bug 332290 is a wishlist item for using the system libneon, which was marked as WONTFIX a few years ago, but given the rise of gvfs and that I've just dumped a patch there to implement it, maybe we can get this sorted out...