Red Hat Bugzilla – Bug 127807
pam-panel-icon opens window on dual-head configuration
Last modified: 2013-07-02 19:01:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040620
Description of problem:
When running a dual-head configuration (laptop with TV-out, and each
displaying a unique X desktop), the pam-panel-icon opens an empty
window (titled "Authentication Indicator"). It also appears in the
tasklist with the same name. When root authentication is made, the
"Authentication Indicator" window displays the keys icon.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Configure dual-head display
3.Observe "Authentication Indicator" in taskbar and small window on
Actual Results: Window opens, taskbar shows "Authentication
Indicator", keys icon displays in window.
Expected Results: No window, "Authentication Indicator" hidden from
taskbar, keys icon appears in system tray.
This is very confusing for a user. The application can't be killed
(it auto-restarts), and identifying the process for bug reporting is
See similar bug 127808 for eggcups.
This bug is corrected in rawhide (currently FC3T3). Resolved.
I'm currently using Fedora Core 3 Test 3 and this problem has *not*
been corrected. I've always experienced it since the start of the
Fedora project and before. It seems as though the problem appears when
xorg.conf (and whatever that file used to be called...) is edited,
which can be pretty commmon if someone installed X without dual-head
support and wants to enable it later and vice versa.
I tested this with a clean install of FC3T3 (freshly partitioned and
mke2fs hard drive). The installation was single head, and I edited
xorg.conf to the configuration I had when the problem was first
reported - I actually copied the backup dual-head configuration back
to /etc/X11. Dual-head operation no longer causes the problem, for me.
If you installed over an existing installation, it's possible that an
existing configuration file is triggering the problem. I suggest
adding a new user and logging in to that after restarting X. If the
problem doesn't occur, then a configuration file in your home
directory is the cause. If it does occur, then a system file is the
culprit. Either way it will be difficult and very time consuming to