You are not logged in.
Thank you both. I guess the moral of the story is that if it sounds too good to be true, it probably is. Sigh.
I'll believe in a 100% libre phone where everything works when I see a RYF announcement from the FSF.
Sorry for the noise. I'll curb my enthusiasm with Purism and will support them with half of what I had planned to. I'd at least like to see them try.
I wrote to Purism. My question:
If you can't find existing peripherals (e.g., mobile WiFi and Bluetooth chips) that can run with 100% free software--no proprietary blobs anywhere--will you make (or ask someone to make) such peripherals for the Librem 5?
Their answer:
I asked our CEO directly, this is his reply:
"Yes. This is one of the reasons I formed Purism, to push the beliefs
into fabrication."-Mladen Pejaković
Purism support
Their goal is 100% free software, no blobs. That's implied in their desire to obtain RYF ("Respects Your Freedom") certification from the FSF--if there are blobs anywhere, FSF will not certify the phone.
This from their FAQ:
Are all hardware components running completely free software, with the source code available?
From testing the CPU, GPU, Bootloader and all software will run free software, we are evaluating the WiFi and Bluetooth chips and firmware, this is an area we have to evaluate, finalize, and test. The mobile baseband will most likely use ROM loaded firmware, but a free software kernel driver. We intend to invest time and money toward freeing any non-free firmware.
Will you be seeking FSF RYF endorsement?
We will constantly keep FSF up-to-date on the hardware and software, our current understanding is any non-free kernel firmware needed for RF chips will not meet the RYF qualifications today, so we will continue to evaluate the WiFi and Bluetooth cards in the hopes to advance toward RYF. The end goal for us is to gain RYF for all Purism products.
I don't like the vague "we will continue to evaluate the WiFi and Bluetooth cards". That needs some clarification.
Nevertheless, I think this effort deserves to be supported: How many phone developers have ever said "we intend to invest time and money toward freeing any non-free firmware...and the end goal for us is to gain RYF [certification]"?
P.S. I realize that this is a longshot given that Replicant has been at it for many years and has yet to deliver a libre phone where everything (including WiFi and Bluetooth) works. Nevertheless, I'm cautiously optimistic about the Librem5 given that, unlike Replicant, Purism will be building the phone themselves out of components they have selected/made.
https://puri.sm/shop/librem-5/
I've been looking for a completely libre GNU/Linux phone for many years. It sounds like the Purism folks are serious about trying to build such a device.
Here's version 2.0, with cleaner logic and a new feature: Cursor disappears during video/audio playback (requires that the "unclutter" package be installed).
#!/bin/bash
while true; do
sleep 10
if grep -q RUNNING /proc/asound/card*/pcm*/sub*/status; then # there is sound, so we want "movie mode"...
# xscreensaver nudge:
/usr/bin/xscreensaver-command -deactivate
# screensaver-agnostic nudge:
# xdotool key Pause
pgrep unclutter || unclutter & # if unclutter isn't running, start it
else # there is no sound, so no "movie mode"...
pgrep unclutter && pkill unclutter # if unclutter is running, kill it
fi
done
TL;DR version: There is nothing wrong with your Devuan Jessie install or with your Samsung phone. You just need a more recent heimdall than what's in the Jessie repository Link to what you need is at the end of the post.
So, I got one Samsung Galaxy S5 for myself and one for the wife, with intention of installing TWRP recovery and LineageOS 14.1 on them. First step is to install TWRP via heimdall.
To test whether heimdall is working, put your phone in "Download mode" (with phone off: volume down + home + power), connect it to your GNU/Linux box, and run this in a terminal as regular user (i.e., without sudo):
heimdall print-pit
My heart sank when, on my Devuan system, this is what happens after the above:
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I got the idea in my head to try a newer heimdall package from Debian Stretch, Buster, or Sid. This is what I get with those:
heimdall: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by ./heimdall)
heimdall: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./heimdall)
The issue here, as you may have guessed, is that the newer packages are compiled against a glibc version that's newer than Jessie's (glibc is forwards-compatible but notoriously not always backwards-compatible).
What you need to do is to compile heimdall from source (to get latest version), on Devuan/Debian Jessie or older distro (so that the package is compiled against Jessie's glibc or older).
I did the above and all errors went away when I used the resulting binary. The phones are now loaded with TWRP and LineageOS
If you don't know how to compile or don't feel like the hassle...
Here is the .deb: heimdall-flash_1.4.2_amd64.deb
If you prefer just the binary, here is is: heimdall 1.4.2 amd64
Enjoy,
Bruno
greenjeans wrote:golinux wrote:Relax and enjoy the stability that 'just works'.
You know, it's funny, because probably nobody that ever posts on this forum will ever do that . . .
Well, I do! I like stable and boring and only try new things when absolutely necessary.
Ditto! I love stable and boring. It's nice to turn my computer on and know exactly what to expect day to day. I'm perfectly happy with Devuan Jessie
a hardcopy is what you print on your own
Yes, I think this is what I'll end up doing. I work at the computer all day and last thing I want when I'm reading "for fun" is more screen time.
Here's a cornucopia of online texts:
https://www.quora.com/What-is-the-best- … -hand-outs
I think I'm going to give up on finding a hardcopy book. I've been looking around for three days and the books that look interesting are at least 10 years old
I figured. The book doesn't have to be super recent. I'd be happy with something 5 years old or less.
I found this: http://lartc.org/howto/
Almost exactly what I'm looking for, but hoping to find a hard copy book.
I'm looking for a book (real one made from dead trees to hold in my hands) on networking, taught from GNU/Linux perspective so that I can experiment at the command line with different utilities. I am comfortable with the very basics (IP addresses, DHCP, DNS) but want to get a grip on jargon such as NAT, DMZ, MASQUERADE, etc. Details of routing and firewalls are especially intimidating and are the topics I want to learn the most.
I've looked around but the books I'm finding tend to have one or more of these problems:
- Too old
- Too advanced
- From Windows perspective
Do any of you have a favorite book that helped you go from noob to confident intermediate skills in networking (especially router and firewall settings)?
@fungus: Fair enough.
Back to the problem at hand. I definitely found a pattern: When the laptop is on AC power, the USB 3.0 ports on the ExpressCard work just fine. Strange that the card slot doesn't provide the card enough power to work when on battery power, since my battery is in good condition. Oh, well. I'll mark the issue as "solved".
Only free software from main repository on both Debian and Devuan, so that's not it.
I discovered (via lshw) that the driver is xhci_hcd. lsmod shows that the respective kernel module is loaded on both Debian and Devuan.
@fungus: Not to get political, but your signature invites it Respecting other people's right to free speech does not constitute endorsement of their worldview.
Devuan comes with dbus by default. I can confirm that dbus-daemon is running on my Devuan Jessie installation.
When I plug the same thumbdrive into a USB 2.0 port, it automounts to /media (specifically, to /media/bruno/PATRIOT).
I'm on a Thinkpad T400 with Devuan Jessie + MATE. The laptop only came with USB 2.0 ports. However, it does have a 54 mm ExpressCard slot that until now has never been used.
As a little upgrade, I decided to get a an ExpressCard with two USB 3.0 ports (this one). Devuan seems to detect it:
bruno@thinkpad:~$ lspci
---snip---
04:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)
---snip---
But when I plug a thumbdrive into one of the USB 3.0 ports, nothing happens: Device doesn't automount, doesn't show up in caja's side pane, its little light doesn't even blink. The thumbdrive automounts in Devuan just fine when I use one of the laptop's built-in USB 2.0 ports.
I tried booting into my Debian Jessie + MATE partition--which I kept to kick around in troubleshooting situations such as this--and no problems there: In Debian, when I plug the same thumbdrive into one of the USB 3.0 ports, caja automounts it as expected.
Can you please help me make these USB 3.0 ports usable in Devuan Jessie?
EDIT: The fix (if you can call it that) is in post #8.
I'm happy to hear that you're in good shape, and that these issues are not present in ascii
Adding the "unset" line to /usr/bin/thunderbird is a good idea with one caveat: An upgrade to TB will overwrite the file. A wrapper script is ugly but upgrades will leave it alone.
You're welcome, Armin. Ha ha--we're both refugees from Gnome3/systemd
Thanks for inspiring me to do things the right way, and for the link to the Enigmail FAQs. That was huge.
Given how similar our setups are, it's a safe bet that the steps in #5 above will work for you. Please let me know how it goes.
BTW, I tried uninstalling gnome-keyring to see what would happen (i.e., to see if I could get away with not having a wrapper script). Unfortunately, it seems that network-manager requires gnome-keyring (or the like) to prompt for wifi passwords.
If I understood the discussion here correctly (see Hans' post at the very bottom of page 1), it seems that currently there are two options for getting full Enigmail functionality without interfering with packages that need a keyring:
(1) Leave gnome-keyring installed, requiring a wrapper script for Thunderbird (as I outlined in #5 above)
or
(2) Uninstall gnome-keyring, install the better-behaved mate-keyring, dump the wrapper script. The fly in the ointment is that mate-keyring is deprecated and no longer in Debian/Devuan repositories--it would require finding it somewhere and downloading it.
Between using a wrapper script or using a deprecated package not in the repository, the wrapper script option seems to better follow the KISS principle.
If anyone can think of a way to get gnome-keyring to stay out of Enigmail's way without resorting to a TB wrapper script, please do tell.
I try to install nearly everything from packages because my hope is, that upgrades are as smooth as possible
I'm not sure staying at TB 45.8 is a good solution, since the upgrade is marked as a security-upgrade.
I completely agree. It was pure laziness that was holding me back.
At any rate, since my laziness was called out I went ahead and upgraded thunderbird and installed enigmail (version 1.9.8) from Devuan repository using package manager--then took a deep breath to deal with the fallout.
From reading Enigmail's FAQ, it seems the Enigmail developers are most familiar with gpg-agent/pinentry and not gnome-keyring and the like. I'm on MATE with gnome-keyring and decided to see if my problems would go away if configured Enigmail to use gpg-agent/pinentry instead of gnome-keyring.
Here is how I configured Enigmail to use gpg-agent and pinentry instead of gnome-keyring:
1. Add "use-agent" (without quotes) to ~/.gnupg/gpg.conf
2. Add "use-standard-socket" (without quotes) to ~/.gnupg/gpg-agent.conf (if the file does not already exist, create it)
3. Reboot
Launch Thunderbird and try using Enigmail. If the window that pops up asking for your password is not called "pinentry", then gnome-keyring is forcing itself on Enigmail and you need a few more steps (I needed steps 4-6 as well, so don't feel bad):
4. Create /usr/bin/thunderbird-wrapper with your favorite text editor, put this in it:
#!/bin/bash
unset GPG_AGENT_INFO
exec /usr/bin/thunderbird "$@"
5. In a terminal, make the wrapper script executable:
sudo chmod a+x /usr/bin/thunderbird-wrapper
6. Make sure that the Thunderbird icons in your menu +/- panel point to /usr/bin/thunderbird-wrapper and not /usr/bin/thunderbird
Reboot, launch Thunderbird, and try using Enigmail again. The window asking for your password when you use Enigmail should now be called "pinentry" and everything should work (encryption, signing, decryption, remembering pin for desired time period).
PS: Armin, I just realized that my previous post did not answer your questions.
In my case, Enigmail was not upgraded automatically because it was installed from within Thunderbird. I'm not a Devuan developer, so if you had Enigmail 1.8.2 installed as a .deb package then I do not know why it wasn't upgraded along with Thunderbird. Even if they both had been upgraded together, however, I am finding that Thunderbird 52.2.1-4 + Enigmail 1.9.8 break ability to send signed messages.
Hi, Amin. All my machines receive automatic security upgrades and I was surprised by this same issue: Havoc in proper functioning of Thunderbird's Enigmail plugin after Thunderbird upgrade to version 1:52.2.1-4~deb8u1.
I found that a newer version of Enigmail restored my ability to send encrypted email. However, if I want to both encrypt and sign, sending fails. Error messages appear in two successive windows:
GnuPG reported an error in the communication with gpg-agent (a component of GnuPG)
then
Sending of the message failed.
The "How to fix" tidbit from the Enigmail website (adding "use-standard-socket" to $HOME/.gnupg/gpg-agent.conf and rebooting) made no difference--signing a message still prevents it from being sent.
Enigmail can be obtained as a .deb package and installed by the package manager, or obtained as a .xpi package and installed from within Thunderbird (Thunderbird > Tools > Add-ons > click on down-arrow next to the little gear > "Install Add-on From File").
My workaround for the time being is to stick with the pre-upgrade versions of Thunderbird (45.8.0-3~deb8u1) and Enigmail (1.8.2 xpi package).
To prevent Thunderbird & Enigmail from being upgraded, I created /etc/apt/preferences.d/thunderbird-keep-v45 with these contents...
Package: thunderbird
Pin: version 1:45.8.0-3~deb8u1
Pin-Priority: 1001
...and in Thunderbird > Tools > Add-ons > click the down-arrow next to the little gear > make sure there's no checkmark by "Update Add-ons Automatically".
My "nasty hack" contribution: A startup script that runs your custom shutdown/reboot jobs (yes, you read that correctly ).
#!/bin/bash
payload()
{
command_or_script1
command_or_script2
command_or_scriptN
}
trap payload TERM
kill -SIGSTOP $$
To use it, just add this script to your startup applications and replace the placeholders with the commands or scripts you want to run at shutdown/reboot.
How it works: When executed, the script immediately stops itself. It stays in stopped state while system is running (or suspended). When you shutdown or reboot your system, every process (including stopped ones) is sent the TERM signal. In the case of this script, when it receives the TERM signal it runs the payload function containing your shutdown/reboot jobs.
What inspired this hack is the fact that it always seems easier to setup startup jobs than shutdown/reboot jobs.
If you are paranoid about privacy like me, you will like this little creation of mine.
EDIT: Final version of script is in post #7. Options for running it automatically at appropriate time are in post #8.
Yes! This caused thumbnails to show up for everything:
rm -r ~/.cache/thumbnails