Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #183344 > unrolled thread

WARNING: Libreoffice - Do not remove ~/.config/libreoffice

Back to article view | Back to linux.debian.user

Contents

  WARNING: Libreoffice - Do not remove ~/.config/libreoffice Hans <hans.ullrich@loop.de> - 2017-07-07 19:10 +0200
    Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Robert Parker <rlp1938@gmail.com> - 2017-07-07 19:30 +0200
    Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Reco <recoverym4n@gmail.com> - 2017-07-07 21:30 +0200
      Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Hans <hans.ullrich@loop.de> - 2017-07-07 21:40 +0200
        Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Reco <recoverym4n@gmail.com> - 2017-07-07 22:00 +0200
          Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Hans <hans.ullrich@loop.de> - 2017-07-16 13:50 +0200
        Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Rene Engelhard <rene@debian.org> - 2017-07-10 09:40 +0200
          Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Hans <hans.ullrich@loop.de> - 2017-07-10 10:10 +0200
            Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Rene Engelhard <rene@debian.org> - 2017-07-10 10:30 +0200
              Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Rene Engelhard <rene@debian.org> - 2017-07-10 13:00 +0200
                Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Hans <hans.ullrich@loop.de> - 2017-07-10 13:20 +0200
                  Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Rene Engelhard <rene@debian.org> - 2017-07-10 14:20 +0200
              Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Hans <hans.ullrich@loop.de> - 2017-07-10 13:30 +0200
                Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Rene Engelhard <rene@debian.org> - 2017-07-10 14:30 +0200
                  Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Hans <hans.ullrich@loop.de> - 2017-07-10 14:50 +0200
                  Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Henrique de Moraes Holschuh <hmh@debian.org> - 2017-07-10 14:50 +0200
                    Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Rene Engelhard <rene@debian.org> - 2017-07-10 23:30 +0200
                      Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice Henrique de Moraes Holschuh <hmh@debian.org> - 2017-07-10 23:50 +0200

#183344 — WARNING: Libreoffice - Do not remove ~/.config/libreoffice

Hi folks, 

due to another problem in libreoffice (no gallery, when dmaths is installed), I 
moved ~/.config/libreoffice out of the way, to get a fresh configuration. 
DO NOT DO THIS except you have a backup available! 

If you do so, you will not be able, to start libreoffice any more.  If you move 
it back, then it will start again. So do not delete these files! 

Just a friendly warning. I suppose, the opackage team, libreoffice team knows 
about, as I saw lots of bugmessages about similar in Ubuntu.

Have fun!

Best

Hans

[toc] | [next] | [standalone]

#183346

[Multipart message — attachments visible in raw view] — view raw

On Sat, Jul 8, 2017 at 12:08 AM, Hans <hans.ullrich@loop.de> wrote:

> Hi folks,
>
> due to another problem in libreoffice (no gallery, when dmaths is
> installed), I
> moved ~/.config/libreoffice out of the way, to get a fresh configuration.
> DO NOT DO THIS except you have a backup available!


 Actually there are times when removing ~/.config/libreoffice is exactly
what
you need to do.

The LO installer is rather brain dead so when you get reported file missing
errors on LO start up, apt-get remove libreoffice && apt-get install
libreoffice
does not fix the problem.

The procedure that worked for me was:
apt-get remove libreoffice
rm -rf ~/.config/libreoffice
apt-get install libreoffice

all as root of course.

There may have been a better way to do this job but the above did work.

Cheers Bob



-- 
All along the untrodden paths of nature may be seen the footprints of an
unseen hand.

[toc] | [prev] | [next] | [standalone]

#183354

	Hi.

On Fri, 07 Jul 2017 19:08:20 +0200
Hans <hans.ullrich@loop.de> wrote:

> Hi folks, 
> 
> due to another problem in libreoffice (no gallery, when dmaths is installed), I 
> moved ~/.config/libreoffice out of the way, to get a fresh configuration. 
> DO NOT DO THIS except you have a backup available! 
> 
> If you do so, you will not be able, to start libreoffice any more.  If you move 
> it back, then it will start again. So do not delete these files! 

