Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12793 - [e-svn] System menu is empty
Attached to Project:
Community Packages
Opened by Nicky726 (Nicky726) - Wednesday, 14 January 2009, 20:37 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 15 January 2009, 10:49 GMT
Opened by Nicky726 (Nicky726) - Wednesday, 14 January 2009, 20:37 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 15 January 2009, 10:49 GMT
|
DetailsDescription:
Some updates ago all items from System menu in E17 disappeared. Theese contain rather vital items like Shut-down, Reboot and so. Deleting .e directory didn't help. Searching Google showed, that some kind of patch is necesary to be aplied, more can be read here:debian-devel-changes@lists.debian.org/msg231742.html"> http://www.mail-archive.com/debian-devel-changes@lists.debian.org/msg231742.html especialy the part starting with: * Add debian/patches/02_fix_default_config_for_upgrades.diff: Additional info: * package version(s) e-svn 38570-1 * config and/or log files etc. Steps to reproduce: Just open the menu by clicking at e logo at panel and you'll see the System submenu is not-expandable, for it is empty. You probably should have E17 installed for some time, as the debian guys say it concerns only users upgrading from older versions. |
This task depends upon
Closed by Ronald van Haren (pressh)
Thursday, 15 January 2009, 10:49 GMT
Reason for closing: Not a bug
Additional comments about closing: upstream change in config files
Thursday, 15 January 2009, 10:49 GMT
Reason for closing: Not a bug
Additional comments about closing: upstream change in config files
Users with old installations had problems with it because these functions went into a new module called 'system controls', which was not automagically loaded on old configurations.
Can you check that you have this module loaded?
I assume you have tried this with a clean config? If so maybe filing a bug upstream or posting on the enlightenment-devel mailing list will help you any further. I'll keep the bug open for now, maybe someone else has better ideas or the same problem