Bug 23023 - Attempting to the tab being viewed causes Otter Browser to crash
Summary: Attempting to the tab being viewed causes Otter Browser to crash
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://otter-browser.org
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-12 18:17 CEST by aguador
Modified: 2018-05-12 22:35 CEST (History)
1 user (show)

See Also:
Source RPM: otter-browser-0.9.92-1.mga7.src.rpm
CVE:
Status comment:


Attachments
Terminal output from Otter crash (2.66 KB, text/plain)
2018-05-12 18:18 CEST, aguador
Details

Description aguador 2018-05-12 18:17:37 CEST
Otter crashes when clicking the icon on a tab to close it.

To reproduce:
1. Start Otter Browser.
2. Click on the x icon of the active tab you are viewing to close it, and Otter crashes.

Note this does NOT happen when closing tabs one is not viewing.

I cannot say when this started as Otter is not my regular browser, simply one I use from time to time given the changes in current Firefox.

System: Fully updated Optimus laptop using nVidia driver and Enlightenment 0.22.3.
Comment 1 aguador 2018-05-12 18:18:28 CEST
Created attachment 10144 [details]
Terminal output from Otter crash
Comment 2 Kristoffer Grundström 2018-05-12 19:12:28 CEST
Do you have any more Desktop Environments installed?
If so, can you reproduce the same crash in any of the other environments?
In your output it doesn't say what version of otter-browser you've installed.
Try to create a new user in Mageia, then login to the new user account and try to reproduce the same issue.

CC: (none) => hamnisdude

Comment 3 aguador 2018-05-12 22:35:09 CEST
I am closing this with apologies. Even I cannot not reproduce this although the crash as persistent earlier today. It works in E, IceWM, and E with new user with no problem.

Version, by the way, is the latest 0.9.92.

Resolution: (none) => INVALID
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.