[CONFIGURATION] Updates held back due to Google repository change?

[MoeNeigh]

Recently in trying to get an update in Kubuntu 18.04, I got this message:

E: Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

The update is for xdg-utils. Not sure if this is even connected to Google, but...

...It sounds as if I must somehow change the Google repository link or its attributes if I'm to get any further updates of any kind. How can I find out what the acceptable repository link is supposed to be?

[GreyGeek]

That URL is NOT part of the default Kubuntu/Ubuntu repository. You must of added it to download and install a more recent and updateable version of Chrome or GoogleEarth:
https://www.google.com/linuxrepositories/

I suggest that you remove that repository, rebuild the cache, and then re-add it and re-install the Google app(s) you bypassed the repository to install.

[MoeNeigh]

Found an answer. Run "sudo apt update" first not"'sudo apt-get update"
Accept the change with "y"
Then run the usual "sudo apt-get update"

[GreyGeek]

Found an answer. Run "sudo apt update" first not"'sudo apt-get update"
Accept the change with "y"
Then run the usual "sudo apt-get update"

You don't have to use apt-get. Using apt is recommended.
https://itsfoss.com/apt-vs-apt-get-difference/

[chimak111]

Found an answer. Run "sudo apt update" first not"'sudo apt-get update"
Accept the change with "y"
Then run the usual "sudo apt-get update"

+1, the confusion arises when the update and upgrade are chained with &&. That swallows the intermediate y/n prompt.

I wonder how GUI programs like Muon and Discover will deal with the issue.

[GreyGeek]

+1, the confusion arises when the update and upgrade are chained with &&. That swallows the intermediate y/n prompt.

I wonder how GUI programs like Muon and Discover will deal with the issue.

Jonathon Riddell wrote Muon 8 years ago and it is a wrapper around QApt.
https://jontheechidna.wordpress.com/...ckage-manager/

It used to be my preferred package manager BUT it started to do a re-indexing almost everytime the contents of the search text box was changed, and the sorting algorithm seemed to have all the speed of a bubble sort. So, I switched to Synaptic.

[chimak111]

Jonathon Riddell wrote Muon 8 years ago and it is a wrapper around QApt.
https://jontheechidna.wordpress.com/...ckage-manager/
...

Nice to know the origin of things for those of us who've started using KDE only recently!

[claydoh]

Jonathon Riddell wrote Muon 8 years ago and it is a wrapper around QApt.
https://jontheechidna.wordpress.com/...ckage-manager/

That's a different Jonathan


Sent from my LG-H931 using Tapatalk

[MoeNeigh]

+1, the confusion arises when the update and upgrade are chained with &&. That swallows the intermediate y/n prompt.

I wonder how GUI programs like Muon and Discover will deal with the issue.

Thanks for the info on chaining update and upgrade. I normally do this. So, if I encounter a similar problem in the future, I can go back and do just the update first and answer the prompt, then upgrade afterwards.

As far as Discover is concerned, the window stays open, and it won't let you close it as an update is supposedly in progress. It doesn't even tell you why. So to continue, I have to power off the computer, rather than perform a normal shutdown or reboot. That's why I went back to using the terminal. I do like that Discover does show an icon on the task bar when updates are available.

[vinnywright]

strangely enough this google problem has fixed it's self .

2-3 day's ago when it hit me , I just commented out the google repo and did my updates .
today I "un-commented" the google repo and did the update routine and it just worked .

VINNY

[vinnywright]

As far as Discover is concerned, the window stays open, and it won't let you close it as an update is supposedly in progress. It doesn't even tell you why. So to continue, I have to power off the computer,

have you used the "scull & crossbones" cursor to try and "kill" it , "CTRL+ALT+ESC" will change the cursor to a scull & crossbones then whatever window you click on will get "killed"

VINNY

[Snowhog]

have you used the "scull & crossbones" cursor to try and "kill" it , "CTRL+ALT+ESC" will change the cursor to a scull & crossbones then whatever window you click on will get "killed"

VINNY

Much better than using the nuclear option -- pressing the power button! Keep in mind: When using the nuclear option, you must be ready for the effects of fallout!

[vinnywright]

Keep in mind: When using the nuclear option, you must be ready for the effects of fallout!

LOL ,,,,,,,yes well their is also the older method .

open a console and do a

ps aux | grep discover

you will get something like this , if discover is running

vinny@vinny-Bonobo-Extreme:~$ ps aux | grep discover 
[COLOR=#ff0000]vinny    12598 26.8  2.4 2107900 407124 ? Sl   20:46   0:07 /usr/bin/plasma-discover[/COLOR]
vinny    12639  0.4  0.1 524212 25804 ? Sl   20:46   0:00 http.so [kdeinit5] https local:/run/user/1000/klauncherlhWVAn.1.slave-socket local:/run/user/1000/discoverFAYMLk.2.slave-socket
vinny    12651  0.0  0.1 336596 17312 ? Sl   20:46   0:00 file.so [kdeinit5] file local:/run/user/1000/klauncherlhWVAn.1.slave-socket local:/run/user/1000/discoverwwSSFN.3.slave-socket
vinny    12680  0.2  0.1 524200 25908 ? Sl   20:46   0:00 http.so [kdeinit5] https local:/run/user/1000/klauncherlhWVAn.1.slave-socket local:/run/user/1000/discovervIgeHD.4.slave-socket
[COLOR=#ee82ee]vinny    14171  0.0  0.0  14428  1040 pts/3    S+   20:46   0:00 grep --color=auto discove[/COLOR][COLOR=#add8e6]r[/COLOR]

the line in pink is "grep" looking for "discover" , the line you want is the one in red that has "/usr/bin/plasma-discover"

you see it has a PID of 12598 , you can now use "kill" on the PID to , well kill it. like so

kill 12598

VINNY

[Snowhog]

LOL ,,,,,,,yes well their is also the older method .

open a console and do a

ps aux | grep discover

you will get something like this , if discover is running

vinny@vinny-Bonobo-Extreme:~$ ps aux | grep discover 
[COLOR=#ff0000]vinny    12598 26.8  2.4 2107900 407124 ? Sl   20:46   0:07 /usr/bin/plasma-discover[/COLOR]
vinny    12639  0.4  0.1 524212 25804 ? Sl   20:46   0:00 http.so [kdeinit5] https local:/run/user/1000/klauncherlhWVAn.1.slave-socket local:/run/user/1000/discoverFAYMLk.2.slave-socket
vinny    12651  0.0  0.1 336596 17312 ? Sl   20:46   0:00 file.so [kdeinit5] file local:/run/user/1000/klauncherlhWVAn.1.slave-socket local:/run/user/1000/discoverwwSSFN.3.slave-socket
vinny    12680  0.2  0.1 524200 25908 ? Sl   20:46   0:00 http.so [kdeinit5] https local:/run/user/1000/klauncherlhWVAn.1.slave-socket local:/run/user/1000/discovervIgeHD.4.slave-socket
[COLOR=#ee82ee]vinny    14171  0.0  0.0  14428  1040 pts/3    S+   20:46   0:00 grep --color=auto discove[/COLOR][COLOR=#add8e6]r[/COLOR]

the line in pink is "grep" looking for "discover" , the line you want is the one in red that has "/usr/bin/plasma-discover"

you see it has a PID of 12598 , you can now use "kill" on the PID to , well kill it. like so

kill 12598

VINNY

That's what some of us would refer to as a 'tactical nuclear strike'; a much smaller, more precise nuclear option. Much less fallout.

[vinnywright]

That's what some of us would refer to as a 'tactical nuclear strike'; a much smaller, more precise nuclear option. Much less fallout.

LOL ,,,your on a role tonight

it's pretty much the same thing the scull & crossbones is doing behind the scene's but not as easy or graphically pretty ,,,,,,of course , those small tactical nukes are kind a pretty , as far a missiles go

VINNY