On 28 Nov 2016 12:01 pm, "Ed Greshko" wrote:
>
>
>
> On 11/28/16 19:11, James Hogarth wrote:
> > You're right it is out of scope as Apache OpenOffice has never been in
> > Fedora, and given the state of the project I doubt it ever will be.
>
> Yes, but I've never been too much of a fan of telling
On 11/28/16 19:11, James Hogarth wrote:
> You're right it is out of scope as Apache OpenOffice has never been in
> Fedora, and given the state of the project I doubt it ever will be.
Yes, but I've never been too much of a fan of telling people what they should
and
shouldn't run. And I like a c
On 28 November 2016 at 07:26, Ed Greshko wrote:
>
>
> On 11/28/16 14:42, Ed Greshko wrote:
>> Ooops... Forget this last try I was on an F25 VM.
>>
>> Going to do same on F24.
>>
>> Wait a bit
>
> Well the core dump was the same in F24 as F25.
>
> I have found this
> https://community
On 11/28/16 14:42, Ed Greshko wrote:
> Ooops... Forget this last try I was on an F25 VM.
>
> Going to do same on F24.
>
> Wait a bit
Well the core dump was the same in F24 as F25.
I have found this
https://community.spiceworks.com/topic/1808558-openoffice-4-1-2-4-1-3-crashed-on-
Ooops... Forget this last try I was on an F25 VM.
Going to do same on F24.
Wait a bit
On 11/28/16 14:36, Ed Greshko wrote:
> Oh, FWIW, I have a VM. So, I erases libreoffice from my system and installed
> Apache_OpenOffice_4.1.3.
--
You're Welcome Zachary Quinto
___
On 11/28/16 13:10, Stephen Davies wrote:
> Looks as if you are running libreoffice rather than openoffice (from Apache).
>
> I also suspected the LD_LIBRARY_PATH but the root version is the same.
Oh, FWIW, I have a VM. So, I erases libreoffice from my system and installed
Apache_OpenOffice_4.1.
On 11/28/16 13:10, Stephen Davies wrote:
> Looks as if you are running libreoffice rather than openoffice (from Apache).
>
> I also suspected the LD_LIBRARY_PATH but the root version is the same.
Oh, you are right. I am running libreoffice 5.2 as supplied by Fedora Project.
I missed
that you
On 28/11/16 15:32, Ed Greshko wrote:
On 11/28/16 12:22, Stephen Davies wrote:
If I run /usr/bin/soffice as root, it works and the Office menu appears.
If I do the same as myself (sh -x /usr/bin/soffice), I get:
+ SAL_ENABLE_FILE_LOCKING=1
+ export SAL_ENABLE_FILE_LOCKING
++ pwd
+ sd_cwd=/home
On 11/28/16 12:22, Stephen Davies wrote:
> If I run /usr/bin/soffice as root, it works and the Office menu appears.
> If I do the same as myself (sh -x /usr/bin/soffice), I get:
>
> + SAL_ENABLE_FILE_LOCKING=1
> + export SAL_ENABLE_FILE_LOCKING
> ++ pwd
> + sd_cwd=/home/scldad
> + sd_res=/usr/bin
On 28/11/16 14:26, Ed Greshko wrote:
On 11/28/16 09:55, Stephen Davies wrote:
Following an upgrade from F23 to F24 yesterday, an attempt to start Open
Office gives the following in /var/log/messages (worked fine under F23):
Nov 28 12:22:13 mustang kwin_x11: QXcbWindow: Unhandled client messag
On 11/28/16 09:55, Stephen Davies wrote:
> Following an upgrade from F23 to F24 yesterday, an attempt to start Open
> Office gives the following in /var/log/messages (worked fine under F23):
>
> Nov 28 12:22:13 mustang kwin_x11: QXcbWindow: Unhandled client message:
> "_NET_CURRENT_DESKTOP"
> Nov
Following an upgrade from F23 to F24 yesterday, an attempt to start Open
Office gives the following in /var/log/messages (worked fine under F23):
Nov 28 12:22:13 mustang kwin_x11: QXcbWindow: Unhandled client message:
"_NET_CURRENT_DESKTOP"
Nov 28 12:22:24 mustang kwin_x11: QXcbConnection: XCB
12 matches
Mail list logo
