Hey Padraig.

On Wed, 2010-02-03 at 08:18 +0000, Padraig O'Briain wrote:
> The webrev, http://cr.opensolaris.org/~padraig/ips-14269-v1/, fixes
> 14269 Add More Software utility crashes in build 131, losing all selections
> 
> The webrev avoids the backtrace reported by the bug submitter. I have 
> not been able to reprpduce this problem but the bug submitter has 
> confirmed that this patch fixes the problem for him.

I saw that bug go by in d.o.o. the other day and I was able to reproduce
the problem on occasion, but only with gate; not build 131. Anyhoo, I
just pulled the latest gate which includes your fix for this bug.
Instead of the old traceback, I now get this one (presented in the
Unexpected Error dialog):

Error details:
Traceback (most recent call last):
  File "/usr/bin/packagemanager", line 5825, in run_with_except_hook
    run_old(*rweh_args, **rweh_kwargs)
  File "/usr/lib/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/bin/packagemanager", line 4622, in __show_package_info
    True)
  File "/usr/lib/python2.6/vendor-packages/pkg/gui/misc.py", line 428, in 
get_pkg_info
    frozenset([api.PackageInfo.LICENSES]))
  File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 1382, in 
info
    self.__acquire_activity_lock()
  File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 230, in 
__acquire_activity_lock
    raise api_errors.ImageLockedError()
ImageLockedError: The image cannot be modified as it is currently in use by 
another package client.

List of configured publishers:
P       O       opensolaris.org (http://pkg-na-2.opensolaris.org/dev/)
P       O       opensolaris.org (http://pkg.opensolaris.org/dev/)
D       O       contrib.opensolaris.org (http://pkg.opensolaris.org/contrib/)
E       O       extra (https://pkg.sun.com/opensolaris/extra/)
E       O       localhost (http://localhost:80/)

pkg version:
c4bc1f90b903

Note that I am running PM as a privileged user and that I verified that
I am not running any other instances of a package client -- unless you
could updatemanager running in the background like it usually does.

As for how to reproduce the problem: It seems to be a timing issue as I
can maximize the likelihood of getting the error to occur if I mark
packages rather quickly while PM is still fetching the package info for
the packages displayed in the list.

Shall I open a new bug?
--joanie


_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to