trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: July 2012

Re: [trinity-devel] bug (kmenu->Settings->Control Center) doesn't work

From: Darrell Anderson <humanreadable@...>
Date: Tue, 17 Jul 2012 17:39:10 -0700 (PDT)
> Yes, this is where the menus have always gone. They are
> totally FUBAR. All apps are dumped in 'Lost & Found'. There are menu folders
> that are moved around in the menu tree. 'Terminal Applications' is now under
> 'Internet'?? It used to be under System. Something must have 'blown up' regarding the
> menu. I've never seen such a mess. Now the questions becomes how do we figure out
> what happened?
> 
> Can I just delete all the menus and have them regenerated
> somehow?

We need to figure out why your tdelibs package does not include the menus from the sources. Or why they did not install correctly. In GIT the menus are located in tdelibs/kded. There are only two menus there we are concerned about. In a pinch you can just copy those. You should not need to restart TDE, but you will need to use the menu once or twice to force TDE to update the menu on its own.

> >> o  taskbar -> Quicklaunch is now added to
> panel with 'Malformed URL' for
> >> 'Home' file manager,
> > 
> > The quicklaunch bug was fixed in commit c839bb9a,
> Thursday July 12. Make sure
> > you are building with tdebase pulled to date.
> 
> The GIT pull was from 7/15.

Okay. Open your quick launch config file with a text editor or viewer. The file name is goofy, like this:

$TDEHOME/share/config/launcher_panelapplet_dyrwtplrzeqcrk4kmi9m_rc

Look for any occurences of kde-.

If you see that, then exit TDE and run the r14-xdg-update script using the 'force' parameter.

By the way, have you ever run the r14-xdg-update script against your 3.5.12 profile? If you don't know or are uncertain, open $TDEHOME/share/config/kdeglobals and look for the following:

[R14 XDG Updates]
Updated=true

If you find that in your 3.5.12 profile, then change the key value to anything other than true or exit Trinity and run the r14-xdg-update script with the 'force' parameter.

>   This is exactly why we need a "Code Freeze" and 10
> days to identify and fix.

Until about a dozen usability bugs and numerous build issue bugs are resolved I think we are a ways off from a freeze. Just my opinion. The problems you are experiencing are growing pains of somebody moving from 3.5.12, which I don't think anybody has done yet. You're the guinea pig. :-)

> I'm in. I have the install and several recent package sets
> we can work from. I'll have a list together soon and let's start putting our
> heads together.
> 
> Do you want to start a new etherpad?

Nah, we can keep things going here.

I have a feeling the problems you are seeing are 1) the menus and 2) corner cases with the r14-xdg-update or migratekde3 scripts. I don't have a 3.5.12 setup. I doubt I could create one that would replicate your setup. So we go one step at a time. The good news is I have been using R14 for several weeks. Everything works. We simply need to learn what breaks with a 3.5.12 migration and we'll be okay.

Darrell