Bug 66254 - self.setArrorCursor() typo in up2date
Summary: self.setArrorCursor() typo in up2date
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date   
(Show other bugs)
Version: 7.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2002-06-06 19:56 UTC by Jim Wright
Modified: 2015-01-07 23:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-26 02:47:51 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jim Wright 2002-06-06 19:56:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Description of problem:
% /usr/sbin/up2date

Traceback (innermost last):
  File "/usr/share/rhn/up2date_client/gui.py", line 832, in doInstallation
AttributeError: setArrorCursor

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.% /usr/sbin/up2date

Additional info:

I presume that "self.setArrorCursor()" really ought to be "self.setArrowCursor()".

I believe everything worked and install was successful.  I got the latest kernel
and grub was updated (but not lilo, sigh).  however, the hourglass cursor is
still present on the gui which gives the impression that it crashed prior to

Comment 1 Jim Wright 2002-06-06 20:04:42 UTC
forgot to mention.  the gui is left with only the "cancel" button enabled.  the
back and next buttons are not enabled.  which furthers the impression that the
packages were not fully installed.  (but I think they were.)

% rpm -V kernel-source-2.4.9-34 kernel-doc-2.4.9-34 kernel-debug-2.4.9-34
kernel-2.4.9-34 kernel-headers-2.4.9-34
S.5....T   /boot/kernel.h-2.4.9

so yes, I think everything was installed fine.

Comment 2 jdalbec 2002-06-07 02:45:49 UTC
This typo is in the CommunicationError exception handler.  The last log message
I see says "Removing packages from package profile: [...]" so the
CommunicationError would have been raised in remoteDelPackages.  Could this be
related to the fact that the server disabled free service at about that time? 
Is there any way to "grandfather" currently running up2date sessions when that
happens?  Anyway, it looks like the packages installed successfully, but RHN
could not be notified of this fact.

Comment 3 Adrian Likins 2002-06-13 20:41:42 UTC
This (the typo) should be fixed in the next versions.

When the servers start throttling live users, it is
done at login time. Existing up2date sessions that
have valid authentication tokens should be fine
for the duration of the token time. 

It possible that a connnection was possibly
dropped at this time do to time outs. Generally
servers only get throttled when we are 100% bandwitdth
utilization, so it's possible.

Comment 4 Jim Wright 2002-10-26 02:47:44 UTC
I presume this can be closed.

Comment 5 Jim Wright 2002-12-03 20:26:50 UTC
up2date-2.8.39-1.7.2 has this fixed

Note You need to log in before you can comment on or make changes to this bug.