MX Linux Forum

Posted: **Tue Dec 05, 2023 7:24 am**

Something I noticed last night:

1) screen blanking is disabled by default in RPi OS and thus here--do we want to leave it there for MX-RPi?

2) If I understand correctly, it can't be enabled with Xfce's Power settings, as one would rightly expect, but only with raspi-config (link on default desktop, also in menu)

3) once blanking has been enabled the blanking occurs at 600 secs. On my system, however, the Display dialog box then pops up a few seconds later and the blanking is broken for another 600 secs. I suspect that is just due to my very cheap monitor but would like to know if others see the same behavior.

Posted: **Tue Dec 05, 2023 11:02 am**

1) As we are including raspi-config, I think we should leave it disabled.

2)

3) Working here without the Display dialogue appearing.

As an aside, on my test bench I have an EIZO monitor that connects to several machines, and a fly-lead, via an HDMI switcher. I used to get that Display dialogue pop-up all the time, and blamed the HDMI switcher, but replacing it didn't fix the problem. I then tried a different cable from the monitor to the switcher, and it fixed the problem. I would guess that not all HDMI cables carry all of the lines needed. I would suggest you try a good quality cable to see if that fixes it for you.

Chris

Posted: **Tue Dec 05, 2023 12:01 pm**

I'll check the cable, thanks.

Posted: **Tue Dec 05, 2023 5:22 pm**

Just upgraded, and the new Firefox (120...) replaced Firefox-esr. That happens to be fine with me, since I was about to remove it b/c it's so damned slow, but I doubt it's what we want.

Posted: **Tue Dec 05, 2023 8:04 pm**

firefox-esr is not installed by default. been using firefox for a while now.

Posted: **Tue Dec 05, 2023 8:17 pm**

Huh. Didn't know that. False alarm, then.

Posted: **Wed Dec 06, 2023 2:13 pm**

I've tested browser startup times on a Pi 5 (That I wasn't going to buy as I couldn't justify it...)

In each case, I opened the browser, set the home page to Google, then closed the browser. I timed from clicking the icon until the Google page was fully rendered; there will be minor variations due to connection speed.

Using the latest release of the official OS. Firefox took 6.5 secs to start, and Chromium 3 secs.

With MX, Firefox took 7 secs, Chromium 2 secs. Turning hardware acceleration off in Firefox reduced startup time by 1 sec.

For comparison, with a Pi 4 and MX as OS, Firefox takes 14 secs, and Chromium 5 secs.

The time for Firefox on a Pi 4 is pretty poor; it would frustrate me, and probably attract criticism from others. Much as I dislike it, perhaps we should consider Chromium as default?

Chris

Posted: **Wed Dec 06, 2023 2:21 pm**

I would be in favor of that, but I think @dolphin_oracle has some reservations.

Posted: **Wed Dec 06, 2023 2:32 pm**

because of the browser link on the panel, I would need to create and maintain a separate Xfce desktop defaults package, set to conflict with the existing destkop-defaults-xfce-mx-desktop package. there are two files that would need to be different to accommodate a change in default browser.

I would also need instructed on how to add our links to a default chromium setup, keeping in mind there is no default browser profiles included, and there won't be.

anyway, if folks want to change, we can make it happen.

Posted: **Wed Dec 06, 2023 3:01 pm**

Hi:
In the usual MX installation I usually change the installation language to Spanish, but in the raspi it doesn't let me do the installation in English, if I try to add a new language I get this error:

fallo-idioma-mxpi.jpg

Best regards

Posted: **Wed Dec 06, 2023 3:02 pm**

Senpai wrote: ↑Wed Dec 06, 2023 3:01 pm Hi:
In the usual MX installation I usually change the installation language to Spanish, but in the raspi it doesn't let me do the installation in English, if I try to add a new language I get this error:

fallo-idioma-mxpi.jpg

Best regards

thanks I will look into it. might be in the app itself, not really the pi.

Posted: **Wed Dec 06, 2023 3:45 pm**

dolphin_oracle wrote: ↑Wed Dec 06, 2023 2:32 pm because of the browser link on the panel, I would need to create and maintain a separate Xfce desktop defaults package, set to conflict with the existing destkop-defaults-xfce-mx-desktop package. there are two files that would need to be different to accommodate a change in default browser.

I would also need instructed on how to add our links to a default chromium setup, keeping in mind there is no default browser profiles included, and there won't be.

anyway, if folks want to change, we can make it happen.

Sounds pretty complicated, so I guess we should stay with FF. Some considerations:
1) raspi-config has an entry for browser choice and, IIRC, RPi OS comes with both installed; I made the switch thinking that it might see that the other browser wasn't installed and install iit, but no
2) the RPi people specify chromium-browser: is that the same as what we have in MXPI?
3) I tried to install libwidevinecmd0 after installing the MXPI Chromium but it can't be found. When I tested earlier (I think I was using chromium-browser) it was available so I wrote the RPI Tips to include it. I'll test again.

Posted: **Wed Dec 06, 2023 3:54 pm**

Jerry3904 wrote: ↑Wed Dec 06, 2023 3:45 pm
dolphin_oracle wrote: ↑Wed Dec 06, 2023 2:32 pm because of the browser link on the panel, I would need to create and maintain a separate Xfce desktop defaults package, set to conflict with the existing destkop-defaults-xfce-mx-desktop package. there are two files that would need to be different to accommodate a change in default browser.

I would also need instructed on how to add our links to a default chromium setup, keeping in mind there is no default browser profiles included, and there won't be.

anyway, if folks want to change, we can make it happen.
Sounds pretty complicated, so I guess we should stay with FF. Some considerations:
1) raspi-config has an entry for browser choice and, IIRC, RPi OS comes with both installed; I made the switch thinking that it might see that the other browser wasn't installed and install iit, but no
2) the RPi people specify chromium-browser: is that the same as what we have in MXPI?
3) I tried to install libwidevinecmd0 after installing the MXPI Chromium but it can't be found. When I tested earlier (I think I was using chromium-browser) it was available so I wrote the RPI Tips to include it. I'll test again.

the chromium pi entry currently installs

Code: Select all

chromium
chromium-l10n
chromium-sandbox

I don't know if that will get you debian's or rpiOS's version. However, we can change the chromium entry on an architecture basis, so just let me know what the mxpi entry should install...

maintaining another package isn't my first choice, but if firefox is unlivable might be unavoidable.

Posted: **Wed Dec 06, 2023 4:01 pm**

dolphin_oracle wrote: ↑Wed Dec 06, 2023 3:54 pm if firefox is unlivable might be unavoidable.

It would be irritating for a Pi 4 user, but if they have used FF with another Pi OS they would at least expect it. Performance once Firefox has started is OK, so perhaps best to leave it as default.

Chris

Posted: **Wed Dec 06, 2023 4:17 pm**

Agreed.

Posted: **Wed Dec 06, 2023 8:19 pm**

I dont suppose librewolf available as an alternative browser ?

Posted: **Thu Dec 07, 2023 5:23 am**

mortlocli wrote: ↑Wed Dec 06, 2023 8:19 pm I dont suppose librewolf available as an alternative browser ?

LibreWolf is available from the Package Installer as a Flatpak.

The first time you select that tab, you will be prompted to install flatpak. Once that has completed you can use the search box to find and install LibreWolf. It won't show in the menu until you reboot.

As it's Firefox based, LibreWolf will be slow to start, especially on a Pi 4. Once started, performance seems OK.

HTH

Chris

Posted: **Thu Dec 07, 2023 8:21 am**

I installed chromium-browser and purged firefox, and after the first couple of launches it is clearly much faster. Have it set to a dark theme with a simple DDG search page for startup and new tabs. I will be staying with it for my own system.

Posted: **Thu Dec 07, 2023 12:14 pm**

Thank you, Chris..I have not yet looked at ''flatpacs' ..but did notice them. Shall do some more reading and use that as an exercise to find out how they work.

Posted: **Thu Dec 07, 2023 4:31 pm**

Back to the browser question, I have a proposal for consideration:

--install the RPi Chromium straight from the repo as default
--add no bookmarks (I believe RPi does not either--will check), pretty confident that the user will find what s/he needs; it's different from our standard scenario because there is no Live session and everything is essentially in front of the user's eyes. Maybe reconsider a desktop "Help" folder with FAQ, Manual, RPi-Tips and Forum link?
--say in the Final announcement something like this:

Unlike our other MX-Linux versions, MX-23 RPi Respin supplies Chromium as default browser because of its significantly better performance during development testing. Users preferring Firefox can easily obtain it [will they get the RPi version?] with MX Package Installer.

I'm thinking that would remove the extra work DO has described and provide a solid rationale as well for the choice.

Posted: **Thu Dec 07, 2023 5:24 pm**

Jerry3904 wrote: ↑Thu Dec 07, 2023 4:31 pm Back to the browser question, I have a proposal for consideration:

--install the RPi Chromium straight from the repo as default
--add no bookmarks (I believe RPi does not either--will check), pretty confident that the user will find what s/he needs; it's different from our standard scenario because there is no Live session and everything is essentially in front of the user's eyes. Maybe reconsider a desktop "Help" folder with FAQ, Manual, RPi-Tips and Forum link?
--say in the Final announcement something like this:
Unlike our other MX-Linux versions, MX-23 RPi Respin supplies Chromium as default browser because of its significantly better performance during development testing. Users preferring Firefox can easily obtain it [will they get the RPi version?] with MX Package Installer.
I'm thinking that would remove the extra work DO has described and provide a solid rationale as well for the choice.

That seems a perfectly reasonable solution.

Chris

Posted: **Thu Dec 07, 2023 6:20 pm**

I'll put together a modified defaults package so that the firefox link on the panel is a chromium link. that way user's won't get a broken link on the panel. and adjust the default mimetypes to point toward chromium rather than firefox.

I would prefer not to have a folder on the desktop. desktop files offer translations if available automatically. desktop folders do not, unless we script a name change per locale.

Posted: **Thu Dec 07, 2023 6:22 pm**

actually mimetypes don't need adjusted.

Posted: **Thu Dec 07, 2023 6:23 pm**

OK, great!

I was finally convinced this morning when Chr just zipped along and it was a pleasure to use. I have read that it handles hardware acceleration better as well (with YT, for example).

Posted: **Thu Dec 07, 2023 6:39 pm**

After installing the chromium browser via mxpi popular apps, I'm seeing a keyring prompt... I canceled the prompt twice, then the browser launched. Now every time I launch chromium I see this prompt.

The falkon browser performance is good, unfortunately its adblocker fails to handle youtube ads very well. Perhaps its adblock just needs a different blocklist?
--

I noticed the lightdm gkt+ greeter settings isn't present in the whisker menu, it doesn't appear to be installed. After installing it via mxpi enabled repos it appears in the menu and runs fine... the 'text keyboard' option on the greeter taskbar doesn't seem to launch anything though.
--

I installed apparmor via mxpi popular apps; aa-status shows the module loads, but the filesystem isn't mounted. lsm=apparmor needs to be added to /boot/cmdline.txt in order for it to mount.

Posted: **Thu Dec 07, 2023 6:46 pm**

fukamushi wrote: ↑Thu Dec 07, 2023 6:39 pm After installing the chromium browser via mxpi popular apps, I'm seeing a keyring prompt... I canceled the prompt twice, then the browser launched. Now every time I launch chromium I see this prompt.

that one is not the rpiOS built one. try chromium-browser package instead, although its lagging behind in version a bit.

Posted: **Thu Dec 07, 2023 6:55 pm**

fukamushi wrote: ↑Thu Dec 07, 2023 6:39 pm <snip>
I noticed the lightdm gkt+ greeter settings isn't present in the whisker menu, it doesn't appear to be installed. After installing it via mxpi enabled repos it appears in the menu and runs fine... the 'text keyboard' option on the greeter taskbar doesn't seem to launch anything though.

Thanks for the report, helps a lot to have people pushing on this B1!

Posted: **Thu Dec 07, 2023 7:42 pm**

the chrome keyring prompt will happen if you have autologin enabled.

Posted: **Thu Dec 07, 2023 7:54 pm**

Yes. Vivaldi (based on Chrome) now does that.

Posted: **Thu Dec 07, 2023 8:18 pm**

Senpai wrote: ↑Wed Dec 06, 2023 3:01 pm Hi:
In the usual MX installation I usually change the installation language to Spanish, but in the raspi it doesn't let me do the installation in English, if I try to add a new language I get this error:

fallo-idioma-mxpi.jpg

Best regards

I can reproduce this on a standard x86 release, so nice catch. definitely needs fixed!

Posted: **Fri Dec 08, 2023 7:46 am**

Senpai wrote: ↑Wed Dec 06, 2023 3:01 pm Hi:
In the usual MX installation I usually change the installation language to Spanish, but in the raspi it doesn't let me do the installation in English, if I try to add a new language I get this error:

fallo-idioma-mxpi.jpg

Best regards

found the problem, should be fixed now in update.

Posted: **Fri Dec 08, 2023 8:01 am**

@Jerry3904 @chrispop99 so go with chromium even with this keyring thing?

Posted: **Fri Dec 08, 2023 8:05 am**

dolphin_oracle wrote: ↑Fri Dec 08, 2023 8:01 am @Jerry3904 @chrispop99 so go with chromium even with this keyring thing?

I think we have to, especially if we are going to say the release is OK for Pi 4 users. 14 seconds to wait for a web browser to open would be frustrating; Chromium only takes 5.

Chris

Posted: **Fri Dec 08, 2023 8:12 am**

Yes, though super annoying. I'm surprised that PAM doesn't have a fix for this

Posted: **Fri Dec 08, 2023 8:15 am**

Jerry3904 wrote: ↑Fri Dec 08, 2023 8:12 am Yes, though super annoying. I'm surprised that PAM doesn't have a fix for this

the trouble is that with autologin, the user never actually authenticates. if you don't autologin, no problem.

I'm going to be sending the updated desktop-defaults packages. alpha and beta users won't get the new package automatically, which is desktop-defaults-xfce-mx-desktop-rpi, but you will see updates to the existing metapackages, which won't actually do anything except bump version numbers, as they are identical to the ones we have currently. no need to remove the existing desktop-defaults-xfce-mx-desktop package, the new package will replace it and removal will be automatic. just wait for the metapackage desktop-defaultx-xfce-mx updates to show up and apply all updates before trying to install the new package.

and keep in mind that package only sets up defaults for new users. existing home folders are not touched.

Posted: **Fri Dec 08, 2023 8:26 am**

I wonder how RPi gets around this, pretty sure I've never had to authenticate after autologin. Will check again

Posted: **Fri Dec 08, 2023 4:37 pm**

After testing I've decided to use raspi-config and cancel autologin.

ADD: maybe we should think about making that the default?

Posted: **Fri Dec 08, 2023 9:30 pm**

Jerry3904 wrote: ↑Fri Dec 08, 2023 4:37 pm After testing I've decided to use raspi-config and cancel autologin.

ADD: maybe we should think about making that the default?

no autologin should be the defualt. you have to enable autologin in the user setup when you first launch the fresh image. I'll double check that.

you could also use mx-user for the same function.

Posted: **Fri Dec 08, 2023 9:36 pm**

Posted: **Sat Dec 09, 2023 5:35 am**

You're right, of course. I must have ticked autologin in the Installer--and forgot that when thinking of the Chromium problem.

Pi 5 tests last night
Installed Thunderbird and set up my mxlinux.org account. All good.
Watched some music videos where the combination of the Pi 5's power, the neat little BT speaker Oontz Angle 3 and Chromium's setup made it very enjoyable.

Posted: **Sat Dec 09, 2023 6:08 am**

About that Chromium autologin problem: I wonder if this piece, though not completely the same, might have useful info:

https://dev.to/rahedmir/how-to-fix-goog ... linux-1dl0

LATER Unless I have missed something, I think we should look at this closely. There will be questions about avoiding overwriting with upgrades and possible security implications, I suppose. I followed the suggestion to add

Code: Select all

--password-store=basic

after every "exec", changed back to autologin and rebooted. First time, Chromium appeared to hang, then I did it again and it opened without asking for authorization. Chromium was treating it as a new user, I believe, since my Forum login info was not preserved. The revised /usr/share/applications/chromium-browser.desktop file:

Code: Select all

[Desktop Entry]
Version=1.0
Name=Chromium Web Browser
Name[ast]=Restolador web Chromium
Name[bg]=Уеб четец Chromium
Name[bn]=ক্রোমিয়াম ওয়েব ব্রাউজার
Name[bs]=Chromium web preglednik
Name[ca]=Navegador web Chromium
Name[ca@valencia]=Navegador web Chromium
Name[da]=Chromium netbrowser
Name[de]=Chromium-Webbrowser
Name[en_AU]=Chromium Web Browser
Name[eo]=Kromiumo retfoliumilo
Name[es]=Navegador web Chromium
Name[et]=Chromiumi veebibrauser
Name[eu]=Chromium web-nabigatzailea
Name[fi]=Chromium-selain
Name[fr]=Navigateur Web Chromium
Name[gl]=Navegador web Chromium
Name[he]=דפדפן האינטרנט כרומיום
Name[hr]=Chromium web preglednik
Name[hu]=Chromium webböngésző
Name[hy]=Chromium ոստայն զննարկիչ
Name[ia]=Navigator del web Chromium
Name[id]=Peramban Web Chromium
Name[it]=Browser web Chromium
Name[ja]=Chromium ウェブ・ブラウザ
Name[ka]=ვებ ბრაუზერი Chromium
Name[ko]=Chromium 웹 브라우저
Name[kw]=Peurel wias Chromium
Name[ms]=Pelayar Web Chromium
Name[nb]=Chromium nettleser
Name[nl]=Chromium webbrowser
Name[pt_BR]=Navegador de Internet Chromium
Name[ro]=Navigator Internet Chromium
Name[ru]=Веб-браузер Chromium
Name[sl]=Chromium spletni brskalnik
Name[sv]=Webbläsaren Chromium
Name[ug]=Chromium توركۆرگۈ
Name[vi]=Trình duyệt Web Chromium
Name[zh_CN]=Chromium 网页浏览器
Name[zh_HK]=Chromium 網頁瀏覽器
Name[zh_TW]=Chromium 網頁瀏覽器
GenericName=Web Browser
GenericName[ar]=متصفح الشبكة
GenericName[ast]=Restolador web
GenericName[bg]=Уеб браузър
GenericName[bn]=ওয়েব ব্রাউজার
GenericName[bs]=Web preglednik
GenericName[ca]=Navegador web
GenericName[ca@valencia]=Navegador web
GenericName[cs]=WWW prohlížeč
GenericName[da]=Browser
GenericName[de]=Web-Browser
GenericName[el]=Περιηγητής ιστού
GenericName[en_AU]=Web Browser
GenericName[en_GB]=Web Browser
GenericName[eo]=Retfoliumilo
GenericName[es]=Navegador web
GenericName[et]=Veebibrauser
GenericName[eu]=Web-nabigatzailea
GenericName[fi]=WWW-selain
GenericName[fil]=Web Browser
GenericName[fr]=Navigateur Web
GenericName[gl]=Navegador web
GenericName[gu]=વેબ બ્રાઉઝર
GenericName[he]=דפדפן אינטרנט
GenericName[hi]=वेब ब्राउज़र
GenericName[hr]=Web preglednik
GenericName[hu]=Webböngésző
GenericName[hy]=Ոստայն զննարկիչ
GenericName[ia]=Navigator del Web
GenericName[id]=Peramban Web
GenericName[it]=Browser web
GenericName[ja]=ウェブ・ブラウザ
GenericName[ka]=ვებ ბრაუზერი
GenericName[kn]=ಜಾಲ ವೀಕ್ಷಕ
GenericName[ko]=웹 브라우저
GenericName[kw]=Peurel wias
GenericName[lt]=Žiniatinklio naršyklė
GenericName[lv]=Tīmekļa pārlūks
GenericName[ml]=വെബ് ബ്രൌസര്‍
GenericName[mr]=वेब ब्राऊजर
GenericName[ms]=Pelayar Web
GenericName[nb]=Nettleser
GenericName[nl]=Webbrowser
GenericName[or]=ଓ୍ବେବ ବ୍ରାଉଜର
GenericName[pl]=Przeglądarka WWW
GenericName[pt]=Navegador Web
GenericName[pt_BR]=Navegador web
GenericName[ro]=Navigator de Internet
GenericName[ru]=Веб-браузер
GenericName[sk]=WWW prehliadač
GenericName[sl]=Spletni brskalnik
GenericName[sr]=Интернет прегледник
GenericName[sv]=Webbläsare
GenericName[ta]=இணைய உலாவி
GenericName[te]=మహాతల అన్వేషి
GenericName[th]=เว็บเบราว์เซอร์
GenericName[tr]=Web Tarayıcı
GenericName[ug]=توركۆرگۈ
GenericName[uk]=Навігатор Тенет
GenericName[vi]=Bộ duyệt Web
GenericName[zh_CN]=网页浏览器
GenericName[zh_HK]=網頁瀏覽器
GenericName[zh_TW]=網頁瀏覽器
Comment=Access the Internet
Comment[ar]=الدخول إلى الإنترنت
Comment[ast]=Accesu a Internet
Comment[bg]=Достъп до интернет
Comment[bn]=ইন্টারনেটে প্রবেশ করুন
Comment[bs]=Pristup internetu
Comment[ca]=Accediu a Internet
Comment[ca@valencia]=Accediu a Internet
Comment[cs]=Přístup k internetu
Comment[da]=Få adgang til internettet
Comment[de]=Internetzugriff
Comment[el]=Πρόσβαση στο Διαδίκτυο
Comment[en_AU]=Access the Internet
Comment[en_GB]=Access the Internet
Comment[eo]=Akiri interreton
Comment[es]=Acceda a Internet
Comment[et]=Pääs Internetti
Comment[eu]=Sartu Internetera
Comment[fi]=Käytä internetiä
Comment[fil]=I-access ang Internet
Comment[fr]=Accéder à Internet
Comment[gl]=Acceda a Internet
Comment[gu]=ઇંટરનેટ ઍક્સેસ કરો
Comment[he]=גישה לאינטרנט
Comment[hi]=इंटरनेट तक पहुंच स्थापित करें
Comment[hr]=Pristupite Internetu
Comment[hu]=Az internet elérése
Comment[hy]=Մուտք համացանց
Comment[ia]=Accede a le Interrete
Comment[id]=Akses Internet
Comment[it]=Accesso a Internet
Comment[ja]=インターネットにアクセス
Comment[ka]=ინტერნეტში შესვლა
Comment[kn]=ಇಂಟರ್ನೆಟ್ ಅನ್ನು ಪ್ರವೇಶಿಸಿ
Comment[ko]=인터넷에 연결합니다
Comment[kw]=Hedhes an Kesrosweyth
Comment[lt]=Interneto prieiga
Comment[lv]=Piekļūt internetam
Comment[ml]=ഇന്റര്‍‌നെറ്റ് ആക്‌സസ് ചെയ്യുക
Comment[mr]=इंटरनेटमध्ये प्रवेश करा
Comment[ms]=Mengakses Internet
Comment[nb]=Bruk internett
Comment[nl]=Verbinding maken met internet
Comment[or]=ଇଣ୍ଟର୍ନେଟ୍ ପ୍ରବେଶ କରନ୍ତୁ
Comment[pl]=Skorzystaj z internetu
Comment[pt]=Aceder à Internet
Comment[pt_BR]=Acessar a internet
Comment[ro]=Accesați Internetul
Comment[ru]=Доступ в Интернет
Comment[sk]=Prístup do siete Internet
Comment[sl]=Dostop do interneta
Comment[sr]=Приступите Интернету
Comment[sv]=Surfa på Internet
Comment[ta]=இணையத்தை அணுகுதல்
Comment[te]=ఇంటర్నెట్‌ను ఆక్సెస్ చెయ్యండి
Comment[th]=เข้าถึงอินเทอร์เน็ต
Comment[tr]=İnternet'e erişin
Comment[ug]=ئىنتېرنېت زىيارىتى
Comment[uk]=Доступ до Інтернету
Comment[vi]=Truy cập Internet
Comment[zh_CN]=访问互联网
Comment[zh_HK]=連線到網際網路
Comment[zh_TW]=連線到網際網路
Exec=chromium-browser --password-store=basic %U
Terminal=false
X-MultipleArgs=false
Type=Application
Icon=chromium-browser
Categories=Network;WebBrowser;
MimeType=text/html;text/xml;application/xhtml_xml;x-scheme-handler/http;x-scheme-handler/https;
StartupNotify=true
Actions=NewWindow;Incognito;TempProfile;
X-AppInstall-Package=chromium-browser

[Desktop Action NewWindow]
Name=Open a New Window
Name[ast]=Abrir una Ventana Nueva
Name[bg]=Отваряне на Нов прозорец
Name[bn]=একটি নতুন উইন্ডো খুলুন
Name[bs]=Otvori novi prozor
Name[ca]=Obre una finestra nova
Name[ca@valencia]=Obri una finestra nova
Name[da]=Åbn et nyt vindue
Name[de]=Ein neues Fenster öffnen
Name[en_AU]=Open a New Window
Name[eo]=Malfermi novan fenestron
Name[es]=Abrir una ventana nueva
Name[et]=Ava uus aken
Name[eu]=Ireki leiho berria
Name[fi]=Avaa uusi ikkuna
Name[fr]=Ouvrir une nouvelle fenêtre
Name[gl]=Abrir unha nova xanela
Name[he]=פתיחת חלון חדש
Name[hy]=Բացել նոր պատուհան
Name[ia]=Aperi un nove fenestra
Name[it]=Apri una nuova finestra
Name[ja]=新しいウィンドウを開く
Name[ka]=ახალი ფანჯრის გახსნა
Name[kw]=Egery fenester noweth
Name[ms]=Buka Tetingkap Baru
Name[nb]=Åpne et nytt vindu
Name[nl]=Nieuw venster openen
Name[pt_BR]=Abre uma nova janela
Name[ro]=Deschide o fereastră nouă
Name[ru]=Открыть новое окно
Name[sl]=Odpri novo okno
Name[sv]=Öppna ett nytt fönster
Name[ug]=يېڭى كۆزنەك ئاچ
Name[uk]=Відкрити нове вікно
Name[vi]=Mở cửa sổ mới
Name[zh_CN]=打开新窗口
Name[zh_TW]=開啟新視窗
Exec=chromium-browser--password-store=basic

[Desktop Action Incognito]
Name=Open a New Window in incognito mode
Name[ast]=Abrir una ventana nueva en mou incógnitu
Name[bg]=Отваряне на нов прозорец в режим \"инкогнито\"
Name[bn]=একটি নতুন উইন্ডো খুলুন ইনকোগনিটো অবস্থায়
Name[bs]=Otvori novi prozor u privatnom modu
Name[ca]=Obre una finestra nova en mode d'incògnit
Name[ca@valencia]=Obri una finestra nova en mode d'incògnit
Name[de]=Ein neues Fenster im Inkognito-Modus öffnen
Name[en_AU]=Open a New Window in incognito mode
Name[eo]=Malfermi novan fenestron nekoniĝeble
Name[es]=Abrir una ventana nueva en modo incógnito
Name[et]=Ava uus aken tundmatus olekus
Name[eu]=Ireki leiho berria isileko moduan
Name[fi]=Avaa uusi ikkuna incognito-tilassa
Name[fr]=Ouvrir une nouvelle fenêtre en mode navigation privée
Name[gl]=Abrir unha nova xanela en modo de incógnito
Name[he]=פתיחת חלון חדש במצב גלישה בסתר
Name[hy]=Բացել նոր պատուհան ծպտյալ աշխատակերպում
Name[ia]=Aperi un nove fenestra in modo incognite
Name[it]=Apri una nuova finestra in modalità incognito
Name[ja]=新しいシークレット ウィンドウを開く
Name[ka]=ახალი ფანჯრის ინკოგნიტოდ გახსნა
Name[kw]=Egry fenester noweth en modh privedh
Name[ms]=Buka Tetingkap Baru dalam mod menyamar
Name[nl]=Nieuw venster openen in incognito-modus
Name[pt_BR]=Abrir uma nova janela em modo anônimo
Name[ro]=Deschide o fereastră nouă în mod incognito
Name[ru]=Открыть новое окно в режиме инкогнито
Name[sl]=Odpri novo okno v načinu brez beleženja
Name[sv]=Öppna ett nytt inkognitofönster
Name[ug]=يوشۇرۇن ھالەتتە يېڭى كۆزنەك ئاچ
Name[uk]=Відкрити нове вікно у приватному режимі
Name[vi]=Mở cửa sổ mới trong chế độ ẩn danh
Name[zh_CN]=以隐身模式打开新窗口
Name[zh_TW]=以匿名模式開啟新視窗
Exec=chromium-browser --incognito --password-store=basic

