Emerging wmakerconf-2.9.2 gives access violation errors: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-x11-misc_-_wmakerconf-2.9.2-3847.log" open_wr: /usr/share/locale/de/LC_MESSAGES/wmakerconf.mo open_wr: /usr/share/locale/fr/LC_MESSAGES/wmakerconf.mo open_wr: /usr/share/locale/pt_BR/LC_MESSAGES/wmakerconf.mo open_wr: /usr/share/locale/da/LC_MESSAGES/wmakerconf-data.mo open_wr: /usr/share/locale/de/LC_MESSAGES/wmakerconf-data.mo open_wr: /usr/share/locale/ja/LC_MESSAGES/wmakerconf-data.mo open_wr: /usr/share/locale/ko/LC_MESSAGES/wmakerconf-data.mo open_wr: /usr/share/locale/pl/LC_MESSAGES/wmakerconf-data.mo open_wr: /usr/share/locale/ru/LC_MESSAGES/wmakerconf-data.mo open_wr: /usr/share/locale/pt_BR/LC_MESSAGES/wmakerconf-data.mo mkdir: /usr/share/locale/es_ES mkdir: /usr/share/locale/es_ES/LC_MESSAGES open_wr: /usr/share/locale/es_ES/LC_MESSAGES/wmakerconf-data.mo open_wr: /usr/share/gnome/apps/Settings/wmakerconf.desktop -------------------------------------------------------------------------------- Reproducible: Always Steps to Reproduce:
Created attachment 43597 [details, diff] wmakerconf-2.9.2.ebuild.patch This is my patch for the ebuild currently in portage that fix this problem. It also adds ~x86 to the KEYWORDS list. Also it removes the blocking on windowmaker-0.9*, as according to the latest news in the home page, the known bug should have been fixed in this version.
changes applied still blocking on windowmaker-0.9* series, as wmakerconf simply does not enable new configuration options, especially in regards to fonts
