We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snarl cannot be launched.
1.When I launch Snarl, this window pops up
2.This is debug logs: -=-=- Snarl logging started -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- bootstrap: Fri, 27 Dec 2019 09:38:34 GMT bootstrap: o/s info follows... platform: Win32NT version: Microsoft Windows NT 6.1.7601 Service Pack 1 service pack: Service Pack 1 bootstrap: server info follows... release: 5.0 api: 47 sys: 47.120 build: 5.0.0 (id=0) bootstrap: getting sysadmin settings... bootstrap: initialising settings... EnvManager.loadAdminSettings(): no redirect.rc EnvManager.loadAdminSettings(): trying from C:\Program Files (x86)\snarl 5.0\sysadmin.json... EnvManager.getSettingsFromPathOrUrl(): "C:\Program Files (x86)\snarl 5.0\sysadmin.json" assumed to be a path... Files.ReadTextFromPath(): failed to read from "C:\Program Files (x86)\snarl 5.0\sysadmin.json": Could not find file 'C:\Program Files (x86)\snarl 5.0\sysadmin.json'. EnvManager.getSettingsFromPathOrUrl(): failed: null file retrieved EnvManager.loadAdminSettings(): failed StartService(): envmgr.service 5.1.0 started ok bootstrap: starting UI... bootstrap: checking user data folders... bootstrap: %APPDATA% is "C:\Users\cp\AppData\Roaming" bootstrap: starting management server on '*:9989'... bootstrap: management server started! bootstrap: SnarlOSD already running bootstrap: starting notification roster... NotificationRoster.Start(): %appdata% is C:\Users\cp\AppData\Roaming\full phat\snarl 5.0\etc NotificationRoster.Start(): loading osd.rc... NotificationRoster.Start(): checking osd presets folder... NotificationRoster.getOsdPresets(): loading osd presets... bootstrap: starting application roster... bootstrap: starting extension roster...
Any advice?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Snarl cannot be launched.
1.When I launch Snarl, this window pops up
![image](https://user-images.githubusercontent.com/2271720/71512095-b9df9380-28cf-11ea-93c1-7c4fce7be269.png)
2.This is debug logs:
-=-=- Snarl logging started -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
bootstrap: Fri, 27 Dec 2019 09:38:34 GMT
bootstrap: o/s info follows...
platform: Win32NT
version: Microsoft Windows NT 6.1.7601 Service Pack 1
service pack: Service Pack 1
bootstrap: server info follows...
release: 5.0
api: 47
sys: 47.120
build: 5.0.0 (id=0)
bootstrap: getting sysadmin settings...
bootstrap: initialising settings...
EnvManager.loadAdminSettings(): no redirect.rc
EnvManager.loadAdminSettings(): trying from C:\Program Files (x86)\snarl 5.0\sysadmin.json...
EnvManager.getSettingsFromPathOrUrl(): "C:\Program Files (x86)\snarl 5.0\sysadmin.json" assumed to be a path...
Files.ReadTextFromPath(): failed to read from "C:\Program Files (x86)\snarl 5.0\sysadmin.json": Could not find file 'C:\Program Files (x86)\snarl 5.0\sysadmin.json'.
EnvManager.getSettingsFromPathOrUrl(): failed: null file retrieved
EnvManager.loadAdminSettings(): failed
StartService(): envmgr.service 5.1.0 started ok
bootstrap: starting UI...
bootstrap: checking user data folders...
bootstrap: %APPDATA% is "C:\Users\cp\AppData\Roaming"
bootstrap: starting management server on '*:9989'...
bootstrap: management server started!
bootstrap: SnarlOSD already running
bootstrap: starting notification roster...
NotificationRoster.Start(): %appdata% is C:\Users\cp\AppData\Roaming\full phat\snarl 5.0\etc
NotificationRoster.Start(): loading osd.rc...
NotificationRoster.Start(): checking osd presets folder...
NotificationRoster.getOsdPresets(): loading osd presets...
bootstrap: starting application roster...
bootstrap: starting extension roster...
Any advice?
The text was updated successfully, but these errors were encountered: