- User Since
- Nov 30 2018, 9:26 PM (7 w, 3 d)
Sat, Jan 19
Will do! I've used both in the past, but found GBP's branching model confusing. Jonas and Matthias have recommendations so I hope to find something that works. :-)
Sorry, I haven't included my debian/ directory yet. I wanted to include a 'pristine' source. Of course I have added a patch, so it isn't pristine, but I wanted to get the source into salsa since there seems to be some movement with the ITA bug in Debian's bug tracker and hopefully we can all work with the same source.
Fri, Jan 18
Looks like you're booting the Purism Librem 13 v2 with a 4.17.0-3 Linux kernel. I'll see if I can find a machine to reproduce that error. In the mean time, would you try and boot from the latest live disk? https://pureos.net/download/ Instructions are here: https://tracker.pureos.net/w/installation_guide/live_system_installation
I've uploaded lastest flashrom code to salsa on debian.org; https://salsa.debian.org/jeremiah-guest/flashrom
Next step (happening now) is to build the package for PureOS and then share any useful artifacts with Debian maintainer.
Thu, Jan 17
Thank you everyone. Please re-open if you see any issue related to this at all. I appreciate all the work done on this issue and the high quality communication from everyone! It is quite satisfying to close this bug and I hope we can continue to resolve issues. Okay, enough of my blather.
Wed, Jan 16
I think we can close this, but I'd like more input from the original poster.
This is an ancient bug. I think we should move it to "won't fix" or try and fix it.
This is a known issue unfortunately; T155 I'll see if we can't update the status of that bug to solve this issue.
Mon, Jan 14
On my machine;
It is confusing for sure. :-)
A couple other issues with this particular piece of software;
- It is listed as being 'proprietary' software
- It won't run when one clicks on "launch" (see screenshot)
Fri, Jan 11
Thu, Jan 10
Reopened the issue until it can be confirmed there is a fix in our repos.
So you get this message when you boot from your laptop? (I just want to make sure you're not booting from the USB stick.) Do you have the USB stick plugged in when you boot? If so, if you could remove it and then reboot and see what it says.
Martial -- do you have more feedback? Have you been able to boot?
We need more feedback on this issue. Closing for now, re-open if necessary.
Thanks to Birin Sanchez for this work around, tested here with a slightly later version 6.0.5-2, and functioned as expected.
Mon, Jan 7
Looking at GNOME's Screenshot with Strace I don't see a call to external networking resources. Running this command;
Sun, Jan 6
The video mentions specifically a couple of items;
- Tor browser launcher not installed on device at default. (16:33)
- httpseverywhere not isntalled (16:59)
- Google is the default search engine (17:32)
- Does using the default Wayland build change settings in the browser (comments re: 13:33)
Sat, Jan 5
Thanks Wayne, I'm glad to hear you're not dead in the water. Thank you for your patience as well. Sadly I didn't have time to drill down and find out more about the situation with dependencies yesterday, I hope to try and get some clarity on this today, but no guarantees as its a weekend. :-)
Fri, Jan 4
Thu, Jan 3
apt show hplip
shows, among other dependencies, this line;
wget, python3 (<< 3.7), xz-utils, python3 (>= 3.6~),
which seems to imply you won't be able to install this unless your python is higher or equal to version 3.6.* but not 3.7. I don't know how many releases of python there were like that but I can't imagine many.
Having an acceptance criteria (AC) in the issue might help, we can put it in the Description. Having an agreed upon "Definition of Done" is also useful and you've provided an example of DoD we can use, when the issue is in Green.
Just for the sake of clarity, you want to install PureOS on USB attached drive? So you're looking to have a persistent version of PureOS on the USB drive?
I just completed a bluetooth transfer of a photograph from my Pixel to the Librem 13 v3.
I did an apt update and installed a new deb -- firmware-atheros -- and that helped the situation. I have Debian repos enabled, not sure if firmware-atheros is in PureOS repos.
I can confirm this, seeing similar issue.
Tue, Jan 1
Yes, that would be my advice. You can do a dist-upgrade anyway and try and fix your system if it gets in a misconfigured state, but that can be time consuming and difficult. Usually with ten days or so that type of package conflict goes away as new software and bug fixes come into the repos.
So, there is a kernel panic because the kernel can't seem to find a file system to mount. How did you install GNOME? Did you use a USB stick or an ISO or similar? Or are you using apt-get or some other means?
The Librem's have a version that I think represents the physical device on that back, one of my Librems says "Librem 13, version 3." If you want to find the software version, or version of the overall OS, try this command (you may have to install inxi);
$ inxi -Fxrz
Which on my system produces;
System: Host: sigmund Kernel: 4.18.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0 Console: tty 1 Distro: PureOS base: Debian buster/sid Machine: Type: Laptop System: Purism product: Librem 13 v3 v: 3.0 serial: <filter> Mobo: Purism model: Librem 13 v3 v: 3.0 serial: <filter> BIOS: coreboot v: 4.7-Purism-4 date: 03/20/2018 Repos: Active apt repos in: /etc/apt/sources.list 1: deb https://repo.puri.sm/pureos green main Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://deb.debian.org/debian stretch main contrib non-free 2: deb-src http://deb.debian.org/debian stretch main contrib non-free 3: deb http://deb.debian.org/debian stretch-updates main contrib non-free 4: deb-src http://deb.debian.org/debian stretch-updates main contrib non-free 5: deb http://security.debian.org/ stretch/updates main contrib non-free 6: deb-src http://security.debian.org/ stretch/updates main contrib non-free
You can see from output above that I'm running a 4.18 kernel. My distro is PureOS that is based on Debian Buster / Sid (so testing) and that my repos are PureOS 'green' mixed with Debian stretch. In the "Machine:" line I note that the coreboot version is 4.78-Purism-4 from 03/20/2018. I don't know where can find the date PureOS "green" and green may be a rolling release which means that the userland packages (and kernel potentially) are updated continually.
Fri, Dec 28
I think that the version of PureBrowser you showed there is quite old. I wonder if we need to discuss with the distributor about updating the software on the devices? I propose we bring this to a Production / QC meeting.
Is this a duplicate of https://tracker.pureos.net/T595?
Dec 22 2018
This is not so surprising for a 'dist-upgrade'. I don't know if you want to do the dist-upgrade or not, perhaps you need those important packages and don't want them removed, but if you like you can try just doing a regular apt upgrade that will not be as invasive.
Cool. I have another Librem that was sent to me for testing, I'm going to look for this too on that one. I worry that some of the machines may be shipping with older software.
This appeared on a laptop that was shipped to me this week. I'll check the vintage of the software.
Dec 21 2018
Can you share the command you used? Also, what is in your /etc/apt/sources.list (or /etc/apt/sources.list.d/* ?
Dec 19 2018
I can't reproduce this.
What is the error message you're getting from update-initramfs?
Dec 18 2018
I think making a flatpak and hosting that flatpak is an acceptable approach. This is why;
It feels like there is a decision to be made here: are we going to invest time and resources in PureOS components when they are not in Debian yet? My feeling from the team is that the answer is an emphatic "yes."
Dec 13 2018
Thank you David. I'm going to take the C as a passing grade and close this tracker item concluding that Gitlab CE is sufficiently free for our purposes.
More discussion on this topic upstream: https://gitlab.com/gitlab-org/gitlab-ce/issues/51287
NB: This thread ^^ is about Gitlab Community Edition.