Racy Resurrector

[rockedge]

I believe the private window is a separate instance of the browser which can be opened and does not record any history of browsing within that instance.

[mikewalsh]

I think I've found it. The palemoon.desktop is in /share/applications and not /usr/share/applications! It shows

Code: Select all

Exec=palemoon -private-window

What is a private window?

Ken.

Okay, the path of the desktop entry has been changed with this version, this is also the reason why it is not showing in the Racy menu. Copy the desktop entry to /usr/share/applications. Does palemoon run when you click the desktop entry? Private window is just a special mode of browsing. You can start palemoon without that switch.

Whoah, whoah, whoah, guys. "/share/applications"??? Where are you getting this from?

I download the newest build from Steve's repo, extract it, and the .desktop entry is under /usr/share/applications, as expected. I'm not seeing a "/share" directory at all; if such existed, it would be at the top level under "/". And that's something I've never, ever seen, because it's not part of the Linux file-system structure, now is it?

Mike.

[amethyst]

I think I've found it. The palemoon.desktop is in /share/applications and not /usr/share/applications! It shows

Code: Select all

Exec=palemoon -private-window

What is a private window?

Ken.

Okay, the path of the desktop entry has been changed with this version, this is also the reason why it is not showing in the Racy menu. Copy the desktop entry to /usr/share/applications. Does palemoon run when you click the desktop entry? Private window is just a special mode of browsing. You can start palemoon without that switch.

Whoah, whoah, whoah, guys. "/share/applications"??? Where are you getting this from?

I download the newest build from Steve's repo, extract it, and the .desktop entry is under /usr/share/applications, as expected. I'm not seeing a "/share" directory at all; if such existed, it would be at the top level under "/". And that's something I've never, ever seen, because it's not part of the Linux file-system structure, now is it?

Mike.

I can only go on what he is reporting Mike, I don't have that build. BTW - I read that you make the portable from the Xubuntu build, interesting to know that it works. Does seem to require extra libraries though, probably for the xfce desktop...

[keniv]

Whoah, whoah, whoah, guys. "/share/applications"??? Where are you getting this from?

I download the newest build from Steve's repo, extract it, and the .desktop entry is under /usr/share/applications, as expected. I'm not seeing a "/share" directory at all; if such existed, it would be at the top level under "/". And that's something I've never, ever seen, because it's not part of the Linux file-system structure, now is it?

Mike.

OK Mike, this is beginning to worry me now particularly in term of what you've said about it not being part of the Linux file system. I found this palemoon.desktop using pfind. Please look at image 1,2 and three below. I've also included the contents of the palemoon.desktop file.

Code: Select all

[Desktop Entry]
Name=Pale Moon
GenericName=Web Browser
GenericName[ar]=متصفح ويب
GenericName[ast]=Restolador Web
GenericName[bn]=ওয়েব ব্রাউজার
GenericName[ca]=Navegador web
GenericName[cs]=Webový prohlížeč
GenericName[da]=Webbrowser
GenericName[el]=Περιηγητής διαδικτύου
GenericName[es]=Navegador web
GenericName[et]=Veebibrauser
GenericName[fa]=مرورگر اینترنتی
GenericName[fi]=WWW-selain
GenericName[fr]=Navigateur Web
GenericName[gl]=Navegador Web
GenericName[he]=דפדפן אינטרנט
GenericName[hr]=Web preglednik
GenericName[hu]=Webböngésző
GenericName[it]=Browser web
GenericName[ja]=ウェブ・ブラウザ
GenericName[ko]=웹 브라우저
GenericName[ku]=Geroka torê
GenericName[lt]=Interneto naršyklė
GenericName[nb]=Nettleser
GenericName[nl]=Webbrowser
GenericName[nn]=Nettlesar
GenericName[no]=Nettleser
GenericName[pl]=Przeglądarka WWW
GenericName[pt]=Navegador Web
GenericName[pt_BR]=Navegador Web
GenericName[ro]=Navigator Internet
GenericName[ru]=Веб-браузер
GenericName[sk]=Internetový prehliadač
GenericName[sl]=Spletni brskalnik
GenericName[sv]=Webbläsare
GenericName[tr]=Web Tarayıcı
GenericName[ug]=توركۆرگۈ
GenericName[uk]=Веб-браузер
GenericName[vi]=Trình duyệt Web
GenericName[zh_CN]=网络浏览器
GenericName[zh_TW]=網路瀏覽器
Comment=Browse the World Wide Web
Comment[ar]=تصفح الشبكة العنكبوتية العالمية
Comment[ast]=Restola pela Rede
Comment[bn]=ইন্টারনেট ব্রাউজ করুন
Comment[ca]=Navegueu per la web
Comment[cs]=Prohlížení stránek World Wide Webu
Comment[da]=Surf på internettet
Comment[de]=Im Internet surfen
Comment[el]=Μπορείτε να περιηγηθείτε στο διαδίκτυο (Web)
Comment[es]=Navegue por la web
Comment[et]=Lehitse veebi
Comment[fa]=صفحات شبکه جهانی اینترنت را مرور نمایید
Comment[fi]=Selaa Internetin WWW-sivuja
Comment[fr]=Naviguer sur le Web
Comment[gl]=Navegar pola rede
Comment[he]=גלישה ברחבי האינטרנט
Comment[hr]=Pretražite web
Comment[hu]=A világháló böngészése
Comment[it]=Esplora il web
Comment[ja]=ウェブを閲覧します
Comment[ko]=웹을 돌아 다닙니다
Comment[ku]=Li torê bigere
Comment[lt]=Naršykite internete
Comment[nb]=Surf på nettet
Comment[nl]=Surf op het internet
Comment[nn]=Surf på nettet
Comment[no]=Surf på nettet
Comment[pl]=Przeglądanie stron WWW
Comment[pt]=Navegue na Internet
Comment[pt_BR]=Navegue na Internet
Comment[ro]=Navigați pe Internet
Comment[ru]=Доступ в Интернет
Comment[sk]=Prehliadanie internetu
Comment[sl]=Brskajte po spletu
Comment[sv]=Surfa på webben
Comment[tr]=İnternet'te Gezinin
Comment[ug]=دۇنيادىكى توربەتلەرنى كۆرگىلى بولىدۇ
Comment[uk]=Перегляд сторінок Інтернету
Comment[vi]=Để duyệt các trang web
Comment[zh_CN]=浏览互联网
Comment[zh_TW]=瀏覽網際網路
Exec=palemoon %u
Terminal=false
Type=Application
Icon=palemoon
Categories=Network;WebBrowser;
MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;x-scheme-handler/ftp;
StartupNotify=false
Actions=NewTab;NewWindow;NewPrivateWindow;
StartupWMClass=Pale moon

