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 1415 - Amarok crashes immediately after startup
Summary: Amarok crashes immediately after startup
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdemultimedia (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: i386 Debian Wheezy
: P5 major
Assignee: Timothy Pearson
URL:
: 1492 (view as bug list)
Depends on: 346
Blocks:
  Show dependency tree / graph
 
Reported: 2013-03-06 13:53 CST by Martin Hodges
Modified: 2013-05-23 18:32 CDT (History)
5 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 Martin Hodges 2013-03-06 13:53:35 CST 
Run from terminal:
martin@hooch:~$ amarok
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
TQLayout "unnamed" added to TQVBox "unnamed", which already has a layout
TQLayout: Adding TDEToolBar/mainToolBar (child of TQVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
TQObject::connect: Incompatible sender/receiver arguments
        StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const TQString&)
martin@hooch:~$

Not very enlightening I'm afraid.
Running gdb on amarokapp:
(gdb) run
Starting program: /opt/trinity/bin/amarokapp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
TQLayout "unnamed" added to TQVBox "unnamed", which already has a layout
TQLayout: Adding TDEToolBar/mainToolBar (child of TQVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
TQObject::connect: Incompatible sender/receiver arguments
        StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const TQString&)
[New Thread 0xb28f1b70 (LWP 9873)]
[New Thread 0xb1effb70 (LWP 9874)]
[Thread 0xb1effb70 (LWP 9874) exited]
[Thread 0xb28f1b70 (LWP 9873) exited]
[New Thread 0xb28f1b70 (LWP 9875)]
[New Thread 0xb1effb70 (LWP 9876)]
[New Thread 0xad277b70 (LWP 9877)]
[New Thread 0xac8a9b70 (LWP 9878)]
[New Thread 0xac0a8b70 (LWP 9879)]
STARTUP

Program received signal SIGSEGV, Segmentation fault.
0xb74ee618 in TQGArray::assign(TQGArray const&) () from /usr/lib/libtqt-mt.so.3

gdb) bt
#0  0xb74ee618 in TQGArray::assign(TQGArray const&) () from /usr/lib/libtqt-mt.so.3
#1  0xb79ee312 in MetaBundle::operator=(MetaBundle const&) () from /opt/trinity/lib/libamarok.so.0
#2  0xb79ee563 in MetaBundle::MetaBundle(MetaBundle const&) () from /opt/trinity/lib/libamarok.so.0
#3  0xb7a7bf65 in UrlLoader::slotNewBundle(MetaBundle const&, TQValueList<TQPair<TQString, TQString> > const&) ()
   from /opt/trinity/lib/libamarok.so.0
#4  0xb7a7c228 in UrlLoader::tqt_invoke(int, TQUObject*) () from /opt/trinity/lib/libamarok.so.0
#5  0xb727f324 in TQObject::event(TQEvent*) () from /usr/lib/libtqt-mt.so.3
#6  0xb722979f in TQApplication::internalNotify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#7  0xb7229cb7 in TQApplication::notify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#8  0xb68eaad1 in TDEApplication::notify(TQObject*, TQEvent*) () from /opt/trinity/lib/libtdecore.so.4
#9  0xb722af2f in TQApplication::sendPostedEvents(TQObject*, int) () from /usr/lib/libtqt-mt.so.3
#10 0xb722b093 in TQApplication::sendPostedEvents() () from /usr/lib/libtqt-mt.so.3
#11 0xb72094e5 in TQEventLoop::processX11Events() () from /usr/lib/libtqt-mt.so.3
#12 0xb7209de1 in TQEventLoop::gsourceDispatch(_GSource*) () from /usr/lib/libtqt-mt.so.3
#13 0xb7209ecc in ?? () from /usr/lib/libtqt-mt.so.3
#14 0xb6eed6d3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#15 0xb6eeda70 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#16 0xb6eedb51 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#17 0xb7209420 in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3
#18 0xb723dbe0 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3
#19 0xb723db64 in TQEventLoop::exec() () from /usr/lib/libtqt-mt.so.3
#20 0xb722a65c in TQApplication::exec() () from /usr/lib/libtqt-mt.so.3
#21 0x0804c5ad in ?? ()
#22 0xb65bde46 in __libc_start_main () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#23 0x0804c6a1 in ?? ()

Hope this helps.
Comment 1 Martin Hodges 2013-03-06 13:58:35 CST 
The package is from the nightly builds ppa.
4:14.0.0-0debian12+r204+pr6~wheezy

The program will run correctly as long as the amarokrc file does not exist.
Comment 2 Slávek Banko 2013-05-04 07:34:29 CDT 
*** Bug 1492 has been marked as a duplicate of this bug. ***
Comment 3 Slávek Banko 2013-05-04 07:36:23 CDT 
I think that the problem is fixed in GIT commit 670b8acb.
Comment 4 Timothy Pearson 2013-05-04 12:13:57 CDT 
(In reply to comment #3)
> I think that the problem is fixed in GIT commit 670b8acb.

Yep, this is fixed in GIT but the nightly builds are still building.

Tim
Comment 5 Alex Couture 2013-05-08 19:43:46 CDT 
(In reply to comment #4)
> (In reply to comment #3)
> > I think that the problem is fixed in GIT commit 670b8acb.
> 
> Yep, this is fixed in GIT but the nightly builds are still building.
> 
> Tim

On my Ubuntu 13.04 system with R14 nightlies of May 08, it doesn't start...
Should I remove some Amarok config files and test after that, or it should work right away with the update?

-Alexandre
Comment 6 Timothy Pearson 2013-05-08 19:46:40 CDT 
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > I think that the problem is fixed in GIT commit 670b8acb.
> > 
> > Yep, this is fixed in GIT but the nightly builds are still building.
> > 
> > Tim
> 
> On my Ubuntu 13.04 system with R14 nightlies of May 08, it doesn't start...
> Should I remove some Amarok config files and test after that, or it should work
> right away with the update?
> 
> -Alexandre

No, do not remove configuration files.  Amarok should just start working, anything else is a bug.

It looks like the Amarok builds failed (https://quickbuild.pearsoncomputing.net/~trinity/+archive/trinity-nightly-builds/+packages?field.name_filter=amarok&field.series_filter=&field.status_filter=published&start=0&batch=300), so you are still running the old unstable version.
Comment 7 Slávek Banko 2013-05-08 19:52:42 CDT 
(Odpověď na komentář #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > > I think that the problem is fixed in GIT commit 670b8acb.
> > > 
> > > Yep, this is fixed in GIT but the nightly builds are still building.
> > > 
> > > Tim
> > 
> > On my Ubuntu 13.04 system with R14 nightlies of May 08, it doesn't start...
> > Should I remove some Amarok config files and test after that, or it should work
> > right away with the update?
> > 
> > -Alexandre
> 
> No, do not remove configuration files.  Amarok should just start working,
> anything else is a bug.
> 
> It looks like the Amarok builds failed
> (https://quickbuild.pearsoncomputing.net/~trinity/+archive/trinity-nightly-builds/+packages?field.name_filter=amarok&field.series_filter=&field.status_filter=published&start=0&batch=300),
> so you are still running the old unstable version.

Yes - successful build awaiting fix bug 346. Unfortunately, I still did not have enough time to create a patch. I suppose I could solve it on Saturday.
Comment 8 Alex Couture 2013-05-18 20:32:57 CDT 
With the nightlies of May 18, 2013 on Ubuntu 13.04, it works as it should!
Thanks!
-Alexandre