Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 45039 - openoffice (ximian at least) does not display normal bullets
Summary: openoffice (ximian at least) does not display normal bullets
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
: 46218 47789 48103 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-03-18 10:29 UTC by rattus
Modified: 2004-05-07 22:28 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rattus 2004-03-18 10:29:00 UTC
That's basically it.  They are not displayed.  Everything else seems to be fine, and exported documents look right in windows.

Not being able to see formatting kinda sucks though and makes it an non-viable product until it's fixed.

Reproducible: Always
Steps to Reproduce:
1. xoowriter
2. enter some bulleted text
3.
Actual Results:  
teh problem happened :(

Expected Results:  
it should have displayed bulleted text.

I did various searches in the openoffice known bugs and received various hits,
however they're largely dismissed as a fixed problem with the function editor
which is total crap.

Hopefully by reporting it here, it might get some action.

Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.6.4)
=================================================================
System uname: 2.6.4 i686 Intel(R) Pentium(R) M processor 1400MHz
Gentoo Base System version 1.4.3.13p1
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe -fstack-protector"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe -fstack-protector"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.netnitco.net http://mirrors.tds.net/gentoo
ftp://mirrors.tds.net/gentoo ftp://gentoo.ccccom.com http://gentoo.ccccom.com"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome
gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg
ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime
readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib"
Comment 1 Andreas Proschofsky (RETIRED) gentoo-dev 2004-03-18 10:57:45 UTC
Which version of openoffice-ximian are you using? This should be fixed with recent versions
Comment 2 Andreas Proschofsky (RETIRED) gentoo-dev 2004-03-29 05:31:37 UTC
Closing this, need further info, should be fixed in recent versions anyway...
Comment 3 rattus 2004-03-29 08:54:07 UTC
That sounds bogus.

After reading the bugs at the main openoffice site, other people were reporting this as well and getting fobbed off as "oh.  it's a windows issue fixed two versions ago."

no.  it's not a windows issue, and it wasn't fixed last week nor two months ago.

