[yakuake] [Bug 493548] Graphical glitches when using yakuake themes with shadow effect and rounded corners (Wayland)
https://bugs.kde.org/show_bug.cgi?id=493548 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #1 from piedro --- I got the same glitch Also after waking my box up from standby yakuake somezimes adds a huge black background area over half of my screen when gliding in into non-fullscreen mode. After switching to full screen and back this corrects itself (but the problem with the shadow effect stays!)... This doesn't always happen, but often enough to be worth reporting. thx for reading, p. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 484307] New: Downloading and deleting wallpapers do not use the trashbin and cannot be renamed while downloading...
https://bugs.kde.org/show_bug.cgi?id=484307 Bug ID: 484307 Summary: Downloading and deleting wallpapers do not use the trashbin and cannot be renamed while downloading... Classification: Plasma Product: ksplash Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open desktop edit mode 2. In the dialog for choosing a wallpaper - delete one 3. Try to recover the wallpaper from the trashbin OBSERVED RESULT Wallpaper is not in the trashbin... EXPECTED RESULT Deleted wallpapers (e.g. by accident) should be moved to the desktop trashbin Operating System: openSUSE Tumbleweed 20240321 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Manufacturer: ASUS ADDITIONAL INFORMATION Also while downloading new wallpapers there is no way to rename the image file. But many wallpapers are just named "02.Jpg" for example and without the ability to rename them during the wallpaper download process they overwrite each other or the installation of the wallpaper has to be omitted... Also even wallpapers with individual file names often aren't very descriptive. And since the naming is up to the author the option to rename the wallpaper image file while downloading would be very helpful. thx, p. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 392501] Volume slider in Elisa does not work
https://bugs.kde.org/show_bug.cgi?id=392501 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #10 from piedro --- On OpenSuse Tumbleweed with all the latest updates and running KDE 6.0.2 I can confirm that in Elisa the volume slider has no effect at all! The mute button works though... Also (not part of this bug here - but still...!) pausing and un-pausing results in short sound stutters - very unpleasant. Neither the non-working volume slider nor the sound stutters on puase/unpause happen with VLC, Deadbeef or other players I tested... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410728] Shortcut deleted with kmenuedit remains in the search results of kickoff
https://bugs.kde.org/show_bug.cgi?id=410728 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #5 from piedro --- It's 2024. This is still the case... And it does not only happen apps that are still installed - I just had the problem of a sticking entry of an application I tested an deleted afterwards. Th is is on Opensuse Tumbleweed with the latest iteration of KDE Plasma: Operating System: openSUSE Tumbleweed 20240212 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-1-default (64-bit) Graphics Platform: X11 Also the general recommendation seems to be to delete *.desktop files referring to the application in ~/.local/share/applications ... This still doesn't work - the application launcher still finds the entries of the deleted app. The remedy is to search for and delete the referring *.desktop files in ~/.local/share/applications and /usr/share/applications But this recommendation is not a solution! - Users can't be expected to clean out application link files in hidden system folders. The solution should be to make the menu editor to delete these entries in the users home folder and hide those in the system folder from the application search in the kickoff menu. thx. p. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 476111] Contacts list names do not respect KDE system scaling and font sizes
https://bugs.kde.org/show_bug.cgi?id=476111 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #2 from piedro --- Created attachment 162909 --> https://bugs.kde.org/attachment.cgi?id=162909&action=edit Screenshot (first column) ... Sure. Here's a screenshot with a test contact. The fonts in the first column with the tiny second row do not seem to change in size no matter what the font or scaling preferences in the KDE settings are... -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 476111] New: Contacts list names do not respect KDE system scaling and font sizes
https://bugs.kde.org/show_bug.cgi?id=476111 Bug ID: 476111 Summary: Contacts list names do not respect KDE system scaling and font sizes Classification: Applications Product: kaddressbook Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE Look at the list of names... OBSERVED RESULT The fonts of the name list are tiny and do not scale with the desktop scaling as set in the KDE settings. EXPECTED RESULT The names in the contact list should get proper font sizes as set in the system settings for normal and small fonts and also use the systems scaling factor. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuse Tumbeweed / 5.27.8 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466182] Google account login window doesn't use system scaling
https://bugs.kde.org/show_bug.cgi?id=466182 --- Comment #2 from piedro --- (In reply to Nicolas Fella from comment #1) > Are you using X11 or Wayland? At the moment I turned back to using X11. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466182] Google account login window doesn't use system scaling
https://bugs.kde.org/show_bug.cgi?id=466182 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466182] New: Google account login window doesn't use system scaling
https://bugs.kde.org/show_bug.cgi?id=466182 Bug ID: 466182 Summary: Google account login window doesn't use system scaling Classification: Applications Product: systemsettings Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kaccounts Assignee: ad...@leinir.dk Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. set system scaling to 150% 2. add new gmail online account 3. try entering login information in popup window authectication dialog OBSERVED RESULT The content of the dialog window to login Google services is way too small - "CTRL +" to zoom the dialog page doesn't work - for me the content is unreadable I have to use a magnifying glass to ebter my credentials and can't read the text to enter for the "I am not a robot" confirmation EXPECTED RESULT Either the "authenticate login" dialog popup content scales to the same degree as systemsettings and font DPI or the dialog window (which is HTMLclearly!) can be zoomed by the usual shortcut "CTRL +" ... SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20230219 (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 465924] Creating a revocation certificate file fails silently
https://bugs.kde.org/show_bug.cgi?id=465924 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #2 from piedro --- No, it's not flatpak but a fresh install of KDE openSUSE Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 465924] New: Creating a revocation certificate file fails silently
https://bugs.kde.org/show_bug.cgi?id=465924 Bug ID: 465924 Summary: Creating a revocation certificate file fails silently Classification: Applications Product: kleopatra Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: piedro.kul...@gmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. rightclick an openpgp key 2. choose details from the context menu 3. pick a folder to save the *.rev file OBSERVED RESULT no result, no file is created at the chosen path EXPECTED RESULT There should be a *rev file in the chosen path SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20230215 (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION With Kgpg it's easy to create the revocation certificate - it's saved as *.revoke file. -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 457930] Seemingly high ram usage
https://bugs.kde.org/show_bug.cgi?id=457930 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #3 from piedro --- I have the same problem on a fresh install of openSUSE... The RAM usage here is excessive: calendar reminder takes up 950Mb !! Kmail in addition takes another 350mb - resulting in 1.3Gb just for thee two akonadi processes. Please have a look into that... there are more reports about that on Reddit. Thx, p. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 340175] Knotes rich text editor icons do not respect system settings
https://bugs.kde.org/show_bug.cgi?id=340175 piedro changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 340175] Knotes rich text editor icons do not respect system settings
https://bugs.kde.org/show_bug.cgi?id=340175 --- Comment #5 from piedro --- Sadly I just checked and the bug is still present: Knotes does not respect KDE scaling (set to 131.25 % in my case). The rich text editor tool symbols in any note stay tiny - so tiny that they are not readable for me... p. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 458587] KRDC access dates have been set back to 1970 - every bookmark shows last access "52 years ago"
https://bugs.kde.org/show_bug.cgi?id=458587 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com Summary|KRDC access dates have been |KRDC access dates have been |set back to 1970 so every |set back to 1970 - every |connection bookmark shows |bookmark shows last access |last access 52 years ago|"52 years ago" -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 458587] New: KRDC access dates have been set back to 1970 so every connection bookmark shows last access 52 years ago
https://bugs.kde.org/show_bug.cgi?id=458587 Bug ID: 458587 Summary: KRDC access dates have been set back to 1970 so every connection bookmark shows last access 52 years ago Product: krdc Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: piedro.kul...@gmail.com CC: aa...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open krdc 2. look at the column for "last access" 3. every row show "52 years ago" ! OBSERVED RESULT Obviously every access date has been reset to 1.1.1970 with one of the last updates EXPECTED RESULT The last access should be accurate as it has been before and show relative dates like "2 days ago", "20 minutes ago" and so forth... SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch fully updated (5.19.5) (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION This is a regression as it has been fine before... please note that this does not match bug https://bugs.kde.org/show_bug.cgi?id=419632 THis bug here is about every recent dates. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 458202] Search for messages in kmail does not work anymore... no results at all
https://bugs.kde.org/show_bug.cgi?id=458202 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #3 from piedro --- Also for clarification: Checking with Akonadi Console there was no "Akondi indexing agent" activated - I am not sure it is needed but I added it now. Sadly this had no effect - still can't search in kmail - filtering works but doesn't help for any searches spanning more than one folder obviously. Please can someone look into this? thx a lot, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 458202] New: Search for messages in kmail does not work anymore... no results at all
https://bugs.kde.org/show_bug.cgi?id=458202 Bug ID: 458202 Summary: Search for messages in kmail does not work anymore... no results at all Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. try to search for messages containing "regards" 2. search or open search folder 3. restart kmail OBSERVED RESULT No matter what I do - I cannot search in kmail anymore! EXPECTED RESULT Mails showing up in a search fitting certain criteria SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch fully updated (5.19.3) (available in About System) KDE Plasma Version: 5.25.4-1 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kmail: 5.21.0 (22.08.0) ADDITIONAL INFORMATION This really has to work - otherwise the whole setup for an email client for multiple mail accounts, filters and so forth is utterly useless if there's no search function to find stuff... seems to be a regression because it kind of worked before. Though also every time I open any search effort there is the complaint that folders have to be reindexed... even if I reindexed two seconds ago... -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 458194] New: Kaddressbook doesn't find any google contacts though the google groupware agent is running ok...
https://bugs.kde.org/show_bug.cgi?id=458194 Bug ID: 458194 Summary: Kaddressbook doesn't find any google contacts though the google groupware agent is running ok... Product: kaddressbook Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com CC: to...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. add addressbook > google groupware > enter credentials 2. close "add new" dialog 3. check with akonadi console that google groupware agent is running ok OBSERVED RESULT no adressbook has been added google groupware agent isn't showing contacts (I can't see it) EXPECTED RESULT Google contacts addressbook should be easily added - it's an important and standard use case for contact management SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux fully updated (kernel 5.19.3) (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Kaddressbook version: 5.21.0 (22.08.0) This worked before - this is a regression. Also this is really important because kmail, kraft and every other software relying on integration of contacts fails also! Nota bene: all google calendars work! they show up in Kalendar and korganizer -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares, "Details" tab in File Properties missing
https://bugs.kde.org/show_bug.cgi?id=452924 --- Comment #17 from piedro --- Just want to add that the context menu (right click) in network folders is different than the one that shows on loacl folders. For example if I cut a file or folder than, on a local fodler, I get the option to paste it into the open folder via context menu. If I try to paste the same file or folder into a network folder I do not get the context menu entry for pasting. I do not know if this behavior is connected - but I think it's worth mentioning here. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares, "Details" tab in File Properties missing
https://bugs.kde.org/show_bug.cgi?id=452924 --- Comment #11 from piedro --- Hmmm... Checking the file on the server with lsattr test.jpg gives me c- test.jpg So there are extended attributes on the file... - maybe it's up to the mount options... May I ask about the filesystem and mount options you are using to make this work? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares
https://bugs.kde.org/show_bug.cgi?id=452924 --- Comment #9 from piedro --- Exactly these - tags and comments... Here's what happens: - I take a simple test.jpg and add the tag "testfile" and the comment "this is just a test file". So now dolphin shows me - all the EXIF metadata of the jpg - the tag "testfile" - the comment "this is just a test file" Now I move the file to my media folder which is a network resource on a Synology Diskstation (I tried this with samba and nfs shares). Dolphin's side pane shows me - no EXIF data - no tags - no comment Now I move the test file back to it's orignal location. - Exif data is shown - no tag - no comment This does not happen with local mounts (obviously these are btrfs, xfs, and ext4 mounts, so these are no network systems obviously) So effectively I lose my comment and my tags by moving the file via a network share... :-( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278 --- Comment #4 from piedro --- Thanks... Yes- this other bug looks like the reason for this bug. If you don't mind - could you mark it as duplicate? Though I do not understand the resolve - does the fix suggested work or not? Do I as a user have to do something with inotify? You're TAG comment is interesting - I didn't know there is such a thing as hierarchical tags - is there any help or documentaion on that topic - I'd really be interested in what exactly I can do with tags (and what I shouldn't even try) :-) ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278 --- Comment #2 from piedro --- Baloo stops working after initial indexing - this also doesn't index new files added later. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #1 from piedro --- After changing a folder name or moving a folder "balooctl status" stays idle - shouldn'T it start working right away? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 453278] New: Baloo doesn't reindex files after they have been moved or renamed - manually reindexing is necessary...
https://bugs.kde.org/show_bug.cgi?id=453278
Bug ID: 453278
Summary: Baloo doesn't reindex files after they have been moved
or renamed - manually reindexing is necessary...
Product: frameworks-baloo
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: piedro.kul...@gmail.com
Target Milestone: ---
SUMMARY
on my system baloo only searches the documents and music folder. Tagging,
content and file name search works initially. But when I work with the files -
renaming them, moving some in subfolders or renaming the containing folder
they disappear from the index.
STEPS TO REPRODUCE
1. index a file in a subfolder in Documents ("recent_path", "recent_file_name")
2. rename the subfolder or the file or both ("current_path",
"current_file_name")
3. search for the content or the file name of the current file in the current
folder
OBSERVED RESULT
Absurd: the search can't find the file name nor the content of the file in the
current folder - though it is right there in the dolphin window if you do not
search for it (navigate > current folder > content: this one current file!)
EXPECTED RESULT
To find the only file in the current folder by it's name within the current
folder...
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux 5.17.5-arch1-1, fully updated
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
the current file's index can be shown with
"balooshow -x /current_path/current_file_name"
but the file index information output still contains the old file path
"/recent_path/recent_file_name"!
So my guess is that after renaming a file the index isn't updated - baloo
sleeps on the job. It doesn't matter to wait a while or reboot - only
reindexing does the job to update the files index information to include the
correct path and file name.
On a curious note: Is it normal that some tags are shown as "TAG-tagname1" and
others as "TAtagname2" or is this a hint that something with the indexing
isn't right anyway?
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares
https://bugs.kde.org/show_bug.cgi?id=452924 --- Comment #7 from piedro --- So I do not think it's only about reading the files metadata - moving the file to the network share and back loses the metadata! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares
https://bugs.kde.org/show_bug.cgi?id=452924 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #6 from piedro --- Same here - I think it is due to extended attributes not correctly assigned. I thought this is happening because my network file server (Synology NAS) might not support xattr data. But I experimented quite a lot and it turns out the server does. I checked the xattr state of files I copied to the server and it turns out they are there. Copying the files in dolphin to the network share and then moving the file back results in a loss of all file tags which are, as I understand saved as extended file attributes. Here's parts of my post on reddit: - Hi! As I understand the KDE file tags that can be applied by dolphin get written into the extended attributes of the tagged files. So that's fine and works most of the times... But it seems that dolphin loses the ability to read or assign tags in any mounted network folder - though the network server uses btrfs as well and the shares (I tried nfs and cifs/samba mounting) should support unix attributes. So do I need additional mount options to make KDE tags "stick" in network shares? I do not seem to have the same problem with local mounts Anyone? Thanks! Cheers, p. p.s.: Btw... - the context menu in dolphin still shows the "Add tag" entry - but adding tags in the mounted folders doesn't do anything... p. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 324596] Date Picking to create an event list is restricted to a one month period
https://bugs.kde.org/show_bug.cgi?id=324596 --- Comment #13 from piedro --- True. And if the search functionality would be able to save the search settings or even make it possible to create virtual search folders (like in kmail) this would be a fantastic and versatile way to organize dates, events and journal entries on a granular level. As it is now you have to configure the search every time you want to look at your search list... - for example, if you want to check all the telephone conference calls with a customer during the whole year, you'd have to manually set up all the dates, filters and conditions of the search every time you want to check these... I like the search function but it is very situational and offers no possibility to keep the generated list - you can't - save it - print it - export it So it is not a useful tool for day to day work but more a tool to search very specifically for a certain entry... But thanks for bringing it up! Cheers, pk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 371640] File type assocations override Gnome preferences
https://bugs.kde.org/show_bug.cgi?id=371640 piedro changed: What|Removed |Added Status|NEEDSINFO |REPORTED CC||piedro.kul...@gmail.com Resolution|WAITINGFORINFO |--- --- Comment #2 from piedro --- Hi Justin! "It seems this is now fixed as I just made an adjustment to my mp4 file association and I can see that ~/.config/mimeapps.list has been modified." That is exactly the bug I reported. It should NOT write to ~/.config/mimeapps.list ! It should write to ~/.config/kde-mimeapps.list ! As recommended by the XDG standards. Thx for reading... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424867] New: Dolphin search doesn't restrict search results "from here"...
https://bugs.kde.org/show_bug.cgi?id=424867 Bug ID: 424867 Summary: Dolphin search doesn't restrict search results "from here"... Product: dolphin Version: 20.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: piedro.kul...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY search for FILENAME and FROM HERE in a subfolder of home directory STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT Only files from the selected directory should show up as results! SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, Dolphin 20.04.3 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367682] Akonadi/Baloo/Whatever doesn't show PIM data on desktop searches
https://bugs.kde.org/show_bug.cgi?id=367682 --- Comment #3 from piedro --- If it provokes someone after three years of inactivity - then it's helpful! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405353] Akonadi doesn't correctly assign "new" and "cur" mail within local-mail - deleted mail shows up again and again
https://bugs.kde.org/show_bug.cgi?id=405353 piedro changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||piedro.kul...@gmail.com --- Comment #3 from piedro --- *** This bug has been marked as a duplicate of bug 376032 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376032] Emails not being moved from "new" to "cur"
https://bugs.kde.org/show_bug.cgi?id=376032 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #6 from piedro --- *** Bug 405353 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367682] Akonadi/Baloo/Whatever doesn't show PIM data on desktop searches
https://bugs.kde.org/show_bug.cgi?id=367682 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #1 from piedro --- I do not think akonadi is still developed - it seems that none of the bugs gets any comments nor fixes... Sad, but if opensource projects create complex solutions like akonadi there has to be enough ressources for developers to maintain it. Otherwise simple solutions are to be preferred! Akonadi is a beast and I doubt that any new developer coming to KDE would have any interest in bug hunting akonadi. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405729] New: Kontact 5.10.3 crashes trying to "configure Kontact"
https://bugs.kde.org/show_bug.cgi?id=405729 Bug ID: 405729 Summary: Kontact 5.10.3 crashes trying to "configure Kontact" Product: kontact Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY Kontact crashes with segmentation fault when entering "configure kontact". STEPS TO REPRODUCE 1. open kontact, any section... 2. open menu "settings" 3. choose "configure kontact" OBSERVED RESULT Kontact crashes immediateley with a segfault EXPECTED RESULT Kontact shouldn't crash, obviously SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux fully updates (available in About System) Kontact 5.10.3 KDE Frameworks 5.56.0 Qt 5.12.2 (built against 5.12.1) ADDITIONAL INFORMATION This is serious. It makes Kontact unconfigurable. Since a "Personal" information maneger has to be configured to individual needs this is a complete showstopper rendering kontact basically unusable for any real life work scenario. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405353] New: Akonadi doesn't correctly assign "new" and "cur" mail within local-mail - deleted mail shows up again and again
https://bugs.kde.org/show_bug.cgi?id=405353 Bug ID: 405353 Summary: Akonadi doesn't correctly assign "new" and "cur" mail within local-mail - deleted mail shows up again and again Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY In my kmail local mail folders, there is no mail shown as "new mail" in kmail. But within the .local/share/local-mail folder mails do not get moved correctly from "new" to "cur" subfolders. In consequence mails I delete reappear until I move them around manually with a file manager - which is not a solution and also doesn't work as reliable workaround since the maildir structure management of akonadi seems to be inconsistent. Some times hidden subfolder structures are created correctly, some times they seem not to be distributed correctly after additional subfolders to local mail in kmail are added. STEPS TO REPRODUCE 1. create a "spam" folder for example within Local folders 2. let hte spam filters of kmail move spam to "Local Folders/spam" 3. try to delete all mails in the "spam" subfolder After switching to another folder and checking back into "spam" many mails reappeared. Reindexing doesn't help. Marking everything as read before deleting doesn't work. Checking with a file manager some Mails are in "cur" some in" new" though there is no more new mail in kmail! Now though this is not a valid option I also tried just waiting for a while... hasn't worked neither. Deleting the mails with a file manager within the .local/share/local-mail is the only way I could get rid of the deleted mail for good. In this case kmail immediatly shows no more mails within "spam". Obviously akonadi doesn't - correctly distribute mail beetween "new" and "cur" - inconsistently handles maildir structures - recreates mails after they have been deleted This behaviour completely spoils the user experience with kmail. At the moment I have to manually maintain the maildir structure within .local/share after already having managed the mail in kmail. Doing it twice in different ways... p.s.: As I mentioned before it is not a good choice to put the local folders of kmail into ".local/share/local-mail". By using this location the mail in subfolders is not contained within the "local-mail" folder but in the hidden ".local/share/.local-mail.directory". Meaning that trying to backup local mail archives is not trivial anymore. also the documentation isn't correct on how to save your mail folder. Why not for example simply use the folder ".local/share/local-mail/local-folder/" as sane default. This way the user can be sure that ALL local mail within the maildir structure is contained in ".local/share/local-mail/". If for some obscure reason it is decided that this won't happen (though I do not see any downside) then please at least make sure the user is asked about the location of the "Local folders" in kmail BEFORE akonadi created the ressource at this location. thx, p. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux fully upgraded Kmail: 5.10.3 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 --- Comment #18 from piedro --- Do you have to recreate the addressbooks to fix the data? Or does the patch make akonadi fix the email fields in the contact database? -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #16 from piedro --- I am using Arch with the latest 18.12.3 version. The problem is still there. Or I am missing something... -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 405200] Creating a subfolder in any addressbook fails: can't create collection...
https://bugs.kde.org/show_bug.cgi?id=405200 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #1 from piedro --- This seems to be a duplicate - I commmented there also and changed to CONFIRMED. Bug 387804 - Create folder in KAddressBook fails -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404947] Many "unknown" identities are created over and over...
https://bugs.kde.org/show_bug.cgi?id=404947 --- Comment #4 from piedro --- Yes the permissions are correct! - I deleted close to one thousand "unknown" identity references in this file now (btw. it grew huge, 850k)... and left the ones I created... until now they have not reappeared... Akonadi shouldn't do things like that. p. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 405200] New: Creating a subfolder in any addressbook fails: can't create collection...
https://bugs.kde.org/show_bug.cgi?id=405200 Bug ID: 405200 Summary: Creating a subfolder in any addressbook fails: can't create collection... Product: kaddressbook Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com CC: to...@kde.org Target Milestone: --- SUMMARY Create an addressbook - doen't matter whether it's Google contacts, the default personal contacts of kaddressbook or a VCard-folder ressource - trying to create a subfolder within fails with: "Could not create address book folder. Could not create collection XYZ, resourceID: 37" STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT Creating subfolders (as option in the context menu indicates) is a core functionality - it should work. p. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ARCH fully upgraded (available in About System) KDE Plasma Version: 5.15 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 387804] Create folder in KAddressBook fails
https://bugs.kde.org/show_bug.cgi?id=387804 --- Comment #2 from piedro --- eh yes, since I cannot edit my comments in this bug tracker... Here you go: CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 387804] Create folder in KAddressBook fails
https://bugs.kde.org/show_bug.cgi?id=387804 piedro changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 387804] Create folder in KAddressBook fails
https://bugs.kde.org/show_bug.cgi?id=387804 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #1 from piedro --- Hello! I have the same problem "creating collcetion fails" when creating any subfolder in any address bbok. The Workaround is to create a lot of *.vcf-card folder addressbooks (also in theses I cannot create a subfolder!) and in consequence clutter the adressbook. If this is the intended way of workflow here then please remove the option to add subfolders - it's not working. Does anyone use this functionality successfully or is it just that nobody cares about it anyway? I am confused - creating subfolders ina an addressbook seems like a core functionality of any address and contacts organizer... WHat's up? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404947] Many "unknown" identities are created over and over...
https://bugs.kde.org/show_bug.cgi?id=404947 piedro changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #1 from piedro --- How can I edit typos? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404947] New: Many "unknown" identities are created over and over...
https://bugs.kde.org/show_bug.cgi?id=404947 Bug ID: 404947 Summary: Many "unknown" identities are created over and over... Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY In the Kmail settings onder identites there are hundreds of "unknown" identities. After deletion the show up again... STEPS TO REPRODUCE I do not know how to produce this result but this has been a clean user account with only 2 imap identities setup when this started... OBSERVED RESULT deletion seems to have an effect for the moment but later these empty ghost identites show up again... EXPECTED RESULT "unknown" identites should not be auto-created and at the least deletion should work as expected! SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.55.0 KDE Frameworks Version: 18.12 Qt Version: Qt 5.12.1 ADDITIONAL INFORMATION ARCH fully updated -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404850] New: Archiving of mails in kmail folders doesn't work - collection does not exist
https://bugs.kde.org/show_bug.cgi?id=404850 Bug ID: 404850 Summary: Archiving of mails in kmail folders doesn't work - collection does not exist Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY The attempt to archive even a single mail does result in a "collection does not exist" error. STEPS TO REPRODUCE 1. create a fresh user account with default settings 2. add an standard email account (also apllies to gmail accounts) 3. right click on any message in any folder and chose archive (make sure you've set an accessible archive folder before!) OBSERVED RESULT you get a notification saying "Collection can't be fetched. collection doesn't exist." EXPECTED RESULT Obviously: move mail to designated archive folder SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Arch linux, fully updated (available in About System) KDE Plasma Version: Plasma 5.15.1 KDE Frameworks Version: KDE 18.12.1 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 352502] .local/share/local-mail has to be the top level of local folders!
https://bugs.kde.org/show_bug.cgi?id=352502 --- Comment #4 from piedro --- Now this is still present and unsolved in KDE 18.12.1! Creating the hidden directory list OUTSIDE the designated local mail folder is a serious bug. In connection with the bug of akonadi creating folders BEFORE the user confirms or intentionally chooses the Mail folder location recreates empty directory list folders over and over again and messes up the local folder in kmail. Because of this subfolders change their name, are recreated, disappear and get moved within the system. It's the source of a whole bunch of problems people complain about. Well as nobody seems to read these bug reports this will stay like this I guess. And that's exactly one reason why kmail is unusable for many people cause you can't even use an archive subfodler in local folders... Keep up the good work! p. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 340175] Knotes rich text editor icons do not respect system settings
https://bugs.kde.org/show_bug.cgi?id=340175 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #3 from piedro --- Sorry, I am not using KDE anymore... pk -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 359494] Kfind crashes after never finishing searching the home folder
https://bugs.kde.org/show_bug.cgi?id=359494 --- Comment #4 from piedro --- Sry, I do not use KDE anymore. Thx for the notice... p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 323066] local folders not created or used.
https://bugs.kde.org/show_bug.cgi?id=323066 --- Comment #14 from piedro --- Sry I missed Martins comments completely, at his time I moved away from KDE as there way too much fixing involved which interfered with my work. I cannot comment on that any further, I remember that akonadi created mail folders in .local/share even if I defined the folders elsewhere and that after crashs or forced shutdowns of akonadi, it would start using the .local/share folders instead of the custom preset... Sry thats all I have. I am not using KDE anymore. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 295259] Folder->Remove Duplicates doesn't work
https://bugs.kde.org/show_bug.cgi?id=295259 --- Comment #12 from piedro --- Sry, I haven't used for 3 years now. So please close the bug if noone else has a problem. thx for the attention, cheers, p. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366564] Please change autostart defaults to not interfere with non-KDE desktops
https://bugs.kde.org/show_bug.cgi?id=366564 --- Comment #8 from piedro --- Thx for your quick answer. The solution you mentioned is troublesome - as with every update (monthly with KDE on ARCH for example) this file will be replaced, so it's still better to have the default content of the file changed. > OnlyShowIn=; as default does what you suggest (I think). There could be an option to activate it permanently in autostart as a "first run" question. This could systemwide or on a desktop environment basis by auto-editing the "kdeconnectd.desktop" either in /etc or ~./config/autostart -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366564] Please change autostart defaults to not interfere with non-KDE desktops
https://bugs.kde.org/show_bug.cgi?id=366564 piedro changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX |--- Ever confirmed|0 |1 --- Comment #6 from piedro --- "This is intended behaviour." Well, that doesn't mean it's well designed... "You can use KDE Connect on all desktops, so it autostarts on all desktops." That's a clear non-sequitur: Just because it works everywhere it doesn't follow by any logic that it should run everywhere no matter what! At least give us a choice! "If you don't want to use it, deinstall it." I like to use Kdeconnect. At least here and then... So unistalling is not a reasonable option. But I do not want to use it everytime my computer starts. And certainly not everytime I use an alternative desktop environment. So what about my suggestion to change the default behaviour of "running in the background no maater what" to "running in the background if and when the user intends to use it"... Kdeconnect gives access to my computer from an outside source. Even if devs consider it secure for the moment there is a good argument to be made to completely shut it down if it is not needed. I have been under the impression KDE tries to not follow the Gnome appraoch of shoving features down their user's throats but instead allow for individual configuration. This approach acknowledges the fact that the intention of devs, as well meant as it might be, does not cover the intended workflows and use cases of the individual user. So according to KDE guidelines and promises of individuality - I'd still call this a bug. A simple option to disable KDEconnect by default (see my suggestion) and activate it when the user wants to use seems a noncontroversial solution. Anyone who wants to run it always and everywhere should be able to either tick an option to autostart with any chosen desktop environment or even systemwide. I do not care if it's optin or optout - just the option suffices. If you don't want to use it, deinstall it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #16 from piedro --- Well, that's fair enough. Cheers, p. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #14 from piedro --- @Rex Dieter: That is true and I launched the same discussion with the Gnome community... The choice of DEs is one of the biggest visible and appealing advantages for new linux users (this is my experience but also see the number of posts about choice of distribution/DEs within the communities...). For the spread of linux desktops it is very important imho that it is possible to install and test different desktop environments alongside without any hidden unwanted interactions or disturbances. I advocate this for more than 5 years now: do not let any DE touch the user preferences (default applications, mime types, background services etc.) of any other DE but the experience atm is still discouraging to new users: New user interested in linux (mostly frustrated with windows) wants to check out linux. Installs a distribution and after a quick look installs different DEs alongside planing to decide which one to run after testing the different environments for his or her use case. The initial experience isn't great and looking for answers gets you comments like above "why don't you copy the config files and adjust them to your liking... or just crash a process". Still to this day clicking on a desktop symbol in GNOME suddenly starts dolphin for some reason, a few files within KDE open with gnome apps, Tracker is slowing down KDE but the new user can't find any information on it in KDE docs (obviously!), saving a file in firefox on KDE might open the file picker dialog of nautilus... well, you get the point... In the end the experience with the shiny and brand new linux system isn't promising at all unless you start solving many little problems by deep diving into configuration files, tricks and workarounds... Most new users I had to work with felt discouraged and thought the barrier of entry is too high - it doesn't help to tell them that many problems only arose because of interacting multiple DEs - it's this first impression that counts... Clean concepts and strict separation of DE experiences are important and have more implications than people might think on first glance. BTW I filed the bug with a few other KDE projects, asking to change the entries in the *.desktop files" to prevent auto starting with other DEs - it seems there has been no problems to change it and it is fixed now! thx for reading, p. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #12 from piedro --- I get it: You guys created a service and you like to see it been used. That is understandable. And since it is technically limited and resources are scarce you prefer to argue for "no changes" instead of looking for a cleaner solution... Also there already is a user-friendly, comprehensible, easy to apply solution in place that can be used by anyone: > Users can override system-wide *.desktop files by copying them into the user- > specific ~/.config/autostart/ folder. > If that isn't working, you can also crash baloo, there are many ways to do > it, > as you can see from the bug list. Also there are clear indications and documentations in place to help unsuspepecting GNOME or LXDE users to easily apply these solutions if their desktop might lag with non-GNOME/LXDE background services... I say "Well done, good work KDE team!" for a perceived problem swiftly and thoroughly solved! I am glad for the discussion and suggest to close this bug. Thx, P. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #9 from piedro --- BTW: please add a possibility to edit one's own comments in this bug forum... p. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #8 from piedro --- Still I don't understand: Why not start a service when it is needed? So if someone using gnome and digikam - why not start baloo the moment digikam is started... I still see no use nor necessity to auto-run it on login... - also there are way, way more use cases in which baloo is running in the background and nobody ever uses digikam (or something else needing the backround services) than there are use cases that benefit from a preloaded baloo... So I do not see what exactly prevents you from taking my advice here and only start KDE background services with a KDE session. If someone needs them using LXDE or Gnome just start them if they are needed... Micrsoft does the same with MS Office: they load Office services in the background just in case somebody wants to use it... it has been pointed out many times as a really bad idea causing problems and wasting ressources. Even MS added an option and made the behaviour opt-in instead of opt-out. Please do the same, thx, p. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #6 from piedro --- "Nobody rejected this ticket." Glad to hear! so thx for that. To your comment about tracker running in KDE: > If I had installed them, and they need to be running to track changes in > indexed files made by applications, yes. I really do not get your logic at all and I am not sure whether you are trolling me or really are convinced by that (if that is even possible). In the hope there is just a msiunderstanding, I try once again: Let's assume family Smith owns a computer and sets it up in the living room. The mother (administrator) installs linux to avoid corporate datamining on her kids. She wants to tailor the desktop to individual needs and teach her kids some computer skills. the setup: - the son uses a simplified GNOME desktop mainly to learn and play simple games - the daughter uses a GNOME with lots of online syncs (Google account) - the mother is just happy with her old school XFCE setup - the father loves the beauty of the plasma desktop (fiddling around a bit) You are saying it is useful, wanted and reasonable behaviour that each and every person has the indexing service of all the other desktop environments running though they will never start the alien DE? So the daughter has the gnome tracker services running, also zeitgeist and while synchronizing her emails and google drive there is also baloo running in the background (which is only useful for her father - but then again, not on her files!)... I feel ridiculous in spelling this out. Even on a pure single user system running background services across DEs only makes sense for users switching the environment on a regular basis. p. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #4 from piedro --- Why isn't it included in the basic GNOME and XFCE installation? The simple fact that the KDE desktop is installed by the administrator as one of many alternative desktop environments should not constitute that every user has to run a service in the background that he or she will never use for anything. And as I stated there is a very easy fix: If someone uses KDE please run it in the background - if someone starts a KDE application that depends on it please run it but if someone doesn't do it simply don't. You know that historically there have been multiple issues with baloo services. Please realize that it is really disrespectful if user A on a multi user system has to troubleshoot problems (or bother the admin) with a bug or a running process that has nothing to do with his or her choice of DE. Also by your logic tracker-miner, zeitgeist or any other indexing service should also run as background process within or underneath KDE. I don't think anyone what think that is a reasonable idea... I really do not understand why you try to defend the status quo: if somebody really is switching beetween DEs on a regular basis it's easy for a power user to add a copy of the *.desktop file to the /.config/autostart folder and add: > X-GNOME-Autostart-enabled=true or whatever is needed. For a user only choosing one DE to work with it's very hard to find the problem if one arises (which happened a lot as you surely remember) if he or she has to search for a solution outside the chosen DE. I am glad that finally someone is reacting to my request but simply to reject it because it might be useful to some users is not a very community friendly approach. At least you should admit that the approach to deactivate a service that has been asked to be deactivated even by many KDE users is a very reasonable and constructive request. BTW: if you don't think there is a problem, try to setup a fresh system install Gnome, XFCE and KDE and let tracker and baloo run in the background at the same time... and if you run into performance issues try to find a solution from either one of the dev teams - good luck! Cheers, p. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 354183] Sonnet uses the wrong path for configuration files...
https://bugs.kde.org/show_bug.cgi?id=354183 --- Comment #4 from piedro --- By this logic it wouldn't it be correct to have the location: ~/.config/Sonnet/sonnet.conf ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 354183] Sonnet uses the wrong path for configuration files...
https://bugs.kde.org/show_bug.cgi?id=354183 --- Comment #2 from piedro --- Is this too challenging a task to just simply fix one entry in the configuration file for developers to care? Sonnet is the only application to use this path. But I guess it's allright, it's only two years old for a 20 second change... Keep up the good work! Cheers, p. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 329149] Skanlite has no settings dialog for the papersize and get's it wrong!
https://bugs.kde.org/show_bug.cgi?id=329149 --- Comment #8 from piedro --- I am still asking the same question after two years of noone answering (great bug reporting system btw!): Where in which file would I have to to correct the papersize value? It isn't hardcoded, is it? Thanks for helping, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 344296] The "remove duplicates" should have some options to define duplicates
https://bugs.kde.org/show_bug.cgi?id=344296 --- Comment #2 from piedro --- Thanks a lot for all your kind comments over the last two year. I am happy that there is so much effort going into improving existing features instead of creating half-assed new ones that will lack polishing in the future... Cheers, great bug reporting system, p. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 324596] Date Picking to create an event list is restricted to a one month period
https://bugs.kde.org/show_bug.cgi?id=324596 --- Comment #8 from piedro --- BTW: That's why I will not bother with bug reporting again. Bug reporting seems not to be working at all at a social level. Since we can't change the social skills of developers, well... P. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #2 from piedro --- Well, bug reporting works great! SO: I have a simple solution. I want to commit my solution to the developer. It's changing two lines in the default xdg desktop start configuration file: Change > X-GNOME-Autostart-enabled=true > OnlyShowIn=KDE;GNOME;Unity;XFCE to > X-GNOME-Autostart-enabled=false > OnlyShowIn=KDE Now the solution is nonintrusive, noncontroversial and very, very simple to accomplish taking any developer on this less than 30 seconds. Why is there no comment nor change on the described behaviour here? Or if it is changed already, please would someone mark this as solved? What uis going on - does the KDE development community want user participation or not? I don't get it... p. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372355] New: Searching for filename is the same as searching for content
https://bugs.kde.org/show_bug.cgi?id=372355 Bug ID: 372355 Summary: Searching for filename is the same as searching for content Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: piedro.kul...@googlemail.com Target Milestone: --- It doesn't matter wehther searching for content or filenames - results are the same... please fix searching mechanisms in KDE... thx for reading, p. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372354] New: Searching for filen ames doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=372354 Bug ID: 372354 Summary: Searching for filen ames doesn't work as expected Product: dolphin Version: 16.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: piedro.kul...@googlemail.com Target Milestone: --- dolphin 16.8.3 If searching for filename "*.pdf" the results also show "hello-pdf.doc" or the folder "interestingPDFs" Please fix, thx for reading -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 371640] New: File type assocations override Gnome preferences
https://bugs.kde.org/show_bug.cgi?id=371640 Bug ID: 371640 Summary: File type assocations override Gnome preferences Product: systemsettings Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_filetypes Assignee: fa...@kde.org Reporter: piedro.kul...@googlemail.com As I understand there is a file for desktop specific mime type preferences: The file association dialog doesn't write to "~/.config/kde-mimeapps.list". This leads to overlap with the Gnome desktop preferences. The mechanism for using a desktop specific file type association file is already there implemented in the XDG standard - it should clearly be used. Otherwise users have to reset their association preferences every time they start another DE. Or build their mime type lists manually which seems a bit challenging... Please just change the location where the file type associations are stored so they only apply to KDE and do not interfere with the preferences of Gnome and XFCE and what ever else there is by using the intended methods... thx for reading, piedro Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354179] File associations cannot be changed if already defined in $XDG_CONFIG_HOME/mimeapps.list
https://bugs.kde.org/show_bug.cgi?id=354179 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #11 from piedro --- The workaround doesn't help - I still can't change the *.aac association. If I do it just jumps back to audacious in my case. Also there is no way to reset all the mime types or at least one by one to default settings. The button "load defaults in the systemsettings is just greyed out. Frustrating because this seems a major problem for anyone actually working on KDE. thx for reading, please fix this or give some workaround instructions, piedro -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354688] Can't remove file File Association in System Settings
https://bugs.kde.org/show_bug.cgi?id=354688 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #4 from piedro --- I do still have this problem in the latest ARch /KDE with all updates. Drives me nuts... thx, p. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 237469] File associations set by user should override systemwide associations
https://bugs.kde.org/show_bug.cgi?id=237469 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #3 from piedro --- this is still the case in plasma 5.8 on fully updated Arch. And it is really disturbing: There should be a simple way to set up user AND desktop specific mime types. Also I wonder why nobody else is concerned - is this a setup specific bug? It affected me with every setup I tried thx for reading, p. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 365855] Krunner's "Recent documents" results still there after "forgetting" recent docs in appdashboard
https://bugs.kde.org/show_bug.cgi?id=365855 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #5 from piedro --- I think there might be even a bit more of a problem. Also krunner shows documents from folders I excluded beforehand. I do backups for customers, projects and other machines. I exclude these folders from searching and indexing obviously. Krunner still finds stuff that doesn't belong to me. So it seems that the settings for indexing and excluding folders from recent documents doesn't do the job. Also excluding some folders or patterns at a later time should delete them out of the database. Please ignore this comment if I misunderstood your approach and my concerns are already included in the proposed solution. A users history of recent activities and documents as useful as is should be the first focus of system security in my opinion... thx for reading, p. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366564] Please change autostart defaults to not interfere with non-KDE desktops
https://bugs.kde.org/show_bug.cgi?id=366564 --- Comment #4 from piedro --- Thx for your answer. Appreciated... p. -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 295446] rekonq doesn't scale flash on zooming websites with embedded video
https://bugs.kde.org/show_bug.cgi?id=295446 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #16 from piedro --- I think rekonq is a dead project. So maybe another browser has to be the solution, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 352472] "Search mails" ignores all settings
https://bugs.kde.org/show_bug.cgi?id=352472 --- Comment #6 from piedro --- I am glad to hear that KDE decided to focus on professional use cases... maybe we start getting something moving here then. Though it feels like the announcements on the KDE pages are completely disconnected from development and bug hunting... p. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 324596] Date Picking to create an event list is restricted to a one month period
https://bugs.kde.org/show_bug.cgi?id=324596 --- Comment #7 from piedro --- That is said to hear... p. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 371587] New: Multimedia Settings do not work as expected, many problems, also inconsistent settings and UI
https://bugs.kde.org/show_bug.cgi?id=371587 Bug ID: 371587 Summary: Multimedia Settings do not work as expected, many problems, also inconsistent settings and UI Product: Phonon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: settings Assignee: sit...@kde.org Reporter: piedro.kul...@googlemail.com CC: myr...@kde.org 1) - If I try to set the default device for Audio in the systemsettings the subcatogories should adopt these values. Otherwise why have the top hierarchies "audio" "recording" etc. at all? 2) - If I change the profile of a device greyed out items items start appearing can't be handled by the backend. All the solutions to remove them involve clearing all settings which is very unsettling. 3) - If I install the pulseaudio equalizer (lsdap or the qpaep) every time I change the settings in there the output of my applications reverts to USB headphones though this is clearly not set as preferred device. 4) - the panel widget offers to set the sound volume for the different application but doesn't allow to switch the output device (by design as I've read) - regarding the fragile state of sound settings and preferences I think this a poor decision as a quick way to switch back to headphones or desktop speakers or equalized output. 5) - In the system settings the top categories of the device priorities have a little arrow indicating I should be able to collapse the categorie - clicking on the arrow has no effect at all... 6) - I get some notification informing me that the sound system reverted to another device with higher priority - checking the device priorities shows that the device it reverts too is set to a lower priority - so I feel my settings are ignored. Maybe others have more issues with the settings. I know it is good practice to tackle one bug at a time. In this case though I feel there is a conceptional issue with the way the settings work and are presented. I also understand that pulseaudio is a bloated and complicated beast to tame but from a users perspective there really should be simple ways to - Volumes: change individual volumes of devices and applications (very nicely done with the new widget) - Output Speaker: change the output device of an application on the fly to switch to headphones feor example when listening for a podcast while playing music on the desktop speakers or quickly push the output of a skype call to the speakers so others in the room can listen in - Bass/Treble Bias: a simple way to adjust sound quality like adjusting bass/treble volume and balance between left and right speakers on a per device basis (so connecting the same set of headphones for second time still remembers enhanced bass setting). This is very important for people using a laptop to connect to different speaker systems e.g. at friends or, more importantly, at presentation rooms - if you do not have a way to reduce or enhance bass/treble settings you easily ruin your presentation - and as KDE announce to focus on professional use this should be a priority! thx for reading, piedro Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 322227] Akonadi Agents hang or freeze after more than 24 hour uptime
https://bugs.kde.org/show_bug.cgi?id=37 --- Comment #4 from piedro --- I switched to gnome for productive work, sry, I can not provide anymore specific information on later versions... thx anyway, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 321054] kmail2 doesn't send emails after long uptime ...
https://bugs.kde.org/show_bug.cgi?id=321054 --- Comment #3 from piedro --- I switched to gnome for productive work, sry, I can not provide anymore specific information on later versions... thx anyway, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 333750] search finds mails but doesn't show them in the search dialog
https://bugs.kde.org/show_bug.cgi?id=333750 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #2 from piedro --- I have run some tests on kmail2 (latest version on Arch) a few weeks ago. While search provides relevant results now (as it seems at a quick glance) - the virtual folders are still lacking: You can apply additional criteria to a virtual folder but the changes have no effect on the content of the virtual search folder. No matter how one edits the search criteria the results always reflect the configuration of th initial search which created the search folder. thx, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 323416] "Forward" or "Reply" doesn't cite the whole content of the original message
https://bugs.kde.org/show_bug.cgi?id=323416 --- Comment #7 from piedro --- I switched to gnome for productive work, sry, I can not provide anymore specific information on later versions... thx anyway, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 302235] Mail sending delayed or does not work / Freezes
https://bugs.kde.org/show_bug.cgi?id=302235 --- Comment #4 from piedro --- I switched to gnome for productive work, sry, I can not provide anymore specific information on later versions... thx anyway, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 293013] dataloss: missing message bodies ON THE IMAP SERVER
https://bugs.kde.org/show_bug.cgi?id=293013 --- Comment #12 from piedro --- I switched to gnome for productive work, sry, I can not provide anymore specific information on later versions... thx anyway, p. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 --- Comment #7 from piedro --- Fixed for me as well, thx a lot! Some other background services are still autostarting but kalarm isn't anymore. Cheers and ty, p. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368084] krunner crashes when I use a name to search for documents
https://bugs.kde.org/show_bug.cgi?id=368084 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m Severity|normal |crash --- Comment #1 from piedro --- How can I edit the original report? Edit: This is on arch linux with KF 16.08 and plasma 5.7.4 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368084] New: krunner crashes when I use a name to search for documents
https://bugs.kde.org/show_bug.cgi?id=368084 Bug ID: 368084 Summary: krunner crashes when I use a name to search for documents Product: krunner Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: filesearch Assignee: pinak.ah...@gmail.com Reporter: piedro.kul...@googlemail.com When I open krunner (Alt+F2) and type a name krunner searches for the name shows some dokuments with the name in the title also some images and after about 2 seconds just crashes... Reproducible: Always Steps to Reproduce: 1. enter a name or term 2. wait 2 seconds 3. watch it crash Actual Results: crash Expected Results: no crash krunner Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion org.kde.kurifilter-ikws: ":q" org.kde.kurifilter-ikws: Keywords Engine: Loading config... org.kde.kurifilter-ikws: Web Shortcuts Enabled: true org.kde.kurifilter-ikws: Default Shortcut: "" org.kde.kurifilter-ikws: Keyword Delimiter: : Error contacting the daemon! tp-qt 0.9.7 WARN: Introspecting roster failed with "org.freedesktop.Telepathy.Error.NotImplemented": "Roster not supported" ktp-common-internals: Current presence changed ktp-common-internals: Current presence changed QSocketNotifier: Invalid socket 73 and type 'Read', disabling... The X11 connection broke (error 1). Did the X11 server die? kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" session switching to "Tes" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" session switching to "Test" Xapian::Query((NAruge:(pos=1,wqf=2) OR ruge:(pos=1,wqf=2))) QtWebEngine::initialize() must be called from the Qt gui thread. KCrash: Attempting to start /usr/bin/krunner from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... QSocketNotifier: Invalid socket 63 and type 'Read', disabling... QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Exception', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... [2] Exit 253krunner [3]+ Angehalten krunner [piedro@arch ~]$ QSocketNotifier: Invalid socket 65 and type 'Read', disabling... The X11 connection broke (error 1). Did the X11 server die? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 353675] Search does not work, neither do search folders
https://bugs.kde.org/show_bug.cgi?id=353675 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #2 from piedro --- On the latest KDE 16.08 on Arch search still cannot be refined after creating a search folder. The virtual folders' context menu shows the entry "edit search" but this does not seem to work. If I add additional search criteria or remove some (which doesn't work at first because the "remove" buttons are greyed out - you have to add one criteria first then it's possible to delete...) - the results do not change at all. this doesn't work since kmail2 has been published - please remove the option from the context menu if it will not be fixed. Otherwise it just leads to a frustrating user experience. thx for reading, p. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366564] Please change autostart defaults to not interfere with non-KDE desktops
https://bugs.kde.org/show_bug.cgi?id=366564 piedro changed: What|Removed |Added Resolution|WONTFIX |--- Status|RESOLVED|UNCONFIRMED --- Comment #3 from piedro --- I think I answerred to the wrong thread here - I can disable it with additional entries in the *.desktop files. So please ignore my comment. Though I still do not understand why autostart is enabled by default just "because it works"? The Gnome file indexer tracker works with every desktop. Still you wouldn't want it to autostart with KDE in the background, right? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366564] Please change autostart defaults to not interfere with non-KDE desktops
https://bugs.kde.org/show_bug.cgi?id=366564 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #2 from piedro --- How to disable it in gnome if I do not want to use it with gnome? Why is it against the design to enable the option to start selectively? Choice is better than no choice, right? thx, p. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #3 from piedro --- I use KDE and kalarm version16.4.3. (Well, I do not use it really but have it installed to check out KDE here and then to find out when it's good enough for productive ue for me...) So, same situation as for David. thx, p. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366564] New: Please change autostart defaults to not interfere with non-KDE desktops
https://bugs.kde.org/show_bug.cgi?id=366564 Bug ID: 366564 Summary: Please change autostart defaults to not interfere with non-KDE desktops Product: kdeconnect Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: piedro.kul...@googlemail.com The kdeconnectd.desktop entries in /etc/xdg/autostart indicate that kdeconnectd is started with every desktop environment. Imo this is very intrusive, a user who installs a secondary DE should not beforced to run KDE daemons in the background. The use of kdeconnectd should be optional and not enabled by default. Please change the entry in kdeconnectd.desktop from > X-GNOME-Autostart-enabled=true > OnlyShowIn=KDE;GNOME;Unity;XFCE; to > X-GNOME-Autostart-enabled=false > OnlyShowIn=KDE; thx, p. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 366562] New: Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 Bug ID: 366562 Summary: Kalarm starts in non-KDE desktop environments... Product: kalarm Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kalarmd Assignee: djar...@kde.org Reporter: piedro.kul...@googlemail.com Kalarm is by default set to start with every desktop environment. Please add X-GNOME-Autostart-enabled=false OnlyShowIn=KDE or something along these lines to the default autostart configuration file in /etc/xdg/autostart/. A KDE application should not be autostarted within other DEs unless explicitly asked for. It's just a little change to the default configuration and leads to less people wondering how to disable kalarm when starting Gnome which has it's own calendar and reminder service. thx a lot, piedro Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] New: Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 Bug ID: 366561 Summary: Baloo file daemon starts with non-KDE Desktop environments Product: frameworks-baloo Version: 5.24.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: piedro.kul...@googlemail.com As I found out after looking into the /ec/xdg/autostart folder - the following settings are used to start the baloo file daemon in the background no matter what DE is used. > X-GNOME-Autostart-enabled=true > OnlyShowIn=KDE;GNOME;Unity;XFCE This is unnecessarily intrusive behaviour. Users installing another desktop environment alongside KDE will have a distorted experience (like performance issues - Gnome for example has it's own background service for indexing!). Since there are now additional background processes running which have no function within their DE. Please change the configuration defaults to something like: > X-GNOME-Autostart-enabled=false > OnlyShowIn=KDE thx, piedro Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 333644] Kontact crashes when using the preferences window for the overview/summary component
https://bugs.kde.org/show_bug.cgi?id=333644 --- Comment #7 from piedro --- I do not have this problem anymore... Cheers, p. -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 55421] KMail can't read a local Maildir without a copy
https://bugs.kde.org/show_bug.cgi?id=55421 piedro changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #11 from piedro --- Since this is very old I do not know if anybody reads this - but I think this is still a major concern: Kmail should be able to use and read mail dir created by evolution and vice versa. Why is there a standard if kmail doesn't follow it - isn't that exactly what standards are for? Also this is one of the most important arguments of the FOSS world against proprietary software with each piece of software following company-owned non-disclosed formats... Still on my wishlist, p. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 333798] KMail: Number of indexed emails doesn't match number of emails
https://bugs.kde.org/show_bug.cgi?id=333798 --- Comment #3 from piedro --- If one enables offline reading for Imap - and then unsubsribes to every single folder - than under "server subsciptions" re-subscribes to all folders again - now the folders get subscibed and while getting downloaded they get indexed... Thing is, now MOST of the mails get indexed but not all of them I get things like inbox containing 212 mails , indexed 201 so about every folder has a few mails missing! This is bad! If there is missing mail in the index you can't use the search in any critical workflow. Also there is no indication whatsoever which mails are indexed iand which aren't - so I do not even know which of my mails are included in a fulltext search and which are not. Also I think it's not a very good habit to not answer or react to bug reports at all. Soon no one will do any reports anymore since it's pointless in most cases. Then you, the devs, have to do your own testing again. ty, p. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #8 from piedro --- p.s.: Also this will probably be realted to many of the bugs regarding incomplete email indices created by the "akonadi-indexing-agent". p. -- You are receiving this mail because: You are watching all bug changes.
