Skip to content
New issue

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

STATS not opening #2121

Closed
nicolopadovan opened this issue Sep 13, 2024 · 4 comments
Closed

STATS not opening #2121

nicolopadovan opened this issue Sep 13, 2024 · 4 comments

Comments

@nicolopadovan
Copy link
Contributor

nicolopadovan commented Sep 13, 2024

Describe the bug
When trying to open the Stats app - and even ad Login when it automatically tries to open up -, the app does not open at all.
I encountered only a couple of instances in which it did flash some widgets, but closed right after.

Streaming from the console while trying to open the app, I get the following message:

Couldn't read values in CFPrefsPlistSource<0x6000015b0ea0> (Domain: eu.exelban.Stats.widgets, User: kCFPreferencesAnyUser, ByHost: Yes, Container: (null), Contents Need Refresh: Yes): Using kCFPreferencesAnyUser with a container is only allowed for System Containers, detaching from cfprefsd

This might be related to issue #2047

Details:

  • Device: Macbook Pro 2021 16" M1 Max 64RAM
  • macOS: 14.6.1 (Sonoma)
  • Application version: 2.11.9 (2.11.8 and 2.11.7 do have the same issue as well)
@exelban
Copy link
Owner

exelban commented Sep 13, 2024

there is any crash reports?

@nicolopadovan
Copy link
Contributor Author

nicolopadovan commented Sep 13, 2024

There is no crash report; I provided everything I managed to quickly gather.
If helpful:

/Applications/Stats.app/Contents/MacOS/Stats ; exit;
(base) user@username ~ % /Applications/Stats.app/Contents/MacOS/Stats ; exit;
2024-09-13 13:50:40 reader.swift:85 DBG [<CPU.LoadReader: 0x150a4b9e0>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:159 DBG [<CPU.ProcessReader: 0x6000016f8090>] Set update interval: 1 sec
2024-09-13 13:50:40 reader.swift:85 DBG [<CPU.ProcessReader: 0x6000016f8090>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:159 DBG [<CPU.AverageReader: 0x6000016f85a0>] Set update interval: 60 sec
2024-09-13 13:50:40 reader.swift:85 DBG [<CPU.AverageReader: 0x6000016f85a0>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:85 DBG [<CPU.TemperatureReader: 0x6000016f8630>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:85 DBG [<GPU.InfoReader: 0x6000016ff7b0>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:85 DBG [<RAM.UsageReader: 0x600001be6d00>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:159 DBG [<RAM.ProcessReader: 0x6000016f5200>] Set update interval: 1 sec
2024-09-13 13:50:40 reader.swift:85 DBG [<RAM.ProcessReader: 0x6000016f5200>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:85 DBG [<Disk.CapacityReader: 0x600000a81a00>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:159 DBG [<Disk.ActivityReader: 0x600000ab2500>] Set update interval: 1 sec
2024-09-13 13:50:40 reader.swift:85 DBG [<Disk.ActivityReader: 0x600000ab2500>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:159 DBG [<Disk.ProcessReader: 0x6000016f53b0>] Set update interval: 1 sec
2024-09-13 13:50:40 reader.swift:85 DBG [<Disk.ProcessReader: 0x6000016f53b0>] Successfully initialize reader
2024-09-13 13:50:40 reader.swift:85 DBG [<Sensors.SensorsReader: 0x6000015c4be0>] Successfully initialize reader
2024-09-13 13:50:41 readers.swift:288 DBG [<Sensors.SensorsReader: 0x6000015c4be0>] Found 2 fans
zsh: trace trap  /Applications/Stats.app/Contents/MacOS/Stats

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

@exelban
Copy link
Owner

exelban commented Sep 13, 2024

I don't see any internal reason then if there is no crash report. Only some external impact.

@exelban exelban closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
@nicolopadovan
Copy link
Contributor Author

nicolopadovan commented Sep 13, 2024

I don't see any internal reason then if there is no crash report. Only some external impact.

My bad, I just found the crash reports: these were not shown as a popup.
Hopefully I am not leaking any personal information :D

The Full Report can be found here
And the Translated Report here

@exelban

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants