The verification of the Stable Release Update for gnome-calculator has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.

  SRU: sin(0)/sin(0) crash the the calculator

Status in GNOME Calculator:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-calculator source package in Xenial:
  Fix Released

Bug description:

  It is possible to cause gnome-calcualtor segfault when elements of
  division to zero have null assigned tokens. For example, the following
  calculation will trigger a segfault:


  [Test Case]

  Open a terminal with CTRL+ALT+t and launch 'gnome-calculator'. Type
  the following into the equation entry area 'sin(0)/sin(0)' and press
  enter, gnome-calculator will segfault.

  When the patched 'gnome-calculator' package is installed performing
  the same calculation described above will not cause 'gnome-calculator'
  to crash and instead the following will be displayed: Division by zero
  is undefined

  A debdiff for Xenial is attached in comment #2:


  [Regression Potential]

  None expected. The applied patch is taken directly from the following
  upstream commit:


  gnome-calculator packages have been built in a PPA and tested.

  [Other Info]

  dw3@linux:~$ gnome-calculator

  (gnome-calculator:29011): GLib-CRITICAL **: g_str_has_prefix:
  assertion 'str != NULL' failed

  (gnome-calculator:29011): GLib-CRITICAL **: g_str_has_prefix: assertion 'str 
!= NULL' failed
  Segmentation fault (core dumped)

  sin(0)/sin(0) = NaN, but it crash the calculator

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to