Reply to topic

Problem: Key Packages Being Marked For Removal

Xendi
Registered Member
Posts
12
Karma
0
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:

Code: Select all
apt install firejail
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 12
Starting 2 pkgProblemResolver with broken count: 12
Investigating (0) xserver-xorg-input-evdev-hwe-16.04 [ amd64 ] < 1:2.10.2-1ubuntu1~16.04.1 > ( x11 )
Broken xserver-xorg-input-evdev-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 0 as a solution to xserver-xorg-input-evdev-hwe-16.04:amd64 2
  Added xserver-xorg-core-hwe-16.04:amd64 to the remove list
  Fixing xserver-xorg-input-evdev-hwe-16.04:amd64 via keep of xserver-xorg-core-hwe-16.04:amd64
Investigating (0) xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 )
Broken xserver-xorg-core-hwe-16.04:amd64 Conflicts on xserver-xorg-core [ amd64 ] < none -> 2:1.18.4-0ubuntu0.2 > ( x11 )
  Considering xserver-xorg-core:amd64 3 as a solution to xserver-xorg-core-hwe-16.04:amd64 0
  Removing xserver-xorg-core-hwe-16.04:amd64 rather than change xserver-xorg-core:amd64
Investigating (0) xserver-xorg-hwe-16.04 [ amd64 ] < 1:7.7+13ubuntu4~16.04.2 > ( x11 )
Broken xserver-xorg-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.2-2)
  Considering xserver-xorg-core-hwe-16.04:amd64 0 as a solution to xserver-xorg-hwe-16.04:amd64 0
  Removing xserver-xorg-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (1) sddm [ amd64 ] < 0.14.0-1~2.gbpf70012+16.04+xenial+build8 > ( kde )
Broken sddm:amd64 Depends on xserver-xorg [ amd64 ] < none -> 1:7.7+13ubuntu3 > ( x11 )
  Considering xserver-xorg:amd64 1 as a solution to sddm:amd64 5
  Added xserver-xorg:amd64 to the remove list
Broken sddm:amd64 Depends on xserver [ amd64 ] < none ->  > ( none )
  Considering xvfb:i386 0 as a solution to sddm:amd64 5
  Added xvfb:i386 to the remove list
  Fixing sddm:amd64 via keep of xserver-xorg:amd64
  Fixing sddm:amd64 via keep of xvfb:i386
Investigating (1) xserver-xorg-input-evdev-hwe-16.04 [ amd64 ] < 1:2.10.2-1ubuntu1~16.04.1 > ( x11 )
Broken xserver-xorg-input-evdev-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 0 as a solution to xserver-xorg-input-evdev-hwe-16.04:amd64 2
  Added xserver-xorg-core-hwe-16.04:amd64 to the remove list
  Fixing xserver-xorg-input-evdev-hwe-16.04:amd64 via keep of xserver-xorg-core-hwe-16.04:amd64
Investigating (1) xorg [ amd64 ] < 1:7.7+13ubuntu3 > ( x11 )
Broken xorg:amd64 Depends on xserver-xorg [ amd64 ] < none -> 1:7.7+13ubuntu3 > ( x11 ) (>= 1:7.7+13ubuntu3)
  Considering xserver-xorg:amd64 1 as a solution to xorg:amd64 1
  Removing xorg:amd64 rather than change xserver-xorg:amd64
Investigating (1) xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 )
Broken xserver-xorg-core-hwe-16.04:amd64 Conflicts on xserver-xorg-core [ amd64 ] < none -> 2:1.18.4-0ubuntu0.2 > ( x11 )
  Considering xserver-xorg-core:amd64 3 as a solution to xserver-xorg-core-hwe-16.04:amd64 0
  Removing xserver-xorg-core-hwe-16.04:amd64 rather than change xserver-xorg-core:amd64
Investigating (1) neon-desktop [ amd64 ] < 4+p16.04+git20170704.1723 > ( metapackages )
Broken neon-desktop:amd64 Depends on xorg [ amd64 ] < 1:7.7+13ubuntu3 > ( x11 )
  Considering xorg:amd64 1 as a solution to neon-desktop:amd64 0
  Removing neon-desktop:amd64 rather than change xorg:amd64
Investigating (2) sddm [ amd64 ] < 0.14.0-1~2.gbpf70012+16.04+xenial+build8 > ( kde )
Broken sddm:amd64 Depends on xserver-xorg [ amd64 ] < none -> 1:7.7+13ubuntu3 > ( x11 )
  Considering xserver-xorg:amd64 1 as a solution to sddm:amd64 5
  Added xserver-xorg:amd64 to the remove list
Broken sddm:amd64 Depends on xserver [ amd64 ] < none ->  > ( none )
  Considering xvfb:i386 0 as a solution to sddm:amd64 5
  Added xvfb:i386 to the remove list
  Fixing sddm:amd64 via keep of xserver-xorg:amd64
  Fixing sddm:amd64 via keep of xvfb:i386
Investigating (2) xserver-xorg-input-evdev-hwe-16.04 [ amd64 ] < 1:2.10.2-1ubuntu1~16.04.1 > ( x11 )
Broken xserver-xorg-input-evdev-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 0 as a solution to xserver-xorg-input-evdev-hwe-16.04:amd64 2
  Added xserver-xorg-core-hwe-16.04:amd64 to the remove list
  Fixing xserver-xorg-input-evdev-hwe-16.04:amd64 via keep of xserver-xorg-core-hwe-16.04:amd64
Investigating (2) xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 )
Broken xserver-xorg-core-hwe-16.04:amd64 Conflicts on xserver-xorg-core [ amd64 ] < none -> 2:1.18.4-0ubuntu0.2 > ( x11 )
  Considering xserver-xorg-core:amd64 3 as a solution to xserver-xorg-core-hwe-16.04:amd64 2
  Removing xserver-xorg-core-hwe-16.04:amd64 rather than change xserver-xorg-core:amd64
Investigating (3) sddm [ amd64 ] < 0.14.0-1~2.gbpf70012+16.04+xenial+build8 > ( kde )
Broken sddm:amd64 Depends on xserver-xorg [ amd64 ] < none -> 1:7.7+13ubuntu3 > ( x11 )
  Considering xserver-xorg:amd64 5 as a solution to sddm:amd64 5
  Try Installing xserver-xorg [ amd64 ] < none -> 1:7.7+13ubuntu3 > ( x11 ) before changing sddm:amd64
Investigating (3) xserver-xorg-input-evdev-hwe-16.04 [ amd64 ] < 1:2.10.2-1ubuntu1~16.04.1 > ( x11 )
Broken xserver-xorg-input-evdev-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-input-evdev-hwe-16.04:amd64 2
  Removing xserver-xorg-input-evdev-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-input-synaptics-hwe-16.04 [ amd64 ] < 1.8.3-1ubuntu1~16.04.1 > ( x11 )
Broken xserver-xorg-input-synaptics-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-input-synaptics-hwe-16.04:amd64 2
  Removing xserver-xorg-input-synaptics-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-vesa-hwe-16.04 [ amd64 ] < 1:2.3.4-1build2~16.04.1 > ( x11 )
Broken xserver-xorg-video-vesa-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-vesa-hwe-16.04:amd64 2
  Removing xserver-xorg-video-vesa-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-ati-hwe-16.04 [ amd64 ] < 1:7.7.1-1~16.04.1 > ( x11 )
Broken xserver-xorg-video-ati-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-ati-hwe-16.04:amd64 2
  Removing xserver-xorg-video-ati-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-qxl-hwe-16.04 [ amd64 ] < 0.1.4-3ubuntu3~16.04.1 > ( x11 )
Broken xserver-xorg-video-qxl-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-qxl-hwe-16.04:amd64 2
  Removing xserver-xorg-video-qxl-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-fbdev-hwe-16.04 [ amd64 ] < 1:0.4.4-1build5~16.04.1 > ( x11 )
Broken xserver-xorg-video-fbdev-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-fbdev-hwe-16.04:amd64 2
  Removing xserver-xorg-video-fbdev-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-nouveau-hwe-16.04 [ amd64 ] < 1:1.0.12-2~16.04.1 > ( x11 )
Broken xserver-xorg-video-nouveau-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-nouveau-hwe-16.04:amd64 2
  Removing xserver-xorg-video-nouveau-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-input-wacom-hwe-16.04 [ amd64 ] < 1:0.33.0-0ubuntu1~16.04.1 > ( x11 )
Broken xserver-xorg-input-wacom-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-input-wacom-hwe-16.04:amd64 2
  Removing xserver-xorg-input-wacom-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-vmware-hwe-16.04 [ amd64 ] < 1:13.1.0-2ubuntu3~16.04.1 > ( x11 )
Broken xserver-xorg-video-vmware-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-vmware-hwe-16.04:amd64 2
  Removing xserver-xorg-video-vmware-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-radeon-hwe-16.04 [ amd64 ] < 1:7.7.1-1~16.04.1 > ( x11 )
Broken xserver-xorg-video-radeon-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-radeon-hwe-16.04:amd64 2
  Removing xserver-xorg-video-radeon-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-amdgpu-hwe-16.04 [ amd64 ] < 1.1.2-1~16.04.1 > ( x11 )
Broken xserver-xorg-video-amdgpu-hwe-16.04:amd64 Depends on xserver-xorg-core-hwe-16.04 [ amd64 ] < 2:1.18.4-1ubuntu6.1~16.04.1 > ( x11 ) (>= 2:1.17.99.902)
  Considering xserver-xorg-core-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-amdgpu-hwe-16.04:amd64 2
  Removing xserver-xorg-video-amdgpu-hwe-16.04:amd64 rather than change xserver-xorg-core-hwe-16.04:amd64
Investigating (3) xserver-xorg-video-all-hwe-16.04 [ amd64 ] < 1:7.7+13ubuntu4~16.04.2 > ( x11 )
Broken xserver-xorg-video-all-hwe-16.04:amd64 Depends on xserver-xorg-video-amdgpu-hwe-16.04 [ amd64 ] < 1.1.2-1~16.04.1 > ( x11 )
  Considering xserver-xorg-video-amdgpu-hwe-16.04:amd64 3 as a solution to xserver-xorg-video-all-hwe-16.04:amd64 1
  Removing xserver-xorg-video-all-hwe-16.04:amd64 rather than change xserver-xorg-video-amdgpu-hwe-16.04:amd64
Investigating (3) xserver-xorg-input-all-hwe-16.04 [ amd64 ] < 1:7.7+13ubuntu4~16.04.2 > ( x11 )
Broken xserver-xorg-input-all-hwe-16.04:amd64 Depends on xserver-xorg-input-evdev-hwe-16.04 [ amd64 ] < 1:2.10.2-1ubuntu1~16.04.1 > ( x11 )
  Considering xserver-xorg-input-evdev-hwe-16.04:amd64 3 as a solution to xserver-xorg-input-all-hwe-16.04:amd64 1
  Removing xserver-xorg-input-all-hwe-16.04:amd64 rather than change xserver-xorg-input-evdev-hwe-16.04:amd64
Done
The following packages were automatically installed and are no longer required:
  libxatracker2 x11-apps x11-session-utils xbitmaps xinit xinput
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  firejail-profiles freeglut3 libgtkglext1 libpango1.0-0 libpangox-1.0-0 libpangoxft-1.0-0 python-avahi
  python-cairo python-dbus python-gdbm python-gi python-gi-cairo python-gobject-2 python-gtk2 python-gtkglext1
  python-lz4 python-lzo python-netifaces python-opengl python-pil python-rencode xpra xserver-xorg
  xserver-xorg-core xserver-xorg-input-void xserver-xorg-video-dummy
Suggested packages:
  python-dbus-doc python-dbus-dbg python-gdbm-dbg python-gobject-2-dbg python-gtk2-doc python-tk python-numpy
  libgle3 python-pil-doc python-pil-dbg openssh-server python-pyopencl gstreamer0.10-plugins-good
  | gstreamer0.10-plugins-ugly | gstreamer0.10-plugins-bad python-gst0.10 xfonts-100dpi | xfonts-75dpi
The following packages will be REMOVED:
  neon-desktop xorg xserver-xorg-core-hwe-16.04 xserver-xorg-hwe-16.04 xserver-xorg-input-all-hwe-16.04
  xserver-xorg-input-evdev-hwe-16.04 xserver-xorg-input-synaptics-hwe-16.04 xserver-xorg-input-wacom-hwe-16.04
  xserver-xorg-video-all-hwe-16.04 xserver-xorg-video-amdgpu-hwe-16.04 xserver-xorg-video-ati-hwe-16.04
  xserver-xorg-video-fbdev-hwe-16.04 xserver-xorg-video-nouveau-hwe-16.04 xserver-xorg-video-qxl-hwe-16.04
  xserver-xorg-video-radeon-hwe-16.04 xserver-xorg-video-vesa-hwe-16.04 xserver-xorg-video-vmware-hwe-16.04
The following NEW packages will be installed:
  firejail firejail-profiles freeglut3 libgtkglext1 libpango1.0-0 libpangox-1.0-0 libpangoxft-1.0-0
  python-avahi python-cairo python-dbus python-gdbm python-gi python-gi-cairo python-gobject-2 python-gtk2
  python-gtkglext1 python-lz4 python-lzo python-netifaces python-opengl python-pil python-rencode xpra
  xserver-xorg xserver-xorg-core xserver-xorg-input-void xserver-xorg-video-dummy
0 upgraded, 27 newly installed, 17 to remove and 0 not upgraded.
Need to get 4,955 kB of archives.
After this operation, 15.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]


Here's my /var/log/apt/history.log:

Code: Select all
Start-Date: 2017-07-06  10:22:31
Commandline: apt-get --yes --force-yes upgrade
Upgrade: init:amd64 (1.29ubuntu1, 1.29ubuntu4), init-system-helpers:amd64 (1.29ubuntu1, 1.29ubuntu4), libdns-export162:amd64 (1:9.10.3.dfsg.P4-8, 1:9.10.3.dfsg.P4-8ubuntu1.7), libfdisk1:amd64 (2.27.1-6ubuntu3, 2.27.1-6ubuntu3.3), ifupdown:amd64 (0.8.10ubuntu1, 0.8.10ubu$
End-Date: 2017-07-06  10:24:14

Start-Date: 2017-07-06  10:24:55
Commandline: apt-get --yes install linux-generic-hwe-16.04 adduser base-passwd busybox-initramfs bzip2 coreutils cpio cron dash debconf debconf-i18n debianutils diffutils e2fslibs e2fsprogs file findutils gcc-6-base gzip hostname initscripts insserv iputils-ping kmod li$
Install: milou:amd64 (4:5.10.3-0neon+16.04+xenial+build43, automatic), libmpc3:amd64 (1.0.3-1, automatic), libgssapi3-heimdal:amd64 (1.7~git20150920+dfsg-4ubuntu1), libkf5notifications-data:amd64 (5.35.0-0neon+16.04+xenial+build27, automatic), cryptsetup-bin:amd64 (2:1.$
End-Date: 2017-07-06  10:41:15

Start-Date: 2017-07-06  10:41:30
Commandline: apt-get --yes install lupin-casper linux-signed-generic-hwe-16.04 neon-live
Install: ubiquity-frontend-kde:amd64 (2.21.63.3+p16.04+git20170316.1346, automatic), ubiquity-casper:amd64 (1.376.2, automatic), python-tdb:amd64 (1.3.8-2, automatic), python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.8, automatic), libqtwebkit4:amd64 (2.3.2-0ubuntu11, a$
End-Date: 2017-07-06  10:42:08

Start-Date: 2017-07-06  10:43:05
Commandline: apt-get purge -y unattended-upgrades
Purge: unattended-upgrades:amd64 (0.90ubuntu0.6)
End-Date: 2017-07-06  10:43:08

Start-Date: 2017-07-22  18:03:27
Requested-By: neon (999)
End-Date: 2017-07-22  18:03:27

Start-Date: 2017-07-22  18:03:33
Requested-By: neon (999)
Purge: ubiquity-frontend-kde:amd64 (2.21.63.3+p16.04+git20170316.1346), ubiquity-casper:amd64 (1.376.2), python-tdb:amd64 (1.3.8-2), python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.8), libqtwebkit4:amd64 (2.3.2-0ubuntu11), python3-icu:amd64 (1.9.2-2build1), ubiquity:am$
End-Date: 2017-07-22  18:03:55

Start-Date: 2017-07-22  18:03:56
Requested-By: neon (999)
End-Date: 2017-07-22  18:03:56

Start-Date: 2017-07-22  18:03:56
Requested-By: neon (999)
End-Date: 2017-07-22  18:03:56

Start-Date: 2017-07-22  18:31:09
Commandline: apt upgrade
Requested-By: trioxin (1000)
Install: linux-headers-4.10.0-27-generic:amd64 (4.10.0-27.30~16.04.2, automatic), libharfbuzz-icu0:amd64 (1.4.6-0neon+16.04+xenial+build2, automatic), linux-image-4.10.0-27-generic:amd64 (4.10.0-27.30~16.04.2, automatic), libre2-1v5:amd64 (20160201+dfsg-1, automatic), l$
Upgrade: milou:amd64 (4:5.10.3-0neon+16.04+xenial+build43, 4:5.10.4-0neon+16.04+xenial+build44), libgssapi3-heimdal:amd64 (1.7~git20150920+dfsg-4ubuntu1, 1.7~git20150920+dfsg-4ubuntu1.16.04.1), libkf5notifications-data:amd64 (5.35.0-0neon+16.04+xenial+build27, 5.36.0-0n$
End-Date: 2017-07-22  18:34:00

Start-Date: 2017-07-22  21:53:12
Commandline: apt install konversation
Requested-By: trioxin (1000)
Install: konversation:amd64 (1.7.2-0neon+16.04+build17), konversation-data:amd64 (1.7.2-0neon+16.04+build17, automatic)
End-Date: 2017-07-22  21:53:13

Start-Date: 2017-07-22  22:07:19
Commandline: apt install nvidia-384
Requested-By: trioxin (1000)
Install: libcuda1-384:amd64 (384.47-0ubuntu0~gpu16.04.3, automatic), policykit-1-gnome:amd64 (0.105-2ubuntu2, automatic), xserver-xorg-legacy:amd64 (2:1.18.4-0ubuntu0.2, automatic), dkms:amd64 (2.2.0.3-2ubuntu11.3, automatic), nvidia-prime:amd64 (0.8.2, automatic), libx$
End-Date: 2017-07-22  22:09:14
NoNameNoBlame
Karma
0
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 …"?
NoNameNoBlame
Karma
0
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???
User avatar acheronuk
KDE Developer
Posts
96
Karma
2
NoNameNoBlame wrote:The package "firejail-profiles" that You install
doesn't exist on KDE neon 5.10.4 User Edition
as of today.


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

firejail (0.9.46~rc1-1) experimental; urgency=low

* New upstream release candidate.
* Split profiles into separate package (Closes: #850273).
- New binary package firejail-profiles
- Remove old profile conffiles from firejail binary package
- Add NEWS to inform about the package split


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.
hiteshshah
Registered Member
Posts
15
Karma
0
OS
I saw something similar when I tried to install firejail from this ppa: https://launchpad.net/~deki/+archive/ubuntu/firejail
Code: Select all
sudo apt-get install firejail
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  firejail-profiles python-cairo python-gi python-gi-cairo
Recommended packages:
  xpra | xserver-xephyr | xvfb
The following packages will be REMOVED:
  xorg xserver-xorg-hwe-16.04
The following NEW packages will be installed:
  firejail firejail-profiles python-cairo python-gi python-gi-cairo
0 upgraded, 5 newly installed, 2 to remove and 0 not upgraded.
Need to get 504 kB of archives.
After this operation, 1,936 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.


I looked at the ppa because the version available for 16.04 is pretty old:
Code: Select all
$ apt policy firejail
firejail:
  Installed: (none)
  Candidate: 0.9.38.10-0ubuntu0.16.04.1
  Version table:
     0.9.38.10-0ubuntu0.16.04.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
     0.9.38-1ubuntu0.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
     0.9.38-1 500
        500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
$
System: Kubuntu 16.04 with kubuntu backports
Code: Select all
Kernel: 4.10.0-27-generic x86_64 (64 bit) Desktop: KDE Plasma 5.8.7
NoNameNoBlame
Karma
0
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?
hiteshshah
Registered Member
Posts
15
Karma
0
OS
I'd conclude that one needs caution while installing ppas or software from outside your distro's repos. Shiny and new can bite you. :)
NoNameNoBlame
Karma
0
Yes. Totally right.

Above, I labeled it "user error".

"ADMINISTRATOR Error" seems a better fit.
Xendi
Registered Member
Posts
12
Karma
0
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.
NoNameNoBlame
Karma
0
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?
Xendi
Registered Member
Posts
12
Karma
0
NoNameNoBlame wrote: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?



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).
NoNameNoBlame
Karma
0
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. )
Xendi
Registered Member
Posts
12
Karma
0
NoNameNoBlame wrote: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. )


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.
NoNameNoBlame
Karma
0
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.

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Belliric, Bing [Bot], Google [Bot], leodd, Majestic-12 [Bot], Yahoo [Bot]