Bug 68085 - Kopete crashes with sigsev11 after adding user to Kontact
Summary: Kopete crashes with sigsev11 after adding user to Kontact
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-13 02:00 UTC by Anthony
Modified: 2003-11-14 13:32 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 Anthony 2003-11-13 02:00:56 UTC
Version:           0.7.93 (using KDE 3.1.93 (3.2 beta 1), SuSE)
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.21-99-smp4G

Right click on user, go down to prop. - click option at bottom to add to Kontact, clock on the ... to select from a list - select the user you want to link it to, OK that - pause, crash out - Sigsev11. Any ideas. Not important - but replicatable on more than one machine - suse 8.2 uni and suse 9 smp.
Comment 1 Stefan Gehn 2003-11-13 09:05:34 UTC
You forgot the backtrace
Comment 2 Anthony 2003-11-13 17:43:01 UTC
Thanks mETz81 - below is the bugtrack:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 
16384 (LWP 3690)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x41ba3a86 in waitpid ()
   from /lib/i686/libpthread.so.0
#0  0x41ba3a86 in waitpid () from /lib/i686/libpthread.so.0
#1  0x410c8bb0 in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#2  0x41ba296c in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3  <signal handler called>

...and relax
Comment 3 Matt Rogers 2003-11-13 18:06:55 UTC
could you recompile kopete with --enable-debug=full (add it to the configure line) and paste the backtrace again when it crashes. This backtrace contains nothing useful to us at all.
Comment 4 Will Stephenson 2003-11-13 18:46:53 UTC
#3  <signal handler called>
#4  0x08a1e165 in ?? ()
#5  0x4015a550 in KABC::AddressBook::releaseSaveTicket(KABC::Ticket*) (
    this=0x84062b0, ticket=0x8837fe0)
    at /home/will/projects/kde/src/kdelibs/kabc/addressbook.cpp:506
#6  0x400bdde2 in KopeteMetaContact::slotWriteAddressBook() (this=0x86d6b30)
    at /home/will/projects/kde/src/kdenetwork/kopete/libkopete/kopetemetacontact.cpp:896
#7  0x400becf7 in KopeteMetaContact::qt_invoke(int, QUObject*)

In the bowdlerised words of Roy Chubby Brown, 'it's _me_ you bustards, i'm the cant!' 

Will investigate tonight.
Comment 5 Will Stephenson 2003-11-14 12:38:33 UTC
Can anyone getting this bug open up KControl, go to KDE Components->KDE Resources Configuration, choose the 'contact' resource and tell me if you get a complaint about 'no valid standard resource' when you do so?
Comment 6 Will Stephenson 2003-11-14 13:32:48 UTC
Subject: kdenetwork/kopete

CVS commit by wstephens: 

Fix a crash when adding fields to kde addressbook entries.

I had written (nay, amended!) our code to match kabc's HOWTO rather than its api docs, while unaware that this behaviour was incorrect.  The kabc regression has now been fixed, which left kopete with its pants down.

CCMAIL: 68085-done@bugs.kde.org


  M +2 -2      kopete/addcontactwizard/addcontactwizard.cpp   1.34
  M +3 -1      libkopete/kopetemetacontact.cpp   1.193


--- kdenetwork/kopete/libkopete/kopetemetacontact.cpp  #1.192:1.193
@@ -892,8 +892,10 @@ void KopeteMetaContact::slotWriteAddress
         {
                 if ( !ab->save( ticket ) )
+                {
                         kdWarning( 14010 ) << k_funcinfo << "ERROR: Saving failed!" << endl;
 #if KDE_IS_VERSION (3,1,90)
                 ab->releaseSaveTicket( ticket );
 #endif
+                }
         }
         kdDebug( 14010 ) << k_funcinfo << "Finished writing KABC" << endl;

--- kdenetwork/kopete/kopete/addcontactwizard/addcontactwizard.cpp  #1.33:1.34
@@ -164,8 +164,8 @@ void AddContactWizard::slotAddAddresseeC
                         {
                                 kdError() << "Saving failed!" << endl;
-                        }
 #if KDE_IS_VERSION (3,1,90)
                         m_addressBook->releaseSaveTicket( ticket );
 #endif
+                        }
                 }
         }