[BUG] Multiple warnings when launching Karing

Open
#2,102 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
dart, linux
Domain
desktop

Research direction

The warnings come from the libcurl dynamic loader check for /usr/share/karing/lib/libsentry.so, a GDK cursor theme message, and libayatana-appindicator deprecation output, all shown in the log. Start by reproducing on Linux by running karing from a terminal and checking which package provides each library. Done means the maintainers agree which warnings are real dependency or compatibility problems and a fix or a documented decision for each exists.

Written by the indexing model from the issue text.

Description

操作系统/Operating System

Linux

系统版本/Operating System Version

Fedora

App版本/App Version

1.2.26.2931

描述/Describeption

Launching Karing from the terminal produces several warnings related to libcurl, GTK, GDK and Ayatana AppIndicator.

Please investigate these startup warnings and check whether they indicate missing dependencies, compatibility issues or outdated library usage.

复现步骤/Reproduction steps
  1. Open a terminal.
  2. Run karing.
  3. Observe the warnings printed during startup.
日志/Log
user@fedora:~$ karing
karing: /lib64/libcurl.so.4: no version information available (required by /usr/share/karing/lib/libsentry.so)
Gdk-Message: 14:00:17.184: Unable to load  from the cursor theme

(karing:10227): libayatana-appindicator-WARNING **: 14:00:18.804: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
Dominant language
Dart
Stars
16k
Forks
1.3k
Avg merge
19h 39m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KaringX/karing

All issues in KaringX/karing

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.