iaddis / electricsheep

Automatically exported from code.google.com/p/electricsheep
1 stars 1 forks source link

electricsheep-preferences does not run under *ubuntu #9

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Attempt to run electricsheep-preferences
2. Windows opens
3. Hover over any text field, application crashes.

What is the expected output? What do you see instead?
electricsheep-preferences should run without crashing. Application crashes and 
throws this error message

SetInstallation: /usr/local/share/electricsheep/Scripts
**
Pango:ERROR:/build/buildd/pango1.0-1.30.0/./pango/pango-layout.c:3801:pango_layo
ut_check_lines: assertion failed: (!layout->log_attrs)
Aborted (core dumped)

What version of the product are you using? On what operating system?
SVN r126, Kubuntu 12.04

Please provide any additional information below.
There are many reports of this issue in the forums, all from different versions 
of Ubuntu. There is a reported fix, but it does not work.

Original issue reported on code.google.com by hideak...@gmail.com on 7 Aug 2012 at 3:42

GoogleCodeExporter commented 9 years ago
linux mint 13...same problem

Original comment by cale...@yahoo.com on 22 Nov 2012 at 4:30

GoogleCodeExporter commented 9 years ago
Arch Linux, newest Git revision of Pango.  Same error.

Original comment by Jeos...@gmail.com on 26 Nov 2012 at 1:53

GoogleCodeExporter commented 9 years ago
Same for me with Arch Linux, Gnome and ES installed from AUR.

Original comment by davideriboli on 15 Dec 2012 at 6:13

GoogleCodeExporter commented 9 years ago
Same for me.

Ubuntu 12.10
Electricsheep 2.7b33
wxWidgets 2.9.4
Flam3 3.0.1

Original comment by brendan....@gmail.com on 5 Mar 2013 at 3:50

GoogleCodeExporter commented 9 years ago
Working fine here:
Ubuntu 12.04
Electric Sheep 2.7b12

Original comment by jamin.co...@gmail.com on 8 Mar 2013 at 9:26

GoogleCodeExporter commented 9 years ago
Yeah, older beta releases don't suffer from this issue. It's only present on 
more recent builds.

Original comment by hideak...@gmail.com on 8 Mar 2013 at 9:45

GoogleCodeExporter commented 9 years ago
Likely a threading/GUI problem.  A similar error was encountered here:
http://forums.wxwidgets.org/viewtopic.php?t=17897&p=77296

Original comment by xan...@yahoo.com on 9 Mar 2013 at 5:04

GoogleCodeExporter commented 9 years ago
Same issue for me as well trying to build and install v2.7b33 from source.  It 
seems like there is no version of ES that runs properly on Ubuntu 12.04 at the 
moment.

@hideak...: 2.7b12 worked ok except for the max_analyze_duration reached 
problem described in this thread: http://electricsheep.org/node/2890

That problem the max_analyze_duration reached prompted the upgrade to the 
latest ES as recommended by Spot.  That led to this problem:  
http://electricsheep.org/node/5263

I worked around that problem by following instructions in this thread:
http://electricsheep.org/node/4278

Only to wind up having the problem described in this report.

Original comment by NetRoa...@gmail.com on 18 Jun 2013 at 6:33

GoogleCodeExporter commented 9 years ago
This issue appears to be caused by the login thread in the preferences 
application. The login thread, which handles the login process in the 
background, also makes some calls to GUI methods (setting label texts etc.), 
which is essentially forbidden and will never work.

I'm looking into this right now and I already have a way that can get me/us 
around this but I have never used wxWidgets before so it might take a little 
while before I can solve this.

Original comment by znovo...@gmail.com on 17 Nov 2013 at 4:31

GoogleCodeExporter commented 9 years ago
Ok, it seems that I was able to fix this issue and electricsheep-preferences 
appears to be working correctly. I'm currently reviewing the changes and then I 
will send the patch to Scott.

Original comment by znovo...@gmail.com on 20 Nov 2013 at 5:20

GoogleCodeExporter commented 9 years ago
@znovo, was this patch ever incorporated? I have this problem on Arch Linux and 
it's labeled an "upstream bug" (https://bugs.archlinux.org/task/32372).

Original comment by ideo...@gmail.com on 15 Oct 2014 at 1:53