Bug 308219

Summary:	Active web browser: crashes when launching GMAIL
Product:	[Unmaintained] Active	Reporter:	Jean Cayron <jean.cayron>
Component:	Applications	Assignee:	active
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	giorgos.tsiapaliokas, notmart
Priority:	NOR	Keywords:	triaged
Version:	PA 3
Target Milestone:	unscheduled
Platform:	Meego/Harmattan
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	output of gdb

Description Jean Cayron 2012-10-11 08:33:55 UTC

The webbrowser from Plasma Active crashes when trying to use Gmail.

Reproducible: Always

Steps to Reproduce:
1. Opens the Browser
2. Go to gmail.com
3. Type your credentials in
Actual Results:  
The web browser will crash either during charging the inbox, either later after clicking on one first mail to read it.

Expected Results:  
Web browser works and does not crash.

Found on basyskom-plasma-active-archos-gen9-omapfb-tablet-mer-testing-release-rc3 but was present since a few versions in devel.

Comment 1 Marco Martin 2012-10-11 17:12:19 UTC

seems to happen only on arm.
can you generate a backtrace?

Comment 2 Jean Cayron 2012-10-12 06:55:14 UTC

Unfortunately, I don't know why but DrKonqui does not show up after the crashes. Would the output of the command in konsole enough?

Comment 3 Giorgos Tsiapaliokas 2012-10-12 08:47:46 UTC

this wiki page describes how to take a backtrace with gdb.

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB

Comment 4 Jean Cayron 2012-10-12 21:15:00 UTC

GDB didn't give a backtrace. I don't know which debug package has I to install to have debug symbols for active-webbrowser. I didn't find it.

Comment 5 Jean Cayron 2012-10-12 21:16:58 UTC

Created attachment 74508 [details]
output of gdb

As said: no backtrace but the output may interest you

Comment 6 Andrew Crouthamel 2018-09-23 02:21:34 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Andrew Crouthamel 2018-10-27 02:10:48 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!