Bug 104423 – "input devices" crashes Gimp when changing settings.

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 104423 - "input devices" crashes Gimp when changing settings.


Summary:	"input devices" crashes Gimp when changing settings.


Status:	RESOLVED FIXED

Product:	GIMP
Classification:	Other
Component:	Tools
Version:	1.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	2.0
Assigned To:	GIMP Bugs
QA Contact:	Daniel Egger

URL:
Whiteboard:

Duplicates:	103760 108836 109247 (view as bug list)
Depends on:
Blocks:

Reported:	2003-01-25 21:20 UTC by Andrea Leganza
Modified:	2003-04-14 14:15 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Andrea Leganza 2003-01-25 21:20:51 UTC

I own a Wacom Graphire, when i try to enable this device (pressure levels
mainly) through the menu (monitor/window) or i try to change the device to
pen0/eraser0/cursor0) all crashes...

Versions GTK: 2.2.0 - Glib 2.2.0 - Kernel 2.4.20

This is the XF86Config:
*******************************
Section "ServerLayout"
        Identifier     "XFree86 Configured"
        Screen      0  "Screen0" 0 0
        InputDevice    "stylus0" "AlwaysCore" 
        InputDevice    "eraser0" "AlwaysCore"
        InputDevice    "cursor0" "AlwaysCore"
        InputDevice    "mouse"     "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection
...
...
...
Section "InputDevice"
   Identifier "stylus0"
   Driver "wacom"
   Option "Device" "/dev/input/event0"
   Option "Mode" "absolute"
   Option "Type" "stylus"
   Option "USB" "on"
   Option "Protocol" "Auto"
EndSection 

Section "InputDevice"
   Identifier "eraser0"
   Driver "wacom"
   Option "Device" "/dev/input/event0"
   Option "Mode" "absolute"
   Option "Protocol" "Auto"
   Option "Type" "eraser"
   Option "USB" "on"
EndSection
Section "InputDevice"
   Identifier "cursor0"
   Driver "wacom"
   Option "Device" "/dev/input/event0"
   Option "Protocol" "Auto"    
   Option "Mode" "absolute"
   Option "Type" "cursor"
   Option "USB" "on"
#   Option "AlwaysCore" "on"
EndSection

.....

*******************************
This is the stack trace of gdb:


gimp-1.3: fatal error: Segmentation fault
gimp-1.3 (pid:4828): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S

+ Trace 33130

#0 g_on_error_stack_trace
from /usr/lib/libglib-2.0.so.0
#1 g_on_error_query
from /usr/lib/libglib-2.0.so.0
#2 gimp_eek
#3 gimp_fatal_error
#4 <signal handler called>
#5 gtk_input_dialog_set_mapping_mode
#6 g_cclosure_marshal_VOID__VOID
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_menu_shell_activate_item
#13 gtk_menu_shell_button_release
#14 gtk_menu_button_release
from /usr/lib/libgtk-x11-2.0.so.0
#15 _gtk_marshal_BOOLEAN__BOXED
#16 g_type_class_meta_marshal
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_widget_event_internal
#22 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#25 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 gimp_main_loop
#30 app_init
#31 main
#32 __libc_start_main
from /lib/libc.so.6


/usr/lib/gimp/1.3/plug-ins/script-fu terminated: Interrupt
gimp-1.3: terminated: Interrupt

Comment 1 Sven Neumann 2003-01-26 02:03:51 UTC

I can confirm this. My setup used to work with gtk+-2.0 but broke as
you described when I updated to 2.2

Comment 2 Sven Neumann 2003-01-26 02:16:15 UTC

I fear the ugly hack we used to swallow the gtk+ input configuration
into our own window doesn't work with gtk+-2.2. This is because
gtk+-2.2 uses an internal routine input_dialog_from_widget(widget)
which returns the result of gtk_widget_get_toplevel(widget). The
calling code assumes to get a GtkInputDialog in return and not a gimp
preferences dialog.

Looks like we have to live with a GtkInputDialog that is opened from
the prefs dialog.

Comment 3 Sven Neumann 2003-01-26 12:34:55 UTC

*** Bug 103760 has been marked as a duplicate of this bug. ***

Comment 4 Sven Neumann 2003-01-26 14:27:40 UTC

While we are it, the current state of this particular part of the
prefs dialog is subject to criticism in bug #95446 as well. Perhaps we
can find a solution that fixes this one as well.

Comment 5 Sven Neumann 2003-03-20 15:22:43 UTC

*** Bug 108836 has been marked as a duplicate of this bug. ***

Comment 6 Ondrej Svetlik 2003-03-20 17:03:21 UTC

I tried to use my devicerc from gimp-1.2, but it doesn't work. What
should I change to make it work?

Error while parsing '/home/osvetlik/.gimp-1.3/devicerc' in line 1:
unable to determine type of 'device'

(device "WacomEraser"
        (mode screen)
        (axes 6 x y pressure xtilt ytilt ignore)
        (keys 32 "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
"" "" ""
        (tool "Rect Select")
        (foreground 0 0 0)
        (brush "Circle (19)")
        (pattern "Pine?")
        (gradient "German_flag_smooth"))

Comment 7 Sven Neumann 2003-03-20 17:47:39 UTC

Help us to fix the input devices dialog, that's what you should do.

Comment 8 Sven Neumann 2003-03-26 12:47:22 UTC

*** Bug 109247 has been marked as a duplicate of this bug. ***

Comment 9 Sven Neumann 2003-04-14 14:15:27 UTC

2003-04-14  Sven Neumann  <sven@gimp.org>

  * app/gui/preferences-dialog.c: don't try to reparent the children
  of GtkInputDialog but simply pop up the dialog as provided by
  GTK+. Looks ugly but shouldn't crash any longer. Fixes bug #104423.