openSUSE Leap 15.4 安裝小記
openSUSE Leap 15.4 安裝小記
openSUSE Leap 15.3 Lifetime 到 2022/11
15.4 可以撐到 2023/11
過了一年又到升級的時候 :)
安裝前處理
使用 imagewriter 建立 openSUSE 安裝USB
整理 /home/sakana 目錄
使用 du -h --max-depth=1 /home/sakana 檢查
清掉不要的檔案, 特別是 ~/.cache , ~/.config 內兩大瀏覽器內有佔很大空間的 cache ( 這次懶得刪就沒有這樣做 )
因為有很多相關的 config 在個人家目錄內, 所以先把舊的 openSUSE Leap 15.3 的 /home 目錄, 切換到隨身碟的目錄中
使用# tar cvf home.tar /home 進行打包到隨身碟 ( 不要使用 .gz 方式, 會比較快速 )
如果剛剛的光碟 ISO 放在下載目錄, 記得刪除來節省空間
新機器再使用 tar 指令還原回來
這次先在 console F1 以 root 使用者,
使用 tar 指令解壓縮 home.tar 到隨身碟目錄
刪除 /home/sakana 目錄, 將解壓縮的檔案直接移動過去
這次也是使用 USB 來進行安裝
== 安裝過程小記==
這次建立的時候我還是選擇 GNOME 桌面
磁碟區分割的部分, 使用引導的方式安裝, 因為一直出線開機分割區的警告, 所以我就用引導模式
刪除所有分割區
建立獨立分割區 XFS
根目錄取消 Btrfs 快照
===============
Network Manager:
openSUSE Leap 15.4 預設為 Network Manager
Google Chrome:106
https://www.google.com/intl/zh-TW/chrome/browser/
還是會有驗證性問題, 但是功能沒有差異
為了進行google 登入,先使用 Google 驗證App, 後面來處理yubikey
home 資料回復:
因為有很多相關的 config 在個人家目錄內, 所以先把舊的 openSUSE Leap 15.0 的 /home 目錄, 使用# tar cvf home.tar /home 進行打包到隨身碟 ( 不要使用 .gz 方式, 會比較快速 )
新機器再使用 tar 指令還原回來
這次先在 console F1 以 root 使用者,
使用 tar 指令解壓縮 home.tar 到隨身碟目錄
刪除 /home/sakana 目錄, 將解壓縮的檔案直接移動過去
Notes
Ifconfig 預設沒有安裝, 要使用 ip address show
關閉GNOME裡面的搜尋功能預設關閉 (點選右上角的設定按鈕), 因為我覺得用不到
中文輸入法問題:
這次預設是 ibus 輸入法
取消 USB 為安裝來源:
# yast2 repositories
Snapd:
因有些軟體可能會透過 snap 來安裝
安裝方式紀錄
# zypper addrepo --refresh https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.4 snappy
# zypper --gpg-auto-import-keys refresh
# zypper dup --from snappy
# zypper install snapd
Additional rpm output:
Please reboot, logout/login or source /etc/profile to have /snap/bin added to PATH.
On a Tumbleweed and Leap 15.3+ systems you need to run: systemctl enable snapd.apparmor.service
可以重開機, 登出登入, 讓 路徑變數內有 /snap/bin 這個路徑
在 X 11 下就是開一個新的終端機切換為 root, 檢查 $PATH
建議使用重開機的方式
# systemctl enable snapd
# systemctl start snapd
# systemctl enable snapd.apparmor
# systemctl start snapd.apparmor
如果安裝應用程式, 可能重開機才會找的到
Freemind:
因為 Freemind 在 Leap 15.4 只有社群維護套件
之前是用 snap 安裝, 但是這次有問題,
所以先用社群維護版本來安裝 https://software.opensuse.org/package/freemind
我用 home:beyerle:IAC 那個版本, 然後把他 repo 裡面的 SLE-15-SP1 ~ SLE-15-SP4 停用了
將.mm 的檔案指定用 freemind 開啟
以後應該要考慮其他的方案
有看到 freeplane https://docs.freeplane.org/ 下次試試看
新增 Packman 套件庫:
使用 #yast2 repositories 加入社群版本的Packman
#yast2 repositories
除了 Packman 順便加入 nVidia 套件庫
Firefox Sync:
登入 Firefox Sync, 會處理之前有下載的 Plugin
例如 https://addons.mozilla.org/zh-TW/firefox/addon/video-downloadhelper/
這次因為沒有刪除 .cache 的關係, 所以好像相關設定都在
flash-player:
# zypper install flash-player
Telegram desktop:
最後的解法是 使用 Web 的方式來使用 Telegram
軟體 ( Flatpak ) 安裝可以輸入中文 - 但是版本太舊會被 Telegram 說會被停用
snap 版本 / 下載 telegram 的 .xz 解壓縮, 不能輸入中文
在 ~/.local/share/applications 目錄下找出 telegram-desktop.desktop 設定檔, 加入 QT_IM_MODULE=gin 也無效
播放器:
Codecs 的部分參考網路上找到的
# zypper install opi
# opi codecs
這邊會裝 ffmpeg-4 以及一堆套件
之後就可以使用播放器看 .mp4
Skype:
使用網頁版的 Skype 不另外安裝
因為網址都會被轉到 www.pchomeskype.com.tw 太煩了
GNOME Extension:
參考調校小記
主要是裝 chrome 內的 GNOME Shell integration
然後到 https://extensions.gnome.org/
選想裝的 Extension, 調爲 on 就好
裝了
NetSpeed
RunCat
Show External IP
Tray Icons: Reloaded
過期
TopIcons Plus (現在都在右上角, 所以就不需要)
.7z 支援:
# zypper install p7zip
imagewriter:
# zypper install imagewriter
用來製作開機 USB
rdesktop 安裝與測試:
#zypper install freerdp
執行方式
#xfreerdp -g 1280x1024 -u administrator HOST_IP
修改 LS_OPTIONS 變數
# vi /etc/profile.d/ls.bash
把 root 的 LS_OPTIONS 的 -A 移除
修改 HISTSIZE 變數
# vi /etc/profile
修改 HISTSIZE 的筆數
ansible 安裝:
目前版本 2.9.27
#zypper install ansible
變更主機名稱:
#yast2 lan
Dropbox 158.4.4564版 :
openSUSE Leap 15.4 預設不支援 dropbox
參考官方網站上面斷頭的安裝方式來安裝
> cd ~ && wget -O - "https://www.dropbox.com/download?plat=lnx.x86_64" | tar xzf -
接下來,請從新建立的 .dropbox-dist 資料夾執行 Dropbox 精靈。
> ~/.dropbox-dist/dropboxd
順便安裝 Nautilus 相關套件
# zypper install nautilus-extension-dropbox
Filezilla 安裝:
#zypper install filezilla
Brave 安裝:
# rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc
# zypper addrepo --refresh https://brave-browser-rpm-release.s3.brave.com/x86_64/ brave-browser
# zypper install brave-browser
Azure-cli 安裝:
版本: 2.38.0
參考
http://sakananote2.blogspot.com/2018/07/kubernetes-in-azure-with-opensuse-leap.html
https://docs.microsoft.com/zh-tw/cli/azure/install-azure-cli-linux?pivots=zypper
匯入 rpm key
# rpm --import https://packages.microsoft.com/keys/microsoft.asc
新增 Azure CLI 的 repo
# zypper addrepo --name 'Azure CLI' --check https://packages.microsoft.com/yumrepos/azure-cli azure-cli
安裝 azure-cli 套件
# zypper install --from azure-cli -y azure-cli
使用互動的方式登入 azure ( 現在已經不需要輸入機器碼, 直接驗證帳號就可以 )
> az login
AWS Cli 安裝:
版本: 2.8.2
# curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
# unzip awscliv2.zip
# ./aws/install
# aws --version
aws-cli/2.8.2 Python/3.9.11 Linux/5.14.21-150400.22-default exe/x86_64.opensuse-leap.15 prompt/off
將補齊的指令 寫到或是修改到個人家目錄的 .bashrc 內
echo "complete -C '/usr/local/bin/aws_completer' aws" >> /root/.bashrc
Google Cloud SDK ( gcloud )安裝:
參考 http://sakananote2.blogspot.com/2019/04/gsutil-google-cloud-storage-in-opensuse.html
安裝 gcloud
但是目前實務上是使用容器的方式來執行
使用一般使用者安裝
> tar zxvf google-cloud-sdk-405.0.0-linux-x86_64.tar.gz
> ./google-cloud-sdk/install.sh
透過 gcloud 安裝 kubectl
> gcloud components install kubectl
確認版本
> kubectl version --client
Visual Studio Core 相關 :
安裝 git
# zypper install git
參考 http://sakananote2.blogspot.com/2019/01/visual-studio-code-with-opensuse-leap-15.html
安裝 vscode
# rpm --import https://packages.microsoft.com/keys/microsoft.asc
# sh -c ' echo -e "[code]\nname=Visual Studio Code\nbaseurl=https://packages.microsoft.com/yumrepos/vscode\nenabled=1\ntype=rpm-md\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc" > /etc/zypp/repos.d/vscode.repo '
# zypper refresh
# zypper install code
安裝 vscode extension ( 這次沒有作, 因為將舊的 /home 還原回來, 另外目前 vscode 也有同步機制 )
AWS Toolkit for Visual Studio Code
Bracket Pair Colorizer
Code Time
Git Graph
GitHub Pull Requests
GitLens
Kubernetes
Python
REST Client
GitHub Pull Requests and Issues
Podman 安裝:
參考官方網頁
# zypper install podman
看起來目前的階段 docker 與 podman 還是要並存 - 生態系支援與 rootless podman 相關考量
Docker 安裝:
目前版本 20.10.17
#zypper install docker
將使用者 sakana 加入 docker 群組
# usermod -a -G docker sakana
#systemctl start docker
#systemctl enable docker
PPPoE 設定:
目前光世代有配一個固定 IP
參考 http://sakananote2.blogspot.com/2021/05/nmcli-network-manager-pppoe-ip.html
設定 PPPoE 以及固定 IP
這個版本沒有安裝的, 以後要安裝就看之前的筆記
http://sakananote2.blogspot.com/2019/08/opensuse-leap-151.html
Sqlitebrowser
VMware workstation Pro 15
Nextcloud client 安裝, crontab 設定
PDF Viewer - Foxit:
hexchat
youtube-dl
Yubico Key ( 現在 google 已經可以直接手機驗證 )
smartgit 安裝 ( 現在使用 vscode )
PPSSPP ( 沒時間 …. )
這樣又可以再戰一年 :p
~ enjoy it
參考
https://sakananote2.blogspot.com/2021/11/opensuse-leap-153.html
http://sakananote2.blogspot.com/2020/08/opensuse-leap-152.html
http://sakananote2.blogspot.com/2019/08/opensuse-leap-151.html
http://sakananote2.blogspot.com/2019/01/opensuse-leap-15-2.html
http://sakananote2.blogspot.com/2017/11/opensuse-leap-423.html
http://sakananote2.blogspot.tw/2017/07/opensuse-leap-423-beta.html
http://sakananote2.blogspot.tw/2016/11/opensuse-leap-422.html
http://sakananote2.blogspot.tw/2016/12/opensuse-leap422-gnomeextension.html
http://sakananote2.blogspot.com/2018/07/kubernetes-in-azure-with-opensuse-leap.html
http://sakananote2.blogspot.com/2019/01/visual-studio-code-with-opensuse-leap-15.html
http://sakananote2.blogspot.com/2019/03/aws-cli-with-opensuse-leap-15.html
More API Endpoint Documentation for Project and Package Sources
Diffusion Models 3D: IA que cria trabalhos/objetos 3D para o Metaverso e Games.
Ultimamente um assunto muito presente e popular no mundo da tecnologia é os modelo generativos denominado Diffusion Models. Entendemos que os modelo de difusão tem capacidade de superar GANS (Rede Adversárias Generativas), tudo isto devidos algumas publicações entre 2020 e 2021.
O que é o Modelo de Difusão:
Aprendi este termo nos livros de Física 2 nos capítulos de termodinâmica. Um sistema desequilibrado possui uma grande concentração de um determinado material (exemplo vazamento de gás que resulta no cheiro forte localmente). A difusão coloca o sistema em equilíbrio, como por exemplo a moléculas de perfume se difunde a partir de uma região para todo sistema assim causando o equilíbrio. Ou seja, tudo torna-se homogêneo.
Esta é toda origem motivacional dos modelos de difusão, que utilizam uma série de variáveis onde o valor de cada uma depende do estado do evento anterior. A difusão usa rede neural durante o processo, tentando prever o ruído a cada fase assim simplificando a tarefa.
Tomando este conceito como base científica, diversos projetos surgiram que alcançam o desempenho humano em tarefas de criação de imagens. A função desta IA é gerar imagens a partir de descrições de texto e também utiliza aprendizado multimodal para conectar a semântica entre texto e imagens. Além de revolucionário iram mudar a área de design de produtos e conteúdo visual para diversas finalidades. Existem alguns projetos famoso como Dall E, Midjourney e Stable Diffusion.
Stablle difusion é opensource, inclusive tenho instalado na minha máquina. E justamente por ser opensource, já avançou para uma segunda geração. A criação de modelos e artes 3D, o paper podemos encontrar neste link https://arxiv.org/abs/2209.14988
Em … o projeto foi implementado em pytorch de toda teoria. O projeto foi batizado como Stable-Dreamfusion similar ao modelos de difusão para criar imagens e artes mas agora em 3D. Com isto este modelos poderão ser utilizados no metaverso e também jogos. Abaixo um exemplo gerado com este projeto https://github.com/ashawkey/stable-dreamfusion, digitando o texto “Um fantasmas comendo um harmburger” ! Vale a pena ressaltar que o projeto pioneiro foi o GET3D da Nvidia https://github.com/nv-tlabs/GET3D.

