Unable to start xaralx on Ubuntu 6.06

Hi,

I've installed the autopackage v.7 rev 1692 on both my laptop and desktop computers, both running Ubuntu Dapper. The desktop computer works like a charm. On the laptop, I get this:

paul@Gernsback:~$ xaralx
Aborted

As you can imagine, this error message does very little to help me track down the problem.

Just in case it's relevant, here is the output of the installation (sudo ./RecXaraLX0.7_rev1692.package), which seemed to have a small error. . .

Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
GTK Panel of SCIM 1.4.4

Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
GTK Panel of SCIM 1.4.4

sed: -e expression #1, char 2: unterminated `s' command
/usr/share/autopackage/apkg-script-utils: line 1965: /,/: No such file or directory
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
GTK Panel of SCIM 1.4.4

Quote:

---

Originally Posted by kashirigi

Hi,

I've installed the autopackage v.7 rev 1692 on both my laptop and desktop computers, both running Ubuntu Dapper. The desktop computer works like a charm. On the laptop, I get this:

---

Is this an x86 or an x86_64 laptop?

If you hold on for a few days there will hopefully be an Ubuntu .deb to install. It looks like an autopackage problem to me.

Alex

It's an x86 laptop.

I suspect a .deb won't help -- I've downloaded other debs, tried various versions of the autopackage, all with the same results.

As far as I can tell, I've met all the dependencies.

That error message is completely useless, and infuriating.

I've also just manually updated autopackage to 1.0.10 and reinstalled Xara. I now get no errors on installation. However, on running xaralx I get the same error, so I suspect it may not be an autopackage difficulty.

Quote:

---

Originally Posted by kashirigi

It's an x86 laptop.

I suspect a .deb won't help -- I've downloaded other debs, tried various versions of the autopackage, all with the same results.

As far as I can tell, I've met all the dependencies.

That error message is completely useless, and infuriating.

---

The autopackage version is compiled with an old version of the C++ libary and an old version of the compiler for maximum compatability, but it sometimes causes problems (hence my suggestion to use the .deb - completely different code, dynamic linked rather than static linked).

I'm running ann x86 laptop here and have no problems (else I'd have just fixed it!). I'm not sure what the easiest way is to debug this - I've never seen LX error so early (and uninformatively) other than with a shared library problem, and that normally tells you which library is at fault.

So first of all, can you check you have plenty of memory free? If it can't even page the executable in, it won't be able to run.

Second, can you try this:
script /tmp/test
gdb /path/to/xaralx [substuting your path]
run
(see what happens)
quit
[CTRL ^D]

then post /tmp/test (which should be a log of the debugger output). That might help.

Alex

Well, it does look like it might be C library problem.

Here's the debugging output, along with a "free" and a "ps aux" for good measure.

Thanks for the help you're giving. I really appreciate it.

Quote:

---

Originally Posted by kashirigi

Well, it does look like it might be C library problem.

Here's the debugging output, along with a "free" and a "ps aux" for good measure.

Thanks for the help you're giving. I really appreciate it.

---

OK, it's getting a seg fault from something or other. Could you please repeat the process, but after the seg fault ("Program received signal SIGSEGV, Segmentation fault.") type "bt" before doing the "quit", then paste the result again.

It must be pretty early on on the execution sequence because we install our own SEGV handler.

Alex

Hi Alex,

Here is the new, revised, output.

Thanks again.

Interesting. It looks like the scim problem we've been having with Mandriva is appearing on Ubuntu too.

I've added your backtrace to:
http://bugzilla.xara.com/show_bug.cgi?id=1574

feel free to add yourself as a CC on the bug (you'll need to set up an account). Hopefully this will be of use to Luke in narrowing it down given it happens so very early on boot.

The good news is that the last I heard from Luke, this /was/ a C-library problem, so a native .deb should fix it.

Alex

I have made a cludgy hack to "solve" the problem. I haven't played around with it, but at least it will start now. I won't have Japanese input in Xara, but I can live without it, at least for now.

make a new file called xaralx.sh, and make it's contents like this:

#! /bin/bash
unset XMODIFIERS
unset GTK_IM_MODULE
unset QT_IM_MODULE
/usr/bin/xaralx &
export XMODIFIERS=@im=SCIM
export GTM_IM_MODULES=scim
export QT_IM_MODULES=scim


instead of running xaralx, use sh ./xaralx.sh

I certainly can't guarantee that this will work on every system. I does, however, make xara start on mine.