Red Hat Bugzilla – Bug 174041
gdm should not log unknown opcodes as an error
Last modified: 2007-11-30 17:11:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; MSIE 6.0; Windows; U; AIIEEEE!; Win98; Windows 98; en-US; Gecko masquerading as IE; should it matter?; rv:1.8b) Gecko/20050217
Description of problem:
gdm records unknown xdmcp opcodes as an error.
It should just ignore them or log them as informative (LOG_INFO) messages.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.wait an hour or so
3.less /var/log/messages (depending on your syslog config)
Actual Results: gdm: gdm_xdmcp_decode_packet: Unknown opcode from host xxxx
Expected Results: That message should only appear whereever LOG_INFO messages are directed.
It is not an error.
Created attachment 121426 [details]
Disables pointless error messages about unknown opcodes
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
applicable to FC6
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)
Still experiencing the problem in FC7.
Given that I attached a patch to fix it, and given that it amounts to just a
couple of lines, perhaps it would require less effort to preemptively fix the
problem than to preemptively close the bug!
Thank you in retrospect.
Comment 4 was a bulk message. You're patch fell through the cracks. Sorry
Looking at the code, this problem has already been fixed in a different way in
I'm going to close this RAWHIDE, but if you end up with spurious xdmcp log
messages again, feel free to reopen this report and we can investigate.
(In reply to comment #6)
> You're patch ...
You're == you are
your == owned by you
You misspelled 'pwned'