vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On upgrading to KDE 3.4 my KDE taskbar (the thing that displays minimized windows) doesn't start up, and if I try to start it manually I get the error "The Taskbar applet could not be loaded. Please check your installation." It works under 3.3. Any ideas? Is there a log somewhere? TIA |
| |||
| Wes Gray wrote: > On upgrading to KDE 3.4 my KDE taskbar (the thing that displays minimized > windows) doesn't start up, and if I try to start it manually I get the > error "The Taskbar applet could not be loaded. Please check your > installation." It works under 3.3. Any ideas? Is there a log somewhere? > TIA Have you tried creating a test user with no ~/.kde directories just to see if its an importation problem? -- Stephen Fairchild |
| |||
| Wes Gray wrote: > On upgrading to KDE 3.4 my KDE taskbar (the thing that displays minimized > windows) doesn't start up, and if I try to start it manually I get the > error "The Taskbar applet could not be loaded. Please check your > installation." It works under 3.3. Any ideas? Is there a log somewhere? > TIA If you used split ebuild, you have to emerge kicker (the kde menu program) |
| ||||
| Kim Pedersen wrote: > > If you used split ebuild, you have to emerge kicker (the kde menu program) I'm not doing a split ebuild that I know of, not even sure what it is. This is odd though. Based on your suggestion I tried pretend emerging kicker and got these strange blockers with *'s in the name: # emerge -p kicker These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-data-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/libkonq-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kicker-3.4.1) [ebuild N ] kde-base/kdebase-data-3.4.1 [ebuild N ] kde-base/libkonq-3.4.1 [ebuild N ] kde-base/kicker-3.4.1 |