Установил KDesktop@обновился до Сизифа, KMail немножко хандрит

[Старче]

Установил KDesktop@обновился до Сизифа, не запускается KMail

Код: [Выделить]

$ kmail -caption "%c"
Object::connect: No such slot KMMainWidget::slotItemNotMovedByFilters( Akonadi::Item )
[d@1 ~]$ kmail2(8136)/libakonadi Akonadi::EntityTreeModelPrivate::firstFetchJobDone: "Неизвестная ошибка. (Failed to create mimetype record)"
kmail2(8136)/libakonadi Akonadi::DefaultResourceJob::slotResult: "Unknown resource"
kmail2(8136)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Неизвестная ошибка. (Unknown resource)"
kmail2(8136) MailCommon::Kernel::emergencyExit: "Аварийное завершение работы KMail.
Причина:
Unknown resource"


[asy]

Установил KDesktop@обновился до Сизифа, не запускается KMail

Не стоило, если нет желания быть бетатестером: в Сизифе переход на KMail2 идёт и не всё ещё хорошо. А если желание есть, то писать лучше в рассылку sisyphus@

[Старче]

Сегодняшее обовление kde4pim (4.7.2-alt6) to 4.7.3-alt1@kde4pim-akonadi (4.7.2-alt6) to 4.7.3-alt1 устранило баг, красота  :)

[Grommit]

А когда нужно ждать KDE 4.7.х в р6, и ждать ли вообще?

[Skull]

А когда нужно ждать KDE 4.7.х в р6, и ждать ли вообще?

Скорее всего, этой версии в стабильном бранче p6 не будет.

[Старче]

Загрузилась вся почта с imap'овского сервера, отображаются все папки кроме почему-то папки Sent, отчёт Akonadi:

Код: [Выделить]

Akonadi Server Self-Test Report
===============================

Test 1:  SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/d/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/d/.local/share/akonadi/socket-1.localdomain/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3:  SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4:  SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld  Ver 5.1.59 for alt-linux-gnu on i586 (ALT Linux MySQL RPM)


Test 5:  SUCCESS
--------

MySQL server log contains no errors.
Details: The MySQL server log file &apos;<a href='/home/d/.local/share/akonadi/db_data/mysql.err'>/home/d/.local/share/akonadi/db_data/mysql.err</a>&apos; does not contain any errors or warnings.

File content of '/home/d/.local/share/akonadi/db_data/mysql.err':
111105 15:17:18  InnoDB: Initializing buffer pool, size = 80.0M
111105 15:17:18  InnoDB: Completed initialization of buffer pool
111105 15:17:18  InnoDB: Started; log sequence number 0 24769146
111105 15:17:18 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.59'  socket: '/home/d/.local/share/akonadi/socket-1.localdomain/mysql.socket'  port: 0  ALT Linux MySQL RPM


Test 6:  SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=8M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000

[client]
default-character-set=utf8


Test 7:  SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8:  SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/d/.local/share/akonadi/mysql.conf'>/home/d/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/d/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=8M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000

[client]
default-character-set=utf8


Test 9:  SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.6.2


Test 10:  SUCCESS
--------

Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.

Test 11:  SUCCESS
--------

Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.

Test 12:  SUCCESS
--------

Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.

Test 13:  SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

Test 14:  SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 15:  SUCCESS
--------

Resource agents found.
Details: At least one resource agent has been found.

Directory listing of '/usr/share/akonadi/agents':
akonotesresource.desktop
birthdaysresource.desktop
calendarsearchagent.desktop
contactsresource.desktop
davgroupwareresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share/kde4:/usr/share'

Test 16:  ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/d/.local/share/akonadi/akonadiserver.error'>/home/d/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/d/.local/share/akonadi/akonadiserver.error':
ItemRetrieverException :  Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ItemRetrieverException :  Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ItemRetrieverException :  Resource was unable to deliver item
ItemRetrieverException :  Resource was unable to deliver item
ItemRetrieverException :  Resource was unable to deliver item
ItemRetrieverException :  Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ItemRetrieverException :  Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


Test 17:  SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.


Перезагрузка Akonadi к сожалению картины не меняет,

Заменять mysql-базу заново как описано здесь https://bugzilla.altlinux.org/show_bug.cgi?id=26541 наверно рано, т.к. и Входящие, и Спам, и Черновики все письма нормально показывают + письма нормально перемещаются из папки в другую.

Есть ли какой-то способ прицельно перезапустить/перезалить одну выбранную папку (не хочется обратно тянуть весь ящик вместе с полгигом Входящих)

[Старче]

Не решив вышеописанную проблему с Отправленными на буржуйском IMAP-сервере из Сизифовской версии KMail, опять переустановил  KDesktop@обновился на этот раз до штатногог p6-го бранча и закачал всю почту с обоих IMAP-овских ящиков в штатную p6-версию KMail'а (4.6.5),

Потом наткнулся на этот пост http://lists.altlinux.org/pipermail/community/2011-November/673497.html в коммьюнити-рассылке, опять решил всё-таки попробовать установить кеды со свежим KMail-ом,

Сперва скачал@скопировал в указанное место базу mysql как это описано здесь https://bugzilla.altlinux.org/show_bug.cgi?id=26541#c12 , подключил бранч@обновился@перезагрузился, в KMail всё мигрировалось большей частью нормально (фотки 4 и 6),

Правда не обошлось без нескольких затыков (фотка 2 - KMail не может достучаться до яндексовского ящика с рассылкой (такое часто выскакивало на KMail-4.6.5, из-за этого кстати я так упорно хотел обновится до Сизиф-версии), ещё яндексовский akonadi-imap-resource один раз упал в процессе миграции, и с буржуйсккого IMAP-сервера почта каждый раз качала множество копий одного и того же письма и получалось например  по 7000 писем вместо реальных 700, приходилось вручную прерывать получение этой почты@перезагружаться, после этого всё норм),

Но в целом почта мигрировалась из старых ящиков штатно, письма получаются-отправляются, только непонятно что сейчас делать с кэшем старых писем, то ли стирать, то ли нет 

Спасибо  Sergey V Turchin за свежие кеды  :) (кстати, похоже сейчас так обновится до свежих кед 4.7.3 с p6-бранча уже не получится, в месте с которого обновлял кеды http://git.altlinux.org/repo/57771/ уже пусто)

И немного не по теме, возможно ли и если да то как в KMail смотреть, с какого почтового клиента отправитель прислал мне письмо? В Thunderbird это было возможно с помощью какого-то дополнения, я помню