Redmine

Yesterday I upgraded from 1.3.X on my gentoo machine to 1.4.1. Everything works except for one thing, as soon as I want to open the settings of a project I get an 500 internal error. Webrick gives me the following output:

Processing ProjectsController#settings (for 89.206.103.147 at 2012-05-10 11:37:57) [GET]
  Parameters: {"action"=>"settings", "id"=>"policelight-ringtoni", "controller"=>"projects"}
Rendering template within layouts/base
Rendering projects/settings

ActionView::TemplateError (Missing template projects/settings/_repository.erb in view path vendor/plugins/redmine_gsc_plantillas/app/views:vendor/plugins/redmine_knowledgebase/app/views:vendor/plugins/redmine_startpage/app/views:vendor/plugins/redmine_wiki_extensions/app/views:app/views) on line #24 of app/views/common/_tabs.html.erb:
21: </script>
22: 
23: <% tabs.each do |tab| -%>
24:   <%= content_tag('div', render(:partial => tab[:partial], :locals => {:tab => tab} ),
25:                        :id => "tab-content-#{tab[:name]}",
26:                        :style => (tab[:name] != selected_tab ? 'display:none' : nil),
27:                        :class => 'tab-content') %>

    app/views/common/_tabs.html.erb:24
    app/views/common/_tabs.html.erb:23:in `each'
    app/views/common/_tabs.html.erb:23
    app/helpers/application_helper.rb:231:in `render_tabs'
    app/views/projects/settings.html.erb:3
    /usr/lib64/ruby/1.8/webrick/httpserver.rb:104:in `service'
    /usr/lib64/ruby/1.8/webrick/httpserver.rb:65:in `run'
    /usr/lib64/ruby/1.8/webrick/server.rb:173:in `start_thread'
    /usr/lib64/ruby/1.8/webrick/server.rb:162:in `start'
    /usr/lib64/ruby/1.8/webrick/server.rb:162:in `start_thread'
    /usr/lib64/ruby/1.8/webrick/server.rb:95:in `start'
    /usr/lib64/ruby/1.8/webrick/server.rb:92:in `each'
    /usr/lib64/ruby/1.8/webrick/server.rb:92:in `start'
    /usr/lib64/ruby/1.8/webrick/server.rb:23:in `start'
    /usr/lib64/ruby/1.8/webrick/server.rb:82:in `start'

Rendering /var/lib/redmine/public/500.html (500 Internal Server Error)

Since it seemed similar to #10827 I applied that patch there, but with no success...