[Bug 743445] New: After hal package update pcscd no longer automatically activated at startup
https://bugzilla.novell.com/show_bug.cgi?id=743445 https://bugzilla.novell.com/show_bug.cgi?id=743445#c0 Summary: After hal package update pcscd no longer automatically activated at startup Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Bernd.Giesen@gmx.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 After an automatically received update of my openSuSE 11.3 x86_64 "hal" package from v0.5.14-9.1.1-x86_64 up to v0.5.14-9.3.1-x86_64 I have the problem, that the pcscd daemon is mostly no longer automatically activated/started on system startup, even if it is configured (and has never been changed!) in the runlevel editor for runlevel 2,3 and 5 as well. This makes me unable to use my PC/SC controlled CyberJack chipcard reader. However, it seems to be a timing issue: in about 2% of all system startups the pcscd is yet loaded. In the /var/log/messages file I noticed the following messages concerning this matter: Jan 22 18:50:29 linux-pc pcscd: hotplug_libhal.c:562:HPRegisterForHotplugEvents() Could not initialise connection to hald. Jan 22 18:50:29 linux-pc pcscd: hotplug_libhal.c:563:HPRegisterForHotplugEvents() Normally this means the HAL daemon (hald) is not running or not ready. Jan 22 18:50:29 linux-pc pcscd: pcscdaemon.c:531:main() SVCServiceRunLoop returned Additionally, I noticed that sometimes also my ALSA sound driver is not loaded properly on startup, so I don't hear any system sound (in my KDE screen I'm getting a message box telling me that my "preferred output device for category "music" could not be detected). Also here, after manually reinstalling the previous "hal" package (0.5.14-9.1.1-x86_64), the problem disappeared as well. And again, this seems to be a timing issue: After manually reinstalling the previous "hal" package (0.5.14-9.1.1-x86_64), all works well again as before. The problems are reproducable, that means, installing v0.5.14-9.3.1-x86_64 let them occur again. My actual system configuration is: openSuSE 11.3 x86_64 / KDE 4.4.4 ("release 3"), 4 GB RAM Kernel 2.6.34.10-0.4-desktop using glibc 2.11.2-3.7.1.x86_64 pcsc-lite1 resp. libpcsclite1 32/64 bit 1.5.5-7.3.1 pcsc-cyberjack 3.99.5final.SP03-1.suse11.3 (3.3.5-1.26) Reproducible: Sometimes Steps to Reproduce: 1.Update from "hal" package v0.5.14-9.1.1-x86_64 to v0.5.14-9.3.1-x86_64 2.Reboot the system 3.In most cases pcscd is no longer automatically activated at startup. Actual Results: In most cases (98% of all system startups) pcscd is no longer automatically activated at startup. Expected Results: I would expect that the pcscd is automatically started on boot-up as before the hal update -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=743445 https://bugzilla.novell.com/show_bug.cgi?id=743445#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |wolfgang@rosenauer.org |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=743445 https://bugzilla.novell.com/show_bug.cgi?id=743445#c1 Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bili@suse.com --- Comment #1 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-01-28 19:46:22 UTC --- It seems the only change in the hal package was that $remote_fs has been added to the init script Required-Start. That probably means hal gets started later than before. On the other side pcsc-lite has "hal" in Should-Start and therefore hal should also get started before pcsc-lite. I'm not sure where the real issue hides or can be fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=743445 https://bugzilla.novell.com/show_bug.cgi?id=743445#c2 Li Bin <bili@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Li Bin <bili@suse.com> 2012-02-02 06:57:47 UTC --- Bernd, The reason that I re-add it is bnc#487190. And I don't why it affects the pcscd. A little weird. the pcscd also need "$remote_fs" as 'Required-Start'. And now 11.3's update channel already closed in official, so we can't provide the updates any more. If you don't mind just use the v0.5.14-9.1.1-x86_64. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=743445 https://bugzilla.novell.com/show_bug.cgi?id=743445#c3 --- Comment #3 from Bernd Giesen <Bernd.Giesen@gmx.net> 2012-02-02 19:36:37 UTC --- Whyever you it, fact is, that providing the v0.5.14-9.3.1-x86_64 update makes the hal package no longer working correctly! So, from my point of view as a customer/user the update did not fix a bug but produced (a new?) one. This is not satisfying! Moreover, it's a little bit disappointing for me, that you simply limit yourself to the statement, that openSuSE 11.3 is no longer supported, rather than to help fixing the issue, that did not exist before! Sorry, but that's my opinion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com