Hi all.

I have slackware64-13.0 & xfce. I installed somebody's openoffice package ( a repackaging of the rpms), openoffice.org-3.2.0_en_US-x86_64-1_rlw.txz and ran into crazy keyboard issues, double inserts of random keys when I type faster than a snail's pace liikee tthiis. I had errors from xkbcomp rolling off the screen.
> Using last definition
> Warning: Duplicate shape name ""
> Using last definition
> Warning: Duplicate shape name ""
> Using last definition
> Warning: Multiple doodads named ""
> Using first definition
> Warning: Multiple doodads named ""
> Using first deeinition

I did find that I had NoDeadKeys specified, and X really objected because there were no dead keys on my keymap. Then this error

(xfce4-settings-helper:25774): xfce4-settings-helper-CRITICAL **: XI
is not present or too old.

is apparently fixed in latest git of xfce, but not in slack-current,
and I was getting nowhere fast. So I thought I'd ask in case someone
had sorted this on slackware and could save me energy

Not a direct solution, but Robby Workman released a package for Xfce 4.6.2 (Slack 13.1 only). You can try his Slackbuild to build Xfce 4.6.2 on Slack 13.0:

http://rlworkman.net/pkgs/

I may well do that. I did actually find a way around the problem thanks, startx > xorg.err 2>&1 showed me keyboard compiling errors; fixing those reported errors stopped all the messing, because xkbcomp is never more verbose than when something isn't quite perfect.

Now I'm left with the openoffice problem, and it is this: when I type 2 letters together very fast the first one is repeated twice. It's even possible to get a string repeated twice, like thithis. When openoffice is open, this madness is present in firefox also.

Have you tried the package at slackbuilds. What i do is run sbopkg and let that do it all for me.

Have you tried http://rlworkman.net/pkgs/13.1/x86_64/ ?
(Haven't done it myself, but will in a couple of days when I finally will have upgraded)

1 members found this post helpful.

@Olaus: That's where I got my openoffice package from. I'm not sure it's a problem with that package, but something nutty is going on that I'm not at the bottom of.

@arubin: I'll head off there now.

Did you check the md5sum of the package? I'm running Robby's 32 bit 13.1 package for OOo 3.2.0 at home without issues on several machines.
Perhaps your download is corrupt?

bash-3.1$ md5sum openoffice.org-3.2.0_en_US-x86_64-1_rlw.txz
032d75cd71b888ec5d822b46a3591863 openoffice.org-3.2.0_en_US-x86_64-1_rlw.txz
I am not in the habit of getting dodgy downloads here.

I built from slackbuilds.org and had exactly the same issue. So it can't be openoffice, unless it's something in the rpms. I have 13.0 updated in the X area to 13.1 and having openoffice open drives X crazy. keyboard input slows and requests back up. If I type a line fast in xorg, I have to wait 4 or 5 seconds to switch screen! Close openoffice, and the problem disappears. I tried this:
top | grep -A5 -e 'PID' >> openoffice.load. The file is at
http://pastebin.com/eAbNCH0f

Top outputs %cpu, %mem, Time, and Program name at the right. You can see that typing a line into openoffice (the only load on X at this time) consumed huge resources - X up to 64% cpu, xfwm4 up to 29% cpu, and I'm sitting on a twin core turion @ 2ghz, with 4 gigs of ram, so I'm not embarrassed for resources. I'm also left with a bug that pressing down arrow inserts a line feed every time. STDOUT has the"Multiple dooads " errors back again, so I presume it's trying to compile a keyboard for every letter or the like. Strewth!

So I'd better take the other bit of advice, and update to xfce-4.6.2
I dream of just going back to being a luser on this box one year soon :-/.

1 members found this post helpful.

Mebbe a bug in OO-3.2.0 or some sort of version conflict that nobody else seems to have. I am getting 11 xkbcomp attempts per letter pressed to compile a keyboard which each add nearly 30k of spam to stdout! And about 7 per mouse key pressed.

There is a new version of OpenOffice.
Now says Oracle.

Anyone have a slackbuild?

You have Slackware 13.0 but with upgraded X packages from 13.1? Maybe that would be the issue. :-/ OOo could just be unmasking a problem with your X setup. You cannot just grab 13.1's X packages and use them on 13.0 without introducing problems...you might be able to compile an upgraded X on 13.0 without suffering such problems but certainly upgrading to 13.1 entirely or sticking with stock 13.0 X would help to identify whether that is the problem or not.

I know, I know. I've told people that myself. I have warned people about being on the bleeding edge - the problem is you bleed!
Moving from xfce-4.6.1 to xfce-4.6.2 involves changes in 4 or 5 libraries, one of which, libnotify, objects to being compiled, and doesn't seem available otherwise. OO-3.2.0 is apparently not bug free, and people are waiting for bugfix releases. I don't want any of this and will forget it, and make friends with abiword, or emacs, even lyx or scribus. I've searched high and low for a line for xkbcomp which will give me a precompiled keyboard. So I regressed to xfce-4.6.1, removed openoffice-3.2.0, and got myself a life. This is testing my loyalty to slackware and xfce somewhat. Slamd64-12.2 just worked much better out of the box.

Is 13.1 up to the latest video drivers from ATI?

For what it's worth, isn't Slackware 13.1 either released or at the very least out with a second (or third) potential release candidate? Would a backup of relevant personal data (unless you have your /home partition separate, which can be a good idea), then a fresh installation of the latest 13.1 kit (with Open Office 3.2), possibly help out?

You indicate possible conflicts between X server libraries and application interfaces. It seems to me that you should be able to get something pretty recent from RC1, RC2, or the latest, whatever is closest to final release that works for you.

I just pushed a package of xfce-4.6.2 for Slackware 13.0 in my repo, but even so, you're trying to do something that isn't supposed to work, so when it doesn't, why even bother asking for help??

That's a valid question deserving an answer.
I have never had decent graphics on this box with the ati drivers available. So I started on that, and tried to update slamd64-12.2 to run the xf86-video-ati-6.9.0. That failed miserably, slamd64 is no longer updating with any frequency. So I installed the latest salckware64, 13.0. Then I had to fight with the video driver again from scratch and finally got a working version after a few weeks of compiling this and that in spare time. Then I had huge keyboard problems, as slackware seems reluctant to run on any locale except en_US without throwing keyboard errors. A kernel upgrade was in there which caused it's own set of problems. Then the radeon released 6.13.0 with KMS so I went after that. It was always a bitch trying to get any new program installed, as it seemed to break everything. I installed googleearth, but found I needed a 32 bit libGL.so so I had to transform to a multilib box and get mesa to compile with the --enable-32bit option. On the way, there were countless updates to this and that, lib*, etc. Then to use any of this, I installed mplayer and lost time getting that right. By this time everything X related was up to slack64-current, and had left slack64-13.1 behind.
When I installed firefox I also had issues, but they were trivial by comparison with openoffice. The only straightforward install was wine. Call me a creature of habit, but I like OO, have many docs in odt format, and wanted OO. And of course all the power management stuff reared up and bit me, because this is a laptop.

To see if OO would settle, I did install xfce-4.6.2. That wouldn't run, because they've updated libraries left, right, & centre between the 2 versions. libnotify definitely didn't want to compile here, and I seemed in for another versions war. Even worse is probably that I've probably installed packages which want a later version of some libs than the ones I have, and that's next to impossible to find. If you compile everything, this gets caught usually, but not simply installing packages

So I decided I could put up with slamd64-12.2, and less than perfect graphics. I seemed caught is a compile/install tailspin, and decided to lay off and get my life back. I simply changed my default choice in grub to point to slamd64-12.2