Issue 59826 - Font Pull-down causes UI freeze
Summary: Font Pull-down causes UI freeze
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@ui
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2005-12-27 17:36 UTC by rdkennedy
Modified: 2008-05-17 23:50 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description rdkennedy 2005-12-27 17:36:50 UTC
SHORT NAME: Font Name selector freezes desktop in Linux FC3/Gnome
AFFECTED OO: 2.0.1
AFFECTED OS: Linux, stock Fedora Core 3, up2dated, using GNOME

When the Font Name pull-down (from toolbar, for instance) is selected and
selection list is pulled down, a few font family names are listed, but then the
entire app and desktop (GNOME) UI freezes.

The kernel and UI are running at some level since several applets continue to
update (cpu utilization). Only way to clear condition is to reboot. Restarting
the X server does not work, surprisingly, as it just leaves one in a hung text
console with working but useless mouse-driven text cursor.

I have reproduced this with swriter, simpress, and scalc. It occurs 100% of the
time, at the same "font name" entry in each occurrence per app, but a different
"font name" per app. I unsetenv SESSION_MANAGER and still reproduced the
problem. I have not tried to reproduce with KDE desktop yet. I have not observed
this with any other programs, nor with any previous OO releases.

NOT AFFECTED:
2.0 on exact same OS, exact same hardware
2.0.1 on Windows XP (home) SP2 on exact same hardware.

AFFECTED OS DETAILS:
kernel-smp-2.6.12-1.1381_FC3
glibc-2.3.6-0.fc3.1
xorg-x11-6.8.2-1.FC3.45.2
gnome-desktop-2.8.0-3
libgnome-2.8.0-2
openoffice.org-gnome-integration-2.0.1-1

HARDWARE:
Intel P4 2.2 GHz PC (Gateway), no HT
ATI R350 (Radeon 9800 Pro)
Comment 1 rdkennedy 2005-12-27 18:10:01 UTC
This also occurs on same hardware with the KDE desktop... freezes at same font
name per app.

This occurs in both a fresh RPM install as well as an RPM upgrade from 2.0. 

Sometimes, one can clear the condition by restarting the X11 server without a
reboot, but not always.

After this happens the first time, one is always queried to recover the document
that was open at the time of the freeze. The error recover succeeds and
subsequent app restarts do not ask again about doc recovery.
Comment 2 rdkennedy 2005-12-28 02:57:58 UTC
After removing OO 2.0.1 and re-installing OO 2.0.0, I can reproduce the UI
freeze which was not present in 2.0.0 for my hardware before. I also saw it
occur when I opened a DOC file with graphics, once I arrive at the graphics area
of the file. While it is still an issue, and quite reproducible, I cannot
explain why it happens now with 2.0.0 when it did not before.... Perhaps this is
specific to my systems afterall. I will try a few other Linux platforms.
Comment 3 janvlug 2006-01-10 09:29:53 UTC
Confirming: I experience exact the same behaviour on FC3 on gnome. Using AMD 64 
hardware, OpenOffice 2.0.1.
I see the freeze both when selecting the Font Name pull-down and a DOC file 
with graphics.
However, the problem with the DOC file with graphics did I see before, when I 
was still using OpenOffice 2.0. And this case is not as reproducable as the 
selecting Font Name pull-down case.
Comment 4 ianstepn 2006-01-14 18:25:44 UTC
I experience the same using either OOo2.0 or OOo2.01 on a Celeron system running
Mandrake 10.0 using KDE, but the freeze only happens using the font name
pull-down menu in the toolbars.  Selecting fonts from menus "format > character
> font" works with no problems.

If I use the font name pull-down, a few fonts are listed then the desktop freezes.  

Freeze can be cleared by "killall soffice.bin"

I have also had freezes opening documents and, for a document that has this
problem, have solved the problem by; open the document in OOo1.1.5, change the
font, save the document, then open the document in OOo2.0 or 2.01.
Comment 5 hwoarang 2006-03-01 03:07:57 UTC
rdkennedy, can you reproduce with same problem with latest version (at least
2.0.2) ?

Thank you.

Hwoarang
Comment 6 janvlug 2006-03-20 09:39:07 UTC
This same problem still happens with OpenOffice 2.0.2.
Comment 7 khirano 2007-02-17 02:34:16 UTC
My friend told me that this is reproduceable with 2.0.4 on Linux (CentOS 4.4),
both on GNOME and KDE.

Now I have just tried to reproduce it with OOF680m6 on Debian Linux, KDE.  It is
not reproduced.
Comment 8 jjmckenzie 2007-02-17 04:10:40 UTC
@khirano:

CentOS/FC/RedHat are from the same distribution source.  This may be the source
of the problem that cannot be recreated on Debian, which is from a different
source.    Can this be confirmed on another system with either FC6 or CentOS 4.4
installed to confirm that this happens.  More details on the users@ list might
be helpful to see if anyone else encountered this problem.

James McKenzie
Comment 9 daihard 2007-02-17 08:06:52 UTC
I just ran into the exact same problem using both OO.o 2.0.4 and 2.1. The OS is
CentOS 4.4. I was using 2.0.4 without this problem until a couple of days ago,
when I must have updated some packages using "yum update." Since then Writer and
Calc will always freeze when I click on the font combo box to select a font.

I can reproduce the problem 100% of the time, with both KDE 3.5.6 and GNOME 2
(not sure the exact version).
Comment 10 Joost Andrae 2007-02-17 09:10:58 UTC
Displaying a broken font freezes every X application. As a workaround you can
disable the font preview within the font listbox in
/tools/options/openoffice.org/view or you can try to check each single font on
your system if it is broken and then delete the broken font
Comment 11 ace_dent 2008-05-17 21:46:19 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 12 ace_dent 2008-05-17 23:50:40 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew