Firefox fails to start when pcscd is running and a security token is present.

Bug #493753 reported by slestak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox-3.5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: firefox-3.5

If PC/SC Lite is automatically started on boot, Firefox will not start. If /etc/init.d/pcscd stop (PC/SC Lite's RC) is issued, Firefox will then start and /etc/init.d/pcscd start can be issued without a problem. In addition to this workaround, if the line "hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4" in /etc/nsswitch.conf is commented out, Firefox will start with pcscd already running. The real problem seems to be related to current NSS functionality embedded within Firefox-3.5.5 (and older). This problem, although workable, causes the use of hardware security tokens and Firefox-3.5.5 to be more confusing, time consuming, and may cause users to further abandon the use of security tokens in Firefox.

Ubuntu 9.10.1
pcscd-1.5.3-1ubuntu1
Firefox-3.5.5+nobinonly-0ubuntu0.9.10.1

ProblemType: Bug
Architecture: amd64
Date: Mon Dec 7 11:50:10 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.5+nobinonly-0ubuntu0.9.10.1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: firefox-3.5
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2429): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2429): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2533): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2582): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:2529): Gdk-CRITICAL **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed

Revision history for this message
slestak (slestak) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.