updatecenter2
  1. updatecenter2
  2. UPDATECENTER2-961

On Mac OS X, trying to stop the notifier hangs the terminal window

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: B18
    • Fix Version/s: B34
    • Component/s: notifier
    • Labels:
      None
    • Environment:

      Operating System: Mac OS X
      Platform: Macintosh

    • Issuezilla Id:
      961
    • Tags:

      Description

      I have updated defaults.cfg and changed the attribute check_at_start value to True

      I have restarted the notifier :

      1. updatetool --notifier --shutdown
      2. updatetool – notifier

      The notifier highlighted some updates, I launched the updatetool by clicking on
      the notifier balloon

      Once again, I edited defaults.cfg file and atted 2 attributes for security updates

      I also set the logging level to DEBUG

      I saved the file ,and retried to relaunch the notifier.

      This time the updatetool --notifier --shutdown did not return

      I checked the running python processes, there was 2 processes running.

      I exited the updatetool, then one process remains.

      There is no Error in the logfile, only some warnings.

      1. defaults.cfg
        0.9 kB
        faouzia
      2. error_log.txt
        2 kB
        faouzia

        Activity

        Hide
        Chris Kasso added a comment -

        Fixed in r2287.

        When the --shutdown option is passed to the updatetool script we bypass using
        the .app on OS X. This avoids the hang. But when we bypass the .app we can't
        initialized WX as that attempts to open the display which gets blocked. Unlike
        wxwidget there is no Initialize method to initialized WX without opening a
        display connection. Why do we need to initialized WX? We use WX methods to
        locate the USERAPPDIR on OS X. So we have had to put conditional code in the
        ipc service to test whether a display is available and if we are on OS X. If
        that is a case we use pure python methods to determine the USERAPPDIR.

        Show
        Chris Kasso added a comment - Fixed in r2287. When the --shutdown option is passed to the updatetool script we bypass using the .app on OS X. This avoids the hang. But when we bypass the .app we can't initialized WX as that attempts to open the display which gets blocked. Unlike wxwidget there is no Initialize method to initialized WX without opening a display connection. Why do we need to initialized WX? We use WX methods to locate the USERAPPDIR on OS X. So we have had to put conditional code in the ipc service to test whether a display is available and if we are on OS X. If that is a case we use pure python methods to determine the USERAPPDIR.
        Hide
        faouzia added a comment -

        Hi Chris Kasso,
        I verified this issue on MAC-OS X
        I was able to shutdown and restart the notifier from the same Terminal Window
        and different terminal windows with the same user image several times without
        facing the hang

        But, I tried the following scenario (also linked to this issue) :

        • Launch updatetool from a B34 User image
        • Open an other terminal and try to launch updatetool from the same user image
          directory

        the bin/updatetool command did not return with a message " updatetool is
        already running" like this is the case for other platforms.

        Do you suggest I reopen this issue or file a separate one for that problem ?

        Thanks

        Show
        faouzia added a comment - Hi Chris Kasso, I verified this issue on MAC-OS X I was able to shutdown and restart the notifier from the same Terminal Window and different terminal windows with the same user image several times without facing the hang But, I tried the following scenario (also linked to this issue) : Launch updatetool from a B34 User image Open an other terminal and try to launch updatetool from the same user image directory the bin/updatetool command did not return with a message " updatetool is already running" like this is the case for other platforms. Do you suggest I reopen this issue or file a separate one for that problem ? Thanks
        Hide
        faouzia added a comment -

        Testing on B37 shows that this issue is still reproducible on MAC-OS X

        I faced a hang when trying the follwoing commands from the same user image from
        which the notifier was launched :

        updatetool -n --shutdown
        updatetool -n --help
        updatetool -n --version

        I am reopening this issue

        Show
        faouzia added a comment - Testing on B37 shows that this issue is still reproducible on MAC-OS X I faced a hang when trying the follwoing commands from the same user image from which the notifier was launched : updatetool -n --shutdown updatetool -n --help updatetool -n --version I am reopening this issue
        Hide
        Chris Kasso added a comment -

        I can not reproduce the issue. If you have a reproducible case please include
        it in the bug report.

        It wasn't clear from the note which command hung:

        updatetool -n --shutdown
        updatetool -n --help
        updatetool -n --version

        All or just --help and --version?

        Show
        Chris Kasso added a comment - I can not reproduce the issue. If you have a reproducible case please include it in the bug report. It wasn't clear from the note which command hung: updatetool -n --shutdown updatetool -n --help updatetool -n --version All or just --help and --version?
        Hide
        faouzia added a comment -

        I retried using B38, and have not faced this issue
        I will set it as verified.

        Show
        faouzia added a comment - I retried using B38, and have not faced this issue I will set it as verified.

          People

          • Assignee:
            Chris Kasso
            Reporter:
            faouzia
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: