bvidinli@bvidinli-yenihdd:~$ uname -a
Linux bvidinli-yenihdd 2.6.28-12-generic #43-Ubuntu SMP Fri May 1
19:27:06 UTC 2009 i686 GNU/Linux
bvidinli@bvidinli-yenihdd:~$
while debug is turned on, i tried to run kword, it started after print
on console enormous lines of debug messages. i saw kword interface, it
started..
But,
After having log, i re-run kdebugdialog, deselect all, applied,
then, i tried to start kword, it still prints debug messages... That
is, debug is not turned off.
I checked again in kdebugdialog that all turned off...
So, last status:
on command line: kword and kspread starts up by printing many log
messages, so, they startup very slow
from menu: they start very slow...
See you,
On Mon, Jun 8, 2009 at 10:36 AM, Harald Sitter<email address hidden> wrote:
> Well, lets try something else then.
>
> Run
>
> kdebugdialog
>
> and make sure everything is turned on. Then run
>
> kbuildsycoca4 > sycoca.log 2>&1
>
> that will create a file named sycoa.log, please attach it to this bug.
> If the problem is that kbuildsycoca4 fails to parse something, then it should show up in the log. If it is not, then we have quite a drag at our hands :D
>
> --
> kword fails to start
> https://bugs.launchpad.net/bugs/381599
> You received this bug notification because you are a direct subscriber
> of the bug.
>
bvidinli@ bvidinli- yenihdd: ~$ kword ::findServiceBy DesktopPath: esktopPath: kwordpart.desktop not found" ::findServiceBy DesktopPath: esktopPath: Office/ kword.desktop not found" bvidinli- yenihdd: ~$ kdebugdialog bvidinli- yenihdd: ~$ kdebugdialog bvidinli- yenihdd: ~$ kbuildsycoca4 > sycoca.log 2>&1 bvidinli- yenihdd: ~$
kword(22663) KServiceFactory
"findServiceByD
kword(22663) KServiceFactory
"findServiceByD
bvidinli@
bvidinli@
bvidinli@
bvidinli@
bvidinli@ bvidinli- yenihdd: ~$ uname -a bvidinli- yenihdd: ~$
Linux bvidinli-yenihdd 2.6.28-12-generic #43-Ubuntu SMP Fri May 1
19:27:06 UTC 2009 i686 GNU/Linux
bvidinli@
while debug is turned on, i tried to run kword, it started after print
on console enormous lines of debug messages. i saw kword interface, it
started..
But,
After having log, i re-run kdebugdialog, deselect all, applied,
then, i tried to start kword, it still prints debug messages... That
is, debug is not turned off.
I checked again in kdebugdialog that all turned off...
So, last status:
on command line: kword and kspread starts up by printing many log
messages, so, they startup very slow
from menu: they start very slow...
See you,
On Mon, Jun 8, 2009 at 10:36 AM, Harald Sitter<email address hidden> wrote: /bugs.launchpad .net/bugs/ 381599
> Well, lets try something else then.
>
> Run
>
> kdebugdialog
>
> and make sure everything is turned on. Then run
>
> kbuildsycoca4 > sycoca.log 2>&1
>
> that will create a file named sycoa.log, please attach it to this bug.
> If the problem is that kbuildsycoca4 fails to parse something, then it should show up in the log. If it is not, then we have quite a drag at our hands :D
>
> --
> kword fails to start
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>