On boot I am seeing
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 10 2018
May 9 2018
Yes, the package manager. There was no output from terminal when launched. I needed to determine another package version (Synergy) that was available, but if Synaptic is going to be dropped this ticket could be closed.
This could indeed be related to stripped firmware as the firmware we strip out (the intel nonfree firmware) indeed contain power management parts.
Coreboot splash screen (with Purism logo) provides that info. Are you using latest coreboot? Note that it is indeed fast in showing that but putting some higher timeout would annoy users who want fast boot :-/
Synaptic the package manager? Please attach the output from terminal once you launch it.
Also note that synaptic does not have (at least last time I checked) Wayland support nor do I know any effort to port it so it will most likely drop from archive in time.
May 8 2018
May 5 2018
May 3 2018
Apr 30 2018
Apr 29 2018
Broken again. Please stop breaking dependencies! This should be trivial to automatically test.
Thanks for the suggestion.
This was addressed in Debian today with the release of kodi 2:17.6+dfsg1-2.
Consequently should likely reach PureOS in ~1 month.
This is not really a duplicate of T255, but rather an issue concretely actionable since it is isolated to a specific package, whereas T255 is a meta-issue tracking the broader concept.
Apr 27 2018
The issue remains. I'm informed of this "unable to install" issue everytime I open Software.
If you go to the hamburger menu and then add ons, you'll see the attached picture. In the past this was directed to a FSF add on page. After loading up the most recent build on a test machine without Firefox installed, the normal Firefox add-ons page is shown within PureBrowser. So the original issue remains despite my being incorrect as to the cause.
Apr 26 2018
Apr 25 2018
This should be addressed in the latest images, I am not sure though if the solution covers all cases (I could only do limited testing).
So, please reopen the issue in case this happens again!
That's a weird one... Can you still reproduce the issue? Can you verify that the "packagekit" package is installed?
What exactly does "issues" mean? What did you try, what did you expect and what was the actual result and error message?
Likely some GNOME weirdness. Needs to be investigated, the image sets should be identical.
Calamares should never even show up in the software center. I marked it's .desktop files to be ignored from inclusion in the software catalog now (effective as of calamares >= 3.2~rc4-0pureos5)
Thanks for noticing!
Keysafe is packaged for Debian - but only targeted experimental: https://tracker.debian.org/pkg/keysafe
We might want to also include Symbola (fonts-symbola) which in my experience fills the gaps on more obscure and newer emoji (and other bits of Unicode). It seems Symbola is not that great for emoji, so I withdraw this suggestion. Still good for ancient fonts, but I'm not sure those will see everyday use :D
Part of the solution may involve backing up (not syncing) your own GPG key, which could be achieved with something like Keysafe
Apr 24 2018
ok. Please in future use chat for guidance - or the user support forum, perhaps - as issue tracker is better suited to track issues (bugs and pseudo-bugs like wishlist requests) tied to components of the Operating system.
Perhaps I should have been clearer, this was just a query about *how* to check that my second disk is encrypted. You have answered my query so I closed the ticket :)
I am confused: Did that actually fix the reported issue?
Seems an issue for @mak.
Seems an issue for @mak.
Seems an issue for @mak.
Seems an issue for @mak.
Seems an issue for @mak.
Seems an issue for @mak.
Seems an issue for @mak.
Thanks! lsblk results:
Please consider filing an RFP bug in Debian - and then reference the resulting bugnumber here: https://www.debian.org/Bugs/Reporting
Please consider filing an RFP bug in Debian - and then reference the resulting bugnumber here: https://www.debian.org/Bugs/Reporting
One way to inspect what is on encrypted volumes is typing lsblk in a terminal - volumes in branches off of a *_crypt entry is encrypted.
Perhaps you typed "255" in the popup dialog, where it expects "T255"?
At best, this is low priority.
Hmmm, this should be closed as a duplicate of https://tracker.pureos.net/T255 but I can't bring it up :P