- Created PROXMOX_COMPATIBILITY.md with detailed analysis
- Added check_proxmox() function to detect Proxmox VE hosts
- Shows warning about potential issues (RAM allocation, kernel params)
- Allows user to continue or abort
- Updated README.md with Proxmox warning
- Recommends running inside VMs instead of on host
Key concerns on Proxmox host:
- zram reduces RAM available for VMs
- tmpfs allocates up to 40% of RAM
- Desktop kernel parameters not optimal for hypervisor
- Safe to use: inside VMs or monitoring scripts only
- Replace ((configured_count++)) with configured_count=$((configured_count + 1))
- This fixes script exiting prematurely after configuring first application
- Issue: ((var++)) returns old value (0) which causes exit with set -euo pipefail
- Fixed 14 instances across the configure_applications_for_tmpfs function
Critical bug fix:
- Script was exiting after 'Application Configuration Status:'
- Issue: ((total_browsers++)) returns 1 when var is 0
- With 'set -e', non-zero return causes immediate exit
- Solution: Use var=$((var + 1)) instead of ((var++))
Changed all increment operations:
- ((total_browsers++)) → total_browsers=$((total_browsers + 1))
- ((configured_browsers++)) → configured_browsers=$((configured_browsers + 1))
This prevents script termination and allows proper browser detection
to complete and display configuration status for all browsers.
- Replace simple yes/no check with detailed per-app status display
- Show configuration status for each detected browser individually
- Display Firefox, Brave, Chrome, Chromium status separately
- Show NPM and Pip configuration status
- Always show status even when apps are configured
- Allow reconfiguration even if some apps are already set up
- Count configured vs total browsers for smart prompting
Output example:
📱 Application Configuration Status:
✅ Firefox: Configured
⚠️ Brave: Not configured
✅ Chromium: Configured
⚠️ NPM: Not configured
Benefits:
- Users can see exactly which apps are configured
- Easy to identify missing configurations
- Can reconfigure specific apps without full reset
- More transparent and informative
- Rewrite browser detection to check config directories instead of commands
- Fix Brave browser detection and configuration (was not being reported)
- Add proper support for Chromium installed via snap
- Separate detection for each browser (Firefox, Brave, Chrome, Chromium)
- Each browser now reports configuration success individually
- Remove standalone configure-apps-for-tmpfs.sh script per user request
- Keep all functionality in the all-in-one optimizer script
- Update README to remove reference to standalone script
Fixes:
- Brave browser now properly detected via ~/.config/BraveSoftware
- Chromium detected even when installed as snap package
- All browsers report their configuration status
- Cleaner, more reliable directory-based detection
- Add check for application configuration when system is already optimized
- Prompt user to configure apps even if tmpfs mounts already exist
- Create standalone configure-apps-for-tmpfs.sh script
- Detect if applications are already configured (Firefox prefs check)
- Skip redundant configuration attempts with 'already configured' messages
- Add backup timestamp to avoid overwriting previous backups
- Update README with new configuration script
Benefits:
- Users with existing tmpfs can now configure applications
- Standalone script allows re-configuration without full optimizer run
- Smarter detection prevents duplicate configurations
- Better user experience for incremental optimization
- Auto-detect and configure Firefox cache location in prefs.js
- Auto-create optimized .desktop launchers for Chrome/Chromium/Brave
- Auto-configure NPM and Pip cache directories
- Auto-link KDE/Plasma thumbnail cache to tmpfs
- Add configure_applications_for_tmpfs() function with smart detection
- Backup original configs before modification
- Set proper ownership and permissions for all cache directories
- Replace manual setup instructions with automatic configuration
- Show progress of configured applications with count
- Update next steps to reflect automatic setup
Benefits:
- Zero post-setup manual configuration needed
- Immediate performance improvement on app restart
- Safer with automatic backups and proper permissions
- Better user experience with clear progress reporting
- Remove unused overlay filesystem configuration and references
- Remove overlayfs sections from all profile JSON files
- Remove OVERLAY_ENABLED/OVERLAY_PROTECT_CONFIGS from config
- Update documentation to focus on tmpfs optimization
- Add overlay detection and removal functionality for cleanup
- Add remove_overlays() function with safe unmounting
- Add overlay status reporting in final optimization summary
- Add test-overlay-detection.sh for testing detection logic
- Simplify codebase by removing complex unused features
- Focus on proven desktop optimizations (tmpfs, zram, kernel)
Resolved conflicts by keeping our comprehensive enhancements:
- Complete tmpfs functionality with German locale support
- Enhanced system scanning and detailed information display
- Fixed division by zero errors and improved error handling
- All bug fixes and performance improvements maintained
- Fixed missing setup_tmpfs() function that was causing silent failures
- Added comprehensive system scanning for browsers, IDEs, gaming caches
- Implemented detailed optimization information display for transparency
- Added German locale compatibility for 'free' command (Speicher: vs Mem:)
- Fixed division by zero errors in RAM calculations
- Created tmpfs-info.sh helper script for detailed status reporting
- Enhanced scanning to work on already-optimized systems
- Added comprehensive optimization breakdowns with purpose explanations
🐛 **Critical Issue Fixed:**
- Identified and resolved 4.35GB RAM waste from duplicate tmpfs mounts
- System had overlapping cache optimizations causing inefficient resource usage
🛠️ **New Tool Added:**
- fix-tmpfs-duplicates.sh: Advanced duplicate detection and consolidation script
🔍 **Duplicate Issues Resolved:**
1. Thumbnail Cache: 2×256MB → 1×256MB (saved 256MB)
2. APT/Package Cache: 2×2GB separate mounts → 1×2GB with proper bind mount (saved 2GB)
3. Browser Cache: Unused optimization mount + active Brave mount → optimized single mount (saved 2GB)
✅ **Results:**
- Reduced tmpfs usage from ~10GB to ~6GB (40% improvement)
- Eliminated all redundant mounts while maintaining functionality
- Proper bind mounting for package cache optimization
- Maintained all existing performance benefits
🔧 **Technical Improvements:**
- Smart detection of existing vs new optimization mounts
- Consolidation without data loss or service interruption
- Preserved active cache usage (550MB Brave cache retained)
- Optimized mount structure for better resource management
💡 **Impact:**
- 4GB+ RAM returned to system for other uses
- Cleaner mount table without redundant entries
- More efficient cache management
- Resolved mount conflicts and overlaps
The tmpfs optimization system now properly consolidates existing
and new mounts, preventing duplicate resource allocation.
