public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] koffice 1.1.1
Date: Thu, 20 Dec 2001 19:15:30 +0200	[thread overview]
Message-ID: <0GON00I5SL60HC@mxout2.netvision.net.il> (raw)
In-Reply-To: <20011220065457.095f0f17.erichey2@attbi.com>

On Thursday 20 December 2001 15:54, you wrote:
> Don't know if any of this is an ebuild problem or just a crappy
> product:
>
> 1) The ebuild installed without a complaint but rendered my system
> unstable - total lockup of X/XFCE.  Some damage to my sylpheed files
> (all files in my current folder marked unread), but ext3 successfully
> recovered from the glitch.
Hi,

Generally speaking, kword works great here and on other computer too, so it's 
not a generic problem.

Your optimization settings may be to blame, as koffice currently has problems 
with some settngs (the ebuild tries to compensate). What are your CXXFLAGS?


> 2) Kword has lots of menus grayed out and
> doesn't work very well (typical kword stuff) 
I don't see anything like that here. Many menus are indeed disabled, but they 
shuold be - frame and table-related menus when there is no table or frame in 
existence, etc. What menu commands are disabled for you that should be 
enabled?

> 3) Kword is compiled with
> debugging crap which you see if you do 'kword &' from a console.
I've tried it and there are indeed a lot of msgs. I'm not sure that's debug 
level output though, debug may produce even more :-) We don't pass explicit 
--disable-debug to kde configures but that's supposed to be the deafult, so I 
don't see what can be done about this.

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel


      reply	other threads:[~2001-12-20 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20 13:54 [gentoo-dev] koffice 1.1.1 Collins Richey
2001-12-20 17:15 ` Dan Armak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0GON00I5SL60HC@mxout2.netvision.net.il \
    --to=danarmak@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox