Xfce Forum

Sub domains
 

You are not logged in.

#1 2016-11-30 13:15:43

otamate
Member
Registered: 2016-11-18
Posts: 5

Fedora 25: Desktop became read only, panels OK!

This is weird - I can drag launchers from the menu to a panel, and they stick there and let me launch the app fine. But suddenly clicking any launcher actually on the desktop comes up with Failed to run "{app}" Process org.xfce.FileManager exited with status 1.
Also, when I Right click the desktop, choose desktop settings and "other" as a way to choose the image to change the wallpaper, all the folders on the system have gone read only including those in my home folder.

There is other weirdness. If I  run Virtual Machine Manager I can no longer right click any of the VMs - when I try, nothing happens. Worse is the top "File | Edit | View | Help" Menu no longer shows the drop down with items but instead draws a blue line under each of those entries and that's it - iow, it's all unusable now.

Offline

#2 2016-11-30 15:39:00

ToZ
Moderator
From: Toronto, Canada
Registered: 2011-06-02
Posts: 3,591

Re: Fedora 25: Desktop became read only, panels OK!

Is this a new install or an upgrade from a previous version?
Were there some recent updates that caused this? If so, what was updated?

This is weird - I can drag launchers from the menu to a panel, and they stick there and let me launch the app fine. But suddenly clicking any launcher actually on the desktop comes up with Failed to run "{app}" Process org.xfce.FileManager exited with status 1.

This might be indicative of a dbus-related issue. What does the following return?

env | grep DBUS

