[kontact] [Bug 470092] Unable to view mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=470092 Odin Vex changed: What|Removed |Added Version|23.04.1 |6.1.0 Component|general |mail Assignee|claudio.cam...@kde.org |kdepim-b...@kde.org Product|Merkuro |kontact -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 470092] Unable to view mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=470092 --- Comment #2 from Odin Vex --- (In reply to Kwon-Young Choi from comment #1) > *** Bug 488298 has been marked as a duplicate of this bug. *** This bug is actually about KMail, but I was unable to find kmail (alone) in the list. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #19 from Odin Vex --- > (In reply to Odin Vex from comment #18) In short, you would not see 'org.kde.smb4k', you would see an unorganized list of: URL1 URL2 URL3 Each would have the username and password. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #18 from Odin Vex --- (In reply to Alexander Reinholdt from comment #17) > It basically looks like this: > > org.kde.smb4k > |-> URL 1: username:password > |-> URL 2: username:password > |-> URL 3: username:password > |-> ... I think the assumption is 'folder/single-entry'. To the best of my knowledge QtKeychain API does not have the concept of 'folders', they're just 'entries', nothing like an array. In KeePassXC, for example, you can manually make your own under an exposed group. It'll just be # entries of key:value, though. Take Tokodon, for example. I have multiple entries of 'Tokodon' for one account. The 'user' has an appended strings of 'access-token' and 'client-secret'. Perhaps you might could try a Tokodon account and see how a typical manager stores it, such as KeePassXC. Maybe it'll help clear up what I'm trying to describe, too. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #15 from Odin Vex --- > No. Everything will be saved in a secure storage (KWallet, Gnome Keyring, > etc.). How are credentials for multiple servers stored in a single key:value then without serialization? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #13 from Odin Vex --- > If QtKeychains API allows for accessing the list of all login credentials in > the future The only difference here is that it would be implemented in SMB4K. The value returned would just be deserialized as a string list. SMB4K needs to access any/all credentials just to mount any/all remotes. Frankly, I think trying to use multiple entries in a Secret Service defeats the purpose of management to begin with. One entry per software, credential(s) are returned as a singular entity (be it an entry or a collection of entries). I think it simplifies things and gives the software control when the software is allowed to serialize as desired. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 Odin Vex changed: What|Removed |Added Resolution|FIXED |LATER Status|RESOLVED|VERIFIED --- Comment #12 from Odin Vex --- (In reply to Alexander Reinholdt from comment #11) > I thought about the serialized approach and possible alternatives. > > I don't like serialized one, because you squeeze all login credentials into > one entry and you either have to read it once and store all credentials in > memory (i.e. in a hash or map) or you have to read everything each time the > program asks for credentials. In any case you have to implement some search > logic to pick the right credentials. Similar things are true for > writing/saving. This is too much overhead for me. That already happens just because we're using credentials. > Another way would be to store the username and password for each server or > share separately, but have a list of all network items in the secure > storage. After starting to implement this, I did not like it and also > decided against it. So it's back to storing everything in a file? > I implemented to possibility to edit the authentication information long > time ago. Looking back, I almost never used it except defining the default > login credentials. If the username or password for a server or share need to > be changed, you can do this with/in the password dialog withou even opening > the configuration dialog. The default credentials can still be defined > there. And when you want to clean up, you can do this with the GUI of the > password manager. You might not have used it but others may very well have (myself, for example). > So, for the time being, I will leave the code as it is now. If QtKeychains > API allows for accessing the list of all login credentials in the future, I > will maybe reimplement the functionality. I'd rather see the credentials clear-text in an rc file than this decision. I think I'll just privately fork it and address it using serialization. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #10 from Odin Vex --- (In reply to Alexander Reinholdt from comment #9) > (In reply to Odin Vex from comment #7) > > Key: "smb4k", Value: "SerializedArray" would work. One key, "smb4k" (since > > this is per user already). The value is a serialized array. > > Okay, that's better than the solution I thought about. However, this > solution is still quite awkward. It may be awkward but it's a forward-compatible work-around and I think that's most important. It'd allow editing via GUI, easy updating for a future change (if any)..seems to be the best approach so far. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #8 from Odin Vex --- Note that serialized is just a placeholder for abstraction. The value can be "MountURIA:PasswordForThisServer MountURIB:PasswordForThatServer MountURIC:PasswordForThatServer MountURID:PasswordForThatServer" etc. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #7 from Odin Vex --- > If I understand correctly, you suggest to save the login credentials as one > data object (collection) into the secret storage. As far as I can see that > won't work, because QtKeychain only allows saving key/value pairs (strings). Key: "smb4k", Value: "SerializedArray" would work. One key, "smb4k" (since this is per user already). The value is a serialized array. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #5 from Odin Vex --- *to provide -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #4 from Odin Vex --- (In reply to Alexander Reinholdt from comment #3) > Git commit 9ce91398edbe5501a9f6e49fcdac9b0c5d086692 by Alexander Reinholdt. > Committed on 30/05/2024 at 08:54. > Pushed by areinholdt into branch 'master'. > > The login credentials are now stored using QtKeychain. This allows the usage > of other secure > storage solutions apart from KWallet. > > Since QtKeychain does not provide access to all login credentials Smb4K > stored, we lost the > capability to edit the login credentials in the configuration dialog. You > need to use the > respective editor program (i.e. kwalletmanager, KeePassXC, ...) to edit or > remove the login > credentials. Would libsecret have been a better option for enumeration or could the way secrets are stored be a collection of all top provide a workaround for QtKeychain? -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend on Xorg
https://bugs.kde.org/show_bug.cgi?id=417157 --- Comment #21 from Odin Vex --- Joy, more 'find the thing you're looking for' to go through. KDE's settings is a marvel mess as it is. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend
https://bugs.kde.org/show_bug.cgi?id=417157 --- Comment #19 from Odin Vex --- I'd angle for ColorD-KDE to be updated supporting Wayland just as it used to X11 and continue to use Color Management as a means to change display/device calibration, just as it's always been used. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend
https://bugs.kde.org/show_bug.cgi?id=417157 --- Comment #18 from Odin Vex --- REVOY is correct as far as I've been able to tell. When I first upgraded to KDE 6 I couldn't get Color Management to even work as it did (with Wayland, it worked on my system for some reason). Instead I -accidentally- found color profile assignment in the Display Configuration settings. Color Management is where any/all of that should be, just like every other system. This way we can calibrate/assign profiles to any/all devices, not just displays. I'm not sure who moved it and why but it makes no sense whatsoever to put the option on the Display Configuration and only for displays. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #1 from Odin Vex --- For some reason I wasn't able to specify the version of Smb4k, 3.2.5. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] New: Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 Bug ID: 486474 Summary: Smb4k does not support alternatives to KDE Wallet Classification: Applications Product: Smb4k Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: odin@ethicalexploiting.com Target Milestone: --- SUMMARY Smb4k does not use libsecret (to support alternatives to KDE Wallet such as KeePassXC). STEPS TO REPRODUCE 1. Disable KDE Wallet. 2. Enable KeePassXC as Secret Service. 3. Attempt to retrieve/store credentials for bookmarks/mounts. OBSERVED RESULT Credentials are not stored. EXPECTED RESULT Credentials to be stored. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro x64 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION libsecret is often used to replace archaic hard-coding around KDE Wallet. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466392] Cannot login after desktop session restore (Access token error)
https://bugs.kde.org/show_bug.cgi?id=466392 --- Comment #7 from Odin Vex --- (In reply to Odin Vex from comment #6) > I've got this issue. Manjaro, neochat 23.08.5-1. I swapped from KDE Wallet > to KeePassXC (it's set up correctly). Just sits loading. libquotient 0.8.1.2-1 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466392] Cannot login after desktop session restore (Access token error)
https://bugs.kde.org/show_bug.cgi?id=466392 Odin Vex changed: What|Removed |Added Status|RESOLVED|REOPENED CC||odin.vex@ethicalexploiting. ||com Resolution|FIXED |--- --- Comment #6 from Odin Vex --- I've got this issue. Manjaro, neochat 23.08.5-1. I swapped from KDE Wallet to KeePassXC (it's set up correctly). Just sits loading. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 393080] Crash in PodcastSettingsDialog::init
https://bugs.kde.org/show_bug.cgi?id=393080 --- Comment #17 from Odin Vex --- It's great to see this fixed. I hope this hits the AUR soon. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend
https://bugs.kde.org/show_bug.cgi?id=417157 --- Comment #14 from Odin Vex --- (In reply to Nate Graham from comment #12) > It was not designed to work on Wayland and anything that does work is > accidental. Regardless, that's not relevant here since the point is that for > Wayland we have a totally new thing that does not involve colord-kde at all. I hope it works at the login screen, I really need it for some displays. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend
https://bugs.kde.org/show_bug.cgi?id=417157 --- Comment #11 from Odin Vex --- (In reply to Nate Graham from comment #10) > Depends on how you look at it. This bug report is about colord-kde, which > only works on X11. The new thing you're referring to is Wayland-only, and > isn't related to colord-kde. So in principle, their features, limitations, > and bugs will differ. I keep seeing "only works on X11" but I've been running Wayland out of box for nearly 4 years and had no issues with colord-kde "working". No X11 server installed (X over Wayland if I recall). It's only since swapping out a GPU from one vendor to another (same model GPU) that I have to use colormgr now because the UI won't enable "Assign Profile". -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend
https://bugs.kde.org/show_bug.cgi?id=417157 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #7 from Odin Vex --- I swapped out a graphics card (same model, different vendor (AMD->ASUS (AMD)) and now no profiles load, I can't assign or remove, no devices show an associated profile. I have to assign it via shell. *sigh* -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 470985] KRunner goes behind Yakuake
https://bugs.kde.org/show_bug.cgi?id=470985 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #2 from Odin Vex --- It works as expected with Qt 5.15.11 and Plasma 5.27.10. Just reporting in. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 393080] Crash in PodcastSettingsDialog::init
https://bugs.kde.org/show_bug.cgi?id=393080 --- Comment #13 from Odin Vex --- (In reply to Odin Vex from comment #12) > The crash is caused by core-impl/podcasts/sql/PodcastSettingsDialog.cpp, > specifically "buttonBox()->button(QDialogButtonBox::Apply)->setEnabled". > Comment-out every call (3 total) to that and it'll work fine. I didn't have time to peek at the Qt documentation to look into Button Box(es) to determine how best to move forward (aside from commenting them out temporarily). The dialog width and height were also really goofed on my end (AUR clone, edit, cmake ..., make, ran the bin without installation, working). -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 393080] Crash in PodcastSettingsDialog::init
https://bugs.kde.org/show_bug.cgi?id=393080 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #12 from Odin Vex --- The crash is caused by core-impl/podcasts/sql/PodcastSettingsDialog.cpp, specifically "buttonBox()->button(QDialogButtonBox::Apply)->setEnabled". Comment-out every call (3 total) to that and it'll work fine. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463696] System Tray Integration
https://bugs.kde.org/show_bug.cgi?id=463696 --- Comment #8 from Odin Vex --- >Sure someone could implement it, but that person would have to make sure it's >well maintained since we're not personally interested in the feature. We have >more than enough optional code/features and there would have to be a really >good argument to adding more. A simple icon was all that was asked..notifications and such wouldn't even be necessary for that. Just a running-in-the-background useful tray icon. Like any other social-media/chat software. >_> I don't understand the rationale against it, but I guess it is whatever it is, I can always use another client. Personally, I just wanted a full-featured experience and software, I expect it from KDE, unlike Gnome which'll eventually end up a startup-shutdown script itself. *shrug* -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463696] System Tray Integration
https://bugs.kde.org/show_bug.cgi?id=463696 --- Comment #6 from Odin Vex --- > Neither me or Carl want to implement a system tray icon Does this mean you won't allow others to implement it or...? This should not have been marked FIXED, it isn't FIXED. 'INTENTIONAL' (if you won't allow the implementation of a tray icon) or 'UNMAINTAINED' (if you will allow it but just aren't at this time able to do so) would be appropriate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475474] Panel too bright
https://bugs.kde.org/show_bug.cgi?id=475474 --- Comment #6 from Odin Vex --- Wow, did not know that was what that was. I've seen the option but never touched it. It made no sense to me for it to behave the adaptive way. Thank you very much for pointing this out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475474] Panel too bright
https://bugs.kde.org/show_bug.cgi?id=475474 Odin Vex changed: What|Removed |Added Attachment #162235|0 |1 is obsolete|| --- Comment #4 from Odin Vex --- Created attachment 162236 --> https://bugs.kde.org/attachment.cgi?id=162236=edit With Window Maximized Uploaded incorrect second comparative image. This shows the color change when a window has been maximized or any window is under the taskbar, even a small one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475474] Panel too bright
https://bugs.kde.org/show_bug.cgi?id=475474 Odin Vex changed: What|Removed |Added Attachment #162234|Demonstrates taskbar color |Without Windows Under or description||Maximized -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475474] Panel too bright
https://bugs.kde.org/show_bug.cgi?id=475474 --- Comment #3 from Odin Vex --- Created attachment 162235 --> https://bugs.kde.org/attachment.cgi?id=162235=edit Without Windows Under or Maximized Demonstrates the change in taskbar color with any window maximized *or* a window placed *anywhere* under the taskbar (even a small window!) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475474] Panel too bright
https://bugs.kde.org/show_bug.cgi?id=475474
--- Comment #2 from Odin Vex ---
Created attachment 162234
--> https://bugs.kde.org/attachment.cgi?id=162234=edit
Demonstrates taskbar color
Demonstrates taskbar color when no window exists under it and no window
maximized. Included two commonly-known icons ("Peek at Desktop",
"Desktop1-2-3") to show it's the taskbar.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 475474] New: Taskbar too bright
https://bugs.kde.org/show_bug.cgi?id=475474 Bug ID: 475474 Summary: Taskbar too bright Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: odin@ethicalexploiting.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY For some reason the taskbar is entirely too bright unless a window is either maximized or moves under the taskbar. This breaks user themes and looks ugly. I can't read my fonts because of this. EXPECTED RESULT Taskbar should not change colors. No idea why it even does this. It's garish and unsightly, makes fonts more difficult to read. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 436935] Colord disabled under wayland
https://bugs.kde.org/show_bug.cgi?id=436935 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #1 from Odin Vex --- I have the odd experience of colord working until sometime last month on Manjaro, now the log reports 'colord: X11 not detect disabling'. I can manually `systemctl start colord` and my color profiles load with the journal showing: dbus-daemon[935]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.291' (uid=1000 pid=61079 comm="/usr/bin/systemsettings kcm_colord" label="kernel") No X11 fussing at all. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 --- Comment #9 from Odin Vex --- (In reply to Odin Vex from comment #8) > I've also noted that the 16 non-symbolic has an RSS icon instead of podcast, > plus the icon has an artifact, top-left of that circle is distorted. The folder is also colored, for some reason. It's the wrong icon for a podcast folder and it shouldn't be colored (blue default). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 --- Comment #8 from Odin Vex --- I've also noted that the 16 non-symbolic has an RSS icon instead of podcast, plus the icon has an artifact, top-left of that circle is distorted. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 --- Comment #7 from Odin Vex --- (In reply to Manuel de la Fuente from comment #6) > Update: added all the missing icons @ 96px in > https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/273. > By the way, it seems like none of the symbolic/16px are missing, including > `folder-podcast`. They are missing. https://invent.kde.org/frameworks/breeze-icons/-/tree/master/icons/places/48 https://invent.kde.org/frameworks/breeze-icons/-/tree/master/icons/places/96 https://invent.kde.org/frameworks/breeze-icons/-/tree/master/icons/places/symbolic -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 --- Comment #5 from Odin Vex --- (In reply to Nate Graham from comment #4) > Thanks for the info. > > It's not possible to automate this in a way that preserves the pixel-perfect > nature of each size. And if we don't actually care about that, then we can > just use a single base size since SVGs are scalable. But they aren't > scalable in a pixel-perfect way. :) I think it'd be better to have something than nothing. Maybe an SVG base that is automatically converted to each variant and marked for preliminary approval/verification before adjustment. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 --- Comment #3 from Odin Vex --- I'm curious why icon-related stuff like aren't automated from vector/SVG originals, is it because it is low priority? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 --- Comment #2 from Odin Vex --- (In reply to Nate Graham from comment #1) > It looks like the 48, 96, and symbolic directories are missing a lot of > places icons, in fact. Odin, can you comment on the real-world impact that > this is having for you? Ah, certainly, Dolphin and Gtk software that use 'Places' just like Dolphin does can't show any correctly symbolic icon for podcasts if a folder has been set to a 'Places' similar to how ~/Documents and ~/...folders are typically used. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] Icon 'folder-podcast' is missing 3 variants
https://bugs.kde.org/show_bug.cgi?id=471128 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] New: Icon 'folder-podcast' is missing 3 variants
https://bugs.kde.org/show_bug.cgi?id=471128 Bug ID: 471128 Summary: Icon 'folder-podcast' is missing 3 variants Classification: Plasma Product: Breeze Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: odin@ethicalexploiting.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- SUMMARY The Breeze “Places” icon “folder-podcast” is missing 3 variants, specifically: 48, 96, symbolic STEPS TO REPRODUCE 1. See https://invent.kde.org/frameworks/breeze-icons/-/tree/master/icons/places/... folders for missing 'folder-podcast' (and 'folder-podcast-symbolic') icons. OBSERVED RESULT Missing icons. ADDITIONAL INFORMATION All other variants are present, but the symbolic icon (most important variant, given the ability to use others) is critically missing. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 470094] [Feature Request] Show a map when clicking on a contact's address
https://bugs.kde.org/show_bug.cgi?id=470094 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 470094] New: [Feature Request] Show a map when clicking on a contact's address
https://bugs.kde.org/show_bug.cgi?id=470094 Bug ID: 470094 Summary: [Feature Request] Show a map when clicking on a contact's address Classification: Applications Product: kalendar Version: 23.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: odin@ethicalexploiting.com CC: c...@carlschwan.eu Target Milestone: --- I've noticed that I can click on phone numbers and e-mail addresses in the contact list of Kalendar's Widget, but addresses cannot be clicked on. EXPECTED RESULT Allow clicking an address to open up (“Maps”) similar to KOrganizer. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.26-1 Manjaro x64 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 470093] [Feature Request] Show all/filter contacts for Kalendar System Tray Widget
https://bugs.kde.org/show_bug.cgi?id=470093 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 470093] New: [Feature Request] Show all/filter contacts for Kalendar System Tray Widget
https://bugs.kde.org/show_bug.cgi?id=470093 Bug ID: 470093 Summary: [Feature Request] Show all/filter contacts for Kalendar System Tray Widget Classification: Applications Product: kalendar Version: 23.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: odin@ethicalexploiting.com CC: c...@carlschwan.eu Target Milestone: --- The Kalendar 'widget' doesn't show contacts that have no e-mail addresses. I'd rather they be shown so that I can initiate a phone call with them (or view other information). In short, I'd like the option to show *all* contacts... A typical example might be so that I can click on a phone number and have KDEConnect initiate the call from my phone for me or view their GPS location on a Map. STEPS TO REPRODUCE 1. Left-click the System Tray widget for Kalendar. OBSERVED RESULT Notice that only contacts with e-mail addresses are shown. EXPECTED RESULT Show all contacts (or allow filtering?). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.26-1 Manjaro x64 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 470092] New: Unable to view mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=470092 Bug ID: 470092 Summary: Unable to view mail in Inbox Classification: Applications Product: kalendar Version: 23.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: odin@ethicalexploiting.com CC: c...@carlschwan.eu Target Milestone: --- My e-mail host uses the Inbox to contain all folders, annoyingly. It's also preventing me from using Kalendar to view mail content in the folder because Kalendar is considering it to be a folder only (clicking on it just results in expanding or collapsing the folder in the view). OBSERVED RESULT Clicking on a folder that has sub-folders but also contains mail results in being unable to view the list of mail. EXPECTED RESULT List mail in the folder. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.26-1 Manjaro x64 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 470092] Unable to view mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=470092 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468924] KDEConnect modifies (converts) files when sent from Desktop to Android
https://bugs.kde.org/show_bug.cgi?id=468924 --- Comment #4 from Odin Vex --- I see, so it does happen, but it is possibly Android's fault. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446895] Desktop SMS Unresponsive
https://bugs.kde.org/show_bug.cgi?id=446895 --- Comment #4 from Odin Vex --- I see, I was mostly going at keywords gleamed here and there. I've had the issue Garry has had, but so rarely. Withdrawing. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468924] KDEConnect modifies (converts) files when sent from Desktop to Android
https://bugs.kde.org/show_bug.cgi?id=468924 --- Comment #2 from Odin Vex --- Any clue what could be doing it? KDEConnect on KDE-based Manjaro + KDEConnect on Android. Any way to debug what is happening from the Android side? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446895] Desktop SMS Unresponsive
https://bugs.kde.org/show_bug.cgi?id=446895 --- Comment #2 from Odin Vex --- I can still send SMS via cli with *kdeconnect-cli --destination ###-###- -n 'DEVICENAME' --send-sms "MESSAGE"*. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446895] Desktop SMS Unresponsive
https://bugs.kde.org/show_bug.cgi?id=446895 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #1 from Odin Vex --- I have the same issue, loading/sending SMS with the main UI has not worked for a while now, though replies via the notification in KDE do work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro x64 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 KDEConnect: 22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468924] New: KDEConnect modifies (converts) files when sent from Desktop to Android
https://bugs.kde.org/show_bug.cgi?id=468924 Bug ID: 468924 Summary: KDEConnect modifies (converts) files when sent from Desktop to Android Classification: Applications Product: kdeconnect Version: 22.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: odin@ethicalexploiting.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Send an .m4a to a mobile device featuring Android. OBSERVED RESULT File arrives, but is .mp3. EXPECTED RESULT File should arrive, but should not be modified or touched in any way. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro x64 (Rolling) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463696] System Tray Integration
https://bugs.kde.org/show_bug.cgi?id=463696 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #3 from Odin Vex --- So many other software programs get it right. I think Tokodon can handle adding simple tray notifications. At the very least, something to simply move it away from taskbars and simply 'open'. Doesn't need to be complicated, but a bare minimum at least. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379860] Kontact inconify does not iconify, it minimizes
https://bugs.kde.org/show_bug.cgi?id=379860 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com Version|5.5.1 |5.22.2 --- Comment #3 from Odin Vex --- Iconifying Kontact doesn't work at all in 5.22.2. All attempts to start it iconified (even via Konsole) fail, it doesn't even start minimized, let alone at the tray. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 465949] Create or remove folders inside ~/Vault/* when opening or closing vaults, hide everything from Plasma Search/Baloo
https://bugs.kde.org/show_bug.cgi?id=465949 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 465949] New: Create or remove folders inside ~/Vault/* when opening or closing vaults, hide everything from Plasma Search/Baloo
https://bugs.kde.org/show_bug.cgi?id=465949 Bug ID: 465949 Summary: Create or remove folders inside ~/Vault/* when opening or closing vaults, hide everything from Plasma Search/Baloo Classification: Plasma Product: Plasma Vault Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: odin@ethicalexploiting.com Target Milestone: --- SUMMARY 1. I'd like to see Plasma Vault automatically create or remove the mounting folders inside ~/Vault/* when opening or closing a vault. This is mostly to 'clean up the residue' of history. 2. I'd like to see Plasma Search and Baloo prevent any evidence of history for any vault in particular, if possible. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 465815] KMail assumes KDEWallet as Secret Service provider, breaking other alternatives
https://bugs.kde.org/show_bug.cgi?id=465815 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 465815] New: KMail assumes KDEWallet as Secret Service provider, breaking other alternatives
https://bugs.kde.org/show_bug.cgi?id=465815 Bug ID: 465815 Summary: KMail assumes KDEWallet as Secret Service provider, breaking other alternatives Classification: Applications Product: kmail2 Version: 5.22.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: odin@ethicalexploiting.com Target Milestone: --- SUMMARY KMail is assuming that KDEWallet is the Secret Service that can exist and attempts to detect it by forcibly detecting *only* KDE Wallet, instead of simply asking on the dbus if a Secret Service provider exists (such as KeePassXC). SMTP can be fetched from KeePassXC, but *not* IMAP credentials. STEPS TO REPRODUCE 1. Disable KDEWallet. 2. Use any other Secret Service provider (such as KeePassXC). 3. Attempt to '' a Receiving entry for an IMAP account. OBSERVED RESULT Error Message: Could not access KWallet. If you want to store the password permanently then you have to activate it. If you do not want to use KWallet, check the box below, but note that you will be prompted for your password when needed. EXPECTED RESULT KMail should accept alternative Secret Service providers. SOFTWARE/OS VERSIONS Linux: Manjaro 22 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION SMTP is remembered correctly, but not anything relating to IMAP. POP3 may be affected, unchecked. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 465636] Crashes quickly after displaying UI
https://bugs.kde.org/show_bug.cgi?id=465636 --- Comment #2 from Odin Vex --- (In reply to Carl Schwan from comment #1) > This is a bug in the flatpak runtime that was fixed 2 weeks ago but the fix > was only released today. I guess it will take a few more days for the new > runtime to be published. Thank you for the swift reply, I'll check the next Flatpak update and follow-up if not fixed. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 465636] Crashes quickly after displaying UI
https://bugs.kde.org/show_bug.cgi?id=465636 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 465636] New: Crashes quickly after displaying UI
https://bugs.kde.org/show_bug.cgi?id=465636 Bug ID: 465636 Summary: Crashes quickly after displaying UI Classification: Applications Product: Tokodon Version: 23.01.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: odin@ethicalexploiting.com CC: c...@carlschwan.eu Target Milestone: --- STEPS TO REPRODUCE 1. Launch Tokodon. OBSERVED RESULT Crashes quickly after displaying UI. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Mint 21.1, Current 2023-02-12 FLATPAK INFO: Ref: app/org.kde.tokodon/x86_64/stable Runtime: org.kde.Platform/x86_64/5.15-21.08 Sdk: org.kde.Sdk/x86_64/5.15-21.08 Commit: 513bcd523cc77f4cf69b9a6d3bb34d27a4a135f3ae1947ae2a76206e71c0d147 Date: 2023-01-29 22:46:52 + ADDITIONAL INFORMATION Output from flatpak run org.kde.tokodon: ``` Qt: Session management error: None of the authentication protocols specified are supported Loading any accounts from settings. file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Switch.qml:60: ReferenceError: controlRoot is not defined ``` I tried downgrading through *every* commit all the way back to 4bcb111cf16bd0f3873ab50cdd3a6ce8749ff5959ce2609349590841a8ee1a40 (2022-11-30 14:31:15 +), no success. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459869] New: Favicons are not always accurate or detected for Institutions
https://bugs.kde.org/show_bug.cgi?id=459869 Bug ID: 459869 Summary: Favicons are not always accurate or detected for Institutions Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: odin@ethicalexploiting.com Target Milestone: --- SUMMARY *** Favicons are not always accurate or detected for Institutions, especially those that use custom paths. Perhaps allowing users to input a custom URI or even allow importing of favicons (ico/png/svg) might be helpful. *** STEPS TO REPRODUCE 1. Add an Institute, specify a website such as "https://sfcuonline.org/;. OBSERVED RESULT Generic Bank icon is used. EXPECTED RESULT Favicon (currently located at https://sfcuonline.org/application/themes/vibrant_theme/_img/favicon.ico or https://sfcuonline.org/application/themes/vibrant_theme/_img/favicon.png) should be used. SOFTWARE/OS VERSIONS Host: Linux Mint 21 x64 Software: kMyMoney 5.1.2 ADDITIONAL INFORMATION I haven't tested this on other platforms or versions. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413650] KDE Connect bug restarting after windows wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=413650 --- Comment #4 from Odin Vex --- I'd like to add, I'm using kdeconnect-kde-master-263-windows-msvc2017_64-cl.exe. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413650] KDE Connect bug restarting after windows wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=413650 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #3 from Odin Vex --- I have the same problem. At any time, KDE Connect can completely "just not work" unless I restart it. Even then, it can take quite a bit of time (a minute, maybe half an hour) for KDE Connect to begin working again. Eventually I will get "Failed to execute program org.kde.kdeconnect: The system cannot...(find the file specified)..." Meanwhile, my phone and laptop can see each other and respond to one another with no issues. Firewalls have been disabled for testing but make no difference. -- You are receiving this mail because: You are watching all bug changes.
