No Suse menu in new kicker-3.5.8-r10

[dave_p_b]

Help

I have not suse menu in the new kicker-3.5.8-r10. I have installed the rest of kde 3.5.8.

Has anyone tried this yet?

Many thanks

Dave

[Fitzcarraldo]

I lost the SuSE kicker when I re-installed the previous version of KDE, but ended up liking the KDE menu better and kept it. However, would the procedure given in the Wiki for updating the Mini Edition (LiveCD) to the LiveDVD SuSE-style kicker get you back to the SuSE kicker, Dave?

http://wiki.sabayonlinux.org/index.php? ... yle_kicker

[dave_p_b]

Hi

Thanks for your quick reply. The dev team have just updated the kicker-3.5.8-r10 ebuild so the Suse menu is back.

Many thanks

Dave

[christophocles]

I also lost the Suse menu when I installed kicker-3.5.8-r10. I also followed the instructions in the wiki (recompiled with -kdeinvisibility USE flag) and I still don't have it. When I try to change from KDE-style menu to SUSE-style menu, kicker reloads but the menu stays the same. How can I get back the original menu that came installed with Sabayon?

Some useful info....

$ eix kde-base/kicker

[I] kde-base/kicker
Available versions:
(3.5) 3.5.5 (~)3.5.6 3.5.7 (~)3.5.8
(0) (~)3.5.5-r90[2] (~)3.5.5-r92[2] (~)3.5.6-r91[2] (~)3.5.6-r92[2] (~)3.5.6-r93[2] 3.5.7[1] (~)3.5.7-r10[2] (~)3.5.7-r11[2] (~)3.5.7-r12[2] (~)3.5.7-r13[2] (~)3.5.8[1] (~)3.5.8-r10[2]
{arts debug elibc_FreeBSD kdeenablefinal kdehiddenvisibility kickoff pertty xcomposite xinerama}
Installed versions: 3.5.8-r10[2](01:14:32 AM 11/04/2007)(arts xcomposite xinerama -debug -elibc_FreeBSD -kdeenablefinal -kickoff)
Description: Kicker is the KDE application starter panel and is also capable of some useful applets and extensions.

[I] kde-base/kicker-applets
Available versions: (3.5) 3.5.5 (~)3.5.6 3.5.7 (~)3.5.8
{arts debug elibc_FreeBSD kdeenablefinal xinerama}
Installed versions: 3.5.8(3.5)(03:27:19 AM 11/04/2007)(arts xinerama -debug -elibc_FreeBSD -kdeenablefinal)
Homepage: http://www.kde.org/
Description: kicker applets

[1] "xeffects" /usr/portage/local/layman/xeffects
[2] "sabayon" /usr/portage/local/layman/sabayon

Found 2 matches.

[momocore]

Try adding the "kickoff" use flag

Code: Select all

# euse -E kickoff && emerge kicker

From there, either restart X or in KControl select the KDE menu, click apply, then select SUSE menu and click apply. It should be intact.

Hope that helps!

[christophocles]

Try adding the "kickoff" use flag

Code: Select all

# euse -E kickoff && emerge kicker

From there, either restart X or in KControl select the KDE menu, click apply, then select SUSE menu and click apply. It should be intact.

Hope that helps!

Sweet, the kickoff USE flag worked like a charm. I was wondering what it was for.. I was afraid to enable it before because its description said <unknown>. Gentoo-portage.com doesn't even list it. Is it new or something?

$ euse -i kickoff
global use flags (searching: kickoff)
************************************************************
no matching entries found

local use flags (searching: kickoff)
************************************************************
no matching entries found