Also, how are you logging into Xfce? Are you using the default display manager (lightdm)? You might also consider clearing your sessions cache (delete the ~/.cache/sessions folder when not logged in OR Settings Manager > Session and Startup > Session > Clear saved sessions, and make sure you don't save your session on logout).

Also, when I Right click the desktop, choose desktop settings and "other" as a way to choose the image to change the wallpaper, all the folders on the system have gone read only including those in my home folder.

This is a known bug that has been fixed in the git source. If you're seeing the issue, the fix hasn't made it into Fedora yet. You should open up a fedora bug report. A temporary workaround is to drag the read-only folder to the bookmark section on the left, and it will become selectable.

There is other weirdness. If I  run Virtual Machine Manager I can no longer right click any of the VMs - when I try, nothing happens. Worse is the top "File | Edit | View | Help" Menu no longer shows the drop down with items but instead draws a blue line under each of those entries and that's it - iow, it's all unusable now.

Maybe a theme issue? What appearance theme are you using? Does it help if you change the theme?

EDIT: Also post back the contents of your ~/.xsession-errors file.

Last edited by ToZ (2016-11-30 15:58:40)


How To Ask For Help           Xfce FAQ                            Xfce Release Information
The Xfce Community          Xfce Tips and Tricks

Offline

#3 2016-11-30 17:33:54

otamate
Member
Registered: 2016-11-18
Posts: 5

Re: Fedora 25: Desktop became read only, panels OK!

Hi Toz & thanks for your help.
The whole server was updated from Fed 24 to Fed 25 via the command line

dnf system-upgrade download --releasever=25
dnf system-upgrade reboot

env | grep DBUS returns nothing, just the prompt back.

I log into Xfce with x2go from a Windows 7 client. Its version 4/0/5/2 and has ben fine this way for years now.

"This is a known bug that has been fixed in the git source. If you're seeing the issue, the fix hasn't made it into Fedora yet. You should open up a fedora bug report. A temporary workaround is to drag the read-only folder to the bookmark section on the left, and it will become selectable." Well I wonder why it just hit me now! It obviously worked in the past because I have custom wallpaper, which I now can't change.

"Maybe a theme issue? What appearance theme are you using? Does it help if you change the theme?"
I've not knowingly changed a theme so it must be at the default, if you tell me how to find its name I'll do so.

"EDIT: Also post back the contents of your ~/.xsession-errors file."

cat .xsession-errors
xfce4-session-Message: ssh-agent is already running; starting gpg-agent without ssh support

(xfce4-session:3303): xfce4-session-WARNING **: Unable to launch "xfce4-settings-helper": Failed to execute child process "xfce4-settings-helper" (No such file or directory)

(xfce4-session:3303): xfce4-session-WARNING **: Unable to launch "xfce4-settings-helper": Failed to execute child process "xfce4-settings-helper" (No such file or directory)
SELinux Troubleshooter: Applet requires SELinux be enabled to run.

** (polkit-gnome-authentication-agent-1:3392): WARNING **: Couldn't register with accessibility bus: 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.

** (nm-applet:3401): WARNING **: Couldn't register with accessibility bus: 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.

** (abrt:3399): WARNING **: Couldn't register with accessibility bus: 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.

** (evolution-alarm-notify:3396): WARNING **: Couldn't register with accessibility bus: 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.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[3381:3381:1011/190916:ERROR:background_mode_manager_aura.cc(14)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[3381:3381:1011/190922:ERROR:desktop_window_tree_host_x11.cc(1547)] Not implemented reached in void views::DesktopWindowTreeHostX11::MapWindow(ui::WindowShowState)
[3381:3696:1011/190931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3659:1011/190931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3671:1011/190931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3659:1011/190931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3659:1011/190931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3659:1011/190931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3654:1011/190941:ERROR:cert_verify_proc_nss.cc(880)] CERT_PKIXVerifyCert for www.dalemacartney.com failed err=-8181
[3381:3665:1011/190946:ERROR:channel.cc(316)] RawChannel read error (connection broken)
[3381:3750:1011/191138:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates
[3381:3659:1011/191931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/191931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3659:1011/191931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/191931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3671:1011/192931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/192931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3671:1011/192931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/192931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3659:1011/193931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/193931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3659:1011/193931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/193931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3659:1011/194931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/194931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3659:1011/194931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/194931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3665:1011/195711:ERROR:channel.cc(316)] RawChannel read error (connection broken)
[3381:3659:1011/195931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/195931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[3381:3659:1011/195931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.peruser
[3381:3696:1011/195931:ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host net.ietab.ietabhelper.perbox
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
[3381:3665:1011/200211:ERROR:channel.cc(316)] RawChannel read error (connection broken)

(xfce4-session:3303): GLib-GObject-CRITICAL **: g_value_get_boxed: assertion 'G_VALUE_HOLDS_BOXED (value)' failed

(xfce4-session:3303): libxfce4util-CRITICAL **: IA__xfce_rc_write_list_entry: assertion 'value != NULL' failed

(xfce4-session:3303): GLib-GObject-CRITICAL **: g_value_get_boxed: assertion 'G_VALUE_HOLDS_BOXED (value)' failed

(xfce4-session:3303): libxfce4util-CRITICAL **: IA__xfce_rc_write_list_entry: assertion 'value != NULL' failed
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 1526 requests (1526 known processed) with 2 events remaining.

(polkit-gnome-authentication-agent-1:3392): Gdk-WARNING **: polkit-gnome-authentication-agent-1: Fatal IO error 0 (Success) on X server :0.0.

[3668:3668:1011/190450:ERROR:x11_util.cc(81)] X IO error received (X server probably went away)
[3381:3381:1011/200450:ERROR:chrome_browser_main_extra_parts_x11.cc(56)] X IO error received (X server probably went away)
nm-applet-Message: PID 3401 (we are 3401) sent signal 15, shutting down...

Offline

#4 2016-11-30 18:20:13

ToZ
Moderator
From: Toronto, Canada
Registered: 2011-06-02
Posts: 3,591

Re: Fedora 25: Desktop became read only, panels OK!

env | grep DBUS returns nothing, just the prompt back.

The dbus environment is not being properly started.

"This is a known bug that has been fixed in the git source. If you're seeing the issue, the fix hasn't made it into Fedora yet. You should open up a fedora bug report. A temporary workaround is to drag the read-only folder to the bookmark section on the left, and it will become selectable." Well I wonder why it just hit me now! It obviously worked in the past because I have custom wallpaper, which I now can't change.

This is a recent bug that was introduced by a change in GTK2 (of all places). You should still be able to set different backgrounds by using the workaround I mention above or by right-clicking your image and selecting "Set As Wallpaper" (assuming that the dbus issue above doesn't interfere).

There is other weirdness. If I  run Virtual Machine Manager I can no longer right click any of the VMs - when I try, nothing happens. Worse is the top "File | Edit | View | Help" Menu no longer shows the drop down with items but instead draws a blue line under each of those entries and that's it - iow, it's all unusable now.

Maybe a theme issue? What appearance theme are you using? Does it help if you change the theme?

I've not knowingly changed a theme so it must be at the default, if you tell me how to find its name I'll do so.

Looks like its an existing issue with x2go. See: https://www.mail-archive.com/x2go-user@ … 01840.html

I log into Xfce with x2go from a Windows 7 client. Its version 4/0/5/2 and has ben fine this way for years now.

Unfortunately, I've never used x2go and don't know how it operates. I would suggest the following:

  1. Log into the server locally to confirm whether these issues exist. If they don't (except for the wallpaper one which will) then its most likely an issue with x2go more than it is an issue with Xfce.

  2. Make sure that your x2go startup files (the ones that start the remote Xfce session), source the files in /etc/X11/xinit/xinitrc.d. Among other things, this will setup the dbus environment properly. This should fix the launcher on desktop issue.

  3. Follow up with x2go support on the menu issue in virtual manager if the previous suggest doesn't fix it.


How To Ask For Help           Xfce FAQ                            Xfce Release Information
The Xfce Community          Xfce Tips and Tricks

Offline

Board footer

Powered by FluxBB