DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Maybe a wild idea. Exit your Window Manager. Kill the xorg process and anything else X-related. Then try again. This shouldn't be necessary but this way none of the files will be open.
Nope, doesn't work. The system isn't using the package in anyway since the module has already been removed and I've set xorg to use ati for the time being.
There must be something wrong with it but it's kinda hard to find the solution.
Well, I got it done in a probable very nasty way. I removed the scripts from /var/lib/dpkg/info and could remove the package. Reinstalled and tried to remove it again...all works again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.