Bug 308749 - rekonq crashe
Summary: rekonq crashe
Status: RESOLVED WORKSFORME
Alias: None
Product: rekonq
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Andrea Diamantini
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-10-21 12:04 UTC by Daniel Moyne
Modified: 2018-10-27 03:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Moyne 2012-10-21 12:04:39 UTC
rekonq crashes with following error message :Executable : rekonq PID : 31707 Signal : Segmentation fault (11)

Reproducible: Always

Steps to Reproduce:
1. happened fater trying to print
2.
3.
Actual Results:  
crash with error message :Executable : rekonq PID : 31707 Signal : Segmentation fault (11)

Expected Results:  
no crash

Before worked fine but after trying to print and a crash, reopening rekonk applying : option restoring previous status not closed properly
Comment 1 Jekyll Wu 2012-10-21 13:11:51 UTC
It is hard to know what has happend without a backtrace.
Comment 2 Daniel Moyne 2012-10-21 14:45:53 UTC
sorry after updating a few things it looks like the bug has desapeared ; I will keep you posted if it show up again.
Comment 3 Andrew Crouthamel 2018-09-23 02:34:43 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 4 Andrew Crouthamel 2018-10-27 03:48:22 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!