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

Allow bigger log file #245

Open
natsume42 opened this issue Oct 4, 2024 · 0 comments
Open

Allow bigger log file #245

natsume42 opened this issue Oct 4, 2024 · 0 comments

Comments

@natsume42
Copy link

Issue

After observing an issue with cosmic-launcher/pop-launcher, pop-launcher.log file cannot be used for analysis, because it is empty.

Analysis

  • 'init_logging()' (main.rs) resets log file, if it exceeds 1000 bytes.
  • This limit gets easily exceeded already during startup of pop-launcher when log level is set to info/debug/trace.
  • This cleanup logic gets executed whenever pop-launcher is started, which in turn happens whenever cosmic-launcher is hidden.
  • As a net effect, log file gets emptied as soon as cosmic-launcher is hidden, basically deleting all logs of the last observed issue.

Solution Proposal

Until journald is used for logging, I would like to propose to at least increase the threshold value to some bigger value, like at least 1 MiB.

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

1 participant