$ equery uses kicker
[ Searching for packages matching kicker... ]
[ Colour Code : set unset ]
[ Legend : Left column (U) - USE flags from make.conf ]
[ : Right column (I) - USE flags packages was installed with ]
[ Found these USE variables for kde-base/kicker-3.5.8-r10 ]
U I
+ + arts : Adds support for aRts: the KDE sound daemon
- - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml .
- - elibc_FreeBSD : <unknown>
- - kdeenablefinal : EXPERIMENTAL: KDE ebuilds will use the enable-final flag, yielding compilation speedups at the cost of heavy mem usage and potentially causing problems. We strongly discourage setting this.
+ + kickoff : <unknown>
+ + xcomposite : Enable support for the Xorg composite extension
+ + xinerama : Add support for the xinerama X11 extension, which allows you to stretch your display across multiple monitors
$

[momocore]

I believe its specific to the Sabayon layman, so it woudn't show up in gentoo...

[velk]

Hi, i moved to kde 3.5.8 and now the Suse Menu (default sabayon KDE menu) is not available in the kcontrol center

How can i get it back ?

[wolfden]

*sighs, the power of search

viewtopic.php?f=59&t=11188&p=66034

Use Search

Merged Redundant Topic

[velk]

it is not working for me;(

Code: Select all

# euse -E kickoff && emerge kicker

...

* checking kdebase-3.5.8.tar.bz2 ;-) ...                                 [ ok ]
 * checking kdebase-3.5-patchset-03.tar.bz2 ;-) ...                       [ ok ]
 * checking kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2 ;-) ...     [ ok ]
 * checking kickoff-icons.tar.bz2 ;-) ...                                 [ ok ]
>>> Unpacking source...
>>> Unpacking parts of kdebase-3.5.8.tar.bz2 to /var/tmp/portage/kde-base/kicker-3.5.8/work
>>> Unpacking kdebase-3.5-patchset-03.tar.bz2 to /var/tmp/portage/kde-base/kicker-3.5.8/work
>>> Unpacking kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2 to /var/tmp/portage/kde-base/kicker-3.5.8/work
>>> Unpacking kickoff-icons.tar.bz2 to /var/tmp/portage/kde-base/kicker-3.5.8/work
Symlinking library libkonq under /usr/kde/3.5/lib/ in source dir
 * Applying kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2 ...

 * Failed Patch: kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2 !
 *  ( /var/tmp/portage/kde-base/kicker-3.5.8/temp/11904.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/kde-base/kicker-3.5.8/temp/kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2-11904.out

 *
 * ERROR: kde-base/kicker-3.5.8 failed.
 * Call stack:
 *             ebuild.sh, line 1701:  Called dyn_unpack
 *             ebuild.sh, line  817:  Called qa_call 'src_unpack'
 *             ebuild.sh, line   44:  Called src_unpack
 *   kicker-3.5.8.ebuild, line   68:  Called epatch '/var/tmp/portage/kde-base/kicker-3.5.8/distdir/kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2'
 *         eutils.eclass, line  304:  Called die
 * The specific snippet of code:
 *                              die "Failed Patch: ${patchname}!"
 *  The die message:
 *   Failed Patch: kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2!
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/kde-base/kicker-3.5.8/temp/build.log'.
 *

 * Messages for package kde-base/kicker-3.5.8:

 * Failed Patch: kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2 !
 *  ( /var/tmp/portage/kde-base/kicker-3.5.8/temp/11904.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/kde-base/kicker-3.5.8/temp/kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2-11904.out
 *
 * ERROR: kde-base/kicker-3.5.8 failed.
 * Call stack:
 *             ebuild.sh, line 1701:  Called dyn_unpack
 *             ebuild.sh, line  817:  Called qa_call 'src_unpack'
 *             ebuild.sh, line   44:  Called src_unpack
 *   kicker-3.5.8.ebuild, line   68:  Called epatch '/var/tmp/portage/kde-base/kicker-3.5.8/distdir/kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2'
 *         eutils.eclass, line  304:  Called die
 * The specific snippet of code:
 *                              die "Failed Patch: ${patchname}!"
 *  The die message:
 *   Failed Patch: kdebase-3.5.7-kicker-kickoff-suse-642174.diff.bz2!
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/kde-base/kicker-3.5.8/temp/build.log'.
 *