[Desktop Action NewTab]
Name=Open new tab
Name[ach]=Yab dirica matidi manyen
Name[af]=Open nuwe oortjie
Name[an]=Ubrir una pestanya nueva
Name[ar]=افتح لسانًا جديدًا
Name[as]=নতুন টেব খোলক
Name[ast]=Abrir llingüeta nueva
Name[az]=Yeni vərəq aç
Name[be]=Адкрыць новую ўстаўку
Name[bg]=Отваряне на нов подпрозорец
Name[bn_BD]=নতুন ট্যাব খুলুন
Name[bn_IN]=নতুন ট্যাব খুলুন
Name[br]=Digeriñ un ivinell nevez
Name[bs]=Otvori novi tab
Name[ca]=Obre una pestanya nova
Name[cs]=Otevřít nový panel
Name[cy]=Agor tab newydd
Name[da]=Åbn nyt faneblad
Name[de]=Neuen Tab öffnen
Name[dsb]=Nowy rejtark wócyniś
Name[el]=Άνοιγμα νέας καρτέλας
Name[eo]=Malfermi novan langeton
Name[es_AR]=Abrir nueva pestaña
Name[es_CL]=Abrir nueva pestaña
Name[es_ES]=Abrir pestaña nueva
Name[es_MX]=Abrir una pestaña nueva
Name[et]=Ava uus kaart
Name[eu]=Ireki fitxa berria
Name[ff]=Uddit tabbere hesere
Name[fi]=Avaa uusi välilehti
Name[fr]=Ouvrir un nouvel onglet
Name[fy_NL]=Iepenje nij ljepblêd
Name[ga_IE]=Oscail i gcluaisín nua
Name[gd]=Fosgail taba ùr
Name[gl]=Abrir unha nova lapela
Name[gu_IN]=નવી ટૅબને ખોલો
Name[he]=פתיחת לשונית חדשה
Name[hi_IN]=नया टैब खोलें
Name[hr]=Otvori novu karticu
Name[hsb]=Nowy rajtark wočinić
Name[hu]=Új lap megnyitása
Name[hy_AM]=Բացել նոր ներդիր
Name[id]=Buka tab baru
Name[is]=Opna nýjan flipa
Name[it]=Apri nuova scheda
Name[ja]=新しいタブ
Name[kk]=Жаңа бетті ашу
Name[kn]=ಹೊಸ ಹಾಳೆಯನ್ನು ತೆರೆ
Name[ko]=새 탭 열기
Name[lij]=Àrvi nêuvo féuggio
Name[lt]=Atverti naują kortelę
Name[mai]=नव टैब खोलू
Name[mk]=Отвори ново јазиче
Name[ml]=പുതിയ റ്റാബ് തുറക്കുക
Name[mr]=नवीन टॅब उघडा
Name[ms]=Buka tab baru
Name[nb_NO]=Åpne ny fane
Name[nl]=Nieuw tabblad openen
Name[nn_NO]=Opna ny fane
Name[or]=ନୂତନ ଟ୍ୟାବ ଖୋଲନ୍ତୁ
Name[pa_IN]=ਨਵੀਂ ਟੈਬ ਖੋਲ੍ਹੋ
Name[pl]=Otwórz nową kartę
Name[pt_BR]=Nova aba
Name[pt_PT]=Abrir novo separador
Name[rm]=Avrir in nov tab
Name[ro]=Deschide o filă nouă
Name[ru]=Открыть новую вкладку
Name[si]=නව ටැබය විවෘත කරන්න
Name[sk]=Otvoriť novú kartu
Name[sl]=Odpri nov zavihek
Name[son]=Nor loku taaga feeri
Name[sq]=Hap skedë të re
Name[sr]=Отвори нови језичак
Name[sv_SE]=Öppna ny flik
Name[ta]=புதிய கீற்றைத் திற
Name[te]=కొత్త టాబ్ తెరువుము
Name[th]=เปิดแท็บใหม่
Name[tr]=Yeni sekme aç
Name[uk]=Відкрити нову вкладку
Name[uz]=Yangi ichki oyna ochish
Name[vi]=Mở thẻ mới
Name[xh]=Vula ithebhu entsha
Name[zh_CN]=打开新标签页
Name[zh_TW]=開啟新分頁
Exec=palemoon -new-tab https://start.palemoon.org

[Desktop Action NewWindow]
Name=Open new window
Name[ach]=Yab dirica manyen
Name[af]=Open nuwe venster
Name[an]=Ubrir una nueva finestra
Name[ar]=افتح نافذة جديدة
Name[as]=নতুন উইন্ডো খোলক
Name[ast]=Abrir ventana nueva
Name[az]=Yeni pəncərə aç
Name[be]=Адкрыць новае акно
Name[bg]=Отваряне на нов прозорец
Name[bn_BD]=নতুন উইন্ডো খুলুন
Name[bn_IN]=নতুন উইন্ডো খুলুন
Name[br]=Digeriñ ur prenestr nevez
Name[bs]=Otvori novi prozor
Name[ca]=Obre una finestra nova
Name[cs]=Otevřít nové okno
Name[cy]=Agor ffenestr newydd
Name[da]=Åbn nyt vindue
Name[de]=Neues Fenster öffnen
Name[dsb]=Nowe wokno wócyniś
Name[el]=Άνοιγμα νέου παραθύρου
Name[eo]=Malfermi novan fenestron
Name[es_AR]=Abrir nueva ventana
Name[es_CL]=Abrir nueva ventana
Name[es_ES]=Abrir nueva ventana
Name[es_MX]=Abrir nueva ventana
Name[et]=Ava uus aken
Name[eu]=Ireki leiho berria
Name[ff]=Uddit henorde hesere
Name[fi]=Avaa uusi ikkuna
Name[fr]=Ouvrir une nouvelle fenêtre
Name[fy_NL]=Iepenje nij finster
Name[ga_IE]=Oscail fuinneog nua
Name[gd]=Fosgail uinneag ùr
Name[gl]=Abrir unha nova xanela
Name[gu_IN]=નવી વિન્ડોને ખોલો
Name[he]=פתח חלון חדש
Name[hi_IN]=नई विंडो खोलें
Name[hr]=Otvori novi prozor
Name[hsb]=Nowe wokno wočinić
Name[hu]=Új ablak megnyitása
Name[hy_AM]=Բացել նոր պատուհան
Name[id]=Buka jendela baru
Name[is]=Opna nýjan glugga
Name[it]=Apri nuova finestra
Name[ja]=新しいウィンドウ
Name[kk]=Жаңа терезені ашу
Name[kn]=ಹೊಸ ವಿಂಡೊವನ್ನು ತೆರೆ
Name[ko]=새 창 열기
Name[lij]=Àrvi nêuvo barcón
Name[lt]=Atverti naują langą
Name[mai]=नई विंडो खोलू
Name[mk]=Отвори нов прозорец
Name[ml]=പുതിയ ജാലകം തുറക്കുക
Name[mr]=नवीन पटल उघडा
Name[ms]=Buka tetingkap baru
Name[nb_NO]=Åpne nytt vindu
Name[nl]=Een nieuw venster openen
Name[nn_NO]=Opna nytt vindauge
Name[or]=ନୂତନ ୱିଣ୍ଡୋ ଖୋଲନ୍ତୁ
Name[pa_IN]=ਨਵੀਂ ਵਿੰਡੋ ਖੋਲ੍ਹੋ
Name[pl]=Otwórz nowe okno
Name[pt_BR]=Nova janela
Name[pt_PT]=Abrir nova janela
Name[rm]=Avrir ina nova fanestra
Name[ro]=Deschide o nouă fereastră
Name[ru]=Открыть новое окно
Name[si]=නව කවුළුවක් විවෘත කරන්න
Name[sk]=Otvoriť nové okno
Name[sl]=Odpri novo okno
Name[son]=Zanfun taaga feeri
Name[sq]=Hap dritare të re
Name[sr]=Отвори нови прозор
Name[sv_SE]=Öppna nytt fönster
Name[ta]=புதிய சாளரத்தை திற
Name[te]=కొత్త విండో తెరువుము
Name[th]=เปิดหน้าต่างใหม่
Name[tr]=Yeni pencere aç
Name[uk]=Відкрити нове вікно
Name[uz]=Yangi oyna ochish
Name[vi]=Mở cửa sổ mới
Name[xh]=Vula iwindow entsha
Name[zh_CN]=打开新窗口
Name[zh_TW]=開啟新視窗
Exec=palemoon -new-window

[Desktop Action NewPrivateWindow]
Name=New private window
Name[ach]=Dirica manyen me mung
Name[af]=Nuwe privaatvenster
Name[an]=Nueva finestra de navegación privada
Name[ar]=نافذة خاصة جديدة
Name[as]=নতুন ব্যক্তিগত উইন্ডো
Name[ast]=Ventana privada nueva
Name[az]=Yeni məxfi pəncərə
Name[be]=Новае акно адасаблення
Name[bg]=Нов прозорец за поверително сърфиране
Name[bn_BD]=নতুন ব্যক্তিগত উইন্ডো
Name[bn_IN]=নতুন ব্যাক্তিগত উইন্ডো
Name[br]=Prenestr merdeiñ prevez nevez
Name[bs]=Novi privatni prozor
Name[ca]=Finestra privada nova
Name[cs]=Nové anonymní okno
Name[cy]=Ffenestr breifat newydd
Name[da]=Nyt privat vindue
Name[de]=Neues privates Fenster öffnen
Name[dsb]=Nowe priwatne wokno
Name[el]=Νέο παράθυρο ιδιωτικής περιήγησης
Name[eo]=Nova privata fenestro
Name[es_AR]=Nueva ventana privada
Name[es_CL]=Nueva ventana privada
Name[es_ES]=Nueva ventana privada
Name[es_MX]=Nueva ventana privada
Name[et]=Uus privaatne aken
Name[eu]=Leiho pribatu berria
Name[ff]=Henorde suturo hesere
Name[fi]=Uusi yksityinen ikkuna
Name[fr]=Nouvelle fenêtre de navigation privée
Name[fy_NL]=Nij priveefinster
Name[ga_IE]=Fuinneog nua phríobháideach
Name[gd]=Uinneag phrìobhaideach ùr
Name[gl]=Nova xanela privada
Name[gu_IN]=નવી ખાનગી વિન્ડો
Name[he]=חלון פרטי חדש
Name[hi_IN]=नया निजी विंडो
Name[hr]=Novi privatni prozor
Name[hsb]=Nowe priwatne wokno
Name[hu]=Új privát ablak
Name[hy_AM]=Գաղտնի դիտարկում
Name[id]=Jendela mode pribadi baru
Name[is]=Nýr einkagluggi
Name[it]=Nuova finestra anonima
Name[ja]=新しいプライベートウィンドウ
Name[kk]=Жаңа жекелік терезе
Name[kn]=ಹೊಸ ಖಾಸಗಿ ಕಿಟಕಿ
Name[ko]=새 사생활 보호 창
Name[lij]=Nêuvo barcón privòu
Name[lt]=Atverti privačiojo naršymo langą
Name[mai]=नव निज विंडो
Name[mk]=Нов прозорец за приватно сурфање
Name[ml]=പുതിയ സ്വകാര്യ ജാലകം
Name[mr]=नवीन वैयक्तिक पटल
Name[ms]=Tetingkap peribadi baharu
Name[nb_NO]=Nytt privat vindu
Name[nl]=Nieuw privévenster
Name[nn_NO]=Nytt privat vindauge
Name[or]=ନୂତନ ବ୍ୟକ୍ତିଗତ ୱିଣ୍ଡୋ
Name[pa_IN]=ਨਵੀਂ ਪ੍ਰਾਈਵੇਟ ਵਿੰਡੋ
Name[pl]=Nowe okno w trybie prywatnym
Name[pt_BR]=Nova janela privativa
Name[pt_PT]=Nova janela privada
Name[rm]=Nova fanestra privata
Name[ro]=Fereastră fără urme nouă
Name[ru]=Новое приватное окно
Name[si]=නව පුද්ගලික කවුළුව
Name[sk]=Nové okno v režime Súkromné prehliadanie
Name[sl]=Novo zasebno okno
Name[son]=Sutura zanfun taaga
Name[sq]=Dritare e re private
Name[sr]=Нови приватни прозор
Name[sv_SE]=Nytt privat fönster
Name[ta]=புதிய தனிப்பட்ட சாளரம்
Name[te]=కొత్త ఆంతరంగిక విండో
Name[th]=หน้าต่างท่องเว็บแบบส่วนตัวใหม่
Name[tr]=Yeni gizli pencere
Name[uk]=Нове приватне вікно
Name[uz]=Yangi shaxsiy oyna
Name[vi]=Cửa sổ riêng tư mới
Name[xh]=Ifestile yangasese entsha
Name[zh_CN]=新建隐私浏览窗口
Name[zh_TW]=新增隱私視窗
Exec=palemoon -private-window

It looks like a desktop file to me just containing many languages. Clicking on this does open palemoon 31.3.0.1, however, it is my intention to unload the palemoon-31.3.0.1.sfs and not use it again until I know it is safe to use.

I download the newest build from Steve's repo, extract it, and the .desktop entry is under /usr/share/applications

Can you give me a link to this build?

Regards,

Ken.

[mikewalsh]

@keniv :-

Oh, you've got all the right items there, Ken.....and they're all in the right directory (/share). But for some strange reason, you've got the /share directory under "/", when it SHOULD be under "/usr".

The .deb I'm talking about is the exact same one amethyst linked to, last post on page 2....

------------------------------

@amethyst :-

TBH, I'm not in the least surprised about the Xubuntu build, Nic. Given that the 'buntus tend to come with the full contents of the kitchen sink included, OOTB, it stands to reason that more stuff probably gets dragged-in at compile time.

And you could well be right about some of it being related to XFCE4. I wouldn't argue that point with anyone, 'cos fully-integrated DEs in general are a complete mystery to me..!

Mike.

[mikeslr]

@ keniv, from your description all you did was unpack and repack. [By the way, sometimes UExtracts reports failure when it actually succeeded. Always look in the extraction folder before discarding it.] I don't know why the original publisher might have created that folder, but if there really was a Top-level share folder containing the desktop file I wouldn't be overly concerned. Linux is flexible until some decides to restrict it.

Puppys have had a /root/my-applications folder with /bin and /lib subfolders since (almost?) day one. It's not 'Linux-Standard'. When google decided it didn't want users to 'run-as-root', the initial work-around developed by the FatDog Team and used by MikeWalsh in his builds was to create a Top-Level 'Home' folder (containing a Spot sub-folder). After decades of independents creating applications which located binaries in the Top-level /bin folder, debian and Ubuntu decided to prevent their operating systems from looking there except for distro-authorized executables. But debian/ubuntu don't know about Puppy's /my-applications/bin folder: so binaries and executables located there are still found by (for example) VanillaDpup while those in /bin won't be.

The real 'got-yah' is that when something is located where your operating system isn't constructed to look for it, your operating system won't. /usr/share/applications is the 'standard' place to locate 'desktop' files: where the application which generates the Menu looks. But I've seen pets build which located desktop files in /usr/local/share. [Puppy could find those; but AppFinder which uses a non-puppy application, can't]. LibreOffice locates desktop files in /opt/LibreOffice/share/xdg; but creates a symlink to it in /usr/share/applications.

So, you actually had a couple of options. Copy, move or symlink to /usr/share/applications.

[mikewalsh]

@mikeslr :-

TBH, I tend to agree with you on this one.

Although most of us know what the 'standard' Linux file-system layout is like by now, there's nothing to say that you can't place files/directories in non-standard locations. From what I recall, amethyst's own package for the Opera Mini browser + Java emulator places a directory for the micro-emulator under "/". And I have myself used /usr/share for locating random older browser build directories, where I didn't want them interfering with similarly-named browsers in the 'standard' locations.

(Same goes for the 'portable' applications. Since they're completely self-contained, it makes no difference at all where you put them.)

You CAN do stuff like this in Linux. Perhaps Windoze allows this sort of behaviour, but I wouldn't like to say. I don't think it has "user" folders as such, does it?

Mike.

[keniv]

OK I've copied and edit the file/share/applications palemoon.desktop (mainly removed all the extra languages). I've placed it in /usr/share/applications. I've also copied the icon to /usr/share/icons. I've have had to make a desktop launcher as palemoon does not appear in the menu. I've tried fixmenus and rebooting but to no avail. I also could not find load-sfs in the menu even although it was shown to be installed in the ppm. There was also a .desktop file for it. I decided to uninstall it then reinstalled it but again no menu entry. Again I've made a desktop launcher for this. So I still have a number of things that don't seem to work properly. They are as follows.
1. Menus (as described above)
2. Thumbnails These don't appear. I've right-clicked on File>Rox-Filer>Options>Thumbnails and ticked the Show Image Thumbnail box but this makes no difference.
3. On booting up each time I get to Updating Layered File System I see "Next Boot Will Be Faster" every time rather than just the first time.
4. I have pwidgets installed. I have moved the Lock, Zip and Trash on-screen icons to accommodate this. Each time I reboot they have returned to their original position or are piled on top of each other. I have dun this in the past without encountering this problem.
Does anybody have any idea as to how to fix any of these?

Regards,

Ken.

[amethyst]

OK I've copied and edit the file/share/applications palemoon.desktop (mainly removed all the extra languages). I've placed it in /usr/share/applications. I've also copied the icon to /usr/share/icons. I've have had to make a desktop launcher as palemoon does not appear in the menu. I've tried fixmenus and rebooting but to no avail. I also could not find load-sfs in the menu even although it was shown to be installed in the ppm. There was also a .desktop file for it. I decided to uninstall it then reinstalled it but again no menu entry. Again I've made a desktop launcher for this. So I still have a number of things that don't seem to work properly. They are as follows.
1. Menus (as described above)
2. Thumbnails These don't appear. I've right-clicked on File>Rox-Filer>Options>Thumbnails and ticked the Show Image Thumbnail box but this makes no difference.
3. On booting up each time I get to Updating Layered File System I see "Next Boot Will Be Faster" every time rather than just the first time.
4. I have pwidgets installed. I have moved the Lock, Zip and Trash on-screen icons to accommodate this. Each time I reboot they have returned to their original position or are piled on top of each other. I have dun this in the past without encountering this problem.
Does anybody have any idea as to how to fix any of these?

Regards,

Ken.

1. When you change menu entries, run fixmenus AND restart JWM. In some cases it's actually necessary to restart x server with these old Puppys. The Palemoon sfs that I load (I don't install big stuff) does show a menu entry but without an icon. Providing the correct icon path in the desktop file may fix this. Not all installed files have desktop entries. There is not a desktop file for sfs_load, you have to create one yourself if you want it as a menu entry.
2. Yes, this is one of the major issues I have encountered with this old Puppy running much updated glibc (which is a miracle all in itself that it can handle it). There is a workaround (partially) that works for me although it may only be a temporary solution. Here is a link for a much older glibc package: https://mega.nz/#!oWo2yaTL!gikpPX2dFsc9 ... s6gutr4PJE. Load this as the bdrv instead of the newer bdrv, see if you can get the thumbnails displayed (most but not all seem to appear for me) and save your settings. Now reboot again with the newer bdrv. It should read from the saved thumbnail cache. But this will not be a permanent solution because any new images which are not in the cache will not display, I think (then you will have to go through the workaround process again). This is one of those issues that is what it is with this old Puppy and new glibc.
3. I don't use a savefile/folder but have seen this before with other Puppys, it's not unique. The bootup time is slightly longer but there are no other ill effects.
4. Don't know if it is a solution but try the different icon layout options (the custom choice perhaps). Run JWMDesk Manager and click the Icon Layout tab.

[keniv]

@mikewalsh

Oh, you've got all the right items there, Ken.....and they're all in the right directory (/share). But for some strange reason, you've got the /share directory under "/", when it SHOULD be under "/usr".

The .deb I'm talking about is the exact same one amethyst linked to, last post on page 2....

Thanks for that Mike. I thought perhaps it was a different .deb.

@mikeslr

from your description all you did was unpack and repack. [By the way, sometimes UExtracts reports failure when it actually succeeded. Always look in the extraction folder before discarding it.] I don't know why the original publisher might have created that folder, but if there really was a Top-level share folder containing the desktop file I wouldn't be overly concerned. Linux is flexible until some decides to restrict it.

I feel a bit less concerned now about this stuff being in the wrong place and have reloaded the .sfs.

So, you actually had a couple of options. Copy, move or symlink to /usr/share/applications.

Think I've sorted this out now. See further down the post.

@amethyst

1. When you change menu entries, run fixmenus AND restart JWM. In some cases it's actually necessary to restart x server with these old Puppys. The Palemoon sfs that I load (I don't install big stuff) does show a menu entry but without an icon. Providing the correct icon path in the desktop file may fix this. Not all installed files have desktop entries.

I copied the palemoon.png icon /usr/share/icons and set this as the path in the palemoon.desktop file and palemoon now appears in the menu with it's icon.

There is not a desktop file for sfs_load, you have to create one yourself if you want it as a menu entry.

Yes it is now there but it's in Setup.

2. Yes, this is one of the major issues I have encountered with this old Puppy running much updated glibc (which is a miracle all in itself that it can handle it). There is a workaround (partially) that works for me although it may only be a temporary solution. Here is a link for a much older glibc package: https://mega.nz/#!oWo2yaTL!gikpPX2dFsc9 ... s6gutr4PJE. Load this as the bdrv instead of the newer bdrv, see if you can get the thumbnails displayed (most but not all seem to appear for me) and save your settings. Now reboot again with the newer bdrv. It should read from the saved thumbnail cache. But this will not be a permanent solution because any new images which are not in the cache will not display, I think (then you will have to go through the workaround process again). This is one of those issues that is what it is with this old Puppy and new glibc.

I've tried this several times. When I change to the older glibc all of the thumbnail appear. However when I revert back to the new bdrv the thumbnails are lost again. I've tried unticking then reticking the box in File>Rox-Filer>Options>Thumbnails and clicking OK but none of this works.

3. I don't use a savefile/folder but have seen this before with other Puppys, it's not unique. The bootup time is slightly longer but there are no other ill effects.

OK, glad there are no ill effects.

4. Don't know if it is a solution but try the different icon layout options (the custom choice perhaps). Run JWMDesk Manager and click the Icon Layout tab.

Tried your suggestion using JWMDesk Manager and making a custom save. It seems to work but when I reboot these icons have moved again. I also tried moving the pwidgets display down the screen and moved these three icons to the top of the screen again made a custom save but again after a reboot they have moved.
So have had a little success but still have problems.

Regards,

Ken.

[amethyst]

I've tried this several times. When I change to the older glibc all of the thumbnail appear. However when I revert back to the new bdrv the thumbnails are lost again. I've tried unticking then reticking the box in File>Rox-Filer>Options>Thumbnails and clicking OK but none of this works.

Did you save your session after using the old glibc? The /root/.thumbnails folder should be occupied (check this immediately after the reboot with the new glibc). Do not untick and then later on tick the box again as this will clear the cache and try to rebuild it (which is not going to happen with the new glibc). As mentioned, the method is a temporary "solution". Racy has this thumbnail issue with all glibc versions newer than version 2.20. BTW - You can use that old glibc (version 2.20 which is still much newer as the glibc with which the original Racy was released) but then you will not be able to run the very latest spanking new Palemoon. You should be able to run up to version 29. I've used version29.1 until very recently, it's not too old (the last 29 version is less than a year old). Your choice - newest browser with thumbnail restrictions or thumbnails working correctly but older browser.

[amethyst]

It will be interesting to know the latest kernel that will work with this Puppy. I'm sure this is hardware related. On my old laptop the kernels of Tahr Puppy (3.14.56) and Xenial Puppy (4.4.95) works well. Others I have tried, boot to desktop without issues but the mouse and keyboard are dead (can't fix it even when booting up with pfix=nox). So if someone can try the kernel here https://archive.org/download/Puppy_Linu ... ae.tar.bz2 and report back, will be useful.
Edit: I've tried kernel 5.4.158 on another machine and it works. So depending on your hardware you can run a recent kernel with this Puppy.
Having lots of fun with this Puppy running the latest Palemoon browser,etc. A magical feeling working with a Puppy with the base sfs compressed to 53MB. Now that is what I would call a thoroughbred, classic Puppy with a power punch.

[keniv]

@amethyst

The /root/.thumbnails folder should be occupied (check this immediately after the reboot with the new glibc). Do not untick and then later on tick the box again as this will clear the cache and try to rebuild it (which is not going to happen with the new glibc). As mentioned, the method is a temporary "solution".

I tried the method you suggested in an earlier to get the thumbnails working but this time when using the bdrv containing glibc 2.20 I also checked the contents of the folder
/.thumbnails/normal. There were 749 thumbnails which were showing as properly. I made a copy of /.thumbnails/normal. After removing the old bdrv and reinstalling the new bdvr I found the original method had failed again for me. However, when I replaced /.thumbnails/normal with the .thumbnails/normal using the old bdvr the thumbnails did appear. I'm not sure if this will last and I am aware that any new thumbnails will not appear unless I go through this again. I also have a solution for the trash, zip and lock icons not staying in position on the desktop.
Now I have found that when I plug in a usb flash drive it does not appear to be seen. I would be interested to know if anybody else has seen this.

Regards,

Ken.
Edit1: Have checked the usb drives and they are working. Tried again and found that the usb drives could be mounted and unmounted using "Mount" though no drive icon appears on the desktop.
Edit2: Found that the thumbnails solution does not persist on rebooting.

[amethyst]

Important Pup Event update. See first post.

[amethyst]

I made a copy of /.thumbnails/normal.

That won't work because the configuration is saved in other files. Just save the session after you have loaded the old glibc and got the thunmbnails to show (you do have a working save file, I presume)...and then boot with the new glibc. After the reboot go to /usr/local/lib/X11/pixmaps and see if it shows. I do not experience your usb flashdrive issue.

[keniv]

@amethyst
I've now tried your thumbnail work around many times and although I see the thumbnails using the old bdrv there is no persistence when I change to the new bdrv as I have described before. I am pretty sure I'm doing exactly what you suggest and have not made errors. It just does not work for me. I have found that when I use the old bdrv all the problems I'm currently having disappear i.e. thumbnails work, desktop icons stay in place from one boot to the next, When I plug in a usb drive it's icon appears on the screen and it can be mounted and unmounted from there. Also with the new bdrv pmcputemp through up an error and did not work. With the old bdrv this now works again.
I've decided to stick with the old bdrv. Although this prevents me using palemoon 31.3.0.1 as an .sfs it does not prevent me using Mikewalsh's portable palemoon 31.3.0.1 which I'm posting from now. I think the new bdrv version was just too broken for someone like me, with my very limited knowledge, to get to work in a usable way. I might still continue to fiddle though.

Regards,

Ken.

[amethyst]

@amethyst
I've now tried your thumbnail work around many times and although I see the thumbnails using the old bdrv there is no persistence when I change to the new bdrv as I have described before. I am pretty sure I'm doing exactly what you suggest and have not made errors. It just does not work for me. I have found that when I use the old bdrv all the problems I'm currently having disappear i.e. thumbnails work, desktop icons stay in place from one boot to the next, When I plug in a usb drive it's icon appears on the screen and it can be mounted and unmounted from there. Also with the new bdrv pmcputemp through up an error and did not work. With the old bdrv this now works again.
I've decided to stick with the old bdrv. Although this prevents me using palemoon 31.3.0.1 as an .sfs it does not prevent me using Mikewalsh's portable palemoon 31.3.0.1 which I'm posting from now. I think the new bdrv version was just too broken for someone like me, with my very limited knowledge, to get to work in a usable way. I might still continue to fiddle though.

Regards,

Ken.

The bdrv containing newer glibc than version 2.20 is not broken, it's a system limitation of Racy. Besides, the bdrv is in read-only format so can't be altered without physically editing the contents. I've dropped the newer glibc in other Puppys (newer than Racy, like Precise Extra) and do not have this issue with the thumbnails. BTW - The workaround works for me so one last question: Are you absolutely sure that you save your changes after using the old glibc? Anyways, personally I would select using a newer browser anytime over eye candy like thumbnails. Thumbnails also slow your machine down (ROX is slower) compared to when it is switched off. I do not encounter a problem with pmcputemp nor the other issues you are reporting so can't assist there. If you are into checking out old Puppys, you may be interested in Precise Extra. You may experience fewer issues.

[mikewalsh]

@amethyst :-

The Racy "limitation" may be due to the way it was built, Nic. I can't be certain, but I think Racy was about the final Puppy to use the older T2 build-system. Precise, of course, was already using Woof, before it then became Woof-CE with the release of the 6-series Pups....

(Barry may have modified certain key system scripts when he was building Wary & Racy. Or, the newer glibc may simply no longer support certain older items, due to being compiled against newer dependencies in the first place. No telling, though I'm inclined to believe the latter has something to do with it. I think with 2.30+ you're definitely getting beyond any possibility of guaranteed 100% compatibility with a Puppy of that vintage.)

Mike.

[AntonioPt]

Just to let you all know that i was able to run Racy in a old pc Petium M and HP Dv9000 but without internet lol i could connect to my router but still no web lol beside that was fun to play with it I may open it again but just for fun since its old

[amethyst]

@keniv
Are you saying that you are using the older glibc 2.20 and then running mike's portable to use the latest Palemoon? If so, that may be a silghtly better solution for your thumbnail issue HOWEVER using glibc2.20 for the system is not a 100% solution. In my case most thumbnails appear but not all of them when using glibc2.20. For instance, the thumbnail images in usr/share/themes do not show for me.

[amethyst]

@amethyst :-

The Racy "limitation" may be due to the way it was built, Nic. I can't be certain, but I think Racy was about the final Puppy to use the older T2 build-system. Precise, of course, was already using Woof, before it then became Woof-CE with the release of the 6-series Pups....

(Barry may have modified certain key system scripts when he was building Wary & Racy. Or, the newer glibc may simply no longer support certain older items, due to being compiled against newer dependencies in the first place. No telling, though I'm inclined to believe the latter has something to do with it. I think with 2.30+ you're definitely getting beyond any possibility of guaranteed 100% compatibility with a Puppy of that vintage.)

Mike.

Yes, whatever it is, I do now think the better option for this specific Puppy is to use the older glibc2.20 and your Palemoon portable for the browser requirements. I've made a note in the first post. As a matter of interest - how do you get the files in the portable not to interfere with similar files (with the same name) in the running filesystem? BTW - The Deadbeef 0.7.2 portable (is it your creation?) works a treat on all my Puppys from Racy right through. Can you get Chromium and Firefox portable running with Racy....

[keniv]

@amethyst

The bdrv containing newer glibc than version 2.20 is not broken

I did not mean to suggest that the bdrv containing newer glibc was broken but instead that for me using the newer bdrv broke racy a bit.

Are you saying that you are using the older glibc 2.20 and then running mike's portable to use the latest Palemoon?

Yes, I'm posting from it now. Also please see the image1 below.

HOWEVER using glibc2.20 for the system is not a 100% solution. In my case most thumbnails appear but not all of them when using glibc2.20. For instance, the thumbnail images in usr/share/themes do not show for me.

I've just tested this. The majority of these do show thumbnail images for me. For instance usr/share/themes/Citrus-cut/gtk-2.0 shows what's in image2 below.
Using the bdrv containing glibc2.20 is not perfect in that I still get "the next boot will be faster" on every boot. I also still get problems with the Zip, Lock and Trash icons moving from the positions I've moved them to on the desktop even after "fixing" them with Desktop>JWMDesk Manager>Icon Layout. They move after reboot though strangely not every time. Hope this is of help.

Regards,

Ken.

[amethyst]

@keniv
I've created a save file to check out your issue. I got the "next boot will be faster" message only after the first boot after the save file was created (this is normal) and not again. I know from times gone by when I still used a save file that the message normally appears when the save file has been compromised in some way, eg. it has been tampered with (moved to another location for instance) or there has been changes to the partition. This is more likely to happen when your save file is on an ntfs or FAT partition. I've checked the icons layout issue and I only have an issue with the xlock icon which only wants to be at the right edge of the screen. It will keep its position if it's top, bottom or any other position at the right edge of the screen, if not it will move to the right edge again after x server is restarted. I don't have a problem with the other icons, one can move them around and they stay put. What I did to test this was to select the full traditional icons layout (you can keep that setting). All the icons were then shown and I then selected all of them and chose to remove them by selecting remove items from the right-click menu. I then dragged the icons I wanted displayed on the desktop, to the desktop (in this case trash, xlock and zip) to simulate your situation.

[mikewalsh]

@amethyst :-

As a matter of interest - how do you get the files in the portable not to interfere with similar files (with the same name) in the running filesystem?

I don't pretend to really understand quite HOW this works.....but this is the relevant chunk of code, lifted - and modified! - straight from watchdog's early experiments with the glibc 'tweak' a few years ago:-

Code: Select all

export LC_ALL=C
#
$HERE/glibc228/lib/ld-linux.so.2 --library-path $HERE/glibc228/lib:$HERE/glibc228/usr/lib:$HERE/glibc228/libstdc++:/usr/X11R7/lib:$HERE $HERE/palemoon32/palemoon "$@" -profile "$HERE/profile"

.....used in conjunction with this statement further up the top of the script:-

Code: Select all

HERE="$(dirname "$(readlink -f "$0")")"

This is the one code snippet that makes all these portable apps work as they do.....the 'readlink' trick, which tells the following code that any reference to the $HERE variable refers to the "containing" directory the script resides in, and keeps everything together in one place.

------------------------------------------------

As for Chromium & Firefox, heh; not for lack of trying, mate. I've spent hours & hours trying to get these functional under Racy, a few years back. I eventually came to the conclusion that there was no way in hell it was going to work, because there's too much new stuff in those browsers trying to interact with a lot of very old stuff in Racy itself.....and complaining at every step. You would end up rebuilding Racy into something much newer simply to get a single item working.....and in the process, buggering-up the required environment for Racy's original, natively-included apps.

This is what led me to explore watchdog's chroot environment scripts much more closely, and is a workaround I still use to this day. Running one Puppy within another CAN be done, for the simple reason Pup is so small in the first place compared to mainstream distros. When Darry and I were playing around with his 431-based "Phoenix" re-master, pre-pandemic, I built an SFS containing the whole of Tahrpup along with a 'portable' version of the Iron browser, all in one. Around 400MB packed, close to 1100MB loaded; big, I know, but you know yourself that as an SFS you can simply unload it when you're finished with it.

Darren couldn't believe we were able to run a then up-to-date Chromium 'clone' in such an elderly Puppy. Frankly, I was a wee bit gobsmacked myself!

There ARE limits with these old Puppies, though, beyond which it's just not practical to go. And glibc 2.20, as compiled by battleshooter several years ago, is about as far as you can "push" Racy. Beyond this, things get unstable, messy & start to break on a regular basis. Trust me, I've explored every possible option with this Puppy, and I know by now the exact point at which to say "Enough is enough...!"

Mike.

[keniv]

@amethyst

I've created a save file to check out your issue.

Thanks for that. I might make a new test savefile and start again and see if the new one has the same problems as the current one. I have not moved or renamed the existing savefile. It's on an ext3 partition. The only thing I can think of that could possibly have compromised it is that it now has saves when racy was using the new bdrv and the old bdrv. If I make a new savefile and only use the old bdrv and I have the same problem it should eliminate this as a possible cause.

I've checked the icons layout issue and I only have an issue with the xlock icon which only wants to be at the right edge of the screen.

For me this happens with both the Lock and Trash icons. Only Zip will stay where it's put. Again perhaps a new savefile might help with this.

Regards,

Ken.
Edit: @amethyst Have made a new savefile. Have setup as normal. Had same problem with sound as before but fixed in the same way. @mikewalsh's Palemoon 31.3.0.1 portable is working. Have both rebooted and shutdown and rebooted several times and only got the "next boot will be faster" message after the first reboot as is normal. If I set the desktop icons order from right to left to Lock, Zip and Trash they have stayed in place after a reboot and a shutdown and reboot though I'm not confident this will persist. So far so good.

[amethyst]

@keniv
Just a mention. I got the thumbnail trick to work when using a save file. It doesn't normally work because the saving mechanism purges the thumbnails cache when it tries to verify after reboot when using the new glibc and can't. So to get it to work: boot with the old bdrv and get the thumbnails displayed > untick the "Show image thumbnails" box in ROX's options > reboot with the new bdrv. The thumbnail cache will not update and the system will still read the thumbnail images in the cache. The thing of course is to get all the images when booted with the old bdrv. That didn't take too long for me as you just need to open the usual folders where images are normally located. Once displayed, the images are in the cache (this is also why some images did not display for me because it will only be saved in the cache once you actually open the specific folder and the images are displayed). Also: I've found that the thumbnail images display a bit faster during a session if you open the /root/.thumbnail/normal folder just after bootup so that all the thumbnails in the cache are displayed/loaded. I've made a little script for this - the folder displays after bootup so that all the thumbnail images can load and then closes after a while. Script attached (remove the fake .gz extension) and place in /root/Startup folder. Note however that if you have many thumbnail images in the cache (say more than 2000), this script may not be such a good idea as it may take some time to display all the images in the cache.

[keniv]

@amethyst
I'm now on my third savefile with this. The previous one was working fine before I tried to fix the last problem which is that the tray icon for "personal storage" does not show. However, it's sort of in stealth mode in that if you hover the mouse arrow above where it should be in the tray the information appears as normal. I tried menu>desktop>JWM configuration>JWM>Application launch buttons in tray. This appeared to have broken the savefile and I was back to "the next boot will be faster" at every boot and the "Lock" and "Trash" icons moving back to their original positions after being moved. On my third try at a stable savefile everything seems OK again but this time I have not tried to get the missing "personal storage" icon to appear in the tray.

Regards,

Ken.

Edit: On shutdown and reboot I'm back to having the same problems so I think I'm going to have to give up on thus as I have no idea how to fix it. I'ts a pity though.

[amethyst]

@amethyst
I'm now on my third savefile with this. The previous one was working fine before I tried to fix the last problem which is that the tray icon for "personal storage" does not show. However, it's sort of in stealth mode in that if you hover the mouse arrow above where it should be in the tray the information appears as normal. I tried menu>desktop>JWM configuration>JWM>Application launch buttons in tray. This appeared to have broken the savefile and I was back to "the next boot will be faster" at every boot and the "Lock" and "Trash" icons moving back to their original positions after being moved. On my third try at a stable savefile everything seems OK again but this time I have not tried to get the missing "personal storage" icon to appear in the tray.

Regards,

Ken.

Edit: On shutdown and reboot I'm back to having the same problems so I think I'm going to have to give up on thus as I have no idea how to fix it. I'ts a pity though.

The missing storage (freememapplet_tray) icon is a known bug of this Puppy, it comes over years. See the first post. Unfortunately nobody then nor me now know how to fix it. The interesting thing is that the icon seems to be built into the executable itself because I can't see a seperate icon for it. As a test, I loaded the original Racy Puppy release with its very, very old glibc and kernel and the icon does show for me then on my machine. However I know this disappearance act has been an issue even with the original release and if you go back to the old forum you will see posts about this issue then. I tried a newer version of that applet too but get the same result, so it remains a mystery. Did you get the thumbnails "trick" working? You need to deselect the "Show image thumbnails) box in ROX's options after you got all the images displayed and keep it like that (don't select it again afterwards if you are going to boot with the newer kernel). I must say I'm having lots of fun with this Puppy, the missing tray icon is the only problem I do not have an answer for. As a final check of your lock, trash and zip icons issue, I again created a save file, moved those icons around and rebooted at least ten times. I can't replicate your problem. ONLY the lock icon always wants to be at any position right against the right edge of the screen. So you can move it up and down against the right edge and it keeps its position for me. The other icons I do not have an issue at all.

[keniv]

@amethyst

The missing storage (freememapplet_tray) icon is a known bug of this Puppy, it comes over years. See the first post. Unfortunately nobody then nor me now know how to fix it.

Yes I did see it but did not realise it was a known bug. I've never seen it before.

Did you get the thumbnails "trick" working?

Well as I'm using the old bdrv with glibc 2.20 I don't have trouble with displaying thumbnails.

As a final check of your lock, trash and zip icons issue, I again created a save file, moved those icons around and rebooted at least ten times. I can't replicate your problem.

Thanks for trying that. I wondered if the reason why after fixing the positions of the lock, zip and trash icons that they move again might be related to this issue of seeing "the next boot will be faster" at every reboot. As I said in an earlier post, when I first start to make a new savefile I only see this message once after the first shutdown and reboot. At this point I also seem to be able to fix these icons. Once I start to see this message at every boot up the icons return to their original position with the exception of zip. I boot with pfix=fsck. Should this be able to detect if the contents of the savefile is corrupted in some way. I'm certainly getting fed up making new savefiles only for them to end up with the same problem as the previous one and which seems to be unfixable.

Regards,

Ken.

[amethyst]

@keniv
I don't have the issues with the save file as you do so don't know what is going on there for you. I also run fsck at bootup, it checks the integrity of the filesystem but not individual files like the save file. This is as good as it is going to get with this old Puppy. This Puppy was the last of the old style traditional Puppys, built differently than the modern line (which started with Precise (which was released only a year later). The mere fact that so many modifications are still possible, is actually surprising. I made basically the same modifications to Precise and everything works (thumbnails, etc. no issues with the upgraded glibc and so on). I use my upgraded version of Precise everyday.