Thanks for the heads up, but it does not reproduce here.

Just removed ~/.config/libreoffice, invoked lowriter, and … lo and
behold - got Libreoffice Writer window.

Maybe it does not break every time?

Reco

[toc] | [prev] | [next] | [standalone]

#183355

Sounds weired. I am running debian/testing , i386. It is an EEEPC. Maybe this 
is the difference. Let's see, if others can confirm or deny this.

Hans
> Thanks for the heads up, but it does not reproduce here.
> 
> Just removed ~/.config/libreoffice, invoked lowriter, and … lo and
> behold - got Libreoffice Writer window.
> 
> Maybe it does not break every time?
> 
> Reco

[toc] | [prev] | [next] | [standalone]

#183358

	Hi.

On Fri, 07 Jul 2017 21:35:53 +0200
Hans <hans.ullrich@loop.de> wrote:

> Sounds weired. I am running debian/testing , i386.

This. It's amd64 for me.
Recent kernel fix to Stack Clash aka CVE-2017-1000364 broke a lot
of stuff, including, but not limited to Java, Libreoffice and Nagios.
Debian got the long end of the stick, so to speak (compared to RHEL7 ;),
but they managed to break some toys too. And it's more severe on i386.

Try setting 'ulimit -s 32768' before launching Libreoffice (may need to
increase stack in /etc/security/limits.conf beforehand), see how it
goes.

Reco

[toc] | [prev] | [next] | [standalone]

#183738

Hi folks,

during the last days I did some upgrades on my debian/testing 32-bit.

It looks like libreoffice is working again, although I can not find out, why.

I did this:

1. removed ~/.libreoffice
2. started libreoffice = worked
3. reboot
4. started libreoffice = worked

Looks like the bug is gone, but let us be wakeful!

Best

Hans

[toc] | [prev] | [next] | [standalone]

#183490

On Fri, Jul 07, 2017 at 09:35:53PM +0200, Hans wrote:
> Sounds weired. I am running debian/testing , i386. It is an EEEPC. Maybe this 
> is the difference. Let's see, if others can confirm or deny this.

LO on i386 is broken when starting. What I'd bet here is that your config
contains "disable Java". Wheres a clean config of course would not.

In that case you run tinto the known Java bug _ONLY ON I386_ with newer
kernels.

Google is your friend, luke.

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#183493

Am Montag, 10. Juli 2017, 09:33:32 CEST schrieb Rene Engelhard:
Hi Rene,
> LO on i386 is broken when starting. What I'd bet here is that your config
> contains "disable Java". Wheres a clean config of course would not.
> 
yes, I am running i386 at the moment only, as my other notebook has died some 
weeks ago. I looked into the bugs of debian, but could not find the required 
information. So, LO is broken, hmm, good to know. However, it is still running 
on my system with my config, as at other people will do, too. So only few 
people will know about this bug at all.  
> In that case you run tinto the known Java bug _ONLY ON I386_ with newer
> kernels.
> 

Yes, I guess so. Running debian/testing with 4.9.0-3 kernel. I believe, I will 
wait for the next version, which is already available in sid 
(experimental???), as it is still running on my system. 

But good to know, that the bug is known. Thank you very much for this 
information indeed!

Best regards

Hans
> Google is your friend, luke.
> 
> Regards,
> 
> Rene

[toc] | [prev] | [next] | [standalone]

#183497

Hi,

On Mon, Jul 10, 2017 at 10:00:01AM +0200, Hans wrote:
> Hi Rene,
> > LO on i386 is broken when starting. What I'd bet here is that your config
> > contains "disable Java". Wheres a clean config of course would not.
> > 
> yes, I am running i386 at the moment only, as my other notebook has died some 
> weeks ago. I looked into the bugs of debian, but could not find the required 
> information. So, LO is broken, hmm, good to know. However, it is still running 

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866

