Description of problem: Terminology cannot start because of a theme problem, it seems. Version-Release number of selected component (if applicable): 0.2.0 Steps to Reproduce: 1. install terminoology via urpmi or rpmdrake 2. try to launch terminology into a terminal to see the error message: CRI<20719>:elementary elm_win.c:2366 elm_win_add() Software X11 engine creation failed. Trying default. ERR<20719>:elementary elm_win.c:2551 elm_win_add() Cannot create window. ERR<20719>: elm_conform.c:571 elm_conformant_add() safety check failed: parent == NULL ERR<20719>: utils.c:13 theme_apply() safety check failed: edje == NULL CRI<20719>:terminology main.c:673 elm_main() Couldn't find terminology theme! Forgot 'make install'? Reproducible: Steps to Reproduce:
It seems not all dependencies are listed in the package. A workaround is to install full Enlightment.
CC: (none) => matija
Keywords: (none) => Triaged
I've looked for missing dependancy, and I've found two packages: - evas - elementary With both dependancies, I can run terminology without installing all e17.
I have uploaded a patched/updated package for Mageia 2. You can test it with the folling command : - urpme libeina1 (remove almost all e17 package) - urpmi terminology (install only terminology) - terminology (run it) then terminology should start Updated packages in core/updates_testing: ======================== terminology-0.2.0-3.mga3 terminology-debuginfo-0.2.0-3.mga3 Source RPMs: terminology-0.2.0-3.mga3
Assignee: tremyfr => qa-bugs
(In reply to trem from comment #3) > I have uploaded a patched/updated package for Mageia 2. Is 2 updated aswell trem or did you mean Mageia 3 here?
Advisory 10312.adv uploaded to svn, assuming it's for 3 only.
CC: (none) => davidwhodgins
Testing i586 and x86_64 on Mga3.
CC: (none) => bozonius
After applying the testing update, the program appears to start as expected, but it issues what look like might be error messages on every individual motion or keypress. I attempted to look up the indicated number on their bug tracking system, but can not find a bug number that high. There was a version control changeset with that number, though. Claire has recommended a bug to clean up these entrails. So far, I have applied the update to i586.
MGA3-64-OK for me in VirtualBox default install terminology-0.2.0-2.mga3.x86_64 from core release [root@localhost wilcal]# urpmi terminology Package terminology-0.2.0-2.mga3.x86_64 is already installed Recreated error messages referred to in Description install terminology-0.2.0-3.mga3.x86_64 from core updates_testing [root@localhost wilcal]# urpmi terminology Package terminology-0.2.0-3.mga3.x86_64 is already installed Relaunch terminology from Menu, launched ok Launch terminology from a terminal and that's fine too. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) VirtualBox 4.2.16-1.mga3.x86_64.rpm
CC: (none) => wilcal.intWhiteboard: (none) => MGA3-64-OK
MGA3-32 ok for me in VirtualBox default install terminology-0.2.0-2.mga3.i586 from core release [root@localhost wilcal]# urpmi terminology Package terminology-0.2.0-2.mga3.i586 is already installed Recreated error messages referred to in Description install terminology-0.2.0-3.mga3.i586 from core updates_testing [root@localhost wilcal]# urpmi terminology Package terminology-0.2.0-3.mga3.i586 is already installed Relaunch terminology from Menu, launched ok Launch terminology from a terminal and that's fine too. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) VirtualBox 4.2.16-1.mga3.x86_64.rpm
Whiteboard: MGA3-64-OK => MGA3-32-OK MGA3-64-OK
Validating the update. Could someone from the sysadmin team push 10312.adv to updates. ready for validation
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
While confirming the defect on x86_64, the errors listed while starting terminology on x86_64 seems to be different; the program does not launch as expected. After testing update is applied, the program works. It also spits out a trace indicating a different (changeset?) number than the i586 version, but it appears to behave the same way, tracing each keyclick or mouse movement. Bug 11021 has been filed against this other issue.
Keywords: validated_update => (none)Whiteboard: MGA3-32-OK MGA3-64-OK => (none)
Validated the update. Since the bug has been requested for push already, I will not duplicate the effort.
Keywords: (none) => validated_updateWhiteboard: (none) => mga3-32-ok mga3-64-ok
Update pushed: http://advisories.mageia.org/MGAA-2013-0087.html
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED