It was a wild guess at what might cause the issue at the _host_ side which is not PureOS.

@jeremiah.foster It does not make sense to me why/how this bug is closed.

For the record (as I understand time's up for your concrete case), use of Logical Volume Management (LVM) can provide a user experience of a single "virtual" partition, stitched together from multiple underlying physical "volume" partitions.

well, in my splitting-hairs mode it is factually alarming: It set off an alarm, of the cenventional blinkenlight type.

I believe it is only the install routines for PureOS that has problems with EFI, the installed PureOS works fine with EFI.

@jeremiah.foster I recommend to put as issue subject the issue (not its solution), and not rename to its solution when closed either: Example: References will then sensibly show the _problem_ as striked out, not confusingly that the solution is striked out.

You were told that this is a pristine live image, or you are guessing?

Yes, PureOS is a general purpose operating system, it is possible to install things on it that attempts to contact a certain IP number every time it boots.

Seems to me that problems running PureOS in an emulator is an issue with that emulator.
I can suggest that you try raise this as an issue in Ubuntu.
A wild guess could be that you use some non-free graphics driver (e.g. for NVIDIA hardware) which might work great for some things but have issues with other things.

This was reported in Debian recently: http://bugs.debian.org/921030

(hm, not really resolved, but seems that's the option we got in this interface)

Thanks for trying, @jgn2112

@jeremiah.foster Better to merge new issue into older - especially when the older is referenced from other places as is the case here.

Thanks for clarifying, @jeremiah.foster - I hope the current title is suitable.

@jeremiah.foster please elaborate on your title change - is this issue not about _continuously_ updating at a faster _pace_ but only about getting some specific new version?!?

How is this issue different from T11?

Thanks for mentioning, @guido - I had missed T594 now linked here.

Tracking fast-changing packages in particular need strong monitoring e.g. by somthing like security-tracker.debian.org.

I find that expressing tickets as what is wrong helps.

@jeremiah.foster: No, this ticket is explicitly about the functionality, not branding of it!

Seems you are on the right track in that the error message indicates FileZilla is requesting a feature unavailable in GnuTLS. The exact cause for you may not be same as the one addressed in the bugreorts you found - they might just be for similar kinds of issues.

This is not (by our definition) a freedom issue: It does not involve installing non-free software locally.

This is not a freedom issue (by our definition), since it does not involve installing non-free software locally.

This is not a freedom issue, since it does not involve installing non-free software locally.

This is not a freedom issue, since it does not involve installing non-free software locally.

@mak ping!

@mak ping!

@mak ping!

Please drop forked package now, @mak

@mak ping!

@mak Ping!

This issue seems possibly related to an issue in LibreOffice resolved today in debian (and thus not yet in PureOS) by tightening its dependency on apparmor: https://bugs.debian.org/918499

@mak Please have a look at this - smells AppStream-related.

I suspect that the line with UbuntuDrivers is totally unrelated and just a warning (despite the confusingly misleading initial word in captial letters).

@jeremiah.foster does it spew anything _after_ that error message about UbuntuDrivers?

ah - sorry, @EchedeyLR: Seems my window didn't refresh properly so I missed your latest response above. Thanks!

(me awaits responses from both @jeremiah.foster and @EchedeyLR for clarification, but suspects this issue is totally unrelated to that "UbuntuDrivers" message and instead the issue relates to AppStream...)

@EchedeyLR What is the output of this command:

@jeremiah.foster: Do you experience same issue, or do you talk about GNOME Applications because the stacktrace in the error message hints about it being tied to software-properties-gtk?

Sorry, I put it on task's name but not into description.

...or @jeremiah.foster maybe you can clue me in here: What is "this particular piece of software" that you are talking about? Perhaps I am missing something obvoius here, but I am totally clueless right now :-/

Sorry, I don't follow: which applications are we talking about here?

reporting bugs is not an accurate science - it is highly appreciated that you filed a report when only suspecting a potential issue here, @Wayne !

@Wayne yes I meant to suggest that you file an issue (here on tracker.debian.net, not in the forum) about our forum triggering warnings about fingerprinting.

Thanks for those details, @Wayne!

DuckDuckGo is no longer privacy-protecting: https://forums.whonix.org/t/duckduckgo-now-fingerprinting-visitors/6497/1

Seems that website doesUser-Aagent sniffing.

Now just lean back and drink gin&tonic for a few weeks while Debian and Laniakea processes it to PureOS green :-D

Package is libhostfile-manager-perl tracked in Debian as bug#916437.

@chris.lamb: Please have a look at the Debian package now in NEW queue, and approve if acceptable.

In T595#12043, @sean.obrien wrote:

the recommendation was unofficial and I'd rather not push on it...

Seems directly tied to Laniakea: Assigning to @mak

@sean.obrien Is the conversation with Mozilla, leading to their suggesting that particular string, public? If so, please provide URL.