Closed zaqueoae closed 11 months ago
I just checked that the flatpack version of debian is working correctly.
@zaqueoae We generally advise installation of the browser before installation of QZ-Tray; the places that QZ-Tray needs to go to install its certificates may not exist otherwise.
You may want to make sure you have certgen installed as well.
It's funny, because after it worked with chromium flatpack, I uninstalled qz, installed a qz with my certificate and it stopped connecting to the websocket. I have uninstalled it, I have reinstalled the official qz that you have on your website, and it doesn't work either, even though it worked before.
@zaqueoae We generally advise installation of the browser before installation of QZ-Tray; the places that QZ-Tray needs to go to install its certificates may not exist otherwise.
You may want to make sure you have certgen installed as well.
I'm going to try the following. I uninstall qz and chromium. I install chromium and then qz. Let's see what happens.
I wouldn't know how to check if I have the certificate installed.
I would
installed a qz with my certificate
I'm not sure I understand what you're saying here. QZ-Tray should install just fine with no changes to the installer. You can always add the certificate fingerprint to allowed.dat afterward. Did you compile this installer yourself?
I'm also curious to know if you're using KDE or another GUI
The QZ-Tray logs should show the certificate value, or if you're using a GUI, Click the QZ-Tray icon > Advanced > Site Manager > Allowed/Blocked tabs
me gustaría
- asegúrese de que certgen esté instalado
- instalar el navegador
- instalar la bandeja QZ
instalé un qz con mi certificado
No estoy seguro de entender lo que estás diciendo aquí. QZ-Tray debería instalarse bien sin cambios en el instalador. Siempre puedes agregar la huella digital del certificado a permitido.dat después. ¿Compilaste este instalador tú mismo?
También tengo curiosidad por saber si estás usando KDE u otra GUI.
I don't know how to do step 1.
Regarding step 2 and 3, I have repeated it several times with flatpack and apt . But I can't get it to work. It keeps giving an error.
It definitely doesn't work. I have uninstalled and installed several times. But it still doesn't work even in the flatpack version. However, it has worked before. So I don't really know what's going on.
I am using kde on both ubuntu and debian.
There is no certificate in the GUI.
I think I don't have any certificate because it hasn't connected with websocket. The only time it connected, the window appeared telling me to accept the certificate.
I just tried it on debian + Xfce with the same result on chromium apt.
I installed qz like this: wget -qO - qz.sh | bash
Firefox on Debian should be fixed once QZ Tray 2.2.3 is released. You can test this out here while you wait, per:
We also added initial support for Epiphany browser here, starting with QZ Tray 2.2.3:
@zaqueoae I tested QZ Tray 2.2.2 with Chromium on Ubuntu 22.04 and I can confirm that it didn't work.
Next, I tested with QZ Tray 2.2.3-rc.2 and it works, so I my instinct is that I must have fixed this with one of the above PRs.
Can you please test it out here and let us know if it's fixed with the RC?
I have tried this:
I have uninstalled all versions of chromium and installed the apt version again and it was still working. Next I uninstalled qz and reinstalled it and with chromium it worked perfectly. Furthermore, when installing qz again, the Firefox window that I had active asked me to restart Firefox for an update (Actually I have not updated anything), and when it restarted it already connected to the websocket. Something quite strange.
The desktop environment shouldn't matter.
I'll check the following. Let me know if I missed one:
This will likely NOT make the 2.2.3 release, but we can provide a one-off installer if needed.
Firefox apt seems to be the only version that doesn't crash. I just tried it in Kubuntu and it works fine.
Summary: Firefox apt works with debian and ubuntu. There is no guarantee that the rest of the browsers and packages will work.
Firefox apt seems to be the only version that doesn't crash.
What do you mean by "crash"?
On Debian 12 Xfce with qz v2.2.3-rc.1
- 🚫 Chromium apt: Not working
On Debian 12 KDE Plasma with qz v2.2.3-rc.1
- ✅ Chromium apt: Yes it works
The desktop environment should not affect this. Is there a chance an older version of QZ Tray was installed on your Plasma environment? See https://github.com/qzind/tray/pull/1004 for more details.
Testing chromium
snap on Debian 12 🚫 FAILS.
IOException executing: [certutil, -d, sql:/home/debian/snap/chromium/current/.pki/nssdb/, -A, -t, TC, -n, QZ Industries, LLC, -i, /tmp/root-ca-16565941996156721047.crt]
Firefox apt seems to be the only version that doesn't crash.
What do you mean by "crash"?
By crash in this case I mean that it does not connect to the websocket. In the case of Firefox, with version v2.2.3-rc.1 it has worked for me on 3 different computers. One with deban kde, another with kubuntu and another with debian xfce.
On the other hand, chromium only in one of them.
On the other hand, chromium only in one of them.
I was able to reproduce, but it was because of missing certutil
. I've patched this here just now: cfaab7e . If that's not the cause, it may be from the other cause I mentioned here: https://github.com/qzind/tray/issues/1194#issuecomment-1771462445. We'll automatically install certutil
on Debian starting with QZ Tray 2.2.3.
Debian 12:
certutil
is installed.QZ Tray 2.2.3 is now available which will fix the majority of the issues listed. If one's not working, please open up a dedicated bug report and we can look into it.
I have installed qz in this way:
wget -qO - qz.sh | bash
Next I installed the browser. In the case of this example it is chromium using apt.
An example can be seen in this video: https://www.youtube.com/watch?v=KaAafMxCQmU
The error that appears in the terminal: