Here's a (long) short explanation...
When you perform a Ubuntu upgrade, it disables all of your "foreign" sources, on the assumption that they may cause problems with the upgrade. It's left to the user to determine which repositories need to be re-enabled, and which might require editing. All these "foreign" repositories have a comment indicating that they've been disabled on upgrade to yakkety
.
You have to edit
each repository entry to determine its status. I'll use one of my own examples.
Here you see that this repository is using an older xenial distribution. I wonder if there's a newer one for yakkety? Copy the URI field to the clipboard, open your web browser, and paste the clipboard into the address bar, and hit enter
to go to the web site.
Here we are at the web site. Click on the dists
directory.
Then we end up here. Notice that this repository does not have a yakkety directory. The newest directory is for xenial. So image #1 is correct, and needs no updating, except for editing the comment field and removing the disabled on upgrade to yakkety
comment. If there was a yakkety directory, we could edit image #1 to show that distribution. Click OK
to save any edits, and enable the checkbox in front of that repository.
Go through all of your repositories like this. Then when you exit Software & Updates
, it'll rescan the newly (re)enabled repositories to make sure that no errors exist. If there are errors, write down the error message, and go back to that repository entry and recheck that the information is correct.
You don't need to do disable security on Ubuntu 18.04, and the 9370, 9570 and 9575 all include new enough thunderbolt firmware out of the box.
On any OS with bolt
and gnome-shell version 3.28
(or the boltd integration back ported) you don't need to do any of this: Thunderbolt devices work out of the box. Ubuntu 18.04.1 Gnome Shell ships with this boltd integration.
So for those on the ancient versions of ubuntu the recommended way at the moment is to use boltctl from https://packages.ubuntu.com/bionic/bolt
first run:
$ boltctl list
● Thunderbolt Cable
├─ type: peripheral
├─ vendor: Dell
├─ uuid: <there will be a UUID here I will call it cable-uuid>
├─ status: authorized
│ ├─ authorized: Mon 11 Jun 2018 11:45:37 UTC
│ └─ connected: Mon 11 Jun 2018 11:45:37 UTC
└─ stored: yes
├─ when: Mon 11 Jun 2018 11:39:20 UTC
├─ policy: auto
└─ key: no
● Thunderbolt Dock
├─ type: peripheral
├─ vendor: Dell
├─ uuid: <there will be a UUID here I will call it dock-uuid>
├─ status: authorized
│ ├─ authorized: Mon 11 Jun 2018 11:45:42 UTC
│ └─ connected: Mon 11 Jun 2018 11:45:42 UTC
└─ stored: yes
├─ when: Mon 11 Jun 2018 11:39:45 UTC
├─ policy: auto
└─ key: no
Then run:
boltctl enroll <cable-uuid>
boltctl enroll <dock-uuid>
The first time I ran enroll
for the <dock-uuid>
I got: failed to authorize device: write error: Invalid argument
So you may need to run it twice or more.
Note that for me boltd 0.3 won't authorize any devices enrolled until after first login. However you can grab bolt 0.4 from the proposed repo (It's likely to be available in the main repos soon though), see also:
https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1778020
Best Answer
I've spoken to Dell about this and am posting this answer here in case it helps anyone else.
Updated 11 Oct 2018
Dell have said that they do now support Ubuntu 18.04 on the XPS 13 9360 (previously they had said that they didn't). The disabled repositories are not necessary and are not supported in Ubuntu 18.04 ('bionic').
In answer to my question, no, you shouldn't replace 'xenial' with 'bionic' and re-enable the repositories.
The "dino2-mlk" is apparently the codename for the 9360 model of the XPS 13. As mentioned in the comments there isn't a
bionic-dell-dino2-mlk
repository.The repositories contain drivers and other updates.