Application crashes if initial login throws an exception

Bug #409334 reported by Hosam Aly
This bug report is a duplicate of:  Bug #409343: Unicode passwords are not supported. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Confirmed
Undecided
sme (OpenERP)

Bug Description

OpenERP - GTK Client - v5.0.0 - Python 2.6.2

The application crashes if an error occurs during initial login. Any exception that is thrown from the login method is not being captured, and the application crashes without showing an error dialog or saying what happened.

Revision history for this message
Hosam Aly (hosamaly) wrote :

An example that shows this bug in action:
1. Open the application.
2. In the initial login screen, enter a password that contains a unicode character (see bug #409345)
3. Press Enter or OK. The application crashes.

sme (OpenERP) (sme-tiny)
Changed in openobject-client:
assignee: nobody → sme(Tiny/Axelor) (sme.tiny.axelor)
status: New → Confirmed
affects: openobject-client → openobject-server
Revision history for this message
Hosam Aly (hosamaly) wrote :

Why was this bug moved to OpenObject Server, I wonder? It seems to me like a bug in the client code. Exceptions thrown from the login process are not being captured. This can happen with any type of exception, whether it comes from the server or any other problem on the client side (e.g. connection breakdown during login).

The client code should be fixed to capture such exceptions and displaying an error message and avoiding the crash.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Hosam Aly,

The server was not sending proper reply to Client, so client was crashed.

Thanks.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Marked as duplicate as another bug with same issue with different aspect is posted.
Thanks.

Revision history for this message
Hosam Aly (hosamaly) wrote :

Hello Jay. Yes, the client crashed because the server did not send a proper reply, but I still believe that case should be handled, the exception should be caught, and an error message should be presented to the user. This issue will happen every time there is a problem in receiving or parsing the reply, so fixing it in the client once will make up for any future bugs that may appear in the server.

Thank you.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.