@dukethereal assuming your talking about the #librem5: yes, with the right docking station you can have usb, #DisplayPort over #usb-c and PD-charging at the same time.
I got one more change in for GNOME 40: better tab completion in the file manager! It's bothered me for a while now, so I'm especially excited that I got to improve it: https://www.jwestman.net/2021/02/17/files-tab-complete.html
Huge thanks to @antoniof_gnome@twitter.com
for reviewing this just in time for the release!
Call to apply for FSFE support for your local project
If you currently look for financial funding for your FSFE activity, we are happy to support you: https://fsfe.org/news/2021/news-20210219-01.html
Deadline: 18.April 2021
Receiving MMS on the #librem5 is working now, using #ModemManager and mmsd and #chatty, after some recent fixes including an addition to libqmi to allow sending ack for "transfer route MT" messages, see https://source.puri.sm/Librem5/chatty/-/issues/30 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/257 #phosh #UserFreedom #mobile #gnu #linux #freesoftware @purism #gnomeonmobile
#MadeAThing …and a year later @brainblasted finally got it out into the world (Thank You :-) )
Typography is another little “tool-app” from the @gnome Design Tooling Team as a companion to (Colour) Palette offering buttons to copy various css classes/characters you may need in your app/mockup
Along the way we got a couple of gtk4 bugs ironed out, thanks @exalm et al for the help with that
As ever some nice artwork from @tbernard
https://flathub.org/apps/details/org.gnome.design.Typography
A friend asked me how to automatically start #GNU #Screen directly via #SSH's configuration file. Here's how to do it:
Add an entry to ~/.ssh/config similar to this one:
Host screen_on_server
Hostname server.example.org
RequestTTY yes
RemoteCommand screen -RD
and then just call
$ ssh screen_on_server
and you'll get connected to an existing screen session if present, otherwise you'll a new new one.
Should work with #tmux, too, maybe different options.
@linmob Are you aware that you can scale #phosh via Settings since 0.8.0? Not fractional but 100% / 200%. It's basically a side effect from the multi monitor setup: https://social.librem.one/@agx/105499360410493591 - necessary GNOME Settings bits are upstream already: https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/942
The Release Team heats up Debian Bullseye with a soft freeze: https://lists.debian.org/debian-devel-announce/2021/02/msg00002.html
#phosh 0.8.1 is out 🚀 : https://source.puri.sm/Librem5/phosh/-/releases/v0.8.1
Mostly bug fixes and cleanups this time around from @eliasr , @dos and yours truly.
@debacle the #librem5 user's manual has end users as audience and explains some bits about #phosh https://docs.puri.sm/Librem_5/First_Time_Use.html#using-the-phone-for-the-first-time
@okennedy not sure i understand. gnome-tweaks and Shell extensions are two different thinks AFAIK. There's no plan to make phosh/phoc compatible with GNOME Shell Extensions since they're very specific to the shell intrinsics.
#librem5 docked day4:
- More 'boring' setup for daily work: #mumble, #flatpak
-- `gsettings set org.gnome.desktop.input-sources xkb-options "['compose:caps', 'lv3:ralt_switch']"`
- most remaining papercuts are in #phoc/#phosh around window placement and good defaults
So from now on I'll just update when something changes (for the good or bad)
@dukethereal you can basically forward everything to the #librem5 you'd forward to your laptop (#vnc, #rdp, ...)
#librem5 docked day3:
- nothing too exciting (mail prodding finish up elpa/#emacs config)
- noticed one issue where textures sometimes get corrupted after display power save. Doesn't look like https://source.puri.sm/Librem5/linux-next/-/merge_requests/233 or https://source.puri.sm/Librem5/linux-next/-/merge_requests/249 so needs investigation.
#librem5 docked day 2:
- Move #gpg config over so #nitrokey works on the dock (hello encryted email, package uploads, ...)
- Join #matrix via element until #chatty fully covers it
- Figure out #gssapi smtp in #mutt needs libsasl2-modules-gssapi-mit (so say goodby to the last on disk location that stored account passwords unencrypted)
- unbreak plymouth in #PureOS #Byzantium so it doesn't force meta packages off the system (https://source.puri.sm/pureos/core/plymouth/-/merge_requests/1)
- no crashes so far