Ubuntu Budgie

CD-Rom is ticked in sources

Bug #1823135 reported by Zebediah Boss
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Budgie
New
Undecided
Unassigned
ubiquity (Ubuntu)
New
Low
Unassigned

Bug Description

When you look in Synaptic Repositories. First Tab at the Bottom. The CD-Rom section is still ticked after the install

This is the daily build 19.04 as of 03/04/2019

zebedee@i7-ubuntu-budgie:~$ budgie-desktop --version
budgie-desktop 10.5
Copyright © 2014-2019 Budgie Desktop Developers

See original description
Revision history for this message
fossfreedom (fossfreedom) wrote :

adding ubiquity as affected - apologies if not - reassign as appropriate.

Zebediah Boss (zebedee-boss)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, why do you consider it as a bug to have the installation media source selected?

Changed in ubiquity (Ubuntu):
importance: Undecided → Low
Revision history for this message
Zebediah Boss (zebedee-boss) wrote :

Because after the install most people will have taken the CD-Rom out of the tray and you receive an error message that it is not available. Maybe Bug is the wrong choice of wording. Perhaps it Could/Would/Should be viewed as a bad default to leave it selected ?

zebedee@i7-ubuntu-budgie:~$ sudo apt update
Ign:1 cdrom://Ubuntu-Budgie 19.04 _Disco Dingo_ - Alpha amd64 (20190403) disco InRelease
Err:2 cdrom://Ubuntu-Budgie 19.04 _Disco Dingo_ - Alpha amd64 (20190403) disco Release
  Please use apt-cdrom to allow APT to recognise this CD-ROM. 'apt-get update' cannot be used to add new CD-ROMs
Hit:3 http://security.ubuntu.com/ubuntu disco-security InRelease
Hit:4 http://gb.archive.ubuntu.com/ubuntu disco InRelease
Hit:5 http://gb.archive.ubuntu.com/ubuntu disco-updates InRelease
Hit:6 http://gb.archive.ubuntu.com/ubuntu disco-backports InRelease
Reading package lists... Done
E: The repository 'cdrom://Ubuntu-Budgie 19.04 _Disco Dingo_ - Alpha amd64 (20190403) disco Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
zebedee@i7-ubuntu-budgie:~$

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.