Is it actually an Untrusted PPA?

[CharlieDaves]

Good question. https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/ppa only states, "Updates for Kubuntu releases which are due to go to Ubuntu Updates. Mostly KDE point releases" which doesn't say much.

This reads as update your system with unsupported packages from an untrusted PPA. Why would anyone do this ?
And this is not the first time I've read "solution" to a problem redirected to this page/link

Can someone please explain this further as I have several problems I am trying to find solutions for
1. Malformed url when connecting a usb drive
2. some GPG error when updating.
2a. Now unable to find new update server as "packages not downloaded" or some such error.

Thanks
Charles

[jglen490]

This update has been promoted to the regular repo, therefore it is supported, as was discussed in the 18.04 forum for the Plasma update sticky thread.

As for the remaining errors you are getting, it would be interesting to see actual outputs showing each. You might be able to see 2 and 2a if you open a konsole and enter:

sudo apt update

followed by

sudo apt full-upgrade

Those two entries should result in capture and install of anything outstanding upgrades to your current Kubuntu.

The following copied exactly into a konsole session would also be useful in helping to understand your current platform:

inxi -Fxz

Your outputs should be copied and pasted into your Reply using CODE boxes (the # button in the Reply).

[CharlieDaves]

jglen
I did find and remove an update source something like 'http.debian.net/debian stretch-backports' in the update sources, and unselected it. (yes it looks like it had a space in it)

output as requested

dave@davesPC:~$ sudo apt update
[sudo] password for dave: 
Hit:1 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu bionic InRelease        
Hit:2 http://archive.canonical.com/ubuntu bionic InRelease                                               
Hit:3 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease                                   
Hit:4 http://ubuntu.mirror.serversaustralia.com.au/ubuntu bionic InRelease                          
Hit:5 http://ubuntu.mirror.serversaustralia.com.au/ubuntu bionic-updates InRelease                  
Hit:6 http://ubuntu.mirror.serversaustralia.com.au/ubuntu bionic-security InRelease
Hit:7 http://ppa.launchpad.net/samoilov-lex/aftl-stable/ubuntu bionic InRelease
Reading package lists... Done                      
Building dependency tree       
Reading state information... Done
All packages are up to date.
dave@davesPC:~$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
bacula-bscan bacula-client bacula-common-pgsql bacula-console bacula-director bacula-director-pgsql
bacula-fd bacula-sd bacula-server dbconfig-common dbconfig-pgsql libmuparser2v5 librecad-data mt-st
mtx python3-notify2
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
dave@davesPC:~$ inxi -Fxz

Command 'inxi' not found, but can be installed with:

sudo apt install inxi

dave@davesPC:~$ sudo apt install inxi
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
bacula-bscan bacula-client bacula-common-pgsql bacula-console bacula-director bacula-director-pgsql
bacula-fd bacula-sd bacula-server dbconfig-common dbconfig-pgsql libmuparser2v5 librecad-data mt-st
mtx python3-notify2
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
hddtemp lm-sensors mesa-utils
Suggested packages:
fancontrol read-edid i2c-tools
The following NEW packages will be installed:
hddtemp inxi lm-sensors mesa-utils
0 to upgrade, 4 to newly install, 0 to remove and 0 not to upgrade.
Need to get 310 kB of archives.
After this operation, 1,345 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ubuntu.mirror.serversaustralia.com.au/ubuntu bionic/universe amd64 hddtemp amd64 0.3-beta15-53 [47.7 kB]
Get:2 http://ubuntu.mirror.serversaustralia.com.au/ubuntu bionic/universe amd64 inxi all 2.3.56-1 [143 kB]
Get:3 http://ubuntu.mirror.serversaustralia.com.au/ubuntu bionic/universe amd64 lm-sensors amd64 1:3.4.0-4 [85.5 kB]
Get:4 http://ubuntu.mirror.serversaustralia.com.au/ubuntu bionic/universe amd64 mesa-utils amd64 8.4.0-1 [34.3 kB]
Fetched 310 kB in 2s (182 kB/s)   
Preconfiguring packages ...
Selecting previously unselected package hddtemp.
(Reading database ... 245672 files and directories currently installed.)
Preparing to unpack .../hddtemp_0.3-beta15-53_amd64.deb ...
Unpacking hddtemp (0.3-beta15-53) ...
Selecting previously unselected package inxi.
Preparing to unpack .../archives/inxi_2.3.56-1_all.deb ...
Unpacking inxi (2.3.56-1) ...
Selecting previously unselected package lm-sensors.
Preparing to unpack .../lm-sensors_1%3a3.4.0-4_amd64.deb ...
Unpacking lm-sensors (1:3.4.0-4) ...
Selecting previously unselected package mesa-utils.
Preparing to unpack .../mesa-utils_8.4.0-1_amd64.deb ...
Unpacking mesa-utils (8.4.0-1) ...
Setting up hddtemp (0.3-beta15-53) ...
Processing triggers for ureadahead (0.100.0-20) ...
ureadahead will be reprofiled on next reboot
Setting up lm-sensors (1:3.4.0-4) ...
Created symlink /etc/systemd/system/multi-user.target.wants/lm-sensors.service → /lib/systemd/system/lm-sensors.service.
Setting up inxi (2.3.56-1) ...
Processing triggers for systemd (237-3ubuntu10.9) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up mesa-utils (8.4.0-1) ...
Processing triggers for ureadahead (0.100.0-20) ...
dave@davesPC:~$ inxi -Fxz            
System:    Host: DavesPC Kernel: 4.15.0-43-generic x86_64 bits: 64 gcc: 7.3.0
       Desktop: KDE Plasma 5.12.7 (Qt 5.9.5) Distro: Ubuntu 18.04.1 LTS
Machine:   Device: desktop System: XXXX product: XXXX serial: N/A                                   
       Mobo: XXXX model: XXXX: Rev X.0x serial: N/A                                         
       BIOS: American Megatrends v: 2205 date: 05/26/2015                                             
CPU:       Quad core Intel Core i5-4460 (-MCP-) arch: Haswell rev.3 cache: 6144 KB
       flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 25585
       clock speeds: max: 3400 MHz 1: 2182 MHz 2: 2190 MHz 3: 2159 MHz 4: 2157 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
       bus-ID: 00:02.0
       Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa)
       Resolution: 1920x1080@60.00hz
       OpenGL: renderer: Mesa DRI Intel Haswell Desktop version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio:     Card Intel 8 Series/C220 Series High Def. Audio Controller
       driver: snd_hda_intel bus-ID: 00:1b.0
       Sound: Advanced Linux Sound Architecture v: k4.15.0-43-generic
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
       driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 04:00.0
       IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 6731.4GB (79.9% used)
       ID-1: /dev/sda model: XXXX size: 480.1GB temp: 33C
       ID-2: /dev/sdb model: XXXX size: 250.1GB temp: 0C
       ID-3: /dev/sdc model: XXXX size: 2000.4GB temp: 29C
       ID-4: /dev/sdd model: XXXX size: 4000.8GB temp: 27C
Partition: ID-1: / size: 440G used: 123G (30%) fs: ext4 dev: /dev/sda1
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
       Fan Speeds (in rpm): cpu: 0
Info:      Processes: 245 Uptime: 26 min Memory: 4640.0/14967.6MB
       Init: systemd runlevel: 5 Gcc sys: 7.3.0 Client: Shell (bash 4.4.191) inxi: 2.3.56 
dave@davesPC:~$

[chimak111]

This reads as update your system with unsupported packages from an untrusted PPA. Why would anyone do this ?

Because they trust the person or team behind the untrusted ppa.

I see you have
Hit:1 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu bionic InRelease
Hit:3 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease
Hit:7 http://ppa.launchpad.net/samoilov-le...-stable/ubuntu bionic InRelease

[sithlord48]

Anything not in the base repo considered "unsupported" since canonical does not provide support or do any security testing with the packages on PPAs.

[oshunluvr]

IMO, "Untrusted" means "Not owned by Canonical" in this instance. Not a wholly scary situation in itself. Their are many PPAs that are extremely useful for specific things. Like a program that is not directly developed by Canonical so drags months or even years behind your installation. Often these projects are well ahead of the "factory" repos and you're much better off with the latest update than the old package, like Handbrake for example. This is especially true if you stick to the LTS cycle rather then the six-month releases.

[oshunluvr]

BTW, this particular PPA has the KDE team supporting it. One could argue that it's more "trusted" than anything Canonical puts out. Or you could just install KDEneon and be done with it.

[jglen490]

... or not

[CharlieDaves]

Because they trust the person or team behind the untrusted ppa.

I see you have
Hit:1 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu bionic InRelease
Hit:3 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease
Hit:7 http://ppa.launchpad.net/samoilov-le...-stable/ubuntu bionic InRelease

Is this Good or Bad?
You didn't mention the other hits, the even ones

[CharlieDaves]

OK. Thanks I think.
I've added this PPA, and updated.

New Problem. (Let me know if I should make a new thread)
I am unable to mount any of my encrypted HDD's using VeraCrypt.
I go to mount, the mount appears to be successful, and is mounted and appears in Dolphin.
VeraCrypt comes up with an error

Failed to write lock '/dev/mapper/veracrypt1': Resource temporarily unavailable
Error opening '/dev/mapper/veracrypt1': Resource temporarily unavailable
Failed to mount '/dev/mapper/veracrypt1': Resource temporarily unavailable

VeraCrypt doesn't display the drive as mounted within VeraCrypt. (The mounted drive is usable as in I can create and delete stuff, but I don't use it in this manner as it is a backup drive, and it takes hours to do a full backup)
I am unable to unmount or remove the drive from appearing in Dolphin (VeraCrypt Name).
I can power off the drive (It is external) and this disconnects the drive from being accessed, but it is still listed in dolphin under the VeraCrypt Name.
If I reconnect the drive, it appears as a new device as in if previous SDd it is now SDe, then SDf, etc
I am unable to mount within VeraCrypt as the device is 'in use'

- Sorry long explanation-

Q- Can I remove this PPA and all associated updated stuff (so I can get my external encrypted Drive working again as I need to finish of EOY backups)?
-- If yes, how?

Q- Is there a work around to get VeraCrypt to work correctly. I have removed and installed a slightly later version ?.22 to ?.23 [& even done the old Windows ready(reboot), Set(Reboot), Go(Reboot & play solitaire)]

Thanks Again
Charles

[Snowhog]

He (chimak111) is just saying that 'untrusted' doesn't have the meaning that you (initially) attributed to it. I believe, technically, Ubuntu (Canonical) takes the position that "If it isn't in our official repositories, we don't officially support it -- it's "untrusted"." and nothing more. That's not to say that people can't establish a PPA for the purpose of hosting malicious files, but if they did, they wouldn't last very long; word gets around VERY quickly. When in doubt as to the safety of using someones PPA, ask others about it first.