p910nd does not run in server mode after reboot

Bug #548739 reported by Alexander Zolotko
2
Affects Status Importance Assigned to Milestone
p910nd (Debian)
Invalid
Undecided
Unassigned
p910nd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: p910nd

After system reboot p910nd does not start because it trying to get lock on "/var/lock/p9100/p9100" file (in upstream "/var/lock/subsys/p9100"), but because of tmpfs nature of /var/lock directory there is no "/var/lock/p9100" ("/var/subsys/p9100") dir after reboot.

Revision history for this message
Alexander Zolotko (azolotko) wrote :
description: updated
Revision history for this message
Alexander Zolotko (azolotko) wrote :

There is a fix in 0.93-2 version of package for Lucid Lynx:
https://launchpad.net/ubuntu/+source/p910nd/0.93-2

Please, backport it to Karmic.

Changed in p910nd (Debian):
status: New → Invalid
Revision history for this message
Alexander Zolotko (azolotko) wrote :

Debian also has a fix already.

description: updated
Changed in p910nd (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package p910nd - 0.95-1

---------------
p910nd (0.95-1) unstable; urgency=low

  * New upstream version
  * Standards-Version bumped to 3.9.2 (no changes needed)
  * Remove patch 60-fix-sin-addr-sockaddr.patch (upstream applied)
  * Add 50-use-var-lock-p910nd-instead-off-var-lock-subsys.patch:
    - Use /var/lock/p910nd instead of /var/lock/subsys
      (Closes: #634225) (LP: #884658) (LP: #548739)
 -- Ubuntu Archive Auto-Sync <email address hidden> Mon, 28 Nov 2011 13:42:11 +0000

Changed in p910nd (Ubuntu):
status: Invalid → Fix Released
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.