[Desktop Action TempProfile]
Name=Open a New Window with a temporary profile
Name[ast]=Abrir una ventana nueva con perfil temporal
Name[bg]=Отваряне на Нов прозорец с временен профил
Name[bn]=সাময়িক প্রোফাইল সহ একটি নতুন উইন্ডো খুলুন
Name[bs]=Otvori novi prozor pomoću privremenog profila
Name[ca]=Obre una finestra nova amb un perfil temporal
Name[ca@valencia]=Obri una finestra nova amb un perfil temporal
Name[de]=Ein neues Fenster mit einem temporären Profil öffnen
Name[en_AU]=Open a New Window with a temporary profile
Name[eo]=Malfermi novan fenestron portempe
Name[es]=Abrir una ventana nueva con perfil temporal
Name[et]=Ava uus aken ajutise profiiliga
Name[eu]=Ireki leiho berria behin-behineko profil batekin
Name[fi]=Avaa uusi ikkuna käyttäen väliaikaista profiilia
Name[fr]=Ouvrir une nouvelle fenêtre avec un profil temporaire
Name[gl]=Abrir unha nova xanela con perfil temporal
Name[he]=פתיחת חלון חדש עם פרופיל זמני
Name[hy]=Բացել նոր պատուհան ժամանակավոր հատկագրով
Name[ia]=Aperi un nove fenestra con un profilo provisori
Name[it]=Apri una nuova finestra con un profilo temporaneo
Name[ja]=一時プロファイルで新しいウィンドウを開く
Name[ka]=ახალი ფანჯრის გახსნა დროებით პროფილში
Name[kw]=Egery fenester noweth gen profil dres prys
Name[ms]=Buka Tetingkap Baru dengan profil sementara
Name[nb]=Åpne et nytt vindu med en midlertidig profil
Name[nl]=Nieuw venster openen met een tijdelijk profiel
Name[pt_BR]=Abrir uma nova janela com um perfil temporário
Name[ro]=Deschide o fereastră nouă cu un profil temporar
Name[ru]=Открыть новое окно с временным профилем
Name[sl]=Odpri novo okno z začasnim profilom
Name[sv]=Öppna ett nytt fönster med temporär profil
Name[ug]=ۋاقىتلىق سەپلىمە ھۆججەت بىلەن يېڭى كۆزنەك ئاچ
Name[vi]=Mở cửa sổ mới với hồ sơ tạm
Name[zh_CN]=以临时配置文件打开新窗口
Name[zh_TW]=以暫時性個人身分開啟新視窗
Exec=chromium-browser --temp-profile --password-store=basic

EDIT: I just got a set of 24 upgrades with some PARM files so maybe DO has already taken care of all this...

Posted: **Sat Dec 09, 2023 10:03 am**

Hi:
When installing Kodi on a raspi4, it does not run, it seems that it is because it asks for pulseaudio and by default this Pipewire, the screen stays black and the raspi hung, I have to turn off from the button.
Any way to put pulseaudio? to test if it runs?
I have tried again after this last update with the same result.
The case is that in the "Alpha" version Kodi worked.

Best regards

Code: Select all

System:
  Kernel: 6.1.0-rpi7-rpi-v8 arch: aarch64 bits: 64 compiler: gcc v: 12.2.0
    parameters: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0
    snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0
    smsc95xx.macaddr=E4:5F:01:A7:63:8E vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000
    console=ttyS0,115200 console=tty1 root=PARTUUID=4f3d088a-02 rootfstype=ext4 fsck.repair=yes
    rootwait
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_rpi_beta1_arm64 Libretto Dec 3  2023 base: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: ARM System: Raspberry Pi 4 Model B Rev 1.5 details: N/A rev: d03115 serial: <filter>
CPU:
  Info: model: N/A variant: cortex-a72 bits: 64 type: MCP arch: ARMv8 family: 8 model-id: 0
    stepping: 3
  Topology: cpus: 1x cores: 4 smt: N/A cache: L1: 320 KiB desc: d-4x32 KiB; i-4x48 KiB
    L2: 1024 KiB desc: 1x1024 KiB
  Speed (MHz): avg: 1800 min/max: 600/1800 scaling: driver: cpufreq-dt governor: ondemand cores:
    1: 1800 2: 1800 3: 1800 4: 1800 bogomips: 432
  Features: Use -f option to see features
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: __user pointer sanitization
  Type: spectre_v2 status: Vulnerable
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef00700 class-ID: hdmi
  Device-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef05700
    class-ID: hdmi
  Device-3: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:gpu class-ID: gpu
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev dri: vc4
    gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary model: LG (GoldStar) FULL HD built: 2016
    res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2 size: 480x270mm (18.9x10.63") diag: 551mm (21.7")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: primary model: MT5531 serial: <filter> built: 2017
    res: 1920x1080 hz: 60 dpi: 305 gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 662mm (26.1")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 3.1 Mesa 23.2.1-1~bpo12+rpt2 renderer: V3D 4.2 direct-render: Yes
Audio:
  Device-1: bcm2711-hdmi0 driver: vc4_hdmi bus-ID: N/A chip-ID: brcm:fef00700 class-ID: hdmi
  Device-2: bcm2711-hdmi1 driver: vc4_hdmi bus-ID: N/A chip-ID: brcm:fef05700 class-ID: hdmi
  API: ALSA v: k6.1.0-rpi7-rpi-v8 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: bcm2835-mmc driver: mmc_bcm2835 v: N/A port: N/A bus-ID: N/A chip-ID: brcm:fe300000
    class-ID: mmcnr
  IF: wlan0 state: up mac: <filter>
  Device-2: bcm2711-genet-v5 driver: bcmgenet v: N/A port: N/A bus-ID: N/A chip-ID: brcm:fd580000
    class-ID: ethernet
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: pl011 driver: uart_pl011 bus-ID: N/A chip-ID: arm:fe201000 class-ID: serial
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.0
    sub-v: 6119 hci-v: 5.0 rev: 17e
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
  Device-2: pl011 driver: N/A bus-ID: N/A chip-ID: arm:serial0 class-ID: serial
Drives:
  Local Storage: total: 29.82 GiB used: 6.4 GiB (21.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: Cruzer Edge size: 29.82 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.26 scheme: MBR
Partition:
  ID-1: / raw-size: 29.32 GiB size: 28.76 GiB (98.11%) used: 6.32 GiB (22.0%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 100 MiB used: 0 KiB (0.0%) priority: -2 file: /var/swap
Sensors:
  System Temperatures: cpu: 48.7 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 1793 libs: 986 tools: apt,apt-get,aptitude,nala,synaptic
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://deb.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb [arch=arm64] http://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/raspi.list
    1: deb http://archive.raspberrypi.com/debian/ bookworm main
Info:
  Processes: 214 Uptime: 19m Memory: 7.7 GiB used: 976.6 MiB (12.4%) gpu: 76 MiB Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Sat Dec 09, 2023 10:32 am**

Senpai wrote: ↑Sat Dec 09, 2023 10:03 am Hi:
When installing Kodi on a raspi4, it does not run, it seems that it is because it asks for pulseaudio and by default this Pipewire, the screen stays black and the raspi hung, I have to turn off from the button.
Any way to put pulseaudio? to test if it runs?
I have tried again after this last update with the same result.
The case is that in the "Alpha" version Kodi worked.

Best regards

I tried installing "pulseaudio", it uninstalled:
pipewire-alsa [0.3.65-3+rpt3], pipewire-setup-mx [23.09.01], and with autoremove: gstreamer1.0-pipewire libspa-0.2-jack pipewire-jack.

Although the error is no longer displayed, it still hangs... I also tried to start Kodi, from Lightdm login, but it doesn't start, it goes back to Lightdm.

Posted: **Sat Dec 09, 2023 10:37 am**

Catfish is not installed, so "Find files" in Thunar does nothing. Should probably be there.

Posted: **Sat Dec 09, 2023 12:34 pm**

There are a lot of threads (complaints) about kodi on the RPi Forum. This is one of those topics that I suggest our users pursue over there where many people with installations are working on it right now--I don't believe we should be trying to support it over here.

BTW: I see people recommending that it works much better when launched with

Code: Select all

kodi fullscreen

(not sure that is the correct syntax).

Posted: **Sat Dec 09, 2023 3:02 pm**

Jerry3904 wrote: ↑Sat Dec 09, 2023 12:34 pm There are a lot of threads (complaints) about kodi on the RPi Forum. This is one of those topics that I suggest our users pursue over there where many people with installations are working on it right now--I don't believe we should be trying to support it over here.

BTW: I see people recommending that it works much better when launched with
Code: Select all
kodi fullscreen
(not sure that is the correct syntax).

Hi Jerry3904:
The command is

Code: Select all

kodi --standalone -fs

, but it still gives the pulseaudio error and does not work.
I put it here because of the error with pulseaudio, which did not give it in the alpha version where it worked without problems, of course it is not a matter of hurry, but I'm sure that respberry users will want to use kodi in MX, if or if...

By the way, although it is out of the thread, I am testing Fluxbox and it works perfectly in this new build.

Best regards

Posted: **Sat Dec 09, 2023 6:28 pm**

[kodi installed via mxpi popular apps]

Seeing the same thing as Senpai. If I launch 'Kodi' or 'Kodi Fullscreen' from the whisker menu, nothing happens.

If I launch 'kodi' or 'kodi --standalone -fs' from terminal:
''
Failed to stop pulseaudio.socket: Unit pulseaudio.socket not loaded.
Failed to stop pulseaudio.service: Unit pulseaudio.service not loaded.
[sudo] password for account:
''

If I enter my account password kodi will launch. Thereafter kodi will successfully launch via the whisker menu, that is until I reboot.

Posted: **Mon Dec 11, 2023 7:01 am**

In his video review of the alpha, Lee suggested that pi-apps would be a great addition. I hadn't thought of that myself so am currently testing it--very cool app, especially for the games. I'm thinking that we could at least add the website to the menu, since there is an install button on it.

Website: https://pi-apps.io/
CLI install:

Code: Select all

wget -qO- https://raw.githubusercontent.com/Botspot/pi-apps/master/install | bash

Posted: **Mon Dec 11, 2023 7:50 am**

Jerry3904 wrote: ↑Mon Dec 11, 2023 7:01 am In his video review of the alpha, Lee suggested that pi-apps would be a great addition. I hadn't thought of that myself so am currently testing it--very cool app, especially for the games. I'm thinking that we could at least add the website to the menu, since there is an install button on it.

Website: https://pi-apps.io/
CLI install:
Code: Select all
wget -qO- https://raw.githubusercontent.com/Botspot/pi-apps/master/install | bash

I'm uncomfortable adding this application. Mostly because it doesn't not stick to package management for install functions. I'm sure its a fine utility, but I don't want to have to deal with questions about how it works. and we would not be able to push updates to the app without packaging the thing our selves.

it also has no localization nor is it set up or localization of any sort.

Posted: **Mon Dec 11, 2023 7:55 am**

I'm uncomfortable adding this application.

OK. No Menu link either?

I think I read that it updates itself, but haven't gotten that far yet.

Posted: **Mon Dec 11, 2023 8:04 am**

Jerry3904 wrote: ↑Mon Dec 11, 2023 7:55 am
I'm uncomfortable adding this application.
OK. No Menu link either?

I think I read that it updates itself, but haven't gotten that far yet.

again its totally outside the package management system. I would prefer not to go down that road. that is a line we drew on the main line distributions and I think its a good one.

Posted: **Mon Dec 11, 2023 8:05 am**

Posted: **Mon Dec 11, 2023 8:21 am**

Jerry3904 wrote: ↑Sat Dec 09, 2023 6:08 am About that Chromium autologin problem: I wonder if this piece, though not completely the same, might have useful info:

https://dev.to/rahedmir/how-to-fix-goog ... linux-1dl0

LATER Unless I have missed something, I think we should look at this closely. There will be questions about avoiding overwriting with upgrades and possible security implications, I suppose. I followed the suggestion to add

Code: Select all

--password-store=basic

after every "exec", changed back to autologin and rebooted. First time, Chromium appeared to hang, then I did it again and it opened without asking for authorization. Chromium was treating it as a new user, I believe, since my Forum login info was not preserved. The revised /usr/share/applications/chromium-browser.desktop file:

Code: Select all

[Desktop Entry]
Version=1.0
Name=Chromium Web Browser
Name[ast]=Restolador web Chromium
Name[bg]=Уеб четец Chromium
Name[bn]=ক্রোমিয়াম ওয়েব ব্রাউজার
Name[bs]=Chromium web preglednik
Name[ca]=Navegador web Chromium
Name[ca@valencia]=Navegador web Chromium
Name[da]=Chromium netbrowser
Name[de]=Chromium-Webbrowser
Name[en_AU]=Chromium Web Browser
Name[eo]=Kromiumo retfoliumilo
Name[es]=Navegador web Chromium
Name[et]=Chromiumi veebibrauser
Name[eu]=Chromium web-nabigatzailea
Name[fi]=Chromium-selain
Name[fr]=Navigateur Web Chromium
Name[gl]=Navegador web Chromium
Name[he]=דפדפן האינטרנט כרומיום
Name[hr]=Chromium web preglednik
Name[hu]=Chromium webböngésző
Name[hy]=Chromium ոստայն զննարկիչ
Name[ia]=Navigator del web Chromium
Name[id]=Peramban Web Chromium
Name[it]=Browser web Chromium
Name[ja]=Chromium ウェブ・ブラウザ
Name[ka]=ვებ ბრაუზერი Chromium
Name[ko]=Chromium 웹 브라우저
Name[kw]=Peurel wias Chromium
Name[ms]=Pelayar Web Chromium
Name[nb]=Chromium nettleser
Name[nl]=Chromium webbrowser
Name[pt_BR]=Navegador de Internet Chromium
Name[ro]=Navigator Internet Chromium
Name[ru]=Веб-браузер Chromium
Name[sl]=Chromium spletni brskalnik
Name[sv]=Webbläsaren Chromium
Name[ug]=Chromium توركۆرگۈ
Name[vi]=Trình duyệt Web Chromium
Name[zh_CN]=Chromium 网页浏览器
Name[zh_HK]=Chromium 網頁瀏覽器
Name[zh_TW]=Chromium 網頁瀏覽器
GenericName=Web Browser
GenericName[ar]=متصفح الشبكة
GenericName[ast]=Restolador web
GenericName[bg]=Уеб браузър
GenericName[bn]=ওয়েব ব্রাউজার
GenericName[bs]=Web preglednik
GenericName[ca]=Navegador web
GenericName[ca@valencia]=Navegador web
GenericName[cs]=WWW prohlížeč
GenericName[da]=Browser
GenericName[de]=Web-Browser
GenericName[el]=Περιηγητής ιστού
GenericName[en_AU]=Web Browser
GenericName[en_GB]=Web Browser
GenericName[eo]=Retfoliumilo
GenericName[es]=Navegador web
GenericName[et]=Veebibrauser
GenericName[eu]=Web-nabigatzailea
GenericName[fi]=WWW-selain
GenericName[fil]=Web Browser
GenericName[fr]=Navigateur Web
GenericName[gl]=Navegador web
GenericName[gu]=વેબ બ્રાઉઝર
GenericName[he]=דפדפן אינטרנט
GenericName[hi]=वेब ब्राउज़र
GenericName[hr]=Web preglednik
GenericName[hu]=Webböngésző
GenericName[hy]=Ոստայն զննարկիչ
GenericName[ia]=Navigator del Web
GenericName[id]=Peramban Web
GenericName[it]=Browser web
GenericName[ja]=ウェブ・ブラウザ
GenericName[ka]=ვებ ბრაუზერი
GenericName[kn]=ಜಾಲ ವೀಕ್ಷಕ
GenericName[ko]=웹 브라우저
GenericName[kw]=Peurel wias
GenericName[lt]=Žiniatinklio naršyklė
GenericName[lv]=Tīmekļa pārlūks
GenericName[ml]=വെബ് ബ്രൌസര്‍
GenericName[mr]=वेब ब्राऊजर
GenericName[ms]=Pelayar Web
GenericName[nb]=Nettleser
GenericName[nl]=Webbrowser
GenericName[or]=ଓ୍ବେବ ବ୍ରାଉଜର
GenericName[pl]=Przeglądarka WWW
GenericName[pt]=Navegador Web
GenericName[pt_BR]=Navegador web
GenericName[ro]=Navigator de Internet
GenericName[ru]=Веб-браузер
GenericName[sk]=WWW prehliadač
GenericName[sl]=Spletni brskalnik
GenericName[sr]=Интернет прегледник
GenericName[sv]=Webbläsare
GenericName[ta]=இணைய உலாவி
GenericName[te]=మహాతల అన్వేషి
GenericName[th]=เว็บเบราว์เซอร์
GenericName[tr]=Web Tarayıcı
GenericName[ug]=توركۆرگۈ
GenericName[uk]=Навігатор Тенет
GenericName[vi]=Bộ duyệt Web
GenericName[zh_CN]=网页浏览器
GenericName[zh_HK]=網頁瀏覽器
GenericName[zh_TW]=網頁瀏覽器
Comment=Access the Internet
Comment[ar]=الدخول إلى الإنترنت
Comment[ast]=Accesu a Internet
Comment[bg]=Достъп до интернет
Comment[bn]=ইন্টারনেটে প্রবেশ করুন
Comment[bs]=Pristup internetu
Comment[ca]=Accediu a Internet
Comment[ca@valencia]=Accediu a Internet
Comment[cs]=Přístup k internetu
Comment[da]=Få adgang til internettet
Comment[de]=Internetzugriff
Comment[el]=Πρόσβαση στο Διαδίκτυο
Comment[en_AU]=Access the Internet
Comment[en_GB]=Access the Internet
Comment[eo]=Akiri interreton
Comment[es]=Acceda a Internet
Comment[et]=Pääs Internetti
Comment[eu]=Sartu Internetera
Comment[fi]=Käytä internetiä
Comment[fil]=I-access ang Internet
Comment[fr]=Accéder à Internet
Comment[gl]=Acceda a Internet
Comment[gu]=ઇંટરનેટ ઍક્સેસ કરો
Comment[he]=גישה לאינטרנט
Comment[hi]=इंटरनेट तक पहुंच स्थापित करें
Comment[hr]=Pristupite Internetu
Comment[hu]=Az internet elérése
Comment[hy]=Մուտք համացանց
Comment[ia]=Accede a le Interrete
Comment[id]=Akses Internet
Comment[it]=Accesso a Internet
Comment[ja]=インターネットにアクセス
Comment[ka]=ინტერნეტში შესვლა
Comment[kn]=ಇಂಟರ್ನೆಟ್ ಅನ್ನು ಪ್ರವೇಶಿಸಿ
Comment[ko]=인터넷에 연결합니다
Comment[kw]=Hedhes an Kesrosweyth
Comment[lt]=Interneto prieiga
Comment[lv]=Piekļūt internetam
Comment[ml]=ഇന്റര്‍‌നെറ്റ് ആക്‌സസ് ചെയ്യുക
Comment[mr]=इंटरनेटमध्ये प्रवेश करा
Comment[ms]=Mengakses Internet
Comment[nb]=Bruk internett
Comment[nl]=Verbinding maken met internet
Comment[or]=ଇଣ୍ଟର୍ନେଟ୍ ପ୍ରବେଶ କରନ୍ତୁ
Comment[pl]=Skorzystaj z internetu
Comment[pt]=Aceder à Internet
Comment[pt_BR]=Acessar a internet
Comment[ro]=Accesați Internetul
Comment[ru]=Доступ в Интернет
Comment[sk]=Prístup do siete Internet
Comment[sl]=Dostop do interneta
Comment[sr]=Приступите Интернету
Comment[sv]=Surfa på Internet
Comment[ta]=இணையத்தை அணுகுதல்
Comment[te]=ఇంటర్నెట్‌ను ఆక్సెస్ చెయ్యండి
Comment[th]=เข้าถึงอินเทอร์เน็ต
Comment[tr]=İnternet'e erişin
Comment[ug]=ئىنتېرنېت زىيارىتى
Comment[uk]=Доступ до Інтернету
Comment[vi]=Truy cập Internet
Comment[zh_CN]=访问互联网
Comment[zh_HK]=連線到網際網路
Comment[zh_TW]=連線到網際網路
Exec=chromium-browser --password-store=basic %U
Terminal=false
X-MultipleArgs=false
Type=Application
Icon=chromium-browser
Categories=Network;WebBrowser;
MimeType=text/html;text/xml;application/xhtml_xml;x-scheme-handler/http;x-scheme-handler/https;
StartupNotify=true
Actions=NewWindow;Incognito;TempProfile;
X-AppInstall-Package=chromium-browser

[Desktop Action NewWindow]
Name=Open a New Window
Name[ast]=Abrir una Ventana Nueva
Name[bg]=Отваряне на Нов прозорец
Name[bn]=একটি নতুন উইন্ডো খুলুন
Name[bs]=Otvori novi prozor
Name[ca]=Obre una finestra nova
Name[ca@valencia]=Obri una finestra nova
Name[da]=Åbn et nyt vindue
Name[de]=Ein neues Fenster öffnen
Name[en_AU]=Open a New Window
Name[eo]=Malfermi novan fenestron
Name[es]=Abrir una ventana nueva
Name[et]=Ava uus aken
Name[eu]=Ireki leiho berria
Name[fi]=Avaa uusi ikkuna
Name[fr]=Ouvrir une nouvelle fenêtre
Name[gl]=Abrir unha nova xanela
Name[he]=פתיחת חלון חדש
Name[hy]=Բացել նոր պատուհան
Name[ia]=Aperi un nove fenestra
Name[it]=Apri una nuova finestra
Name[ja]=新しいウィンドウを開く
Name[ka]=ახალი ფანჯრის გახსნა
Name[kw]=Egery fenester noweth
Name[ms]=Buka Tetingkap Baru
Name[nb]=Åpne et nytt vindu
Name[nl]=Nieuw venster openen
Name[pt_BR]=Abre uma nova janela
Name[ro]=Deschide o fereastră nouă
Name[ru]=Открыть новое окно
Name[sl]=Odpri novo okno
Name[sv]=Öppna ett nytt fönster
Name[ug]=يېڭى كۆزنەك ئاچ
Name[uk]=Відкрити нове вікно
Name[vi]=Mở cửa sổ mới
Name[zh_CN]=打开新窗口
Name[zh_TW]=開啟新視窗
Exec=chromium-browser--password-store=basic

[Desktop Action Incognito]
Name=Open a New Window in incognito mode
Name[ast]=Abrir una ventana nueva en mou incógnitu
Name[bg]=Отваряне на нов прозорец в режим \"инкогнито\"
Name[bn]=একটি নতুন উইন্ডো খুলুন ইনকোগনিটো অবস্থায়
Name[bs]=Otvori novi prozor u privatnom modu
Name[ca]=Obre una finestra nova en mode d'incògnit
Name[ca@valencia]=Obri una finestra nova en mode d'incògnit
Name[de]=Ein neues Fenster im Inkognito-Modus öffnen
Name[en_AU]=Open a New Window in incognito mode
Name[eo]=Malfermi novan fenestron nekoniĝeble
Name[es]=Abrir una ventana nueva en modo incógnito
Name[et]=Ava uus aken tundmatus olekus
Name[eu]=Ireki leiho berria isileko moduan
Name[fi]=Avaa uusi ikkuna incognito-tilassa
Name[fr]=Ouvrir une nouvelle fenêtre en mode navigation privée
Name[gl]=Abrir unha nova xanela en modo de incógnito
Name[he]=פתיחת חלון חדש במצב גלישה בסתר
Name[hy]=Բացել նոր պատուհան ծպտյալ աշխատակերպում
Name[ia]=Aperi un nove fenestra in modo incognite
Name[it]=Apri una nuova finestra in modalità incognito
Name[ja]=新しいシークレット ウィンドウを開く
Name[ka]=ახალი ფანჯრის ინკოგნიტოდ გახსნა
Name[kw]=Egry fenester noweth en modh privedh
Name[ms]=Buka Tetingkap Baru dalam mod menyamar
Name[nl]=Nieuw venster openen in incognito-modus
Name[pt_BR]=Abrir uma nova janela em modo anônimo
Name[ro]=Deschide o fereastră nouă în mod incognito
Name[ru]=Открыть новое окно в режиме инкогнито
Name[sl]=Odpri novo okno v načinu brez beleženja
Name[sv]=Öppna ett nytt inkognitofönster
Name[ug]=يوشۇرۇن ھالەتتە يېڭى كۆزنەك ئاچ
Name[uk]=Відкрити нове вікно у приватному режимі
Name[vi]=Mở cửa sổ mới trong chế độ ẩn danh
Name[zh_CN]=以隐身模式打开新窗口
Name[zh_TW]=以匿名模式開啟新視窗
Exec=chromium-browser --incognito --password-store=basic

[Desktop Action TempProfile]
Name=Open a New Window with a temporary profile
Name[ast]=Abrir una ventana nueva con perfil temporal
Name[bg]=Отваряне на Нов прозорец с временен профил
Name[bn]=সাময়িক প্রোফাইল সহ একটি নতুন উইন্ডো খুলুন
Name[bs]=Otvori novi prozor pomoću privremenog profila
Name[ca]=Obre una finestra nova amb un perfil temporal
Name[ca@valencia]=Obri una finestra nova amb un perfil temporal
Name[de]=Ein neues Fenster mit einem temporären Profil öffnen
Name[en_AU]=Open a New Window with a temporary profile
Name[eo]=Malfermi novan fenestron portempe
Name[es]=Abrir una ventana nueva con perfil temporal
Name[et]=Ava uus aken ajutise profiiliga
Name[eu]=Ireki leiho berria behin-behineko profil batekin
Name[fi]=Avaa uusi ikkuna käyttäen väliaikaista profiilia
Name[fr]=Ouvrir une nouvelle fenêtre avec un profil temporaire
Name[gl]=Abrir unha nova xanela con perfil temporal
Name[he]=פתיחת חלון חדש עם פרופיל זמני
Name[hy]=Բացել նոր պատուհան ժամանակավոր հատկագրով
Name[ia]=Aperi un nove fenestra con un profilo provisori
Name[it]=Apri una nuova finestra con un profilo temporaneo
Name[ja]=一時プロファイルで新しいウィンドウを開く
Name[ka]=ახალი ფანჯრის გახსნა დროებით პროფილში
Name[kw]=Egery fenester noweth gen profil dres prys
Name[ms]=Buka Tetingkap Baru dengan profil sementara
Name[nb]=Åpne et nytt vindu med en midlertidig profil
Name[nl]=Nieuw venster openen met een tijdelijk profiel
Name[pt_BR]=Abrir uma nova janela com um perfil temporário
Name[ro]=Deschide o fereastră nouă cu un profil temporar
Name[ru]=Открыть новое окно с временным профилем
Name[sl]=Odpri novo okno z začasnim profilom
Name[sv]=Öppna ett nytt fönster med temporär profil
Name[ug]=ۋاقىتلىق سەپلىمە ھۆججەت بىلەن يېڭى كۆزنەك ئاچ
Name[vi]=Mở cửa sổ mới với hồ sơ tạm
Name[zh_CN]=以临时配置文件打开新窗口
Name[zh_TW]=以暫時性個人身分開啟新視窗
Exec=chromium-browser --temp-profile --password-store=basic

EDIT: I just got a set of 24 upgrades with some PARM files so maybe DO has already taken care of all this...

there is a spot in /etc/chromium for command line switches, which is probably easier than dealing with a modified desktop file.

but I don't think we should modify that particular default. --basic stores passwords in plain text, IIRC.

Posted: **Mon Dec 11, 2023 8:22 am**

Jerry3904 wrote: ↑Sat Dec 09, 2023 10:37 am Catfish is not installed, so "Find files" in Thunar does nothing. Should probably be there.

good, will add.

I should be able to get caught up on the pi respin soon. the kernel issues over the weekend ate up a lot of time.

Posted: **Mon Dec 11, 2023 9:01 am**

Yeah, you were pretty busy there for a while.

Posted: **Mon Dec 11, 2023 5:29 pm**

Just a data point. This respin also runs well on my Orange Pi 5
Nothing special was needed - used RPi imager with no customizations and booted to the MX setup screen.
That expands the potential user base a bit -and the Orange Pi 5 has a built in M.2 socket. I've been running it with debian bullseye on a 1TB nvme drive for months now. It's fast and runs cool (37C) and very quiet in a small case with a 5V fan running off the 3.3 V line.

Code: Select all

System:
  Kernel: 5.10.110-rockchip-rk3588 arch: aarch64 bits: 64 compiler: N/A
    parameters: root=UUID=<filter> rootwait rootfstype=ext4 splash plymouth.ignore-serial-consoles
    console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=
    usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=64M cgroup_enable=cpuset
    cgroup_memory=1 cgroup_enable=memory swapaccount=1
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_rpi_beta1_arm64 Libretto Dec 3  2023 base: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: ARM System: Orange Pi 5 details: N/A
CPU:
  Info: model: N/A variant-1: cortex-a55 variant-2: cortex-a76 bits: 64 type: MCP AMP arch: ARMv8
    family: 8 model-id: 2 stepping: 0
  Topology: variant: cpus: 1x cores: 4 min/max: 408/1800 variant: cpus: 2x cores: 2
    min/max: 408/2400 smt: <unsupported> cache: L1: 3x 256 KiB (768 KiB) desc: d-4x32 KiB; i-4x32 KiB
    L2: 3x 512 KiB (1.5 MiB) desc: 4x128 KiB L3: 3x 3 MiB (9 MiB) desc: 1x3 MiB
  Speed (MHz): avg: 552 high: 600 min/max: 408/1800:2400 scaling: driver: cpufreq-dt
    governor: ondemand cores: 1: 600 2: 600 3: 600 4: 600 5: 600 6: 600 7: 408 8: 408 bogomips: N/A
  Features: Use -f option to see features
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl  Type: spectre_v1 mitigation: __user pointer sanitization
  Type: spectre_v2 status: Vulnerable: Unprivileged eBPF enabled
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: display-subsystem driver: rockchip_drm v: N/A bus-ID: N/A
    chip-ID: rockchip:display-subsystem class-ID: display-subsystem
  Device-2: mali-bifrost driver: mali v: N/A bus-ID: N/A chip-ID: arm:fb000000 class-ID: gpu
  Device-3: rk3588-dw-hdmi driver: dwhdmi_rockchip v: N/A bus-ID: N/A chip-ID: rockchip:fde80000
    class-ID: hdmi
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting dri: swrast gpu: rockchip_drm,mali,dwhdmi_rockchip display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Dell SE2717H/HX serial: <filter> built: 2018
    res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.5 Mesa 23.2.1-1~bpo12+rpt2 renderer: llvmpipe (LLVM 15.0.6 128 bits)
    direct-render: Yes
Audio:
  Device-1: hdmi driver: rk_hdmi_sound bus-ID: N/A chip-ID: rockchip:dp0-sound class-ID: dp0-sound
  Device-2: rk3588-dw-hdmi driver: dwhdmi_rockchip bus-ID: N/A chip-ID: rockchip:fde80000
    class-ID: hdmi
  Device-3: hdmi driver: rk_hdmi_sound bus-ID: N/A chip-ID: rockchip:hdmi0-sound
    class-ID: hdmi0-soundV line
  API: ALSA v: k5.10.110-rockchip-rk3588 status: kernel-api tools: alsamixer,amixerV
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: rk3588-gmac driver: rk_gmac_dwmac v: N/A port: N/A bus-ID: N/A
    chip-ID: rockchip:fe1c0000 class-ID: ethernet
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1012.11 GiB used: 5.67 GiB (0.6%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/mmcblk1 maj-min: 179:0 model: SD size: 58.24 GiB block-size: physical: 512 B
    logical: 512 B type: SSD serial: <filter> scheme: MBR
  ID-2: /dev/nvme0n1 maj-min: 259:0 model: JAJP600M1TB size: 953.87 GiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: VC2S038E
    scheme: GPT
Partition:
  ID-1: / raw-size: 7.72 GiB size: 7.5 GiB (97.24%) used: 5.6 GiB (74.6%) fs: ext4
    dev: /dev/mmcblk1p2 maj-min: 179:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 100 MiB used: 0 KiB (0.0%) priority: -2 file: /var/swap
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 1640 libs: 914 tools: apt,apt-get,aptitude,nala,synaptic
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://deb.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb [arch=arm64] http://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/raspi.list
    1: deb http://archive.raspberrypi.com/debian/ bookworm main
Info:
  Processes: 267 Uptime: 0m Memory: 7.51 GiB used: 858.6 MiB (11.2%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Mon Dec 11, 2023 5:34 pm**

That's great. I was planning to try it but wasn't sure whether it would pick up the sd. Pls describe the steps you took for my help material.

Posted: **Mon Dec 11, 2023 7:40 pm**

The only thing I had to do differently was because I was already running from the nvme drive. Otherwise it was just the same as running on your RPis.
As you thought might be the case, you can't boot from the SD card if there's a system on the nvme. There is one exception - if the UUIDs of the root system on the SD card and the root partition on the nvme match, then it will boot from the SD card. So I changed the UUID on the SD card using these commands from the Orange Pi 5 running in the nvme with the sd card plugged in.

Code: Select all

sudo blkid
sudo e2fs -f /dev/mmcblk1p2
tune2fs -U "UUID of the root partition on the nvme from the first command" /dev/mmcblk1p2

Reboot and it boots off the sd card. Shut down, remove the sd card, and it boots off the nvme.
For some reason tune2fs won't change the uuid unless the sd card partition has had the e2fs -f run on it first, that's why it's in there.

Posted: **Mon Dec 11, 2023 7:46 pm**

Thanks

Posted: **Tue Dec 12, 2023 9:43 am**

added catfish, made a new image. things seem correct, however due to technical reasons beyond my control I cannot upload the image right now. will do so tonight.

Posted: **Tue Dec 12, 2023 9:56 am**

Great, no hurry exactly.

Posted: **Tue Dec 12, 2023 3:41 pm**

mugshot not installed, so editing profile fails

Posted: **Tue Dec 12, 2023 3:47 pm**

ok will add

Posted: **Tue Dec 12, 2023 3:54 pm**

@chrispop99 You were right about the hdmi cable being the problem I was seeing with the monitor; the one that came with the Cana kit is just not very good. Buying a high-quality shielded and heavily wrapped cable fixed not only the problem of the Display dialog box popping up but also the flickering of the cursor. It's hard to find a cable with a micro-hdmi end, at least around here, so I ended up buying an adapter and a 4' standard hdmi cable.

I saw one of the RPi Devs (Dom) say that the cable is usually responsible for the video problems people report,maybe especially on the Pi 5.

Posted: **Wed Dec 13, 2023 4:09 am**

Jerry3904 wrote: ↑Tue Dec 12, 2023 3:54 pm @chrispop99 You were right about the hdmi cable being the problem I was seeing with the monitor; the one that came with the Cana kit is just not very good. Buying a high-quality shielded and heavily wrapped cable fixed not only the problem of the Display dialog box popping up but also the flickering of the cursor. It's hard to find a cable with a micro-hdmi end, at least around here, so I ended up buying an adapter and a 4' standard hdmi cable.

I saw one of the RPi Devs (Dom) say that the cable is usually responsible for the video problems people report,maybe especially on the Pi 5.

Thanks for the confirmation.

Chris

Posted: **Wed Dec 13, 2023 8:51 am**

can someone that has access to the pi respin post the following items:

Code: Select all

ls /etc
ls /etc/init.d
ls /lib/systemd/system

thanks!

Posted: **Wed Dec 13, 2023 9:27 am**

Will this do?

Posted: **Wed Dec 13, 2023 10:17 am**

Jerry3904 wrote: ↑Wed Dec 13, 2023 9:27 am Will this do?

perfect thanks.

working on not having the user setup launch until after the pi's first reboot.

Posted: **Wed Dec 13, 2023 10:33 am**

Good luck with that, it would be nice for sure.

Posted: **Wed Dec 13, 2023 1:15 pm**

Jerry3904 wrote: ↑Wed Dec 13, 2023 10:33 am Good luck with that, it would be nice for sure.

can you give me the contents of /etc/rpi-issue?

Posted: **Wed Dec 13, 2023 1:20 pm**

on the Pi 5 still

Code: Select all

Raspberry Pi reference 2023-10-10
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 962bf483c8f326405794827cce8c0313fd5880a8, stage2

Posted: **Wed Dec 13, 2023 2:04 pm**

great thanks

Posted: **Wed Dec 13, 2023 8:07 pm**

I have a proof-of-concept splash. Here's what I did:

--snooped around the RPi Forum, found som very helpful threads
--looked at what synaptic showed in a search on "splash"
--installed rpd-plym-splash
--removed the file "splash.png" file from /usr/share/plymouth/themes/pix/
--pasted Melber's image (1024x768, the recommended size) into that folder and renamed it "splash.png"
--ran this command:

Code: Select all

sudo plymouth-set-default-theme --rebuild-initrd pix

Notes
--Splash can be turned on/off using raspi-config > System Options > Splash Screen
--We would want to test variations of image size, colors, etc.
--Couldn't run on a user's first boot, so would need an installation flag or something
--BTW: I realize we may not want to have it, this is just an exploration not a recommendation

Video
50 secs of my test/development machine with a cheap monitor, starting from my clicking "Restart" until back at desktop. BTW: RPi has the same line of code bottom left on booting, though Ubuntu has it blocked out.

https://drive.google.com/file/d/1OmYw8D ... drive_link

Posted: **Thu Dec 14, 2023 4:20 am**

@Jerry3904 Looks good; hope we go with it.

I don't mind seeing the code at the bottom. It makes it obvious things are happening.

Chris

Posted: **Thu Dec 14, 2023 4:49 am**

@Jerry3904 I threw that png together quickly and have just noticed the thin white border, which was not intentional.

Let me know if you want a version without the border, or some other change.

+++edit+++

Here's a version using the last image from the mx boot animation

splash.png

Posted: **Thu Dec 14, 2023 6:55 am**

Beta2 is up: https://sourceforge.net/projects/mx-lin ... p/download

No time now, but took a quick look and it seems the first-run sequence has been nicely smoothed out and that Chromium security has been fixed.

Posted: **Thu Dec 14, 2023 7:45 am**

Jerry3904 wrote: ↑Thu Dec 14, 2023 6:55 am Beta2 is up: https://sourceforge.net/projects/mx-lin ... p/download

No time now, but took a quick look and it seems the first-run sequence has been nicely smoothed out and that Chromium security has been fixed.

fwiw I did not touch chromium

Posted: **Thu Dec 14, 2023 8:09 am**

Aha, well it's better. Wishful thinking...

Posted: **Thu Dec 14, 2023 11:40 am**

@chrispop99 Can you run a test of blanking for me on the Pi 5?

On either our b2 or the official updated RPi OS that came with the Pi 5, when I use raspi-config to enable screen blanking (for the xset default of 10 mins of inactivity) the screen indeed blanks after that amount of inactivity. But: about 20 secs later it comes on again.

I would like to eliminate the monitor factor, hence my request. I don't get the impression that the PI 4 or 400 is affected, though I have found very little about this whole topic on the RPi Forum that is useful. Nothing in the Documentation either.

TIA

Posted: **Thu Dec 14, 2023 2:11 pm**

Jerry3904 wrote: ↑Thu Dec 14, 2023 11:40 am @chrispop99 Can you run a test of blanking for me on the Pi 5?

On either our b2 or the official updated RPi OS that came with the Pi 5, when I use raspi-config to enable screen blanking (for the xset default of 10 mins of inactivity) the screen indeed blanks after that amount of inactivity. But: about 20 secs later it comes on again.

I would like to eliminate the monitor factor, hence my request. I don't get the impression that the PI 4 or 400 is affected, though I have found very little about this whole topic on the RPi Forum that is useful. Nothing in the Documentation either.

TIA

I tested with a Pi 5, and the Beta. Let it blank for about 10 minutes, and it resumed OK, without coming back on. Tested a couple of times for shorter off periods, waking it first with the mouse, then with the keyboard, and again it worked as it should.

Chris

Posted: **Thu Dec 14, 2023 2:12 pm**

Thanks, very helpful. Must be the monitor, I guess.

Posted: **Fri Dec 15, 2023 9:10 am**

Highly irregular use of this thread: my basic customization of B2 this morning, nice match of wallpaper with smaller logo and conky flair

Posted: **Fri Dec 15, 2023 9:40 am**

Like the look!

I was about to ask if we should show the CPU temperature somewhere, as it's a bit of an issue with Pi 5.

Chris

Posted: **Fri Dec 15, 2023 10:35 am**

That's a very good question. The one I use in that image is the only one I can think of off-hand.

If @dolphin_oracle would be willing to switch default conky I could easily modify the one we use to include temp. I'll do a test this afternoon (4hrs from now) so people can see how it would look.

Posted: **Fri Dec 15, 2023 11:07 am**

Jerry3904 wrote: ↑Fri Dec 15, 2023 10:35 am That's a very good question. The one I use in that image is the only one I can think of off-hand.

If @dolphin_oracle would be willing to switch default conky I could easily modify the one we use to include temp. I'll do a test this afternoon (4hrs from now) so people can see how it would look.

yes it can be adjusted. that selection is not part of any package, so there are no conflicts to worry about.

Posted: **Fri Dec 15, 2023 11:15 am**

I'm seeing a problem with a freshly downloaded b2. The mouse cursor flashes at about 1Hz. If I turn Conky off, it stops the flashing. Changing to a different Conky doesn't fix the problem.

Chris

Posted: **Fri Dec 15, 2023 11:29 am**

I've seen that and was able to almost eliminate it by adjusting the values in the Mouse and Touchpad settings. On the road for a few hours but will report working settings when I get back.Another example of wishful thinking...

Posted: **Fri Dec 15, 2023 4:35 pm**

About a revised default conky, here is the best that I can produce (MX-Cowon_MildBlue_temp):

Code: Select all

conky.config = {
--#####################
-- - Conky settings - #
--#####################
	update_interval = 1,
	total_run_times = 0,
	net_avg_samples = 1,
	cpu_avg_samples = 1,

	imlib_cache_size = 0,
	double_buffer = true,
	no_buffers = true,

--####################
-- - Text settings - #
--####################
	use_xft = true,
    font = 'Roboto-Light:size=100',
	override_utf8_locale = true,
	text_buffer_size = 2048,
	xftalpha = 0.9,

--############################
-- - Window specifications - #
--############################
	own_window_class = 'Conky',
	own_window = true,
	own_window_type = 'normal',
	own_window_transparent = true,

	own_window_hints = 'undecorated,below,skip_taskbar,skip_pager,sticky',
--own_window_argb_visual yes
--own_window_argb_value 100

	alignment = 'top_right',
	gap_x = 40,
	gap_y = 40,
	minimum_width = 200, minimum_height = 220,

	
--########################
-- - Templates - 		#
--########################

template1 = '${color3}${font RobotoMono-Light:bold:pixelsize=12}${offset 8}',
template2 = '${offset 3} ${color3}bat${offset 6}',

	
--########################
-- - Graphics settings - #
--########################
	draw_shades = false,

	--hour
	default_color = 'aabbcc',
	default_shade_color = '1d1d1d',
	color0 = 'ffffff',
	--date
	color1 = 'aabbcc',
	--min
	color2 = '77ddff',
	--text
	color3 = '77ddff',
	--percentages
	color4 = 'aabbcc',

--lua_load ~/.conky/conkybg.lua
--lua_draw_hook_pre conky_draw_bg

	own_window_argb_value = 0,
	own_window_argb_visual = true,
	own_window_colour = '000000',
	lua_load = 'lua/conky.lua',

};

-- fluxbox adjustment
-- if os.getenv("XDG_SESSION_DESKTOP") == 'fluxbox' then
return_code = os.execute('pidof -q fluxbox')
if _VERSION == 'Lua 5.1' and math.floor(return_code/256) == 0 or
   _VERSION ~= 'Lua 5.1' and return_code then
   conky.config.own_window_transparent = true
   conky.config.own_window_argb_visual = false
end

conky.text = [[
${if_match "${lua time A}" == "${time %A}"}${lua set_time A}\
${else}${lua set_time a}${endif}\
${if_match "${lua time B}" == "${time %B}"}${lua set_time B}\
${else}${lua set_time b}${endif}\
${voffset -176}
${lua hours}
${color2}${offset 36}${voffset -95}${time %M}
${voffset -130}${offset 10}\
${if_match "${lua cjk}" == "false"}\
${font Roboto-Light:bold:size=12}\
${else}\
${font wqy-microhei:bold:size=12}\
${endif}\
${color1}${lua date}
${offset 150}${voffset -175}\
${if_match "${lua cjk}" == "false"}\
${font Roboto-Light:size=12}\
${else}\
${font wqy-microhei:size=12}\
${endif}\
${color2}${lua AM_PM}
#system
${offset 0}${voffset 160}\
${font Roboto-Light:bold:pixelsize=14}${offset 12}${color3}hdd \
${offset 2}${color4}\
${font RobotoMono-Light:bold:pixelsize=12}${fs_used_perc /}%\
${font Roboto-Light:bold:pixelsize=14}\
${offset 4}${color3} mem \
${offset 2}${color4}\
${font RobotoMono-Light:bold:pixelsize=12}${lua memperc}%\
${font Roboto-Light:bold:pixelsize=14}\
${offset 2}${offset 4}${color3}cpu\
${color4}${font RobotoMono-Light:bold:pixelsize=12}${lua cpu}%\
#battery and temperature
${offset 4}${voffset 4}\
${if_existing /sys/class/power_supply/BAT0}${template1}
${template2} ${color4}${battery_percent BAT0}% ${endif}\
${if_existing /sys/class/power_supply/BAT1}${template1}
${template2} ${color4}${battery_percent BAT1}% ${endif}\
${offset 20}${color3}temp ${color4}${if_existing /sys/class/thermal/thermal_zone0/temp}${eval ${acpitemp}}${endif}°C

${voffset -190}
]];

I would like to ask @ceeslans and anyone else who has time and inclination to review it when time and inclination are present.

Posted: **Fri Dec 15, 2023 5:09 pm**

EDIT: gets screwed up when I move it over to the Pi 5 where there is no battery. Will review tomorrow again, rats.

Posted: **Fri Dec 15, 2023 6:58 pm**

Jerry3904 wrote: ↑Fri Dec 15, 2023 5:09 pm EDIT: gets screwed up when I move it over to the Pi 5 where there is no battery. Will review tomorrow again, rats.

@Jerry3904 Since this is for the (no-battery) Pi 5 respin, you probably should remove the battery section.
Here is a version without that section. Tried to maintain the same layout, but grouped the system items to make it visually more coherent.
Trust that transparency can be set enabled/disabled using conkymanager2.

scrot_Rpi-conky.png

Code: Select all

conky.config = {

--#####################
-- - Conky settings - #
--#####################
	update_interval = 1,
	total_run_times = 0,
	net_avg_samples = 1,
	cpu_avg_samples = 1,

	imlib_cache_size = 0,
	double_buffer = true,
	no_buffers = true,

--####################
-- - Text settings - #
--####################
	use_xft = true,
    font = 'Roboto Light:size=100',
	override_utf8_locale = true,
	text_buffer_size = 2048,
	xftalpha = 0.9,

--############################
-- - Window specifications - #
--############################
	own_window_class = 'Conky',
	own_window = true,
	own_window_type = 'normal',
	
	own_window_transparent = true,
	own_window_argb_visual = false,
	own_window_argb_value = 0,
	
	own_window_hints = 'undecorated,below,skip_taskbar,skip_pager,sticky',

	alignment = 'top_right',
	gap_x = 30,
	gap_y = 45,
	minimum_width = 210, 
	minimum_height = 0,

--########################
-- - Graphics settings - #
--########################
	draw_shades = false,
	own_window_colour = '000000',
	
	--hour
	default_color = 'aabbcc',
	default_shade_color = '1d1d1d',
	color0 = 'ffffff',
	--date
	color1 = 'aabbcc',
	--min
	color2 = '77ddff',
	--text
	color3 = '77ddff',
	--percentages
	color4 = 'aabbcc',

	lua_load = 'lua/conky.lua',

};

		-- fluxbox adjustment
		-- if os.getenv("XDG_SESSION_DESKTOP") == 'fluxbox' then
		-- return_code = os.execute('pidof -q fluxbox')
		-- if _VERSION == 'Lua 5.1' and math.floor(return_code/256) == 0 or
		--   _VERSION ~= 'Lua 5.1' and return_code then
		--   conky.config.own_window_transparent = true,
		--   conky.config.own_window_argb_visual = false,
		-- end

conky.text = [[
### hours
${if_match "${lua time A}" == "${time %A}"}${lua set_time A}${else}${lua set_time a}${endif}\
${if_match "${lua time B}" == "${time %B}"}${lua set_time B}${else}${lua set_time b}${endif}\
${voffset -175}
${lua hours}
### minutes
${color2}${offset 36}${voffset -95}${time %M}
### date
${voffset -130}${offset 10}\
${if_match "${lua cjk}" == "false"}${font Roboto Light:bold:size=11}${else}${font wqy-microhei:bold:size=12}${endif}${color1}${lua date}
### am/pm
${offset 150}${voffset -175}\
${if_match "${lua cjk}" == "false"}${font Roboto Light:size=12}${else}${font wqy-microhei:size=12}${endif}${color2}${lua AM_PM}
#system
${offset 0}${voffset 160}\
${font Roboto Light:bold:size=10}${goto 25}${color3}hdd ${offset 2}${color4}${fs_used_perc /}%\
${font Roboto Light:bold:size=10}${goto 105}${color3}temp ${offset 2}${color4}${if_existing /sys/class/thermal/thermal_zone0/temp}${eval ${acpitemp}}${endif}°
${voffset 2}\
${font Roboto Light:bold:size=10}${goto 25}${color3}mem ${offset 2}${color4}${memperc}%\
${font Roboto Light:bold:size=10}${goto 105}${color3}cpu${offset 6}${color4}${cpu}%
${voffset -215}
]];

Posted: **Fri Dec 15, 2023 7:31 pm**

That looks nice, I'll give it a spin.

Thanks

Posted: **Fri Dec 15, 2023 8:01 pm**

I was originally thinking that this would be a conky with temp that could be used in other situations, but your simplification looks good and I'm going to go with it after a bit more testing tomorrow. I can always upgrade it later if need be.

I think Chris was exactly right here. Point of reference: on the Pi 5 I'm running an ambient temp of 55-60 for smaller tasks (35-40 on my personal laptop), and it will be interesting to see how it does with more demanding situations.

Posted: **Sat Dec 16, 2023 6:00 am**

I have finished what I was intended of the "RPi TIps" (Wiki) that is linked on the Respin desktop. I just copied the Wiki text and paste-specialed it into a LO document to make it easier (use Track Changes if convenient). It would be great if at least one other person could look at it before Final.

Looking for
--corrections
--suggestions
--curses
--etc.

TIA

Posted: **Sat Dec 16, 2023 6:44 am**

Had a read-through of 'Tips', and all seemed to make sense.

In the Netflix section, this part seemed a bit loose:

This command assumes you are using the default Chromium browser. If not, paste in this command in a terminal:
sudo apt install chromium-browser

Perhaps add:

This command assumes you are using the default Chromium browser. If not, install it by pasting in this command in a terminal:
sudo apt install chromium-browser

Chris

Posted: **Sat Dec 16, 2023 7:33 am**

Good suggestion, thanks for reading it

Posted: **Sat Dec 16, 2023 10:16 am**

you can't use firefox for netflix. at least I never got it to work

sudo rpi-chromium-mods libwidevinecmd0

I presume there is an apt install missing from that command.

int he audio setup, the tips implies audio will not work over HDMI. it does work on HDMI, so some clarification is required there.

Posted: **Sat Dec 16, 2023 10:55 am**

Thanks for looking.

--Yeah, lost that "apt install" when I cut out the chromium part after we changed our default browser.
---On the audio: right, got a bit dumb there....
--I'll go ahead and test Netflix on FF; the RPi group seems to think it works.

Posted: **Sat Dec 16, 2023 10:56 am**

ok.

for me, the widevine plugin never completed setup inside the browser.

Posted: **Sat Dec 16, 2023 10:57 am**

So one older question: is the splash a no-go for you?

Posted: **Sat Dec 16, 2023 11:02 am**

Jerry3904 wrote: ↑Sat Dec 16, 2023 10:57 am So one older question: is the splash a no-go for you?

haven't tested a fresh setup yet. I'm given pause by the fact its not set by default.

Posted: **Sat Dec 16, 2023 11:08 am**

We could leave it as an explicit option in the Tips doc. It's less work and I'd be OK with it.

Posted: **Sat Dec 16, 2023 11:42 am**

Netflix can't work with our ESR version. I tried downloading directly from the Mozilla site, but they have a single blob for all Linux and I couldn't get it to launch on the Pi 5. I'll check the documentation again, but have now just taken out the Firefox section altogether and let the user pursue it on his/her own.

Posted: **Sat Dec 16, 2023 1:51 pm**

The Firefox on the betas is not esr. It’s rpi’s firefox.

Mozilla only provides x86 builds.

Posted: **Sat Dec 16, 2023 2:13 pm**

Ah, the things I don't remember...

Posted: **Sat Dec 16, 2023 2:46 pm**

Installed the RPi Firefox and the other two files--butNetflix won't show. That may explain why I was unable to find it any longer in the RPi Documentation.

Posted: **Sat Dec 16, 2023 2:50 pm**

on the splash, the raspi-config splash enable works only with their own splash theme.

however, I can enable whatever plymouth theme you want. the current default of MXLiveLogo is a little heavy on the pi400, but it does work smoothly. futureprototype-mx is better.

if you want one we don't have, probably should zip up the theme folder and sent it. it should not rely on deleting/replacing any existing graphics, as that will cause a package conflict if there is an update. well, maybe not a conflict, but the changes will be lost.

Posted: **Sat Dec 16, 2023 3:31 pm**

dolphin_oracle wrote: ↑Sat Dec 16, 2023 2:50 pm on the splash, the raspi-config splash enable works only with their own splash theme.

J: I found in my testing that it will work with a graphic theme (at least the single one I tried) renamed to and replacing pix/splash.png

however, I can enable whatever plymouth theme you want. the current default of MXLiveLogo is a little heavy on the pi400, but it does work smoothly. futureprototype-mx is better.

J: I don't know that off hand, but if you feel good about it then I say let's go with it

if you want one we don't have, probably should zip up the theme folder and sent it. it should not rely on deleting/replacing any existing graphics, as that will cause a package conflict if there is an update. well, maybe not a conflict, but the changes will be lost.

Thanks for the look.

Posted: **Sat Dec 16, 2023 4:00 pm**

Jerry3904 wrote: ↑Sat Dec 16, 2023 3:31 pm
dolphin_oracle wrote: ↑Sat Dec 16, 2023 2:50 pm on the splash, the raspi-config splash enable works only with their own splash theme.

J: I found in my testing that it will work with a graphic theme (at least the single one I tried) renamed to and replacing pix/splash.png

only if their theme is already installed. the rpd-splash-theme (name?, i forget exact name) package is just a theme pack, but the active splash function in raspi-config doesn't do anything unless its installed. its not actually necessary to have rdp-splash-theme installed.

Posted: **Sat Dec 16, 2023 4:29 pm**

Ok, didn't realize that. I think I might have installed it in an earlier trial.

We would certainly like to have an easy off/on for splash if possible IMO, especially since we don't have Boot Options available.

BTW: since we're going to be using blanking as a screensaver, I'm going to look again at that script I started once (if I can find it) before you incorporated dpms time into the MXFB Tweak. It would be nice for the user to have an option to change the time without having to go to the console. Might be something that @Melber could do a yad with.

EDIT: here it is, kind of clunky...

Code: Select all

# this script sets screen timeout value in seconds using xset for a given session. It was intended for use with Fluxbox and other Window Managers in order to override the default of 600. When placed in the Autostart file, it enables the user's value to persist across sessions

## the parameter TIMEOUT is set in $(HOME)/.config/screen-timeout.conf

source $HOME/.config/screen-timeout.conf

xset -dpms && xset s $TIMEOUT

exit

Posted: **Sat Dec 16, 2023 4:59 pm**

however, I can enable whatever plymouth theme you want. the current default of MXLiveLogo is a little heavy on the pi400, but it does work smoothly. futureprototype-mx is better.

J: I don't know that off hand, but if you feel good about it then I say let's go with it

That said, the MX-23 animation would certainly be the best if it's not just deathly slow on the 400.

Posted: **Sat Dec 16, 2023 5:56 pm**

About the flickering cursor: looking around the web, there are some suggestions that it is associated with the compositor. I don't know that area at all well, but will try to pursue it tomorrow.

EDIT: before a movie, I switched to compton and there is no flickering...but I still know nada about all this.

Posted: **Sat Dec 16, 2023 7:06 pm**

Jerry3904 wrote: ↑Sat Dec 16, 2023 4:29 pm Might be something that @Melber could do a yad with.

Something like this?

Code: Select all

#!/bin/bash

# Simple Yad Frontend to set screen timeout
# This app was developed by MX Devs 2023 and released under GPLv3
# this script sets screen timeout value in seconds using xset for a given session.
# the parameter TIMEOUT is set in $(HOME)/.config/screen-timeout.conf
# version 231201

# yad settings

TITLE="Timeout Settings"
CLASS="mxpi-to"
ICONPATH="appointment-soon-symbolic" 

# yad buttons

export BTN_CLOSE=$(gettext "Close")      ; BTN_CLOSE+='!window-close'
export BTN_APPLY=$(gettext "Apply")    ; BTN_APPLY+='!object-select'

# yad strings

TIMEOUT_TEXT1="Current timeout:"
TIMEOUT_TEXT2="minutes"
TIMEOUT_TEXT3="Select new timeout:     "
TIMEOUT_VALUES="1!5!10!15!30!60!120"
DIALOG_TEXT="Modify screen timeout setting"

# check if conf file exists

if [ ! -f $HOME/.config/screen-timeout.conf ]; then
    echo 'TIMEOUT=600' > $HOME/.config/screen-timeout.conf
fi

# function

set_timeout () {

source $HOME/.config/screen-timeout.conf
TIMEOUT_OLD=$(( $TIMEOUT / 60))

MAIN_YAD=$(yad \
--title="$TITLE" --class="$CLASS" --window-icon="$ICONPATH" \
--center --width=250 --height=250 --borders=10 \
--buttons-layout=spread --button="${BTN_CLOSE}":7 --button="${BTN_APPLY}":6 \
--form --separator='' --align=center \
--text-align=center --text="<b>$DIALOG_TEXT</b>\n" \
--field="$TIMEOUT_TEXT1   <b>$TIMEOUT_OLD</b> $TIMEOUT_TEXT2":LBL "" \
--field=" ":LBL "" \
--field="$TIMEOUT_TEXT3":CB "$TIMEOUT_OLD!$TIMEOUT_VALUES" \
)

ret=$?

case $ret in
    7 | 252 )
        ENDLOOP=getouttahere
    ;;    
        
    6 )
        TIMEOUT_NEW=$(( $MAIN_YAD * 60 ))       
        
        if [ "$TIMEOUT_NEW" != "$TIMEOUT_OLD" ]; then
            sed -i "s/$TIMEOUT/$TIMEOUT_NEW/" $HOME/.config/screen-timeout.conf  
            xset -dpms && xset s $TIMEOUT_NEW
        fi   
    ;;
esac

}

export -f set_timeout

# loop

until [ "$ENDLOOP" = "getouttahere" ]; do

    set_timeout

done

exit

Posted: **Sat Dec 16, 2023 7:06 pm**

Does not the power manager settings app work? To control screen blanking I mean.

Posted: **Sat Dec 16, 2023 8:05 pm**

Haven't had much luck there but will check again in the morning

Posted: **Sat Dec 16, 2023 8:48 pm**

might need to turn OFF the display blanking in raspi-config. experimenting now.

Posted: **Sat Dec 16, 2023 9:13 pm**

yep, turning off the display blanking in raspi-config changes the /etc/X11/xorg.conf.d/10-screen-blanking file to set DPMS disabled to be reused at next login.

but that just allows the xfce power manager daemon to control the screen blanking per the Xfce gui settings. successfully set the screen blanking to 10 minutes (default), 3 minutes, and 30 minutes without issue.

right now I have the next image built with the X screen blanking set to disabled and the usual MXLiveLogo plymouth theme enabled.

Posted: **Sat Dec 16, 2023 9:36 pm**

Cool.

Posted: **Sun Dec 17, 2023 6:32 am**

Melber wrote: ↑Sat Dec 16, 2023 7:06 pm
Jerry3904 wrote: ↑Sat Dec 16, 2023 4:29 pm Might be something that @Melber could do a yad with.
Something like this?

<snip>

Thanks! Works on the Pi 5 no matter what the raspi-config setting is. But it looks like a log out/in resets xset to 600. Maybe a little session starup script that ran "xset s X" where X was the value your script had stored?
I personally find the Xfce4 Power dialog box unappealing for this simple task, so will be interested in testing it more carefully today.

Posted: **Sun Dec 17, 2023 8:31 am**

Further testing reveals that all the radio-config switch does is turn off or reset X defaults.

And doesn’t seem to matter if on or off screen blanking times set by xfce are honored.

Posted: **Sun Dec 17, 2023 8:59 am**

Yeah, it also persists across log out/in apparently b/c they are killing the dpms as well.

Is this the directions we want:

Click Menu > Power Manager, "DIsplay" tab. Confirm that "Display Power Manager" is set to on, then slide bottom 2 sliders to zero before adjusting top slider "Blank after" to number of minutes desired

Posted: **Sun Dec 17, 2023 12:18 pm**

BTW: magnus is not installed, though onboard is. It's available in the repos as a arm64,

Posted: **Sun Dec 17, 2023 12:27 pm**

Jerry3904 wrote: ↑Sun Dec 17, 2023 12:18 pm BTW: magnus is not installed, though onboard is. It's available in the repos as a arm64,

got it

Posted: **Mon Dec 18, 2023 8:26 am**

So what's left?

From my POV: not much
1) evaluate use of compton to fix cursor flicker
--Default or option?
--Downside of use?
--Is it only the Pi 5? If yes, maybe a script to detect that device--ask @timkb4cq about Orange Pi 5--and switch to compton?
2) test/evaluate any splash on all devices
3) correct the wrong temp conky some idiot pushed (happening today)

Recent things I like
1) major upgrade to chromium this morning, much RPi activity (raspi-config, eeprom, etc.)
2) settlement of blanking question
3) review and completion of RPI Tips

My long shot
1) the alternate and smaller logo background (THE_Jet_Dark...) as default. Personal preference for less screen domination--especially on smaller screens frequently used with Raspberry Pi devices--and subtler image

What do you have?

Posted: **Mon Dec 18, 2023 9:01 am**

pretty much the same list, but not the compton thing. I haven't seen any screen/cursor flicker at all on any of the pi spins, both current and the original buster based ones. I would need to investigate HOW to make compton the default. probably not hard, just don't know. There is the option in mx-tweak to change compositors, but I'll need to make sure it works on the pi.

speaking of compton, picom is also on the image. its pulled in by some package, as a recommend (which raspian installs by default and I have not changed). long ago I started working on making picom an option in mx-tweak but never finished. may look into making that option available next year.

I have a RC1 ready, just waiting on the changes to mx-conky-data. we will see how everyone feels about the splash once its enabled.

maybe for mx23.2 the default wallpaper can be revisited.

Posted: **Mon Dec 18, 2023 9:20 am**

Interesting about picom, about to upload the revised conky as soon as my coffee is done.

BTW: I will be totally out of action Friday to Wednesday with at least 7 family members staying in the house, which will render my little RPi workstation in a living room corner totally unusable without risking divorce proceedings...