I even turned off all possibly interesting CFLAGS with no change in behavior.  Perhaps this is an issue with some of the bitmap creation?  I have no idea. :(
Comment 4 rattus 2004-03-29 09:03:29 UTC
version is 1.1.0 I guess.

it's the current one with ~xf86 enabled.
Comment 5 Andreas Proschofsky (RETIRED) gentoo-dev 2004-03-29 13:37:58 UTC
The current version of openoffice-ximian is 1.1.51, I closed the bug because i asked you for further info and you didn't provide it, also I didn't say that it is a bug with the windows version, it is indeed a known problem, but one which SHOULD be fixed with recent versions in our build. If you provide your version number we can look further into it.

One thing you could try, start xfs and see if that helps:

/etc/init.d/xfs start

You will have to close and reopen oox afterwards
Comment 6 rattus 2004-03-29 14:34:12 UTC
qpkg says that I'm hoppin with 1.1.51.

xfs caches everything nicely.  app closed and re-opened -- to no effect.

oh well.  if it's still a known problem, that's good enough for me.  it's just not fixed.

if there's any more information I can provide, let me know.  I think that the initial version information was bitbucked somehow, so I was slow on the uptake on that one.
Comment 7 Mike Auty (RETIRED) gentoo-dev 2004-04-01 16:18:18 UTC
Perhaps bug 46218 is a duplicate of this bug?  As mentioned there, installing the fonts from http://ooo.ximian.com/openoffice/fonts/ seemed to fix the problem.  I'm not certain whether this is a ximian specific problem or not.  Please note these fonts are jiggered versions of the original opensymbol font.  You can read more about them at:

http://lists.ximian.com/archives/public/openoffice/2003-October/000116.html
Comment 8 rattus 2004-04-01 17:07:08 UTC
looks promising.

I don't think I'm up to submitting a patch though.
Comment 9 Andreas Proschofsky (RETIRED) gentoo-dev 2004-04-01 22:13:34 UTC
@Mike Auty: Where did you install the font to? 

Because this is exactly the font that IS installed during the emerge process

It's there:
/usr/X11R6/lib/X11/fonts/truetype/opens___.ttf
Comment 10 Mike Auty (RETIRED) gentoo-dev 2004-04-02 03:20:05 UTC
I installed it in my ~/.fonts local directory.  I've just emerged 1.1.52 and it still has the same problem.  If I move opens___.ttf out of my .fonts directory I get boxes, if I move it back in, bullet points.  It seems that my /usr/X11R6/lib/X11/fonts/truetype does contain exactly the same font file opens___.ttf.

Could this be some kind of font configuration problem?  The fonts.dir file contains no references to the OpenSymbol font, but does for all the other fonts deposited there.  My XF86Config contains the following:

    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/truetype/"
    # FontPath   "/usr/share/fonts/unifont/"
    FontPath   "/usr/share/fonts/corefonts"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"

and my /etc/fonts/local.conf contains:

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<!-- /etc/fonts/local.conf file for local customizations -->
<fontconfig>
<!-- <dir>/usr/X11R6/lib/X11/fonts/CID</dir>
<dir>/usr/X11R6/lib/X11/fonts/Speedo</dir>
<dir>/usr/X11R6/lib/X11/fonts/TTF</dir>
<dir>/usr/X11R6/lib/X11/fonts/UKR</dir>
<dir>/usr/X11R6/lib/X11/fonts/cyrillic</dir>
<dir>/usr/X11R6/lib/X11/fonts/misc</dir> -->
<!--
  Enable sub-pixel rendering
        <match target="font">
                <edit name="rgba" mode="assign"><const>rgb</const></edit>
        </match>
-->
<dir>/usr/share/fonts/corefonts</dir>
</fontconfig>

Note that everything is commented out except for the /usr/share/fonts/corefonts line.

The XFS service is not running, and has not been needed by any other program, for instace after installing corefonts, all programs located the corefonts, so I wouldn't mind finding a solution that avoids having to run it.

I don't know much about font configurations on X, but I'll be happy to try out anything anyone would like.
Comment 11 Andreas Proschofsky (RETIRED) gentoo-dev 2004-04-15 11:46:56 UTC
*** Bug 47789 has been marked as a duplicate of this bug. ***
Comment 12 Andreas Proschofsky (RETIRED) gentoo-dev 2004-04-15 11:48:08 UTC
*** Bug 46218 has been marked as a duplicate of this bug. ***
Comment 13 rattus 2004-04-15 12:55:01 UTC
this was corrected in 1.1.52 btw.
Comment 14 Mike Auty (RETIRED) gentoo-dev 2004-04-15 13:49:59 UTC
Rattus,

As mentioned in comment #10 I'm still experiencing this problem with 1.1.52 (unless it's been patched and the ebuild number not bumped).  I can reproduce it quite easily by removing the opens___.ttf from my ~/.fonts directory and then bulleted lists no longer work.  Could it be that having the font installed locally when I emerged it may have stopped it being installed globally?  Can anyone else verify whether the bug still exists or not?  Anyone have any ideas what might be going on?  I've provided all the details I have in comment #10, but if there's anything specific anyone else wants to know, please just ask...
Comment 15 Mike Auty (RETIRED) gentoo-dev 2004-04-15 13:56:17 UTC
Actually, hmmm, it may still be going wrong for me because I've recently upgraded to xorg-x11, which uses the new font paths /usr/share/fonts.  So I'm no longer able to tell whether the problem is an openoffice-ximian one or not, someone else will have to help diagnose this one.  I also don't know how it's decided where to put the font, but if it doesn't work with xorg-x11 then that's another bug to file (sigh).
Comment 16 Andreas Proschofsky (RETIRED) gentoo-dev 2004-04-15 14:23:57 UTC
This is not fixed for everyone so reopening again
Comment 17 Andreas Proschofsky (RETIRED) gentoo-dev 2004-04-16 22:42:19 UTC
*** Bug 48103 has been marked as a duplicate of this bug. ***
Comment 18 Andreas Proschofsky (RETIRED) gentoo-dev 2004-05-07 11:46:35 UTC
I've changed the install path of the fonts in recent version of oox (1.1.54 and 1.1.55), do you still get the problem?
Comment 19 Mike Auty (RETIRED) gentoo-dev 2004-05-07 13:18:20 UTC
Ok, so using Openoffice-ximian 1.1.54, with xorg-x11 the bullet points seem to be working fine for me now.  Thanks!
Comment 20 Andreas Proschofsky (RETIRED) gentoo-dev 2004-05-07 13:23:08 UTC
Ah the joys of self healing problems! 

;-)
Comment 21 rattus 2004-05-07 22:28:18 UTC
well it has been like a month and four releases since I reported this bug. :)