I'm posting this here and not on Murga Linux Forums because I never got my confirmation email from Murga. Besides, I like this community for its informative insight and knowledgeable user base. I appreciate every post here and wind up here more often than not when troubleshooting. I figure by having two communities looking at these issues (i.e., Murga Linux Forums & LinuxQuestions) we'll be able to have more eyes on this distribution and help aid in its development.

I want everyone who has experience using the latest Fatdog64 to weigh in on this conversation and contribute with as much detail as possible (e.g., hardware information, architecture, etc.). Try to find and chronicle any solutions you may have found to your problems posted here; but don't worry if you haven't found any remedies as nobody will judge you, discriminate against you, or think less of you. This is supposed to be a diverse and inclusive thread for everyone. Feel free to ask Fatdog64 related questions as well. I'll be willing to assist in any way I can.

My hardware is as follows (output of inxi -F):
Machine: System: Dell (portable) product: Latitude D630
Mobo: Dell model: 0KU184 Bios: Dell v: A15 date: 11/24/2008
Battery: BAT0: charge: 33.6 Wh 82.0% condition: 41.0/52.0 Wh (79%)
CPU: Dual core Intel Core2 Duo T9300 (-MCP-) cache: 6144 KB
clock speeds: max: 2501 MHz 1: 2000 MHz 2: 1600 MHz
Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
Display Server: X.Org 1.18.3 drivers: intel (unloaded: vesa)
Resolution: 1440x900@59.90hz
GLX Renderer: Mesa DRI Intel 965GM GLX Version: 2.1 Mesa 11.2.2
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.4.19
Network: Card-1: Broadcom NetXtreme BCM5755M Gigabit Ethernet PCI Express
driver: tg3
IF: eth0 state: down mac: ##:##:##:##:##:##
Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi
IF: wlan0 state: up mac: ##:##:##:##:##:##
Drives: HDD Total Size: 151.1GB (4.1% used)
ID-1: /dev/sda model: Patriot_Torch size: 120.0GB
ID-2: USB /dev/sdb model: Ultra_Fit size: 31.1GB
Partition: ID-1: / size: 105G used: 6.0G (6%) fs: ext4 dev: /dev/root
ID-2: swap-1 size: 6.44GB used: 0.30GB (5%) fs: swap dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 43.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 180 Uptime: 9 days Memory: 1847.4/3931.5MB
Client: Shell (bash) inxi: 2.3.0

Issues I've encountered:
yassm doesn't find any network shares from my Windows machines; . MX-Linux could find them with some difficulty with spacefm. I was able to use netdiscover to find IP addresses, but hostname resolution is dysfunctionally listed as "Unknown vendor". I have been able to mount using yassm, but the search function doesn't work.

termit is missing the proper icon referenced from the termit.desktop file. I changed it to be identical with the urxvt icon.

lxqt panel has minor graphical issues with the Application Menu and Date & Time. When you click on either one to expand their menus and proceed to click on any other window or desktop to shift focus, the graphics remain as though they are actively expanded.
Occasionally when rebooting, the Application Menu will open at the top-left of my screen which is peculiar. When this happens, the menu will always open at the top-left instead of the bottom-left until rebooting; ditto for the clock's built in calendar. That's only the half of the story, minimizing when the lxqt panel glitches will animate the windows going upwards instead of downwards. Removing the desktop switcher from the panel takes about 2 tries for it to be saved when rebooting.

I've been attempting to remove the "free disk space" applet from the panel for too long now. I don't need to know I have 98Gb remaining on my drive. Please instruct me on how to remove this.

Uninstalling pidgin, xournal, and osmo still leaves their entries in the Application Menu with missing icons. I deleted their .desktop files as I had no need for them. The entry for x11vnc remained after uninstall, yet its icon was intact.

Gparted is not visible by default in the Utility submenu or any menu. Nodisplay is set to true for some odd reason. I happen to use Gparted often so to be expected to open this through the Fatdog64 Control Panel is inconvenient. I also trimmed down the size by removing multiple language support as I only use US english (perhaps consider making a script to scrub .desktop files of languages you have no need of. I don't think I will ever want GParted in Aramaic, Russian, Chinese, or Japanese. If this were done to many .desktop files, you could shave some Megabytes off of the ISO while reducing sever bandwidth usage).

After uninstalling/installing seemingly unrelated programs, I can no longer launch libreoffice. I have even used it before in Fatdog64 fresh install. In console, it proclaims "libnss3.so: cannot open shared object file: No such file or directory" Additionally, the getlibre.sh script lists neither en_us or US as language options. What have I done to libreoffice? I don't recall ever touching anything related to it. Did xournal's, pidgin's, or seamonkey's uninstall affect libreoffice or was it my installation of Palemoon? I have been digging around for libnss3 files in Pfind. I've found that the exact same filename, libnss3.so, was found in /usr/lib64/palemoon. I think this is a twofold problem with seamonkey uninstallation and palemoon installation.

I've made a workaround by symlinking libnss3.so, libnssutil3.so, libsmime3.so, libssl3.so, libsoftokn3.so, libplds4.so, libplc4.so, libnspr4.so, and libmozsqlite3.so into /usr/lib64. I'm wondering whether its better to symlink using /usr/lib64/palemoon/ or /usr/lib64/palemoon-27.0.3/ as I've read issues arise from symlinking to symlinks, yet if I use the exact version number of palemoon-27.0.3, it will likely break my symlinks each time palemoon needs to update. I could just copy it into /usr/lib64/ but that would take up unnecessary space on my drive.

I decided to symlink from /usr/lib64/palemoon, and all of it works flawlessly now.

This is probably a hardware specific issue, but I will relate it anyway. When I turned off my Dell Latitude D630's WiFi switch, my WiFi shut off as expected; however, when I switched it back on, wpa_gui couldn't get my WiFi to work again. I ended up having to use the Network Wizard to configure my WiFi again, but the interesting thing about the problem is once I configured my WiFi in Network Wizard, the switch works perfectly fine. Perhaps configuring in the console is best for hardware support and should be noted for people with laptop network switches. Another WiFi anomaly regards a vanilla fatdog64 710 install and using only Network Wizard for configuration. When rebooting or on resume from suspend, WiFi connection is lost, yet the adapter is on according to the light indicator on my laptop. I need to then go into wpa_gui and reconfigure my WiFi connection using the proper settings. Then and only then may WiFi work flawlessly in both scenarios.

My advice entails using BOTH methods to configure your wifi to avoid all issues which might arise.