Posted: **Mon Dec 18, 2023 9:27 am**

Jerry3904 wrote: ↑Mon Dec 18, 2023 9:20 am Interesting about picom, about to upload the revised conky as soon as my coffee is done.

BTW: I will be totally out of action Friday to Wednesday with at least 7 family members staying in the house, which will render my little RPi workstation in a living room corner totally unusable without risking divorce proceedings...

I would like to be officially released this week. maybe the weekend.

Posted: **Mon Dec 18, 2023 9:34 am**

That would be terrific--sorry I held up the RC1 a day!

Posted: **Mon Dec 18, 2023 2:53 pm**

I'm posting from beta2 on the OrangePi 5.
No, there is no mouse pointer blink.
But it doesn't recognize one of the 3 USB ports and I can't get wifi working. The ethernet port works.
the lsmod command returns no data making it harder to trroubleshoot the wifi I suspect I'll need to change kernels for this respin to work as it should.

I must admit, I never tried wifi on beta 1 because the Opi was already hooked up to ethernet.

Posted: **Mon Dec 18, 2023 3:23 pm**

I'm hoping to try with the soon-to-be RC1 if I can get it installed.

Posted: **Mon Dec 18, 2023 5:58 pm**

Found one decent thread about cursor blinking on the Pi 5:

https://forums.raspberrypi.com/viewtopic.php?t=361313

I'm thinking the best we can do is put a paragraph in Tips with options mentioned there and in other threads:
--disable conkies
--change monitors
--use a larger SD (supposedly 128 is recommended; Pi 5 shipped from Cana with 256 and I see no blinking--but it's not Xfce)
--turn off Xfce4 compositor
--switch to compton

Posted: **Tue Dec 19, 2023 5:39 am**

Jerry3904 wrote: ↑Mon Dec 18, 2023 5:58 pm Found one decent thread about cursor blinking on the Pi 5:

https://forums.raspberrypi.com/viewtopic.php?t=361313

I'm thinking the best we can do is put a paragraph in Tips with options mentioned there and in other threads:
--disable conkies
--change monitors
--use a larger SD (supposedly 128 is recommended; Pi 5 shipped from Cana with 256 and I see no blinking--but it's not Xfce)
--turn off Xfce4 compositor
--switch to compton

Disabling Conky works.
I'm struggling to see this as a monitor issue, but all mine are the same make, so can't test.
Again, I fail to see this as a solution, as long as the card has plenty of space, but will check later if I have a large enough card.
If the Xfce4 compositor is turned off, Conky loses transparency, so you get the black box around the Conky.
I haven't tried Compton.

Chris

Posted: **Tue Dec 19, 2023 6:07 am**

I don't have another monitor either, though I might try to use the nice portable screen I use with my phone.

Compton works fine for me and, if I need a conky on all the time, that's what I'll use. (Reminder to self: conky toggle for just critical info).

Posted: **Tue Dec 19, 2023 6:32 am**

I connected the Pi 5 to my smart TV, and the flickering persisted.
I 'borrowed' a 128GB SD card from a GoPro, and the flickering persisted.

Perhaps rather than show unproven suggestions in Tips, just list a clear guide to enabling Compton?

Chris

Posted: **Tue Dec 19, 2023 6:42 am**

chrispop99 wrote: ↑Tue Dec 19, 2023 6:32 am Perhaps rather than show unproven suggestions in Tips, just list a clear guide to enabling Compton?

That along with conky toggle and no conkies would certainly cover all bases--thanks for testing.

I suspect that it is xfwm itself (on this hardware), since neither compton nor the rudimentary xcompmgr shows the problem. I tried disabling xfwm's shadow under docks setting, since compton has it disabled, but no change. Also posted on the Xfce Forum about this, but am not hopeful...

Posted: **Tue Dec 19, 2023 7:13 am**

Bonjour,
Mon système est sur un m2 de 256 Go , et j' avais ce problème de clignotement du curseur qui commence dès que le Conky démarre.
En changeant le compositeur pour compton, plus de problème avec le bureau Xcfe.
Par contre le clignotement continue sur les autres Bureau (Budgie et Cinnamon)

Posted: **Tue Dec 19, 2023 7:18 am**

Compton hasn't been maintained for a while; it appears common wisdom is to use 'picom' instead. We have that installed by default, and it fixes the flickering issue for me.

Perhaps the 'Tips' should say something like:

Some users experience problems with the mouse cursor flickering. Suggested ways to stop this are:

1) Use Conky Toggle to turn the on-screen system monitor off.

2) For users who would still like to use Conky, change the default compositor to the pre-installed 'picom' in the following way:
Go to Settings>Window Manager Tweaks>Compositor, and uncheck 'Enable display compositing'.
To check this fixes the problem, in a terminal, type:

Code: Select all

picom -b

If this fixes the flickering problem, make picon start at boot like this:
Go to Settings>Session and Startup>Application Autostart. Click 'Add'. Fill in the 'Name' and 'Description' fields with whatever seems suitable. Type picom in the 'Command' field.
Reboot to check all is working.

Chris

Posted: **Tue Dec 19, 2023 7:23 am**

Yeah I wanted to try that after DO mentioned it, but just haven't yet--thanks for the directions (I assume that anybody trying this would also need to first turn off any compositor in MX Tweak).

Window Manager Tweaks, "Compositor" tab is off by default for me.

Posted: **Tue Dec 19, 2023 7:45 am**

That does not work for me, even after log out/in. Will try a reboot--no diff.

Code: Select all

$ picom -b
[ 12/19/2023 07:44:07.175 open_config_file_at WARN ] This compositor has been renamed to "picom", the old config file paths is deprecated. Please replace the "compton"s in the path with "picom"
[ 12/19/2023 07:44:07.175 parse_config_libconfig WARN ] Option `menu-opacity` is deprecated, and will be removed.Please use the wintype option `opacity` of `popup_menu`and `dropdown_menu` instead.
[ 12/19/2023 07:44:07.175 parse_config_libconfig WARN ] The refresh-rate option has been deprecated. Please remove it from your configuration file. If you encounter any problems without this feature, please feel free to open a bug report
[ 12/19/2023 07:44:07.175 parse_config_libconfig ERROR ] vsync option will take a boolean from now on. "none" in your configuration should be changed to "false"
[ 12/19/2023 07:44:07.175 main FATAL ERROR ] Failed to create new session.

Posted: **Tue Dec 19, 2023 8:15 am**

J' ai les mêmes erreur que pour Jerry3904, alors qu'il n'y a aucun problème avec compton.

Posted: **Tue Dec 19, 2023 8:15 am**

I'm pretty confident that DO is looking carefully at this so will just chill.

Posted: **Tue Dec 19, 2023 8:16 am**

Mike913 wrote: ↑Tue Dec 19, 2023 8:15 am J' ai les mêmes erreur que pour Jerry3904, alors qu'il n'y a aucun problème avec compton.

Merci.

Posted: **Tue Dec 19, 2023 6:40 pm**

Just putting this out there: do we want to entertain disabling the default short form of desktop icons so users have some sense of what they are?

Posted: **Fri Dec 22, 2023 8:05 am**

will have a new image today, dubbed rc1, for testing.

one known issue. during the first session after the user is set up, chromium will not launch. or rather, chromium launches, but it hangs in the background. a log in and log out cleared the issue for me, but I don't know why its happening in the first place. could be a rpi patch, could be something completely unrelated. Still kept rpi's build of chromium because its hardware accelerated on the pi. firefox and debian's chromium is not.

Posted: **Fri Dec 22, 2023 9:23 am**

dolphin_oracle wrote: ↑Fri Dec 22, 2023 8:05 am will have a new image today, dubbed rc1, for testing.

one known issue. during the first session after the user is set up, chromium will not launch. or rather, chromium launches, but it hangs in the background. a log in and log out cleared the issue for me, but I don't know why its happening in the first place. could be a rpi patch, could be something completely unrelated. Still kept rpi's build of chromium because its hardware accelerated on the pi. firefox and debian's chromium is not.

Did that happen with both auto- and manual login?

Posted: **Fri Dec 22, 2023 9:38 am**

I only had time to test one and I tested manual.

I'm uploading now. should be up in around half and hour.

Posted: **Fri Dec 22, 2023 10:22 am**

A quick around the web on that issue always seems to end with: problem in the profile. That may be irrelevant in this case, but maybe launching it from a terminal with what someone on RPi Forum suggests would be a good way to find out:

Code: Select all

chromium-browser --clear-data

downloading now, very slowly

Posted: **Fri Dec 22, 2023 10:33 am**

Jerry3904 wrote: ↑Fri Dec 22, 2023 10:22 am A quick around the web on that issue always seems to end with: problem in the profile. That may be irrelevant in this case, but maybe launching it from a terminal with what someone on RPi Forum suggests would be a good way to find out:
Code: Select all
chromium-browser --clear-data
downloading now, very slowly

hmm. there shouldn't be a default profile, unless chromium stuffs part of itself somewhere other than the home folder.

Posted: **Fri Dec 22, 2023 10:37 am**

I'm about to publish the video

Posted: **Fri Dec 22, 2023 11:21 am**

OK, I tried to launch chromium in a terminal--and saw the same error message I sent you earlier about missing bluealsa, then a zillion repeats about "failure to get fd for plane" and "no export buffer to dma_buf: no such file or directory."

Much less important: pls change the desktop icon for the YT vid to a recognizable video icon such as /usr/share/icons/Papirus/24x24/mimetypes/video-mp4.svg

Posted: **Fri Dec 22, 2023 11:24 am**

Should we report testing for the RC here, or will there be a new thread?

Chris

Posted: **Fri Dec 22, 2023 11:25 am**

Jerry3904 wrote: ↑Fri Dec 22, 2023 11:21 am OK, I tried to launch chromium in a terminal--and saw the same error message I sent you earlier about missing bluealsa, then a zillion repeats about "failure to get fd for plane" and "no export buffer to dma_buf: no such file or directory."

Much less important: pls change the desktop icon for the YT vid to a recognizable video icon such as /usr/share/icons/Papirus/24x24/mimetypes/video-mp4.svg

that message comes up no matter what, even when chromium launches. red herring. its just checking for old bluetooth libraries and its part of rpi's modifications of the package if I read the forums correctly.

so reboot and see if chromium launches.

Posted: **Fri Dec 22, 2023 11:28 am**

chrispop99 wrote: ↑Fri Dec 22, 2023 11:24 am Should we report testing for the RC here, or will there be a new thread?

Chris

lets keep it here for a bit, mostly because I'm not sure I want to even announce/release it with the chromium issue.

Posted: **Fri Dec 22, 2023 11:35 am**

I'm still seeing the cursor flicker with Conky active, and I've noticed that even with Conky off, there is some flicker when hovering over links in Chromium.

Chris

Posted: **Fri Dec 22, 2023 11:42 am**

On my 1920*1200 monitor, the panel clock is still truncated. The panel needs to be 40 pixels wide as a minimum, but 42 is better.

Chris

Posted: **Fri Dec 22, 2023 12:00 pm**

OK, the reboot worked fine.

I've attached that alternate icon for the vid

Posted: **Fri Dec 22, 2023 12:07 pm**

I'll be back in an hour or so...

Posted: **Fri Dec 22, 2023 12:18 pm**

We can just freeze this until after New Year's if people would like to.

The video is now live but I don't think that matters.

Posted: **Fri Dec 22, 2023 12:42 pm**

Thanks, the video is great and very informative.
:)

Posted: **Fri Dec 22, 2023 12:58 pm**

Thanks for the positive feedback!

Posted: **Sat Dec 23, 2023 8:16 am**

A bit bored early this morning when it's cold and gray, and no one is up yet; so I decided to see to what extent using MXPI to install KDE would work. I'm not a KDE person, but it certainly looks good. On the basic desktop I found only one non-functional component--a task manager, I gather. My Pi 5 8G had no trouble handling what I looked at quickly, and I imagine a Pi 4 8G would do fine as well; not sure about a Pi 400. I'd be really interested in hearing what actual KDE-users who own a Pi think, especially of course @Adrian.

