Jump to content

Akonadi/pt-br: Difference between revisions

From KDE UserBase Wiki
FuzzyBot (talk | contribs)
Updating to match new version of source page
FuzzyBot (talk | contribs)
Updating to match new version of source page
 
(108 intermediate revisions by 7 users not shown)
Line 1: Line 1:
<languages />
<languages />


== Introdução ==
<span id="Introduction"></span>
==Introdução==


<span class="mw-translate-fuzzy">
<div class="mw-translate-fuzzy">
Na versão 4.4 da compilação de software do KDE, o '''KAddressBook''' (Gerenciador de Contatos) tornou-se a primeira aplicação a utilizar '''Akonadi'''. Existem pequenos erros no sistema, inevitáveis nas primeiras fases da migração, e a '''[[Special:myLanguage/Akonadi_4.4/Troubleshooting|página de solução de problemas]]''' pode auxiliá-lo a resolvê-los. Para uma breve descrição da finalidade do '''Akonadi''', veja '''[[Special:myLanguage/Glossary#Akonadi|esta palavra no glossário]]'''. Você também encontrará alguma ligações úteis para mais informações. Uma vez ultrapassados os problemas iniciais, o '''Akonadi''' fornecerá uma base poderosa que será usada por muitas aplicações.
O '''Akonadi''' é o responsável pelo fornecimento de aplicativos com um banco de dados centralizado para armazenar, indexar e recuperar informações pessoais do usuário. Isso inclui e-mails do usuário, contatos, calendários, eventos, diários, alarmes, notas, etc. Na versão 4.4 do KDE, o [[Special:myLanguage/KAddressBook|KAddressBook]] tornou-se o primeiro aplicativo a utilizar o '''Akonadi'''. Na versão 4.7, [[Special:myLanguage/KMail|KMail]], [[Special:myLanguage/KOrganizer|KOrganizer]], [[Special: myLanguage/KJots|KJots]], etc, foram atualizados para também utilizar o '''Akonadi'''. Além disso, vários widgets do [[Special:myLanguage/Plasma|Plasma]] também usam o '''Akonadi''' para armazenar e recuperar eventos de calendário, notas, etc.
</span>
</div>


