Bug 54624 - LOdev from 05/09 refuses to start after installation
Summary: LOdev from 05/09 refuses to start after installation
Status: CLOSED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.0.0.0.alpha0+ Master
Hardware: x86-64 (AMD64) Linux (All)
: medium blocker
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-07 07:22 UTC by Alex Thurgood
Modified: 2012-09-07 10:28 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
strace on startup (106.22 KB, application/x-gzip)
2012-09-07 08:08 UTC, Alex Thurgood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Thurgood 2012-09-07 07:22:22 UTC
1) Downloaded installation set from daily build 05/09 for Linux 64bit

2) Untar, then sudo dpkg -i *.deb in the corresponding DEBS directory.

3) Try to start LO from the command line :
/opt/lodev3.6/program/soffice

4) Message below is displayed :

The application cannot be started. 
LOdev user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LOdev:

/home/alex/.config/lodev/3


5) What should happen :
LO should start without error message.

6) No rights/permissions have been changed in my LO config directory.


Alex
Comment 1 Alex Thurgood 2012-09-07 07:31:02 UTC
gdb /opt/lodev3.6/program/soffice.bin
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /opt/lodev3.6/program/soffice.bin...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/lodev3.6/program/soffice.bin 
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffece39700 (LWP 23854)]
[New Thread 0x7fffe4374700 (LWP 23855)]
[New Thread 0x7fffe3b73700 (LWP 23856)]
[Thread 0x7fffe4374700 (LWP 23855) exited]
[Thread 0x7fffe3b73700 (LWP 23856) exited]
[Thread 0x7fffece39700 (LWP 23854) exited]
[Inferior 1 (process 23851) exited with code 0115]
Comment 2 Alex Thurgood 2012-09-07 07:34:37 UTC
In comparison, LO 3.5.4.2 starts just fine.


Alex
Comment 3 Alex Thurgood 2012-09-07 07:36:09 UTC
libreoffice-3-6~2012-09-05_19.27.02_LibO-Dev_3.6.2.0_Linux_x86-64_install-deb_en-US
Comment 4 Stephan Bergmann 2012-09-07 07:52:21 UTC
If you work backwards from the error message in the code the only place that can cause it is the call to copy_recursive in desktop/source/app/userinstall.cxx (to copy from .../presets to .../user) returns osl::FileBase::E_ACCES.

Alex, can you attach the output of running "strace -f /opt/lodev3.6/program/soffice"?
Comment 5 Alex Thurgood 2012-09-07 07:58:18 UTC
(In reply to comment #4)

Hi Stephan,

> Alex, can you attach the output of running "strace -f
> /opt/lodev3.6/program/soffice"?

Enclosed strace.txt

Alex
Comment 6 Stephan Bergmann 2012-09-07 08:02:01 UTC
(In reply to comment #5)
> Enclosed strace.txt

There is no attachment?
Comment 7 Alex Thurgood 2012-09-07 08:08:49 UTC
Created attachment 66766 [details]
strace on startup
Comment 8 Alex Thurgood 2012-09-07 08:10:43 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > Enclosed strace.txt
> 
> There is no attachment?

Sorry about that, I was having problems getting the output into a file, as the man page doesn't tell you that -o has to be place before the -f option... and then it generated a 3Mb file, which I tried to upload and which of course failed, sigh...you live and learn ;-)


Alex
Comment 9 Stephan Bergmann 2012-09-07 08:23:24 UTC
Alex, what is the output of "ls -al /home/alex/.config/lodev/3/user"?
Comment 10 Alex Thurgood 2012-09-07 08:26:14 UTC
ls -al /home/alex/.config/lodev/3/user/
total 20
drwxr-xr-x 5 root root 4096 2012-09-06 16:56 .
drwxr-xr-x 3 root root 4096 2012-09-07 09:02 ..
drwxr-xr-x 2 root root 4096 2012-09-03 20:43 config
drwxr-xr-x 4 root root 4096 2012-09-06 16:56 extensions
drwxr-xr-x 3 root root 4096 2012-09-06 16:56 uno_packages
Comment 11 Alex Thurgood 2012-09-07 08:27:07 UTC
Hmm, don't think they should be owned by root :-)

Alex
Comment 12 Alex Thurgood 2012-09-07 08:31:41 UTC
A quick chown and now it starts :-))
Comment 13 Alex Thurgood 2012-09-07 08:32:44 UTC
So the problem is that the installation routine sets the owner of a users LO config to root on startup ?

Alex
Comment 14 Stephan Bergmann 2012-09-07 08:45:59 UTC
(In reply to comment #13)
> So the problem is that the installation routine sets the owner of a users LO
> config to root on startup ?

Could it be that you already had a root-owned /home/alex/.config/lodev/3 tree before installing/running the 05/09 build?

With the existing /home/alex/.config/lodev moved out of the way, can you check that neither running "/opt/lodev3.6/program/soffice" nor "sudo dpkg -i *.deb" creates a root-owned /home/alex/.config/lodev/3 tree?
Comment 15 Alex Thurgood 2012-09-07 09:27:57 UTC
(In reply to comment #14)


> 
> Could it be that you already had a root-owned /home/alex/.config/lodev/3 tree
> before installing/running the 05/09 build?
> 
> With the existing /home/alex/.config/lodev moved out of the way, can you check
> that neither running "/opt/lodev3.6/program/soffice" nor "sudo dpkg -i *.deb"
> creates a root-owned /home/alex/.config/lodev/3 tree?

Will have a try and report back. The only things I have installed recently are the TDF 3.6.0.4 build and then daily builds.


Alex
Comment 16 Alex Thurgood 2012-09-07 09:33:50 UTC
So, its not the soffice startup script. I removed lodev from .config, and can start LO :

/opt/lodev3.6/program/soffice

alex@Aspire-T180 ~ $ ls -al /home/alex/.config/lodev/
total 12
drwxrwxr-x  3 alex alex 4096 2012-09-07 11:30 .
drwxr-xr-x 32 alex alex 4096 2012-09-07 11:30 ..
drwx------  3 alex alex 4096 2012-09-07 11:31 

the lodev directory gets created with the right permissions.

Now to try dpkg again.

Alex
Comment 17 Alex Thurgood 2012-09-07 09:41:59 UTC
Not the dpkg installation either, I can start LO no problem after a new installation of the basic installation package.


The only other things I've installed with the dev installation set have been the lang pack and help pack for French. Will try re-installing them to see whether the problem might have come from there.

Alex
Comment 18 Alex Thurgood 2012-09-07 09:52:03 UTC
No problem with restarting LO after removing ./config/lodev and installing either the fr langpack or the fr helppack.

Oh well, looks like this is now WFM.