Bug 402571

Summary:	i get error message on starting discover after upgrading to neon 18.04 'the repository http://archive.neon.kde.org bionic release does not have a release file'
Product:	[KDE Neon] neon	Reporter:	keharuan
Component:	Packages User Edition	Assignee:	Neon Bugs <neon-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	jr, nate, neon-bugs, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	split screen image for both error msg and viber update issue

Description keharuan 2018-12-26 01:45:36 UTC

Created attachment 117112 [details]
split screen image for both error msg and viber update issue

SUMMARY
updated from neon 16.04 to 18.04 based OS. Whenever i open discover i get the message 'the repository http://archive.neon.kde.org bionic release does not have a release file'( screenshot attached in top part of image). 

1) Up until a week ago i was unable to update packages although updates were available(the options for 'check for updates' and 'update all ' were in white and couldnt be clicked. this was reported as a bug ( bug 399981) by other users and seems to have been resolved. 
2) i have another issue where i cant update viber (flatpak) although i see there is an available update (screenshot attached in bottom part of image). I mention these two problems in this report because im not sure if the cause for both of them is the 
above-mentioned message i get whenever i start discover.


STEPS TO REPRODUCE
1. start discover
2. 
3. 

OBSERVED RESULT
1)error message at the bottom. 2)cant update viber although update is available


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Justin Zobel 2023-01-19 00:19:05 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 2 Bug Janitor Service 2023-02-03 05:02:22 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2023-02-18 03:48:05 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!