On Jan 2, 2006, at 5:26 PM, Martin Costabel wrote:
Stan,
I have seen many crashes of scribus, but yours are new :-)
Thanks Martin.
I've always enjoyed blazing new trails...
Stan Sanderson wrote:
aagggghhh.
OS 10.4.3, latest unstable tree all updated, XOrg, Gnome
Scribus 1.3.1-2
Did you build scribus while the same version of xorg was installed?
Which version of xorg?
Yes, and have both rebuilt from source *and* apt-get install(ed) the
binary. Both behaved the same way.
I am using xorg v. 6.8.2-35 (latest). Also should note that I have
XTools 2.0 installed.
[]
I have tried repairing permissions, single-user boot w/ fsck,
reinstalling Scribus, rm -r the ~/.scribus directory, reinstalling
xorg all with out success.
Suggestions would be greatly appreciated.
Crash report upon attempting a new document:
EXC_BAD_ACCESS (0x0001)
KERN_INVALID_ADDRESS (0x0001) at 0xfd85b400
Thread 2 Crashed:
0 Dispatch + 636 (crt.c:355)
1 main + 1472 (crt.c:355)
2 -[XServer run] + 120 (crt.c:355)
3 forkThreadForFunction + 108
4 _pthread_body + 96
(XDarwin quits)
From what you are saying it seems that it worked at first and now
you cannot even create a new document, right?
Right. When starting Scribus, it takes a very long time "searching
for fonts" before loading the initial document setup window. I have
another machine running 10.3.9 (and xorg). I installed the scribus
binary (v 1.2.?) and noted that the font search was very fast.
If this is so, then *something* must be different between the time
when it worked and now.
Only a few hours elapsed, during which time the machine was asleep.
As mentioned, I had trouble getting a two-column text section,
decided to put the work aside temporarily so saved and closed the
file. I later restarted XDarwin (xorg) and tried to bring the
document up in scribus but couldn't with the results mentioned.
Again- xephem, gnumeric, and apparently the gimp appear to be working.
It is difficult to see from the distance what this difference could
be. Since you also tried removing the ~/.scribus directory, it
cannot really be anything directly coming from scribus, because
scribus is the same then and now. Also, this first crash happens
inside xorg, so it might be an xorg bug.
Crash report when attempting to open an existing document:
EXC_BAD_ACCESS (0x0001)
KERN_PROTECTION_FAILURE (0x0002) at 0x0031fa88
Thread 0 Crashed:
0 art_rgb_fill_run_ + 12 (art_rgb.c:58)
1 art_rgb_svp_alpha_opaque_callback_ + 236 (art_rgb_svp.c:347)
2 art_svp_render_aa + 156 (icplusplus.c:28)
3 art_rgb_svp_alpha_ + 176 (art_rgb_svp.c:461)
4 ScPainter::drawVPath(_ArtVpath*, int, bool) + 1080 (rc4.c:138)
5 ScPainter::drawRect(double, double, double, double) + 316
(rc4.c:138)
6 ScribusView::drawContents(QPainter*, int, int, int, int) +
1296 (rc4.c:138)
7 QScrollView::drawContentsOffset(QPainter*, int, int, int,
int, int, int) + 152 (icplusplus.c:28)
8 QScrollView::viewportPaintEvent(QPaintEvent*) + 540
(icplusplus.c:28)
9 QScrollView::eventFilter(QObject*, QEvent*) + 824
(icplusplus.c:28)
(XDarwin remains open, xwindows apps seem to run normally)
This crash is inside scribus allright, so it could also be
worthwhile to file this on the scribus bug tracker, together with
the source of your document, and perhaps a complete crash log with
the list of loaded libraries.
Instead of further fishing in the dark, I'll just quote I don't
remember who: "If a DTP program crashes, in 99% of all cases the
reason is a bad font". So you could also empty your ~/.fonts
directory and scrutinize the contents of your ~/Library/Fonts
directory and see if this changes anything.
I rm'd the ~/.font-cache-1 file. Font Book.app found 3 damaged fonts,
which I removed. Scribus startup produced the same results as before.
I am concerned that the problem will require some serious repair. If
more was broken, my concern would be greater.
One thing I didn't mention. When using Scribus-aqua (before I dumped
it), I noticed some anomalies with scribus preferences. First, the
preference window seemed to grow in width, to the point that the
right edge was waaaaaay out there. Second, one of the preferences
(possibly to do with mapping keys to tasks, but my memory is very
fuzzy) had a long row of some weird combination of characters which
didn't appear do anything. I'm wondering if I had some kind of
"memory leak" which overwrote something. Speculation from ignorance.
Anyway, I thought I should at least send some response to your (much
appreciated) message and suggestions.
--
Martin
Stan
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
