kicker segfaults

Bug #16528 reported by Gurney
10
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Medium
Jonathan Riddell

Bug Description

When running a script in a terminal session of octave, kicker segfaults when a number of gnuplot windows are
closed. In my case it happens when at least 4 windows are close simultaneously using the octave command
'close all'. Note that this does not always happen, if it doesn't it mostly is on the first one or two runs.
The shortest octave scipt that enables me to produce this effect is:

<start crash.m>
figure(1);
plot(1);
figure(2);
plot(1);
figure(3);
plot(1);
figure(4);
plot(1);
close all;
<end crash.m>

I am using the Ubuntu Hoary Hedgehog release. All packages are installed using either dselect or apt-get.
Packages concerned:
* gnuplot-nox 4.0.0-2
* gnuplot-x11 4.0.0-2
* kicker 3.4.0-0ubuntu
* konsole 3.4.0-0ubuntu
* octave 2.1.64-1
* octave2.1 2.1.64-1

Here's the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1231575040 (LWP 10755)]
(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)
(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)
[KCrash handler]
#4 0xb7833d7f in KWin::WindowInfo::valid () from /usr/lib/libkdecore.so.4
#5 0xb65bfc90 in Task::isIconified () from /usr/lib/libtaskmanager.so.1
#6 0xb65d60be in TaskContainer::drawButton () from /usr/lib/libtaskbar.so.1
#7 0xb729fffc in QButton::paintEvent () from /usr/lib/libqt-mt.so.3
#8 0xb7247910 in QWidget::event () from /usr/lib/libqt-mt.so.3
#9 0xb71bc370 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#10 0xb71bb9d4 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#11 0xb77c4960 in KApplication::notify () from /usr/lib/libkdecore.so.4
#12 0xb7188191 in QWidget::repaint () from /usr/lib/libqt-mt.so.3
#13 0xb7248882 in QWidget::repaint () from /usr/lib/libqt-mt.so.3
#14 0xb7157e4e in QETWidget::translateConfigEvent ()
   from /usr/lib/libqt-mt.so.3
#15 0xb715389a in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#16 0xb7168ec2 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#17 0xb71cd74c in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#18 0xb71cd60e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#19 0xb71bc57b in QApplication::exec () from /usr/lib/libqt-mt.so.3
#20 0xb7f66872 in kdemain () from /usr/lib/libkdeinit_kicker.so
#21 0x080484bf in ?? ()
#22 0x00000001 in ?? ()
#23 0xbffffa94 in ?? ()
#24 0xbffffa68 in ?? ()
#25 0xb7d188c8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#26 0xb7d188c8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#27 0x08048401 in ?? ()

Revision history for this message
Mark Histed (histed237) wrote :

This happens to me when using Matlab.
If I close several windows using 'close all', kicker segfaults and doesn't
automatically get restarted.
I'm also using Hoary and the Kubuntu packages in Hoary.

(Rob, thanks for the nice testcase!)

I see the same trace as above, and many repetitions of the below message are
sent to stdout/stderr:

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20
  Minor opcode: 0
  Resource id: 0x3800a2d

Revision history for this message
Rocco Stanzione (trappist) wrote :

This sounds like a duplicate of a bug I can't find right now that was fixed, where clicking the "show desktop" button would crash kicker. Since this is a year old with no more reports, I'm assuming fixedness. Please feel free to reopen if it's not fixed.

Changed in kdebase:
status: Unconfirmed → Fix Committed
Revision history for this message
Carthik Sharma (carthik) wrote :

Changing to Fix Released since I think that the intention when the status was set to Fix Committed.

Please feel free to reopen this bug if it still exists.

Changed in kdebase:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.