Admittedly they somehow (probably because of the version tracking)
don't end up in libreoffices bug list...

> on my system with my config, as at other people will do, too. So only few 
> people will know about this bug at all.  

If you have an old config disabling Java - true. Otherwise if you have Java
enabled it will crash, too. It's not only about old vs. new config.

And yeah, people don't know, people also can't google...

They appear here and there and even in totally unrelated bugreports with this
problem only affecting a oboslete architecture...

> Yes, I guess so. Running debian/testing with 4.9.0-3 kernel. I believe, I will 
> wait for the next version, which is already available in sid 
> (experimental???), as it is still running on my system. 

LO? Won't help. (And there won't be a update in unstable for LO because of exactly
tis bug - because it fails to build because the LO testsuite fails exactly because
of this problem.)

The problem is kernel and/or openjdk. But yeah, you could
try kernel 4.11, but AFAIK that one still is affected. Would be good to know
whether that really is the case.

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#183500

{ and what is so private here that this can't be on-list so that peole
except you know? }

Hi,

Fullquoting:

On Mon, Jul 10, 2017 at 12:51:32PM +0200, Hans wrote:
> I now installed kernel 4.11 now, removed ~/.config/libreoffice and ----- worked!
> Thanks for the hint with related to the kernel.
> 
> Best 
> 
> Hans
> 
> > The problem is kernel and/or openjdk. But yeah, you could
> > try kernel 4.11, but AFAIK that one still is affected. Would be good to know
> > whether that really is the case.
> > 
> > Regards,
> > 
> > Rene

[toc] | [prev] | [next] | [standalone]

#183502

Am Montag, 10. Juli 2017, 12:57:44 CEST schrieben Sie:
Ahem, maybe you misunderstood my mail. What I wanted to express, is, if people 
do just an upgrade and never delete their ~/.config/libreoffice, they will never 
notice that bug. This is, what I meant, that only few people will notice this, 
mostly those, who install a fresh system or install libreoffice for the first 
time. 

Sorry, if I did it not clear enough. Bad English...

Best 

Hans

> { and what is so private here that this can't be on-list so that peole
> except you know? }
> 
> Hi,
> 
> Fullquoting:
> 


-- 
Ullrich-IT-Consult
Ihr Partner für die Themen 
* IT-SICHERHEIT * IT-SERVICE * 
* LINUX * EDV-SCHULUNGEN *

Hans-J. Ullrich
Münstedter Weg 10
31246 Oberg 
 
TEL.: 0179 3666 059
FAX: 05172 930 414

E-Mail: hans.ullrich@loop.de

[toc] | [prev] | [next] | [standalone]

#183505

Hi,

On Mon, Jul 10, 2017 at 01:12:56PM +0200, Hans wrote:
> Am Montag, 10. Juli 2017, 12:57:44 CEST schrieben Sie:
> Ahem, maybe you misunderstood my mail. What I wanted to express, is, if people 
> do just an upgrade and never delete their ~/.config/libreoffice, they will never 
> notice that bug. This is, what I meant, that only few people will notice this, 
> mostly those, who install a fresh system or install libreoffice for the first 
> time. 

No, I got that.

a) there's always new peopple installing it or re-installing their system for
   whatever reason (new machine, ...)
b) there's people who kept the default settings enabling Java and now are
   screwed anyway, so they are affected, too

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#183504

Huh, first mail went accidently private! 

I now installed kernel 4.11 now, removed ~/.config/libreoffice and ----- worked 
only once! After stopping and restarting LO again, it will not start again. 
Sorry, the problem is not fixed with a newer kernel - as I thought before!

I will watch this.

Best 

Hans

[toc] | [prev] | [next] | [standalone]

#183506

