GNOME Bugzilla – Bug 771847
program hangs when trying to add axis label to surface plot
Last modified: 2016-09-26 04:43:26 UTC
Ubuntu 16.04, gnumeric version 1.12.28 Insert graph. Select surface. Press forward. Highlight any of the axis (X, Y or Z), press ADD, select "Label to X-Axis1" and program stops responding.
I'm unable to reproduce with current trunk, and I don't remember any other similar report. Would it be possible to get a meaningful stack trace?
(In reply to Jean Bréfort from comment #1) > I'm unable to reproduce with current trunk, and I don't remember any other > similar report. Would it be possible to get a meaningful stack trace? I've tried entering "sudo strace -ffp 4509" in Ubuntu terminal (4509 was PID of gnumeric app), the result was this: [pid 4514] restart_syscall(<... resuming interrupted restart_syscall ...> <unfinished ...> [pid 4513] restart_syscall(<... resuming interrupted restart_syscall ...>strace: [ Process PID=4509 runs in x32 mode. ] <unfinished ...> [pid 4512] restart_syscall(<... resuming interrupted restart_syscall ...> And the cursor just blinks at the end of the last line.
You should run gnumeric from gdb and Ctrl+C when it hangs. Does this happen if you add an axis label to another plot type?
Specifically, ... gnumeric `which gnumeric` run # make it hang, then press Ctrl-C where This will work better if the relevant debug information is installed, but it is a bit difficult to predict what is relevant at this point.
This happens only with surface plot. Also when the program hangs, System Monitor shows that gnumeric CPU usage is 100%. What I did was: open terminal entered "gdb gnumeric" entered "run" made all steps described in the first message pressed Ctrl+C in terminal entered "where" The result was this: (gdb) run Starting program: /usr/bin/gnumeric [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe9905700 (LWP 4591)] [New Thread 0x7fffe9104700 (LWP 4592)] [New Thread 0x7fffe8903700 (LWP 4593)] ^C Thread 1 "gnumeric" received signal SIGINT, Interrupt. __GI___pthread_mutex_lock (mutex=0x5555559495b0) at ../nptl/pthread_mutex_lock.c:64 64 ../nptl/pthread_mutex_lock.c: No such file or directory. (gdb) where
+ Trace 236695
I have two computers, both with Ubuntu 16.04 and Gnumeric 1.12.28. Both had the same surface plot problem. In one machine I've updated Ubuntu to 16.10 and installed Gnumeric 1.12.32. Adding axis labels to surface plot now works on this computer. I've created gnumeric file with surface plot having axis label and tried to open it from gnumeric 1.12.28. If plot is in the first sheet - program hangs. If file is not in the first sheet then file can be opened. But if I try to select the sheet with surface plot in it - Gnumeric stops responding. The result from gdb gnumeric, when opening file with plot in second sheet and then selecting that sheet: (gdb) run Starting program: /usr/bin/gnumeric [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe9905700 (LWP 8353)] [New Thread 0x7fffe9104700 (LWP 8354)] [New Thread 0x7fffe8903700 (LWP 8355)] [New Thread 0x7fffd965a700 (LWP 8357)] [New Thread 0x7fffd8a59700 (LWP 8358)] [Thread 0x7fffd965a700 (LWP 8357) exited] ^C Thread 1 "gnumeric" received signal SIGINT, Interrupt. __ieee754_hypot (x=x@entry=10, y=y@entry=0) at ../sysdeps/ieee754/dbl-64/e_hypot.c:54 54 ../sysdeps/ieee754/dbl-64/e_hypot.c: No such file or directory. (gdb) where
+ Trace 236696
Oops, I did not remember that one. *** This bug has been marked as a duplicate of bug 765480 ***