4 ms·

Well the problem is it sounds like you are dealing with a proprietary gl package. Which sucks because the package mangers can't do anything about that. Blame yo

Well the problem is it sounds like you are dealing with a proprietary gl package. Which sucks because the package mangers can't do anything about that. Blame your graphics chip provider. You wouldn't have this problem if you didn't give up your freedoms to mega corps (only some snark).

mehrdadn 9y ago
Which of these packages is proprietary? I was doing this in VirtualBox without guest additions installed, and while I used to boot this installation on an NVIDIA system, I don't believe I had any NVIDIA-specific packages on it. Let me know the proprietary package name(s) you think I had and I'll search to see if I had any of them installed.
- SolarNet 9y ago
  Well there is your problem. You have the NVIDIA graphics drivers / GL shim "installed". Likely manually because that's the only way they can be used (maybe your distribution did it automatically, but I find that doubtful); you can tell you did it through this simple question: did you use the video card's acceleration at any point? if you did (and I assume you did, since you called it a system by the brand of your video card) you have effectively told your package manager (probably through some "convenient" NVIDIA provided "installer" script): "I really really want this package and do whatever other proprietary shit this script I didn't read thought was a good idea (like maybe put it into the system with some bizarre name) on a system that will always have this NVIDIA card in it" And now you are trying to upgrade to something (the proper mesa gl library) which conflicts with that request. But because the package you "installed" has no information (because it's not a real package; because it's a bundle of proprietary code that NVIDIA refuses to properly support) the package manager can't really help you (it can't remove a package it doesn't know how to, so it can't remove the dependencies it's providing, so it can't add a new package with the same provided dependencies). You have to undo whatever shit that script did before you can proceed with a stable system. Also note, what you are trying, is basically impossible with a Windows system (e.g. installing an arbitrary video driver; moving a system - without re-installation - from hardware to a virtual box system, or even hardware to hardware). So if it doesn't work... it's not like you had any other options anyway. NVIDIA assumes the Windows paradigm here, the open source systems you bludgeon with their proprietary code can do nothing to stop the bad actors you force on them from doing bad things. I don't know the list of NVIDIA driver packages off the top of my head, or whatever bizarre shit they did to your installation, and it's not the responsibility of the Linux community to provide tech support for your hardware manufacturer. I had considered trying to be more helpful, and do some cursory research into your problem, but your attitude towards someone else that was being extremely helpful showed you don't want to be helped, you want to angry at someone. We are not your tech support, so I can tell you: Fuck off.
  - mehrdadn 9y ago
    > We are not your tech support, so I can tell you: [expletive] off. 1. I wasn't here to seek tech support at all. The discussion was on package managers and I was sharing an experience I had. Users such as you decided to issue judgments that I must have necessarily ignored apt and broken my system by... installing non-OSS software (?!) without any information on my actual system setup. As I said in the very beginning, I already reverted to my backup. Nowhere did I solicit tech support, and nowhere did I expect any, especially based on almost complete lack of knowledge about the actual system configuration. 2. Flagged. This is the first time I've seen such an attack on HN. And you can imagine I have no interest in replying after this.
    - SolarNet 9y ago
      You were asking to be provided tech support here: > Which of these packages is proprietary? I was doing this in VirtualBox without guest additions installed, and while I used to boot this installation on an NVIDIA system, I don't believe I had any NVIDIA-specific packages on it. Let me know the proprietary package name(s) you think I had and I'll search to see if I had any of them installed. (Also, how would you do that if it was already wiped? Edit 2: yea.... because as not tech support I have read everything you have posted on your problem and am aware you have backups) You were acting pretty entitled to this other person's help here: > What "it" are you even talking about? I didn't "choose to ignore" anything. I Marked all Upgrades, clicked Apply, rebooted when it was finished, went to see if there were any more upgrades (there were some), tried to mark & apply them, and was greeted with this error. Apt/Synaptic got me into this broken state and couldn't get me out of it. I don't know what story you're reading, but it doesn't seem to be what I've been writing. There was nothing for me to ignore. The error wasn't something I ignored; it was the problem. Edit: Oh and that's a perfectly civil response to you continuing to tell people who know how these systems actually work (which does not include you) that they are incapable of understanding what you are writing and implying that they are somehow delusional.
      - mehrdadn 9y ago
        I'll reply to this because you posted it after I was finished editing my reply above, but as I said there, I have no interest in replying to your profanity beyond this: >> You were asking to be provided tech support here: > Which of these packages is proprietary? [...] Let me know the proprietary package name(s) you think I had and I'll search to see if I had any of them installed. I was fact-checking your (unsolicited) diagnosis, which you had already provided despite my lack of request for any kind of support. You made a claim seemingly out of the blue that caught me off-guard (it seemed unfounded and I had neither requested support nor a diagnosis), and in response I said if you wanted to check your facts I would provide you with information to confirm or disprove your (again: unsolicited) diagnosis. I thought maybe you would be interested in seeing whether you are correct. Of course I won't anymore, after your profane verbal abuse. > (Also, how would you do that if it was already wiped?) Because as I said multiple times since the beginning, I had a backup from before the update, which I ended up restoring to. Apparently you are not reading?

