Menubars missing in libreoffice when used in unshare session in 18.04
Multi tool use
up vote
0
down vote
favorite
When using libreoffice inside unshare -m
session, the menubar is missing.
In the console output I see these warnings:
** (soffice:9193): CRITICAL **: 10:29:29.171:
void g_lo_menu_insert_section(GLOMenu*, gint, const gchar*, GMenuModel*):
assertion 'G_IS_LO_MENU (menu)' failed
(soffice:9193): Gtk-CRITICAL **: 10:29:29.171:
gtk_menu_bar_new_from_model:
assertion 'G_IS_MENU_MODEL (model)' failed
In my normal session, the menubar appears correctly. Also this used to work before I upgraded from 16.04 to 18.04.
18.04 libreoffice dbus
add a comment |
up vote
0
down vote
favorite
When using libreoffice inside unshare -m
session, the menubar is missing.
In the console output I see these warnings:
** (soffice:9193): CRITICAL **: 10:29:29.171:
void g_lo_menu_insert_section(GLOMenu*, gint, const gchar*, GMenuModel*):
assertion 'G_IS_LO_MENU (menu)' failed
(soffice:9193): Gtk-CRITICAL **: 10:29:29.171:
gtk_menu_bar_new_from_model:
assertion 'G_IS_MENU_MODEL (model)' failed
In my normal session, the menubar appears correctly. Also this used to work before I upgraded from 16.04 to 18.04.
18.04 libreoffice dbus
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When using libreoffice inside unshare -m
session, the menubar is missing.
In the console output I see these warnings:
** (soffice:9193): CRITICAL **: 10:29:29.171:
void g_lo_menu_insert_section(GLOMenu*, gint, const gchar*, GMenuModel*):
assertion 'G_IS_LO_MENU (menu)' failed
(soffice:9193): Gtk-CRITICAL **: 10:29:29.171:
gtk_menu_bar_new_from_model:
assertion 'G_IS_MENU_MODEL (model)' failed
In my normal session, the menubar appears correctly. Also this used to work before I upgraded from 16.04 to 18.04.
18.04 libreoffice dbus
When using libreoffice inside unshare -m
session, the menubar is missing.
In the console output I see these warnings:
** (soffice:9193): CRITICAL **: 10:29:29.171:
void g_lo_menu_insert_section(GLOMenu*, gint, const gchar*, GMenuModel*):
assertion 'G_IS_LO_MENU (menu)' failed
(soffice:9193): Gtk-CRITICAL **: 10:29:29.171:
gtk_menu_bar_new_from_model:
assertion 'G_IS_MENU_MODEL (model)' failed
In my normal session, the menubar appears correctly. Also this used to work before I upgraded from 16.04 to 18.04.
18.04 libreoffice dbus
18.04 libreoffice dbus
asked Nov 21 at 8:50
jpa
48423
48423
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The problem is caused by apparmor denying access to DBUS socket.
This can be seen in dmesg
output:
audit: type=1400 audit(1542789068.289:1060): apparmor="ALLOWED"
operation="connect"
info="Failed name lookup - disconnected path"
error=-13 profile="libreoffice-soffice"
name="run/user/1000/bus" pid=9545
comm="soffice.bin" requested_mask="wr"
denied_mask="wr" fsuid=1000 ouid=1000
I didn't find out how to fix the actual problem with the apparmor rules, but here is how one can disable the apparmor completely for libreoffice. This has some security risks if you open untrusted files.
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.* /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.*
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The problem is caused by apparmor denying access to DBUS socket.
This can be seen in dmesg
output:
audit: type=1400 audit(1542789068.289:1060): apparmor="ALLOWED"
operation="connect"
info="Failed name lookup - disconnected path"
error=-13 profile="libreoffice-soffice"
name="run/user/1000/bus" pid=9545
comm="soffice.bin" requested_mask="wr"
denied_mask="wr" fsuid=1000 ouid=1000
I didn't find out how to fix the actual problem with the apparmor rules, but here is how one can disable the apparmor completely for libreoffice. This has some security risks if you open untrusted files.
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.* /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.*
add a comment |
up vote
0
down vote
The problem is caused by apparmor denying access to DBUS socket.
This can be seen in dmesg
output:
audit: type=1400 audit(1542789068.289:1060): apparmor="ALLOWED"
operation="connect"
info="Failed name lookup - disconnected path"
error=-13 profile="libreoffice-soffice"
name="run/user/1000/bus" pid=9545
comm="soffice.bin" requested_mask="wr"
denied_mask="wr" fsuid=1000 ouid=1000
I didn't find out how to fix the actual problem with the apparmor rules, but here is how one can disable the apparmor completely for libreoffice. This has some security risks if you open untrusted files.
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.* /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.*
add a comment |
up vote
0
down vote
up vote
0
down vote
The problem is caused by apparmor denying access to DBUS socket.
This can be seen in dmesg
output:
audit: type=1400 audit(1542789068.289:1060): apparmor="ALLOWED"
operation="connect"
info="Failed name lookup - disconnected path"
error=-13 profile="libreoffice-soffice"
name="run/user/1000/bus" pid=9545
comm="soffice.bin" requested_mask="wr"
denied_mask="wr" fsuid=1000 ouid=1000
I didn't find out how to fix the actual problem with the apparmor rules, but here is how one can disable the apparmor completely for libreoffice. This has some security risks if you open untrusted files.
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.* /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.*
The problem is caused by apparmor denying access to DBUS socket.
This can be seen in dmesg
output:
audit: type=1400 audit(1542789068.289:1060): apparmor="ALLOWED"
operation="connect"
info="Failed name lookup - disconnected path"
error=-13 profile="libreoffice-soffice"
name="run/user/1000/bus" pid=9545
comm="soffice.bin" requested_mask="wr"
denied_mask="wr" fsuid=1000 ouid=1000
I didn't find out how to fix the actual problem with the apparmor rules, but here is how one can disable the apparmor completely for libreoffice. This has some security risks if you open untrusted files.
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.* /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.*
answered Nov 21 at 8:50
jpa
48423
48423
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094728%2fmenubars-missing-in-libreoffice-when-used-in-unshare-session-in-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
92,BzkreYZfAxN1hqqI3DsjmwlJS,4IUVTzLnn1Ul1 gAbIj GYupgVqec9v0KVD2