Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0-MS15
    • Fix Version/s: future-release
    • Component/s: updatetool
    • Labels:
      None
    • Environment:

      Operating System: Solaris
      Platform: All

    • Issuezilla Id:
      709
    • Tags:

      Activity

      Hide
      Snjezana Sevo-Zenzerovic added a comment -

      Moving to more appropriate subcategory since issue is not with the OLH content
      but (presumably) with UI implementation.

      Show
      Snjezana Sevo-Zenzerovic added a comment - Moving to more appropriate subcategory since issue is not with the OLH content but (presumably) with UI implementation.
      Hide
      ckamps added a comment -

      Build: GFv3Prelude build 19
      OS: Solaris 10 X86 U5

      Encountered the following repeated lines of the same error (about 24 lines) on
      the console screen where updatetool was launched when Help->Contents is selected
      from the GUI:

        • (python:1678): CRITICAL **: file blueprint-draw.c: line 81: assertion
          `GTK_WIDGET (widget)' failed

      Note: Although "Help->Content" is working, the error message is very visible to
      the end user especially when 24 lines of "...CRITICAL..." took up the entire
      screen. Thus, the issue is filed as P2.

      Steps to reproduce:
      -------------------
      1) Install the build using the default values
      2) Invoke <install-dir>/bin/updatetool
      3) Select Help->Contents
      4) Observe that the console displays about 24 lines of the above error.

      Users saw this on Solaris 10 SPARC as well.

      Show
      ckamps added a comment - Build: GFv3Prelude build 19 OS: Solaris 10 X86 U5 Encountered the following repeated lines of the same error (about 24 lines) on the console screen where updatetool was launched when Help->Contents is selected from the GUI: (python:1678): CRITICAL **: file blueprint-draw.c: line 81: assertion `GTK_WIDGET (widget)' failed Note: Although "Help->Content" is working, the error message is very visible to the end user especially when 24 lines of "...CRITICAL..." took up the entire screen. Thus, the issue is filed as P2. Steps to reproduce: ------------------- 1) Install the build using the default values 2) Invoke <install-dir>/bin/updatetool 3) Select Help->Contents 4) Observe that the console displays about 24 lines of the above error. Users saw this on Solaris 10 SPARC as well.
      Hide
      ckamps added a comment -

      Note that under other situations, other GTK errors (WARININGs) show up:

      https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=419

      Show
      ckamps added a comment - Note that under other situations, other GTK errors (WARININGs) show up: https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=419
      Hide
      ckamps added a comment -

      As Manpreet noted in today's i-team call, this issue is the result of a known
      bug in Solaris 10:

      http://bugs.opensolaris.org/bugdatabase/printableBug.do?bug_id=6480242

      This issue was apparently filed back in 2006, but it does not appear to have
      been fixed.

      It does not have any negative impact on the function being performed, but it is
      a nuisance to the end user that launches the tool from the command line. People
      running the Update Tool from a file manager and from the desktop will not see
      these messages because a terminal window will not be present in those cases.

      For the Update 1 release, we'll look into how we might be able to hide such
      nuisance messages yet still allow useful remote x display messages and such
      through to the terminal. i.e. it's not as simple as redirecting all terminal
      output to a file or to /dev/nul.

      In the meantime, we'll release note this issue for 2.0.

      Show
      ckamps added a comment - As Manpreet noted in today's i-team call, this issue is the result of a known bug in Solaris 10: http://bugs.opensolaris.org/bugdatabase/printableBug.do?bug_id=6480242 This issue was apparently filed back in 2006, but it does not appear to have been fixed. It does not have any negative impact on the function being performed, but it is a nuisance to the end user that launches the tool from the command line. People running the Update Tool from a file manager and from the desktop will not see these messages because a terminal window will not be present in those cases. For the Update 1 release, we'll look into how we might be able to hide such nuisance messages yet still allow useful remote x display messages and such through to the terminal. i.e. it's not as simple as redirecting all terminal output to a file or to /dev/nul. In the meantime, we'll release note this issue for 2.0.
      Hide
      Tom Mueller added a comment -

      Moved to B17 per iteam on Oct 14.

      Show
      Tom Mueller added a comment - Moved to B17 per iteam on Oct 14.
      Hide
      Joe Di Pol added a comment -

      I have verified that the 2.8.9.1 version of wxPython does not
      fix this. We will not be addressing this in 2.1, so I am
      deferring to a future release.

      Show
      Joe Di Pol added a comment - I have verified that the 2.8.9.1 version of wxPython does not fix this. We will not be addressing this in 2.1, so I am deferring to a future release.
      Hide
      Joe Di Pol added a comment -
          • Issue 930 has been marked as a duplicate of this issue. ***
      Show
      Joe Di Pol added a comment - Issue 930 has been marked as a duplicate of this issue. ***

        People

        • Assignee:
          Joe Di Pol
          Reporter:
          Snjezana Sevo-Zenzerovic
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated: