From c3a65b2fc53d03b83401c641f6977d5e4edd10c0 Mon Sep 17 00:00:00 2001 From: Ettore Perazzoli Date: Wed, 23 May 2001 12:08:44 +0000 Subject: Re-indented the FAQ document. svn path=/trunk/; revision=9944 --- doc/C/evolution-faq.sgml | 859 +++++++++++++++++++++++------------------------ doc/ChangeLog | 4 + 2 files changed, 425 insertions(+), 438 deletions(-) (limited to 'doc') diff --git a/doc/C/evolution-faq.sgml b/doc/C/evolution-faq.sgml index 62621ba798..84f71a89fa 100644 --- a/doc/C/evolution-faq.sgml +++ b/doc/C/evolution-faq.sgml @@ -1,32 +1,32 @@ - + Frequently Asked Questions About Ximian Evolution - - Here are some frequently asked questions about the - Evolution groupware suite from - Ximian. - - - - - - - Getting and Compiling Evolution - + + Here are some frequently asked questions about the + Evolution groupware suite from + Ximian. + + + + + + + Getting and Compiling Evolution + - Where can I get the latest Evolution release? + Where can I get the latest Evolution release? - There are two ways to install the latest Evolution - release: - + There are two ways to install the latest Evolution + release: + If you have Ximian GNOME installed, you can start @@ -40,18 +40,18 @@ - If you want to compile from source, you can - download the latest official Evolution tarball - from: + If you want to compile from source, you can + download the latest official Evolution tarball + from: - ftp://ftp.gnome.org/pub/GNOME/unstable/sources/evolution + ftp://ftp.gnome.org/pub/GNOME/unstable/sources/evolution - + @@ -61,15 +61,15 @@ - - Yes, if you have Ximian GNOME installed. Just run Red - Carpet and subscribe to the Evolution Snapshot channel. - - - - You can check the status of snapshots at http://primates.ximian.com/~snapshot. - + + Yes, if you have Ximian GNOME installed. Just run Red + Carpet and subscribe to the Evolution Snapshot channel. + + + + You can check the status of snapshots at http://primates.ximian.com/~snapshot. + @@ -95,34 +95,34 @@ If you already have GNOME CVS access, + url="http://cvs.gnome.org">GNOME CVS access, simply check out the following modules: evolution, gtkhtml, gal. - - - If you don't have a CVS account, you can use anoncvs - instead. Bear in mind that anoncvs is only synchronized once - a day, and code received from anoncvs may not be latest - version available. - - - - Before using the anoncvs server, you have to log into it. - This only needs to be done once. Use this command: - - - -cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome login - - - - Then you can retrieve the modules needed to compile Evolution - using the following command: - - - -cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co evolution gtkhtml gal - + + + If you don't have a CVS account, you can use anoncvs + instead. Bear in mind that anoncvs is only synchronized once + a day, and code received from anoncvs may not be latest + version available. + + + + Before using the anoncvs server, you have to log into it. + This only needs to be done once. Use this command: + + + + cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome login + + + + Then you can retrieve the modules needed to compile Evolution + using the following command: + + + + cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co evolution gtkhtml gal + @@ -130,47 +130,47 @@ cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co evolution gtkhtml How should I compile Evolution avoiding conflicts with my existing GNOME installation? - + - - The best way is to install Evolution into a separate prefix. - In order to specify a non-default installation prefix, you - can pass the --prefix option to - configure or - autogen.sh. For example: - - - -cd /cvs/evolution -./autogen.sh --prefix=/opt/gnome - - - - If you install Evolution and the Evolution libraries in a - non-standard prefix, make sure you set the appropriate - environment variables in the startup script for Evolution: - - - -export PATH=/opt/gnome:$PATH -export GNOME_PATH=/opt/gnome:/usr - - - - You may also need to add $prefix/lib - (e.g. /opt/gnome/lib) to your - /etc/ld.so.conf. Of course, this will - not work for systems which do not use ld.so.conf, such as - HP-UX. - + + The best way is to install Evolution into a separate prefix. + In order to specify a non-default installation prefix, you + can pass the --prefix option to + configure or + autogen.sh. For example: + + + + cd /cvs/evolution + ./autogen.sh --prefix=/opt/gnome + + + + If you install Evolution and the Evolution libraries in a + non-standard prefix, make sure you set the appropriate + environment variables in the startup script for Evolution: + + + + export PATH=/opt/gnome:$PATH + export GNOME_PATH=/opt/gnome:/usr + + + + You may also need to add $prefix/lib + (e.g. /opt/gnome/lib) to your + /etc/ld.so.conf. Of course, this will + not work for systems which do not use ld.so.conf, such as + HP-UX. + I get make: *** No rule to make target - `all-no-@BUILD_INCLUDED_LIBINTL@' + `all-no-@BUILD_INCLUDED_LIBINTL@' @@ -183,61 +183,61 @@ export GNOME_PATH=/opt/gnome:/usr - + - - Troubleshooting + + Troubleshooting I get Cannot initialize the Evolution - shell. - + shell. + Check that: - - - - oafd is listen in your PATH - environment variable. - - - - - - GNOME_Evolution_Shell.oaf and - the other       - GNOME_Evolution_*.oaf files are - readable and installed in - $prefix/share/oaf, where - $prefix is one of the prefixes - listed in GNOME_PATH or - OAF_INFO_PATH.  (These variables are - supposed to contain $PATH-like colon-separated lists of - paths.  If the installation prefix for Evolution is - different from that). Run `oaf-slay' once before running - `evolution' again if you change $GNOME_PATH or - $OAF_INFO_PATH. - - - - - - evolution, - evolution-mail and the other - evolution-* executables are in your - $PATH. - - - + + + + oafd is listen in your PATH + environment variable. + + + + + + GNOME_Evolution_Shell.oaf and + the other       + GNOME_Evolution_*.oaf files are + readable and installed in + $prefix/share/oaf, where + $prefix is one of the prefixes + listed in GNOME_PATH or + OAF_INFO_PATH.  (These variables are + supposed to contain $PATH-like colon-separated lists of + paths.  If the installation prefix for Evolution is + different from that). Run `oaf-slay' once before running + `evolution' again if you change $GNOME_PATH or + $OAF_INFO_PATH. + + + + + + evolution, + evolution-mail and the other + evolution-* executables are in your + $PATH. + + + - + @@ -246,107 +246,107 @@ export GNOME_PATH=/opt/gnome:/usr - This actually means that Evolution cannot activate the HTML - editor component from GtkHTML. The comments in the previous - answer still apply; also make sure that - gnome-gtkhtml-editor is in your - PATH. - + This actually means that Evolution cannot activate the HTML + editor component from GtkHTML. The comments in the previous + answer still apply; also make sure that + gnome-gtkhtml-editor is in your + PATH. + - - - - - I updated my Evolution, but my addressbook contacts are no - longer there, what should I do? - + + + + + I updated my Evolution, but my addressbook contacts are no + longer there, what should I do? + - - Evolution uses the libdb library to - handle the addressbook database. Two versions of - libdb can be used with Evolution: version - 1.88 and version 2. - - - - Unfortunately, an Evolution executable that is linked against - a certain version of libdb will only be - able to read addressbook files written by another Evolution - executable that is linked with the same version of the - library. If your addressbook is not readable by Evolution - anymore, it probably means that you used to have Evolution - linked with a certain version of libdb, - but now it gets linked to a different version. - - - - Because of the way libdb is designed, it - is not easy for Evolution to automatically do the conversion - between the two formats. But, if your Evolution used to be - linked against version 1.85 and now is linked to version 2, - there is a very simple way to convert the database and recover - your data. - - - - - - - First of all, check the format of the database using the - file command: - - - + + Evolution uses the libdb library to + handle the addressbook database. Two versions of + libdb can be used with Evolution: version + 1.88 and version 2. + + + + Unfortunately, an Evolution executable that is linked against + a certain version of libdb will only be + able to read addressbook files written by another Evolution + executable that is linked with the same version of the + library. If your addressbook is not readable by Evolution + anymore, it probably means that you used to have Evolution + linked with a certain version of libdb, + but now it gets linked to a different version. + + + + Because of the way libdb is designed, it + is not easy for Evolution to automatically do the conversion + between the two formats. But, if your Evolution used to be + linked against version 1.85 and now is linked to version 2, + there is a very simple way to convert the database and recover + your data. + + + + + + + First of all, check the format of the database using the + file command: + + + file ~/evolution/local/Contacts/addressbook.db - - - - You want version 1.85 there. If your version is 2, then - your current Evolution is probably linked against - version 1.85 and you cannot convert the database to the - old format. To do that, follow these instructions: - - - - - - Quit Evolution. - - - - - - Make a copy of the addressbook database for backup - purposes. - - - -cd ~/evolution/local/Contacts -cp addressbook.db addressbook.db.backup - - - - - - Convert the contacts to the new format using - db_dump185 and - db_load: - - - -db_dump185 ~/evolution/local/Contacts/addressbook.db.backup | db_load ~/evolution/local/Contacts/addressbook.db - - - - - - Restart Evolution. - - - - + + + + You want version 1.85 there. If your version is 2, then + your current Evolution is probably linked against + version 1.85 and you cannot convert the database to the + old format. To do that, follow these instructions: + + + + + + Quit Evolution. + + + + + + Make a copy of the addressbook database for backup + purposes. + + + + cd ~/evolution/local/Contacts + cp addressbook.db addressbook.db.backup + + + + + + Convert the contacts to the new format using + db_dump185 and + db_load: + + + + db_dump185 ~/evolution/local/Contacts/addressbook.db.backup | db_load ~/evolution/local/Contacts/addressbook.db + + + + + + Restart Evolution. + + + + @@ -365,8 +365,8 @@ db_dump185 ~/evolution/local/Contacts/addressbook.db.backup | db_load ~/evolutio -chmod 1777 /var/spool/mail - + chmod 1777 /var/spool/mail + Yes, we know this is a problem. It will be fixed eventually. @@ -375,11 +375,11 @@ chmod 1777 /var/spool/mail - - - Evolution crashes reporting that it couldn't allocate N - billion bytes; how do I fix this? - + + + Evolution crashes reporting that it couldn't allocate N + billion bytes; how do I fix this? + @@ -396,32 +396,32 @@ chmod 1777 /var/spool/mail applies to GtkHTML upgrades; after upgrading and installing a newer GtkHTML, always re-compile and re-install Evolution against it. - + - - - What is killev and why do I need to use it? - + + + What is killev and why do I need to use it? + - - Evolution is actually made up of several components that run - as separate processes. Evolution's shell is not very good - at cleaning up stale processes, so it is possible that - sometimes already-running components cause unexpected and/or - broken behavior. - - - - It's always a good idea to run killev - after a crash in Evolution, especially if the Evolution - shell itself crashed. (If a component crashes instead, you - should try to exit the shell cleanly first, so you give a - chance to the other components to clean things up properly.) - + + Evolution is actually made up of several components that run + as separate processes. Evolution's shell is not very good + at cleaning up stale processes, so it is possible that + sometimes already-running components cause unexpected and/or + broken behavior. + + + + It's always a good idea to run killev + after a crash in Evolution, especially if the Evolution + shell itself crashed. (If a component crashes instead, you + should try to exit the shell cleanly first, so you give a + chance to the other components to clean things up properly.) + @@ -438,32 +438,32 @@ chmod 1777 /var/spool/mail GNOME Desktop to activate components. It will kill the object activation daemon (oafd) as well as all the active components on the system. - - - - Normally, you shouldn't need to run - oaf-slay, unless oafd - gets stuck or confused. For example, it might help in case - Evolution cannot activate components. - - - - Using oaf-slay - oaf-slay is quite drastic and can cause - problems with other programs that use oaf, especially with - Nautilus. To avoid problems, do - not run oaf-slay while you are in GNOME. - + + + + Normally, you shouldn't need to run + oaf-slay, unless oafd + gets stuck or confused. For example, it might help in case + Evolution cannot activate components. + + + + Using oaf-slay + oaf-slay is quite drastic and can cause + problems with other programs that use oaf, especially with + Nautilus. To avoid problems, do + not run oaf-slay while you are in GNOME. + - + - + Questions about Bugs and Debugging - - Find a bug? Here's how to help us fix it! - + + Find a bug? Here's how to help us fix it! + @@ -476,16 +476,16 @@ chmod 1777 /var/spool/mail You should report bugs about Evolution into the Ximian bug reporting system (Bugzilla), located at http://bugzilla.ximian.com. - - + url="http://bugzilla.ximian.com">http://bugzilla.ximian.com. + + Please use the query function to check if a bug has been submitted already before submitting it. - + @@ -493,11 +493,11 @@ chmod 1777 /var/spool/mail - - Not yet. The Ximian bug tracker does not yet have an - email-based interface, so Bug Buddy cannot talk to it. This - will be fixed eventually. - + + Not yet. The Ximian bug tracker does not yet have an + email-based interface, so Bug Buddy cannot talk to it. This + will be fixed eventually. + @@ -508,114 +508,114 @@ chmod 1777 /var/spool/mail - - A stack trace is a list of the chain of function calls that - lead to some point in the program. Typically, you want to - get a stack trace when Evolution crashes or hangs and you - want to try to figure out where in the code that happened - and why. For this reason, stack traces are extremely - useful for the Evolution developers, so it's important that - you learn how to get them, and include them in crash - reports. Once we have bug-buddy working - with our bug database, it will be much easier to do - this. Until then, here's how: - - - - First of all, in order to get a stack trace, your executable - (and possibly the libraries) must be compiled with debugging - symbols. Debugging symbols are created by default if you - compile from CVS, and are included in the snapshot builds. - If you decide to compile by yourself with some custom CFLAGS - value, make sure -g is included in them. - - - - Finally, you must put the component that crashes through - gdb. Make sure all the components are - dead (exit Evolution and killev), then - run the following command: - - - -gdb name-of-component - - - - Then, at the gdb prompt, type r (for - "run") and wait a few seconds to make sure the component has - registered with the name service. Then start Evolution - normally from a different terminal. - - - - Then, reproduce the crash, and go back to the terminal where - you ran gdb. If the component crashed, - you should have a prompt there; otherwise, just hit - - Control - C - . - At the prompt, type: - - - -info threads - - - - This will give you a list of the current running threads, - e.g. - - - -(gdb) info threads - 8 Thread 6151 (LWP 14908) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 7 Thread 5126 (LWP 14907) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 6 Thread 4101 (LWP 1007) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 5 Thread 3076 (LWP 1006) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 4 Thread 2051 (LWP 1005) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 3 Thread 1026 (LWP 1004) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 2 Thread 2049 (LWP 1003) 0x40a10d90 in poll () from /lib/libc.so.6 - 1 Thread 1024 (LWP 995) 0x40a10d90 in poll () from /lib/libc.so.6 - - - - (Notice that, normally, only - evolution-mail will have more than one - thread.) - - - - Now, for each of the thread listed, type the following - commands: - - - -thread N -bt - - - - Where `N' is the thread number. (In this example, you would - have to do it with N as 1, 2, 3... 8.) Then cut and paste - all the output into some text file, and quit - gdb by typing - quit. - - - - You can also get a stack trace from a running component or a - component that has just crashed. Just start - gdb normally and, instead of using the - r command, use - attach to attach to the running - process: - - - -attach PID - + + A stack trace is a list of the chain of function calls that + lead to some point in the program. Typically, you want to + get a stack trace when Evolution crashes or hangs and you + want to try to figure out where in the code that happened + and why. For this reason, stack traces are extremely + useful for the Evolution developers, so it's important that + you learn how to get them, and include them in crash + reports. Once we have bug-buddy working + with our bug database, it will be much easier to do + this. Until then, here's how: + + + + First of all, in order to get a stack trace, your executable + (and possibly the libraries) must be compiled with debugging + symbols. Debugging symbols are created by default if you + compile from CVS, and are included in the snapshot builds. + If you decide to compile by yourself with some custom CFLAGS + value, make sure -g is included in them. + + + + Finally, you must put the component that crashes through + gdb. Make sure all the components are + dead (exit Evolution and killev), then + run the following command: + + + + gdb name-of-component + + + + Then, at the gdb prompt, type r (for + "run") and wait a few seconds to make sure the component has + registered with the name service. Then start Evolution + normally from a different terminal. + + + + Then, reproduce the crash, and go back to the terminal where + you ran gdb. If the component crashed, + you should have a prompt there; otherwise, just hit + + Control + C + . + At the prompt, type: + + + + info threads + + + + This will give you a list of the current running threads, + e.g. + + + + (gdb) info threads + 8 Thread 6151 (LWP 14908) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 7 Thread 5126 (LWP 14907) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 6 Thread 4101 (LWP 1007) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 5 Thread 3076 (LWP 1006) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 4 Thread 2051 (LWP 1005) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 3 Thread 1026 (LWP 1004) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 2 Thread 2049 (LWP 1003) 0x40a10d90 in poll () from /lib/libc.so.6 + 1 Thread 1024 (LWP 995) 0x40a10d90 in poll () from /lib/libc.so.6 + + + + (Notice that, normally, only + evolution-mail will have more than one + thread.) + + + + Now, for each of the thread listed, type the following + commands: + + + + thread N + bt + + + + Where `N' is the thread number. (In this example, you would + have to do it with N as 1, 2, 3... 8.) Then cut and paste + all the output into some text file, and quit + gdb by typing + quit. + + + + You can also get a stack trace from a running component or a + component that has just crashed. Just start + gdb normally and, instead of using the + r command, use + attach to attach to the running + process: + + + + attach PID + Where PID is the PID of the @@ -630,10 +630,10 @@ attach PID Features - - Following is a list of questions about the features in - Evolution. - + + Following is a list of questions about the features in + Evolution. + @@ -660,7 +660,7 @@ attach PID -rm -rf ~/evolution/local/Inbox/subfolders/Foo + rm -rf ~/evolution/local/Inbox/subfolders/Foo @@ -668,7 +668,7 @@ rm -rf ~/evolution/local/Inbox/subfolders/Foo - + @@ -688,7 +688,7 @@ rm -rf ~/evolution/local/Inbox/subfolders/Foo -cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/Bar + cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/Bar @@ -699,11 +699,11 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/ - - - Can I read mail from a mailbox file created by some other - application (e.g. Mutt) without importing mail from it? - + + + Can I read mail from a mailbox file created by some other + application (e.g. Mutt) without importing mail from it? + @@ -759,7 +759,7 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/ for this to work you need the gnome-spell component, which is not shipped with Ximian GNOME yet. - + If you are brave enough, you can check out module @@ -807,14 +807,14 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/ GNOME Control Center, go to the "HTML Viewer" configuration page, which is under the "Document Handlers" category. - + How do I import my Outlook .pst files into Evolution? - + @@ -824,7 +824,7 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/ convert them into the mbox format, which can then be imported by Evolution. - + To start importing your Outlook mail to Evolution, run Mozilla Mail on Windows and select the @@ -833,21 +833,21 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/ Outlook. Once Mozilla has imported all your mail, reboot your computer into Linux. - + Mount your Windows partition in Linux and run Evolution to begin importing your mail. Select FileImport - File... to start importing. Set + File... to start importing. Set the file type to MBox (mbox) and click on Browse to select the mail you want to import. - + If you are the only user on Windows, the mail files will be stored in /mnt/c/windows/Application - Data/Mozilla/Profiles/default/XXXX/Mail/imported.mail/ + Data/Mozilla/Profiles/default/XXXX/Mail/imported.mail/ where /mnt/c/ is your windows partition mount point and XXXX is some collection of numbers and digits ending in .slt. @@ -857,14 +857,14 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/ If there is more than one user, the file will be in /mnt/c/windows/Profiles/USERNAME/XXXX/Mail/imported.mail/ where USERNAME is your Windows username. - + For each mail folder in Outlook, Mozilla will convert the folder into one mbox file. To import all your mail, import all the files without a .msf extension. - + @@ -876,31 +876,14 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/ - Mozilla on Windows accesses the .pst - files through the MAPI.DLL, which is - only avaliable on Windows. MAPI.DLL - is the only way to access .pst files - and Evolution cannot use this DLL in Linux. + Mozilla on Windows accesses the .pst + files through the MAPI.DLL, which is + only avaliable on Windows. MAPI.DLL + is the only way to access .pst files + and Evolution cannot use this DLL in Linux. - - - - - - - - - - - - - - - - - - - + + diff --git a/doc/ChangeLog b/doc/ChangeLog index 6bde52e51c..65402a993e 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +2001-05-23 Ettore Perazzoli + + * C/evolution-faq.sgml: Re-indented. + 2001-05-18 Duncan Mak * C/evolution-faq.sgml: Added two questions about importing Outlook (text from Iain). -- cgit v1.2.3