Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 283555 - gnome-extra/gpointing-device-settings ebuild to obsolete gsynaptics
Summary: gnome-extra/gpointing-device-settings ebuild to obsolete gsynaptics
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement
Assignee: Peter Volkov (RETIRED)
URL: http://gsynaptics.sourceforge.jp/
Whiteboard:
Keywords: EBUILD, InOverlay
Depends on:
Blocks:
 
Reported: 2009-09-02 19:46 UTC by Saphirus
Modified: 2009-09-29 17:16 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Saphirus 2009-09-02 19:46:29 UTC
GPointingDeviceSettings looks to be the more up to date GUI application for the configuration of synaptics touchpads, and therefore an ebuild is needed.

Reproducible: Always

Steps to Reproduce:
1.emerge gpointing-device-settings
2.Package not found
3.

Actual Results:  
No ebuild is available, no application was installed.

Expected Results:  
The program should be available, subsequently compiled, and installed

GPointingDeviceSettings: http://live.gnome.org/GPointingDeviceSettings
Comment 1 Peter Volkov (RETIRED) gentoo-dev 2009-09-21 07:11:56 UTC
I've tried this package but regretfully it's not working here. YMMV, so, please, try it from my overlay:

svn checkout http://overlays.gentoo.org/svn/dev/pva/gnome-extra

Currently I have two issues with this package:

1. it does not work. It fails with the following error:

Gdk-ERROR **: The program 'gpointing-device-settings' received an X
Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 108 error_code 1 request_code 145 minor_code 36)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.)
aborting...

I've fired gdb and here's what I got:

Breakpoint 1, gdk_x_error (display=0x8f1a000, error=0xbfe8e1cc) at
gdkmain-x11.c:614
614     gdkmain-x11.c: No such file or directory.
        in gdkmain-x11.c
(gdb) bt
#0  gdk_x_error (display=0x8f1a000, error=0xbfe8e1cc) at gdkmain-x11.c:614
#1  0xb72e54c8 in _XError () from /usr/lib/libX11.so.6
#2  0xb72edfd1 in _XReply () from /usr/lib/libX11.so.6
#3  0xb73be2ee in XListDeviceProperties (dpy=0x8f1a000, dev=0x90416b0, nprops_return=0xbfe8e30c) at XListDProp.c:61
#4  0xb7eef552 in get_atom (xinput=<value optimized out>, property_name=0x8f6a000 "Evdev Middle Button Emulation", error=0xbfe8e40c)
    at gpds-xinput.c:387
#5  0xb7eefb1a in gpds_xinput_get_int_properties_by_name (xinput=0x8f69e78, property_name=0x8f6a000 "Evdev Middle Button Emulation", 
    error=0xbfe8e40c, values=0xbfe8e45c, n_values=0xbfe8e458) at gpds-xinput.c:426
#6  0xb7eefd6b in gpds_xinput_get_int_properties (xinput=0x8f69e78, property_enum=0, error=0xbfe8e40c, values=0xbfe8e45c, 
    n_values=0xbfe8e458) at gpds-xinput.c:491
#7  0xb7eee816 in gpds_xinput_ui_get_xinput_int_property (ui=0x8f54428, property=0, values=0xbfe8e45c, n_values=0xbfe8e458)
    at gpds-xinput-ui.c:142
#8  0xb7eeea75 in gpds_xinput_ui_set_toggle_button_state_from_preference (ui=0x8f54428, property=0, 
    gconf_key_name=0xb6f26cdb "middle_button_emulation", button_name=0xb6f26cdb "middle_button_emulation") at gpds-xinput-ui.c:199
#9  0xb6f25bb4 in build (ui=0x8f54428, error=0xbfe8e59c) at gpds-mouse-ui.c:410
#10 0xb7eee02f in gpds_ui_build (ui=0x8f54428, error=0xbfe8e59c) at gpds-ui.c:221
#11 0x08049287 in append_ui (icon_view=0xb77e95c0, notebook=0x8f1a000, ui=0x8f1a000) at gpointing-device-settings.c:104
#12 0x0804969c in main (argc=1, argv=0xbfe8e6c4) at gpointing-device-settings.c:166

2. gnome-cotrol-center starting with 2.27.4 now has similar configuration for touchpad:

http://git.gnome.org/cgit/gnome-control-center/commit/?id=e14a84a718d9882d320de1f359c0547836a9b4e3

Well, this is limited configuration, but still common things exist and it looks like both configuration tools will collide. How could we will handle this situation?

I've contacted upstream on this issues and we'll see how it goes...
Comment 2 Oldrich Jedlicka 2009-09-21 21:35:30 UTC
Works for me: xorg-server-1.6.3, xorg-x11-7.4-r1 and xf86-input-synaptics-1.1.3. This has something to do with new device properties in xorg I guess.
Comment 3 waynedpj 2009-09-22 00:23:49 UTC
(In reply to comment #1)
> I've tried this package but regretfully it's not working here. YMMV, so,
> please, try it from my overlay:
> 
> svn checkout http://overlays.gentoo.org/svn/dev/pva/gnome-extra
> 
> Currently I have two issues with this package:
> 
> 1. it does not work. It fails with the following error:
> 
> Gdk-ERROR **: The program 'gpointing-device-settings' received an X
> Window System error.
> This probably reflects a bug in the program.
> The error was 'BadRequest (invalid request code or no such operation)'.
>   (Details: serial 108 error_code 1 request_code 145 minor_code 36)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.)
> aborting...
> 
> I've fired gdb and here's what I got:
> 
> Breakpoint 1, gdk_x_error (display=0x8f1a000, error=0xbfe8e1cc) at
> gdkmain-x11.c:614
> 614     gdkmain-x11.c: No such file or directory.
>         in gdkmain-x11.c
> (gdb) bt
> #0  gdk_x_error (display=0x8f1a000, error=0xbfe8e1cc) at gdkmain-x11.c:614
> #1  0xb72e54c8 in _XError () from /usr/lib/libX11.so.6
> #2  0xb72edfd1 in _XReply () from /usr/lib/libX11.so.6
> #3  0xb73be2ee in XListDeviceProperties (dpy=0x8f1a000, dev=0x90416b0,
> nprops_return=0xbfe8e30c) at XListDProp.c:61
> #4  0xb7eef552 in get_atom (xinput=<value optimized out>,
> property_name=0x8f6a000 "Evdev Middle Button Emulation", error=0xbfe8e40c)
>     at gpds-xinput.c:387
> #5  0xb7eefb1a in gpds_xinput_get_int_properties_by_name (xinput=0x8f69e78,
> property_name=0x8f6a000 "Evdev Middle Button Emulation", 
>     error=0xbfe8e40c, values=0xbfe8e45c, n_values=0xbfe8e458) at
> gpds-xinput.c:426
> #6  0xb7eefd6b in gpds_xinput_get_int_properties (xinput=0x8f69e78,
> property_enum=0, error=0xbfe8e40c, values=0xbfe8e45c, 
>     n_values=0xbfe8e458) at gpds-xinput.c:491
> #7  0xb7eee816 in gpds_xinput_ui_get_xinput_int_property (ui=0x8f54428,
> property=0, values=0xbfe8e45c, n_values=0xbfe8e458)
>     at gpds-xinput-ui.c:142
> #8  0xb7eeea75 in gpds_xinput_ui_set_toggle_button_state_from_preference
> (ui=0x8f54428, property=0, 
>     gconf_key_name=0xb6f26cdb "middle_button_emulation", button_name=0xb6f26cdb
> "middle_button_emulation") at gpds-xinput-ui.c:199
> #9  0xb6f25bb4 in build (ui=0x8f54428, error=0xbfe8e59c) at gpds-mouse-ui.c:410
> #10 0xb7eee02f in gpds_ui_build (ui=0x8f54428, error=0xbfe8e59c) at
> gpds-ui.c:221
> #11 0x08049287 in append_ui (icon_view=0xb77e95c0, notebook=0x8f1a000,
> ui=0x8f1a000) at gpointing-device-settings.c:104
> #12 0x0804969c in main (argc=1, argv=0xbfe8e6c4) at
> gpointing-device-settings.c:166
> 
> 2. gnome-cotrol-center starting with 2.27.4 now has similar configuration for
> touchpad:
> 
> http://git.gnome.org/cgit/gnome-control-center/commit/?id=e14a84a718d9882d320de1f359c0547836a9b4e3
> 
> Well, this is limited configuration, but still common things exist and it looks
> like both configuration tools will collide. How could we will handle this
> situation?
> 
> I've contacted upstream on this issues and we'll see how it goes...
> 

i can confirm that i had this exact bug.  however, i updated to xorg-server 1.6.3.901-r2 and xf86-input-synaptics 1.0.0 and now it works.  just needs a menu entry and icon :)

peace

Comment 4 Oldrich Jedlicka 2009-09-22 06:08:08 UTC
(In reply to comment #3)
> i can confirm that i had this exact bug.  however, i updated to xorg-server
> 1.6.3.901-r2 and xf86-input-synaptics 1.0.0 and now it works.  just needs a
> menu entry and icon :)

I think the minimum is xorg-server-1.6, it first introduced device properties: http://www.x.org/wiki/Server16Branch
Comment 5 Peter Volkov (RETIRED) gentoo-dev 2009-09-25 16:16:53 UTC
Thank you guys. It really works with xorg-server-1.6, so I've added blocker into ebuild. Also now it creates menu entry and I did some cleanups, so, time to svn up and rebuild and report if anything went wrong :)

The last problem I have: it does not restore settings on gnome startup. I found similar report in Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530306 Currently I have no ideas what cases this behavior and I've reported bug upstream https://bugzilla.gnome.org/show_bug.cgi?id=596328
Comment 6 Peter Volkov (RETIRED) gentoo-dev 2009-09-29 15:32:42 UTC
Upstream resolved issue and this package is in the tree. Thank you again guys.

NOTE that if you used previous versions of gpointing-device-settings you may need to remove buggy boolean value with the following command:

$ gconftool-2 -u
/desktop/gnome/peripherals/SynPS@47@2@32@Synaptics@32@TouchPad/off
Comment 7 waynedpj 2009-09-29 17:16:51 UTC
(In reply to comment #6)
> Upstream resolved issue and this package is in the tree. Thank you again guys.
> 
> NOTE that if you used previous versions of gpointing-device-settings you may
> need to remove buggy boolean value with the following command:
> 
> $ gconftool-2 -u
> /desktop/gnome/peripherals/SynPS@47@2@32@Synaptics@32@TouchPad/off
> 

thanks to you for getting this fixed and in portage.  much appreciated.