By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 210 - Programs crash when deleting all text in filter fields
Summary: Programs crash when deleting all text in filter fields
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.11 [Trinity]
Hardware: i386 All
: P2 critical
Assignee: Timothy Pearson
URL:
: 373 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-31 15:46 CDT by nmrugg
Modified: 2012-10-19 15:13 CDT (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String: 3.5.11
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description nmrugg 2010-05-31 15:46:09 CDT 
Every time I delete all of the text from a filter input field (like the one in Konqueror on the upper right) the program crashes.

This happens whenever I use backspace or the delete key to delete all of the text.  Once the last character is deleted, the program crashes.

It does crash, however, when clicking the Clear Filter Field button or when selecting all of the text and cutting it.


Below is the backtrace:

[Thread debugging using libthread_db enabled]
[KCrash handler]
#5  0x01ab2274 in KIconViewSearchLine::updateSearch(QString const&) ()
   from /opt/kde3/lib/libkdeui.so.4
#6  0x01a18a22 in KIconViewSearchLine::activateSearch() ()
   from /opt/kde3/lib/libkdeui.so.4
#7  0x01ae93d0 in KIconViewSearchLine::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/libkdeui.so.4
#8  0x0146a19a in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/libqt-mt.so.3
#9  0x017c8d0e in QSignal::signal(QVariant const&) ()
   from /usr/lib/libqt-mt.so.3
#10 0x01486b27 in QSignal::activate() () from /usr/lib/libqt-mt.so.3
#11 0x0148e2e3 in QSingleShotTimer::event(QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#12 0x014053d7 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#13 0x0140634b in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#14 0x03fdf4fb in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#15 0x013fae42 in QEventLoop::activateTimers() () from /usr/lib/libqt-mt.so.3
#16 0x013b01b6 in QEventLoop::processEvents(unsigned int) ()
   from /usr/lib/libqt-mt.so.3
#17 0x0141e3b0 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#18 0x0141e256 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#19 0x01405a2f in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#20 0x006a0bcc in kdemain () from /opt/kde3/lib/libkdeinit_konqueror.so
#21 0x0804852b in ?? ()
#22 0x0016bbc6 in __libc_start_main () from /lib/libc.so.6
#23 0x08048471 in ?? ()
Comment 1 Timothy Pearson 2010-05-31 15:53:03 CDT 
This should have been fixed in Lucid.  Can you upgrade and verify that the problem is indeed fixed?

As an aside, this bug has been present in Kubuntu since Hardy...
Comment 2 nmrugg 2010-06-01 10:35:35 CDT 
Actually, I am using 10.04 Lucid.  I accidentally chose the wrong version.
Comment 3 Markus Raab 2011-07-06 14:02:26 CDT 
I have exactly the same problem on one Computer, but not on the other one (both Debian Squeeze with 3.5.12). So it seems dependend on a specific circumstance which is not the version or OS.

Here the backtrace from the computer where the crash occurs (always and reproducible)
[Thread debugging using libthread_db enabled]
[KCrash handler]
#6  0xb65bda54 in KIconViewSearchLine::updateSearch(QString const&) ()
   from /opt/trinity/lib/libkdeui.so.4
#7  0xb6522312 in KIconViewSearchLine::activateSearch() ()
   from /opt/trinity/lib/libkdeui.so.4
#8  0xb65f0b60 in KIconViewSearchLine::qt_invoke(int, QUObject*) ()
   from /opt/trinity/lib/libkdeui.so.4
#9  0xb715f9aa in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/libqt-mt.so.3
#10 0xb74be22e in QSignal::signal(QVariant const&) ()
   from /usr/lib/libqt-mt.so.3
#11 0xb717c8a7 in QSignal::activate() () from /usr/lib/libqt-mt.so.3
#12 0xb7184043 in QSingleShotTimer::event(QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#13 0xb70fb167 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#14 0xb70fc14b in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#15 0xb69aa89b in KApplication::notify(QObject*, QEvent*) ()
   from /opt/trinity/lib/libkdecore.so.4
#16 0xb70f0cb2 in QEventLoop::activateTimers() () from /usr/lib/libqt-mt.so.3
#17 0xb70a60a3 in QEventLoop::processEvents(unsigned int) ()
   from /usr/lib/libqt-mt.so.3
#18 0xb7114130 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#19 0xb7113fd6 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#20 0xb70fb7bf in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#21 0xb5f143ac in kdemain () from /opt/trinity/lib/libkdeinit_konqueror.so
#22 0xb78d04f4 in kdeinitmain () from /opt/trinity/lib/kde3/konqueror.so
#23 0x0804f08c in ?? ()
#24 0x0804fb95 in ?? ()
#25 0x08050282 in ?? ()
#26 0x08050c18 in ?? ()
#27 0xb7609c76 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#28 0x0804b961 in ?? ()
Comment 4 Markus Raab 2011-07-06 14:04:51 CDT 
*** Bug 373 has been marked as a duplicate of this bug. ***
Comment 5 Markus Raab 2011-07-10 02:47:01 CDT 
I found out that the crash only occurs when the icon view is selected. In list view the problem does not occur.

Does someone know which debug packages I have to install for more information?
Comment 6 Timothy Pearson 2011-07-10 13:51:33 CDT 
(In reply to comment #5)
> I found out that the crash only occurs when the icon view is selected. In list
> view the problem does not occur.
> 
> Does someone know which debug packages I have to install for more information?

Yes.  kdebase-kde3-dbg and kdeaddons-kde3-dbg should give you a valid backtrace.  That being said, this particular crash is due to an original Qt3 design flaw, and will need to be fixed in our new upstream Qt3 sources before it can be fixed in Trinity.  Therefore, this will probably have to wait for 3.5.13 to be released along with Qt 3.3.9.
Comment 7 Timothy Pearson 2012-06-12 14:43:03 CDT 
This was fixed some time ago, in the recommended manner via a Qt3 addition, in GIT hashes 660a32cf and 5c8a387b (and possibly a few others).