Bug 149711 - kopete crashes on boot - no error message
Summary: kopete crashes on boot - no error message
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-09 19:47 UTC by Ron Eggler
Modified: 2008-02-07 06:14 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Eggler 2007-09-09 19:47:13 UTC
Version:           0.12.6 (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
Compiler:          gcc 4.1.2 
OS:                Linux

My Kopete just crashes when i start it, the konsole ouput looks like:
reg@desktop-reg:~> kopete
reg@desktop-reg:~> QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: ListTask
CLIENT: SendPictureTask: Task::done()
CLIENT: SendPictureTask: emitting finished
CLIENT: SendPictureTask: Task::done()
CLIENT: SendPictureTask: emitting finished
Transfer ACCEPTED by: StatusNotifierTask
Transfer ACCEPTED by: MailNotifierTask
Transfer ACCEPTED by: StatusNotifierTask
QGArray::find: Index 0 out of range
KCrash: Application 'kopete' crashing...

No idea what's wrong there :o I probably need to reinstall it...(remove it completely first and then put it back on)

Anyone?

Thanks!
Ron
Comment 1 Matt Rogers 2007-09-09 23:19:30 UTC
Please provide a backtrace of the crash, read http://techbase.kde.org/ 
Development/Tutorials/Debugging/How_to_create_useful_crash_reports  
for more info on how to do this.
Comment 2 Matt Rogers 2008-02-07 06:14:25 UTC
Waiting for more than three months for information on how to reproduce, either through instructions or a backtrace. Since I cannot reproduce this, I'll close the bug for now. Please reopen it when you can provide more information.