[frameworks-kglobalaccel] [Bug 453423] Numpad shortcuts don't work in wayland sessions.
https://bugs.kde.org/show_bug.cgi?id=453423 Stefanos Harhalakis changed: What|Removed |Added CC||v...@v13.gr -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 357571] IMAP folder re-syncing
https://bugs.kde.org/show_bug.cgi?id=357571 Stefanos Harhalakis changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #7 from Stefanos Harhalakis --- Closing this because I no longer use KDE's IMAP for large mailboxes and can't confirm whether it's still an issue. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 199467] Strange javascript + rendering behavior - bad width calculation?
https://bugs.kde.org/show_bug.cgi?id=199467 Stefanos Harhalakis changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Stefanos Harhalakis --- This is obsolete, 14 years later and can't be reproduced because the URL doesn't exist any more. I don't see an "OBSOLETE" closing justification -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 357215] Plasma-pa controls the volume even after it gets unloaded
https://bugs.kde.org/show_bug.cgi?id=357215 Stefanos Harhalakis changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 202303] Konqueror renders the same page with an error after refresh (data corruption?).
https://bugs.kde.org/show_bug.cgi?id=202303 Stefanos Harhalakis changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 149436] konqueror should default to permanently accepting invalid certificates
https://bugs.kde.org/show_bug.cgi?id=149436 Stefanos Harhalakis changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Stefanos Harhalakis --- With a quick check, seems to be the case. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415271] New: akonadi does not create the file_lost+found folder
https://bugs.kde.org/show_bug.cgi?id=415271 Bug ID: 415271 Summary: akonadi does not create the file_lost+found folder Product: Akonadi Version: GIT (master) Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: v...@v13.gr Target Milestone: --- It seems that akonadi does not create the file_lost+found directory which results in "akonadictl fsck" failing to move files there. See here: https://github.com/KDE/akonadi/blob/ed93384ff692a684a1ade9bbc283ba495c0b3fe3/src/server/storagejanitor.cpp#L460-L466 There isn't anything that creates the directory. In my case, I was running fsck continuously without any effect. The result was like this: Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/56/5634856_r0 Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/27/7826627_r0 Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/08/5711008_r1 And then: Moved 105853 unreferenced files to lost+found. But nothing was being moved. Then, once I created it by hand, it moved 3.8GB I tried restarting akonadi in case it creates the directory, but nothing I'm using akonadi server 4:18.08.3-7 (debian testing). -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 --- Comment #9 from Stefanos Harhalakis --- The patch got submitted and it works for me. I'd suggest trying it yourself. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403124] Two kalarm resources fighting each other
https://bugs.kde.org/show_bug.cgi?id=403124 --- Comment #2 from Stefanos Harhalakis --- I don't actually remember. It is possible that I created something or that one of the upgrades did it. It was a funny failure mode though, even if it's not worth looking at. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403124] New: Two kalarm resources fighting each other
https://bugs.kde.org/show_bug.cgi?id=403124 Bug ID: 403124 Summary: Two kalarm resources fighting each other Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KAlarm resource Assignee: djar...@kde.org Reporter: v...@v13.gr CC: kdepim-b...@kde.org Target Milestone: --- SUMMARY It seems that I have two resources fighting each other. I noticed in akonadiconsole. It never stops: AgentBase(akonadi_kalarm_resource_12): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_12/template.ics-347'. AgentBase(akonadi_kalarm_resource_22): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_22/template.ics-349'. AgentBase(akonadi_kalarm_resource_12): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_12/template.ics-348'. AgentBase(akonadi_kalarm_resource_22): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_22/template.ics-350'. AgentBase(akonadi_kalarm_resource_12): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_12/template.ics-349'. AgentBase(akonadi_kalarm_resource_22): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_22/template.ics-351'. AgentBase(akonadi_kalarm_resource_12): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_12/template.ics-350'. AgentBase(akonadi_kalarm_resource_22): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_22/template.ics-352'. AgentBase(akonadi_kalarm_resource_12): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_12/template.ics-351'. AgentBase(akonadi_kalarm_resource_22): The file 'file:///home/v13/.kde/share/apps/kalarm/template.ics' was changed on disk. As a precaution, a backup of its previous contents has been created at 'file:///home/v13/.local/share/akonadi_kalarm_resource_22/template.ics-353'. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 --- Comment #7 from Stefanos Harhalakis --- I believe the problem is that it ignores virtual devices. https://phabricator.kde.org/D17784 fixes it for me. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 Stefanos Harhalakis changed: What|Removed |Added CC||v...@v13.gr -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 301447] Desktop grid effect changes activities
https://bugs.kde.org/show_bug.cgi?id=301447 --- Comment #13 from Stefanos Harhalakis --- Thanks Vlad! -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185 Stefanos Harhalakis changed: What|Removed |Added CC||v...@v13.gr -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 Stefanos Harhalakis changed: What|Removed |Added CC||v...@v13.gr -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 357571] New: IMAP folder re-syncing
https://bugs.kde.org/show_bug.cgi?id=357571 Bug ID: 357571 Summary: IMAP folder re-syncing Product: Akonadi Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: v...@v13.gr CC: kdepim-b...@kde.org, vkra...@kde.org Hi there, This is related to the thread "IMAP and permanent folder syncing" (https://marc.info/?t=14484380794&r=1&w=2) which I'm not sure how to respond to as I'm not subscribed to the list. I'm using the the equivalent of disconnected IMAP which is meant to keep the messages locally. However, the messages keep refreshing again and again and there is also some random behavior. By refreshing, I mean that kmail/akonadi are actually re-downloading the whole folder again and again on random times. I.e they re-download all messages. This happens since the upgrade to this version. If I start akonadi from the command line I see its output, which indicates this. Here's an example: -- log_imapresource: Starting retrieval for "23 - X" log_imapresource: Starting message retrieval. Elapsed(ms): 900 log_imapresource: MessageCount: 4442 Local message count: 4440 log_imapresource: UidNext: 258627 Local UidNext: 258626 log_imapresource: HighestModSeq: 0 Local HighestModSeq: 0 log_imapresource: Detected inconsistency in local cache, we're missing some messages. Server: 4442 Local: 4440 log_imapresource: Refetching complete mailbox. akonadiagentbase_log: 4442 4442 log_imapresource: Fetching 1 intervals Received: 10 In total: 10 Wanted: 4442 Received: 16 In total: 26 Wanted: 4442 Received: 2 In total: 28 Wanted: 4442 Received: 17 In total: 4436 Wanted: 4442 Received: 5 In total: 4441 Wanted: 4442 Received: 1 In total: 4442 Wanted: 4442 log_imapresource: Applying collection changes log_imapresource: Retrieval complete. Elapsed(ms): 65660 finished log_imapresource: "/23 - XX" -- The above example is quite interesting as it is accompanied by another strangeness in kmail: The folder "23 - " (I'm masking the name here) is what is referenced in the logs. It is also the one I see in akonadiconsole being synced. However, after the retrieval, the messages are accounted in a completely different folder in kmail, which now has 4441 unread messages. Clicking on that folder I see one message (on a previous occurrence there were more). When clicking on the message I get blank contents and kmail writes this to the console: log_messagelist: View message selected [ "I'm masking the subject here" ] log_kmail: 103 "Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Invalid item retrieved" At this point kmail did a timed synced (it's configured to check every ~5 minutes) and all the message from this folder were moved to the proper folder instead (i.e. it fixes itself). When that happened, the console displayed this: "Item query returned empty result set" My setup is debian test+experimental. akonadi-server 15.08.3, kmail 15.08.3, using akonadi's mysql. I have this behavior on two separate debian systems with similar setup but with different accounts. One is Gmail and the other is a company email server. I tried wiping the DIMAP account completely and recreating it from scratch (the messages above are from a kmail account that I created 2 weeks ago), but there was no luck. I have also tried "akonadictl fsck" and "akonadictl vacuum", but there wasn't any improvement. I just ran another "akonadictl fsck" and I got this: ... "Item \"1509180\" has no RID." "Item \"1509182\" has no RID." "Item \"1509183\" has no RID." "Item \"1509184\" has no RID." "Item \"1509185\" has no RID." "Found 64977 items without RID." "Found 0 dirty items." "Consistency check done." (lines above that scrolled outside of the scroll buffer, but there were no errors other than the RID one) Finally, the akonadi resource crashes with segmentation fault (sig 11) every now and then (e.g. it crashed right now). I don't think it correlates to the problem though. Is there anything more I could check to try and figure out what's wrong? Thanks, Stefanos Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 357215] New: Plasma-pa controls the volume even after it gets unloaded
https://bugs.kde.org/show_bug.cgi?id=357215 Bug ID: 357215 Summary: Plasma-pa controls the volume even after it gets unloaded Product: plasma-pa Version: 5.4.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: v...@v13.gr Hi again, When plasma-pa is unloaded from the system tray, it still controls the volume. Scenario: * Start plasma with plasma-pa disabled ** Keyboard's volume keys are not captured by plasma-pa * Enable plasma-pa on the system tray (from system tray settings) ** Keyboard's volume keys are captured by plasma-pa and plasma-pa's OSD is shown * Disable plasma-pa on the system tray ** Keyboard's volume keys are still captured by plasma-pa The only way to disable plasma-pa is to disabled it in the system tray and the restart plasmashell. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 357214] New: Volume control affects all inputs
https://bugs.kde.org/show_bug.cgi?id=357214 Bug ID: 357214 Summary: Volume control affects all inputs Product: plasma-pa Version: 5.4.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: v...@v13.gr Hi there, I tested plasma-pa and while it looks nice, I believe that there are two issues: OSD and volume control. This bug report is about the latter. In short, the issue is that when you adjust the volume with the keyboard's volume keys, the volume gets adjusted for all inputs (in contrast with kmix where you can select a master channel). I find this to be an issue for any setup that has multiple outputs. My setup is as follows: * Pulseaudio * 3 outputs: Onboard sound card, USB sound card, Bluetooth headphones * Pulseaudio is configured to have a simultaneous output * Everything uses the simultaneous output by default The above mean that there are 4 outputs: 3 plus the simultaneous one. I'm setting up the volume individually to relatively adjust them, or set them to the maximum to preserve quality. I then control the volume with the master channel (simultaneous output), which is 100% feasible with kmix, but impossible with plasma-pa. But it gets worse: If I mute one of the outputs (which I do, because one has a pair of cabled headphones connected and I don't want them playing anything when I use the bluetooth ones) and I use the keyboard's volume control keys, it unmutes the output. As such, please consider making the volume control keys only affect one output and not all of them. I.e. add an option for the master channel/output a'la kmix. Thanks, Stefanos Reproducible: Always Steps to Reproduce: Use the keyboard to adjust the volume Actual Results: All outputs are adjusted Expected Results: Only one output should be affected -- You are receiving this mail because: You are watching all bug changes.
