As you see, there are 2 different Firefox browsers (Firefox and Firefox Developer Edition) and they are no separated in dock and looking as only “Firefox” at top bar too. Name of application or WMClass does not change the active window name at the bar.
I’ve been using same desktop entry for a long time but it hadn’t been working like that until these days.
Please read this: How to provide good information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
P.S. If you enter a bit more details in your profile, we can also see which Desktop Environment you’re using, which exact CPU/GPU or Kernel, … you have without typing it every time
They already don’t have the same icon or same WMClass. Also I shared the desktop entry above. It wasn’t working like that before, since the latest updates it’s been broken.
Dealt with something similar in bspwm/xprop. I can see you have an alternate icon in the posted .desktop file. I think you can change the exec command in the .desktop file to add --class arg and it should pick it up. The spaces I’m not sure about, I would personally use something like “FirefoxDev”
I guess there’s another thing and I started to think dual boot may causing that because today I ran Manjaro 4 times and first 3 of 4 was working healthy, Firefox Developer Edition was not displaying as Firefox.
But before the last time, I booted Windows. After a while I switched to Manjaro and I got a fail about pkgfile (couldn’t read the whole line) but I can’t see it in logs with dmesg | less or sudo cat /var/log/boot.log.
I don’t know how to solve or debug that.
/dev/nvme0n1p2: clean, 2118075/14671872 files, 30809580/58664828 blocks
[ OK ] Finished Tell Plymouth To Write Out Runtime Data.
[ OK ] Finished Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Record System Boot/Shutdown in UTMP...
[ OK ] Finished Record System Boot/Shutdown in UTMP.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Set.
[ OK ] Finished Load Kernel Modules.
Starting Apply Kernel Variables...
[ OK ] Finished Apply Kernel Variables.
Starting CLI Netfilter Manager...
[ OK ] Finished CLI Netfilter Manager.
[ OK ] Reached target System Initialization.
[ OK ] Started CUPS Scheduler.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Monthly clean packages cache.
[ OK ] Started Generate mirrorlist weekly.
[ OK ] Started pkgfile database update timer.
[ OK ] Started Daily verification of password and group files.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Path Units.
[ OK ] Reached target Timer Units.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Listening on D-Bus System Message Bus Socket.
Starting Socket activation for snappy daemon.
[ OK ] Listening on Socket activation for snappy daemon.
[ OK ] Reached target Socket Units.
[ OK ] Reached target Basic System.
[ OK ] Started Periodic Command Scheduler.
[ OK ] Started D-Bus System Message Bus.
Starting Network Manager...
Starting Clean up modules from old kernels...
Starting Authorization Manager...
Starting Snap Daemon...
Starting User Login Management...
Starting Rotate log files...
Starting Daily man-db regeneration...
[ OK ] Started Verify integrity of password and group files.
[ OK ] Finished Clean up modules from old kernels.
[ OK ] Started Network Manager.
[ OK ] Reached target Network.
Starting Network Manager Wait Online...
Starting CUPS Scheduler...
Starting PostgreSQL database server...
Starting Permit User Sessions...
[ OK ] Started User Login Management.
Starting Hostname Service...
[ OK ] Started CUPS Scheduler.
[ OK ] Finished Rotate log files.
[ OK ] Finished Permit User Sessions.
Starting GNOME Display Manager...
Starting Hold until boot process finishes up...
Starting Terminate Plymouth Boot Screen...
[ OK ] Started Authorization Manager.
Starting Modem Manager...
Apparently you’re suffering of what is called a side effect:
When rebooting from Windows to Manjaro, please cold boot:
Shut down Windows completely
Press the power button to start the PC
Choose Manjaro from grub
When rebooting from Manjaro to Windows, warm boot is still allowed
This is probably from a buggy Windows driver that leaves the UEFI system in an undesired state, but as most people don’t dual boot, the Windows driver manufacturers probably won’t care even if you file a bug…
Actually, I don’t think so because if that bug created by Mozilla it wouldn’t be random at different boots. It would be random at every processes.
And, one more thing here. I removed the default Firefox browser which is built-in by Manjaro and I’ve seen when that error occurs, whole desktop entry is being ignored. All types of Firefox is just looking as “firefox”.
It’s really weird but I’m leaving that information as a solution.
Logging in with GNOME XOrg from login screen fixes that fault with Discord’s black screen problem while screen sharing.
Wayland screen sharing is not nearly as mature as X11 screen sharing.
The simplest and quickest solution is to log out, and before logging in, click on the gear icon in the lower right corner, and select the Xorg/X11 session.
Electron applications can only share the full screen when you are in an X11 session, nonetheless, even in a Wayland session, you should be able to share other X11 applications running in XWayland, just not Wayland-native applications and the full screen.
There is some experimental support for full screen sharing in Firefox and Google Chrome, as far as I’m aware.