trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2010

Wireless messages in xsession logs

From: Darrell Anderson <humanreadable@...>
Date: Tue, 21 Sep 2010 10:17:41 -0700 (PDT)
I was browsing through KControl and selected the Wireless Network module. I later saw the following messages in the xsession-errors log:

QComboBox::setCurrentItem: (protocolCombo) Index 5 out of range
QComboBox::setCurrentItem: (aclCompatibilityCombo) Index 3 out of range
QComboBox::setCurrentItem: (maxProtocolCombo) Index 5 out of range
QComboBox::setCurrentItem: (serverSigningCombo) Index 3 out of range
lo        no wireless extensions.
eth0      no wireless extensions.

I don't have wireless configured in any manner. Just a wired connection.

When I selected that module, I received a warning message box four times:

[Sorry - Control Center]
Unable to detect wireless interface.
(OK button)

Four warnings match the number of tabs in the module.

I think that after the user responds to the first message box the remaining three warnings should be quashed.

Unchecking the Autodetect check box does not disable the warning messages.

I don't believe the message warnings add usability value. Possibly a better method would be to provide a message (in each tab of the module) that no connection was detected.

Further, there should be no warning messages if nothing is yet configured.

Second, the QComboBox messages should not appear in the xsession-error messages. The content of those messages indicate some kind of code error, which translates to noise and clutter in the log. Some kind of error trap is needed to quash the messages.

Third, the messages about lo and etho should be prefixed with something like [kcontrol] so users know the source of the messages. Logs are meant to help users, so let's help them. :)

I hope this helps!

Darrell