[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Bug#18780: KDE crashes - more info
From: Sonam Chauhan <sonamc () ce ! com ! au>
Date: 2001-01-24 19:08:39
[Download RAW message or body]
I set core size to unlimited, but I could not get KDE/X to dump a core
file despite several more crashes. The bug was not affected by settings
for screensaver, powermanagement or screen locking... but always caused a
crash after 20-30 mins of inactivity.
In the end, I tired of the crashes, so I upgraded X to 4.0.2 and the problems
seem to have stopped.
Thank you all for your help. KDE 2.0.1 is otherwise wonderful!
Regards,
Sonam
The problems
Leon Widdershoven wrote:
>
> Hi,
>
> you could look at your limits. The bash command ulimit -c displays
> the max core size, the command ulimit -c <size> sets it to the size.
>
> Leon
>
> Sonam Chauhan wrote:
> >
> > > This one seems to be from kicker after clicking on the calendar in the panel.
> > > I don't think that it is related if you say that you got the crash after some
> > > minutes of inactivity.
> >
> > Hi Waldo: KDE just crashed again - again this was after about 30 mins of inactivity.
> > Unfortunately it didn't generate a core file so I couldn't get a backtrace. :(
> > All I got is the output below from the terminal window.
> > Could you suggest how I could force KDE/X to generate a core file?
> >
> > Regards,
> > Sonam
> >
> > --SNIP--
> > ..
> > Major opcode: 14
> > KLauncher doing clientStarted(`konsole')
> > kdecore (KURL): KURL couldn't parse URL "lo devsvr1"
> > kdecore (KURL): KURL couldn't parse URL "lo"
> > KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> > Major opcode: 14
> > KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> > Major opcode: 14
> > KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> > Major opcode: 14
> >
> > nohup: appending output to `nohup.out'
> > KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> > Major opcode: 14
> >
> > Fatal server error:
> > Caught signal 11. Server aborting
> >
> >
> > When reporting a problem related to a server crash, please send
> > the full server output, not just the last messages.
> > This can be found in the log file "/var/log/XFree86.0.log".
> > Please reports problems to xfree86@xfree86.org.
> >
> > [drm:mga_release] *ERROR* Process 13019 dead, freeing lock for context 6
> >
> > ...
> > --SNIP--
> >
> > Regards,
> > Sonam
> >
> > >> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>
> --
> ==========================================================
> Undefined behaviour: It works in the debug phase, it works
> during testing, and it blows up in your customers' face.
> Inspired by: Scott Meyers, Effective C++
--
Electronic Commerce
Corporate Express Australia Ltd.
Phone: +61-2-9335-0725 Fax: +61-2-9335-0753
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic