25 Dec

LXDE: desktop manager is not active

I’ve got some memory-intensive works to do recently. So I managed to log in to lxde desktop again last night after repairing a long-pending black screen problem by just uninstalling Nvidia driver.

However, I came up with a new problem this morning. After I set wallpaper on an external monitor, the desktop-preference program crashed by reporting "desktop manager is not active" and I got a wrongly configured wallpaper as an accompanying result. The link here said that this is because the pcmanfm failed to draw desktop at startup. Manually redraw desktop by executing:
pcmanfm --desktop &
will restore desktop-preference. I planned to add this command to autostart menu and found that there was already a similar command:
pcmanfm --desktop --profile LXDE
Obviously, this is the failed command which caused the trouble. It seems that an LXDE profile config file related to this command was corrupted.
I finally found this desktop-items-0.conf file under /home/user/.config/pcmanfm/LXDE and modified the wallpaper related settings in it to default. To be specific:

wallpaper_mode=crop
wallpaper=/usr/share/backgrounds/images/default.png

Actually, I copied these 2 lines from a desktop-items-1.conf file in the same folder.

15 Oct

Memory problem of VMPlayer14 on Fedora26

Upgraded My Fedora to 26 today and found my VMplaye-12.5.7 can not be started on Fedora 26. So I reinstalled vmplayer with version 14. VMplayer14 started properly, but when I started a VM, an error occurred as

” The virtual machine is unable to reserve memory“.

I tried several times, it reported either

” The virtual machine is unable to reserve memory” or “Not enough physical memory is available to power on this virtual machine”.

The vm’s memory is 1G, and I still have more than 4G free memory at the moment, so it can’t be the shortage of the memory that causes the problem. I searched for a while and found the solution here: https://communities.vmware.com/thread/573966

What is needed is the vmware-host-module patch from GitHub. Download the correct branch which corresponds to the vmware version, that is player-14.0.0 in my case, and do the following operations :

tar -cf vmmon.tar vmmon-only/

tar -cf vmnet.tar vmnet-only/

cp *.tar /usr/lib/vmware/modules/source/

Then remove the .ko files from /lib/modules/$(uname -r)/misc.

now do

vmware-modconfig –install-all

Then I rebooted the system and tried to run VMplayer again, everything went ok now.

7 Aug

Disable touchpad in fedora25-lxde

As synaptics is no longer available for controlling touchpad, we have to use xinput instead.
First, use command : xinput list to display all input devices and find out touchpad’s number.
In my system the result is:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech M215 2nd Gen id=10 [slave pointer (2)]
⎜ ↳ Logitech M280/320/275 id=11 [slave pointer (2)]
⎜ ↳ Logitech M280/320/275 id=12 [slave pointer (2)]
⎜ ↳ Logitech M280/320/275 id=13 [slave pointer (2)]
⎜ ↳ Logitech M280/320/275 id=14 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=18 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Integrated Camera id=15 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=19 [slave keyboard (3)]

As displayed, my touchpad’s id number is 17. Next, just disable it using the following command:
xinput --disable 17

6 Aug

Ibus not work in LXDE-Fedora

search result talks about an “input method selector” in preference menu which was not found on my system.
solution:
sudo dnf install imsettings-lxde

then you can find “input method selector” in preference menu.

14 Jul

Fedora network icon disappeared

I created a fedora VM on Lubuntu host this afternoon. When I reopen it tonight, I found the network icon on the top-right disappeared and the network function failed too. I tried some solutions on the forum but nothing helped. Therefore I stopped to do something else. When I came back to VMplayer and tried to open the VM file again, I found that there was my “Fedora” folder along with an empty “fedora” folder under the same path, so I think it maybe the duplicated file name which played the trick. I deleted the empty file and opened the VM again, Now the problem is gone.