Problem: Key Packages Being Marked For Removal
Page 1 of 1 (14 posts)
Tags:
None
Registered Member 
|
This is my third install of KDE Neon and the same thing happens each time. I update with apt, then go to install a package, and it wants to remove several essential packages. Here is what it's trying to do:
Here's my /var/log/apt/history.log:
|
|
Only to get clarity into Your description:
1) Which Version/Edition of KDE Neon? 2) Did You do a clean, fresh install on a newly formatted partition? 3) Before You install anything new, do You always do an "apt update". followed immediately by "apt upgrade"? And only thereafter "apt install …"? |
|
The package "firejail-profiles" that You install
doesn't exist on KDE neon 5.10.4 User Edition as of today. Where does it come from? What are You doing there??? |
KDE Developer
|
In the ubuntu base, doesn't seem to exist in Xenial (nor later releases), and 1st appears recently in the artful dev release archive. Origin of that appearing is
from debian, which ended up in artful. So maybe the OP is doing something very odd like trying to run Neon with artful ubuntu repos (unlikely), or they are trying to use a backported version of the artful firejail from a ppa such as: https://launchpad.net/~deki/+archive/ub ... ter=xenial I would guess the latter. If so then they are trying a configuration/packages that would be unsupported in a normal ubuntu 16.04 install, so doubly likely to introduce breakage in Neon. |
|
Registered Member
|
I saw something similar when I tried to install firejail from this ppa: https://launchpad.net/~deki/+archive/ubuntu/firejail
I looked at the ppa because the version available for 16.04 is pretty old:
|
|
With the data collected so far,
I'd conclude: This is a user error because KDE neon correctly protects itself against incompatible packages from unsupported foreign archives. Problem solved. Because: Not a problem. Any other opinions? |
|
Registered Member
|
I'd conclude that one needs caution while installing ppas or software from outside your distro's repos. Shiny and new can bite you.
|
|
Yes. Totally right.
Above, I labeled it "user error". "ADMINISTRATOR Error" seems a better fit. |
|
Registered Member
|
KDE neon 5.10
It wasn't just firejail. It also happened on a previous Neon install when I tried to install the cuda package from nvidia's repo. Yes, I always do update and upgrade first before anything else. I don't know why apt keeps doing this. On this latest install, I have resolved to only use aptitude. I've repeated the steps that would cause the problem to happen but with aptitude and all is fine now. It's still a terrible thing to happen though if one isn't paying attention to what apt is doing during a package install. |
|
Ubuntu (X Window System)
and Nvidia (propriatary drivers) both recommend using distribution's packages. With KDE Neon, this means Ubuntu LTS driver packages. You didn't use the recommended, automatic way. Why didn't You? |
|
Registered Member
|
I didn't use any repo containing any system packages or any of the packages that were marked for removal. In the case of cuda, there are no system packages and cuda can't run on noveu (Whatever it's called) driver. The open-source driver for nvidia is absolutely horrific in terms of performance and isn't compatible with machine learning libraries AFAIK. I followed the recommended way of installing Tensorflow with GPU support on 16.04. No-one with an NVIDIA card would use the open driver. Using that driver, you can't even use the OS without KDE lagging. But anyway, this isn't a problem with the proprietary driver or with any package. There's nothing wrong with the graphics repo or the firejail repo. There's something wrong with how apt is behaving in Neon which, in my experience, isn't happening with other distros. I just came to Neon from Kubuntu where I never had that problem. Using aptitude has cleared it up and I don't have to worry about it. I just can't use apt anymore (Fine with me). |
|
1)
Recommendation is: https://www.tensorflow.org/install/install_linux You must choose one of the following types of TensorFlow to install: TensorFlow with CPU support only. If your system does not have a NVIDIA® GPU, you must install this version. Note that this version of TensorFlow is typically much easier to install (typically, in 5 or 10 minutes), so even if you have an NVIDIA GPU, we recommend installing this version first. 2) Nouveau-Driver is good enough for watching video and for KDE Plasma 5. For example with Debian Stable, I use it. ("no one uses it"?, "it lags horribly"? Seems a little bit too harsh.) 3) You should get a better understanding of package management. Do You think, proposing the deinstalling of key components of Your Desktop-OS was caused by apt? It was caused by You. 4) Read aptitude's documentation. It's good, but it can bite You if You don't understand what it does in detail. # Docu after installation: file:///usr/share/doc/aptitude/html/en/index.html 4) Good Luck! 5) Did You get Tensorflow running successfully like You expected? On any of Your Linux-based machines? (That's a question concerning You and Your personal installation problems. I don't intend to discuss 'www.tensorflow.org'-software. ) |
|
Registered Member
|
I realize it seems harsh but that driver doesn't even support the HDMI ports on my card (Titan X Pascal). The only port that worked was my DVI port. Thankfully I have 1 DVI monitor. Here's the thing about package management. I will concede that I did something wrong if you explain to me what I did wrong. Until then, it might has well be considered a bug because I didn't do anything abnormal. Any number of packages were causing essential packages to be removed by apt. It had nothing to do with the packages I was trying to install but something in the way dependencies are handled, right? I'm not trying to be overtly critical. I love Neon now that I'm using aptitude. I've gotten TF working before on other Ubuntu installs and I'm almost done on this one. I'll get that sorted no matter what. I'd just hate to think that someone else is going to come along and install Neon, then go to install some arbitrary package (It was seemingly happening for any package from any repo that didn't come preset), and their install breaks. |
|
Thank You for Your friendly reaction.
I'd like to recommend, You read the following: https://www.debian.org/doc/manuals/debi ... 02.en.html if You find the time. Reading this slowly and carefully is essential for any local System Administrator to protect him/herself against misunderstandings. If You change the pre-installed package management configuration, it's a must-read. By the way: I understand Your feelings. But it can't be helped. |
Page 1 of 1 (14 posts)
Bookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft
