Bug 42441

One other thing:
This problem only seems to occur when I am using a transparent background
schema for Konsole.


Thanks
Mike 

---
Michael E. Beckish                       Tel: (570)803-0535 x1702
mike@sea-incorporated.com                Fax: (570)803-0536
Software Engineering Associates Inc.    http://www.sea-incorporated.com/

On Friday 10 May 2002 08:50 am Michael E. Beckish wrote:
> Package: konsole
> Version: KDE 3.0.0=20
> Severity: normal
> Installed from:    FreeBSD Ports
> Compiler:          Not Specified
> OS:                FreeBSD
> OS/Compiler notes: Not Specified

> When I log into KDE I can open maybe 2 or 3 Konsoles.  After that every
> time I try to open a new Konsole it crashes.

> kdeui (KPixmapIO): WARNING: Could not get shared memory segment.
> KCrash: crashing.... crashRecursionCounter =3D 2
> KCrash: Application Name =3D konsole path =3D <unknown> pid =3D 15104

> One other thing:
> This problem only seems to occur when I am using a transparent background
> schema for Konsole.

It seems you are running out of shared memory and I suspect this to be a=20
freebsd specific problem somehow. Can anyone reproduce this on freebsd?=20

Cheers
Waldo
--=20
bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com

The weird thing is if it is a lack of shared memory it doesn't seem to
be affecting any other applications nor does it affect Konsole when not
using transparent backgrounds.
Plus I have hundreds of megs of free swap space.

Another note: this problem didn't appear until I upgraded to KDE3.

---
Michael E. Beckish                       Tel: (570)803-0535 x1702
mike@sea-incorporated.com                Fax: (570)803-0536
Software Engineering Associates Inc.    http://www.sea-incorporated.com/

On Fri 10 May 2002 Waldo Bastian wrote:

> On Friday 10 May 2002 08:50 am Michael E. Beckish wrote:
> > Package: konsole
> > Version: KDE 3.0.0 
> > Severity: normal
> > Installed from:    FreeBSD Ports
> > Compiler:          Not Specified
> > OS:                FreeBSD
> > OS/Compiler notes: Not Specified
> 
> > When I log into KDE I can open maybe 2 or 3 Konsoles.  After that every
> > time I try to open a new Konsole it crashes.
> 
> > kdeui (KPixmapIO): WARNING: Could not get shared memory segment.
> > KCrash: crashing.... crashRecursionCounter = 2
> > KCrash: Application Name = konsole path = <unknown> pid = 15104
> 
> > One other thing:
> > This problem only seems to occur when I am using a transparent background
> > schema for Konsole.
> 
> It seems you are running out of shared memory and I suspect this to be a 
> freebsd specific problem somehow. Can anyone reproduce this on freebsd? 
> 
> Cheers
> Waldo
> -- 
> bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com
> 
>

On Fri May 10 2002 at 01:21:03PM -0700 Waldo Bastian wrote:
> It seems you are running out of shared memory and I suspect this to be a 
> freebsd specific problem somehow. Can anyone reproduce this on freebsd? 

Yes.  100% reproducible here.  I originally thought his problem
was not sufficiently allocating shm segments in his kernel config
which can cause this but it looks like this might be a bug in
KDE wrt FreeBSD.  Unfortunately my code was compiled without
debugging so I can't look further [this coupled with my lack of
use of Konsole.. maybe someday I'll switch but aterm has my heart
for now :)].

regards
-- 
wca

Waldo Bastian wrote:

> On Friday 10 May 2002 08:50 am Michael E. Beckish wrote:
> 
>>Package: konsole
>>Version: KDE 3.0.0 
>>Severity: normal
>>Installed from:    FreeBSD Ports
>>Compiler:          Not Specified
>>OS:                FreeBSD
>>OS/Compiler notes: Not Specified
>>
> 
>>When I log into KDE I can open maybe 2 or 3 Konsoles.  After that every
>>time I try to open a new Konsole it crashes.
>>
> 
>>kdeui (KPixmapIO): WARNING: Could not get shared memory segment.
>>KCrash: crashing.... crashRecursionCounter = 2
>>KCrash: Application Name = konsole path = <unknown> pid = 15104
>>
> 
>>One other thing:
>>This problem only seems to occur when I am using a transparent background
>>schema for Konsole.
>>
> 
> It seems you are running out of shared memory and I suspect this to be a 
> freebsd specific problem somehow. Can anyone reproduce this on freebsd? 
> 
> Cheers
> Waldo
> 

