Summary: | dev-libs/efl-1.21.1: efreet did not update cache, icons missing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tbartdev |
Component: | Current packages | Assignee: | Joonas Niilola <juippis> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch to for x11-wm/enlightenment-0.24 |
Description
tbartdev
2018-12-05 10:21:55 UTC
So I installed parcellite and it shows icon when ran from "Everything launcher". Do you have some custom .desktop file for it, which looks for icon from ~ or something? Also could you show your efl USE flags? Then 2nd thing: Some time ago (I believe in e-0.22.3) Enlightenment-WM dropped support for xembed systray apps. Does parcellite launch itself to systray? You may need to install some external systray app capable of showing old-school xembed apps. Or play with panel settings trying to get systray to work there. I realized this because I ran parcellite from terminal but it doesnt show anywhere, it still seems to work from and in terminal. https://wiki.gentoo.org/wiki/Enlightenment#Applications_requiring_system_tray_not_working_properly Created attachment 650430 [details, diff]
Patch to for x11-wm/enlightenment-0.24
/etc/portage/patches/x11-wm/enlightenment/enlightenment-0.24.1.patch
I'm running into the same situation, I was able to circumvent the problem by increasing the timeout (from 10 seconds to 60 seconds) that e_startup uses when waiting for efreetd to start. The real question is why is efreetd taking so long to start. I haven't ran into this, if you backup your ~/.e and ~/.elementary directories, then move/delete them and relog, does it help? I think I solved this by removing the consolekit USE flag (currently not at my box). And then I haven't reported back - shame on me.. Do you still get this error with a current version built with elogind (which seems to be the way to go as it seems)? Removing the consolekit USE flag or building a more current version with elogind also fixed the application not getting started. Can you reproduce this? Maybe the additional time helps to not run into a timeout waiting for some consolekit/elogind-like daemon? I think I remember not using slim/lightdm to login but using startx from a console also helped. |