mehrdadn 9y ago

Which of these packages is proprietary? I was doing this in VirtualBox without guest additions installed, and while I used to boot this installation on an NVIDIA system, I don't believe I had any NVIDIA-specific packages on it. Let me know the proprietary package name(s) you think I had and I'll search to see if I had any of them installed.

SolarNet 9y ago
Well there is your problem. You have the NVIDIA graphics drivers / GL shim "installed". Likely manually because that's the only way they can be used (maybe your distribution did it automatically, but I find that doubtful); you can tell you did it through this simple question: did you use the video card's acceleration at any point? if you did (and I assume you did, since you called it a system by the brand of your video card) you have effectively told your package manager (probably through some "convenient" NVIDIA provided "installer" script): "I really really want this package and do whatever other proprietary shit this script I didn't read thought was a good idea (like maybe put it into the system with some bizarre name) on a system that will always have this NVIDIA card in it" And now you are trying to upgrade to something (the proper mesa gl library) which conflicts with that request. But because the package you "installed" has no information (because it's not a real package; because it's a bundle of proprietary code that NVIDIA refuses to properly support) the package manager can't really help you (it can't remove a package it doesn't know how to, so it can't remove the dependencies it's providing, so it can't add a new package with the same provided dependencies). You have to undo whatever shit that script did before you can proceed with a stable system. Also note, what you are trying, is basically impossible with a Windows system (e.g. installing an arbitrary video driver; moving a system - without re-installation - from hardware to a virtual box system, or even hardware to hardware). So if it doesn't work... it's not like you had any other options anyway. NVIDIA assumes the Windows paradigm here, the open source systems you bludgeon with their proprietary code can do nothing to stop the bad actors you force on them from doing bad things. I don't know the list of NVIDIA driver packages off the top of my head, or whatever bizarre shit they did to your installation, and it's not the responsibility of the Linux community to provide tech support for your hardware manufacturer. I had considered trying to be more helpful, and do some cursory research into your problem, but your attitude towards someone else that was being extremely helpful showed you don't want to be helped, you want to angry at someone. We are not your tech support, so I can tell you: Fuck off.
- mehrdadn 9y ago
  > We are not your tech support, so I can tell you: [expletive] off. 1. I wasn't here to seek tech support at all. The discussion was on package managers and I was sharing an experience I had. Users such as you decided to issue judgments that I must have necessarily ignored apt and broken my system by... installing non-OSS software (?!) without any information on my actual system setup. As I said in the very beginning, I already reverted to my backup. Nowhere did I solicit tech support, and nowhere did I expect any, especially based on almost complete lack of knowledge about the actual system configuration. 2. Flagged. This is the first time I've seen such an attack on HN. And you can imagine I have no interest in replying after this.
  - SolarNet 9y ago
    You were asking to be provided tech support here: > Which of these packages is proprietary? I was doing this in VirtualBox without guest additions installed, and while I used to boot this installation on an NVIDIA system, I don't believe I had any NVIDIA-specific packages on it. Let me know the proprietary package name(s) you think I had and I'll search to see if I had any of them installed. (Also, how would you do that if it was already wiped? Edit 2: yea.... because as not tech support I have read everything you have posted on your problem and am aware you have backups) You were acting pretty entitled to this other person's help here: > What "it" are you even talking about? I didn't "choose to ignore" anything. I Marked all Upgrades, clicked Apply, rebooted when it was finished, went to see if there were any more upgrades (there were some), tried to mark & apply them, and was greeted with this error. Apt/Synaptic got me into this broken state and couldn't get me out of it. I don't know what story you're reading, but it doesn't seem to be what I've been writing. There was nothing for me to ignore. The error wasn't something I ignored; it was the problem. Edit: Oh and that's a perfectly civil response to you continuing to tell people who know how these systems actually work (which does not include you) that they are incapable of understanding what you are writing and implying that they are somehow delusional.
    - mehrdadn 9y ago
      I'll reply to this because you posted it after I was finished editing my reply above, but as I said there, I have no interest in replying to your profanity beyond this: >> You were asking to be provided tech support here: > Which of these packages is proprietary? [...] Let me know the proprietary package name(s) you think I had and I'll search to see if I had any of them installed. I was fact-checking your (unsolicited) diagnosis, which you had already provided despite my lack of request for any kind of support. You made a claim seemingly out of the blue that caught me off-guard (it seemed unfounded and I had neither requested support nor a diagnosis), and in response I said if you wanted to check your facts I would provide you with information to confirm or disprove your (again: unsolicited) diagnosis. I thought maybe you would be interested in seeing whether you are correct. Of course I won't anymore, after your profane verbal abuse. > (Also, how would you do that if it was already wiped?) Because as I said multiple times since the beginning, I had a backup from before the update, which I ended up restoring to. Apparently you are not reading?