Message: previous - next
Month: March 2015

Re: [trinity-users] next problem, konqueror's 75% crash rate when clicking on an http link in kmail

From: Lisi Reisz <lisi.reisz@...>
Date: Sun, 8 Mar 2015 16:49:31 +0000
On Sunday 08 March 2015 16:29:03 Gene Heskett wrote:
> Ping?

?????  See below at the end.

> On Saturday 07 March 2015 14:04:12 Gene Heskett wrote:
> > Where do I change this (TDE? IDK) default broswer to iceweasal when I
> > click on a web link in a kmail incoming message?

Lisi, earlier:
KControl -> KDE components -> File associations.  Probably TDE components in 
14.  I am on my desktop."

Dave Lers, earlier:
"Yes, Trinity Control Center > TDE Components > File Associations

From Konqueror its Services > Settings > TDE Components > File
Associations :-)."

> >
> > If it runs long enough, I can switch to iceweasal in its file
> > pulldown, but 75% of the time I am looking at its crash report popup,
> > which for the purposes of registering a bug report is worthless
> > because the debug symbols are not compiled in.  So the report it does
> > file is basically konqueror crashed, no further details.  Those I
> > believe must get routed to /dev/null since not one of them over the
> > last 5+ years has ever resulted in a reply (from anyone) asking for
> > further details.

elcaseti earlier:
"For many, many years, I have also had trouble with Konquerer crashing all
the time.  This is the case on TDE and KDE, and on every distro I have
used, which is a lot of them."

You've hit a bug.

It wasn't TDE that didn't answer, you haven't been using it for five years.  I 
never click those things. They do seem to be useless.

 Here is an explanation for some of the Konqueror problems in TDE:
Timothy Pearson earlier:
"David Lers said:
> Pretty much
> the only thing Konqueror cannot browse is resource hungry web sites.
> While I'd love to see that change, I'm not holding my breath. Despite
> that, Konqueror remains my primary desktop application because I can
> do/start anything with/from Konqueror.

As you've probably guessed fixing this is very hard.  It would require
integrating a different browser engine (such as Webkit) into a Konqueror
plugin while retaining the functionality of the KHTML plugin.  While much
of the groundwork has been laid to allow Webkit integration no one has
stepped up to put a prototype together at this time."

So what didn't get a reply and needs pinging?  Perhaps rephrase the bit you 
think did not get a reply.