The problem after the transition to the test branch

Bug #1804167 reported by Artem Konkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
flatpak (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hello to all!
Sorry for my English, I am writing through a translator from Russian.

There was a problem after switching from a stable branch to dev/unstable by changing /etc/apt/sources.list.d/neon.list to

deb http://archive.neon.kde.org/dev/unstable bionic main
deb-src http: //archive.neon.kde.orgdev/unstable bionic main

Attached screenshots of the loading in the normal mode and the "system testing" in the recovery mode.

KDE Neon Ubuntu 18.04 based

Tags: kde neon
Revision history for this message
Artem Konkin (temakonkin) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue seems to have to do with flatpak

affects: ubiquity (Ubuntu) → flatpak (Ubuntu)
Revision history for this message
Andrew Hayzen (ahayzen) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

So this seems like network manager failed to start correctly (?) and then some service trying to configure a flatpak repo became stuck. I have spoken to the flatpak developers and they are not aware of such a service (maybe it is something specific to KDE?). Also you have switched to an unstable branch, so maybe something is broken within that.

Could you provide more information from syslog/journalctl ? Eg what caused network manager to fail (systemctl status NetworkManager-wait-online.service) and also look in syslog/journalctl for errors around the same time related to flatpak and copy them here ?

Until there is more info as to what is happening I'll mark this as incomplete.

Changed in flatpak (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for flatpak (Ubuntu) because there has been no activity for 60 days.]

Changed in flatpak (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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