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.

Sign up for GitHub

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

Jump to bottom

Warning message when opening a book #634

Closed
3 tasks done
braoult opened this issue Nov 6, 2022 · 0 comments
Closed
3 tasks done

Warning message when opening a book #634

braoult opened this issue Nov 6, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@braoult
Copy link

braoult commented Nov 6, 2022

I've already installed the latest developer version of Koodo Reader, this problem still exsits

  • Yes

There are no similar issues on the issue list

  • Yes

I've already read the document, still can't solve it.

  • Yes

Operating system or browser

Ubuntu

App Version

1.4.9

Bug Detail

The program has unexpected warning on standard error when opening a book (no warning until we pick a book from library) :

(node:105112) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `exe --trace-deprecation ...` to show where the warning was created)

Screenshots (Optional)

No response

Files (Optional)

No response
@braoult braoult added the bug Something isn't working label Nov 6, 2022
@braoult braoult changed the title Error output Warning message when opening a book Nov 6, 2022
troyeguo added a commit that referenced this issue Jan 25, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
f6d1fe3 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674
troyeguo added a commit that referenced this issue Jan 25, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
a005d91 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674
troyeguo added a commit that referenced this issue Jan 25, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
7fe73f6 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674

Former-commit-id: a005d91
troyeguo added a commit that referenced this issue Mar 2, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
f8dc153 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674

Former-commit-id: a005d91
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@braoult