| Summary: | Restored maximized windows can't be minimized | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Gabriel C <nix.or.die> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde.org, nix.or.die |
| Priority: | NOR | ||
| Version First Reported In: | 5.9.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Gabriel C
2016-10-19 13:33:55 UTC
What do you mean with "No way to minimize?" How did you try to minimize? With the 'minimize' button from the decoration. Also I found out every app is fine with -session and will minimize / mazimize but not when kwin_x11 starts with -session. Also I get lots : conversion of \"0,0,0,0\" to QRect failed from fsrestoreX= and restoreX= .. here is a partial valgrind log from 5.9.2.. ==27531== Command: kwin_x11 -session 10e1776572000148787086900000239150010_1487871669_986439 --replace ==27531== QXcbConnection: XCB error: 3 (BadWindow), sequence: 178, resource id: 2097158, major code: 20 (GetProperty), minor code: 0 "\"restore1\" - conversion of \"0,0,0,0\" to QRect failed" "\"restore2\" - conversion of \"0,0,0,1048\" to QRect failed" GAB: isManaged() ==27531== Syscall param writev(vector[...]) points to uninitialised byte(s) ==27531== at 0x512946D: ??? (in /lib/libc-2.24.so) ==27531== by 0x610449C: ??? (in /usr/lib/libxcb.so.1.1.0) ==27531== by 0x610489C: ??? (in /usr/lib/libxcb.so.1.1.0) ==27531== by 0x6104AF6: ??? (in /usr/lib/libxcb.so.1.1.0) ==27531== by 0x61052CB: xcb_flush (in /usr/lib/libxcb.so.1.1.0) ==27531== by 0x55C5507: KWin::Client::sendSyntheticConfigureNotify() (geometry.cpp:1581) ==27531== by 0x55C7A3C: KWin::Client::setGeometry(int, int, int, int, KWin::AbstractClient::ForceGeometry_t) (geometry.cpp:1978) ==27531== by 0x55095A4: KWin::AbstractClient::setGeometry(QRect const&, KWin::AbstractClient::ForceGeometry_t) (abstract_client.h:1086) ==27531== by 0x55C8B1D: KWin::AbstractClient::blockGeometryUpdates(bool) (geometry.cpp:2137) ==27531== by 0x55A0C60: KWin::Client::manage(unsigned int, bool) (manage.cpp:646) ==27531== by 0x54CD04C: KWin::Workspace::createClient(unsigned int, bool) (workspace.cpp:520) ==27531== by 0x54CC148: KWin::Workspace::init() (workspace.cpp:327) ==27531== Address 0x1bbfa6f8 is 4,936 bytes inside a block of size 21,152 alloc'd ==27531== at 0x4C2D765: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==27531== by 0x6103E7B: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.1.0) ==27531== by 0x6107BB0: xcb_connect_to_display_with_auth_info (in /usr/lib/libxcb.so.1.1.0) ==27531== by 0xD5A5989: _XConnectXCB (in /usr/lib/libX11.so.6.3.0) ==27531== by 0xD596EBE: XOpenDisplay (in /usr/lib/libX11.so.6.3.0) ==27531== by 0x22C171A7: QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (qxcbconnection.cpp:581) ==27531== by 0x22C1B5FB: QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (qxcbintegration.cpp:186) ==27531== by 0x40265EC: QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) (qxcbmain.cpp:56) ==27531== by 0x6FA3188: QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (qplatformintegrationfactory.cpp:71) ==27531== by 0x6FB0903: init_platform (qguiapplication.cpp:1094) ==27531== by 0x6FB0903: QGuiApplicationPrivate::createPlatformIntegration() (qguiapplication.cpp:1257) ==27531== by 0x6FB15E4: QGuiApplicationPrivate::createEventDispatcher() (qguiapplication.cpp:1274) ==27531== by 0x76138EF: QCoreApplicationPrivate::init() (qcoreapplication.cpp:787) .. These GAB messages are just some qDebug() I've added around , there is no code changes. There an small video to demonstrate this : http://ftp.frugalware.org/pub/other/people/crazy/vokoscreen-2017-02-24_16-37-11.mkv Still an bug in plasma 5.10.0 Still an bug in 5.10.2 This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23? (In reply to kde.org from comment #6) > This issue report is quite old. Can you please confirm, that it still > persists with KDE 5.23? Yes that issue still exists. 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! 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! |