Jump to content
dil_bert

issues with Libreoffice

Recommended Posts

[martin-pc martin]# --writer
bash: --writer: Kommando nicht gefunden.
[martin-pc martin]# start lo
bash: start: Kommando nicht gefunden.
[martin-pc martin]# start calc
bash: start: Kommando nicht gefunden.
[martin-pc martin]# start --calc
bash: start: Kommando nicht gefunden.
[martin-pc martin]# libreoffice --calc
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0

 

Unable to create io-slave. Can not create socket for launching io-slave for protocol 'file'.

 

 

Share this post


Link to post
Share on other sites

hello dear requnix

many many thanks for the quick reply great to hear from you... i am very glad.

well that is a great hint. - i think it is a good way not to do so,.

btw: see - i have tried it another time ..../due to the fact that it did not want to start  at all :  see the result:

 

martin@martin-pc ~]$ soffice run
QPaintDevice: Cannot destroy paint device that is being painted
[martin@martin-pc ~]$ soffice run
QPaintDevice: Cannot destroy paint device that is being painted
[martin@martin-pc ~]$  journalctl
-- Logs begin at Thu 2019-03-28 14:41:26 CET, end at Fri 2019-04-19 19:58:58>
Mär 28 14:41:26 martin-pc kernel: microcode: microcode updated early to revi>
Mär 28 14:41:26 martin-pc kernel: Linux version 4.19.23-1-MANJARO (builduser>
Mär 28 14:41:26 martin-pc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1>
Mär 28 14:41:26 martin-pc kernel: KERNEL supported cpus:
Mär 28 14:41:26 martin-pc kernel:   Intel GenuineIntel
Mär 28 14:41:26 martin-pc kernel:   AMD AuthenticAMD
Mär 28 14:41:26 martin-pc kernel:   Centaur CentaurHauls
Mär 28 14:41:26 martin-pc kernel: x86/fpu: Supporting XSAVE feature 0x001: '>
Mär 28 14:41:26 martin-pc kernel: x86/fpu: Supporting XSAVE feature 0x002: '>
Mär 28 14:41:26 martin-pc kernel: x86/fpu: Supporting XSAVE feature 0x004: '>
Mär 28 14:41:26 martin-pc kernel: x86/fpu: xstate_offset[2]:  576, xstate_si>
Mär 28 14:41:26 martin-pc kernel: x86/fpu: Enabled xstate features 0x7, cont>
Mär 28 14:41:26 martin-pc kernel: BIOS-provided physical RAM map:
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x0000000000000000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x0000000000100000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x0000000020000000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x0000000020200000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x0000000040000000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x0000000040200000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bac0c000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bac0d000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bad20000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bad48000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bad78000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bad8e000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bad94000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bad95000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bad96000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000badb8000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000badc6000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bade8000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bae35000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bafe8000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000baffd000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000bb000000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000fed18000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000ff980000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x00000000ffd80000-0x00000>
Mär 28 14:41:26 martin-pc kernel: BIOS-e820: [mem 0x0000000100000000-0x00000>
Mär 28 14:41:26 martin-pc kernel: NX (Execute Disable) protection: active
Mär 28 14:41:26 martin-pc kernel: efi: EFI v2.00 by American Megatrends
Mär 28 14:41:26 martin-pc kernel: efi:  ACPI 2.0=0xbaffff98  SMBIOS=0xbadb62>
Mär 28 14:41:26 martin-pc kernel: SMBIOS 2.6 present.
Mär 28 14:41:26 martin-pc kernel: DMI: ASUSTeK Computer Inc. K54L/K54L, BIOS>
Mär 28 14:41:26 martin-pc kernel: tsc: Fast TSC calibration using PIT
Mär 28 14:41:26 martin-pc kernel: tsc: Detected 2195.012 MHz processor
Mär 28 14:41:26 martin-pc kernel: e820: update [mem 0x00000000-0x00000fff] u>
Mär 28 14:41:26 martin-pc kernel: e820: remove [mem 0x000a0000-0x000fffff] u>
Mär 28 14:41:26 martin-pc kernel: last_pfn = 0x13f800 max_arch_pfn = 0x40000>
Mär 28 14:41:26 martin-pc kernel: MTRR default type: uncachable
Mär 28 14:41:26 martin-pc kernel: MTRR fixed ranges enabled:
Mär 28 14:41:26 martin-pc kernel:   00000-9FFFF write-back
Mär 28 14:41:26 martin-pc kernel:   A0000-BFFFF uncachable
Mär 28 14:41:26 martin-pc kernel:   C0000-CFFFF write-protect
Mär 28 14:41:26 martin-pc kernel:   D0000-DFFFF uncachable
Mär 28 14:41:26 martin-pc kernel:   E0000-E7FFF write-through
Mär 28 14:41:26 martin-pc kernel:   E8000-FFFFF write-protect
Mär 28 14:41:26 martin-pc kernel: MTRR variable ranges enabled:
Mär 28 14:41:26 martin-pc kernel:   0 base 000000000 mask F80000000 write-ba>
Mär 28 14:41:26 martin-pc kernel:   1 base 080000000 mask FC0000000 write-ba>
Mär 28 14:41:26 martin-pc kernel:   2 base 0BC000000 mask FFC000000 uncachab>
Mär 28 14:41:26 martin-pc kernel:   3 base 0BB000000 mask FFF000000 uncachab>
Mär 28 14:41:26 martin-pc kernel:   4 base 100000000 mask FC0000000 write-ba>
Mär 28 14:41:26 martin-pc kernel:   5 base 13F800000 mask FFF800000 uncachab>
Mär 28 14:41:26 martin-pc kernel:   6 base 0FFC00000 mask FFFC00000 write-pr>
Mär 28 14:41:26 martin-pc kernel:   7 disabled
Mär 28 14:41:26 martin-pc kernel:   8 disabled
Mär 28 14:41:26 martin-pc kernel:   9 disabled
lines 51-75

 

dear requinix - well i would be more than happy if you can give me a helping hand.

 

many many thanks for all you did so far!!

 

i am very glad to be a part of this great community,

 

greetings

dilbert

 

Share this post


Link to post
Share on other sites

Help for what? I told you not to run it from the command line, which you're still doing, but now you've posted part of your kernel log which I can only assume you're doing for a reason that I can't figure out.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.