Issue 2614 - Crash on startup if KDE panel is on left side of display
Summary: Crash on startup if KDE panel is on left side of display
Status: CLOSED DUPLICATE of issue 2575
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: Mac Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: philipp.lohmann
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-21 12:37 UTC by Unknown
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

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

Attachments
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 Unknown 2001-12-21 12:37:17 UTC 
In setup, will print "glibc version: 2.2.1" and exit. Launching soffice 
will cause immediate segmentation fault. Both occur if using KDE and 
the panel (kicker) is located on the left side of the display. 

Moving the panel anywhere else resolves the problem. Unfortunately, the 
lack of diagnostic messages makes discovering this workaround difficult. 
The problem is likely not platform specific. A message in the users 
forum from Matthias Weiss, using x86 linux, complained of (possibly) 
the same problem. 

No errors logged in .xsession-errors, /var/log/XFree86.0.log, or 
/var/log/messages

Setup: Using XFree86 4.1.0, yellowdog linux 2.1, kernel 2.4.10
Comment 1 Olaf Felka 2001-12-21 13:00:46 UTC 
I know that we've had an inhouse task for this.  The fix hasn't reached the 641c?
Comment 2 philipp.lohmann 2001-12-21 13:53:53 UTC 
should be fixed in OO641C


*** This issue has been marked as a duplicate of 2575 ***
Comment 3 michael.bemmer 2003-03-11 17:28:22 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-11 17:57:03 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.