I tested the https://gitlab.com/users/sign_in URL including with logging in fully to my GitLab account on Firefox, Brave and Chromium (Version 135.0.7049.95 (Official Build, ungoogled-chromium) openmandriva 25.90 (64-bit)) on my Rome machine and could not reproduce a crash.
Do you have any browser extensions / plugins loaded that may be causing any issues there?
If you have extensions installed, did you try with all extensions disabled? - Even if only to rule those out of causing any issues.
No I don’t have any extensions as the last time I checked I could not install any extension. I even created a totally new profile and still the same results.
One other thing I have noticed (might be related), I cannot create a pdf print of any website. Can it be a graphics issue?
I think @bero fixed the extensions issue. They load fine now.
I thought that was just happening on brave. I find that it is more than just PDFs that won’t print. I tried to print a map a couple weeks ago and could not.
I figured you probably did those steps, but always worth asking
This was reported in matrix chat around a week ago with Brave (also Chromium based), yet when I tested printing from all browsers printing worked for me via CUPS to a colour laser printer with no problems.
The reporter of that was going to look into whether it was a CUPS library / configuration issue or not, but I do not think they ever got back to us about it.
You could try running Chromium from a console to see if it outputs any further useful information when those tab crashes happen as searching for that error code returns a lot of varying results with no single solution for it.
I want to buy your hardware! What computer is this, that no issue can be reproduced on it?
When I try to PDF print a page, it tried to load the preview, then it fails. The destination field gets disabled, while set to “Save as PDF”. Here is the errors in the command line when this happens:
Mind you I have a network printer, but at the moment it is not in my printers list on KDE. I actually send prints to it from inside a docker container, or from my smartphone.
Asked gemeni 2.5 Pro. Did:
Restarted chromium, still has the problem with pdf printing. When I press Ctrl+Shift+Print to bring up the kde’s print dialog, I don’t see any option for PDF printing there.
I was not stating that to say it is not an issue because I cannot reproduce it on my machine, I was stating that to emphasise that it may be a CUPS configuration issue and not an issue with the browser itself as I had to manually configure my own printer in CUPS and I do not see these printing issues with any browser.
It sounds like you are trying to print without having your printer set up in CUPS and without it set as a default, that is bound to fail.
[238010:238010:0428/180516.226756:ERROR:print_backend_cups.cc(211)] CUPS: Error getting default printer: No destinations added.
This error is a CUPS error essentially stating that you do not have a default printer configured in CUPS and possibly going by what you stated above that you do not have a printer installed in CUPS at all.
Assuming you do have your printer set up in CUPS then in order to set your printer as the default in CUPS you can do the following steps:
Restart the CUPS system service: sudo systemctl restart cups.service
You would now have your printer set as the system default, you may have to restart your browser for it to pick up the updated CUPS Printer configuration.
If you do not have your printer added in CUPS, there are numerous guides you can find online that will help you through installing a new printer in CUPS as well as the CUPS Documentation website to aid in that quest.
The above may well fix your non-printing issue, but it doesn’t help resolve your Chromium tabs crashing on the GitLab login page that you initially reported.
Relying on ML garbage for any kind of technical guidance rather than reading the actual documentation produced by the CUPS developers and educating yourself on how to install and configure a printer in CUPS properly is a waste of everyone’s time and will not fix a printer installation/configuration issue, if a printer is not installed and configured in CUPS it will not magic itself into working out of thin air.
This needs/ed its own thread. If you think it’s related then put a link back to this one.
The users have to bear in mind that the forum is not individual technical support helpdesk.
Discussing 2 (or more) different issues won’t serve well to the others who may look around for the same problem in the future.
