Bug 431444 - Titlebars disappear when doing drag and drop with a file while pressing Alt+Tab
Summary: Titlebars disappear when doing drag and drop with a file while pressing Alt+Tab
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.21.4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-11 16:06 UTC by Lua
Modified: 2021-12-04 04:39 UTC (History)
3 users (show)

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


Attachments
bug happening (656.93 KB, video/mp4)
2021-01-11 16:06 UTC, Lua
Details
kde 5.21.4 still has this bug (929.86 KB, video/mp4)
2021-05-01 19:37 UTC, Lua
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lua 2021-01-11 16:06:02 UTC
Created attachment 134739 [details]
bug happening

SUMMARY


STEPS TO REPRODUCE
1. Open Dolphin, create a txt file and open and Kate
2. Drag the file, press Alt+Tab and drop the file in Kate's thumbnail in the left panel

OBSERVED RESULT
Window titlebars will disappear.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 20.10
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
plasma-shell --replace doesn't solve the problem. It's necessary to press Control+Alt+Backspace to restart Xorg.
Comment 1 Nate Graham 2021-01-12 00:55:02 UTC
Looks like KWin crashed. Can you grab a backtrace of the crash? coredumpctl may be useful. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Cannot reproduce FWIW.
Comment 2 Bug Janitor Service 2021-01-27 04:33:24 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Lua 2021-02-01 17:13:34 UTC
This is the output:
$ coredumpctl
TIME                            PID   UID   GID SIG COREFILE  EXE
Mon 2021-02-01 14:10:14 -03    1439  1000  1000  11 truncated /usr/bin/kwin_x11

I'm using
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Comment 4 Lua 2021-02-01 17:20:15 UTC
Also, I ran coredumpctl gdb 1439. Is there any sensitive info in this? I hid the ID numbers.

$ coredumpctl gdb 1439
           PID: 1439 (kwin_x11)
           UID: 1000 (cosmic)
           GID: 1000 (cosmic)
        Signal: 11 (SEGV)
     Timestamp: Mon 2021-02-01 14:10:11 -03 (4min 45s ago)
  Command Line: /usr/bin/kwin_x11
    Executable: /usr/bin/kwin_x11
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (cosmic)
       Boot ID: [there's an ID here]
    Machine ID: [there's an ID here]
      Hostname: [my hostname]
       Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.[Machine ID here].1439.[I think there's an ID here too].lz4 (truncated)
       Message: Process 1439 (kwin_x11) of user 1000 dumped core.
                
                Stack trace of thread 1439:
                #0  0x00007fce854aebf9 n/a (/usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5.78.0 + 0x47bf9)
                
                Stack trace of thread 1480:
                #0  0x00007fcf47953bf6 n/a (n/a + 0x0)

GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kwin_x11...
(No debugging symbols found in /usr/bin/kwin_x11)
BFD: warning: /var/tmp/coredump-puVKoj is truncated: expected core file size >= 2375802880, found: 2147483648
[New LWP 1439]
[New LWP 1480]
[New LWP 1454]
[New LWP 1444]
[New LWP 1453]
[New LWP 1517]
[New LWP 5180]
[New LWP 1440]
[New LWP 1455]
[New LWP 1452]
Cannot access memory at address 0x7fcf49584168
Cannot access memory at address 0x7fcf49584160
Failed to read a valid object file image from memory.
--Type <RET> for more, q to quit, c to continue without paging--
Core was generated by `/usr/bin/kwin_x11'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fce854aebf9 in ?? ()
[Current thread is 1 (LWP 1439)]
Comment 5 Bug Janitor Service 2021-02-16 04:33:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Nate Graham 2021-02-16 15:14:35 UTC
Thanks. However I'm afraid the backtrace doesn't have any information in it. :(

> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x00007fce854aebf9 in ?? ()
> [Current thread is 1 (LWP 1439)]

Looks like it was truncated somehow. Maybe you can reach out to other Kubuntu users to se how to proceed? Thanks!
Comment 7 Lua 2021-02-21 20:16:50 UTC
It happens in Neon 5.21 too.
Comment 8 Nate Graham 2021-03-09 03:56:14 UTC
moving to KWin since this is caused by a KWin crash.
Comment 9 Bug Janitor Service 2021-03-24 04:33:48 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2021-04-08 04:33:38 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 11 Lua 2021-05-01 19:37:30 UTC
Created attachment 138067 [details]
kde 5.21.4 still has this bug

This still happens in 5.21.4.
Comment 12 kde.org 2021-11-04 20:25:41 UTC
If you can still reproduce this bug, please provide a backtrace with debug information following the instructions given in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 13 Bug Janitor Service 2021-11-19 04:39:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2021-12-04 04:39:00 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!