Briefly describe your issue below:
What version of Parrot are you running? 4.7, security edition, amd64 (originally installed 4.5.1 and updated to 4.7 via rolling release)
What method did you use to install Parrot? Debian Standard
Configured to multiboot with other systems? yes, with windows 10 (ugh)
If there are any similar issues or solutions, link to them below:
It shouldnt ideally.
But on my machines i dont need to run it as root for it to work.
There are a few posts on other forums that you could try:
https://superuser.com/questions/564534/only-root-user-is-able-to-open-libreoffice
They more or less say the same thing. It looks like if you start libreoffice as root, it generates a config under the root user, then whenever it tries to load that config as a standard user, it fails (If your having the same problem).
Briefly describe your issue below:
I ran full Parrot updates today. No Libreoffice apps will start now. I don’t know if this is due to the updates, or when the problem began.
When I try to start any Libreoffice app, it shows up on the taskbar for a few seconds, and then disappears.
Is there a logfile somewhere that I can pull to investigate?
I have not asked Libreoffice support yet.
thanks
What version of Parrot are you running? (include version, edition, and architecture)
4.18.0-parrot10-amd64
What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
.iso
Configured to multiboot with other systems? (yes / no)
no
If there are any similar issues or solutions, link to them below:
If there are any error messages or relevant logs, post them below:
libreoffice issue (latest)
If there are any error messages or relevant logs, post them below:
“Final linking of kernel DynamicKernal failed” -or something like that. I unfortunately failed to note the EXACT message before I fixed it, but it’s close enough.
dmknght
(Nông Hoàng Tú)
October 27, 2019, 6:04pm
2
Firejail problem from my exp. Can you try run this command in terminal firejail --noprofile libreoffice
?
RedRuby
(Jessica)
October 27, 2019, 6:29pm
3
Hello @happyoutkast
As @dmknght said, Its most probably a sandbox issue.
Try this if the issue still persist, It may be a kernel compatibility issue as suggested by the (supposedly) name of the description of the error :
Let us know how it goes!
Cheers!
system
(system)
Closed
February 24, 2020, 6:29pm
4
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.