In Maverick, same procedure as reporter caused same problem. Not to dig,
but I use Kolour (in GNOME), may want to switch to for time being. Bug
report auto-spotted this so placed myself on affected list and
confirming.
lsb_release -rd
Description:Ubuntu maverick (development branch)
Release:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I noticed that the package version your bugging is
updated in Lucid. Please update via http://releases.ubuntu.com/lucid/
repost a detailed error report, and update the bug status. Thanks!
** Changed in: xaralx
Running Ubuntu Karmic Beta on AMD64 somtimes I was able to print, but it
usually crashes
--
[apport] xaralx crashed with SIGSEGV in wxWindow::OnInternalIdle() when
attempting to print
https://bugs.launchpad.net/bugs/122158
You received this bug notification because you are a member of Ubuntu
Is this a duplicate of bug 96046?
--
[apport] xaralx crashed with SIGSEGV in wxWindow::OnInternalIdle() when
attempting to print
https://bugs.launchpad.net/bugs/122158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The crash is still present on Ubuntu 8.10.
--
[apport] xaralx crashed with SIGSEGV in wxWindow::OnInternalIdle() when
attempting to print
https://bugs.launchpad.net/bugs/122158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The same problem happens with freshly installed Gutsy (7.10) on x68 and
amd64 platforms. xaralx crashes 100% when attempting to print to a
printer or exporting the drawing to a pdf.
Attaching the stack dump from the core file of xaralx version 0.7r1692-2
from amd64 platform.
** Attachment added:
** Attachment added: xaralx-core-file-amd64
http://launchpadlibrarian.net/12705268/core.gz
--
[apport] xaralx crashed with SIGSEGV in wxWindow::OnInternalIdle() when
attempting to print
https://bugs.launchpad.net/bugs/122158
You received this bug notification because you are a member of
The error is not from xaralx.
Apparently apt did a bad job upgrading xara to gutsy.
all you have to do to have it working again is
sudo apt-get install xaralx, as the package is not even recognized as installed
by the system.
(type sudo apt-get remove --purge xaralx in a terminal and you'll
** Changed in: xaralx (Ubuntu)
Importance: Undecided = Medium
--
[apport] xaralx crashed with SIGSEGV in wxWindow::OnInternalIdle()
https://bugs.launchpad.net/bugs/122158
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/8187159/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/8187160/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/8187161/Disassembly.txt
** Attachment
I don't have any type of debug version of XaraLx, but I got as much
information as possible without having appropriate debug symbols in the
executable.
** Attachment added: gdb-xaralx.txt
http://launchpadlibrarian.net/8187195/gdb-xaralx.txt
--
[apport] xaralx crashed with SIGSEGV in
Does the problem occur in the upstream version (try the autopackage
version from www.xaraxtreme.org)?
I have a feeling this is some wxWindows incompatibility on Feisty Fawn.
Alex
--
[apport] xaralx crashed with SIGSEGV in wxWindow::OnInternalIdle()
https://bugs.launchpad.net/bugs/122158
You
12 matches
Mail list logo