Almuerzos Libres de GNU/Linux València edición octubre 2022
Poco a todo vuelve a la normalidad. La pandemia no disminuyó demasiado los eventos pero deberieon adaptarse a una nueva realidad: la virtualización por necesidad. No obstante, algunos deberieon desaparecer dado su carácter intrínsecamente humano que los hacían imposible de replicar detrás de una pantalla. Además, la extrema virtualización ha hecho que los eventos presenciales retornen pero a una velocidad menor de lo esperado. Es por ello que me complace compartr con todos vostros de esta iniciativa, los Almuerzos Libres de GNU/Linux València edición octubre de 2022, cuyo objetivo principal es poner en contacto físico a las personas que día a día trabajan en el desarrollo del Software Libre en cualquiera de sus facetas: programando, promocionando, diseñando, utilizando, etc.
Almuerzos Libres de GNU/Linux València edición octubre 2022
Organizados por GNU/Linux Valencia vuelve una iniciativa que une la tradición valencian de almorzar de forma contundente mientras se comparte Conocimiento Libre y se disfruta de la companía.
Como es habitual en estos casos, me gusta poner la descripción que hacen del evento los organizadores:
Desde GNU/Linux València os invitamos a una nueva quedada de Almuerzos en Libertad el próximo sábado 29 de octubre en el Puig de Santamaria, València.
Los datos de interés son lo siguientes:
Fecha: 29-10-2022
Tema: Libre
Dirección: Plaça del Ajuntament, 2, 46540 de El Puig de Santamaria.
Hora: 10 de la mañana

