Bug 55579

Summary:	kconsole crashes when resizing with a transparent background under MetaFrame for UNIX 1.1 Feature Release 1 (with patches)
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Russ LeBar <Russell.J.LeBar>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED FIXED
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Solaris
Latest Commit:		Version Fixed In:

Description Russ LeBar 2003-03-05 22:11:29 UTC

Version:            (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2.1 
OS:          Solaris

FYI, MetaFrame for UNIX uses its own xserver (i.e. *not* XSun). FYI, Kpager crashes on startup with a similar error message.


From the console:

ASSERT: "qstrcmp( locale, "en_US" ) == 0" in kernel/qapplication_x11.cpp (1968)
QFont::setPointSize: Point size <= 0 (-1)
kdeui (KPixmapIO): WARNING: Could not get shared memory segment.
konsole: WARNING: KDE detected X Error: BadShmSeg (invalid shared segment parameter) \x80
  Major opcode:  \x81


I compiled without debugging so this probably will not help, but here's the backtrace anyway:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
sol-thread active.
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP    1        ]
[New Thread 1 (LWP 1)]
[Switching to Thread 1 (LWP 1)]
0xfdf9f598 in _waitid () from /usr/lib/libc.so.1
#0  0xfdf9f598 in _waitid () from /usr/lib/libc.so.1
#1  0xfdf56838 in _waitpid () from /usr/lib/libc.so.1
#2  0xfde6ab00 in waitpid () from /usr/lib/libthread.so.1
#3  0xfde6b82c in __sighndlr () from /usr/lib/libthread.so.1
#4  <signal handler called>
#5  0xff33062c in memcpy ()
   from /usr/platform/SUNW,Sun-Fire-880/lib/libc_psr.so.1
#6  0xfee5f584 in _ZN9KPixmapIO17convertFromXImageEv ()
   from /usr/local/kde31/lib/libkdeui.so.4
#7  0xfee5eed4 in _ZN9KPixmapIO8getImageEPK7QPixmapiiii ()
   from /usr/local/kde31/lib/libkdeui.so.4
#8  0xfee5ebac in _ZN9KPixmapIO14convertToImageERK7QPixmap ()
   from /usr/local/kde31/lib/libkdeui.so.4
#9  0xfeef050c in _ZN11KRootPixmap16updateBackgroundEP13KSharedPixmap ()
   from /usr/local/kde31/lib/libkdeui.so.4
#10 0xfeeefefc in _ZN11KRootPixmap8slotDoneEb ()
   from /usr/local/kde31/lib/libkdeui.so.4
#11 0xfeef08dc in _ZN11KRootPixmap9qt_invokeEiP8QUObject ()
   from /usr/local/kde31/lib/libkdeui.so.4
#12 0xfe2713b8 in _ZN7QObject15activate_signalEP15QConnectionListP8QUObject ()
   from /usr/local/qt-x11-free-3.1.1/lib/libqt-mt.so.3
#13 0xfe27174c in _ZN7QObject20activate_signal_boolEib ()
   from /usr/local/qt-x11-free-3.1.1/lib/libqt-mt.so.3
#14 0xfedf5788 in _ZN13KSharedPixmap8x11EventEP7_XEvent ()
   from /usr/local/kde31/lib/libkdeui.so.4
#15 0xfe1b853c in _ZN12QApplication15x11ProcessEventEP7_XEvent ()
   from /usr/local/qt-x11-free-3.1.1/lib/libqt-mt.so.3
#16 0xfe1ce618 in _ZN10QEventLoop13processEventsEj ()
   from /usr/local/qt-x11-free-3.1.1/lib/libqt-mt.so.3
#17 0xfe229a24 in _ZN10QEventLoop9enterLoopEv ()
   from /usr/local/qt-x11-free-3.1.1/lib/libqt-mt.so.3
#18 0xfe2298f4 in _ZN10QEventLoop4execEv ()
   from /usr/local/qt-x11-free-3.1.1/lib/libqt-mt.so.3
#19 0xfe21630c in _ZN12QApplication4execEv ()
   from /usr/local/qt-x11-free-3.1.1/lib/libqt-mt.so.3
#20 0xff2b6a34 in main () from /usr/local/kde31/lib/konsole.so

Comment 1 Karl Vogel 2003-03-06 17:21:50 UTC

I believe this is fixed in the CVS HEAD branch. This was caused by a bug in
kdelibs' KPixmapIO function not properly checking the shared memory function
returns.

see Bug #42441

Comment 2 Stephan Binner 2003-03-06 20:47:16 UTC

Was it backported to KDE_3_1_BRANCH or not?

Comment 3 Karl Vogel 2003-03-07 09:05:53 UTC

Yups:
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/kdeui/kpixmapio.cpp.diff?r1=1.23&r2=1.23.4.1&only_with_tag=KDE_3_1_BRANCH

Revision 1.23.4.1 / (download) - annotate - [select for diffs], Fri Feb 14
08:47:54 2003 UTC (3 weeks ago) by lunakl
Branch: KDE_3_1_BRANCH
Changes since 1.23: +50 -31 lines
Diff to previous 1.23 (colored)

Backport fix for #42441 .

Comment 4 Stephan Kulow 2003-03-10 20:54:16 UTC

with Lubos's fix it definitly shouldn't crash anymore and with my kpixmapio 
fixes in HEAD it shouldn't even give the error (but that's not backported 
as it's suboptimal - Lubos is promising a cleaner version in Qt)