MobileRead Forums - View Single Post

tigran · 06-08-2016, 07:50 AM

There are not one but two ways to self-destruct this system:

1. Logout (as described before).

2. Rebooting from the previous state being Kobo's Linux environment (with KSM as the base interface of course).

In both cases the "destroyed system" appears like this (maybe someone knows how to recover from it?) --- the panel starts in the second state (the one with lots of useless buttons, some arrows, +/-, image of the Sun etc) instead of the normal state as "system tray" and clicking on "return to normal state" button causes panel to stop completely.

I tried starting xfce4-panel manually from a terminal. It does startup, but as a completely white line at the bottom, no buttons on it.

It just occurred to me that "tray" and "xfce4-panel" are different things. Maybe that "tray" process is responsible for "system tray"? Hmmm, I'll try to figure this out as having to restore from backup every time this happens is quite tedious (even though it is only the rootfs that has to be restored).

UPDATE: I see lots of subdirectories in ~/.config/xfce4/panel --- are they all necessary or is this some junk that can be deleted and re-created on the next startup? Also, I see that (even though nothing actually happened on the system except me entering a few details in OSMO application) 260 files all over the system are different from yesterday's evening backup, most notably these files which I think are the culprit:

home/xu/.config/xfce4/panel/launcher-15/14125051482.desktop
home/xu/.config/xfce4/panel/launcher-26/14112778309.desktop
home/xu/.config/xfce4/panel/launcher-29/141127814211.desktop
home/xu/.config/xfce4/panel/launcher-5/141127843012.desktop
home/xu/.config/xfce4/panel/launcher-7/14183788291.desktop
home/xu/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml
home/xu/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml
home/xu/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml

The xfce4-panel.xml file is very seriously different and this is probably what is causing the broken panel. I wonder how much of this stuff can be safely deleted and re-created on the next startup...

UPDATE: Ok, I have figured out how to configure xfce4-panel after all, so no more restoring from backups. Still, it is very strange that the configuration gets corrupted by such innocent actions like logout or booting into KSM.

06-08-2016, 07:50 AM	#92
tigran Zealot Posts: 140 Karma: 23528 Join Date: Nov 2009 Location: London Device: Kobo Aura One,HD,H2O,Touch,Mini,Kindle 3+DXG,Nook Simple Touch	two ways to self-destruct There are not one but two ways to self-destruct this system: 1. Logout (as described before). 2. Rebooting from the previous state being Kobo's Linux environment (with KSM as the base interface of course). In both cases the "destroyed system" appears like this (maybe someone knows how to recover from it?) --- the panel starts in the second state (the one with lots of useless buttons, some arrows, +/-, image of the Sun etc) instead of the normal state as "system tray" and clicking on "return to normal state" button causes panel to stop completely. I tried starting xfce4-panel manually from a terminal. It does startup, but as a completely white line at the bottom, no buttons on it. It just occurred to me that "tray" and "xfce4-panel" are different things. Maybe that "tray" process is responsible for "system tray"? Hmmm, I'll try to figure this out as having to restore from backup every time this happens is quite tedious (even though it is only the rootfs that has to be restored). UPDATE: I see lots of subdirectories in ~/.config/xfce4/panel --- are they all necessary or is this some junk that can be deleted and re-created on the next startup? Also, I see that (even though nothing actually happened on the system except me entering a few details in OSMO application) 260 files all over the system are different from yesterday's evening backup, most notably these files which I think are the culprit: home/xu/.config/xfce4/panel/launcher-15/14125051482.desktop home/xu/.config/xfce4/panel/launcher-26/14112778309.desktop home/xu/.config/xfce4/panel/launcher-29/141127814211.desktop home/xu/.config/xfce4/panel/launcher-5/141127843012.desktop home/xu/.config/xfce4/panel/launcher-7/14183788291.desktop home/xu/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml home/xu/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml home/xu/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml The xfce4-panel.xml file is very seriously different and this is probably what is causing the broken panel. I wonder how much of this stuff can be safely deleted and re-created on the next startup... UPDATE: Ok, I have figured out how to configure xfce4-panel after all, so no more restoring from backups. Still, it is very strange that the configuration gets corrupted by such innocent actions like logout or booting into KSM. Last edited by tigran; 06-08-2016 at 11:18 AM.