[opensuse-support] LibreOffice cannot be started by normal user but no problem by root
Hi there, I had posted a startup problem with LibreOffice recently. But mistakenly, I had posted it in a hijacking way. Thanks to Carlos for pointing out this and providing me some ideas along with other people. So I start a new thread because I need further help on this issue and here are something new I found on my problem. And the direction to solve the problem seems changed. For reference, following is the links to the posts in the hijacked thread: [1] https://lists.opensuse.org/opensuse-support/2018-12/msg00055.html [2] https://lists.opensuse.org/opensuse-support/2018-12/msg00065.html First of all, I can confirm that the issue is not with Java. I fired up a VirtualBox and installed openSUSE Tumbleweed in it with almost all settings as default. LibreOffice runs smoothly without further setup, just like my current system. Here are something new, 1. LibreOffice does not run in a newly created account in my system. The error messages are the same. 2. I have already tried to remove LibreOffice and reinstall all related packages and this does not help. 3. It seems that LibreOffice can run by root, ```bash cnzhx@ostp:/home/cnzhx> libreoffice --version terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' ``` ```bash cnzhx@ostp:/home/cnzhx> sudo libreoffice --version LibreOffice 6.1.3.2 10(Build:2) ``` Then, the question is that how could I make LO also works by normal user. I have no clue where to start trying. Any suggestions are welcome! -- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 27/12/2018 15.32, H Zeng wrote:
Then, the question is that how could I make LO also works by normal user.
I have no clue where to start trying. Any suggestions are welcome!
Maybe mount options of the /home partition? Run "mount" in a terminal to find out. Anything by apparmor? Run "aa-logprof" as root to see what it complains about. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On Thursday, 27 December 2018 23:29:06 HKT Carlos E. R. wrote:
On 27/12/2018 15.32, H Zeng wrote:
Then, the question is that how could I make LO also works by normal user.
I have no clue where to start trying. Any suggestions are welcome!
Maybe mount options of the /home partition? Run "mount" in a terminal to find out.
```bash cnzhx@ostp:/home/cnzhx> mount | grep home /dev/nvme0n1p7 on /home type ext4 (rw,noatime,data=ordered) ``` Is this OK?
Anything by apparmor? Run "aa-logprof" as root to see what it complains about.
cnzhx@ostp:/home/cnzhx> sudo aa-logprof
[sudo] password for root:
Reading log entries from /var/log/audit/audit.log.
Updating AppArmor profiles in /etc/apparmor.d.
Thank you, Carlos. Could you find anything unusual from the outputs? -- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 27/12/2018 16.59, H Zeng wrote:
On Thursday, 27 December 2018 23:29:06 HKT Carlos E. R. wrote:
On 27/12/2018 15.32, H Zeng wrote:
Then, the question is that how could I make LO also works by normal user.
I have no clue where to start trying. Any suggestions are welcome!
Maybe mount options of the /home partition? Run "mount" in a terminal to find out.
```bash cnzhx@ostp:/home/cnzhx> mount | grep home /dev/nvme0n1p7 on /home type ext4 (rw,noatime,data=ordered) ``` Is this OK?
AFAIK, yes. If it were "noexec" we could suspect that, but it isn't. Nor "ro".
Anything by apparmor? Run "aa-logprof" as root to see what it complains about.
cnzhx@ostp:/home/cnzhx> sudo aa-logprof [sudo] password for root: Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d.
And this is empty, so nothing was blocked.
Thank you, Carlos. Could you find anything unusual from the outputs?
No... :-( -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On Friday, 28 December 2018 02:17:51 HKT Carlos E. R. wrote:
On 27/12/2018 16.59, H Zeng wrote:
On Thursday, 27 December 2018 23:29:06 HKT Carlos E. R. wrote:
On 27/12/2018 15.32, H Zeng wrote:
Then, the question is that how could I make LO also works by normal user.
I have no clue where to start trying. Any suggestions are welcome!
Maybe mount options of the /home partition? Run "mount" in a terminal to find out.
```bash cnzhx@ostp:/home/cnzhx> mount | grep home /dev/nvme0n1p7 on /home type ext4 (rw,noatime,data=ordered) ``` Is this OK?
AFAIK, yes. If it were "noexec" we could suspect that, but it isn't. Nor "ro".
Anything by apparmor? Run "aa-logprof" as root to see what it complains about.
```bash cnzhx@ostp:/home/cnzhx> sudo aa-logprof [sudo] password for root: Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. ```
And this is empty, so nothing was blocked.
Thank you, Carlos. Could you find anything unusual from the outputs?
No... :-( This situation is very strange but it seems not a bug so I have not reported it. This is far beyond my knowledge. I guess I just have to reinstall my system again.
In the last reinstallation of openSUSE Tumbleweed, the installer did not remind me to scan and import existing users from existing /home partition. I skipped the user creation and create a new user with the same old username with the old user dir as it's home dir. Do you think this could possibly be the cause of my current issue? If yes, is there anything I can do to find out? -- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 28/12/2018 02.19, H Zeng wrote:
On Friday, 28 December 2018 02:17:51 HKT Carlos E. R. wrote:
On 27/12/2018 16.59, H Zeng wrote:
...
Thank you, Carlos. Could you find anything unusual from the outputs?
No... :-( This situation is very strange but it seems not a bug so I have not reported it. This is far beyond my knowledge. I guess I just have to reinstall my system again.
In the last reinstallation of openSUSE Tumbleweed, the installer did not remind me to scan and import existing users from existing /home partition.
I believe the installer reads /etc/passwd. Maybe fstab.
I skipped the user creation and create a new user with the same old username with the old user dir as it's home dir. Do you think this could possibly be the cause of my current issue? If yes, is there anything I can do to find out?
Well, that's why I asked you to try with a new user. A new user has a new home, everything set at defaults, so if there was a problem with the old user configuration or files, a new user would work. But you said it failed, so that was not it. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Friday, 28 December 2018 09:29:02 HKT Carlos E. R. wrote:
On 28/12/2018 02.19, H Zeng wrote:
On Friday, 28 December 2018 02:17:51 HKT Carlos E. R. wrote:
On 27/12/2018 16.59, H Zeng wrote: ...
Thank you, Carlos. Could you find anything unusual from the outputs?
No... :-(
This situation is very strange but it seems not a bug so I have not reported it. This is far beyond my knowledge. I guess I just have to reinstall my system again.
In the last reinstallation of openSUSE Tumbleweed, the installer did not remind me to scan and import existing users from existing /home partition.
I believe the installer reads /etc/passwd. Maybe fstab.
I skipped the user creation and create a new user with the same old username with the old user dir as it's home dir. Do you think this could possibly be the cause of my current issue? If yes, is there anything I can do to find out? Well, that's why I asked you to try with a new user. A new user has a new home, everything set at defaults, so if there was a problem with the old user configuration or files, a new user would work. But you said it failed, so that was not it. OK. Maybe I just need to reinstall again :(
-- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 28/12/2018 02.49, H Zeng wrote:
On Friday, 28 December 2018 09:29:02 HKT Carlos E. R. wrote:
OK. Maybe I just need to reinstall again :(
I hate doing that, I consider it as admiting defeat. But I have no idea what is going on. Install again, let's see... this time don't import any user, create new users. If it works, you can import later. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Friday, 28 December 2018 09:58:00 HKT Carlos E. R. wrote:
On 28/12/2018 02.49, H Zeng wrote:
On Friday, 28 December 2018 09:29:02 HKT Carlos E. R. wrote:
OK. Maybe I just need to reinstall again :(
I hate doing that, I consider it as admiting defeat. But I have no idea what is going on. Yeah, I hate reinstalling too.
Install again, let's see... this time don't import any user, create new users. If it works, you can import later. Thx for the hint. I'll try this in the weekend.
-- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 28/12/2018 03.39, H Zeng wrote:
Install again, let's see... this time don't import any user, create new users. If it works, you can import later. Thx for the hint. I'll try this in the weekend.
You may create user of different name, yet same UID. The home directory will be different, but the ownership of the old home will remain the same. At the install, don't remove packages from the default list, just in case. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 28/12/2018 03.39, H Zeng wrote:
Install again, let's see... this time don't import any user, create new users. If it works, you can import later.
Thx for the hint. I'll try this in the weekend.
You may create user of different name, yet same UID. The home directory will be different, but the ownership of the old home will remain the same.
At the install, don't remove packages from the default list, just in case. I just finished the installation since I got a break this afternoon. This time I used the current snapshot 20181224. Amazingly, there is an "import user"
On Friday, 28 December 2018 11:14:45 HKT Carlos E. R. wrote: option available. So I tried it. Now LibreOffice starts smoothly. I guess it's possible to solve previous problem if I know how the "import" user process works. Anyway, this can be closed now. Thank you very much for your times these days. -- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 28/12/2018 09.52, H Zeng wrote:
On 28/12/2018 03.39, H Zeng wrote:
Install again, let's see... this time don't import any user, create new users. If it works, you can import later.
Thx for the hint. I'll try this in the weekend.
You may create user of different name, yet same UID. The home directory will be different, but the ownership of the old home will remain the same.
At the install, don't remove packages from the default list, just in case. I just finished the installation since I got a break this afternoon. This time I used the current snapshot 20181224. Amazingly, there is an "import user"
On Friday, 28 December 2018 11:14:45 HKT Carlos E. R. wrote: option available. So I tried it. Now LibreOffice starts smoothly. I guess it's possible to solve previous problem if I know how the "import" user process works.
Anyway, this can be closed now. Thank you very much for your times these days.
If you imported users and LO works, the issue was not your user, it was something in the system. Maybe there was something bad in the release. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Friday, 28 December 2018 20:53:02 HKT Carlos E. R. wrote:
On 28/12/2018 09.52, H Zeng wrote:
On Friday, 28 December 2018 11:14:45 HKT Carlos E. R. wrote:
On 28/12/2018 03.39, H Zeng wrote:
Install again, let's see... this time don't import any user, create new users. If it works, you can import later.
Thx for the hint. I'll try this in the weekend.
You may create user of different name, yet same UID. The home directory will be different, but the ownership of the old home will remain the same.
At the install, don't remove packages from the default list, just in case.
I just finished the installation since I got a break this afternoon. This time I used the current snapshot 20181224. Amazingly, there is an "import user" option available. So I tried it. Now LibreOffice starts smoothly. I guess it's possible to solve previous problem if I know how the "import" user process works.
Anyway, this can be closed now. Thank you very much for your times these days. If you imported users and LO works, the issue was not your user, it was something in the system. Maybe there was something bad in the release. Yeah, probably but I guess it is not important now as the new release works well.
-- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 28/12/2018 04:39, H Zeng wrote:
Yeah, I hate reinstalling too
- last resort : maybe try stupid stuff : as root , experiment with chown & chmod : try chown libreoffice to your user-name & try chmod to rwxrwxrwx .... !! -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Friday, 28 December 2018 17:32:43 HKT ellanios82 wrote:
On 28/12/2018 04:39, H Zeng wrote:
Yeah, I hate reinstalling too
- last resort : maybe try stupid stuff : as root , experiment with chown & chmod : try chown libreoffice to your user-name & try chmod to rwxrwxrwx
Sorry, I cannot do that now as I have reinstalled the system right before your reply. -- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thursday, December 27, 2018 10:32:05 PM HKT you wrote:
Hi there,
I had posted a startup problem with LibreOffice recently. But mistakenly, I had posted it in a hijacking way. Thanks to Carlos for pointing out this and providing me some ideas along with other people. So I start a new thread because I need further help on this issue and here are something new I found on my problem. And the direction to solve the problem seems changed.
For reference, following is the links to the posts in the hijacked thread: [1] https://lists.opensuse.org/opensuse-support/2018-12/msg00055.html [2] https://lists.opensuse.org/opensuse-support/2018-12/msg00065.html
First of all, I can confirm that the issue is not with Java. I fired up a VirtualBox and installed openSUSE Tumbleweed in it with almost all settings as default. LibreOffice runs smoothly without further setup, just like my current system.
Here are something new, 1. LibreOffice does not run in a newly created account in my system. The error messages are the same. 2. I have already tried to remove LibreOffice and reinstall all related packages and this does not help. 3. It seems that LibreOffice can run by root, ```bash cnzhx@ostp:/home/cnzhx> libreoffice --version terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' ``` ```bash cnzhx@ostp:/home/cnzhx> sudo libreoffice --version LibreOffice 6.1.3.2 10(Build:2) ```
Then, the question is that how could I make LO also works by normal user.
I have no clue where to start trying. Any suggestions are welcome!
It's weird that I got maybe the same problem again. And this time it happened when I was updating my system to snapshot 20190108. After several minutes' not responding and blinking "CapsLock" key (it has a LED indicator), the laptop restarted itself and enterred directly into rescue mode. At lease, the root partition, which was BtrFS, was reported not mountable because of "bad superblock". This is the same as last time. Of course, I have no clue on how to rescue it. So I reinstalled again but this time I used EXT4 for the root partition. Let's see where it goes. Regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 11/01/2019 17.36, H Zeng wrote:
On Thursday, December 27, 2018 10:32:05 PM HKT you wrote:
Hi there,
I had posted a startup problem with LibreOffice recently. But mistakenly, I had posted it in a hijacking way. Thanks to Carlos for pointing out this and providing me some ideas along with other people. So I start a new thread because I need further help on this issue and here are something new I found on my problem. And the direction to solve the problem seems changed.
For reference, following is the links to the posts in the hijacked thread: [1] https://lists.opensuse.org/opensuse-support/2018-12/msg00055.html [2] https://lists.opensuse.org/opensuse-support/2018-12/msg00065.html
First of all, I can confirm that the issue is not with Java. I fired up a VirtualBox and installed openSUSE Tumbleweed in it with almost all settings as default. LibreOffice runs smoothly without further setup, just like my current system.
Here are something new, 1. LibreOffice does not run in a newly created account in my system. The error messages are the same. 2. I have already tried to remove LibreOffice and reinstall all related packages and this does not help. 3. It seems that LibreOffice can run by root, ```bash cnzhx@ostp:/home/cnzhx> libreoffice --version terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' ``` ```bash cnzhx@ostp:/home/cnzhx> sudo libreoffice --version LibreOffice 6.1.3.2 10(Build:2) ```
Then, the question is that how could I make LO also works by normal user.
I have no clue where to start trying. Any suggestions are welcome!
It's weird that I got maybe the same problem again. And this time it happened when I was updating my system to snapshot 20190108. After several minutes' not responding and blinking "CapsLock" key (it has a LED indicator), the laptop restarted itself and enterred directly into rescue mode. At lease, the root partition, which was BtrFS, was reported not mountable because of "bad superblock". This is the same as last time.
But that's not LO? That's something else, a problem with btrfs.
Of course, I have no clue on how to rescue it. So I reinstalled again but this time I used EXT4 for the root partition. Let's see where it goes.
I'm sorry to say that I would have done the same :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Saturday, 12 January 2019 01:29:19 HKT Carlos E. R. wrote:
On 11/01/2019 17.36, H Zeng wrote:
On Thursday, December 27, 2018 10:32:05 PM HKT you wrote:
Hi there,
I had posted a startup problem with LibreOffice recently. But mistakenly, I had posted it in a hijacking way. Thanks to Carlos for pointing out this and providing me some ideas along with other people. So I start a new thread because I need further help on this issue and here are something new I found on my problem. And the direction to solve the problem seems changed.
For reference, following is the links to the posts in the hijacked thread: [1] https://lists.opensuse.org/opensuse-support/2018-12/msg00055.html [2] https://lists.opensuse.org/opensuse-support/2018-12/msg00065.html
First of all, I can confirm that the issue is not with Java. I fired up a VirtualBox and installed openSUSE Tumbleweed in it with almost all settings as default. LibreOffice runs smoothly without further setup, just like my current system.
Here are something new, 1. LibreOffice does not run in a newly created account in my system. The error messages are the same. 2. I have already tried to remove LibreOffice and reinstall all related packages and this does not help. 3. It seems that LibreOffice can run by root, ```bash cnzhx@ostp:/home/cnzhx> libreoffice --version terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' ``` ```bash cnzhx@ostp:/home/cnzhx> sudo libreoffice --version LibreOffice 6.1.3.2 10(Build:2) ```
Then, the question is that how could I make LO also works by normal user.
I have no clue where to start trying. Any suggestions are welcome!
It's weird that I got maybe the same problem again. And this time it happened when I was updating my system to snapshot 20190108. After several minutes' not responding and blinking "CapsLock" key (it has a LED indicator), the laptop restarted itself and enterred directly into rescue mode. At lease, the root partition, which was BtrFS, was reported not mountable because of "bad superblock". This is the same as last time.
But that's not LO? That's something else, a problem with btrfs. It's so embarrassing that I posted to the wrong place, again.
Of course, I have no clue on how to rescue it. So I reinstalled again but this time I used EXT4 for the root partition. Let's see where it goes.
I'm sorry to say that I would have done the same :-(
-- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (3)
-
Carlos E. R.
-
ellanios82
-
H Zeng