Bug 168150 - kget crashes if an item is extended when deleted or the info widget stays forever in the list
Summary: kget crashes if an item is extended when deleted or the info widget stays for...
Status: RESOLVED FIXED
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-02 22:05 UTC by George Kiagiadakis
Modified: 2008-09-14 14:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot that shows the extender widget after deleting both downloads (46.84 KB, image/png)
2008-08-02 22:07 UTC, George Kiagiadakis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description George Kiagiadakis 2008-08-02 22:05:23 UTC
Version:           2.1.0 (using KDE 4.1.0)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc version 4.3.1 (Debian 4.3.1-2) 
OS:                Linux

Steps to reproduce (for the crash):
1) make sure you have only *one* download in the list.
2) extend the download in the list to show information
3) delete the download
4) that results in: ASSERT: "extenderIndices.value(extender).isValid()" in file /tmp/buildd/kde4libs-4.1.0/kdeui/itemviews/kextendableitemdelegate.cpp, line 128

Steps to reproduce (to make the info widget stay forever in the listview):
1) make sure you have *two* downloads in the list.
2) extend the second download
3) delete both downloads (Downloads -> delete all finished)
4) the extended info widget of the second download is still there (I'll attach a screenshot).

These may actually be two different bugs, but I think they are too much related, that's why I am reporting them in one bug report.
Comment 1 George Kiagiadakis 2008-08-02 22:07:24 UTC
Created attachment 26582 [details]
screenshot that shows the extender widget after deleting both downloads
Comment 2 Urs Wolfer 2008-08-02 23:41:19 UTC
The crash (assert) has already been fixed (not sure why it is not for your, I thought it went into 4.1.0...)
We will take a look at the second issue.
Comment 3 Urs Wolfer 2008-09-14 14:47:06 UTC
These bugs should be fixed at least in trunk.