Comment 36 for bug 67532
Revision history for this message
| Niklas Edmundsson (niklas-edmundsson) wrote | #36 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This is a machine upgraded from edgy, and doing dpkg-reconfigure libgphoto2-2 indeed gives me a correct 45-libgphoto2.rules that has the comment about being for a new udev version.
I suspect that when doing an upgrade it's still running the old udev-version, and thus generates the file for the old version. When the machine finally gets around to running the new udev version (it might even take a reboot, I don't really know) it obviously will not work.
The kludge for the moment is of course doing dpkg-reconfigure on libgphoto2-2, I was too tired and frustrated to even think of that.
In the long run this should really be fixed in some sane way, you really shouldn't be expected to do dpkg-reconfigure on various packages in order for stuff to work after an upgrade.