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 358 - Amarok 1.4 crashes when the Collection tab is clicked
Summary: Amarok 1.4 crashes when the Collection tab is clicked
Status: RESOLVED WORKSFORME
Alias: None
Product: TDE
Classification: Unclassified
Component: tdemultimedia (show other bugs)
Version: 3.5.12 [Trinity]
Hardware: amd64 Kubuntu Maverick
: P5 critical
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2010-10-12 12:44 CDT by bkadoctaj
Modified: 2013-05-04 12:56 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
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 bkadoctaj 2010-10-12 12:44:49 CDT 
Hello,

This behavior happens consistently, without fail.  It has happened both with an iPod plugged in and with no iPod plugged in.  The output of running Amarok 1.4 from the terminal when the crash occurs is here:
-------------------------------------------------------------------------------
mcballz@mcballz-GA-MA785GMT-UD2H:~$ amarokapp
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
        StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
STARTUP
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (376)
Amarok is crashing...
Running: gdb --nw -n --batch -x /tmp/kde-mcballz/amarokmyji6I.tmp amarokapp 2336
sh: gdb: not found
Running: file `which amarokapp`
1.4.10 [___stripped][xine]

Amarok has crashed! We are terribly sorry about this :(

But, all is not lost! Perhaps an upgrade is already available which fixes the problem. Please check your distribution's software repository.
------------------------------------------------------------------------------

Thanks for a beautiful operating environment.  :D
Comment 1 bkadoctaj 2010-10-12 12:54:23 CDT 
After installing the Amarok 1.4 debug tools, this came up as well:
------------------------------------------------------------------------------
Amarok has crashed! We are terribly sorry about this :(

But, all is not lost! You could potentially help us fix the crash. Information describing the crash is below, so just click send, or if you have time, write a brief description of how the crash happened first.

Many thanks.







The information below is to help the developers identify the problem, please do not modify it.



======== DEBUG INFORMATION  =======
Version:    1.4.10
Engine:     xine-engine
Build date: Sep  7 2010
CC version: 4.4.5 20100902 (prerelease)
KDElibs:    3.5.12 [Trinity]
Qt:         3.3.8b
TagLib:     1.6.3
CPU count:  2
NDEBUG:     true
==== file `which amarokapp` =======
/opt/kde3/bin/amarokapp: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped


==== (gdb) bt =====================

==== (gdb) thread apply all bt ====


==== kdBacktrace() ================
Comment 2 Timothy Pearson 2012-06-12 22:41:35 CDT 
Can you confirm that this crash is still present with a newer version of Trinity?  There have been many improvements to overall TDE application stability, for example the resolution of Bug 812, that may have resolved this problem.
Comment 3 Darrell 2013-04-27 12:22:01 CDT 
I am not seeing this problem with the latest GIT. As the report is rather old, if the original reporter does not respond within the next seven days to confirm the bug still exists, then let's close this report as Resolved Works For Me.
Comment 4 Timothy Pearson 2013-05-04 12:56:56 CDT 
I am going to assume that this was a threading error similar to various other threading glitches I have encountered in Amarok.  Closing as WORKSFORME.