Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Xaralx on testingHi, Recently, I upgraded my machine to testing from sarge. On sarge, xaralx .... Can someone point to me a solution for this problem? Regards, -- Be security conscious -- National defense is at stake. Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Xaralx on testing
On Tue, Nov 28, 2006 at 21:36:24 +0530, Sridhar M.A. wrote:
> Hi,
>
> Recently, I upgraded my machine to testing from sarge. On sarge, xaralx
> (version 0.7 rev. 1764) would run without any issues. But after the upgrade,
> it segfaults. Removed ~/..XARA-XTREME-WX-xaralx-mas and
> ~/.XaraLXFilters/. Still the same problem. Ran strace on xaralx and here
> are the last lines of the ouput:
>
> ....
> fstat64(6, {st_mode=S_IFREG|0644, st_size=909044, ...}) = 0
> mmap2(NULL, 935588, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 6,
> 0) = 0xb6fea000
> mmap2(0xb70c4000, 20480, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 6, 0xd9) = 0xb70c4000
> mmap2(0xb70c9000, 22180, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb70c9000
> close(6) = 0
> mprotect(0xb70c4000, 12288, PROT_READ) = 0
> gettimeofday({1164678795, 243914}, NULL) = 0
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> rt_sigaction(SIGFPE, {SIG_DFL}, NULL, 8) = 0
> rt_sigaction(SIGILL, {SIG_DFL}, NULL, 8) = 0
> rt_sigaction(SIGBUS, {SIG_DFL}, NULL, 8) = 0
> rt_sigaction(SIGSEGV, {SIG_DFL}, NULL, 8) = 0
> rt_sigaction(SIGFPE, {0xb781e790, [], 0}, {SIG_DFL}, 8) = 0
> rt_sigaction(SIGILL, {0xb781e790, [], 0}, {SIG_DFL}, 8) = 0
> rt_sigaction(SIGBUS, {0xb781e790, [], 0}, {SIG_DFL}, 8) = 0
> rt_sigaction(SIGSEGV, {0xb781e790, [], 0}, {SIG_DFL}, 8) = 0
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> Process 3907 detached
>
> Can someone point to me a solution for this problem?
Do you really need to have rev. 1764? The xaralx package 0.7r1692-2 from
the testing/non-free repository works fine for me.
How did you install the newer version? If you compiled it yourself then
you might simply have to recompile it for Etch.
--
Regards,
Florian
--
Xaralx on testing
On Tue, Nov 28, 2006 at 07:50:52PM +0100, Florian Kulzer wrote:
>
> Do you really need to have rev. 1764? The xaralx package 0.7r1692-2 from
> the testing/non-free repository works fine for me.
>
That works here. Regarding your observation whether I _really_ need it,
I can just say I am curious to try new version for the new features,
etc.
But, the question is more about a software that ran perfectly not
running on an upgraded system. The particular version which ran under
sarge no longer runs under etch. FWIW, I was using the xorg packages
from backports under sarge.
> How did you install the newer version? If you compiled it yourself then
> you might simply have to recompile it for Etch.
>
Running the tarball. Tried the 1692 tarball from xaraxtreme.org; that
also segfaults :-(
Regards,
--
Sridhar M.A. GPG KeyID : F6A35935
Fingerprint: D172 22C4 7CDC D9CD 62B5 55C1 2A69 D5D8 F6A3 5935
Chihuahuas drive me crazy. I can't stand anything that shivers when it's warm.
Xaralx on testing
On Wed, Nov 29, 2006 at 07:42:22 +0530, Sridhar M.A. wrote:
> On Tue, Nov 28, 2006 at 07:50:52PM +0100, Florian Kulzer wrote:
> >
> > Do you really need to have rev. 1764? The xaralx package 0.7r1692-2 from
> > the testing/non-free repository works fine for me.
> >
> That works here. Regarding your observation whether I _really_ need it,
> I can just say I am curious to try new version for the new features,
> etc.
Acknowledged. I justed wanted to make sure you knew that there is a
ready-to-go package (slightly older) available in testing/non-free.
> But, the question is more about a software that ran perfectly not
> running on an upgraded system. The particular version which ran under
> sarge no longer runs under etch. FWIW, I was using the xorg packages
> from backports under sarge.
>
> > How did you install the newer version? If you compiled it yourself then
> > you might simply have to recompile it for Etch.
> >
> Running the tarball. Tried the 1692 tarball from xaraxtreme.org; that
> also segfaults :-(
I think this means that the binaries in the tarballs have been compiled
for the Sarge versions of certain libraries and do not work with the
newer versions of those libraries on Etch. You might have to compile
from source yourself if you want the latest xaralx release to run on
Etch. I assume you noticed the remark on the webpage regarding
libstdc++5 compatibility; maybe the necessary package is not installed
by default on a standard Etch system.
--
Regards,
Florian
--
Xaralx on testing
On Wed, Nov 29, 2006 at 05:17:43PM +0100, Florian Kulzer wrote:
>
> I assume you noticed the remark on the webpage regarding
> libstdc++5 compatibility; maybe the necessary package is not installed
> by default on a standard Etch system.
>
It was installed and is even in Etch.
$ apt-cache policy libstdc++5
libstdc++5:
Installed: 1:3.3.6-13
Candidate: 1:3.3.6-13
Version table:
*** 1:3.3.6-13 0
900 http://ftp.debian.org testing/main Packages
100 /var/lib/dpkg/status
I will try compiling from the source and see. It might be some days
before I get to that.
Regards,
--
Sridhar M.A. GPG KeyID : F6A35935
Fingerprint: D172 22C4 7CDC D9CD 62B5 55C1 2A69 D5D8 F6A3 5935
micro:
Thinker toys.
Xaralx on testing (solved)
On Fri, Dec 01, 2006 at 08:40:15PM +0530, Sridhar M.A. wrote:
> On Wed, Nov 29, 2006 at 05:17:43PM +0100, Florian Kulzer wrote:
> >
> > I assume you noticed the remark on the webpage regarding
> > libstdc++5 compatibility; maybe the necessary package is not installed
> > by default on a standard Etch system.
> >
> It was installed and is even in Etch.
>
> $ apt-cache policy libstdc++5
> libstdc++5:
> Installed: 1:3.3.6-13
> Candidate: 1:3.3.6-13
> Version table:
> *** 1:3.3.6-13 0
> 900 http://ftp.debian.org testing/main Packages
> 100 /var/lib/dpkg/status
>
> I will try compiling from the source and see. It might be some days
> before I get to that.
>
The problem seems to be with the SCIM package. I was pointed to the
error in xaralx forum which solved the problem. In case, someone has a
similar problem, here is the link :
http://talkgraphics.com/showthread.php?t=22858
Thanks for everyone.
Regards,
--
Sridhar M.A. GPG KeyID : F6A35935
Fingerprint: D172 22C4 7CDC D9CD 62B5 55C1 2A69 D5D8 F6A3 5935
Excuse me, but didn't I tell you there's NO HOPE for the survival of
OFFSET PRINTING?