** Changed in: zaptel (Debian)
Status: Won't Fix = Fix Released
--
Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'
https://bugs.launchpad.net/bugs/64059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: zaptel (Debian)
Status: New = Won't Fix
--
Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'
https://bugs.launchpad.net/bugs/64059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Debdiff for Karmic attached.
nlinux: are you able to apply this diff and build to test it functions
as it should before I upload. (should apply against Jaunty also)
Thanks
** Attachment added: karmic-debdiff
http://launchpadlibrarian.net/28256470/karmic-debdiff
--
Wrong device-names in
I'll be testing this in the lab sometime this week, is there any
additional data that you need logged?
Also, is this debdiff hardy compatible as well? If I remember correctly
I had to manually adjust this the last time I did an install.
--
Wrong device-names in udev - Unable to open master
The last patch, autoudev, in that thread fixed the problem correctly. I
would suggest packaging up and including it.
Thanks again for the quick response,
Mark
On Fri, Jun 19, 2009 at 9:42 PM, Stefan Lesicnik ste...@lsd.co.za
wrote:
nlinux: Could you try the fix described here and let us
This bug is still valid, I'm seeing this exact problem with a fresh
Jaunty install, but the fix is not working. No idea how to get rid of
the wrong /dev/zapctl and get the correct /dev/zap/ctl at thispoint. :(
** Changed in: zaptel (Ubuntu)
Status: Invalid = Confirmed
--
Wrong
nlinux: Could you try the fix described here and let us know...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495459
Thanks!
--
Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'
https://bugs.launchpad.net/bugs/64059
You received this bug notification because you are a
