Please do the following:

yum update --enablerepo=updates-testing

If you get noting please paste output of:

rpm -qa |grep cinnamon
rpm -qa |grep nemo
rpm -qa |grep muffin

The crash is related to my ~/.config/dconf/user file, which is a preexisting file, from before the upgrade to F19.

I moved the filed away, and now I'm able to start cinnamon.
I wonder which settings I lost because of this...

Also, I installed debug information, so I can give you the full stack with variables:

#0  g_logv (log_domain=0x7fcdc31bda98 "GLib-GIO", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7fff764715e8) at gmessages.c:981
#1  0x00007fcdc1bba092 in g_log (log_domain=log_domain@entry=0x7fcdc31bda98 "GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7fcdc31d8840 "Settings schema '%s' does not contain a key named '%s'")
    at gmessages.c:1010
#2  0x00007fcdc3179734 in g_settings_schema_get_value (schema=schema@entry=0x3dbe300, key=key@entry=0x3ea9360 "idle-dim-ac") at gsettingsschema.c:640
#3  0x00007fcdc317990d in g_settings_schema_key_init (key=key@entry=0x7fff76471750, schema=0x3dbe300, name=name@entry=0x3ea9360 "idle-dim-ac") at gsettingsschema.c:751
#4  0x00007fcdc317cc9b in g_settings_get_value (settings=0x3dce720, key=0x3ea9360 "idle-dim-ac") at gsettings.c:1079
#5  0x00007fcdc317d8db in g_settings_get_boolean (settings=<optimized out>, key=<optimized out>) at gsettings.c:1785
#6  0x00007fcdc0722cfc in ffi_call_unix64 () from /lib64/libffi.so.6
#7  0x00007fcdc072262c in ffi_call () from /lib64/libffi.so.6
#8  0x00007fcdc9e88b37 in gjs_invoke_c_function (context=context@entry=0x2199ce0, function=function@entry=0x257b520, obj=obj@entry=0x7fcd98ee7828, js_argc=js_argc@entry=1, js_argv=js_argv@entry=0x7fcda63fd648, 
    js_rval=js_rval@entry=0x7fff76471c78) at gi/function.c:893
#9  0x00007fcdc9e8a054 in function_call (context=0x2199ce0, js_argc=1, vp=0x7fcda63fd638) at gi/function.c:1202
#10 0x00007fcdc99cfd99 in CallJSNative (vp=0x7fcda63fd638, argc=1, native=<optimized out>, cx=0x2199ce0) at jscntxtinlines.h:701
#11 js::Invoke (cx=cx@entry=0x2199ce0, argsRef=..., flags=flags@entry=0) at jsinterp.cpp:696
#12 0x00007fcdc99b923a in js::Interpret (cx=cx@entry=0x2199ce0, entryFrame=entryFrame@entry=0x7fcda63fd048, inlineCallCount=10, inlineCallCount@entry=0, interpMode=interpMode@entry=JSINTERP_NORMAL) at jsinterp.cpp:4810
#13 0x00007fcdc99cda56 in js::RunScript (cx=cx@entry=0x2199ce0, script=script@entry=0x22d2aa0, fp=0x7fcda63fd048) at jsinterp.cpp:653
#14 0x00007fcdc99ce8e8 in js::Execute (cx=0x2199ce0, chain=<optimized out>, script=0x22d2aa0, prev=<optimized out>, flags=<optimized out>, result=0x7fff76472270) at jsinterp.cpp:1028
#15 0x00007fcdc9939a85 in EvaluateUCScriptForPrincipalsCommon (cx=0x2199ce0, obj=0x7fcdac203048, principals=<optimized out>, chars=<optimized out>, length=<optimized out>, filename=<optimized out>, lineno=lineno@entry=1, 
    rval=rval@entry=0x7fff76472270, compileVersion=JSVERSION_1_8) at jsapi.cpp:5031
#16 0x00007fcdc9939c27 in JS_EvaluateUCScriptForPrincipals (cx=<optimized out>, obj=<optimized out>, principals=<optimized out>, chars=<optimized out>, length=<optimized out>, filename=<optimized out>, lineno=1, 
    rval=0x7fff76472270) at jsapi.cpp:5058
#17 0x00007fcdc9939d31 in JS_EvaluateScriptForPrincipals (cx=0x2199ce0, obj=0x7fcdac203048, principals=principals@entry=0x0, bytes=<optimized out>, nbytes=nbytes@entry=54, filename=filename@entry=0x7fcdca3e9399 "<main>", 
    lineno=lineno@entry=1, rval=rval@entry=0x7fff76472270) at jsapi.cpp:5081
#18 0x00007fcdc9939ed2 in JS_EvaluateScript (cx=<optimized out>, obj=<optimized out>, bytes=<optimized out>, nbytes=nbytes@entry=54, filename=filename@entry=0x7fcdca3e9399 "<main>", lineno=lineno@entry=1, 
    rval=rval@entry=0x7fff76472270) at jsapi.cpp:5101
#19 0x00007fcdc9e78e91 in gjs_context_eval (js_context=0x7fcda0002370, script=<optimized out>, script@entry=0x7fcdca3e9400 "imports.ui.environment.init();imports.ui.main.start();", script_len=54, script_len@entry=-1, 
    filename=filename@entry=0x7fcdca3e9399 "<main>", exit_status_p=exit_status_p@entry=0x7fff764722c4, error=error@entry=0x7fff764722c8) at gjs/context.c:1013
#20 0x00007fcdca39a66f in gnome_cinnamon_plugin_start (plugin=<optimized out>) at cinnamon-plugin.c:193
#21 0x00007fcdca0ddb50 in meta_plugin_manager_initialize (plugin_mgr=0xb28100) at compositor/meta-plugin-manager.c:129
#22 0x00007fcdca0db1b7 in meta_compositor_manage_screen (compositor=<optimized out>, screen=0xb25200) at compositor/compositor.c:598
#23 0x00007fcdca0edc84 in enable_compositor (composite_windows=0, display=0x2227e10) at core/display.c:405
#24 meta_display_open () at core/display.c:849
#25 0x00007fcdca0fb2dd in meta_run () at core/main.c:567
#26 0x0000000000401a98 in main (argc=1, argv=0x7fff76472fb8) at main.c:324

> yum update --enablerepo=updates-testing

Nothing.


> If you get noting please paste output of:

[root@lapkaie ~]# rpm -qa |grep cinnamon
cinnamon-1.8.3-1.fc19.x86_64
cinnamon-debuginfo-1.8.3-1.fc19.x86_64
[root@lapkaie ~]# rpm -qa |grep nemo
nemo-1.8.2-1.fc19.x86_64
nemo-extensions-1.8.2-1.fc19.x86_64
[root@lapkaie ~]# rpm -qa |grep muffin
muffin-debuginfo-1.8.2-1.fc19.x86_64
muffin-1.8.2-1.fc19.x86_64

(In reply to Kai Engert (:kaie) from comment #2)
> The crash is related to my ~/.config/dconf/user file, which is a preexisting
> file, from before the upgrade to F19.
> 
> I moved the filed away, and now I'm able to start cinnamon.
> I wonder which settings I lost because of this...
> 

Any settings stored in dconf (most user based customizations (themes, etc.)

> Also, I installed debug information, so I can give you the full stack with
> variables:

We know what broke cinnamon, but we appreciate the information and will see if linux mint upstream can do anything with it.

The root cause of this issue is Cinnamon code not being fully Gnome 3.8.x compatible.

Indeed, I lost a lot of configuration settings.

My deja-dup backup configuration had a lot of tweaking, it's unfortunate I lost it.

So to summarize:

- affected are users that had certain (at least the brightness) applets
  enabled in F18
- those users, when upgrading to F19, will be unable to login to
  cinnamon, because cinnamon crashes

We need a way for those people to recover, or even prepare.

My initial fix was to remove the dconf storage. But that file actually contained a lot of configuration, and I was unwilling to lose it.

I came up with the following solution, that allows to keep most of the old configuration, and will simply reset the list of enabled cinnamon applets.

The following commands can be executed from within a console window, even if the user is unable to start a graphical environment. The user should log in to the console using the affected user account, and execute the following commands:

$ export `dbus-launch`
  # comment: above command will run dbus and make environment variables
  #          available, that will allow the following commands to work.
$ dconf reset /org/cinnamon/enabled-applets
$ dconf reset /org/cinnamon/next-applet-id

The above commands should succeed without errors.
Afterwards, it should be possible to login with cinnamon.

(In reply to Kai Engert (:kaie) from comment #6)
> So to summarize:
> 
> - affected are users that had certain (at least the brightness) applets
>   enabled in F18
> - those users, when upgrading to F19, will be unable to login to
>   cinnamon, because cinnamon crashes
> 
> We need a way for those people to recover, or even prepare.
> 
> My initial fix was to remove the dconf storage. But that file actually
> contained a lot of configuration, and I was unwilling to lose it.
> 
> I came up with the following solution, that allows to keep most of the old
> configuration, and will simply reset the list of enabled cinnamon applets.
> 
> The following commands can be executed from within a console window, even if
> the user is unable to start a graphical environment. The user should log in
> to the console using the affected user account, and execute the following
> commands:
> 
> $ export `dbus-launch`
>   # comment: above command will run dbus and make environment variables
>   #          available, that will allow the following commands to work.
> $ dconf reset /org/cinnamon/enabled-applets
> $ dconf reset /org/cinnamon/next-applet-id
> 
> The above commands should succeed without errors.
> Afterwards, it should be possible to login with cinnamon.

does this scratch build fix your brightness applet? https://koji.fedoraproject.org/koji/taskinfo?taskID=5443512

(In reply to leigh scott from comment #7)
> 
> does this scratch build fix your brightness applet?
> https://koji.fedoraproject.org/koji/taskinfo?taskID=5443512

Yes, it does, great work!
I could add the applet, and it correctly adjusts brightness.

cinnamon-1.8.6-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/cinnamon-1.8.6-1.fc19

Package cinnamon-1.8.6-2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cinnamon-1.8.6-2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9735/cinnamon-1.8.6-2.fc19
then log in and leave karma (feedback).

cinnamon-1.9.1-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/cinnamon-1.9.1-1.fc19

cinnamon-1.9.1-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Sounds like this doesn't need commonbugs any more.