Bug 2184330 - Electron based apps don't remember maximized window flag after restart in Fedora 38
Summary: Electron based apps don't remember maximized window flag after restart in Fed...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Yaakov Selkowitz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-04 09:17 UTC by Patryk
Modified: 2023-07-14 12:13 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-14 12:13:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Patryk 2023-04-04 09:17:55 UTC
Description of problem:
I'm not sure if it's a mutter issue but I had to choose a component. After upgrade from F37 Workstation to F38 Workstation I see that Electron based apps (I tested Visual Studio Code from RPM and Heroic Game Launcher from AppImage) apps don't remember maximized window flag. All the time windowed mode is forced by OS even if I exited at maximized window mode. I see this issue on both Wayland and X11 session.


Version-Release number of selected component (if applicable):


How reproducible:
All the time

Steps to Reproduce:
1. Launch eg. VS Code
2. Maximize a window
3. Close an app
4. Launch again

Actual results:


Expected results:


Additional info:

Comment 1 lokijuhz 2023-04-24 20:31:52 UTC
I hit the issue after updating from F37 to F38 with Thunderbird and other apps like QtCreator or Java apps. Running GNOME on Xorg.

Comment 2 lokijuhz 2023-04-24 20:44:42 UTC
(In reply to lokijuhz from comment #1)
> I hit the issue after updating from F37 to F38 with Thunderbird and other
> apps like QtCreator or Java apps. Running GNOME on Xorg.

Running on ThinkPad X1 Carbon Gen 9, Kernel 6.2.11-300.fc38.x86_64, GNOME 44.0

Comment 3 Than Ngo 2023-07-14 10:43:22 UTC
it looks like a issue in window manager. reassing to correct component

Comment 4 Patryk 2023-07-14 12:13:26 UTC
It's already fixed. It was related to a missing flags at windows creation in Mutter.


Note You need to log in before you can comment on or make changes to this bug.