On Mon, Jul 10, 2017 at 01:28:54PM +0200, Hans wrote:
> only once! After stopping and restarting LO again, it will not start again. 

bt? Is that the same Java crash? See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866

> Sorry, the problem is not fixed with a newer kernel - as I thought before!

As "you" thought? Ah, well, I leave you in that belief.

Anyway, I marked those bugs as also found in linux 4.11.6-1.

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#183509

> bt? Is that the same Java crash? See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
> and
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
> 

No, it is not the same. Strace output differs from the one in the bugreport.

> Anyway, I marked those bugs as also found in linux 4.11.6-1.
> 

That is great. Good to know, there is a problem and is accepted as a problem.
> Regards,
> 
> Rene

Best

Hans
-- 
Ullrich-IT-Consult
Ihr Partner für die Themen 
* IT-SICHERHEIT * IT-SERVICE * 
* LINUX * EDV-SCHULUNGEN *

Hans-J. Ullrich
Münstedter Weg 10
31246 Oberg 
 
TEL.: 0179 3666 059
FAX: 05172 930 414

E-Mail: hans.ullrich@loop.de

[toc] | [prev] | [next] | [standalone]

#183512

On seg, 10 jul 2017, Rene Engelhard wrote:
> On Mon, Jul 10, 2017 at 01:28:54PM +0200, Hans wrote:
> > only once! After stopping and restarting LO again, it will not start again. 
> 
> bt? Is that the same Java crash? See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
> and
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866

It is related, yes.  LO does something rather unexpected (and arguably
Not Good) to its stack on i386, and that clashes with the added kernel
protection against the "stack clash" vulnerability.

Fixes are being prepared on kernel upstream, on the grounds that
userspace regressions are Bad, but in the end it is likely that we will
want to fix both LO and the kernel.

As for java, what it does is actually reasonably sane and there are
already two or three kernel fix alternatives upstream, I think they
settled on one already and merged it.  If it proves stable, it should
end up in a stable kernel and Debian kernels soon.

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#183539

On Mon, Jul 10, 2017 at 09:47:09AM -0300, Henrique de Moraes Holschuh wrote:
> On seg, 10 jul 2017, Rene Engelhard wrote:
> > On Mon, Jul 10, 2017 at 01:28:54PM +0200, Hans wrote:
> > > only once! After stopping and restarting LO again, it will not start again. 
> > 
> > bt? Is that the same Java crash? See
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
> > and
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
> 
> It is related, yes.  LO does something rather unexpected (and arguably
> Not Good) to its stack on i386, and that clashes with the added kernel
> protection against the "stack clash" vulnerability.

No. Java does. LO just calls into the JVM. Other stuff having the JVM
in-process (in contrast to calling "java") is also affected. See the reports.

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#183540

On Mon, 10 Jul 2017, Rene Engelhard wrote:
> On Mon, Jul 10, 2017 at 09:47:09AM -0300, Henrique de Moraes Holschuh wrote:
> > On seg, 10 jul 2017, Rene Engelhard wrote:
> > > On Mon, Jul 10, 2017 at 01:28:54PM +0200, Hans wrote:
> > > > only once! After stopping and restarting LO again, it will not start again. 
> > > 
> > > bt? Is that the same Java crash? See
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
> > > and
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
> > 
> > It is related, yes.  LO does something rather unexpected (and arguably
> > Not Good) to its stack on i386, and that clashes with the added kernel
> > protection against the "stack clash" vulnerability.
> 
> No. Java does. LO just calls into the JVM. Other stuff having the JVM
> in-process (in contrast to calling "java") is also affected. See the reports.

I did, but maybe I have misunderstood something...

What I got from LKML is that LO (but not java) has a rwx weird
stack-guard page (Bad Idea), while the JVM has PROT_NONE stack-guard
pages between each thread-local stack.

Obviously, LO with java support would *also* trigger any issues the JVM
has with the stack-guard kernel changes.

-- 
  Henrique Holschuh

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web