https://bugs.freedesktop.org/show_bug.cgi?id=62447
Michael Meeks <michael.me...@novell.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #29 from Michael Meeks <michael.me...@novell.com> ---
> Well, I have manage to reproduce it again, after 1 day. But the problem with
> this was when I executed "SAL_USE_VCLPLUGIN=gen soffice", LibreOffice 3.5 was
> the one to be opened, and not 4.0.
Drat - of course, there could be any number of issues with 3.5 that are hard to
track and fix, so ... we love testing of 4.0 :-)
> Then, I could open LibreOffice 4.0, and of course, it looked like the old
> Windows theme... but nothing else.
Good - I wonder if you could make it go wrong like that ? if you cannot, but
you can with the KDE backend, then I suspect some issue with that backend -
but it's unlikely of course.
> Should I wait with this "theme" after the problem appears again?
Just waiting is not the best approach ;-) what is really needed is finding a
way to trigger the problem that is quick - so with 10 steps from a blank (or
attached) document the problem can be triggered.
If it takes a long time to do - it's either memory corruption; or - you have
some cron-job / rsync or something that touches your font configuration (I
guess) which makes this a dup of bug#60565 :-)
Thanks !
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
