You are not logged in.
Hi,
On recent slitaz-rolling, steps to reproduce in terminal :
tux@slitaz:~$ gnumeric
** (gnumeric:1865): WARNING **: Couldn't connect to accessibility bus: Empty address ''
Here in gnumeric I did press menu_key and that cause the crash :
(gnumeric:1865): Gdk-WARNING **: The program 'gnumeric' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
(Details: serial 2627 error_code 146 request_code 140 (XInputExtension) minor_code 40)
(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 GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
No problem on another machine :
pierre@dv7-bullseye-xfce:~$ gnumeric -v
gnumeric version « 1.12.48 »
menu_key brings up a menu as expected.
So a gnumeric upgrade would be appreciated. Thanks in advance and regards,
Pierre
Offline
Pushed https://hg.slitaz.org/wok/rev/4c101652eb90#l4.1
Can you test http://mirror1.slitaz.org/packages/cooking/goffice-0.10.53.tazpkg
and http://mirror1.slitaz.org/packages/cooking/gnumeric-1.12.53.tazpkg ?
Offline
Unfortunately problem is not solved. Same error, see below.
Le système est à jour...
296 paquets installés scannés en 0s
tux@slitaz:~$ gnumeric --version
gnumeric version '1.12.53'
datadir := '/usr/share/gnumeric/1.12.53'
libdir := '/usr/lib/gnumeric/1.12.53'
tux@slitaz:~$ gnumeric
** (gnumeric:13738): WARNING **: Couldn't connect to accessibility bus: Empty address ''
Here in gnumeric I did press menu_key and that cause the crash :
(gnumeric:13738): Gdk-WARNING **: The program 'gnumeric' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
(Details: serial 5590 error_code 146 request_code 140 (XInputExtension) minor_code 40)
(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 GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
tux@slitaz:~$
Thanks for your help. Regards, Pierre
Offline
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]