[kmail2] [Bug 333963] [4.13] Search bar does not work anymore
https://bugs.kde.org/show_bug.cgi?id=333963 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Version Fixed In||4.13.1 Resolution|--- |FIXED --- Comment #2 from Laurent Montel mon...@kde.org --- I fixed quick search for searching email even if baloo is disable. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #12 from Raymond Wooninck tittiatc...@gmail.com --- Issue has been resolved. Synchronizing my GMAIL account is now done is the same time as with KDE 4.13.0. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)
https://bugs.kde.org/show_bug.cgi?id=332358 Jonathan Marten j...@keelhaul.me.uk changed: What|Removed |Added CC||j...@keelhaul.me.uk -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)
https://bugs.kde.org/show_bug.cgi?id=332358 Sebastian Vöcking k...@voecking.net changed: What|Removed |Added CC||k...@voecking.net -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 334406] New: possible timing problem at startup - setting resources online and mail check failing
https://bugs.kde.org/show_bug.cgi?id=334406 Bug ID: 334406 Summary: possible timing problem at startup - setting resources online and mail check failing Classification: Unclassified Product: kmail2 Version: Git (master) Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: j...@keelhaul.me.uk If KMail needs to start the Akonadi server because it is not currently running, there appears to be a timing problem between the server starting up and KMail doing things which assume that the server is fully available. In my case, this results in resources not being set online when they should be (notably Local Folders, this may be the root cause of bug 334175) and a mail check not being done on startup (assuming that this is configured). I have added debug messages to KMKernel::setAccountStatus() and KMKernel::checkMailOnStartup() to report when they are called and how many agent instances are reported from MailCommon::Util::agentInstances(). The server state is initially 4 (Broken) and no agents are reported; only when the state changes to 2 (Running) is the list available. By then it is too late. Attached is an extract from a voluminous log file, with all lines are still in the original time order. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 334406] possible timing problem at startup - setting resources online and mail check failing
https://bugs.kde.org/show_bug.cgi?id=334406 --- Comment #1 from Jonathan Marten j...@keelhaul.me.uk --- Created attachment 86485 -- https://bugs.kde.org/attachment.cgi?id=86485action=edit KMail startup log file -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 334409] New: Drag and drop to a shell doesn't work for multiple files
https://bugs.kde.org/show_bug.cgi?id=334409 Bug ID: 334409 Summary: Drag and drop to a shell doesn't work for multiple files Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: dav1dblunk...@hotmail.com I can drag an attachment from kmail for a shell (where the file gets copied to the directory that the shell is in). This is super handy. However, doing the same thing for more than one file doesn't work and instead pastes the names of the files into the shell each separated by a return which is not handy. It is a bit more complex - D+D works only if the file icon is dragged and when dragging a selection it only copies the file whose icons was dragged even if there is a selection, dragging any other part of the text highlighted gets the text. Reproducible: Always Steps to Reproduce: Attempt to D+D multiple attachments Actual Results: Either get one or the text Expected Results: All attachments copied together -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knode] [Bug 334362] Can't configure: Configure window is empty
https://bugs.kde.org/show_bug.cgi?id=334362 Wolfgang Bauer wba...@tmo.at changed: What|Removed |Added CC||wba...@tmo.at --- Comment #2 from Wolfgang Bauer wba...@tmo.at --- (In reply to comment #1) Works here in Kubuntu 12.04, 4.13 + master compiled from sources. Please report your problem to openSUSE Well, it works here as well in openSUSE 13.1 with the 4.13 packages from the KDE:Current repo, so I doubt this is an openSUSE issue. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334412] New: Data of Akonadi Google are not synced
https://bugs.kde.org/show_bug.cgi?id=334412 Bug ID: 334412 Summary: Data of Akonadi Google are not synced Classification: Unclassified Product: Akonadi Version: 4.13 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Google Resource Assignee: dvra...@redhat.com Reporter: vojtech.zei...@opensuse.org CC: kdepim-bugs@kde.org KOorganizer does not show all Google calendars I have checked in the resources settings. Also, new events created in KOrganizer (or edited, e.g. checking task as done) are not synced to Google. Similar with contacts. New contacts added to Google resource in KAddressBook are not synced to Google. There is no error reported. If I browse the resource in Akonadi Console, I see the event or contact, but it doesn't have Remote Id. There does not seem to be any errors in Debugger of Akonadi Console. Interesting is, that remote changes and added events and contacts are downloaded. The problem doesn't happen in 100 % of cases, sometimes local changes are synced, but it is not reliable. I don't know if it is related, but when I try to modify some Akonadi Google resources, I get an error Bad request and when trying to synchronize them, I see error Failed to refresh tokens. There is also last problem. I don't know if related. KAddressBook does not show contact pictures for all contacts. I tried to remove and recreate affected resource, but no success. There are some changes, but general state is same. I checked kdewallet and contacts and calendars and tasks Google are connected and Akonadi Google folder contains expected data. Reproducible: Always Actual Results: Local changes in Google contacts, calendars and tasks are not synced and some calendars are not displayed, not all contact pictures are downloaded. Expected Results: All on-line data are retrieved and syncing works in both directions with all data. $ uname -a Linux veles.site 3.11.10-7-desktop #1 SMP PREEMPT Mon Feb 3 09:41:24 UTC 2014 (750023e) x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a LSB Version:n/a Distributor ID: openSUSE project Description:openSUSE 13.1 (Bottle) (x86_64) Release:13.1 Codename: Bottle -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 286826] After system crash, postgresql akonadi server doesn't start due to lock file
https://bugs.kde.org/show_bug.cgi?id=286826 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||1.12.2 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/akon ||adi/f217d9e96dc8de88916e8ca ||0b93dd9a7500bbbc3 --- Comment #2 from Daniel Vrátil dvra...@redhat.com --- Git commit f217d9e96dc8de88916e8ca0b93dd9a7500bbbc3 by Dan Vrátil. Committed on 06/05/2014 at 14:38. Pushed by dvratil into branch '1.12'. Fix PostgreSQL start when postmaster.pid is not removed after non-clean shutdown When PostgreSQL is not terminated nicely, a pidfile is left behind in db_data, which will prevent pg_ctl from starting a new PostgreSQL server. We check for postmaster.pid file and verify that postgres server with PID specified in the pidfile is not running anymore, then delete the pidfile to allow pg_ctl to start a new server. If the postgres server is still running (possibly after Akonadi server crash), we try to connect to it right away. FIXED-IN: 1.12.2 M +37 -0server/src/storage/dbconfigpostgresql.cpp http://commits.kde.org/akonadi/f217d9e96dc8de88916e8ca0b93dd9a7500bbbc3 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334420] New: Different behavior when starting mysqld via command line and crash/do not start after doing same via akonadi
https://bugs.kde.org/show_bug.cgi?id=334420 Bug ID: 334420 Summary: Different behavior when starting mysqld via command line and crash/do not start after doing same via akonadi Classification: Unclassified Product: Akonadi Version: 4.13 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: peter.fod...@stuba.sk When staring mysqld via /usr/sbin/mysqld --defaults-file=/home/peto/.local/share/akonadi/mysql.conf --datadir=/home/peto/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-petoMOJ/mysql.socket is mysqld straed as single process and I reached mysql.err as of 140506 14:34:49 InnoDB: The InnoDB memory heap is disabled 140506 14:34:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140506 14:34:49 InnoDB: Compressed tables use zlib 1.2.8 140506 14:34:49 InnoDB: Using Linux native AIO 140506 14:34:49 InnoDB: Initializing buffer pool, size = 128.0M 140506 14:34:49 InnoDB: Completed initialization of buffer pool 140506 14:34:49 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 815629381135 140506 14:34:49 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 815629381247 140506 14:34:49 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 634, file name ./mysql-bin.000331 140506 14:34:50 InnoDB: Waiting for the background threads to start 140506 14:34:51 Percona XtraDB (http://www.percona.com) 5.5.33-MariaDB-31.1 started; log sequence number 815629381247 140506 14:34:51 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.33-MariaDB-log' socket: '/tmp/akonadi-petoMOJ/mysql.socket' port: 0 openSUSE package 140506 14:39:13 [Note] /usr/sbin/mysqld: Normal shutdown 140506 14:39:13 InnoDB: Starting shutdown... 140506 14:39:14 InnoDB: Shutdown completed; log sequence number 815629381247 140506 14:39:14 [Note] /usr/sbin/mysqld: Shutdown complete or 140506 14:34:49 InnoDB: The InnoDB memory heap is disabled 140506 14:34:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140506 14:34:49 InnoDB: Compresse devtmpfs1.9G 8.0K 1.9G 1% /dev tmpfs 2.0G 88K 2.0G 1% /dev/shm tmpfs 2.0G 3.7M 2.0G 1% /run tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup d tables use zlib 1.2.8 140506 14:34:49 InnoDB: Using Linux native AIO 140506 14:34:49 InnoDB: Initializing buffer pool, size = 128.0M 140506 14:34:49 InnoDB: Completed initialization of buffer pool 140506 14:34:49 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 815629381135 140506 14:34:49 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 815629381247 140506 14:34:49 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 634, file name ./mysql-bin.000331 140506 14:34:50 InnoDB: Waiting for the background threads to start 140506 14:34:51 Percona XtraDB (http://www.percona.com) 5.5.33-MariaDB-31.1 started; log sequence number 815629381247 140506 14:34:51 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.33-MariaDB-log' socket: '/tmp/akonadi-petoMOJ/mysql.socket' port: 0 openSUSE package 140506 14:39:13 [Note] /usr/sbin/mysqld: Normal shutdown 140506 14:39:13 InnoDB: Starting shutdown... 140506 14:39:14 InnoDB: Shutdown completed; log sequence number 815629381247 140506 14:39:14 [Note] /usr/sbin/mysqld: Shutdown complete 140506 14:40:27 InnoDB: The InnoDB memory heap is disabled 140506 14:40:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140506 14:40:27
[Akonadi] [Bug 333808] DAV resource asks for password, while kwallet password dialog is still open
https://bugs.kde.org/show_bug.cgi?id=333808 --- Comment #1 from Frédéric COIFFIER frederic.coiff...@free.fr --- Same problem with Gentoo and KDE 4.13.0 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 333808] DAV resource asks for password, while kwallet password dialog is still open
https://bugs.kde.org/show_bug.cgi?id=333808 Frédéric COIFFIER frederic.coiff...@free.fr changed: What|Removed |Added CC||frederic.coiff...@free.fr -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332988] crash during startup with postgres backend
https://bugs.kde.org/show_bug.cgi?id=332988 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||1.12.2 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/akon ||adi/74b2d3a43e19f5262ec84cc ||f609925eeb071d755 --- Comment #2 from Daniel Vrátil dvra...@redhat.com --- Git commit 74b2d3a43e19f5262ec84ccf609925eeb071d755 by Dan Vrátil. Committed on 06/05/2014 at 14:49. Pushed by dvratil into branch '1.12'. Remove space from an argument passed to postgres server Some users reported problem with starting PostgreSQL when there's a space between name and value of an argument passed to postgres. Removing the space fixes problem for them (withouth breaking PostgreSQL for those who didn't have a problem with the space) Thanks SergTruf for the patch. FIXED-IN: 1.12.2 M +1-1server/src/storage/dbconfigpostgresql.cpp http://commits.kde.org/akonadi/74b2d3a43e19f5262ec84ccf609925eeb071d755 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 334357] knotes migration fails if akonadi is not running
https://bugs.kde.org/show_bug.cgi?id=334357 --- Comment #2 from Wolfgang Bauer wba...@tmo.at --- (In reply to comment #1) PS: I now even got the timeout (the first one) with akonadi running already. I had to retry 3 times to finally get my notes migrated again. Please ignore this last comment, this was apparently caused by some left-over (hanging) akonadi_agent_launcher processes, that kept running even after stopping akonadi. (and I had a knotes process as well that I couldn't even kill) After a reboot it works again now when akonadi is running. I still get the timeouts when akonadi is not running, i.e. the original bug report is still valid. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328636] Calendar event isn't syncronized with google calendar after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=328636 --- Comment #4 from Ezio Vergine virgo...@gmail.com --- Created attachment 86501 -- https://bugs.kde.org/attachment.cgi?id=86501action=edit workaround script Script to resyncronize google calendar resources -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328636] Calendar event isn't syncronized with google calendar after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=328636 --- Comment #5 from Ezio Vergine virgo...@gmail.com --- I've also found the script attached with name workaround script, but it doesn't work, I've to reboot my laptop to have akonadi work. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334448] New: imap stuck on Retrieving extra folder information for some folders.
https://bugs.kde.org/show_bug.cgi?id=334448 Bug ID: 334448 Summary: imap stuck on Retrieving extra folder information for some folders. Classification: Unclassified Product: Akonadi Version: GIT (master) Platform: Compiled Sources OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: lacsi...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org The imap resource gets stuck at some point (near the end, I am guessing) during mail retrieval. This happens only for imap resources fetching mail from Microsoft outlook servers. In kmail or akonadiconsole I have a message saying Retrieving extra folder information for folder Most of the time this folder is INBOX but sometimes it is other random folder. I have waited to see if it was just a matter of time but after a couple of hours the situation remains. When this happens, I have to restart akonadi (or just the resources) to be able to see my mail again in any folder, independently of the acount. Reproducible: Always All the imap acounts have the Disconnected mode enabled. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