I just opened 15 consoles on KDE 3.0 on FreeBSD 4.5 on my laptop. No
problem.

-Jim

Same here no probs.  Dell Inspiron 7500 laptop 
18 konsoles w tranparent shade to black ~80%
background image is Default_Blue.jpg

"uname -mrs" gives "FreeBSD 4.5-RELEASE i386"

Install Ports:
kde-3.0_1           
kdeaddons-3.0_1     
kdeartwork-3.0      
kdebase-3.0_1       
kdegames-3.0_1      
kdegraphics-3.0_2   
kdelibs-3.0_1       
kdemultimedia-3.0_1 
kdenetwork-3.0_1    
kdepim-3.0_1        
kdesdk-3.0_1        
kdetoys-3.0_1       
kdeutils-3.0        
koffice-1.1.11     

On Fri May 10 2002 at 05:04:49PM -0400 Jim Durham wrote:
> 
> I just opened 15 consoles on KDE 3.0 on FreeBSD 4.5 on my laptop. No
> problem.

-- 
David Huttleston Jr
7941 Tree Lane Suite 200
Madison WI 53717

On Friday 10 May 2002 16:40 Will Andrews wrote:
> On Fri May 10 2002 at 01:21:03PM -0700 Waldo Bastian wrote:
> > It seems you are running out of shared memory and I suspect this to be a
> > freebsd specific problem somehow. Can anyone reproduce this on freebsd?
>
> Yes.  100% reproducible here.  I originally thought his problem
> was not sufficiently allocating shm segments in his kernel config
> which can cause this but it looks like this might be a bug in
> KDE wrt FreeBSD.  Unfortunately my code was compiled without
> debugging so I can't look further [this coupled with my lack of
> use of Konsole.. maybe someday I'll switch but aterm has my heart
> for now :)].

Will I use a konsole with transparent background and I just opened up 10 =
of=20
them w/o a  problem. I do not have any special settings in /etc/sysctl.conf=
=20
nor do I have any special settings in my kernel config file.

I also have a hue-shift blended jpeg on top of a horizontal gradient=20
background. At the moment I have kmail this composer xmms and a konq=20
window open as well.

--=20
AlanE

Bug #15463 seems to be the same problem (transparent konsole "Could not
get shared memory segment" error) except it is on Solaris instead of
freeBSD.

Mike

*** Bug 48200 has been marked as a duplicate of this bug. ***

is anyone still seing this, possibly with newer version? :)

I

I'm still seeing this with 3.1 final on sparc/solaris8.  
Any time I set the schema to be transparent, it crashes.  
 

This behavior is dependent upon how much RAM the box has.  
I have one sparc/solaris8 box with 256 MB RAM, and transparencies 
core dump every time.  I've another sparc/solaris8 box with identical  
kde 3.1 binaries, but with 512MB RAM.  transparencies work fine with 512  
MB RAM.  

This is a problem in kdelibs/kdeui/kpixmap.cpp. 
 
void KPixmapIO::initXImage(int w, int h) 
{ 
    if (d->ximage && (w == d->ximage->width) && (h == d->ximage->height)) 
        return; 
 
    createXImage(w, h); 
    int size = d->ximage->bytes_per_line * d->ximage->height; 
    if (size > d->shmsize) 
        createShmSegment(size); 
    d->ximage->data = d->shminfo->shmaddr; 
    return; 
} 
 
If createShmSegment() is unable attach the shm segment, then it sets m_bShm to false. In this 
case d->shminfo->shmaddr is not valid! So there needs to be a test written for this case. 
 
 
Konsole uses KRootPixmap::updateBackground() for the transparant background. So this is 
where you are experiencing the crash. 
 

Should be fixed now.