Description of problem: Using "yum", I loaded Evolution. Then, I removed theprevious "evolution" directories from ~/.cache/, ~/.config/, and ~/.local/. I did this to start the use of Evolution from scratch. Then, I fired up Evolution from the GUI, and told it to IMAP my gmail.com account in its entirety. I did this to backup my gmail.com account. I hit the send/receive button, and Evolution appeared to be starting to download my gmail.com account. So, I went to bed. When I awoke, this appeared to be still going on 10 hours later, and there were all sorts of error writing journal messages in all of my text windows. When I tried to deal with Evolution, it crashed. I still could not "cat" a text file. So, I attempted to reboot the system. This went well until I tried to log in, but then I got some error message saying something could not be logged. This happened repeatedly when I tried to log in. So, I powered down the machine, and finally got total control back. Version-Release number of selected component: mate-session-manager-1.5.1-1.fc18 Additional info: backtrace_rating: 4 cmdline: mate-session crash_function: gvdb_table_lookup executable: /usr/bin/mate-session kernel: 3.8.8-202.fc18.x86_64 uid: 500 ureports_counter: 1 xsession_errors: mate-session[1423]: WARNING: Could not launch application 'dropbox.desktop': Unable to start application: Failed to execute child process "dropbox" (No such file or directory) Truncated backtrace: Thread no. 1 (10 frames) #0 gvdb_table_lookup at gvdb-reader.c:340 #1 gvdb_table_get_value at gvdb-reader.c:653 #2 dconf_engine_read at dconf-engine.c:525 #3 g_settings_backend_read at gsettingsbackend.c:733 #4 g_settings_read_from_backend at gsettings.c:1040 #5 g_settings_get_value at gsettings.c:1080 #6 g_settings_get_int at gsettings.c:1615 #7 load_idle_delay_from_gsettings at gsm-manager.c:2306 #8 gsm_manager_init at gsm-manager.c:2400 #9 g_type_create_instance at gtype.c:1890
Created attachment 742445 [details] File: backtrace
Created attachment 742446 [details] File: cgroup
Created attachment 742447 [details] File: core_backtrace
Created attachment 742448 [details] File: dso_list
Created attachment 742449 [details] File: environ
Created attachment 742450 [details] File: limits
Created attachment 742451 [details] File: maps
Created attachment 742452 [details] File: open_fds
Created attachment 742453 [details] File: proc_pid_status
Created attachment 742454 [details] File: var_log_messages
The .config dir stores all X settings. Of course it crashed... .config gets created on your first login.
Try the same thing again with MSM 1.5.2 but please logout and log back in after you delete .config
mate-session-manager-1.5.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-session-manager-1.5.2-1.fc18
If anything you will get the same results and this is a dconf or evolution bug. Profile Specification dconf stores its profiles in text files. $DCONF_PROFILE can specify a relative path to the file from "/etc/dconf/profile/", or an absolute path (such as in a user's home directory). For example, the 'user' profile is stored in "/etc/dconf/profile/user". The profile name can only use alphanumeric characters or '_'. A profile file might look like the following: user-db:user system-db:local system-db:site Each line in a profile specifies one dconf database. The first line indicates the database used to write changes, and the remaining lines indicate read-only databases. (The first line should specify a user-db, so that users can actually make configuration changes.) A "user-db" line specifies a user database. These databases are found in ${XDG_CONFIG_HOME}/dconf/ (typically ~/.config/dconf/). The name of the file to open in that directory is exactly as it is written in the profile. In our example, "~/.config/dconf/user" would be opened. This file is expected to be in the binary dconf (GVDB) database format. Note that XDG_CONFIG_HOME cannot be set/modified per terminal or session (E.G. export XDG_CONFIG_HOME=...), because then the writer and reader would be working on different DBs (the writer is started by DBus and cannot see that variable).
mate-session-manager-1.5.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.