#1 Popper 1.0 with KDE 3.0.0 Segfaults

[Anonymous]

Every time someone sends me a message and I click
reply, popper segfaults. If I close the message, and
send a new message it works. Has anyone else noticed
this?

Here is a backtrace:
0x41366389 in wait4 () from /lib/libc.so.6
#0 0x41366389 in wait4 () from /lib/libc.so.6
#1 0x413de058 in __check_rhosts_file () from
/lib/libc.so.6
#2 0x41296263 in waitpid () from
/lib/libpthread.so.0
#3 0x40642e4f in KCrash::defaultCrashHandler ()
from /opt/kde/lib/libkdecore.so.4
#4 0x41293d94 in pthread_kill () from
/lib/libpthread.so.0
#5 0x412ef908 in sigaction () from /lib/libc.so.6
#6 0x8054a77 in Popper::qt_invoke ()
#7 0x40a86a2a in QObject::activate_signal ()
from /usr/lib/qt/lib/libqt-mt.so.3
#8 0x40a86da4 in QObject::activate_signal ()
from /usr/lib/qt/lib/libqt-mt.so.3
#9 0x8054e04 in PopupImpl::reply ()
#10 0x804ef04 in PopupImpl::gotReply ()
#11 0x8053680 in Popup::qt_invoke ()
#12 0x8054e84 in PopupImpl::qt_invoke ()
#13 0x40a86a2a in QObject::activate_signal ()
from /usr/lib/qt/lib/libqt-mt.so.3
#14 0x40a86924 in QObject::activate_signal ()
from /usr/lib/qt/lib/libqt-mt.so.3
#15 0x40e581f0 in QButton::clicked () from
/usr/lib/qt/lib/libqt-mt.so.3
#16 0x40b505a4 in QButton::mouseReleaseEvent ()
from /usr/lib/qt/lib/libqt-mt.so.3
#17 0x40ac5341 in QWidget::event () from
/usr/lib/qt/lib/libqt-mt.so.3
#18 0x40a07e9e in QApplication::internalNotify ()
from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x40a07707 in QApplication::notify () from
/usr/lib/qt/lib/libqt-mt.so.3
#20 0x405a5bf4 in KApplication::notify () from
/opt/kde/lib/libkdecore.so.4
#21 0x409a3eca in QETWidget::translateMouseEvent ()
from /usr/lib/qt/lib/libqt-mt.so.3
#22 0x409a110f in QApplication::x11ProcessEvent ()
from /usr/lib/qt/lib/libqt-mt.so.3
#23 0x4099fc6e in QApplication::processNextEvent ()
from /usr/lib/qt/lib/libqt-mt.so.3
#24 0x40a0999f in QApplication::enter_loop ()
from /usr/lib/qt/lib/libqt-mt.so.3
#25 0x4099fbdb in QApplication::exec () from
/usr/lib/qt/lib/libqt-mt.so.3
#26 0x8051f1d in main ()
#27 0x412df74f in __libc_start_main () from
/lib/libc.so.6

[Bernd Hoffmann]

Logged In: YES
user_id=179639

Hi,

same problem here. Sending/receiving works, but as soon as I hit the reply
button the whole app segfaults.

Cheers,
Bernd

[Giovanni Beltrame]

Logged In: YES
user_id=492082

I fixed this bug. It is due to a call to che method
KComboBox.lineEdit() in , which works only if the combo box is
editable. Obviously it was not. In this case lineEdit() returns 0,
but popper makes no check and calls the setText() method on it.
The result is a nice segfault.
I can commit the fix in the cvs tree, I don't know if I need some
kind of authorization.

P.s. The reply was not completely implemented, I also added
some string manipulation to correctly set the destination of the
replyed message.

[Giovanni Beltrame]

Logged In: YES
user_id=492082

I just forgot to write file and method!
popper.cpp:101 in Popper::newMessage()