Red Hat Bugzilla – Bug 178251
debug output appears for up2date on ia64
Last modified: 2007-11-30 17:07:22 EST
+++ This bug was initially created as a clone of Bug #175755 +++
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111
Description of problem:
On ia64 only:
Run up2date --configure with up2date-4.4.56-3 and up2date-gnome-4.4.56-3
This is the output (before the GUI pops up):
[root@test01-ia64 up2date]# up2date --configure
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 32790
debug1: channel 1: new [x11]
debug1: confirm x11
None of the other architectures have any debug output.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install up2date-4.4.56-3 and up2date-gnome-4.4.56-3 on RHEL 3 U6.
2. Run up2date --configure
Actual Results: See "debug1" output in Description.
Expected Results: No output, just the GUI.
-- Additional comment from email@example.com on 2006-01-16 16:46 EST --
that output isn't coming from up2date, looks like maybe gtk or X11 debug info.
What happens if you run /usr/sbin/up2date instead of /usr/bin/up2date? Might
be userhelper spew... (aka, if /usr/bin/up2date shows the spew, but
/usr/sbin/up2date does not, it's "userhelper").
If both show it, which it might, then I'm not sure wheres it's coming from, but
up2date isn't printing it directly.
-- Additional comment from firstname.lastname@example.org on 2006-01-18 15:34 EST --
/usr/bin/up2date shows the debug output
/usr/sbin/up2date shows the debug output
does this show up on all ia64 boxes? or just that one host?
whats the X setup on that box?
I'm not able to reproduce this, and I'm 99.99% sure this is coming
from X and not up2date (it doesn't have these strings anywhere in it's
QA Engineer made an error in testing. The fix is fine.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.