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 646142 - problems with binary operations in programming mode
problems with binary operations in programming mode
Status: RESOLVED FIXED
Product: gnome-calculator
Classification: Core
Component: general
5.91.x
Other Linux
: Normal major
: ---
Assigned To: gcalctool maintainers
gcalctool maintainers
: 647415 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-03-29 17:30 UTC by Jonathan
Modified: 2011-04-20 02:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example (123.31 KB, image/png)
2011-04-04 21:13 UTC, Fabio Durán Verdugo 		Details

Description Jonathan 2011-03-29 17:30:56 UTC 
When in programming mode, and setting/unsetting bits by clicking them a "Displayed value not an integer" error occurs. The first bit set/unset works fine, but the second does not.

A similar problem is true for bit shifts. The first operation works fine, the second bit shift causes a "No sane value to bitwise shift" error.

Kind regards,
Jonathan
Comment 1 Jonathan 2011-03-29 17:34:46 UTC 
I am using archlinux on gnome 2.32.1
I had the same issue when running gnome on FreeBSD
Comment 2 Vikram Kamath 2011-04-04 13:51:10 UTC 
Hi, I was just looking at the bug and unfortunately I couldn't replicate it. Could you please try and post the input to which the error occoured.
Comment 3 Fabio Durán Verdugo 2011-04-04 21:13:06 UTC 
Created attachment 185151 [details]
Example

I can reproduce, I only follow the steps given by Jonathan.
I get  when Enable/Disable the first byte "Displayed value not an integer".

Test in gcalctool-5.91.93-1
Comment 4 Robert Ancell 2011-04-20 02:05:28 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 5 Robert Ancell 2011-04-20 02:15:11 UTC 
*** Bug 647415 has been marked as a duplicate of this bug. ***