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 151070 - Crash exiting from "text to columns" dialog
Crash exiting from "text to columns" dialog
Status: RESOLVED DUPLICATE of bug 132450
Product: atk
Classification: Platform
Component: gail
1.4.x
Other other
: Normal normal
: ---
Assigned To: padraig.obriain
padraig.obriain
Depends on:
Blocks:
 
 
Reported: 2004-08-25 22:10 UTC by ppujal
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
valgrind trace - from after startup until the segfault dialog appears (5.11 KB, text/plain)
2004-08-26 14:03 UTC, Jon Kåre Hellan
Details
valgrind trace with deeper stack (9.22 KB, text/plain)
2004-08-26 14:14 UTC, Jon Kåre Hellan
Details

Description ppujal 2004-08-25 22:11:06 UTC
Distribution: Debian testing/unstable
Package: Gnumeric
Severity: normal
Version: GNOME2.6.1 unspecified
Gnome-Distributor: Debian
Synopsis: Crash exiting from "text to columns" dialog
Bugzilla-Product: Gnumeric
Bugzilla-Component: General
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Steps to reproduce the crash:
1. Open a new file, select nothing but the A1 cell
2. Click on Data --> Text to Columns
3. On the dialog window Click on Cancel
4. Click on yes on confirmation window

That's all. I get a crash on gnumeric 1.2.13 


Additional Information:

Kernel 2.6.7
Debian sid


Debugging Information:

Backtrace was generated from '/usr/bin/gnumeric'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1091581152 (LWP 11606)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x408a340e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread 1091581152 (LWP 11606))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gail_tree_view_ref_focus_cell
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #4 gail_tree_view_ref_focus_cell
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #5 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-25 18:11 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "Gnumeric".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Morten Welinder 2004-08-26 01:15:15 UTC
Interesting, although the crash appears to be in gail code, not gnumeric.
Comment 2 J.H.M. Dassen (Ray) 2004-08-26 13:52:40 UTC
Please supply the output of "reportbug --template gnumeric".
Comment 3 Jon Kåre Hellan 2004-08-26 13:59:54 UTC
Crash confirmed when accessibility is enabled
Comment 4 Jon Kåre Hellan 2004-08-26 14:03:30 UTC
Created attachment 30969 [details]
valgrind trace - from after startup until the segfault dialog appears
Comment 5 Jon Kåre Hellan 2004-08-26 14:14:23 UTC
Created attachment 30970 [details]
valgrind trace with deeper stack

This trace actually reaches gnumeric code.
Haven't looked into things, but would expect this to be a bug in a11y.
Comment 6 Jon Kåre Hellan 2004-08-27 16:58:32 UTC
Trace shows that gtk_tree_model_row_deleted sends a signal which ends up
somewhere which no longer exists.

gnumeric does not listen for row-deleted, so this seems to be a bug in gail.
Comment 7 J.H.M. Dassen (Ray) 2004-09-03 19:30:57 UTC
Both sarge and sid still have gail 1.4.1(-1). Looking at current gail's NEWS,
the problem here may well be one that was fixed in gail 1.5.4:
"* Fix crasher bug in gnumeric when treeview is destroyed. (bug #132450)".
Comment 8 J.H.M. Dassen (Ray) 2004-09-03 20:07:32 UTC
Unfortunately I can't seem to reproduce the problem, so can someone please test
if the problem is still repeatable after upgrading the gail packages to the ones at
http://www.xinara.org/~ray/tmp/gail/ ?
Comment 9 Jon Kåre Hellan 2004-09-04 13:37:25 UTC
I can repeat the problem with gail packages from sid. There is no crash with the
gail 1.6.6 packages at http://www.xinara.org/~ray/tmp/gail/.
Comment 10 padraig.obriain 2004-09-06 16:06:55 UTC

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