Bug 360142 - tried updating sources/ check for updates
Summary: tried updating sources/ check for updates
Status: RESOLVED NOT A BUG
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 15.08.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-05 20:34 UTC by Mark Rudeseal
Modified: 2018-10-24 19:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
what I see after using Konsole, muon updater/ and muon package manager, when trying to check for updates (292 bytes, text/plain)
2016-03-05 20:37 UTC, Mark Rudeseal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Rudeseal 2016-03-05 20:34:14 UTC
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.


Reproducible: Always
Comment 1 Mark Rudeseal 2016-03-05 20:37:16 UTC
Created attachment 97699 [details]
what I see after using Konsole, muon updater/ and muon package manager, when trying to check for updates

W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.
Comment 2 Mark Rudeseal 2016-03-05 23:34:06 UTC
ok, I found the reason for the failures.   

I am using google chrome, google has misreported something.
 I did not fix the error, I just unchecked the box in software sources that google had put in. (http://dl.google.com/linux/chrome/db/ stable main)
Comment 3 Julian Steinmann 2018-10-24 19:24:13 UTC
This does not appear to be a problem within Konsole. Please report such an issue directly to the maintainer of the repository (Google in this case). Thanks!