Hi, I would like to update Firefox-esr Version 115.15.0 to the latest Version 129, because of constantly crashing during surfing.
I followed the instruction on mozilla website to includer their repository, however i did not worked at all.
Same with adding the mozilla team repository with
" sudo add-apt-repository ppa:mozillateam/ppa"
What to do for upgrading ??
regards, hitam
Could you tell us which command have you typed? In which qube exactly? And why doesn’t it work?
It would be easier to read if you were using the code-block formatting string (```) around your command lines, like this:
sudo add-apt-repository ppa:mozillateam/ppa
Hey! sorry to interrupt but the Qubes forum isn’t a general linux issues one. So I am afraid I’ll close this topic.
The forum welcomes all discussions where Qubes is or could be involved. In this case, the problem could as well happen on any linux. I hope you understand.
A user kindly brought to my attention that this couls be due to “networkless” templates. Sorry for the missjudgement and feel free to continue discussion.
Post the commands that you run in the terminal and their output to see what did not work for you.
Did you try these instructions?
The only Qubes OS specific change for these instructions is to add the use of proxy for wget e.g.:
https_proxy=http://127.0.0.1:8082/ http_proxy=http://127.0.0.1:8082/ wget -q https://packages.mozilla.org/apt/repo-signing-key.gpg -O- | sudo tee /etc/apt/keyrings/packages.mozilla.org.asc > /dev/null
Hi,
firefox crashes reatedly many times during operation…on my UBUNTU 22.04 firefox never crashes at all.
I put all commands an tried to insall in the template debian-12-clone-office template, which the Office Qubes is based on.
Maybe it’s crashing because you’re opening too many tabs and your qube don’t have enough memory for them. Try to increase the qube’s max memory in its Settings → Advanced tab.
Thanks for the advice. I increased the memory size in the office Qube and quadrupled it, since I have ample physically memory (128 GB) installed. Thanks for your advice.
regards, hitam
Hi, the debian-12-clone office does not want to start anymore. I tried to download from /va/log/xen/console some logs, however I did not work out.
What to do next ??
reagrds, hiatm
After start of the Office ube including Gnome desktop…the ube starts to increase the CPu utilization up to 99 %, making it unusuable…even killing the Qubes does not work immediately and takes some time.
What did you do in this template before this issue happened?
If you’ve installed something there maybe it’s out of free space in the system storage. Try to increase the system storage size in the template’s Settings → Basic tab and start again.
But need to look at the qube’s logs to be sure.
You can also try to connect to this qube’s console using qvm-console-dispvm CLI tool in dom0 terminal to see the logs and maybe try to login as user or root user there to check what’s happening, e.g. the disks usage.
error message: cannot connect to qrexec agent for 60 seconds…
This is not enough. Check the log from this file:
/var/log/xen/console/guest-YourQubeName.log
What I changed:
in fstab i changed the mounting of
/dev/xdvi /date form noauto —> auto.
This case the attached partiton will be automatically mounted inside the Office Qube Gnome enviroment, without doing it manually.
The is the last command i observed in when I opened a dom0 console.
That’s the issue, with auto the system waits for this partition and since it’s missing the system fails to boot.
You need to change it back no noauto.
Mount your template’s system storage (root) LVM image in some disposable qube and edit the fstab:
However, the partition are nicely mounted inside Qube Office / Gnome environment.
Did you attach the block devices to your qubes persistently or are you attaching them manually after the qubes are started?
i attached them persistently, not to repeat it again after each restart.