Comment history
Versions of a comment on Issues installing the new desktop client. The update hangs, newest first.
Current version | Edited by omster
Changes
Removed: I also had Fluxer Canary hang at the 'Starting...' phase for a solid 20-30s through an AppImage install/update (previous files existed from before the yellow-blue auto-merge @ ~/.config/fluxercanary). Unfortunately the diagnostics button didn't appear so I hadn't copied it before closing the app.Added: I also had Fluxer Canary hang, but at the 'Starting...' phase for a solid 20-30s through an AppImage install/update (previous files existed from before the yellow-blue auto-merge @ ~/.config/fluxercanary). Unfortunately the diagnostics button didn't appear so I hadn't copied it before closing the app.Resolved it by closing the app, and deleting the modules and Cache folder. The Cache folder had ballooned to 500MB~ compared to the 32MB it's sitting at now after deleting the app image and re-running the install after launching through Gear Lever
Show
I also had Fluxer Canary hang, but at the 'Starting...' phase for a solid 20-30s through an AppImage install/update (previous files existed from before the yellow-blue auto-merge @ ~/.config/fluxercanary). Unfortunately the diagnostics button didn't appear so I hadn't copied it before closing the app.
Resolved it by closing the app, and deleting the modules and Cache folder. The Cache folder had ballooned to 500MB~ compared to the 32MB it's sitting at now after deleting the app image and re-running the install after launching through Gear Lever
Edited by omster
Changes
Removed: I also had Fluxer Canary hang at the 'Starting...' phase for a solid 20-30s through an AppImage install/update (previous files existed @ ~/.config/fluxercanary). Unfortunately the diagnostics button didn't appear so I hadn't copied it before closing the app.Added: I also had Fluxer Canary hang at the 'Starting...' phase for a solid 20-30s through an AppImage install/update (previous files existed from before the yellow-blue auto-merge @ ~/.config/fluxercanary). Unfortunately the diagnostics button didn't appear so I hadn't copied it before closing the app.Resolved it by closing the app, and deleting the modules and Cache folder. The Cache folder had ballooned to 500MB~ compared to the 32MB it's sitting at now after deleting the app image and re-running the install after launching through Gear Lever
Show
I also had Fluxer Canary hang at the 'Starting...' phase for a solid 20-30s through an AppImage install/update (previous files existed from before the yellow-blue auto-merge @ ~/.config/fluxercanary). Unfortunately the diagnostics button didn't appear so I hadn't copied it before closing the app.
Resolved it by closing the app, and deleting the modules and Cache folder. The Cache folder had ballooned to 500MB~ compared to the 32MB it's sitting at now after deleting the app image and re-running the install after launching through Gear Lever
Original by omster
Show
I also had Fluxer Canary hang at the 'Starting...' phase for a solid 20-30s through an AppImage install/update (previous files existed @ ~/.config/fluxercanary). Unfortunately the diagnostics button didn't appear so I hadn't copied it before closing the app.
Resolved it by closing the app, and deleting the modules and Cache folder. The Cache folder had ballooned to 500MB~ compared to the 32MB it's sitting at now after deleting the app image and re-running the install after launching through Gear Lever