Apache OpenOffice (AOO) Bugzilla – Issue 4366
Font problems after the 2end start - Bold and Normal Fonts
Last modified: 2008-04-05 09:11:16 UTC
When I installed OpenOffice.org 1.0 on my up-to-date Red Hat 7.2, first everything works fine. The installation procedure starts, and I followed the instructuons. The first Start was also no problem .. everything works fine. In the past, I used Star Office and so it was no problem to find my way in OpenOffice. But all things changed after the 2end start. Like I new it from Star Office, ther were a wziard for registering. The problem was, that there where only a big white window with nothing inside. So I closed it. But thats not enough. I noticed, that there was a font problem I think. It was impossible to get along with it. The menus ware unreadeble, there were nothing expect the symbols .... Writing in the text processor was impossible ... and it was also impossible to open files, because the sema with gie file open dialog (only a big white window). So I considered to repair it, but the same procedure in the setup program. The dialogs .. simply e big white window. The only way for me to get it working again was to completely delete and reinstall it. After that it works for the first start, but than the same procedure as above. I had that problem only in OpenOffice.org 1.0. No problem with other applications .. Star Office 5.2 or the BETA of Star Office 6.0.. I hope I can give more informations about it later, I'll get back to it later ..
Created attachment 1519 [details] Screen shot showing Open Office running OK showing all characters.
Created attachment 1520 [details] Screen shot showing Open Office suddenly not being able to show the characters.
The above two screen shots illustrate the problem. Between screen shot 1 and screen shot 2 I closed down all Open Office Windows, and then restarted Writer and opened the same file again. At this restart the program asked me about registering. I chose "never register" (since I'd already registered). After this Open Office no longer displays most "funny characters" (e.g characters from Latin Extended A) in most of my fonts. Some fonts still work, but not e.g. Times New Roman (used in both screen shots). Only a completely new Setup helps (deleting the old Open Office user directory). The problem comes back at the second start of the program. I use Open Office 1.0 in RedHat Linux 7.2.
I get virtually the same problem w/ a "./setup -net" install on Red Hat 7.1. I can still read the fonts, but they have changed between my first use and the second. The first time, I got the same fonts that I did w/ the most recent OOo's before 1.0. The 2nd time, I got the fonts that I used to get w/ old OOo's--eg Times New Roman that displays poorly and lacks any special characters. The problem occurred both when I chose the register-later option and the I'm-already-registered option while opening OOo for the 2nd time.
changed component to gsl, philipp, is at our known issue ?
pl->mh: I think so. The wrong font cache leads to taking a font that is not usable. psprint/source/fontmanager/fontcache.cxx rev 1.5 will fix this. Could the original submitter please confirm this ? The workaround is to delete <openoffice>/share/psprint/pspfontcache (and <openoffice>/user/psprint/pspfontcache if you made a user installation) after which the document should be ok again.
Deleting <openoffice>/user/psprint/pspfontcache from my user installation worked for the next run. I couldn't find <openoffice>/share/psprint/pspfontcache, though, and the next runs reverted back to the original problem. I did find a fontmetric directory as well as psprint.conf file in the -net installation directories.
I kind of fixed this problem for myself like this: I opened <openoffice>/share/psprint/pspfontcache in a text editor, took out all the contents, and saved the file (0 bytes). Then I write protected the file. I also put a copy of the file, also write-protected at <openoffice>/user/psprint/pspfontcache. Now I don't get this problem. This probably has some negative side effects, but it seems to work for me now. A better solution should of course be found.
ok, I tried that but it doesnt really fix it I think. Now, documents are displayed correctly .. ok but tie fonts in the menue are also misdisplayed. The file open dialog, the proferences and the autopilot where still unuseble
reassign to owner of selected component
Created attachment 1528 [details] the first one shows the main window ot OO writer after doing the workaround
Created attachment 1532 [details] this one shows the close dialog .. still no fonts there :( like in the open and preferences dialog
Ok. Here's a second hack (I know this is not any real solution, but anyway...): I modified the startup shell script for Writer to automatically kill any "pspfontcache" files. See the attachment for details. The same four lines can be added to all the other start-up scripts. It works for me... (If you already tried my first hack, you must write-enable those "pspfontcache" files first.)
Created attachment 1533 [details] Modified shell script that kills of "pspfontcache".
Created attachment 1534 [details] ok, everything works fine, it's enouth to modify the soffice script, because the other scripts call it
Ok, I get it working again, only by modifiing the soffice script, bit I have to create my own shortcute (heare on XFCE). I think the shortcuts für GNOME, KDE and CDE should become modifications too, because with that, its the samel problem as above
known issue. We are preparing a fix. It's not necessary to modify the soffice script. Just do a rm pspfontcache touch pspfontcache chmod 444 pspfontcache in the user/psprint directory of a user installation or in the share/psprint directory otherwise.
OK. The last solution is an elegant way of doing what I did in my first hack, which somehow did not work for René Marten. So maybe he needs my second hack, until the real patch is available.
*** Issue 4420 has been marked as a duplicate of this issue. ***
René, Bertilo, bost solutions must be equivalentby nature of the bug. Have you made a network installation (installing with -net or /net parameter) and lateron a user installation ? I just want to make sure that we are really talking about the same problem: Please try my suggested solution. Have a look in both places: <office_installed_as_root>/share/psprint/pspfontcache and <user_installation>/user/psprint/pspfontcache and apply the "rm -f xxx; touch xxx; chmod 444 xxx" stuff. By the way, do you have the RedHat 7.2 latin-2 fonts in the fontpath ? Check with "xset -q" for /usr/X11R6/lib/X11/fonts/latin2/Type1 or with "chkfontpath" (or with "/usr/sbin/chkfontpath") for the mentioned directory.
Created attachment 1541 [details] log of conversation with cp on this issue
Christof Pintaske: > Have you made a network installation (installing with -net or > /net parameter) and lateron a user installation ? I can't remember using any -net or /net parameter. I just launched the "install" and later "setup" programs (and was very impressed with what I got! ... until the bug bit...). > Have a look in both places: > <office_installed_as_root>/share/psprint/pspfontcache > <user_installation>/user/psprint/pspfontcache > and apply the "rm -f xxx; touch xxx; chmod 444 xxx" stuff. That works for me, as well as both my hacks. > By the way, do you have the RedHat 7.2 latin-2 fonts in the > fontpath ? All the fonts are there. They must be, mustn't they?, since the fonts works perfectly in Oo at the first launch. Why is this pspfontcache thing at all necessary? BTW, I use KDE 3.
pspfontcache caches font imformation. If you have e.g. 1000 font files on your system it cuts down startup time by 10 to 20 seconds.
I had a similar problem: I couldnt see any difference between normal fonts and bold one and the result was that this problem appeared in printed documents too. So I tried to remove and touch pspfontcache and I protected it from writing. Now it works fine
The font problem, in my installation of OOo 1.0 on a up-to-date RH 7.2, arises not only at the 2nd start but each time I use an administrative tools (spadmin). In particular, I installed OOo 1.0 (-net option) and at the 2nd start I noticed the font problem. So, I fixed it by using the Christof Pintaske's suggestion. Then, OOo 1.0 works fine. After that, I used spadmin and, then, the font problem arises again. I fixed it and I checked what happen if I use spadmin again. The result is that every time I use spadmin the font problem arises.
That is not suprising since spadmin uses the same code in this regard. Still the workaround (when will this damned single line of code make it to the download site ?!?) of making a 0 byte pspfontcache not writable fixes that problem.
I have the same problem on RedHat 7.2 with oo1.0. I dir rm, touch and chmod on share/psprint/pspfontcache. Still the normal fonts are ugly. Interestingly if I change chars to italics and save/exit and restart, the italics fornts remain anti-aliased!! Here is my fontlists: Current directories in font path: 1: /usr/X11R6/lib/X11/fonts/misc:unscaled 2: /usr/X11R6/lib/X11/fonts/75dpi:unscaled 3: /usr/X11R6/lib/X11/fonts/100dpi:unscaled 4: /usr/X11R6/lib/X11/fonts/misc 5: /usr/X11R6/lib/X11/fonts/Type1 6: /usr/X11R6/lib/X11/fonts/Speedo 7: /usr/X11R6/lib/X11/fonts/CID 8: /usr/X11R6/lib/X11/fonts/75dpi 9: /usr/X11R6/lib/X11/fonts/100dpi 10: /usr/X11R6/lib/X11/fonts/latin2/Type1 11: /usr/share/fonts/default/TrueType 12: /usr/share/fonts/default/Type1 13: /usr/share/AbiSuite/fonts 14: /usr/share/fonts/ja/TrueType 15: /usr/share/fonts/windowsttf ( all ttfonts from Windows 2000) Thanks, Prabir
*** Issue 4532 has been marked as a duplicate of this issue. ***
System: RH 7.2 /OOo 1.0 After making the hack (rm pspfontcache et al) i still have the problem, after printing. The bold and normal is printed as the same, with any type of font. bash-2.05# ll /openoffice/share/psprint/pspfontcache -r--r--r-- 1 vd vd 0 May 10 11:32 /openoffice/share/psprint/pspfontcache bash-2.05# ll /openoffice/user/psprint/pspfontcache -r--r--r-- 1 vd vd 0 May 10 22:48 /openoffice/user/psprint/pspfontcache My printer is on a network (with any other kind of writer it prints well).
The problem with printing the bold and normal fonts is relationed with the printer configuration under OO. After installing the fonts that i use under OO Writer in the printer configuration menu, the printing is alright.
*** Issue 4643 has been marked as a duplicate of this issue. ***
*** Issue 4726 has been marked as a duplicate of this issue. ***
I think Mandrake have addressed this problem with this patch: http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/contrib-SPECS/OpenOffice.org/openoffice-fontcache-copy-weight.patch
*** Issue 4441 has been marked as a duplicate of this issue. ***
Created attachment 1693 [details] Nice looking screen font before applying fix or patched libpsp641li.so
Created attachment 1694 [details] Distorted font raterization after applying patch 'rm pspfontcache'
I noticed that by applying any of the workarounds or patches so far offered, I get a markedly worse raterization of TT fonts. This effectively means I can either have a legible display of my work and all the printed output in bold font, or I can have a lousy rendition of the displayed fonts and correct selection of the font weights in my printed output. Of course, I was hoping for nicely displayed screen fonts and correct postscript output. Details: Mandraked 8.2 Linux with standard fonts. Added MS Web fonts using /usr/sbin/chkfontpath --add OpenOffice installed as root using ./setup -net. The user installs in /home/<user> using /opt/Openoffice.org1.0/setup User added MS Web fonts using /home/<user>/Openoffice.org1.0/spadmin /usr/sbin/chkfontpath says... Current directories in font path: 1: /usr/X11R6/lib/X11/fonts/misc:unscaled 2: /usr/X11R6/lib/X11/fonts/drakfont 3: /usr/X11R6/lib/X11/fonts/75dpi:unscaled 4: /usr/X11R6/lib/X11/fonts/100dpi:unscaled 5: /usr/X11R6/lib/X11/fonts/misc:unscaled 6: /usr/X11R6/lib/X11/fonts/Type1 7: /usr/X11R6/lib/X11/fonts/TTF 8: /usr/X11R6/lib/X11/fonts/Speedo 9: /usr/X11R6/lib/X11/fonts/pcf_drakfont:unscaled 10: /usr/X11R6/lib/X11/fonts/mdk:unscaled 11: /usr/share/fonts/default/Type1 12: /usr/share/fonts/ttf/decoratives 13: /usr/share/fonts/ttf/western 14: /usr/X11R6/lib/X11/fonts/drakfont/ttf <== MS Web fonts in here 15: /usr/java/j2re1.4.0/lib/fonts/ MS Web fonts are also in here due to spadmin copying them... /home/<user>/OpenOffice.org1.0/user/fonts
Charles, this is issue 2613. The problem is that OpenOffice.org due to some weird legal reasons doesn't enable grid fitting when rendering the TrueType fonts by itself. The XFree86 in all distros happily enables it and nobody seems to be scared by the legal reasons. <RANT MODE OFF> The reason why you see good looking fonts when the fontcache is broken is due to the fact that OpenOffice.org then doesn't use the fonts directly but as XFree86 fonts.
*** Issue 4911 has been marked as a duplicate of this issue. ***
*** Issue 5037 has been marked as a duplicate of this issue. ***
*** Issue 4521 has been marked as a duplicate of this issue. ***
*** Issue 4730 has been marked as a duplicate of this issue. ***
I had another problem: font selection dialogs didn't show correct font styles. For instance, there were only Italic and Bold-Italic styles for Avantgarde (no Regular nor Bold), and many other fonts didn't show any style at all. Applying the workaround given in this issue report (emptying and protecting pspfontcache files) resolved the issue. I write this for the case no one noted it was also a "listing" problem, and not only a "display" one.
*** Issue 5051 has been marked as a duplicate of this issue. ***
*** Issue 4457 has been marked as a duplicate of this issue. ***
I thought that it would be important to know that sometimes the file pspfontcache contain truncated or incomplete lines, like File: and a bit of the file name missing in the begining of a font definition group. I can't say if the other lines are correct because I don't know their meaning. All the way protecting the file to writing solves the problem.
can you send/attach such a corrupted file ?
Hi! I just want to update what happend in RedHat (7.3) Additional comment by tengchiangtsao@yahoo.com 2002-05-30 22:55:34 Hi! All, I found a work around !! Uninstall the above five packages (freetype, ttfonts, ttfonts-zh_TW, XFree86-xfs, and taipeifonts.)and then reinstall them all again with "rpm -i" (I didn't try "rpm -U"), then the problem is corrected !! Ya!!!!! Additional comment by llch@redhat.com 2002-05-31 00:17:16 We don't ship OpenOffice package yet so we don't offically support it. However we will try our best to resolve it. You can try the following steps and report if it helps or not: - reinstall those packages - edit /usr/share/fonts/zh_TW/TrueType/fonts.scale - delete any entries with ascii-0 charset - add bsmi00lp.ttf -Arphic Technology Co.-AR PL Mingti2L Big5-medium-r-normal--0-0-0- 0-p-0-iso8859-1 bkai00mp.ttf -Arphic Technology Co.-AR PL KaitiM Big5-medium-r-normal--0-0-0-0- p-0-iso8859-1 - save and exit - # cp /usr/share/fonts/zh_TW/TrueType/fonts.{scale,dir} - # service xfs restart Thanks Additional comment by tengchiangtsao@yahoo.com 2002-05-31 02:48:18 Yes, it is ascii-0 that is causing all these troubles. However, according to my bash history, if we use this perticular sequence to reinstall these packages, the ascii-0 won't show up. So, I didn't manually modify any fonts.scale or fonts.dir . Hope this can help. ------------------------------------------------------------------------------ 322 rpm -U --force ttfonts-zh_TW-2.11-5.noarch.rpm 323 rpm -q ttfm 324 exit 325 rpm -U ttfm-0.9.1-8.i386.rpm 326 ttfinfo 327 ./ttfinfo /usr/share/fonts/ttf/bkai00mu.ttf 328 ttfinfo /usr/share/fonts/ttf/bkai00mu.ttf 329 exit 330 /usr/sbin/ttfm.sh --list 331 exit 332 /usr/share/fonts/install/xttfm.ttfm 333 /usr/sbin/ttfm.sh --add /usr/share/fonts/zh_TW/TrueType/bkai00mp.ttf 334 /usr/sbin/ttfm.sh --add /usr/share/fonts/zh_TW/TrueType/bsmi00lp.ttf 335 exit 336 cd /etc/init.d 337 ls 338 ./xfs restart 339 exit 340 /usr/sbin/ttfm.sh --remove bkai00mp.ttf 341 /usr/sbin/ttfm.sh --remove bsmi00lp.ttf 342 /usr/sbin/ttfm.sh --list 343 rpm -e ttfm 344 exit 345 rpm -U --force /mnt/cdrom/RedHat/RPMS/freetype-2.0.3-7.i386.rpm 346 rpm -U --force --nodeps /mnt/cdrom/RedHat/RPMS/freetype-2.0.3-7.i386.rpm 347 ln -s /usr/lib/libfreetype.so.6.0.1 /usr/lib/libfreetype.so.6.3.0 348 ls /usr/lib/libfreetype.so.6.3.0 349 exit 350 cd /usr/lib 351 ls *.6.3 352 ls *.6.3* 353 rm libfreetype.so.6.3.0 354 rpm -U /mnt/cdrom/RedHat/RPMS/freetype-2.0.9-2.i386.rpm 355 exit 356 rpm -U --force --nodeps /mnt/cdrom/RedHat/RPMS/freetype-2.0.3-7.i386.rpm 357 cd /usr/lib 358 ln -s libfreetype.so.6.0.1 libfreetype.so.6.3.0 359 exit 360 cd /etc/init.d 361 ./xfs restart 362 exit 363 rpm -U /mnt/cdrom/RedHat/RPMS/freetype-2.0.9-2.i386.rpm 364 rm /usr/lib/libfreetype.so.6.3.0 365 rpm -U /mnt/cdrom/RedHat/RPMS/freetype-2.0.9-2.i386.rpm 366 rpm -U --nodeps --force /mnt/cdrom/RedHat/RPMS/freetype-2.0.9-2.i386.rpm 367 exit 368 cd /etc/init.d/ 369 ./xfs restart 370 exit 371 init 3 372 init 5 373 rpm -e ttfonts-zh_TW 374 rpm -e ttfonts 375 rpm -e --nodeps ttfonts 376 rpm -e taipeifonts 377 rpm -e freetype 378 rpm -e --nodeps freetype 379 rpm -e --nodeps XFree-xfs 380 rpm -q XFree86-xfs 381 rpm -e --nodeps XFree86-xfs 382 exit 383 mount /mnt/cdrom 384 ls /mnt/cdrom/ 385 ls /mnt/cdrom/RedHat/RPMS/ 386 rpm -i /mnt/cdrom/RedHat/RPMS/XFree86-xfs-4.2.0-8.i386.rpm 387 rpm -i /mnt/cdrom/RedHat/RPMS/ttfonts-1.0-9.noarch.rpm 388 rpm -i /mnt/cdrom/RedHat/RPMS/freetype-2.0.9-2.i386.rpm 389 rpm -i /mnt/cdrom/RedHat/RPMS/ttfonts-1.0-9.noarch.rpm 390 umount /mnt/cdrom 391 eject 392 mount /mnt/cdrom/ 393 umount /mnt/cdrom 394 eject 395 mount /mnt/cdrom/ 396 rpm -i /mnt/cdrom/RedHat/RPMS/taipeifonts-1.2-16.noarch.rpm 397 rpm -i /mnt/cdrom/RedHat/RPMS/ttfonts-zh_TW-2.11-10.noarch.rpm 398exit 399 umount /mnt/cdrom 400 exit 401 ls 402 cd /etc/init.d 403 ls 404 ps -ef | grep gdm 405 kill 1415 406 ./xfs restart -------------------------------------------------------------------------------
*** Issue 4635 has been marked as a duplicate of this issue. ***
Please forget me if this is a repetition. I tried the proposed workaround (cd ...user/psprint; rm pspfontcache; touch pspfontcache; chmod 444 pspfontcache) and... now openoffice refuses to start for me. (0)pern:~% lib/OpenOffice.org1.0/soffice zsh: 13329 abort lib/OpenOffice.org1.0/soffice (0)pern:~% lib/OpenOffice.org1.0/setup zsh: 13220 segmentation fault lib/OpenOffice.org1.0/setup Removing again pspfontcache does not work. Same errors. I will reinstall all things, I need openoffice... what could have been happened?
please try to install the proposed fix instead and install http://gsl.openoffice.org/servlets/ProjectDownloadList?action=download&dlID=48
That link does not work for me; it seems it try to dnload a .so file (a dll? what am I supposed to do, put it in some place instead of another one? Sorry to ask idiocies...) but it gave an error "not found". By the way, I managed to resolve the thing. It was a font problem in /usr/share/fonts/Type1; look at issue #4468 ...now it is working. Thanks!
It should have downloaded a new libpsp641li.so that you would have to put into the <office>/program directory. I'm not sure why the link does not work, but you can go to the files section of gsl.openoffice.org directly; perhaps the cgi works better then.
I've applied the new libpsp641li.so to the programs directory, deleted all pspfontcache files, and now my printing works perfectly (thanks). The problem now (and it has been noted by many others) that the screen handling of fonts in a document is so poor that OpenOffice.org is very annoying to use. I have read about and understand the problem with Apple's patents on TrueType rendering, however, when the font cache was broken, my screen handling was great, now that the font cache is fixed, the screen handling is poor. Why not allow the default handler render the screen as it does when then font cache is broken? Secondly, does StarOffice 6.0 also have the same problem? I would be more than happy to purchase StarOffice if this problem is fixed.
StarOffice comes with additional quality ttf fonts; the font rendering code is the same though. I suspect the difference you see is because you now don't get the bold fonts per default (which is correct) and the bold fonts looked a little rounder.
James, can you provide a screenshot ? something like befor -- after ? Can you explain in more detail what you mean by "poor". I just want to make cristal clear that we share the same idea about the problem.
Created attachment 2028 [details] Two clips from screenshots showing before/after libpsp641li.so upgrade
Looking at the attachment above (id=2028). My question is why does OpenOffice.org try to render the screen fonts internally when the default screen handler does a much better job? Or at least why not give the user an option to use the default screen handler (without breaking pspfontcache)?
there's a couple of issues with your screenshot. in the first screenshot you use plain X fonts, whereas in the second you use fonts rastered by freetype. Most people prefer the antialiasing of fonts. That's why it is in. Rendering the fonts ourselfs has the benefit of giving more control over metrics, allowing for rotation on all displays, vertical writing, complex text layout, ... We are looking into the quality of rasterization, but that's a difficult issue and I cannot promise a quick solution. You can get rid of the antialiazing by unchecking "Tools -> Options -> OpenOffice -> View -> Screenfont antialiasing" the problem with the pspfontcache will be fixed in the next release
Actually, in the first example, the TrueType fonts are "hinted" using freetype (Standard with RedHat Linux 7.3). Fonts that are smaller than 16 point are not anti-aliased, because antialiasing small fonts produces very bad results (that's why hinting is important). The way an application looks is very important to end users, thus the success of Microsoft and Apple. If I increase the size of the fonts, they do anti-alias. In fact at 32 point both examples look virtually identical. However, I can't see typing up all documents at 32 point just to make the screen look decent. I do understand it is very difficult to determine if someone has their X setup correctly to handle the font rendering of OOo. But, I would ask again . . . why not allow the user to choose between X rendering or OOo rendering of fonts? Leave OOo rendering on by default, that should work for the newbies, but the rest of us should have the option of having a decent looking screen. The reason that I am so determined on this point is that I would like to shift many of our systems at work from Windows/MS-Office to Linux/StarOffice. At a staff meeting I demonstrated the Linux/OpenOffice.org option, and was simply told that the display quality was unacceptable and we can't switch until it can be fixed. So, this is a show-stopper for me.
Please understand that this bug does not deal with rendering quality but with pspfontcache !!! Rendering quality is discussed in http://l10n.openoffice.org/issues/show_bug.cgi?id=2613 please have a look at it.
ok now it works for me after 1. Removing the pspfontcache file and creating a new one without writing rights 2. copying sone trueType fonts into /<OOo installation directory>/share/fonts/truetype After That it works for me. I thing with or withot the "Hack" I've never applied the patch mentioned in another posting .. But now it works for me I think the problem is, that sometimes OOo doesn't find the TrueType fonts used bei the X server .. if they were installed .. If there are some TrueType Fonts in .../share/fonts/truetype/ everything works . I've recognized, that this is a problem with the pspfontcache and the font path ... But I think, if the nessesary fonts were in ... /share/fonts/truetype/ than it works with or without reinstalling the xfs-, font- and freetype packages ..
*** Issue 5603 has been marked as a duplicate of this issue. ***
*** Issue 5595 has been marked as a duplicate of this issue. ***
*** Issue 5468 has been marked as a duplicate of this issue. ***
*** Issue 5703 has been marked as a duplicate of this issue. ***
I have tried to fix the problem on my system by: rm pspfontcache touch pspfontcache chmod 444 pspfontcache in both my user directory and the central OpenOffice.org share/psprint/ directory. This didn't fix the problem of fonts printing bold. So I then replaced libpsp641li.so with the patched version, but again this had no effect. (Yes, I did close down OpenOffice.org writer in between times.) So, neither fix helps to make my print output look like that from StarOffice 5.2 using the same font. I am running Linux.
Please try OpenOffice.org 1.0.1
I installed OpenOffice.org 1.0.1 as Christof Pintaske suggested, but it makes no difference - it still prints bold, unlike StarOffice 5.2. (It also looks much bolder on screen than StarOffice 5.2. This also is the same as version 1.0.0.)
*** Issue 6228 has been marked as a duplicate of this issue. ***
*** Issue 6484 has been marked as a duplicate of this issue. ***
*** Issue 4889 has been marked as a duplicate of this issue. ***
closed