Bug 251213

Summary: Packing windows broken
Product: [Plasma] kwin Reporter: Radek Novacek <rad.n>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Radek Novacek 2010-09-14 14:29:57 UTC
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

Packing windows doesn't work correctly - windows sometimes disappears and then become unresponsive (window content is not repainted). I have to restart affected application to get that working. I have Qt with patch from bug [1] applied. Without it the crash from that bug occurs. So it might be connected.

[1] https://bugs.kde.org/show_bug.cgi?id=230490

Reproducible: Sometimes

Steps to Reproduce:
1. Set keyboard shortcut for packing windows (kwin section)
2. Run some application
3. Move unmaximized windows with shortcuts



Output of some application when this happens:

Kate:

X Error: RenderBadPicture (invalid Picture parameter) 159
  Extension:    148 (RENDER)
  Minor opcode: 8 (RenderComposite)
  Resource id:  0x34009d2

Gwenview:
No error but packing not working - window flick at anticipated position but remain in previous position

gnome-about:

Gdk-ERROR **: The program 'gnome-about' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1516 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted (core dumped)
Comment 1 Christoph Feck 2010-09-14 14:37:50 UTC

*** This bug has been marked as a duplicate of bug 241049 ***