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 118641 - gnumeric crashes trying to start it.
gnumeric crashes trying to start it.
Status: RESOLVED DUPLICATE of bug 113020
Product: linc
Classification: Deprecated
Component: general
CVS HEAD
Other other
: Normal critical
: ---
Assigned To: Michael Meeks
Michael Meeks
Depends on:
Blocks:
 
 
Reported: 2003-07-30 07:23 UTC by Rodd Clarkson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rodd Clarkson 2003-07-30 07:23:39 UTC 
Distribution: Red Hat Linux release 9 (Shrike)
Package: Gnumeric
Severity: normal
Version: GNOME2.3.4 1.1.19
Gnome-Distributor: GARNOME
Synopsis: gnumeric crashes trying to start it.
Bugzilla-Product: Gnumeric
Bugzilla-Component: Analytics
Bugzilla-Version: 1.1.19
BugBuddy-GnomeVersion: 2.0 (2.3.3.1)
Description:
Description of the crash:

Clicking the gnumeric icon or starting it from the terminal results in a
crash.

I have had it running after installing it using garnome, but it no
longer works.  Not sure what changed.


Debugging Information:

Backtrace was generated from '/home/rodd/gnome-2.3.3/bin/gnumeric'

[New Thread 1091392192 (LWP 11861)]
0xffffe002 in ?? ()

+ Trace 39143

Thread 1 (Thread 1091392192 (LWP 11861))

  • #0 ??
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 738
  • #2 <signal handler called>
  • #3 g_logv
    at gmessages.c line 513
  • #4 g_log
    at gmessages.c line 527
  • #5 link_server_handle_io
    at linc-server.c line 199
  • #6 link_source_dispatch
    at linc-source.c line 54
  • #7 g_main_dispatch
    at gmain.c line 1720
  • #8 g_main_context_dispatch
    at gmain.c line 2268
  • #9 g_main_context_iterate
    at gmain.c line 2349
  • #10 g_main_loop_run
    at gmain.c line 2569
  • #11 gtk_main
    at gtkmain.c line 1093
  • #12 main
    at main-application.c line 227
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-30 03:23 -------

Unknown version 1.1.19 in product Gnumeric. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, jody@gnome.org.
Comment 1 Andreas J. Guelzow 2003-07-30 13:46:48 UTC 
Gnome 2.3.4?  Gnumeric 1.1.x is written for Gnome 2.0 or 2.2.
Comment 2 Jody Goldberg 2003-07-30 14:04:02 UTC 
Lets send this over to linc to see if that trace rings any bells.

This is well before gnumeric gets control of things.
Something is pissing linc off.  Are you loading some gtk modules ?
you can try wiping your ~/.gconf/apps/gnumeric dir to see if that
makes gconf happy, or deleteing /tmp/orbit-<username> to see if there
is something dangling in there.


andreas : gnome-2.3.4 is fine, we work againt cvs head too.
Comment 3 Elijah Newren 2003-08-01 16:28:18 UTC 
For what it's worth, this appears to be a unique stack trace.  Setting
severity->critical (crasher), adding bugsquad and STACKTRACE (due to
the debugging symbols) keywords, and selecting "Reassign bug to owner
of selected component" (/me nudges Jody to remind him to do that as
well when reassigning).
Comment 4 Rodd Clarkson 2003-08-04 00:04:27 UTC 
Okay, I tried deleting  ~/.gconf/apps/gnumeric and no change, but when
I deleted /tmp/orbit-<username> this fixed it.  Unfortunately, I
didn't stop and think maybe to move it so that I could supply it to
you to see what was wrong.
Comment 5 Michael Meeks 2003-08-05 11:26:21 UTC 
Very odd; it is _possible_ but unlikely that there was an
insufficiently random number and we got a socket collision in
/tmp/orbit-$USER, but we have code to catch and avoid this.

I've really no idea how a valid, listening socket can get in such a
state; we do our listen before setting O_NONBLOCK;

really no idea.
Comment 6 Michael Meeks 2003-08-05 11:30:36 UTC 
a duplicate it seems:

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