Si quieres apuntarte al almuerzo contacta con nosotr@s por nuestros canales de comunicación habituales Matrix (https://riot.im/#/room/%23gnulinuxvalencia:matrix.org) o Telegram (https://t.me/gnulinuxvalencia)/etc…) lo antes posible para ayudarnos a organizar mejor.
¡¡¡ANÍMATE!!!
Info completa en: GNU/Linux Valencia
¡Únete a GNU/Linux València!
Aprovecho para recordar que desde un tiempo los chicos de GNU/Linux Valencia ya tienen su menú propio en el blog, con lo que seguir sus eventos en esta humilde bitácora será más fácil que nunca, y así podréis comprobar su alto nivel de actividades que realizan que destacan por su variedad.
Y que además, GNU/Linux València creció y se ha convertió en asociación. Así que si buscas una forma de colaborar con el Software Libre, esta asociación puede ser tu sitio. ¡Te esperamos!
La entrada Almuerzos Libres de GNU/Linux València edición octubre 2022 se publicó primero en KDE Blog.
Do you need a Strong Leader?
“Strong” is often used as a metaphor for capable, competent, effective leadership.
Strength is not always the most helpful metaphor for leadership skills.
Listen to how people describe strong leaders, sometimes there are connotations at odds with effective leadership. Sometimes even hints of toxic masculinity. What does it say about our gender biases that we so often use strength as a metaphor for leadership effectiveness?
If you stopped pouring fuel onto the fires, maybe you would not need heroic firefighters.

What does Strong Imply?
Resilient?
Do you want strong leaders who are tough and resilient, who can withstand the pressures of the role…

…or leaders who facilitate simple mechanisms to help the team handle big challenges

Do you need strong leaders who don’t need help? Is everyone else too busy to help? What’s causing that busy-ness? Is the lack of slack in your system precluding the possibility for collaboration towards better outcomes?

Adding a leader who can handle more is a treatment for a symptom. The underlying disease may be incentives for high utilisation. Are you cramming quarterly plans full? Are you setting OKRs with goals to stretch beyond what you know you can achieve?
Does this road need an extra lane to handle more cars? or a train, or a bicycle? The fix for your overload may need more creative thinking.
Powerful?
Do you need strong leaders who are powerful and can wield that power to achieve great feats? Why is achieving great outcomes so hard in your organisation? What’s getting in the way of folks self-organising towards the most important outcomes? What is disempowering any and every individual on the team from getting things done?

Is it bureaucracy? What would happen if you removed all the rules? What if you gave everyone authority (with accountability) to spend money as they saw fit, and autonomy to choose what to work on?
Is it fear of failures? Tackle the things causing it to be unsafe to fail rather than adding a more reckless leader. Praise people for saying no to things. Celebrate what’s learned from failures as well as successes. Reward humility and vulnerability. Bet on a team where everyone learns from each other’s missteps and comes to trust each other, over a team that avoids traps but never achieves greatness.
Is it perchance that your mighty leaders are not leaving space for others to step up?

Dispassionate?
Do you need leaders who don’t let emotion cloud their judgement? It sounds positive, but everyone has emotions; we are not Vulcans.

Do we not want leaders who are sensitive to the emotional impact of decisions and events on those they have a responsibility to serve? As well as aware of how their own emotions are influencing their judgement.
Feelings exist and we ignore them at our peril. A rational decision is not rational if it leaves the team despondent, fearful, angry, or demotivated.
Decisive?
Do you want leaders who think they know better than their teams? The group is often smarter than any one individual. Do you want to limit your success to the limits of your leader? Why do you have a team if one person knows best?

Do you want leaders who act confident in their own judgement? Or those who are open about their rationale, their intent, as well as the reasons their judgement could be wrong. Articulating intent enables the team to adapt in the face of new information.
Do you want stubborn leaders who need persuading to try something different? People who stick to their guns even in the face of evidence they may be wrong?
What’s making it hard for the groups to make decisions without a decisive leader?
Groups get stuck when there’s a lack of psychological safety: Are folks safe to express their opinions? Leaders who are quick to express their strong opinions undermine safety. A power imbalance adds friction to the voicing of dissenting opinions.
Decisive leaders are not necessary for decisive teams. Groups get stuck when they think they need consensus, unanimity or permission, lacking mechanisms such as
- Group decision making with roman voting, or occupy signals.
- Pre-agreed time/spend budgets for experimentation.
- Healthy habits that remove the need for repeated considered decision making.
Inspirational?
If you need a leader to inspire the team to achieve great things, what’s destroying the team’s intrinsic motivation?
Inspire sounds positive but has coercive undertones.
A charismatic leader who inspires their team to follow them without dissent may be very effective; as long as their chosen destination is actually a good outcome.
The organisation can lose its resilience and adaptability in the face of a leader whom folks blindly follow.


Visible?
Folks often want a visible leader so that people know who to go to if they want to get something done.
Good leadership is often nearly invisible. Tending to the systems. A quiet word of feedback here. Pointing out an opportunity there. Asking the right questions at the right times.
Which of these organisations has a highly visible leader?
Which of these organisations is fragile?


Different?
“We need a strong leader” implies “we need a different leader”.
What is causing the current leadership (whether vested in a single person explicitly or distributed) to be inadequate?
Changing or adding one person with authority can be a quick fix, but isn’t guaranteed to work; especially if you don’t have a diagnosis that explains the need for a new leader. Do you really need a superhero to save you?
What are your best hopes for what a new leader will do? What stops you doing those without them?
Instead
Helping a team overcome its weaknesses requires an appreciation for weakness more than a show of strength. Being the strongest member of a team can even be a disadvantage.
We need leaders who
- model vulnerability, being open about their weaknesses, limitations, and uncertainties.
- build others up rather than hoarding power themselves.
- can adapt and help their team adapt to their context. Diagnosis and strategy over strength and power.
- connect people, more than leaders who translate.
- are curious about the options their team sees, more than they inspire action towards their preconceptions.
- remove impediments to others making decisions more than they make decisions.
- set examples with boundaries, protecting their mental health more than projecting invincibility.
- disperse power instead of wielding power.
- tend to the systems that enable us more than using systems to control us.
Strength? Of a sort: Courage and humility.
Reflecting
What’s behind your desire for a strong leader?
How strong is your organisation if you remove the strong leader?
What mechanisms could make the group’s success inevitable, despite the fallibility of whoever is currently serving as leader?
The post Do you need a Strong Leader? appeared first on Benji's Blog.
¿Conoces Mycroft Mark II? La alternativa libre a Alexa, Siri o Google Assistant
Es cierto que ya he hablado de Mycroft en el blog aunque de la última vez tenemos que retroceder a febrero de 2018, cuando hablé de la posibildad de adquirir su segunda versión. Así que esta entrada pretende ser un recordatorio de este proyecto que cada día que pasa me parece más importante. Así que emulando a Barney Stinson… ¿Conoces Mycroft Mark II?
El proyecto Mycroft y la privacidad
Cada vez es más habitual tener un asistente personal libre que reacciona a tus órdenes controlando luces, música o simplemente dándote el parte meteorológico. Debe ser muy importante para las empresas porque Amazon (el mayor supermercado del mundo), Google (la empresa que domina internet) y Apple (la empresa que mejor vende sus dispositivos) tienen proyectos relacionados con este tipo de gadgets, lo cuales intentan colarnos con campañas de publicidad agresvas y que consiguen que sus oídos se cuelen cada vez más en nuestras casas, contándo nuestros secretos en forma de datos a sus amos.
No obstante hay que reconocer que las funcionalidades de estos dispositivos son atractivas y, en algunas casos, necesarias. Estoy pensando en personas con movilidad reducida o en nuestros mayores que tienen dificultades para interaccionar con dispositivos tecnológicos.
Evidentemente, la Comunidad del Software Libre no ha dado la espalda a este problema y hace unos años se inició el proyecto Mycroft que, en palabras de sus desarrolladores es:
Mycroft es el principal asistente de voz de código abierto del mundo. Es privado por defecto y completamente personalizable.
Nuestro software se ejecuta en muchas plataformas: en el escritorio, en nuestro hardware de referencia, en una Raspberry Pi o en tu propio hardware personalizado.
La pila de voz de código abierto de Mycroft puede ser remezclada libremente, ampliada y desplegada en cualquier lugar. Mycroft puede usarse en cualquier cosa, desde un proyecto científico hasta un entorno empresarial global.

Es evidente que con estos principios Mycroft no va a compartr tus datos con las grandes compañías tecnológicas y su misión es servir a sus usuarios, no minar datos. DE esta forma Mycroft por defecto no almacena consultas u otros datos sensibles.
¿Conoces Mycroft Mark II? La alternativa libre a Alexa, Siri o Google Assistant
De esta forma los chicos y chicas de Mycroft no se quedaron solo creando la inteligencia artificial y ponerla a disposición de cualquiera que quiera utilizarala sino que desarrollaron un primer modelo comercial para aquellos que simplemente comprar y utilizar el dispositivo. Lo bautizaron con el nombre de Mycroft Mark I y lo vendieron… y gracias a su éxito trabajaron en su sucesor llamado Mycroft Mark II y que financiaron con un kickstarter.

La nueva y mejorada versión del asistente tiene las siguentes características:
- Nuevo diseño exterior
- Quad core Cortex-A72 (ARM v8) 64-bit, 1.5GHz
- RAM: 2GB LPDDR4-3200 SDRAM
- Mejoras en la recepción del sonido gracias a la inclusión de 6 micrófonos
- Altavoces mejorados de 10W
- Más interfaces gráficas hasta llegar a tener 140 diseños con la posibilidad de aumentarlas gracias a la Comunidad
- Conexiones exteriores USB tipo A, ranura para MicroSD, Bluetooth y Wifi.
- Pantalla 4.3″ IPS táctil
- Posibilidad de cambiar el nombre al asistente
- Más dispositivos compatibles
Si ha ido todo bien, los primeros afortunados habrán recibido su Mycroft Mark II este pasado mes de septiembre y tú puedes reservar el tuyo que te llegará en enero del año que vien.
Vídeo de Mycroft Mark II
Me reservo para el final del artículo tanto el vídeo de Mycroft Mark II, donde se pueden ver algunas de las funciones de este maravilloso dispositivo.
La entrada ¿Conoces Mycroft Mark II? La alternativa libre a Alexa, Siri o Google Assistant se publicó primero en KDE Blog.
Translations available for KDE unstable packages
As many readers of this blog are aware, openSUSE has been offering packages of git snapshots from KDE since quite a while. They are quite useful for those wiling to test, report bugs, and / or hack on the code, but also for those who want to see what’s brewing in KDE land (without touching their existing systems). However, a major drawback for non English speakers was the lack of translations.
What’s the problem with translations?
KDE translations are not hosted on the community’s git repositories, but are instead stored in KDE’s SVN server. The main reason they were not moved to git was to preserve the existing workflows of the translation teams (who might not be as technical as the actual hackers). Translations are then placed in tarballs at the times of betas / RCs / releases.
This unfortunately means that having a git checkout, like what the OBS does when building the unstable packages, will not carry any translations whatsoever. Worse, existing -lang packages for stable versions will raise dependency problems if present (because they require the exact same version of their corresponding binary paclage).
Also, since the KDE team tries to keep the same set of package defintions (spec files) between the stable and unstable OBS projects, this meant some extra complexity to take into account the fact that translations might or might not be there.
As far as I remember, since some time there was some tooling in KDE infrastructure to download translations at build time, but it was a big no-no for the OBS, as there is no network access during building for security reasons.
Two sides of a solution
This proved to be a problem also for KDE’s own release management. On September 2nd, KDE hacker Albert Astals Cid outlined a proposal to have an automated way to copy translations from SVN into their corresponding repository, with a series of scripts that would do so periodically.
After some discussion and once at Akademy, the switch was turned on October 2nd. This means that our git checkouts were getting translations!
Of course, some adjustments were needed: spec files in the KDE Unstable projects were not taking the presence of translations into account, and thus quite a number of builds were failing. krop, KDE team member extraordinaire, stepped in and fixed all the spec files. This in turn made him realize that some upstream KDE projects were not actually handling translations correctly in their CMake code, so he fixed them too.
Within a couple days, all KDE Unstable repositories (Frameworks, Applications and Extra) had translations enabled, where applicable. After many years, it became possible to test the latest KDE software and have it in your own language.
Do I need to do anything?
If you don’t have the language packages installed and you have installation of recommended packages enabled (the default), they should be installed automatically. If you have, like myself, forcibly installed the language packages from the stable repositories, you can force install the new ones (for example with zypper install -f <packagename>), or if you’re on Tumbleweed, accept to swap them when prompted (this occurs when a new stable version of KDE software is published in a snapshot). Or you can install them manually should you prefer to do so.
Should any issues with the packaging arise (e.g., missing dependencies, conflicts), please file a ticket on bugzilla.opensuse.org.
And as always, have a lot of fun!
Episodio de septiembre de 2022 los podcast de GNU/Linux València
Hoy me complace compartir con todos vosotros el episodio de septiembre de 2022 los podcast de GNU/Linux València, un nuevo capítulo que revive un proyecto que tras la pandemia ha estado un poco parado pero que seguro que volverá a dar mucho que hablar.
Episodio de septiembre de 2022 los podcast de GNU/Linux València

Tras bastante tiempo en silencio, básicamente porque no tienen forma de cuadrar agendas, vuelven los podcast de GNU/Linux València. Unos podcast que suelen ser de tipo tertulia muy amena y destinada a todo el mundo.
De esta forma en este podcast con Alejandro, Alex y Taraak y se va a hablar de la tiranía de los teléfonos, del próximo evento de Emancipación Comunitaria, algo ya conocido por los lectores del blog y de algunas jugosas noticias que os pongo a continuación:
- La charla y taller «Install Party» en Carcaixent (València) organizada por Asociació Emancipació Comunitaria
- El fallo de hace 15 años en Python permite la ejecución de código arbitrario en 350k proyectos
- MD MZ: un libro para el desarrollo práctico de malware, con trucos, técnicas de evasión y persistencia
- Richard Stallman anuncia el manual de referencia del lenguaje C de GNU
- Audacity 3.2 incluye efectos en tiempo real y soporte de ffmpeg 5.0
Y como es habitual en este tipo de entrada, os dejo directamente el audio para que lo disfrutéis.
Más información: GNU/Linux València
¡Únete a GNU/Linux València!
Aprovecho para recordar que desde hace unos meses, los chicos de GNU/Linux Valencia ya tienen su menú propio en el blog, con lo que seguir sus eventos en esta humilde bitácora será más fácil que nunca, y así podréis comprobar su alto nivel de actividades que realizan que destacan por su variedad.
Y que además, GNU/Linux València creció y se ha convertió en asociación. Así que si buscas una forma de colaborar con el Software Libre, esta asociación puede ser tu sitio. ¡Te esperamos!
La entrada Episodio de septiembre de 2022 los podcast de GNU/Linux València se publicó primero en KDE Blog.
QEMU, Vim update in Tumbleweed
Snapshot releases of openSUSE Tumbleweed were plentiful during the month of September with the rolling release delivering 27 snapshots out of 30 days in the month.
Since last Friday, four snapshots have been released.
Several libraries were updated in snapshot 20221003. An update of libva 2.16.0 was among those changed in the snapshot; the Video Acceleration Application Programming Interface for Linux simplified some mapping tables. Another library to update was libcap 2.66. This library made the Makefiles more robust to address an error and the package fixed some documentation typos. The links 2.28 package disabled the cache when following redirects from consent.google.com. An update of yast2-network 4.5.8 fixed an issue when writing the NetworkManager configuration without a gateway. The C library for parsing command line parameters, popt 1.19, fixed multiple resource and memory leaks. It also improved random number handling. There were several other packages to update in the snapshot including libbluray 1.3.3, tdb 1.4.7, python-cryptography 38.0.1 and more.
Text editor vim 9.0.0626 updated in snapshot 20221001 and it fixed a Common Vulnerability and Exposure; CVE-2022-3352. The text editor also fixed the command line window that remained visible when quitting with CTRL-C. An update of qemu 7.1.0 switched QEMU Linux use to emulate the same CPU as the one of the host by default. While controversial and tricky, it should be just fine for Linux users, according to the changelog. The emulator had some fixes for arm and added RISC-V support for privileged spec version 1.12.0. The package also provided optimisations and improvements for the vector extension for RISC-V. The update of php7 7.4.32 was a security release that fixed CVE-2022-31628, which had potential Denial-of-Service issues, and CVE-2022-31629, which had a vulnerability to enable network and same-site attackers to set a standard insecure cookie in the victim’s browser. The super-thin layer on the DBus interface fwupd updated to version 1.7.10. It had several fixes including checking for invalid depth requirements and aligning up addresses greater than 4GB.
A few GNOME packages were updated in snapshot 20220930. Both gnome-logs and the screen-reader speech/braille package orca transitioned from the beta release to version 43. The latter prevents double-presentation of notifications and it fixed the presentation of Nautilus items for GTK4. It also fixed a bug causing the wrong voice to be used. Both gnome-logs and orca updated translations while gnome-logs updated screenshots. GNOME’s spellcheck package gspell 1.12.0 had some small maintenance tasks and simplification changes, and pango 1.50.10, which is a text layout and rendering package, fixed line height computations. A total of three CVEs were fixed in the nodejs18 18.10.0 version, which only CVE-2022-35255 was considered to be greater than a moderate threat. The update of yast2 to version 4.5.15 allows for better detection of yast2-journal. Linux Kernel 5.19.12 had multiple Advanced Linux Sound Architecture for ASUS. Other packages to update in the snapshot were perl-Image-ExifTool 12.45 and xterm 373.
Packages to update in snapshot 20220929 were adwaita-qt-src 1.4.2, libqt5-qttranslations 5.15.6 and v4l2loopback 0.12.7.
Data visualization with Grafana and Telegraf
It all started when…
Few weeks ago we have decided to create a dashboard where we can monitor the status of the SUSE Linux Enterprise maintenance update queue. Naturally there are tons of cool open source solutions to build this type of monitoring. Two decades ago I probably would have written a Perl or Python based monitoring script for the monitoring part and use the good old gnuplot (http://www.gnuplot.info/) to visualize the data and create an active page written in some silly web UI framework. Let’s just say that luckily those times has passed.