Issue 17294 - Crash when clicking on links in the Help-system
Summary: Crash when clicking on links in the Help-system
Status: CLOSED DUPLICATE of issue 17109
Alias: None
Product: documentation
Classification: Unclassified
Component: Manuals (show other issues)
Version: OOo 1.1 RC
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: issues@documentation
QA Contact: issues@documentation
URL:
Keywords: crash, oooqa
Depends on:
Blocks:
 
Reported: 2003-07-23 09:24 UTC by korsi
Modified: 2008-05-17 23:22 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Crashlog (4.56 KB, text/plain)
2003-07-23 09:26 UTC, korsi 		no flags Details
Crashlog with libc6 2.3.2-1 on Debian Sid (i386) (4.64 KB, text/plain)
2003-07-30 11:36 UTC, korsi 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description korsi 2003-07-23 09:24:45 UTC 
Starting swriter and going directly to the help system «Help - Contents». 
The crash occures after click randomly number of times (less than 10) on some 
links in the Contents Navigator.
Comment 1 korsi 2003-07-23 09:26:54 UTC 
Created attachment 7964 [details]
Crashlog
Comment 2 laimis 2003-07-24 22:30:01 UTC 
Your crash dumps are very similar and the bug occurs on the same feature.

*** This issue has been marked as a duplicate of 17109 ***
Comment 3 dankegel 2003-07-26 05:44:06 UTC 
You wrote in the other issue that you're using glibc-2.3.1 on Debian.

There is a known problem in glibc-2.3.1 on debian 
that causes crashes.  Could you try updating to glibc-2.3.2?
Thanks!
Comment 4 korsi 2003-07-30 11:36:38 UTC 
Created attachment 8136 [details]
Crashlog with libc6 2.3.2-1 on Debian Sid (i386)
Comment 5 korsi 2003-07-30 11:38:10 UTC 
I have tried with libc6 2.3.2-1, and I got the same result.
Comment 6 ace_dent 2008-05-17 21:19:17 UTC 
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 7 ace_dent 2008-05-17 23:22:33 UTC 
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew