Reply to thread

Message: [QUOTE="Bombastus, post: 91166, member: 2178"] The current Reverie 1.14 Linux download is a roughly 71 MiB ZIP containing both an amd64 DEB and x86_64 AppImage. They are alternatives, so installing the DEB and keeping the AppImage active only creates two copies to manage. Extract the archive before choosing, because the commands need real files, not a file manager’s preview of ZIP contents. Both builds require a 64-bit x86 Linux desktop, glibc 2.31 or newer, and 4 GB of RAM. Ubuntu 20.04 and Debian 11 meet the stated baseline, while current Fedora and rolling distributions normally exceed it. An ARM machine reporting aarch64 cannot run this release natively. That practical detail sits outside [B][URL='https://goldmidi.com/community/threads/parallel-minds-brought-reverie-1-14-to-linux.76476/']Reverie’s move onto Linux desktops[/URL][/B], which announces availability without explaining the package decision. The downloaded README is unusually direct. Its [B]two-package Linux bundle[/B] recommends the DEB for Debian-family systems and the portable AppImage elsewhere. [HEADING=2]The DEB gives Debian systems cleaner integration[/HEADING] On Debian, Ubuntu, or Linux Mint, open a terminal in the extracted folder and run sudo apt install ./reverie_*.deb. The leading ./ tells APT to install the local package rather than search configured repositories for that name. APT can then resolve the declared libc6, libstdc++6, and libgl1 dependencies. The package places Reverie under /opt/reverie, adds a reverie command, and creates an applications-menu entry. It also recommends a desktop file chooser and a clipboard helper, which matter when you browse for source audio or paste a Pro license key. This is the less fiddly route on a compatible distribution. The DEB itself is about 31.8 MB, but its declared installed size is roughly 150 MiB because it unpacks bundled libraries and resources. That footprint is separate from the audio files you later generate and save. APT may print an unsandboxed-download warning involving the _apt user when the DEB remains in a private Downloads folder. The bundled instructions classify that warning as harmless when the terminal also confirms that Reverie was set up. Moving the DEB into /tmp before installation avoids the warning without changing the installed program. Removing this build later is straightforward with sudo apt remove reverie. That command removes the system package but leaves your personal license, settings, and presets under ~/.config/reverie/. Keeping or deleting that directory should therefore be a separate, deliberate decision. [HEADING=2]The AppImage trades integration for portability[/HEADING] Fedora, Arch, openSUSE, and other non-Debian systems get the AppImage path. Move the roughly 43.4 MB file somewhere permanent, grant execution permission with chmod +x Reverie-*-x86_64.AppImage, then run it directly. Root access and a package installation are unnecessary. Location matters more than it first appears. A menu shortcut or pinned launcher points to the AppImage file itself, so moving it later can break that entry. Keeping versioned AppImages in a stable applications directory also makes it obvious which build is actually opening. The AppImage cannot assume that a clipboard helper exists. On Wayland, installing wl-clipboard enables reliable license-key pasting, while X11 users can provide xclip or xsel. File selection also depends on a working desktop portal or a compatible dialog provider such as Zenity or KDialog. An AppImage does not become part of the distribution’s normal package-update stream. Reverie can check for a newer release, but replacing the downloaded executable remains distinct from a repository upgrade. Retaining the version number in its filename prevents an older copy from quietly surviving beside the current one. Deleting the AppImage removes that program copy but does not erase ~/.config/reverie/. Your settings and license can therefore survive a binary replacement, which is useful during upgrades but important to remember during a complete uninstall. [HEADING=2]Small dependencies explain most launch failures[/HEADING] Run uname -m before troubleshooting anything deeper. A result of x86_64 confirms the supported processor architecture, while ldd --version reveals whether glibc reaches the required 2.31 baseline. Failure on an older system is a compatibility limit, not an audio-driver problem. Playback and file access fail through different Linux layers. Reverie can send audio through ALSA, PulseAudio, or PipeWire, while its source dialogs depend on xdg-desktop-portal or a compatible dialog provider. A silent preview points toward audio configuration, while a missing chooser points toward desktop integration. Reverie 1.14 also repairs a specific startup crash that affected proprietary NVIDIA drivers under Wayland in builds through 1.13.7. Those older packages bundled Wayland libraries missing a required symbol and could fail before drawing a window. The current build uses the system libraries, so disabling Wayland should not be the first response to that old error. If Reverie opens but cannot display a file picker, inspect the desktop portal rather than reinstalling the audio stack. If the license key will not paste, check the session type and its clipboard helper. The configuration directory remains ~/.config/reverie/, making it the small but essential item to preserve before a clean reinstall or system migration. [/QUOTE]

Name