Issue 2952 - KDE kicker causes setup segmentation violation
Summary: KDE kicker causes setup segmentation violation
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
: 2963 3010 3162 3300 3359 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-01-26 22:21 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

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-01-26 22:21:07 UTC
Hi,

KDE kicker (panel) causes the "setup" program to crash with segmentation
violation under certain circumstances: When kicker panel is in
its default position (bottom) or on top, things work fine and the
setup/installation window starts. 
When the panel has been positioned on the left or right side (vertical
arrangement), setup crashes and the window does not come up (see 
the last part of strace below).

I am using Linux Debian "sid" in a fairly up to date version,
1900x1200 screen, xserver-xfree86 4.1.0-13, kdebase 2.2.2-13
This problem exists in older versions of OpenOffice as well,
and also in the Staroffice Beta.

Cheers, Stefan.

readv(8, [{"-100-100-p-86-iso8859-1:-adobe-t"..., 71860}, {"", 0}], 2) = 65280
readv(8, [{"iso8859-7:-monotype-courier new-"..., 6580}, {"", 0}], 2) = 6580
old_mmap(NULL, 172032, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
  0x418d1000
brk(0x80bd000)                          = 0x80bd000
brk(0x80be000)                          = 0x80be000
munmap(0x4187f000, 335872)              = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS,
  -1, 0) = 0x4187f000
  old_mmap(NULL, 4096, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x41880000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x41881000
open("/etc/mtab", O_RDONLY)             = 10
fstat64(10, {st_mode=S_IFREG|0644, st_size=481, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
x41882000
read(10, "/dev/hda1 / ext2 rw,errors=remou"..., 4096) = 481
close(10)                               = 0
munmap(0x41882000, 4096)                = 0
open("/proc/meminfo", O_RDONLY)         = 10
fstat64(10, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
x41882000
read(10, "        total:    used:    free:"..., 4096) = 522
close(10)                               = 0
munmap(0x41882000, 4096)                = 0
old_mmap(NULL, 172032, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x41882000
munmap(0x41882000, 172032)              = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
Comment 1 Olaf Felka 2002-01-28 11:17:21 UTC
Hi Stefan,
could you please tell us which OOo version you are using? We couldn't 
reproduce this with OOo 641.
We know this issue and it should be fixed in OOo641.
Comment 2 Olaf Felka 2002-01-29 13:24:21 UTC
Please use issuezilla for answers!!!
I'm sorry, this fix hasn't reached OOo641c. 
Next OOo release should do better.
Comment 3 Olaf Felka 2002-02-01 10:51:21 UTC
*** Issue 2963 has been marked as a duplicate of this issue. ***
Comment 4 Olaf Felka 2002-02-05 16:13:37 UTC
*** Issue 3010 has been marked as a duplicate of this issue. ***
Comment 5 Olaf Felka 2002-02-21 08:48:00 UTC
*** Issue 3162 has been marked as a duplicate of this issue. ***
Comment 6 Olaf Felka 2002-03-04 08:39:17 UTC
*** Issue 3300 has been marked as a duplicate of this issue. ***
Comment 7 Unknown 2002-03-04 15:29:51 UTC
Will wait for next release.
Comment 8 Olaf Felka 2002-03-06 08:20:48 UTC
*** Issue 3359 has been marked as a duplicate of this issue. ***