Issue Details (XML | Word | Printable)

Key: FDT-2396
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: FDT Team
Reporter: Piotr Berlowski
Votes: 0
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
FDT

FDT crashes on startup

Created: 01/Nov/11 06:20 PM   Updated: 22/Jun/12 06:12 PM
Component/s: Linux (Deprecated), Welcome Screen
Affects Version/s: FDT 5.0
Fix Version/s: FDT 5.5
Security Level: public

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. lastscreen.png
(358 kB)
Environment: Gentoo Linux, Compiz-Fusion, GNOME

Review Type: Review by Product Owner


 Description  « Hide
The FDT manages to load properly but dies miserably after displaying the "FDT start page". It's possible to actually keep it alive if you manage to close the start page before it loads the content...

(FDT 5:18974): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed

    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    • (FDT 5:18974): DEBUG: NP_Initialize
    • (FDT 5:18974): DEBUG: NP_Initialize succeeded
      The program 'FDT 5' received an X Window System error.
      This probably reflects a bug in the program.
      The error was 'BadValue (integer parameter out of range for operation)'.
      (Details: serial 17688 error_code 2 request_code 53 minor_code 0)
      (Note to programmers: normally, X errors are reported asynchronously;
      that is, you will receive the error a while after causing it.
      To debug your program, run it with the --sync command line
      option to change this behavior. You can then get a meaningful
      backtrace from your debugger if you break on the gdk_x_error() function.)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Sebastian Bär made changes - 02/Nov/11 01:15 PM
Field Original Value New Value
Resolution none [ 6 ]
Assignee Philipp Arnolds [ phiarn ] Sebastian Bär [ sb ]
Status Open [ 1 ] Under Investigation [ 10004 ]
[ Permalink | « Hide ]
Piotr Berlowski added a comment - 02/Nov/11 03:38 PM
Please let me know if I can help in any way in debugging this.

[ Permalink | « Hide ]
Sebastian Bär added a comment - 02/Nov/11 05:13 PM
Hi Piotr,

thanks for your offer. I couldn't reproduce the issue on the binary distros we have here yet so I will give Gentoo with Compiz & Gnome a try now.
What's your default browser on Gnome?

I would like to contact you as soon as we have a potential fix ready.


[ Permalink | « Hide ]
Piotr Berlowski added a comment - 02/Nov/11 05:31 PM
Hi Sebastian,

I'm running Mozilla Firefox as prefered browser. At the moment my version is 3.6.17.

My compiz is on 0.8.4 with both plugins main and plugins extra. Gnome version is 2.32.1

Are you rendering the start page programatically somehow, or would I be able to just check my system config by trying to open some page with my browser?

If this proves to be local issue for me, is there any way to prevent the start page from showing up on every startup? It anoys me greatly anyway

Cheers


[ Permalink | « Hide ]
Piotr Berlowski added a comment - 02/Nov/11 05:51 PM
To be more precise about the moment when the issue occurs, I attach the latest screenshot that I can take before the IDE crashes.

Piotr Berlowski made changes - 02/Nov/11 05:51 PM
Attachment lastscreen.png [ 13312 ]
[ Permalink | « Hide ]
Piotr Berlowski added a comment - 02/Nov/11 06:38 PM - edited
Sorry for spamming, but I actually found out that I lied in one of my previous comments.

Whereas I have Mozilla Firefox set in "Preferred Applications", the browser in the system is Gnome's Epiphany (2.30.6-r1).

I went to http://welcomescreen.fdt.powerflasher.com/html/1VUBI37D/index.php and Firefox stays alive, whereas Epiphany dies miserably with the aforementioned error.

Unsure as to why Eclipse/FDT uses Epiphany - will investigate.

–

Also confirmed Epiphany crashing on another machine with similar configuration.


[ Permalink | « Hide ]
Sebastian Bär added a comment - 02/Nov/11 08:10 PM
Sorry for the delay and thanks a lot for the help!
We'll work on the issue by fixing the welcome screen's content for Epiphany and by investigating why Epiphany is used as preferred browser.
It may be the case that the problem even if it'll be solved on server side takes us a day to fix.
So I will send you a mail with instructions of how you can disable (temporarily deactivate) the welcome screen now to ensure that you can work in the meantime.

Sebastian Bär made changes - 02/Nov/11 08:33 PM
Status Under Investigation [ 10004 ] Confirmed [ 10000 ]
[ Permalink | « Hide ]
Piotr Berlowski added a comment - 10/Nov/11 11:27 AM
Hi Sebastian, I still haven't received the e-mail about welcome screen deactivation... Would it be possible for you to look at that?

[ Permalink | « Hide ]
Sebastian Bär added a comment - 10/Nov/11 11:39 AM
Hi Piotr, I sent it a week ago to the address you created your jira account with. Could you send me a mail from your current address to sbATpowerflasher.de. Thanks

[ Permalink | « Hide ]
Zachary Richley added a comment - 07/Jan/12 04:10 PM
Didn't realize this issue was already being tracked so I started a new one: http://bugs.powerflasher.com/jira/browse/FDT-2516

In any event FDT crashes if I don't close the Welcome Screen (WS) within 30 seconds.

Up until last week the WS gave me a message about "no suitable browser found" no crashes involved. I have firefox, chrome, midori, opera, dillo installed and none of those would fix the "no suitable browser" found message. Then a few days ago the WS started displaying information instead of the afformentioned message, but now crashes within 30 seconds.

I am running Gentoo Linux (3x series kernel) XFCE desktop & fluxbox netbook both have the same problem. Any other information you need I will be happy to provide.

Thanks for a great product btw.


[ Permalink | « Hide ]
Eugene added a comment - 19/Feb/12 09:41 PM
Hi.
I have exactly the same issue.
FDT 5.0.0.1460
Ubuntu 10.04
Sun Java 1.6.0_31
FireFox 10.0.2

No problems in Aptana Studio 3 or Eclipse 3.7.1


Alan K (Deprecated) made changes - 28/Feb/12 07:57 PM
Review Type Review by Product Owner
Fix Version/s 5.1 [ 10432 ]
Dennis Sabelleck made changes - 23/Apr/12 04:45 PM
Assignee Sebastian Bär [ sb ] Dennis Sabelleck [ dsa ]
Alan K (Deprecated) made changes - 30/Apr/12 03:37 PM
Component/s Welcome Screen [ 10510 ]
Philipp Arnolds made changes - 02/May/12 12:23 PM
Fix Version/s 5.5 Beta [ 10432 ]
Fix Version/s FDT 5.5 [ 10491 ]
Resolution none [ 6 ] Fixed [ 1 ]
Status Confirmed [ 10000 ] Resolved [ 5 ]
Sebastian Bär made changes - 07/May/12 06:19 PM
Status Resolved [ 5 ] Confirmed [ 10000 ]
[ Permalink | « Hide ]
Sebastian Bär added a comment - 07/May/12 06:20 PM
Guys,

sorry for the sloppy handling of this issue. It should be fixed by now.


Sebastian Bär made changes - 07/May/12 06:20 PM
Status Confirmed [ 10000 ] Resolved [ 5 ]
Sebastian Bär made changes - 07/May/12 06:21 PM
Status Resolved [ 5 ] Closed [ 6 ]
FDT Team made changes - 22/Jun/12 06:12 PM
Assignee Dennis Sabelleck [ dsa ] FDT Team [ fdt team ]
Status Closed [ 6 ] Resolved [ 5 ]
FDT Team made changes - 22/Jun/12 06:12 PM
Status Resolved [ 5 ] Closed [ 6 ]

Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.5-#360) - Bug/feature request - Atlassian news - Contact Administrators