(I hadn't really thought much about this project enabling the other versions, though I did look earlier at Fluxbox and found that with a bit of work on my part it would be normal.)

Posted: **Sat Dec 23, 2023 8:45 am**

What really needs fixed is the chromium first startup. Enough chromium process start that you would think the browser is running but there is one hung process that doesn’t do anything when the problem occurs and it shows up as chromium-browse when watching processes in htop. Killing that process does not let chromium launch and so far I have no remedy except a reboot. Logout login is not enough. . (Not browser, not a typo).

Posted: **Sat Dec 23, 2023 9:02 am**

Agreed. Doesn't happen on RPi OS so nothing showed up in a search there.

In your RC work it looks like you made some changes in the first boot sequence or I'm imagining things. Was there something there that might be affecting this?

I want to look at an upgraded b2 to check--thinking of an incremental upgrade.

Posted: **Sat Dec 23, 2023 9:46 am**

Went through an incremental upgrade from a clean b2, found this interesting

--chromium, no change
--pipewire and the other pipe stuff, no change
--sh--chromium hung, saw the error message I've reported before
--rest

Don't know enuf to tell if that is relevant or not

Posted: **Sat Dec 23, 2023 9:57 am**

does rpiOS ship with chromium?

Posted: **Sat Dec 23, 2023 9:58 am**

Posted: **Sat Dec 23, 2023 10:09 am**

version recently updated: 120.0.6099.102-rpt1

Posted: **Sat Dec 23, 2023 10:15 am**

To finish my incremental process: set up the splash, all good.

Posted: **Sat Dec 23, 2023 10:16 am**

Nice Youtube video!

Posted: **Sat Dec 23, 2023 10:17 am**

Thanks.

Posted: **Sat Dec 23, 2023 10:27 am**

Since it works after a reboot, I would expect incremental upgrade also work

The only changed to the initial bootup sequence is the addition of the splash

Posted: **Sat Dec 23, 2023 10:42 am**

I'm out for a couple, family stuff.

Posted: **Sat Dec 23, 2023 10:56 am**

chromium data point: you don't actually have to start chromium before a reboot does any good. upon an immediate reboot from desktop, chromium starts right up the first time.

Posted: **Sat Dec 23, 2023 11:19 am**

chromium data point: splash enabled or disabled doesn't matter.

Posted: **Sat Dec 23, 2023 12:42 pm**

next data point: launching chromium the first time using the basic password store intead of the defualt keyring works.

so I'm kind of leaning towards something wrong with the keyring rather than chromium, either with the display of the keyring prompt, or the actual keyring itself on first login.

Posted: **Sat Dec 23, 2023 12:47 pm**

That's interesting, wasn't even on my radar. Wonder what RPi OS is using--over I go.

EDIT: gnome-keyring and raspberrypi-archive-keyring

Posted: **Sat Dec 23, 2023 1:01 pm**

both are installed. and work after a reboot.

raspberrypi-archive-keyring is the apt keys.

Posted: **Sat Dec 23, 2023 3:40 pm**

restarting the gnome-keyring-daemon with

Code: Select all

gnome-keyring-daemon --replace

is enough to keep chromium launching.

So I'm surmising that there is some setup step that needs done after the user is logged in that might not be occurring. will investigate options, but I think light is at the end of the tunnel.

Posted: **Sat Dec 23, 2023 3:43 pm**

Good sleuthing, I'm starting to hope. Weird that is showed up so late in Development.

Posted: **Sat Dec 23, 2023 5:25 pm**

Jerry3904 wrote: ↑Sat Dec 23, 2023 3:43 pm Good sleuthing, I'm starting to hope. Weird that is showed up so late in Development.

didn't switch to chromium until relatively late. and even then, I wasn't usually launching the web browser on the first boot until we added the video link. just glad you mentioned it.

Posted: **Sat Dec 23, 2023 5:28 pm**

Me too. A bit of serendipity always makes Development go round, huh?

Posted: **Sat Dec 23, 2023 5:33 pm**

might actually be some kind of conflict, although not sure why it would only affect first boot. got some additional experimenting to do.

Posted: **Sat Dec 23, 2023 8:47 pm**

Some suggestions:

* add and enable to adduser.conf the extra_groups,
so newly added user, gain more functionality, otherwise with only beeing in the users-group
may create some confusions for those new user.

* maybe add default locale/keyboard to en_US/us, so user see the default inthe oem-minstaller,
in case it was not intentially left out.

* perhaps disable gnome-keyring in auto-start,
but do enable gnome-keyring-daemon.service as user-service instead.
This might help pam to unlock the newly created login-keyring.
at least in theory...
...
ttfn

Posted: **Sat Dec 23, 2023 10:25 pm**

fehlix wrote: ↑Sat Dec 23, 2023 8:47 pm Some suggestions:

* add and enable to adduser.conf the extra_groups,
so newly added user, gain more functionality, otherwise with only beeing in the users-group
may create some confusions for those new user.

will check this, thought I had our usual adduser.conf included. --edit-- somewhere along the way I lost it, thanks.

* perhaps disable gnome-keyring in auto-start,
but do enable gnome-keyring-daemon.service as user-service instead.
This might help pam to unlock the newly created login-keyring.
at least in theory...

I did try that, but there was no help.

Posted: **Sun Dec 24, 2023 8:13 am**

Jerry3904 wrote: ↑Sat Dec 23, 2023 8:16 am A bit bored early this morning when it's cold and gray, and no one is up yet; so I decided to see to what extent using MXPI to install KDE would work. I'm not a KDE person, but it certainly looks good. On the basic desktop I found only one non-functional component--a task manager, I gather. My Pi 5 8G had no trouble handling what I looked at quickly, and I imagine a Pi 4 8G would do fine as well; not sure about a Pi 400. I'd be really interested in hearing what actual KDE-users who own a Pi think, especially of course @Adrian.

(I hadn't really thought much about this project enabling the other versions, though I did look earlier at Fluxbox and found that with a bit of work on my part it would be normal.)

Hi:
I installed Fluxbox and it consumes much less memory than Xfce of course, but it seems to work fine

Posted: **Sun Dec 24, 2023 8:17 am**

<off topic>
It does work fine, there's just a couple of things missing such as the gkrellm themes. Let's postpone further discussion of this (my bad) until we get Final out.
<back on topic>

Posted: **Sun Dec 24, 2023 8:25 am**

fehlix wrote: ↑Sat Dec 23, 2023 8:47 pm Some suggestions:

* add and enable to adduser.conf the extra_groups,
so newly added user, gain more functionality, otherwise with only beeing in the users-group
may create some confusions for those new user.

* maybe add default locale/keyboard to en_US/us, so user see the default inthe oem-minstaller,
in case it was not intentially left out.

* perhaps disable gnome-keyring in auto-start,
but do enable gnome-keyring-daemon.service as user-service instead.
This might help pam to unlock the newly created login-keyring.
at least in theory...
...
ttfn

Hi:
In the normal MX installation, in this part you see the default language en_us.
But in RC1 it comes out empty, you can add any language without problems with the correction that was made at the time, I could add my Spanish language and keyboard well, but it is strange that this empty.
Best regards

Posted: **Sun Dec 24, 2023 10:15 am**

I have an rc2 brewing with the adduser.conf and /etc/default/keyboard changes, as well as what is at least a work around for the chromium startup issue. On first login, there will be a forced restart of the gnome-keyring-daemon. this is mostly invisible to users, but they will get a keyring prompt if they launch chromium on first login, no matter if they autologin or not, but only on the very first login of the user.

Posted: **Sun Dec 24, 2023 10:33 am**

Good to hear. Anxious to test it...

Posted: **Sun Dec 24, 2023 2:29 pm**

RC2 up in about half an hour.

Posted: **Sun Dec 24, 2023 3:31 pm**

I see it--now downloading.

Thanks for all the work!

Posted: **Sun Dec 24, 2023 3:54 pm**

Only able to do a brief sanity check - next couple of days here in the UK get taken over a bit - but it looks great. The issues I was seeing are all fully resolved. Great work @Jerry3904 and @dolphin_oracle !

Chris

Posted: **Sun Dec 24, 2023 5:02 pm**

I totally agree! The workaround is nearly invisible and removes the problem. I appreciate the change in desktop icons.

Final thoughts
1) would like to see us consider one last time removing shortened desktop icon captions to give this very clear setup.

fullicontitles.png

2) think we might want to speak directly to localization, since the choices are embedded and small on the Installer. Maybe right in the Announcement would be good, and I can add a section to the Tips document adding the methods (RPi and Tools) of changing once installed. Along that line of thinking, I would like to point to rc-config, wondering if it would be better eventually to use that for the menu entry we have for R P Configuration:

rc-config.png

Otherwise, IMO, as Bugs Bunny always said: That's it, folks!

Posted: **Mon Dec 25, 2023 12:06 pm**

dolphin_oracle wrote: ↑Sat Dec 23, 2023 10:25 pm
* perhaps disable gnome-keyring in auto-start,
but do enable gnome-keyring-daemon.service as user-service instead.
This might help pam to unlock the newly created login-keyring.
at least in theory...
I did try that, but there was no help.

OK, this works here:

To unlock gnome-keyring automatically at user login with password (not with auto-login):

* masks both user-services :
gnome-keyring-daemon.service
and
gnome-keyring-daemon.socket

* remove from autostart the temp-workaround zz-restart-gnome-keyring-1-time.desktop

Tested this way
First mounted mounted mx23.1_rc2_rpi.img writable
with
gnome-disk-image-mounter -w mx23.1_rc2_rpi.img
and
mounted rootfs from mx23.1_rc2_rpi.img at /media/fehlix/rootfs

Next:
Created two systemd user masks:
sudo mkdir -p /media/fehlix/rootfs/etc/skel/.config/systemd/user
sudo ln -s /dev/null /media/fehlix/rootfs/etc/skel/.config/systemd/user/gnome-keyring-daemon.service
sudo ln -s /dev/null /media/fehlix/rootfs/etc/skel/.config/systemd/user/gnome-keyring-daemon.socket

and removed zz-restart-gnome-keyring-1-time.desktop
sudo rm /media/fehlix/rootfs/etc/skel/.config/autostart/zz-restart-gnome-keyring-1-time.desktop

Now unmounted,
and wrote the image to an USB-stick, with help of BitJam's image writer:

Code: Select all

sudo dd-live-usb -f  mx23.1_rc2_rpi.img

Booted now with this USB-stick from a Raspberry PI 400.
Success Login keyring unlocked after login at the Lightdm login screen.
Also any newly created user, will immediately get the keyring unlocked
after user creation and logout login to the new user.
Suggest to get this onto the release image.
Thanks

Posted: **Mon Dec 25, 2023 12:42 pm**

Thanks for working through this, @fehlix!

Posted: **Mon Dec 25, 2023 12:51 pm**

BTW: I noticed when running a search for "Raspberry" in synaptic that the package rpi-chromium-mods is not installed, has in the comment "Pi-specific modifications." Did we ever look at that?

I'm going to install it this week and try to see what those patches are doing.

Posted: **Mon Dec 25, 2023 2:01 pm**

fehlix wrote: ↑Mon Dec 25, 2023 12:06 pm
dolphin_oracle wrote: ↑Sat Dec 23, 2023 10:25 pm
* perhaps disable gnome-keyring in auto-start,
but do enable gnome-keyring-daemon.service as user-service instead.
This might help pam to unlock the newly created login-keyring.
at least in theory...
I did try that, but there was no help.
OK, this works here:

To unlock gnome-keyring automatically at user login with password (not with auto-login):

* masks both user-services :
gnome-keyring-daemon.service
and
gnome-keyring-daemon.socket

* remove from autostart the temp-workaround zz-restart-gnome-keyring-1-time.desktop

Tested this way
First mounted mounted mx23.1_rc2_rpi.img writable
with
gnome-disk-image-mounter -w mx23.1_rc2_rpi.img
and
mounted rootfs from mx23.1_rc2_rpi.img at /media/fehlix/rootfs

Next:
Created two systemd user masks:
sudo mkdir -p /media/fehlix/rootfs/etc/skel/.config/systemd/user
sudo ln -s /dev/null /media/fehlix/rootfs/etc/skel/.config/systemd/user/gnome-keyring-daemon.service
sudo ln -s /dev/null /media/fehlix/rootfs/etc/skel/.config/systemd/user/gnome-keyring-daemon.socket

and removed zz-restart-gnome-keyring-1-time.desktop
sudo rm /media/fehlix/rootfs/etc/skel/.config/autostart/zz-restart-gnome-keyring-1-time.desktop

Now unmounted,
and wrote the image to an USB-stick, with help of BitJam's image writer:
Code: Select all
sudo dd-live-usb -f  mx23.1_rc2_rpi.img
Booted now with this USB-stick from a Raspberry PI 400.
Success Login keyring unlocked after login at the Lightdm login screen.
Also any newly created user, will immediately get the keyring unlocked
after user creation and logout login to the new user.
Suggest to get this onto the release image.
Thanks

I thought about doing it that way. It’s essentially the way it works on sysvinit. Will make the adjustment.

Posted: **Mon Dec 25, 2023 2:43 pm**

@fehlix keeping in mind that the pi uses systemd do we have any issues with missing sockets this way.

Posted: **Mon Dec 25, 2023 3:47 pm**

dolphin_oracle wrote: ↑Mon Dec 25, 2023 2:43 pm @fehlix keeping in mind that the pi uses systemd do we have any issues with missing sockets this way.

The socket /run/user/$UID/keyring/control used by gnome-keyring's secrets
seems to get created by gnome-keyring-daemon itself, if not exists.
Not sure why systemd thinks to need all and every socket created by it's own.

Posted: **Mon Dec 25, 2023 3:51 pm**

fehlix wrote: ↑Mon Dec 25, 2023 3:47 pm
dolphin_oracle wrote: ↑Mon Dec 25, 2023 2:43 pm @fehlix keeping in mind that the pi uses systemd do we have any issues with missing sockets this way.
The socket /run/user/$UID/keyring/control used by gnome-keyring's secrets
seems to get created by gnome-keyring-daemon itself, if not exists.
Not sure why systemd thinks to need all and every socket created by it's own.

Ok good

Posted: **Mon Dec 25, 2023 6:01 pm**

Hmm, seems machine-id get's not re-generated during oobe-install as it always is the same as on the image.
Suggest to have dbus-uuidgen call also somwehre added to oobe.cpp, and not only on the normal mx-installer part.
Otherwise I guess systemd related local network activities might get confused with two identical machine-id's.
Probably an easy one.

Another point is about the FS-UUID for the ext4 partition, which is not change and taken from the image,
which creates confusion, eg. if some plugs-in a 2nd USB with the image, b/c two identical UUID cannot be handled by the kernel properly, and would make one partition invisible
Probably a bit more involved, as we cannot run uuid-generation during the oobe-installer b/c it's already mounted.
So somewhere to inject in the early expansion phase of the image during first boot.

MX Linux Forum

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing

Re: MX-23 Rpi Respin -- Beta testing