At the time of writing, the following applications are enabled to use the '''Akonadi''' framework to centrally store and access user data. Follow through to each application's page to learn more.
Currently, all [https://kontact.kde.org/ KDE PIM applications] with the exception of [[Special:myLanguage/Akregator|Akregator]] are using '''Akonadi''' to access user's PIM data.


:{|
<span id="Controlling_Akonadi"></span>
{{AppItem|KMail|View-pim-mail.png|
<div class="mw-translate-fuzzy">
KMail}}Mail Client
==Controle do servidor Akonadi==
Uses '''Akonadi''' to store emails
</div>
|-
{{AppItem|KAddressBook|View-pim-contacts.png|
KAddressBook}}Contact Manager
Uses '''Akonadi''' to store contact information
|-
{{AppItem|KOrganizer|View-pim-calendar.png|
KOrganizer}}Personal Organizer
Uses '''Akonadi''' to store calendars, events, journals, etc.
|-
{{AppItem|KJots|kjots.png|
KJots}}Note Taking Application
Uses '''Akonadi''' to store notes
|}


In addition to this, plasma widgets like the Digital Clock widget, the Notes widget also use Akonadi to store and retrieve events and notes.
'''Akonadi''' will start automatically in the background when any application using it is started.  


==Controlling the Akonadi server==
To manually start, stop or restart '''Akonadi''', you can use the <code>akonadictl</code> command from the commandline.
Using this method, you can get additional useful information on the console.


The Akonadi control module in System Settings provides an easy means to starting, stopping, restarting and querying the status of the Akonadi server. You may also accomplish this from the commandline using the command akonadictl.
Para iniciar o servidor '''Akonadi''',
 
To start the Akonadi server,


{{Input|1=akonadictl start}}
{{Input|1=akonadictl start}}


To stop the Akonadi server,
Para parar o servidor '''Akonadi''',


{{Input|1=akonadictl stop}}
{{Input|1=akonadictl stop}}


To restart a running Akonadi server,
Para reiniciar o servidor '''Akonadi''' em execução,


{{Input|1=akonadictl restart}}
{{Input|1=akonadictl restart}}


To query the status of the Akonadi server,
Para verificar o status do servidor '''Akonadi''',


{{Input|1=akonadictl status}}
{{Input|1=akonadictl status}}


===Disabling the Akonadi subsystem===
<span id="Disabling_the_Akonadi_subsystem"></span>
===Desabilitando o subsistema Akonadi===  


{{Warning|1=Disabling the Akonadi subsystem causes all Akonadi-enabled applications to not have access to the user's data. This means you will not be able to use any of the above applications while Akonadi is turned off. If you understand this and still wish to disable the Akonadi subsystem, read on.}}
<div class="mw-translate-fuzzy">
O servidor '''Akonadi''' é iniciado por qualquer aplicativo habilitado a usar o '''Akonadi'''. Se não quiser que o Akonadi seja iniciado após o início da sessão, você deve certificar-se de que nenhum aplicativo habilitado a usar o '''Akonadi''' seja carregado na autenticação ou posteriormente. Lembre-se também de verificar os widgets do '''Plasma''' - o widget '''Relógio digital''' do painel padrão, por exemplo, usa o '''Akonadi''' para, opcionalmente, mostrar os eventos do calendário e é ativado por padrão (veja  a opção "Exibir eventos"). Você deve remover todos os widgets que podem iniciá-lo durante a inicialização, caso queira que o Akonadi inicie apenas quando iniciar o '''KMail''' ou outro aplicativo.
</div>


The Akonadi server is launched automatically at login whenever any Akonadi-enabled application requests access to it.
<div class="mw-translate-fuzzy">
{{Remember/pt-br|1=Se não quiser que o '''Akonadi''' fique em execução no seu sistema, você não poderá utilizar nenhum dos aplicativos que precisam do '''Akonadi''' para funcionar. Esses aplicativos não funcionarão quando o '''Akonadi''' for desativado usando os passos abaixo. Veja a lista de [[Special:myLanguage/Akonadi#ApplicationTable|aplicativos que usam o Akonadi]]. Lembre-se de que alguns widgets do '''Plasma''', como o '''Relógio Digital''', usam o '''Akonadi'''.}}
</div>


To disable the Akonadi subsystem, first, shut down the running Akonadi server from the control module or the command line:
<div class="mw-translate-fuzzy">
Para garantir que o Akonadi não seja iniciado, verifique se não há aplicativos que necessitam dele ao iniciar a sessão. Em particular, abra as preferências do miniaplicativo de relógio do Plasma, vá para a página <menuchoice>Calendário</menuchoice> e desmarque a opção "Exibir eventos" para impedir que o Plasma solicite informações ao Akonadi e, dessa forma, inicie-o.
</div>


{{Input|1=akonadictl stop}}
==Some Definitions==
 
;Real data
:By ''real data'' we mean the data, like the contacts or events. These data are stored either on a groupware server or in local files. Where exactly depends on the resource you are using. E.g. the ''Personal Contacts'' resource stores its data under ''$XDG_DATA_HOME/contacts''.
 
;Cached data
:The ''cached data'' are copies of the real data that are kept in the database for faster access and offline caching. The database also keeps the ''meta data'' which are management data needed by '''Akonadi''' to work correctly.
 
;Configuration data
:The ''configuration data'' are the data that configure the '''Akonadi''' server and the individual resources. The general configuration data for the server can be found under ''$XDG_CONFIG_HOME/akonadi''. The configuration data for each indvidual resources are stored under ''$XDG_CONFIG_HOME/akonadi_xyz_resourcerc#'' ('''''xyz''''' is name of resource and '''''#''''' its instance number).
 
:The '''Akonadi''' server configuration is a couple of files in ''$XDG_CONFIG_HOME/akonadi''. It contains which data sources and helper programs are active and will be started and watched (so they can be restarted on crashes) by one of '''Akonadi's''' server processes '''(akonadi_control)'''.
 
:Each data source handler (called resources) or helper program (called agents) can have its own configuration although some agents or resources don't require configuration. The general rule is that for every entry in ''$XDG_CONFIG_HOME/akonadi/agentsrc'' there is a corresponding configuration file in ''$XDG_CONFIG_HOME''.  For example, if the ''[Instances]'' section in ''agentrc'' contains an entry for ''akonadi_ical_resource_2'', there is also a config file called ''akonadi_ical_resource_2rc'' in the ''$XDG_CONFIG_HOME directory''.
 
:Depending on the type of data, such config files for resources will have filenames or directory names of where the data is stored.  Common locations are KDE's legacy default files, e.g. ''$HOME/.kde/share/apps/korganizer/std.ics''.  New default locations are files and directories in ''$XDG_DATA_HOME'', e.g. ''$XDG_DATA_HOME/contacts''.
 
==Backup==
 
So now we need to decide what to back up.  If you want to backup the "real data", then it depends on the resources you have configured... if you use a groupware server, then the backup should be done there. For contacts, the files under ''$XDG_DATA_HOME/contacts'' will normally be what you need.
 
To back up the entire ''Akonadi'' configuration, including which resources are active and their configuration, you can use the '''pimdataexporter''' tool. This, however doesn't back up the Akonadi database containing the cached data and, unfortunately, after restoring the configuration (using the '''pimdataexporter'' again), Akonadi will have to re-fetch all data again into its cache. This can cause configuration that points to actual mail folders or calendars to get broken and accidentally point to another folder.
 
'''After restoring configuration and syncing all data, it's vital to manually check all folder configuration, especially in KMail identities and make sure the folders are configured properly.'''
 
<span id="Frequently_Asked_Questions"></span>
==Perguntas frequentes==
 
<span id="Where_is_my_data_now?"></span>
=== Onde os meus dados estão agora? ===
 
Your data are safely stored outside of '''Akonadi''' control on your disk (e.g. local maildir folder or iCal calendar), or on a remote server (in case of e.g. email over IMAP or events from a CalDAV calendar). '''Akonadi''' will optionally store a copy of this data in its database to allow applications to quickly retrieve and display them. Any modifications done to data in the '''Akonadi''' database will be synced to the actual storage. The main advantage of using the database as a cache is that remote PIM data are available even when you are offline, and you can still interact with them (e.g. mark emails as read or move them, create new events, reschedule existing meetings etc.) and all the changes will get synced automatically once you connect to the internet again.
 
Thus, deleting the '''Akonadi''' database will not cause any data to be lost (as long as all pending changes are synced).
 
<span id="How_to_upgrade_my_PostgreSQL_database?"></span>
=== Como atualizar a minha base dado PostgreSQL? ===


Now, edit the file <tt>~/.config/akonadi/akonadiserverrc</tt> and change <tt>StartServer</tt> from true to false:
Depois de atualizar o seu server PostgreSQL para uma nova versão, algumas vezes você vai ter que converter a sua base de dados Akonadi para usar com essa nova versão. Instruções podem ser encrontradas [[Special:myLanguage/Akonadi/Postgres_update|nessa página]].


{{Output|1=StartServer=false}}
<span id="Migration_problems"></span>
=== Problemas durante a migração ===


The Akonadi server should no longer launch automatically on login.
<div class="mw-translate-fuzzy">
O item '''Akonadi''' do [[Special:myLanguage/Glossary#Akonadi|Glossário]] tem uma breve explicação do seu propósito e outros links úteis. [[Special:myLanguage/Akonadi_and_AddressBook|Esta]] página explica como o '''Akonadi''' e o '''KAddressBook''' funcionam juntos.
</div>


{{Note|1=The Akonadi server will still be started by any Akonadi-enabled application. Ensure that no akonadi-enabled application is launched at login or thereafter. Remember to check Plasma widgets as well — the Digital Clock widget in the default panel, for instance uses Akonadi to (optionally) display Calendar events and this is enabled in its settings by default.}}
=== How do I switch from MySQL/PostgreSQL to SQLite? ===


==Frequently Asked Questions==
Since Akonadi 6 [https://invent.kde.org/pim/akonadi/-/merge_requests/154 akonadi-db-migrator] is included in akonadi that allows you to switch the database backend. Where for previous versions this involved deleting and recreating the database a migration is now properly supported by akonadi.


Refer to [[Special:myLanguage/Akonadi_4.4/Troubleshooting|the Troubleshooting page]] for resolving glitches during migration. Akonadi's [[Special:myLanguage/Glossary#Akonadi|Glossary entry]] has a brief description of its purpose and other useful links. [[Special:myLanguage/Akonadi_and_AddressBook|This]] page explains how Akonadi and KAddressBook work together.
The tool needs to be called with the parameter --newengine to chose to which backend it should to:
{{{
  --newengine <ENGINE>      The new DB engine to use. Possible values are
                            "sqlite", "mysql" and "postgres"
}}}


If you are experiencing 100% CPU usage by the ''virtuoso-t'' process when using Akonadi and related applications, try this proposed workaround while it is being investigated: In KRunner's configuration page, disable the Nepomuk search plugin and the Contact plugin. Then, log out and back in. For further information and inputs, report back here or on the Forum or on the IRC channel #kontact.
For example:
{{{
akonadi-db-migrator --newengine sqlite
}}}


[[Category:Sistema]]
[[Category:Sistema/pt-br]]

Latest revision as of 07:02, 10 August 2024

Introdução

O Akonadi é o responsável pelo fornecimento de aplicativos com um banco de dados centralizado para armazenar, indexar e recuperar informações pessoais do usuário. Isso inclui e-mails do usuário, contatos, calendários, eventos, diários, alarmes, notas, etc. Na versão 4.4 do KDE, o KAddressBook tornou-se o primeiro aplicativo a utilizar o Akonadi. Na versão 4.7, KMail, KOrganizer, KJots, etc, foram atualizados para também utilizar o Akonadi. Além disso, vários widgets do Plasma também usam o Akonadi para armazenar e recuperar eventos de calendário, notas, etc.

Currently, all KDE PIM applications with the exception of Akregator are using Akonadi to access user's PIM data.

Controle do servidor Akonadi

Akonadi will start automatically in the background when any application using it is started.

To manually start, stop or restart Akonadi, you can use the akonadictl command from the commandline. Using this method, you can get additional useful information on the console.

Para iniciar o servidor Akonadi,

akonadictl start

Para parar o servidor Akonadi,

akonadictl stop

Para reiniciar o servidor Akonadi em execução,

akonadictl restart

Para verificar o status do servidor Akonadi,

akonadictl status

Desabilitando o subsistema Akonadi

O servidor Akonadi é iniciado por qualquer aplicativo habilitado a usar o Akonadi. Se não quiser que o Akonadi seja iniciado após o início da sessão, você deve certificar-se de que nenhum aplicativo habilitado a usar o Akonadi seja carregado na autenticação ou posteriormente. Lembre-se também de verificar os widgets do Plasma - o widget Relógio digital do painel padrão, por exemplo, usa o Akonadi para, opcionalmente, mostrar os eventos do calendário e é ativado por padrão (veja a opção "Exibir eventos"). Você deve remover todos os widgets que podem iniciá-lo durante a inicialização, caso queira que o Akonadi inicie apenas quando iniciar o KMail ou outro aplicativo.

Lembrete

Se não quiser que o Akonadi fique em execução no seu sistema, você não poderá utilizar nenhum dos aplicativos que precisam do Akonadi para funcionar. Esses aplicativos não funcionarão quando o Akonadi for desativado usando os passos abaixo. Veja a lista de aplicativos que usam o Akonadi. Lembre-se de que alguns widgets do Plasma, como o Relógio Digital, usam o Akonadi.

Para garantir que o Akonadi não seja iniciado, verifique se não há aplicativos que necessitam dele ao iniciar a sessão. Em particular, abra as preferências do miniaplicativo de relógio do Plasma, vá para a página Calendário e desmarque a opção "Exibir eventos" para impedir que o Plasma solicite informações ao Akonadi e, dessa forma, inicie-o.

Some Definitions

Real data
By real data we mean the data, like the contacts or events. These data are stored either on a groupware server or in local files. Where exactly depends on the resource you are using. E.g. the Personal Contacts resource stores its data under $XDG_DATA_HOME/contacts.
Cached data
The cached data are copies of the real data that are kept in the database for faster access and offline caching. The database also keeps the meta data which are management data needed by Akonadi to work correctly.
Configuration data
The configuration data are the data that configure the Akonadi server and the individual resources. The general configuration data for the server can be found under $XDG_CONFIG_HOME/akonadi. The configuration data for each indvidual resources are stored under $XDG_CONFIG_HOME/akonadi_xyz_resourcerc# (xyz is name of resource and # its instance number).
The Akonadi server configuration is a couple of files in $XDG_CONFIG_HOME/akonadi. It contains which data sources and helper programs are active and will be started and watched (so they can be restarted on crashes) by one of Akonadi's server processes (akonadi_control).
Each data source handler (called resources) or helper program (called agents) can have its own configuration although some agents or resources don't require configuration. The general rule is that for every entry in $XDG_CONFIG_HOME/akonadi/agentsrc there is a corresponding configuration file in $XDG_CONFIG_HOME. For example, if the [Instances] section in agentrc contains an entry for akonadi_ical_resource_2, there is also a config file called akonadi_ical_resource_2rc in the $XDG_CONFIG_HOME directory.
Depending on the type of data, such config files for resources will have filenames or directory names of where the data is stored. Common locations are KDE's legacy default files, e.g. $HOME/.kde/share/apps/korganizer/std.ics. New default locations are files and directories in $XDG_DATA_HOME, e.g. $XDG_DATA_HOME/contacts.

Backup

So now we need to decide what to back up. If you want to backup the "real data", then it depends on the resources you have configured... if you use a groupware server, then the backup should be done there. For contacts, the files under $XDG_DATA_HOME/contacts will normally be what you need.

To back up the entire Akonadi configuration, including which resources are active and their configuration, you can use the pimdataexporter' tool. This, however doesn't back up the Akonadi database containing the cached data and, unfortunately, after restoring the configuration (using the pimdataexporter again), Akonadi will have to re-fetch all data again into its cache. This can cause configuration that points to actual mail folders or calendars to get broken and accidentally point to another folder.

After restoring configuration and syncing all data, it's vital to manually check all folder configuration, especially in KMail identities and make sure the folders are configured properly.

Perguntas frequentes

Onde os meus dados estão agora?

Your data are safely stored outside of Akonadi control on your disk (e.g. local maildir folder or iCal calendar), or on a remote server (in case of e.g. email over IMAP or events from a CalDAV calendar). Akonadi will optionally store a copy of this data in its database to allow applications to quickly retrieve and display them. Any modifications done to data in the Akonadi database will be synced to the actual storage. The main advantage of using the database as a cache is that remote PIM data are available even when you are offline, and you can still interact with them (e.g. mark emails as read or move them, create new events, reschedule existing meetings etc.) and all the changes will get synced automatically once you connect to the internet again.

Thus, deleting the Akonadi database will not cause any data to be lost (as long as all pending changes are synced).

Como atualizar a minha base dado PostgreSQL?

Depois de atualizar o seu server PostgreSQL para uma nova versão, algumas vezes você vai ter que converter a sua base de dados Akonadi para usar com essa nova versão. Instruções podem ser encrontradas nessa página.

Problemas durante a migração

O item Akonadi do Glossário tem uma breve explicação do seu propósito e outros links úteis. Esta página explica como o Akonadi e o KAddressBook funcionam juntos.

How do I switch from MySQL/PostgreSQL to SQLite?

Since Akonadi 6 akonadi-db-migrator is included in akonadi that allows you to switch the database backend. Where for previous versions this involved deleting and recreating the database a migration is now properly supported by akonadi.

The tool needs to be called with the parameter --newengine to chose to which backend it should to: {{{

 --newengine <ENGINE>       The new DB engine to use. Possible values are 
                            "sqlite", "mysql" and "postgres"

}}}

For example: {{{ akonadi-db-migrator --newengine sqlite }}}