Bug 240546 - kopete crash at startup - Ubuntu 10.04-06--
Summary: kopete crash at startup - Ubuntu 10.04-06--
Status: RESOLVED DUPLICATE of bug 287364
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-03 04:27 UTC by bug.correspondence
Modified: 2011-11-28 15:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bug.correspondence 2010-06-03 04:27:07 UTC
Application: kopete (1.0.0)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
Crash occurs on startup in Ubuntu 10.04 (32 bit), running Gnome (all packages updated as of 2010-06-02 at 20:00 CST (United States).

Will provide any additional information if requested.

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[KCrash Handler]
#5  0x00400e91 in free () from /lib/tls/i686/cmov/libc.so.6
#6  0x0762245d in XFree (data=0x1) at ../../src/XlibInt.c:3221
#7  0x010d33fa in KApplicationPrivate::parseCommandLine (this=0x8d25148) at ../../kdeui/kernel/kapplication.cpp:860
#8  0x010d3a8a in KApplicationPrivate::init (this=0x8d25148, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:460
#9  0x010d49fb in KApplication (this=0xbf8c7b74, GUIenabled=true, cData=...) at ../../kdeui/kernel/kapplication.cpp:378
#10 0x010db64e in KUniqueApplication (this=0xbf8c7b74, GUIenabled=false, configUnique=<value optimized out>) at ../../kdeui/kernel/kuniqueapplication.cpp:321
#11 0x08059b03 in KopeteApplication (this=0xbf8c7b74) at ../../../kopete/kopete/kopeteapplication.cpp:56
#12 0x08059a09 in main (argc=2, argv=0xbf8c7fb4) at ../../../kopete/kopete/main.cpp:104

Reported using DrKonqi
Comment 1 Christoph Feck 2011-11-28 15:11:08 UTC

*** This bug has been marked as a duplicate of bug 287364 ***