libreOffice crash system

English Applications
1

Hi,
when trying to open a file in LibreOffice (latest version from Leap 42.1 installation) the system crashes and I have login again. What could be the problem?. I have a 64bit stm.

2

what desktop are you using, what graphic card and driver?
also post your repo’s

zypper lr -d
3

It’s Lenovo MT-80ECO-BU_idea_FM Z50-75 x64 with A10-7300 Radcon R6 computer cores 4C+6G processor (BIOS Lenovo a4cn40ww v. 2.09) and AMD Radeon R6 graphics cotroller. The graphics driver seems to be ATI Kaveri Radeon R6 Graphics or ATI Jet PRO Radeon 5 M230 Graphics (2 drivers listed in Yast hw information). I originally installed Leap 42.1 with Gnome. Then I added all other frameworks for testing purposes (KDE Plasma, Cinnamon, Enlightenment, Mate …).

zypper lr -d

| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service

—±------------------------------±-------------------------------------------------------------±--------±----------±--------±---------±-------±-------------------------------------------------------------------------------------±-------
1 | X11_Cinnamon_Current | The latest official release of Cinnamon (openSUSE_Leap_42.1) | Yes | (r ) Yes | No | 99 | rpm-md | http://download.opensuse.org/repositories/X11:/Cinnamon:/Current/openSUSE_Leap_42.1/ |
2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/ |
3 | ftp.gwdg.de-suse | Packman Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_42.1/ |
4 | geeko.ioda.net-amd-fglrx | AMD/ATI Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_Leap_42.1/ |
5 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
6 | linuxdownload.adobe.com-linux | Adobe Flash Plugin | Yes | ( p) Yes | Yes | 99 | rpm-md | http://linuxdownload.adobe.com/linux/x86_64/ |
7 | openSUSE-42.1-0 | openSUSE-42.1-0 | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.1/repo/oss/ |
8 | opensuse-guide.org-repo | Libdvdcss Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_42.1/ |
9 | repo-debug | openSUSE-Leap-42.1-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.1/repo/oss/ |
10 | repo-debug-non-oss | openSUSE-Leap-42.1-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.1/repo/non-oss/ |
11 | repo-debug-update | openSUSE-Leap-42.1-Update-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.1/oss |
12 | repo-debug-update-non-oss | openSUSE-Leap-42.1-Update-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.1/non-oss/ |
13 | repo-non-oss | openSUSE-Leap-42.1-Non-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/ |
14 | repo-source | openSUSE-Leap-42.1-Source | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.1/repo/oss/ |
15 | repo-update | openSUSE-Leap-42.1-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.1/oss/ |
16 | repo-update-non-oss | openSUSE-Leap-42.1-Update-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.1/non-oss/

4

Hi,
I also noticed that the fglrx64 packages for amd (acc. to Yast sw manager, 5 pcs ) are not installed. don’t know which package should be installed.

5

All 5.

But actually you only need to install fglrx64_xpic_SUSE421, that will automatically pull in the other ones.

And I would definitely recommend to try it, your problem does seem to be graphics driver related.

6

Ok, I did that installation through Yast. Now I get only the terminal window, and Yast hw mngt shows the same graphics drivers as before. Is this a group loader issue?

7

Ok, I did that installation through Yast. Now I get only the terminal window, and Yast hw mngt shows the same graphics drivers as before. Is this a group loader issue?

8

I also tried to open the amd control center (# amdcccle) from the terminal and got the response "sh: -c: line 0: syntax error near unexpexted token ‘(’ and sh: -c: line 0: ‘ps -e (null) | egrep ‘gnome-session|xfce4-session|startkde’’ ". I did the amd-driver installation under gnome framework. Could that give this problem and how to fix it?

9

So I uninstalled the fglrx64 drivers and started libreoffice from terminal (root) and got the following response:
" libreoffice
GConf warning: failure listing pairs in /desktop/gnome/interface': Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /system/proxy’: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /system/http_proxy/host': Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /desktop/gnome/url-handlers/mailto’: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /apps/openoffice': Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /desktop/gnome/lockdown’: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /apps/openoffice/lockdown': Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /desktop/gnome/interface’: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /system/proxy': Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /system/http_proxy/host’: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /desktop/gnome/url-handlers/mailto': Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /apps/openoffice’: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /desktop/gnome/lockdown': Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.GConf warning: failure listing pairs in /apps/openoffice/lockdown’: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** (soffice:7602): CRITICAL : void g_lo_menu_insert_section(GLOMenu, gint, const gchar, GMenuModel*): assertion ‘G_IS_LO_MENU (menu)’ failed"

Is it there a way to fix broken connectios?

10

It was not a graphics driver issue. Just installed the libreoffice-gtk3 package, and it works fine. Thanks

11

I fail to understand what “group loader” means in this context.

But better have a look into /var/log/Xorg.0.log to see what driver is used.
The driver “names” you posted earlier make absolutely no indication which one is which (radeon, fglrx).

Though if you use GDM, the log is somewhere else, I think in /var/log/gdm/.

And if you run a GNOME Wayland session (I’m not sure it’s the default/included in Leap 42.1 already), things are completely different again.
Actually Wayland (or GNOME on Wayland) might be the reason for problems in the first place…

No. It should be perfectly fine to install the driver inside GNOME.

That error message basically just means that you cannot run the amd controlcenter in text mode, I suppose…

Yes, don’t run it as root.
It doesn’t find the user’s session when run as root.

Might still have been a graphics driver issue though.

OTOH, not too long ago libreoffice-gtk3 was “broken”/buggy, and installing it actually caused problems.
I’m not sure of the current state, but if installing it fixed your problem, it should be ok…

12

when I asked about the desktop I meant the desktop environment is seams you use gnome.
it could have been a bug in libre’s gtk integration that was fixed,
Never ever run gui apps as root in a terminal!
gnome 3 is resource intensive and without the proper drivers all of the visual processing is done by the cpu which is not a good idea so install the ati driver and let the graphic card do it’s job.