Bug 492413 - Full Screen Mode Broken
Summary: Full Screen Mode Broken
Status: REPORTED
Alias: None
Product: ghostwriter
Classification: Applications
Component: general (other bugs)
Version First Reported In: 24.01.75
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: megan.conkle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-30 15:37 UTC by scottwilliamhannan
Modified: 2024-10-28 15:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-3825900-0.html (1.20 KB, text/html)
2024-10-13 00:33 UTC, scottwilliamhannan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description scottwilliamhannan 2024-08-30 15:37:55 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Full screen mode does not function properly on Ubuntu 24.04.1 LTS. Pressing F11 or selecting Full Screen mode from the drop down menu turns the screen completely white. Pressing F11 or Escape exits just fine, the program does not crash. 

STEPS TO REPRODUCE
1.  Press F11 or enter Full Screen Mode
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: GNOME not Plasma (sorry)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This feature worked as intended yesterday when I was running the previous Ubuntu LTS. I upgraded to 24.04.1 just last night and now it doesn't work. I suspect that is the culprit.
Comment 1 megan.conkle 2024-10-12 21:43:12 UTC
Are you running X or Wayland?
Comment 2 scottwilliamhannan 2024-10-13 00:33:54 UTC
Created attachment 174752 [details]
attachment-3825900-0.html

Wayland.

Thanks!

On Sat, Oct 12, 2024, 3:43โ€ฏPM <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=492413
>
> megan.conkle@kdemail.net changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from megan.conkle@kdemail.net ---
> Are you running X or Wayland?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Bug Janitor Service 2024-10-28 03:46:42 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 scottwilliamhannan 2024-10-28 15:08:04 UTC
(In reply to Bug Janitor Service from comment #3)
> ๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15
> days. Please provide the requested information, then set the bug status to
> REPORTED. If there is no change for at least 30 days, it will be
> automatically closed as RESOLVED WORKSFORME.
> 
> For more information about our bug triaging procedures, please read
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.
> 
> Thank you for helping us make KDE software even better for everyone!

It might be that I'm just really unfamiliar with this process, but, I just received the above email, asking to provide the requested info regarding whether I'm using X or Wayland. It sure looks like I did provide that info several days ago: Wayland. 

I just changed the status in this message to reported. If I'm missing something, it's because I'm totally unfamiliar with this bug reporting process. On my end, this bug persists. Let me know if I'm supposed to do something else to keep it open or whatever.