unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 30292-done@debbugs.gnu.org
Subject: bug#30292: [PATCH] gnu: libreoffice: Fix build with Poppler >= 0.62.0.
Date: Thu, 1 Feb 2018 15:51:43 -0500	[thread overview]
Message-ID: <20180201205143.GA12960@jasmine.lan> (raw)
In-Reply-To: <20180130203808.GA27887@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Tue, Jan 30, 2018 at 03:38:08PM -0500, Leo Famulari wrote:
> On Tue, Jan 30, 2018 at 04:08:24AM -0500, Leo Famulari wrote:
> > I'll push this if and when the build finishes and I confirm that
> > LibreOffice is still working.
> > 
> > * gnu/packages/libreoffice.scm (libreoffice)[arguments]: Patch header and
> > function names in 'prepare-src' phase.
> 
> This does allow the build to finish but I can't start the resulting
> libreoffice.
> 
> During start it shows a dialogue that says "Fatal Error: The application
> cannot be started. User installation could not be completed.".

The issue is related to how NSS is configured on my Debian system, and
glibc 2.26 retiring libnss_compat.so. If nscd is running, then
libreoffice has no problem figuring out where to install it's per-user
files. That general issue was discussed in <https://bugs.gnu.org/30298>.

So, pushed as eb096cdebab56680375b26069ec524ddec60267e.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-02-01 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  9:08 [bug#30292] [PATCH] gnu: libreoffice: Fix build with Poppler >= 0.62.0 Leo Famulari
2018-01-30 20:38 ` Leo Famulari
2018-01-30 21:14   ` Leo Famulari
2018-01-30 21:42     ` Leo Famulari
2018-02-01 20:51   ` Leo Famulari [this message]
2018-01-30 20:39 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180201205143.GA12960@jasmine.lan \
    --to=leo@famulari.name \
    --cc=30292-done@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).