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 159000 - GIMP 2.2.p2 (FreeBSD) dies instantly when trying to use ink tool with Wacom tablet
GIMP 2.2.p2 (FreeBSD) dies instantly when trying to use ink tool with Wacom t...
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: Tools
2.1.x
Other FreeBSD
: High major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-11-21 23:32 UTC by lauri.jarvenpaa
Modified: 2004-12-20 02:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description lauri.jarvenpaa 2004-11-21 23:32:51 UTC 
Start GIMP
Create new image
Select ink tool
Try to draw
result: Segmentation fault (core dumped)

GIMP dies at the moment you touch picture with ink tool and tablet. No freezing,
it just shuts down immediately.

Naturally, I would expect a stroke to appear instead.

Ink tools works normally with mouse.
Comment 1 Sven Neumann 2004-11-22 00:49:46 UTC 
If you could provide a stack trace, that would help a lot. Please try running
gimp with the "--stack-trace-mode always" command-line option.
Comment 2 lauri.jarvenpaa 2004-11-22 21:42:27 UTC 
Do you mean this:

alt@alt> gimp --stack-trace-mode always
script-fu: Script-Fu Virhe suorittaessa
 (load "/home/alt/.gimp-2.2/scripts/extract_Frames.scm")
ERROR: end of file inside list


gimp: fatal error: Segmentation fault

+ Trace 52458

  • #0 g_on_error_stack_trace
  • #1 gimp_terminate
  • #2 gimp_fatal_error
  • #3 main
  • #4 ??
  • #5 blob_ellipse
  • #6 gimp_ink_get_type
  • #7 gimp_ink_get_type
  • #8 gimp_ink_get_type
  • #9 gimp_paint_core_paint
  • #10 gimp_paint_core_get_type
  • #11 gimp_paint_core_interpolate
  • #12 gimp_paint_tool_enable_color_picker
  • #13 gimp_tool_motion
  • #14 tool_manager_motion_active
  • #15 gimp_display_shell_canvas_tool_events
  • #16 gtk_marshal_VOID__UINT_STRING
  • #17 g_closure_invoke
    from /usr/local/lib/libgobject-2.0.so.400
  • #18 signal_emit_unlocked_R
  • #19 g_signal_emit_valist
  • #20 g_signal_emit
    from /usr/local/lib/libgobject-2.0.so.400
  • #21 gtk_widget_send_expose
  • #22 gtk_widget_event
    from /usr/X11R6/lib/libgtk-x11-2.0.so.400
  • #23 gtk_propagate_event
  • #24 gtk_main_do_event
  • #25 gdk_x11_register_standard_event_type
  • #26 g_main_dispatch
    from /usr/local/lib/libglib-2.0.so.400
  • #27 g_main_context_dispatch
  • #28 g_main_context_iterate
  • #29 g_main_loop_run
    from /usr/local/lib/libglib-2.0.so.400
  • #30 app_run
  • #31 main
  • #32 _start 

(script-fu:293): LibGimpBase-WARNING **: script-fu: wire_read(): error
Killed


I had to kill it, it didn't exit by itself. First time it locked all input, next
time just keyboard.
Comment 3 Sven Neumann 2004-11-22 22:05:16 UTC 
Now if your build had more useful debugging info that stack trace would be even
more useful. But it's a start.
Comment 4 Sven Neumann 2004-11-22 22:22:03 UTC 
I don't have a chance to test this myself right now but I have asked other
tablet users (on Linux) and they reported that the ink tool would work for them
on GIMP 2.2-preX. I wonder if this is specific to your setup. Does the ink tool
in GIMP 2.0 work for you?
Comment 5 lauri.jarvenpaa 2004-11-23 12:28:03 UTC 
Ink tool worked in gimp 2.0 and (when I installed it again) it still works.
Only in GIMP 2.2 it crashes.

Should I do some other tests?
Like, compiling with debug-flags (if there is such a switch in FreeBSD)?
Comment 6 lauri.jarvenpaa 2004-12-20 02:23:35 UTC 
I apologize, my mistake.

It appears that this too was a result of having HistorySize setting in XF86Config.
When I removed HistorySize from configuration, this problem vanished.

HistorySize was inherited to config from some how-to documents that drifted
around net.

Closing as NOTGNOME.