[Bug 278090] Re: konqueror crashes X (Saw signal 11. Server aborting. )

[B-ZaR]

Harald Sitter wrote:
> Are all packages up-to-date?
>   
As up-to-date as ubuntu intrepid repos are.
> What do you do when X crashes?
>   
Start konquror, sometimes seems to be related to pressing the right 
button anywhere in the konqueror window.
> What did you do before that (even unrelated to konqueror)?
>   
At the first time, I had Terminal and System Settings open, but I also 
tested with a freshly started xorg + KDE.
> file:///media/disk/var/log/gdm/:0.log.2
> Are you using a clean installation of Intrepid or an upgraded Hardy?
>   
Clean intrepid.
> Please attach /var/log/Xorg.0.log /var/log/Xorg.1.log /var/log/kdm.log /var/log/kdm.log.1 /home/$YOURUSERNAME/.xsession-errors
>   
I use gdm, so I don't have kdm logs. I'll attach a gdm log instead. 
Attached xorg log shows the crashing.

Okay... funny thing. I forgot to take the .xsession-errors, so I went 
back to my intrepid installation (I use 8.04 for production, 8.10 is 
just for beta testing for now) and was unable to reproduce the crash. I 
tried twice, and konqueror just worked normally. I reproduced this bug 
eight times before reporting it, but now it seems to be gone? Anyhow, I 
attached the xsession-errors generated when I /tried/ to crash it.

I had not updated any packages, nor changed any configurations. How 
konqueror didn't crash /that/ time is beyond me.
> ** Changed in: kdebase (Ubuntu)
>        Status: New => Incomplete
>
>

-- 
konqueror crashes X (Saw signal 11.  Server aborting. )
https://bugs.launchpad.net/bugs/278090
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.