Bug#588590: Conflicts with nvidia-glx
I have the same trouble with nvidia-glx. I had both nvidia-glx and nvidia-glx-legacy-173xx installed (due to upgrading my video card), and now I can't purge nvidia-glx-legacy-173xx. When I try to purge it, it says: Removing nvidia-glx-legacy-173xx ... Purging configuration files for nvidia-glx-legacy-173xx ... rm: cannot remove `/usr/lib/libGL.so': No such file or directory dpkg-divert: mismatch on package when removing `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-legacy-173xx' found `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx' dpkg: error processing nvidia-glx-legacy-173xx (--purge): subprocess post-removal script returned error exit status 2 configured to not write apport reports Removing nvidia-kernel-legacy-173xx-source ... Errors were encountered while processing: nvidia-glx-legacy-173xx A new version of nvidia-glx-legacy-173xx will not help me, how do I purge the package? Should I manually edit the postrm script? -Ariel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Conflicts with nvidia-glx
Ariel asdeb...@dsgml.com writes: I have the same trouble with nvidia-glx. I had both nvidia-glx and nvidia-glx-legacy-173xx installed (due to upgrading my video card), and now I can't purge nvidia-glx-legacy-173xx. When I try to purge it, it says: Removing nvidia-glx-legacy-173xx ... Purging configuration files for nvidia-glx-legacy-173xx ... rm: cannot remove `/usr/lib/libGL.so': No such file or directory dpkg-divert: mismatch on package when removing `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-legacy-173xx' found `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx' So you have old versions of both nvidia-glx and nvidia-glx-legacy-173xx installed, both of which predate the reworking of how the diversions are handled. I wonder how you managed to get both packages installed at the same time ever. They've always conflicted in their diversions, and I would have expected one or the other to have failed to install. I don't understand how nvidia-glx managed to take over the diversions while leaving nvidia-glx-legacy-173xx in a state where it still thought it owned the diversions. Thankfully, this is one of the problems that will be entirely fixed going forward, with the new shared diversion handling packages. A new version of nvidia-glx-legacy-173xx will not help me, I'm not sure that's true. how do I purge the package? Should I manually edit the postrm script? That's what I'd do. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Conflicts with nvidia-glx
On Tue, 7 Sep 2010, Russ Allbery wrote: Ariel asdeb...@dsgml.com writes: I have the same trouble with nvidia-glx. I had both nvidia-glx and nvidia-glx-legacy-173xx installed (due to upgrading my video card), and now I can't purge nvidia-glx-legacy-173xx. dpkg-divert: mismatch on package when removing `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-legacy-173xx' found `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx' So you have old versions of both nvidia-glx and nvidia-glx-legacy-173xx installed, both of which predate the reworking of how the diversions are handled. I wonder how you managed to get both packages installed at the same time ever. They've always conflicted in their diversions, and I would have expected one or the other to have failed to install. I don't understand how nvidia-glx managed to take over the diversions while leaving nvidia-glx-legacy-173xx in a state where it still thought it owned the diversions. nvidia-glx-legacy-173xx doesn't seem to think it owns the diversions - they are manually removed in the postrm script. And no, I don't know how it got installed this way. Thankfully, this is one of the problems that will be entirely fixed going forward, with the new shared diversion handling packages. Is this uploaded currently, or planned? And does this mean nvidia-glx-legacy-173xx and nvidia-glx can both be installed at the same time? (Although, that's probably not useful since the kernel module can't be.) A new version of nvidia-glx-legacy-173xx will not help me, I'm not sure that's true. I meant, I'm not going to install it because I'm using nvidia-glx now. how do I purge the package? Should I manually edit the postrm script? That's what I'd do. OK. Thank you. -Ariel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Conflicts with nvidia-glx
Ariel asdeb...@dsgml.com writes: On Tue, 7 Sep 2010, Russ Allbery wrote: So you have old versions of both nvidia-glx and nvidia-glx-legacy-173xx installed, both of which predate the reworking of how the diversions are handled. I wonder how you managed to get both packages installed at the same time ever. They've always conflicted in their diversions, and I would have expected one or the other to have failed to install. I don't understand how nvidia-glx managed to take over the diversions while leaving nvidia-glx-legacy-173xx in a state where it still thought it owned the diversions. nvidia-glx-legacy-173xx doesn't seem to think it owns the diversions - they are manually removed in the postrm script. That's what I mean by own. As long as those diversions weren't removed, nvidia-glx should never have been installable, and if those diversions were removed, that should have been followed by removing the postrm script... oh. Oh, I get it. You removed the package but didn't purge it, and the postrm script removes the diversions on both remove and purge. Aie. Yeah. I see how you got into that situation. I don't think there's any good solution at this point other than commenting out the dpkg-divert invocations in the postrm script and then purging the package. Thankfully, once someone upgrades to one of the new packages, this problem should be impossible to create. Thankfully, this is one of the problems that will be entirely fixed going forward, with the new shared diversion handling packages. Is this uploaded currently, or planned? Already in the archive for nvidia-glx, in NEW for the legacy package. And does this mean nvidia-glx-legacy-173xx and nvidia-glx can both be installed at the same time? Not yet, but it makes it possible eventually. (Although, that's probably not useful since the kernel module can't be.) Yeah, that's still a problem. A new version of nvidia-glx-legacy-173xx will not help me, I'm not sure that's true. I meant, I'm not going to install it because I'm using nvidia-glx now. Oh, I see. But yes, the more I think about it, the more I think you're right: trying to upgrade the package won't help. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Conflicts with nvidia-glx
On Tue, 7 Sep 2010, Russ Allbery wrote: Ariel asdeb...@dsgml.com writes: On Tue, 7 Sep 2010, Russ Allbery wrote: That's what I mean by own. As long as those diversions weren't removed, nvidia-glx should never have been installable, and if those diversions were removed, that should have been followed by removing the postrm script... oh. Oh, I get it. You removed the package but didn't purge it, and the postrm script removes the diversions on both remove and purge. Aie. Yeah. That makes a lot of sense, I went back and forth between the packages at one point. I wonder if this is in any way related to bug #366910 (which I reported), either that this explains it, or that my fix made it worse. And does this mean nvidia-glx-legacy-173xx and nvidia-glx can both be installed at the same time? Not yet, but it makes it possible eventually. (Although, that's probably not useful since the kernel module can't be.) Yeah, that's still a problem. I assume no one is current attempting to change this. But is it a goal for the future, or is it just too much trouble? (It would be nice, so I can have multiple monitors, since I already have the card. But then again new low end nvidia cards are not very expensive.) BTW, thanks for your help (and the packages). -Ariel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Conflicts with nvidia-glx
On 2010-09-07 11:12, Ariel wrote: I have the same trouble with nvidia-glx. I had both nvidia-glx and nvidia-glx-legacy-173xx installed (due to upgrading my video card), and now I can't purge nvidia-glx-legacy-173xx. How did you manage to install both? They should have been conflicting forever. What problematic versions do you currently have installed? A new version of nvidia-glx-legacy-173xx will not help me, how do I purge the package? Should I manually edit the postrm script? Can you try to purge nvidia-glx first and reinstall it (using the current version) later after you got rid of nvidia-glx-legacy-173xx? After fixing your nvidia setup you may want to reinstall libgl1-mesa-glx and libgl1-mesa-dev (if you had them installed), because messing with the diversions might have lost/corrupted the original files. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Bug#588590: Conflicts with nvidia-glx
On 2010-09-07 11:47, Ariel wrote: And does this mean nvidia-glx-legacy-173xx and nvidia-glx can both be installed at the same time? Not yet, but it makes it possible eventually. (Although, that's probably not useful since the kernel module can't be.) Yeah, that's still a problem. I assume no one is current attempting to change this. But is it a goal for the future, or is it just too much trouble? (It would be nice, so I can have multiple monitors, since I already have the card. But then again new low end nvidia cards are not very expensive.) What are you trying to do? Run two cards in one machine using two different versions of the driver? That won't work. Having multiple versions of the libraries installed would only be useful if there was some automatic way that detects the the card and configures the system to use the correct kernel module and libraries and Xorg driver. As we don't have this, we just let you install one variant and that tries to have strict dependencies so that you don't run into trouble mixing the variants/versions or missing some pieces. So without a real use case I don't see a need for allowing multiple nvidia-glx variants to coexist. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Conflicts with nvidia-glx
On Tue, 7 Sep 2010, Andreas Beckmann wrote: On 2010-09-07 11:12, Ariel wrote: I have the same trouble with nvidia-glx. I had both nvidia-glx and nvidia-glx-legacy-173xx installed (due to upgrading my video card), and now I can't purge nvidia-glx-legacy-173xx. How did you manage to install both? They should have been conflicting forever. What problematic versions do you currently have installed? Russ Allbery figured it out (I think). I uninstalled nvidia-glx-legacy-173xx, but did not purge it. Then installed nvidia-glx and then nvidia-glx-legacy-173xx, I'm not certain exactly how but I ended up with both, and I was housecleaning and tried to remove nvidia-glx-legacy-173xx because I don't need it anymore. I have nvidia-glx 190.53-4, and a removed, but not purged, version of nvidia-glx-legacy-173xx. A new version of nvidia-glx-legacy-173xx will not help me, how do I purge the package? Should I manually edit the postrm script? Can you try to purge nvidia-glx first and reinstall it (using the current version) later after you got rid of nvidia-glx-legacy-173xx? I can't install the current version of nvidia-glx because it depends on a more recent dpkg, and I can't update dpkg because of a VERY long chain of depends that include openoffice, python, and kde. And I don't want to update kde till squeeze is released. After fixing your nvidia setup you may want to reinstall libgl1-mesa-glx and libgl1-mesa-dev (if you had them installed), because messing with the diversions might have lost/corrupted the original files. I did reinstall libgl1-mesa-glx, but I couldn't reinstall nvidia-glx because I don't have a deb for it, but I did run debsums to verify the checksums and everything seems OK. -Ariel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Bug#588590: Conflicts with nvidia-glx
Andreas Beckmann deb...@abeckmann.de writes: On 2010-09-07 11:12, Ariel wrote: I have the same trouble with nvidia-glx. I had both nvidia-glx and nvidia-glx-legacy-173xx installed (due to upgrading my video card), and now I can't purge nvidia-glx-legacy-173xx. How did you manage to install both? They should have been conflicting forever. What problematic versions do you currently have installed? Just in case my previous explanation was too stream-of-consciousness to follow, the basic problem is that a conflict removes but doesn't purge. So there weren't any files left from nvidia-glx-legacy-173xx, but the maintainer script was still there and trying to remove the diversions on a subsequent purge. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Bug#588590: Conflicts with nvidia-glx
On Tue, 7 Sep 2010, Andreas Beckmann wrote: On 2010-09-07 11:47, Ariel wrote: I assume no one is current attempting to change this. But is it a goal for the future, or is it just too much trouble? (It would be nice, so I can have multiple monitors, since I already have the card. But then again new low end nvidia cards are not very expensive.) What are you trying to do? Run two cards in one machine using two different versions of the driver? That won't work. Yes, exactly. It won't work because it can't, or because it's not written to handle this (but could be)? So without a real use case I don't see a need for allowing multiple nvidia-glx variants to coexist. The use case is I had an old card. I bought a new one, and now I want to use both so I can have 3 monitors. Obviously the kernel module has to support two versions at once first, so I'm not asking for multiple nvidia-glx variants if the kernel part is not possible. I actually wasn't asking for anything, I was just wondering if a: it was possible, and b: if anyone who understood the driver even had it on some future wishlist, or if it's not something that was even considered. -Ariel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588590: [pkg-nvidia-devel] Bug#588590: Bug#588590: Bug#588590: Conflicts with nvidia-glx
Ariel asdeb...@dsgml.com writes: On Tue, 7 Sep 2010, Andreas Beckmann wrote: What are you trying to do? Run two cards in one machine using two different versions of the driver? That won't work. Yes, exactly. It won't work because it can't, or because it's not written to handle this (but could be)? I'm pretty sure the NVIDIA kernel modules aren't bright enough to handle this case. I think I tried to do something like that before with someone's system that had two cards of different vintages, and the kernel modules conflict with each other. I haven't tried recently, though, and I may be misremembering. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
