Github messages for voidlinux
 help / color / mirror / Atom feed
From: nuckle <nuckle@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Kdeconnect doesn't use qt theme and doesn't send files
Date: Wed, 05 Jun 2024 20:47:12 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50706@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]

New issue by nuckle on void-packages repository

https://github.com/void-linux/void-packages/issues/50706

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.32_1 x86_64 GenuineIntel notuptodate rrrmFFFFFFFF

### Package(s) Affected

kdeconnect-24.02.2_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

A working qt theme and an ability to send file to other devices (android in this case)

### Actual behaviour

- Qt theme is applied only partially (in KDE Connect Settings and KDE Connect Indicator)
- Files don't send to android device via gui (works fine in `kdeconnect-cli`)


<details>
  <summary>Preview</summary>
  
![image](https://github.com/void-linux/void-packages/assets/37220313/52ae2c71-c9f1-4b37-847d-38318590c721)

 
</details>

### Steps to reproduce

I updated the package recently and noticed this bug. Didn't change anything in my configuration. Other QT programs work fine

1. Run `kdeconnect-app`

             reply	other threads:[~2024-06-05 18:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 18:47 nuckle [this message]
2024-06-06  2:18 ` KDE Connect doesn't use user's " Luciogi
2024-06-06  7:42 ` nuckle
2024-06-06  7:42 ` nuckle
2024-06-06  9:30 ` Luciogi
2024-06-06  9:49 ` nuckle
2024-06-07 12:07 ` Dr64h
2024-06-07 13:26 ` Luciogi
2024-06-07 13:26 ` Luciogi
2024-06-07 13:32 ` nuckle
2024-06-07 13:41 ` Luciogi
2024-06-07 13:41 ` Luciogi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50706@inbox.vuxu.org \
    --to=nuckle@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).