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 660373 - Crash at startup
Crash at startup
Status: RESOLVED DUPLICATE of bug 652531
Product: vinagre
Classification: Applications
Component: general
git master
Other OpenBSD
: Normal critical
: ---
Assigned To: vinagre-maint
vinagre-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-28 15:55 UTC by Jasper Lievisse Adriaanse
Modified: 2011-09-29 07:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jasper Lievisse Adriaanse 2011-09-28 15:55:02 UTC 
Vinagre works ok on my 32-bit i386, but starting vinagre on a 64-bit machine directly results in a crash. Full backtrace follows:

(gdb) run
Starting program: /usr/local/bin/vinagre 

Program received signal SIGSEGV, Segmentation fault.
[Switching to process 3150, thread 0x2071fa800]
0x0000000209f8e9a2 in g_build_path_va (separator=0x20a102aa6 "/", 
    first_element=0x33769c0 <Address 0x33769c0 out of bounds>, args=0x7f7fffff09b0, str_array=0x0)
    at gfileutils.c:1592
1592          if (!*element)
(gdb) bt

+ Trace 228628

  • #0 g_build_path_va
    at gfileutils.c line 1592
  • #1 g_build_filename
    at gfileutils.c line 1907
  • #2 vinagre_cache_prefs_init
    at vinagre/vinagre-cache-prefs.c line 34
  • #3 app_init
    at vinagre/vinagre-main.c line 59
  • #4 app_command_line
    at vinagre/vinagre-main.c line 100
  • #5 ffi_call_unix64
    at src/x86/unix64.S line 75
  • #6 ffi_call
    at src/x86/ffi64.c line 484
  • #7 g_cclosure_marshal_generic
    at gclosure.c line 1147
  • #8 g_closure_invoke
    at gclosure.c line 774
  • #9 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #10 g_signal_emit_valist
    at gsignal.c line 3013
  • #11 g_signal_emit
    at gsignal.c line 3060
  • #12 g_application_run
    at gapplication.c line 1301
  • #13 main
    at vinagre/vinagre-main.c line 162
  • #0 g_build_path_va
    at gfileutils.c line 1592
  • #1 g_build_filename
    at gfileutils.c line 1907
  • #2 vinagre_cache_prefs_init
    at vinagre/vinagre-cache-prefs.c line 34
  • #3 app_init
    at vinagre/vinagre-main.c line 59
  • #4 app_command_line
    at vinagre/vinagre-main.c line 100
  • #5 ffi_call_unix64
    at src/x86/unix64.S line 75
  • #6 ffi_call
    at src/x86/ffi64.c line 484
  • #7 g_cclosure_marshal_generic
    at gclosure.c line 1147
  • #8 g_closure_invoke
    at gclosure.c line 774
  • #9 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #10 g_signal_emit_valist
    at gsignal.c line 3013
  • #11 g_signal_emit
    at gsignal.c line 3060
  • #12 g_application_run
    at gapplication.c line 1301
  • #13 main
    at vinagre/vinagre-main.c line 162 

It seems it's actually due to a glib issue in gfileutils.c? I'm running with
vinagre 3.2.0, glib 2.30.0 and libffi 3.0.9.
Comment 1 David King 2011-09-28 17:32:56 UTC 
I would guess that this is due to bug 652531.
Comment 2 Jasper Lievisse Adriaanse 2011-09-28 18:22:37 UTC 
Perhaps, though this means that vinagre is currently broken on all 64-bit machines?
I'm still trying to backport the fixes though without any success so far.
Comment 3 Jasper Lievisse Adriaanse 2011-09-28 18:40:20 UTC 
Got it working, using the ugly fix from the aforementioned ticket as the other way wouldn't work out for me.
Comment 4 Jasper Lievisse Adriaanse 2011-09-29 07:59:19 UTC 

*** This bug has been marked as a duplicate of bug 652531 ***