Bug 52579 - EDITING: Special characters
Summary: EDITING: Special characters
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.5.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-27 09:56 UTC by Sascha Mehlhase
Modified: 2013-07-08 21:21 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sascha Mehlhase 2012-07-27 09:56:43 UTC
Problem description: 

Software crashes on a mac when scrolling in the Special Characters dialog.

Steps to reproduce:
1. Start impress
2. Create a presentaion
3. Click on some text field
4. Choose -> Insert -> Special Characters
5. Scroll in the dialog

Current behavior:
Crash!

Expected behavior:
No Crash!

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.49 Safari/537.1
Comment 1 Julien Nabet 2012-08-05 13:52:25 UTC
On pc Debian x86-64, with master sources and 3.5 branch (both updated today), I didn't reproduce the problem.
(not tested on 3.6 branch, since the 2 others were ok).

Did you install a specific font ?
Could you give details on which dialog did you scroll ?
Do you reproduce this with a brand new LO profile ? (see http://wiki.documentfoundation.org/UserProfile)
Comment 2 Sascha Mehlhase 2012-08-06 05:01:01 UTC
Hi,

it happens when I use the mouse scrolling in the special characters window. Just using the keys, doesn't show the problem. The font of the document is Verdana. 

After removing/re-creating the user profile the problem seems gone!?
So far I did not manage to reproduce with the new user profile.

Thanks anyways!
I'll get back once I can reproduce it on a clean profile.
Comment 3 Julien Nabet 2012-08-06 08:00:52 UTC
Thank you for your feedback.

It could be a dup of fdo#43489.

- Did the problem appear after an upgrade ?
- Did you backup the LO directory profile ?
    - If yes, could you zip and attach it to this bugtracker ?
Comment 4 QA Administrators 2013-05-27 16:54:22 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2013-07-08 21:21:45 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO