Closed kreativK closed 1 month ago
When did this happen? Did you just launch it and it was gone or was it never there?
When did this happen? Did you just launch it and it was gone or was it never there?
It worked when I first installed my system a few days ago but I switched to brave and didn't run it again until yesterday. Now it's just gone, can't get it back with a restart.
Odd, I'm assuming you are certain you were running hardened chromium when it did work, because it shipped recently so there is a chance you weren't.
Odd, I'm assuming you are certain you were running hardened chromium when it did work, because it shipped recently so there is a chance you weren't.
I installed the system on the 29th of july. I'm certain I ran the browser that was packaged with secureblue, named chromium web browser and with the blue chromium icon, which should be the same one causing errors right now. I don't know if anything has changed since then and I don't know if you just shipped regular chromium or hardened at the time.
29th of July
Lol, thats the day it shipped. All the info around the icon is the same between hardened and regular chromium. Would you be willing to test run it under X11 if you haven't already? (You would need to enable XWayland)
29th of July
Lol, thats the day it shipped. All the info around the icon is the same between hardened and regular chromium. Would you be willing to test run it under X11 if you haven't already? (You would need to enable XWayland)
Sorry, I see now that it actually was the 28th. I toggled XWayland and ran chromium-browser --backend=x11-backend.so --xwayland, it made no difference.
I see now that before it starts spamming the konsole with the errors provided above, it gives these errors:
[30715:30737:0801/174829.638666:ERROR:simple_backend_impl.cc(79)] Failed to create directory: /dev/null/Default/Code Cache/js [30715:30752:0801/174829.638677:ERROR:simple_backend_impl.cc(79)] Failed to create directory: /dev/null/Default/Code Cache/wasm [30715:30752:0801/174829.638774:ERROR:simple_backend_impl.cc(79)] Failed to create directory: /dev/null/Default/Code Cache/wasm [30715:30752:0801/174829.638778:ERROR:simple_backend_impl.cc(751)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Default/Code Cache/wasm [30715:30737:0801/174829.638781:ERROR:simple_backend_impl.cc(79)] Failed to create directory: /dev/null/Default/Code Cache/js [30715:30737:0801/174829.638790:ERROR:simple_backend_impl.cc(751)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Default/Code Cache/js [30715:30764:0801/174829.638862:ERROR:disk_cache.cc(208)] Unable to create cache [30715:30764:0801/174829.638875:ERROR:disk_cache.cc(208)] Unable to create cache Warning: disabling flag --expose_wasm due to conflicting flags [30762:30803:0801/174829.760206:ERROR:simple_backend_impl.cc(79)] Failed to create directory: /dev/null/Default/Cache/Cache_Data [30762:30803:0801/174829.760604:ERROR:simple_backend_impl.cc(79)] Failed to create directory: /dev/null/Default/Cache/Cache_Data [30762:30803:0801/174829.760612:ERROR:simple_backend_impl.cc(751)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Default/Cache/Cache_Data [30762:30806:0801/174829.760835:ERROR:disk_cache.cc(208)] Unable to create cache
Did you change your home directory /partition?
What happens if you clear the browsee cache by deleting the content in $HOME/.cache/google-chrome/Default/Cache
?
@34N0 Cache is disabled, these errors are normal. So are the wasm errors.
@kreativK
--backend=x11-backend.so
I'm not sure this works, maybe it does. I meant try chromium-browser --ozone-platform=x11
@34N0 Cache is disabled, these errors are normal. So are the wasm errors.
@kreativK
--backend=x11-backend.so
I'm not sure this works, maybe it does. I meant try
chromium-browser --ozone-platform=x11
This fixed it!
@kreativK Awesome, I guess chromium isn't too stable on wayland+nvidia yet.
Could also just be a wayland+nvidia thing relating to decorations, idk.
you can set it to always run in x11 in about:flags -> search "Preferred Ozone platform" -> set it to x11.
@kreativK Awesome, I guess chromium isn't too stable on wayland+nvidia yet.
Could also just be a wayland+nvidia thing relating to decorations, idk.
Yeah maybe. Something similar happened with brave, it couldn't open without --ozone-platform=wayland, but I could change the ozone flag to Wayland and I didn't need to enable XWayland.
you can set it to always run in x11 in about:flags -> search "Preferred Ozone platform" -> set it to x11.
This weirdly doesn't work, and setting it to Wayland doesn't work either. I have to manually run it with "chromium-browser --ozone-platform=x11", otherwise the top bar stays invisible.
Did you change your home directory /partition?
What happens if you clear the browsee cache by deleting the content in
$HOME/.cache/google-chrome/Default/Cache
?
I haven't changed my home directory or partition
This weirdly doesn't work, and setting it to Wayland doesn't work either. I have to manually run it with "chromium-browser --ozone-platform=x11", otherwise the top bar stays invisible.
... huh. Strange. They do the same thing? Does --ozone-platform=x11
or --ozone-platform-hint=x11
show under Command Line in about:version when you run it without the commandline flag but with the about:flags toggle?
... huh. Strange. They do the same thing?
Yeah, they both have the top bar invisible.
Does
--ozone-platform=x11
or--ozone-platform-hint=x11
show under Command Line in about:version when you run it without the commandline flag but with the about:flags toggle?
No, it says --ozone-platform=wayland in about:version even tho its toggled to x11 in about:flags
Yeah, they both have the top bar invisible.
Wdym both?
No, it says --ozone-platform=wayland in about:version even tho its toggled to x11 in about:flags
Did you restart after doing it?
Wdym both?
When you asked if they do the same thing I thought you meant setting the ozone about:flags to X11 and Wayland.
Did you restart after doing it?
Restarting chromium after toggling to X11? If so, yes.
When you asked if they do the same thing I thought you meant setting the ozone about:flags to X11 and Wayland.
Sorry, I meant the commandline flags and UI flag. They should do the same thing...
Restarting chromium after toggling to X11? If so, yes.
I think I know what the issue is but I'm not sure, you can add the flag to /etc/chromium.conf
in the mean time.
Sorry, I meant the commandline flags and UI flag. They should do the same thing...
Oh, yeah weirdly they don't.
I think I know what the issue is but I'm not sure, you can add the flag to
/etc/chromium.conf
in the mean time.
I FIXED IT! In /etc/chromium.conf, NATIVE_WAYLAND was turned off. I edited it to on and now it starts as it should, I can even toggle XWayland to off. Changed the ozone about:flags to wayland and no difference, everything just works as it should!
... huh. Alright. That seems like something we need to fix then, alter the chromium.conf for that I guess. Thank you.
Yeah, thx for the help!
The top bar is invisible. I can still search for stuff, but I can't see what I type and I can't minimize or close the program as usual because those buttons are gone.
When running the program in the console with the "chromium-browser" command, the following is flooding the console:
[24129:24172:0801/163633.198269:ERROR:client_shared_image.cc(294)] Unable to create ScopedMapping [24129:24172:0801/163633.198274:ERROR:one_copy_raster_buffer_provider.cc(355)] MapSharedImage Failed. [24129:24172:0801/163633.198540:ERROR:client_native_pixmap_dmabuf.cc(45)] Failed to mmap dmabuf: Invalid argument (22) [24129:24172:0801/163633.198551:ERROR:client_shared_image.cc(156)] Failed to map the buffer. [24129:24172:0801/163633.198556:ERROR:client_shared_image.cc(142)] ScopedMapping init failed. [24129:24172:0801/163633.198562:ERROR:client_shared_image.cc(294)] Unable to create ScopedMapping
My image is kinoite-asus-nvidia-userns-hardened and I use unstable hardened kargs.
Output of ujust check-local-overrides:
diff -r --suppress-common-lines '--color=always' --exclude 'passwd' --exclude 'group' '--exclude=subgid' '--exclude=subuid' '--exclude=machine-id' '--exclude=adjtime' '--exclude=fstab' '--exclude=system-connections' '--exclude=shadow' '--exclude=gshadow' '--exclude=ssh_host' '--exclude=cmdline' '--exclude=crypttab' '--exclude=hostname' '--exclude=localtime' '--exclude=locale' '--exclude=lock' '--exclude=.updated' '--exclude=LOCK' '--exclude=vconsole' '--exclude=00-keyboard.conf' '--exclude=grub' '--exclude=system.control' '--exclude=cdi' '--exclude=default.target' /usr/etc/authselect/authselect.conf /etc/authselect/authselect.conf 4c4 < with-faillock