Bug 27964

On Sunday 1. July 2001 13:24 jgs1960@yahoo.com wrote:
>
> Crash occurs trying to check in new mail able to send w/o a problem. 
> First occurred some 4-6 weeks ago after a CVS co of kdenetwork.  Reported
> it on kmail list but never answered.  After fresh CVS co still occurs. 
> Tried deleting $HOME/Mail and kmailrc to no avail.  Backtrace shows:

Is your kdelibs and kdebase also up to date?
Does that happen always or sometimes?

Regards
Michael Häckel

Michael Häckel wrote:
> 
> On Sunday 1. July 2001 13:24 jgs1960@yahoo.com wrote:
> >
> > Crash occurs trying to check in new mail able to send w/o a problem.
> > First occurred some 4-6 weeks ago after a CVS co of kdenetwork.  Reported
> > it on kmail list but never answered.  After fresh CVS co still occurs.
> > Tried deleting $HOME/Mail and kmailrc to no avail.  Backtrace shows:
> 
> Is your kdelibs and kdebase also up to date?
> Does that happen always or sometimes?
> 
Sorry yes they were this time and last.  I tried from a newly create user
and get same... it had been working and I'm bummed because I was really
starting to like it.

regards
-John

Michael Häckel wrote:
> 
> Does that happen always or sometimes?
> 
Always...

-John

On Sunday 1. July 2001 17:34 John Schmidt wrote:
>
> Sorry yes they were this time and last.  I tried from a newly create user
> and get same... it had been working and I'm bummed because I was really
> starting to like it.

Well and what shall I do now?
4-6 weeks ago that was probably the time when POP3 was ported to connection 
oriented mode in order to be able to pass information for authentication and 
encryption but I really can't see what's wrong with that and it works for 
nearly everyone else.

Well I read:
Compiler:          gcc 2.96

Maybe you should use a stable version of gcc for example 2.95.3.

Regards
Michael Häckel

Michael Häckel wrote:
> 
> On Sunday 1. July 2001 17:34 John Schmidt wrote:
> 
> Well and what shall I do now?
> 4-6 weeks ago that was probably the time when POP3 was ported to connection
> oriented mode in order to be able to pass information for authentication and
> encryption but I really can't see what's wrong with that and it works for
> nearly everyone else.
> 
> Well I read:
> Compiler:          gcc 2.96
> 
> Maybe you should use a stable version of gcc for example 2.95.3.
> 
Compiler didn't change from when it was working until it broke and I'm not
having crashes throughout KDE to warrant re-installation of an older compiler
then re-compile all of KDE & Qt.  At least not on a "maybe!"

From the backtrace KIO looked to be invoking a QString just before crash bad/
null pointer to a QString??  From .xsession-errors:

kmail: entering KMKernel::init()
kmail: exiting KMKernel::init()
kmail: KMKernel::openReader called
libkdenetwork: loaded the scorefile creating internal representation
libkdenetwork: inspecting node of type 9 named
libkdenetwork: inspecting node of type 7 named
libkdenetwork: inspecting node of type 1 named Scorefile
libkdenetwork: ready got 0 rules
khtml (part): KHTMLPart::init this=0x8251f00 d=0x8258d90
kmail: updateMessageMenu
kmail: Not equal
khtml (memory): KHTMLPart::clear() this = 0x8251f00
kmail: Not equal
khtml (memory): KHTMLPart::clear() this = 0x8251f00
khtml (memory): KHTMLPart::clear(): dereferencing the document
khtml (memory): HTMLDocumentImpl::detach()
libkdenetwork: created cache for group inbox with 0 rules
libkdenetwork: created cache for group inbox with 0 rules
kmail: end 28550[void KMHeaders::setFolder (KMFolder * bool)]
kmail: updateMessageMenu
kdeinit: PID 1660 terminated.
DCOP:  unregister 'anonymous-1660'
DCOP: number of clients is now down to 10
kdecore (KStartupInfo): check_startup
kdecore (KStartupInfo): find_id:rh70.hobbes;994014683;793859;1575
kdecore (KStartupInfo): check_startup_id:match
kdecore (KStartupInfo): check_startup
kdecore (KStartupInfo): find_id:rh70.hobbes;994014683;793859;1575
kdecore (KStartupInfo): check_startup_id:match
kdecore (KStartupInfo): new window match
kdecore (KStartupInfo): removing
kdecore (KStartupInfo): check_startup
kdecore (KStartupInfo): find_id:rh70.hobbes;994014683;793859;1575
kdecore (KStartupInfo): check_startup_id:match
kdecore (KStartupInfo): new window match
kdecore (KStartupInfo): removing
kmail: enable progress
kdecore (KURL): KURL couldn't parse URL "pop3s:"
QGDict::hashStringKey: Invalid null key
QGDict::hashStringKey: Invalid null key
kio (Slave): createSlave '' for pop3s:
kio (KLauncher): requestSlave
kio (KLauncher): KLauncher::requestSlave for : looking for a slave handling
kio (KProtocolInfo): ERROR: Protocol '' not found
kio (KLauncher): requestSlave got pid 0
kmail: ERROR: ERROR 3: couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol ''.
kmail:
kio (Scheduler): Scheduler::_doJob protocol=pop3s
kio (Scheduler): _assignJobToSlave( 0x83175b0 (nil))
*** KMail got signal 11 (Crashing)
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kmail path = <unknown> pid = 1661
DCOP:  unregister 'kmail'
DCOP: number of clients is now down to 9

How do you fire up a debugger working inside KDE??  Haven't been at this 
very long I was just adding err->addMsg/display in debugging KUser...

regards
John

John Schmidt wrote:
> 
> kdecore (KURL): KURL couldn't parse URL "pop3s:"
> QGDict::hashStringKey: Invalid null key
> QGDict::hashStringKey: Invalid null key
> kio (Slave): createSlave '' for pop3s:
> kio (KLauncher): requestSlave
> kio (KLauncher): KLauncher::requestSlave for : looking for a slave handling
> kio (KProtocolInfo): ERROR: Protocol '' not found
> kio (KLauncher): requestSlave got pid 0
> kmail: ERROR: ERROR 3: couldn't create slave : Unable to create io-slave:
> klauncher said: Unknown protocol ''.

Uhhh you might want to add an isNull or such check for dip-wads like me that
put my mail server in Name and leave Host blank!  :))  Don't know how that
happened but I was also switching between KDE 2.1.1 and 2.2 when this 
first started.  Also the port was showing 995???  Set back to 110.  

So no more crashes but now it hangs and eventually comes back with Unable to 
connect or something like that.  Netscape works fine...
 
regards
John

On Sunday 01 July 2001 04:29 pm you wrote:
> On Sunday 1. July 2001 21:22 John Schmidt wrote:
> > kmail:
> > kio (Scheduler): Scheduler::_doJob protocol=pop3s
> > kio (Scheduler): _assignJobToSlave( 0x83175b0 (nil))
>
> Somehow it trys to assign a job to a slave whose pointer is nil.
>
> Does it work without SSL?
Yes I am now happily KMailing again!!

> Maybe you don't have openssl installed properly I didn't test this case
> yet.

I dunno never installed it (knowingly) assume it was installed as part of 
installing OS.  Configuration required??
>
> Looking at the code I just see that this case is indeed not handled
> correctely.

Blank Host parm?

regards
-John

On Sunday 1. July 2001 21:22 John Schmidt wrote:

> kmail:
> kio (Scheduler): Scheduler::_doJob protocol=pop3s
> kio (Scheduler): _assignJobToSlave( 0x83175b0 (nil))

Somehow it trys to assign a job to a slave whose pointer is nil.

Does it work without SSL?
Maybe you don't have openssl installed properly I didn't test this case yet.

Looking at the code I just see that this case is indeed not handled 
correctely.

Regards
Michael Häckel

On Sunday 1. July 2001 22:28 John Schmidt wrote:
>
> I dunno never installed it (knowingly) assume it was installed as part of
> installing OS.  Configuration required??

If the configure script of kdelibs doesn't complain then it should actually 
work.

> > Looking at the code I just see that this case is indeed not handled
> > correctely.
>
> Blank Host parm?

Ok then I close this report as duplicate for now.

Regards
Michael Haeckel