scribus crashed with SIGSEGV in ScribusMainWindow::ClipChange()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
scribus (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: scribus
opened scribus ... tried to open the presentation with a large number of images in openoffice... scribus crached
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: scribus 1.3.3.13.
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelMo
Architecture: i386
CheckboxSubmission: 2a13c603e031963
CheckboxSystem: b5acb6c9ca4017b
Date: Thu Apr 8 11:49:14 2010
Disassembly: => 0x79: Cannot access memory at address 0x79
ExecutablePath: /usr/bin/scribus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: scribus /home/username/
ProcEnviron:
LANG=ru_RU.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x79: Cannot access memory at address 0x79
PC (0x00000079) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: scribus
StacktraceTop:
ScribusMainWin
ScribusMainWin
QObject:
QObject:
QClipboard:
Title: scribus crashed with SIGSEGV in ScribusMainWind
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running `apport-collect 557759` and any other logs that are relevant for this particular issue.
Furthermore, Lucid (desktop) reached EOL on 2013-05-09. /wiki.ubuntu. com/Releases
See this document for currently supported Ubuntu releases: https:/
I've tried recreating this bug with Trusty and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible please do what I write above.
Do feel free to report any other bugs you may find.