Bug 24129 - Libreoffice Fails on i686 (32-bit) Gnome Install
Summary: Libreoffice Fails on i686 (32-bit) Gnome Install
Status: RESOLVED DUPLICATE of bug 24122
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: 7beta1
Depends on:
Blocks:
 
Reported: 2019-01-04 20:00 CET by Brian Rockwell
Modified: 2019-01-05 13:06 CET (History)
2 users (show)

See Also:
Source RPM: magea-7-beta2-i586.iso
CVE:
Status comment:

Attachments
Journal file (67.56 KB, application/gzip)
2019-01-04 20:06 CET, Brian Rockwell 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Brian Rockwell 2019-01-04 20:00:17 CET 
Description of problem:  Clicking on libreoffice writer or any libreoffice product fails


Version-Release number of selected component (if applicable):  7Beta2

- Gnome using xorg (on wayland gnome crashed on this equipment)


How reproducible:  From command line:  libreoffice or click on shortcut for writer

[brian@localhost ~]$ uname -a
Linux localhost 4.19.13-desktop-1.mga7 #1 SMP Sat Dec 29 23:03:11 UTC 2018 i686 i686 i386 GNU/Linux

[brian@localhost ~]$ libreoffice
/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
[brian@localhost ~]$ 



Steps to Reproduce:
1.  
2.
3.
Comment 1 Brian Rockwell 2019-01-04 20:06:05 CET 
Created attachment 10642 [details]
Journal file
Comment 2 Martin Whitaker 2019-01-05 01:45:14 CET 
This is happening because the firefox package now provides libnss3.so, but doesn't install it in a location where libreoffice can find it:

  https://ml.mageia.org/l/arc/dev/2018-12/msg00275.html

CC: (none) => mageia

Comment 3 Ben McMonagle 2019-01-05 03:15:48 CET 
see also bug #24122

CC: (none) => westel

Ben McMonagle 2019-01-05 05:58:33 CET

Keywords: (none) => 7beta1

Comment 4 Martin Whitaker 2019-01-05 13:06:59 CET 
Yes, this is the same as bug 24122.

*** This bug has been marked as a duplicate of bug 24122 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.