Canary desktop app does not launch on Linux Mint 21.3 Cinnamon

Observed behaviour

I do have the stable branch 508 installed already.
I am a Linux neophyte and exhaust my "things I can try" tools pretty quickly.

System Info: System: Kernel: 5.15.0-187-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.5 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Machine: Type: Desktop Mobo: Micro-Star model: Z370-A PRO (MS-7B48) v: 1.0 serial: <superuser required> BIOS: American Megatrends v: 2.D0 date: 07/06/2024 CPU: Info: 6-core model: Intel Core i5-8500 bits: 64 type: MCP smt: <unsupported> arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 9 MiB Speed (MHz): avg: 2373 high: 3357 min/max: 800/4100 cores: 1: 2156 2: 3357 3: 2177 4: 2091 5: 2397 6: 2065 bogomips: 36000 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: PNY driver: nvidia v: 595.84 pcie: speed: 5 GT/s lanes: 16 ports: active: none off: DVI-D-1,HDMI-A-1 empty: DP-1 bus-ID: 01:00.0 chip-ID: 10de:2184 class-ID: 0300 Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-9:4 chip-ID: 046d:0825 class-ID: 0102 serial: <filter> Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x1080 s-dpi: 81 s-size: 1204x343mm (47.4x13.5") s-diag: 1252mm (49.3") Monitor-1: DVI-D-0 pos: right res: 1920x1080 hz: 75 dpi: 82 size: 598x336mm (23.5x13.2") diag: 686mm (27") Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 75 dpi: 82 size: 598x336mm (23.5x13.2") diag: 686mm (27") OpenGL: renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2 v: 4.6.0 NVIDIA 595.84 direct render: Yes Audio: Device-1: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403 Device-2: NVIDIA TU116 High Definition Audio vendor: PNY driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403 Device-3: Logitech H390 headset with microphone type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-12:6 chip-ID: 046d:0a8f class-ID: 0300 Device-4: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-9:4 chip-ID: 046d:0825 class-ID: 0102 serial: <filter> Sound Server-1: ALSA v: k5.15.0-187-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8 bus-ID: 1-11:5 chip-ID: 0a12:0001 class-ID: e001 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 sub-v: 22bb hci-v: 4.0 rev: 22bb Drives: Local Storage: total: 7.52 TiB used: 2.93 TiB (39.0%) ID-1: /dev/sda vendor: TeamGroup model: TM8PS7001T size: 953.87 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0A0 scheme: GPT ID-2: /dev/sdb vendor: Patriot model: Burst size: 223.57 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 91.2 scheme: MBR ID-3: /dev/sdc vendor: Toshiba model: MG04ACA400N size: 3.64 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: FJ3A scheme: GPT ID-4: /dev/sdd vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: MBR ID-5: /dev/sde vendor: Crucial model: CT1000BX500SSD1 size: 931.51 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 030 scheme: GPT Partition: ID-1: / size: 937.33 GiB used: 189.01 GiB (20.2%) fs: ext4 dev: /dev/sda3 ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 Device-1: 1-7:2 info: Microsoft Ergonomic Mouse type: Mouse,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 045e:082e class-ID: 0300 serial: <filter> Device-2: 1-8:3 info: Razer USA Ornata V3 X type: Keyboard,Mouse driver: razerkbd,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 1532:02a2 class-ID: 0300 Device-3: 1-9:4 info: Logitech Webcam C270 type: Video,Audio driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 046d:0825 class-ID: 0102 serial: <filter> Device-4: 1-11:5 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 0a12:0001 class-ID: e001 Device-5: 1-12:6 info: Logitech H390 headset with microphone type: Audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 046d:0a8f class-ID: 0300 Device-6: 1-13:7 info: Microsoft Xbox360 Controller type: <vendor specific> driver: xpad interfaces: 4 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 045e:028e class-ID: ff00 serial: <filter> Hub-2: 2-0:1 info: Super-speed hub ports: 10 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 Hub-4: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 36 C Fan Speeds (RPM): N/A gpu: nvidia fan: 40% Repos: Packages: 2982 apt: 2947 flatpak: 35 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/nextdns.list 1: deb [signed-by=/etc/apt/keyrings/nextdns.gpg] https: //repo.nextdns.io/deb stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com virginia main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse Active apt repos in: /etc/apt/sources.list.d/openrazer-stable-jammy.list 1: deb [signed-by=/etc/apt/keyrings/openrazer-stable-jammy.gpg] https: //ppa.launchpadcontent.net/openrazer/stable/ubuntu jammy main Active apt repos in: /etc/apt/sources.list.d/winehq.sources 1: deb https: //dl.winehq.org/wine-builds/ubuntu jammy main Info: Processes: 298 Uptime: 13m wakeups: 0 Memory: 31.28 GiB used: 3.28 GiB (10.5%) Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.5 inxi: 3.3.13

Reproduction steps

tried .deb, AppImage, Tar.Gz versions in that order (none launched)
tried to restart
upon restarting, did not open stable branch but ran .deb again. Tried AppImage after that.
No error messages or log that I'm seeing. It's as if it is either not opening or closing immediately

Build information

Fresh Install - Fluxer Canary-2026.825.215649-linux-x86_64 (AppImage, Deb, Tar.gz)

Platform

macOS, Windows, Linux

3 comments

HampusStaff 1 vote 1mo ago originally by @hampus-fluxer on GitHub

Let me know if the latest canary release, 2026.827.132039, solves this problem.

RexSystem 1 vote 1mo ago originally by @Jimmydabomb on GitHub OP

Yes, app launched successfully. Installed from the .deb file. My passkey wasn't being recognized by the app, and it seemed to think I should use one from my linux browser instead of my android phone. I don't currently have a physical passkey on my desktop. I ended up setting up my Authenticator app which the linux client could then utilize. This also was a small challenge as a QR code wasn't generated and for some reason it wouldn't let me C&P the key so I had to manually type in the authenticator key. But all that being done, we're in and working. (I should add that this all came up today after the 827 build was successful in launching. the 825 build didn't even get to the login screen.)

Cool! As for the passkey issue, you could file another bug report for that if you'd like – it does indeed offer the ability to login via a web browser too in case there are any shenanigans with Electron on your platform for the passkey, since you should be able to use the passkey in any case properly in the web app, but ideally there wouldn't be any obstacles here, though at least the immediate problem is solved.