After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 735654 - "incorrect expression" error when switching from hexa to decimal
"incorrect expression" error when switching from hexa to decimal
Status: RESOLVED FIXED
Product: gnome-calculator
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gcalctool maintainers
gcalctool maintainers
Depends on:
Blocks:
 
 
Reported: 2014-08-29 08:08 UTC by exebetche
Modified: 2014-08-31 14:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description exebetche 2014-08-29 08:08:43 UTC
Version 1:3.10.2-0ubuntu1.1 on ubuntu 14.04 32bit

How to reproduce:
- open gcalctool
- choose "Programming mode"
- choose "decimal" and enter a decimal number
- choose "hexadecimal" to convert the number in hexa
- then try to put and other hexadecimal number and you get the error "Incorrect expression" every time

I can't find a way to enter a new value at this point and I have to restart the tool. This problem definitvely didn't occur with the previous version on ubuntu 12.04.

I filled a bug report to the gcalctool dev team and they confirmed it was an upstream bug.

Here is the error output:
** (gcalctool:4245): CRITICAL **: string_splice: assertion '_tmp18_ <= _tmp19_' failed

** (gcalctool:4245): CRITICAL **: string_get_next_char: assertion 'self != NULL' failed

** (gcalctool:4245): CRITICAL **: string_splice: assertion '_tmp18_ <= _tmp19_' failed

** (gcalctool:4245): CRITICAL **: string_get_next_char: assertion 'self != NULL' failed

....
Comment 1 Michael Catanzaro 2014-08-29 12:19:16 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 2 Sebastien Bacher 2014-08-31 09:15:10 UTC
could you give details on the commit? is that issue fixed only in 3.13? can you backport to fix to stable?
Comment 3 Michael Catanzaro 2014-08-31 14:00:39 UTC
It's this commit: https://git.gnome.org/browse/gnome-calculator/commit/?id=9ff8396ca73eaade391acc9eceacc1fcfe774cfc

I don't know why it wasn't backported.