Apache OpenOffice (AOO) Bugzilla – Issue 16633
Crash reporter has to used system installed GTK libraries
Last modified: 2003-07-17 09:44:17 UTC
Installation sets released by Martin Hollmichel on 20030710 1) 6d04a063bcf81064da6a9f90c1cc664c OOo_1.1rc_Win32Intel_install.zip -- On Windows98SE -- Incorrect display of some parts 2) aefb05b99d7a03eb19dd11b59e6ec55e OOo_1.1rc_LinuxIntel_install.tar.gz -- On RedHat8 -- Pops up but Ugly 3) aefb05b99d7a03eb19dd11b59e6ec55e OOo_1.1rc_LinuxIntel_install.tar.gz -- On SuSE8.1 -- Doesn't pop up Installation sets released by Sander Vesik on 20030704 4) c17d833437aea745728c19b8655c5878 OOo_1.1rc_04072003_Win32Intel_install_ja.zip -- On Windows98SE -- Doesn't pop up 5) 0bbb49686b85755c9c7bce5618b01fcc OOo_1.1rc_04072003_LinuxIntel_install_ja.tar.gz -- On RedHat8 -- Fine, beautiful 6) 0bbb49686b85755c9c7bce5618b01fcc OOo_1.1rc_04072003_LinuxIntel_install_ja.tar.gz -- On SuSE8.1 -- Ok, fine Please take a look at: http://www.transwift.net/ooo/crash_reporter.html
ATR->HRO: Hi Hennes, please have a look on this issue, because JA is on vacation.
Sanders build did not show the crash reporter on Windows 98 SE because the dbghelp.dll was not installed I guess. @khirano: The ugly strings in some parts may be a font problem. It's a japanese Win 98 SE isn't it ? Can you send me a copy of your win.ini file ? That would help me to reproduce that. The different behaviour of the different Linux builds on the same systems looks to me as a mixup of a translation issue and different linkage of gtk. I've to investigate what the difference between those build were. Maybe you can be so kind to let me know what 'ldd crash_report.bin' shows?
Also seeing problem on Suse 8.1, crash reporter does not launch when user issues kill -SEGV <soffice_process_no>. Marking issue as New
Hi, Yes, I am using Japanese Windows98SE and finding that the dbghelp.dll is missing from /OpenOffice.org1.1/program/ of Sander's build. My win.ini file will be attached here. Also I will create attachments: 'ldd crash_report.bin' of Sander's and Martin's on SuSE8.1. Thanks
Created attachment 7528 [details] Win.ini file in UTF-8 containing some Japanese texts
Created attachment 7529 [details] Results of 'ldd crash_report.bin' of the two builds
Created attachment 7543 [details] "ldd crash_report.bin" results on rh8. above id=7529 was on SuSE8.1
@pl: Please take over. Crashreporter only comes up when it was dynamically linked against GTK on that Suse 8.1 system. When GTK is already installed on the system use a dynamically linked crash reporter. @khirano: Ugly looking on Suse 8.1 and Redhat because you installed an english Office on a japanese locale-> No fix. Some controls show garbage in Windows 98 crash reporter. This is a font issue only on CJK versions of Windows 9x. Please submit a separate issue for this.
I tested the following builds: ----------------------- 1) Build using 28eb61c5daeabb2f489f9793a5cbb97d OOo_1.1rc_source.tar.gz with Vine2.1.5, kernel2.4.21, glibc2.1.3, gcc3.3, jdk1.4.1, gtk+2 etc. (rc1) 2) Build using cws_srx645_ooo11rc2 with Suse8.1, kernel2.4.19, glibc2.2.5, gcc3.3, jdk1.4.1, gtk+2 etc. (rc2) 3) b6f4aa6da7f29f0ae6516b494c47d762 OOo_1.1rc_030710_LinuxIntel_install_ja.tar.gz (rc_ja) Summary: --------- 1) rc1 - On SuSE8.1: ErrorReport doesn't come up when soffice crashes. - On RedHat8: ErrorReport doens't come up when soffice crashes. 2) rc2 - On SuSE8.1: ErrorReport comes up when soffice crashes and looks fine. - On RedHat8: ErrorReport comes up when soffice crashes and looks beautiful. 3) rc_ja - On SuSE8.1: ErrorReport doesn't come up when soffice crashes. - On RedHat8: ErrorReporr comes up when soffice crashes but looks ugly. Please refer to: http://www.transwift.net/ooo/11rc_ErrorReport.html
what a mess ...
fixed in CWS setupicon
Hi all, Sorry, was a little misunderstanding. I think this is a developer task and PL agreed. I'll test the little rest (crashreporter still working eg.).
Reassigning
.
verified in CWS setupicon
merged in m13s1, closing