[kwin] [Bug 344326] Black or corrupted screen on resume from suspend
https://bugs.kde.org/show_bug.cgi?id=344326 --- Comment #81 from Ruslan Kabatsayev --- (In reply to Rafael from comment #79) > Another atypical issue I saw some time in the unlock screen is "crossed > text", that's to say, the text (and only the text) appeared like if you > put your eyes "crossed". I have some screenshot of this and will send here. It might be bug 307003. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 306338] konsole freezes when i select text
https://bugs.kde.org/show_bug.cgi?id=306338 Ruslan Kabatsayev changed: What|Removed |Added CC||b7.10110...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 367894] On GTK apps Windows drag mode incorrectly drags from non titlebar area
https://bugs.kde.org/show_bug.cgi?id=367894 --- Comment #2 from Ruslan Kabatsayev --- Are both GTK2 and GTK3 apps affected? Which apps exactly? -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 367894] On GTK apps Windows drag mode incorrectly drags from non titlebar area
https://bugs.kde.org/show_bug.cgi?id=367894 Ruslan Kabatsayev changed: What|Removed |Added Component|gtk3-engine |gtk2-engine --- Comment #3 from Ruslan Kabatsayev --- Ah sorry, I see some mentioned in the OP. These are GTK2. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 367894] On GTK apps Windows drag mode incorrectly drags from non titlebar area
https://bugs.kde.org/show_bug.cgi?id=367894 Ruslan Kabatsayev changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Ruslan Kabatsayev --- OK, apparently Oxygen-Qt has changed the way it handles its config. Previously there was [Style]/WindowDragEnabled, which you could set to false in ~/.kde/share/config/oxygenrc. Now this option seems to have been dropped, and a new mode has been added: WD_NONE. To work around this problem, in ~/.kde/share/config/oxygenrc after WindowDragMode=WD_NONE add this: WindowDragEnabled=false -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364201] No button icons are shown for most buttons in Window Decoration settings
https://bugs.kde.org/show_bug.cgi?id=364201 Ruslan Kabatsayev changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #8 from Ruslan Kabatsayev --- I've checked this on live image of Kubuntu 16.04, and it doesn't show this bug. Apparently this is a buggy upgrade process, which led to this, not a problem with KWin itself. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 367894] On GTK apps Windows drag mode incorrectly drags from non titlebar area
https://bugs.kde.org/show_bug.cgi?id=367894 --- Comment #6 from Ruslan Kabatsayev --- Can you confirm that this problem appears despite this line being present in ~/.kde/share/config/oxygenrc in KDE session while using oxygen-gtk with pidgin? I can't reproduce this in Kubuntu Xenial live image run in QEMU. For me this line "fixes" the problem. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 367894] On GTK apps Windows drag mode incorrectly drags from non titlebar area
https://bugs.kde.org/show_bug.cgi?id=367894 --- Comment #8 from Ruslan Kabatsayev --- Firefox, Chrome and Thunderbird are not real GTK programs. Oxygen-GTK can't force such behavior in these apps even when it wants to. This must be a problem in something else (maybe some Kubuntu-specific plugins for XUL and something in Chrome/Chromium). -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 360019] unison-gtk alwasy chrash when i use the oxygen-gtk theme
https://bugs.kde.org/show_bug.cgi?id=360019 Ruslan Kabatsayev changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ruslan Kabatsayev --- It's a GTK bug, not oxygen's. If you change "appears-as-list = 1" to "appears-as-list = 0" in /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc , you'll work around this bug. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364115] New: A seam is present between window decoration and window background
https://bugs.kde.org/show_bug.cgi?id=364115 Bug ID: 364115 Summary: A seam is present between window decoration and window background Product: Oxygen Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: style Assignee: hugo.pereira.da.co...@gmail.com Reporter: b7.10110...@gmail.com I'll add some screenshots. Basically, if you set a dark color scheme, e.g. Obsidian Coast, you'll notice a dark line just above the bottom line of the topmost stripe of single color (neglecting the radial gradient). You can see it more easily if you increase brightness and contrast of a screenshot. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364115] A seam is present between window decoration and window background
https://bugs.kde.org/show_bug.cgi?id=364115 --- Comment #1 from Ruslan Kabatsayev --- Created attachment 99417 --> https://bugs.kde.org/attachment.cgi?id=99417&action=edit Screenshot This is an unmodified screenshot of the problem. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364115] A seam is present between window decoration and window background
https://bugs.kde.org/show_bug.cgi?id=364115 --- Comment #2 from Ruslan Kabatsayev --- Created attachment 99418 --> https://bugs.kde.org/attachment.cgi?id=99418&action=edit Screenshot with increased brightness and contrast This screenshot has increased brightness and contrast to easier see what to look for when debugging. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355696] Plasmashell hangs at icon removeing from panel
https://bugs.kde.org/show_bug.cgi?id=355696 Ruslan Kabatsayev changed: What|Removed |Added CC||b7.10110...@gmail.com --- Comment #3 from Ruslan Kabatsayev --- I can reproduce the hang in QQuickWindowPrivate::polishItems() by simply suspending to RAM and resuming my machine. Then some notification appears, but isn't drawn: just a rectangle with garbage contents, and plasma is hung. I attach to it via gdb, and repeatedly executing "fin" command finally shows that the hanging function is QQuickWindowPrivate::polishItems(). -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 348790] oxygen-transparent kf5 fails to compile against modern KDE Frameworks
https://bugs.kde.org/show_bug.cgi?id=348790 Ruslan Kabatsayev changed: What|Removed |Added CC||b7.10110...@gmail.com --- Comment #3 from Ruslan Kabatsayev --- DIRTY_HACK_BEGIN You can force re-creation of the X11 window if you find a way to reliably call protected members QWindow::destroy() and QWindow::create(). Here's an example with undefined behavior, but which is almost guaranteed to work (and does work in my experiments): struct Hack : QWindow { void doRecreate() { destroy(); create(); } }; // ... widget->setAttribute( Qt::WA_TranslucentBackground ); // Apply the flag (has UB, but works) if(widget->windowHandle()) static_cast(widget->windowHandle())->doRecreate(); This makes it somewhat work when I try this on K4Oxygen [1]. Somewhat because for some reason blur and other properties are not preserved, although I think this is fixable. [1]: https://github.com/10110111/k4oxygen/commit/ff0960d241fdd79cfa5f5c85de51316ae303e7d2 Yes, I love hacks :D -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 348790] oxygen-transparent kf5 fails to compile against modern KDE Frameworks
https://bugs.kde.org/show_bug.cgi?id=348790 --- Comment #4 from Ruslan Kabatsayev --- In fact, it doesn't have to be done using UB: struct Hack : QWindow { static void recreateWindow(QWindow* w) { w->destroy(); w->create(); } }; The problem remains though that widget->winId() and widget->internalWinId() no longer match widget->windowHandle()->winId(). This means that all the other helpers like BlurHelper should use the latter. This also means that the integrity of QWidget is now somewhat broken, and the behavior can be hard to predict. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 348790] oxygen-transparent kf5 fails to compile against modern KDE Frameworks
https://bugs.kde.org/show_bug.cgi?id=348790 --- Comment #5 from Ruslan Kabatsayev --- OK, the winId problem is also easy to solve: it's enough to send QEvent::ScreenChangeInternal to the widget. So the proof of concept is here (this is fourth commit in the series, see actual code inside the #if-#endif or parent commits to see how it works): https://github.com/10110111/k4oxygen/commit/5e21080da0eb72a33ec007681d303733dc69b99e -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 326043] Oxygen-Transparent breaks kpartsplugin embedding (a.k.a. xembed)
https://bugs.kde.org/show_bug.cgi?id=326043 Ruslan Kabatsayev changed: What|Removed |Added CC||b7.10110...@gmail.com --- Comment #10 from Ruslan Kabatsayev --- > P.S. this only affect Qt4 version since the Qt5 never recreate the window > (for now). Actually it does recreate window on screen change. What's more problematic with Qt5 is that it seems that all toplevel windows have _XEMBED_INFO property set, so it'll be hard to detect kpartsplugin this way. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364194] New: Now way to tell windows apart and to find which window is active when compositing is off
https://bugs.kde.org/show_bug.cgi?id=364194 Bug ID: 364194 Summary: Now way to tell windows apart and to find which window is active when compositing is off Product: Oxygen Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: win deco Assignee: hugo.pereira.da.co...@gmail.com Reporter: b7.10110...@gmail.com In KF5 oxygen window decorations now lack "ugly shadows" which in KDE4 served at least two purposes: 1. Visually separate different windows 2. Indicate which window is active (similarly to shadow vs glow) In KF5, since no ugly shadows are drawn, oxygen window decoration without compositing is unusable. I'll attach a screenshot. Reproducible: Always Steps to Reproduce: 1. Turn off compositing 2. Open System Settings, on a page where much of the background is system background color — e.g. Compositor page 3. Open Konsole, move the window over the one opened in step 2, so that Konsole top is near the top of System Settings window top 4. Try to tell: a) where Konsole window ends and System Settings starts b) which one is active when you move them apart so that they don't overlap Actual Results: Step 4 is quite hard to do. Expected Results: Step 4 should be at least as easy as it was in KDE4. Tested on stock Kubuntu 16.04 LiveISO. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364194] Now way to tell windows apart and to find which window is active when compositing is off
https://bugs.kde.org/show_bug.cgi?id=364194 --- Comment #1 from Ruslan Kabatsayev --- Created attachment 99443 --> https://bugs.kde.org/attachment.cgi?id=99443&action=edit Screenshot of the problem -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364201] No button icons are shown for most buttons in Window Decoration settings
https://bugs.kde.org/show_bug.cgi?id=364201 --- Comment #1 from Ruslan Kabatsayev --- Created attachment 99450 --> https://bugs.kde.org/attachment.cgi?id=99450&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364201] New: No button icons are shown for most buttons in Window Decoration settings
https://bugs.kde.org/show_bug.cgi?id=364201 Bug ID: 364201 Summary: No button icons are shown for most buttons in Window Decoration settings Product: systemsettings Version: 5.6.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_style Assignee: tibi...@kde.org Reporter: b7.10110...@gmail.com No button icons are shown for most buttons in Window Decoration settings. Reproducible: Always Steps to Reproduce: 1. Open System Settings 2. Go to Application Style->Window Decorations->Buttons Actual Results: Most icons for buttons missing, and when you try dragging the text, you miss when trying to place it on the "Titlebar" part of the widget, because the button's symbol which appears above the dragged text is almost invisible, and the text itself seems to not be a valid object to place. Expected Results: All buttons, not just Menu and Close ones, should be visible — at least some placeholders for them, if no icons are available. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364201] No button icons are shown for most buttons in Window Decoration settings
https://bugs.kde.org/show_bug.cgi?id=364201 --- Comment #3 from Ruslan Kabatsayev --- i think I do: it's the default decoration on Kubuntu. In the list of decorations it's called "org.kde.breeze". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364201] No button icons are shown for most buttons in Window Decoration settings
https://bugs.kde.org/show_bug.cgi?id=364201 --- Comment #5 from Ruslan Kabatsayev --- I do have Breeze icon theme, but even selecting it as current theme doesn't show the windeco button icons, although all other icons do change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364201] No button icons are shown for most buttons in Window Decoration settings
https://bugs.kde.org/show_bug.cgi?id=364201 --- Comment #7 from Ruslan Kabatsayev --- Yes, I restarted it. In fact, even without restart the menu icon had changed to Breeze version of it. But the others except "close" still remain invisible. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364693] When upgrading from Qt5.4 to Qt5.6, the color and theme handling ignores local settings
https://bugs.kde.org/show_bug.cgi?id=364693 --- Comment #3 from Ruslan Kabatsayev --- You can compile oxygen-gtk passing -DOXYGEN_DEBUG=1 to cmake. Then you'll get tons of debug output when you start GTK2 apps - including info about config it loads. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364693] When upgrading from Qt5.4 to Qt5.6, the color and theme handling ignores local settings
https://bugs.kde.org/show_bug.cgi?id=364693 --- Comment #4 from Ruslan Kabatsayev --- @Hugo Is kde4-config optional in KF5? It seems to be there with the default install. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 --- Comment #60 from Ruslan Kabatsayev --- Created attachment 99068 --> https://bugs.kde.org/attachment.cgi?id=99068&action=edit Attempt to fix in Qt I'm not sure whether this patch for Qt4 even goes in the right direction, but it does appear to fix this problem for me with US+Russian layouts, regardless of which layout is primary. I guess it might break with e.g. US+AZERTY or other cases when all layouts are Latin, I didn't check this yet. Maybe someone could constructively criticize my approach so that I could do it in a better way. Didn't try to submit it to Qt, since 1) not sure if it's the right approach and 2) Qt bug 15319 is closed. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 354633] [ntfs] ktorrent freezes very often
https://bugs.kde.org/show_bug.cgi?id=354633 Ruslan Kabatsayev changed: What|Removed |Added CC||b7.10110...@gmail.com --- Comment #24 from Ruslan Kabatsayev --- Could this fix be somehow backported to KTorrent 4.3? I'm experiencing the same problem on Kubuntu 14.04 LTS with this version and NTFS destination. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 340288] Port to CSS as GTK+3.15.0 doesn't load theme engines
https://bugs.kde.org/show_bug.cgi?id=340288 Ruslan Kabatsayev changed: What|Removed |Added CC||dar...@darose.net --- Comment #5 from Ruslan Kabatsayev --- *** Bug 356845 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 Ruslan Kabatsayev changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Ruslan Kabatsayev --- *** This bug has been marked as a duplicate of bug 340288 *** -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 --- Comment #7 from Ruslan Kabatsayev --- GTK3 is binary incompatible with GTK2, and it uses CSS to do all its theming now. So no way to use oxygen-gtk2 with GTK3 apps. Your only option is to downgrade GTK3, although some GTK3 apps might require the features introduced in 3.15 and higher. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 362197] New: Scrollback buffer loses data when it grows large enough
https://bugs.kde.org/show_bug.cgi?id=362197 Bug ID: 362197 Summary: Scrollback buffer loses data when it grows large enough Product: konsole Version: 15.08.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: b7.10110...@gmail.com This can be reproduced with the following bash command: i=0; while true; do echo "$i $i $i $i $i $i $i $i $i $i $i" >&2; i=$((i+1)); done Once the numbers printed grow larger than about 2.1 million, Konsole starts repeatedly printing a message to its parent terminal: HistoryFile::add.seek: Invalid argument And if you try to scroll back, you'll see empty lines right above the first visible line. If you scroll more back, you'll get to the last line which has successfully been appended to the scrollback buffer. Saving the scrollback also gives this result, i.e. lines between the last screen and last successful scrollback update are completely empty. Reproducible: Always Steps to Reproduce: 0. Set scrollback to Unlimited in Konsole settings 1. Run Konsole (from another terminal to see its stderr) 2. Run this command in bash inside Konsole session: i=0; while true; do echo "$i $i $i $i $i $i $i $i $i $i $i" >&2; i=$((i+1)); done 3. Wait until numbers printed grow larger than about 2.1 million 4. Try to scroll back Actual Results: Nearest scrollback lines get lost Expected Results: The complete scrollback buffer should be saved correctly This happens both in KDE 4.14 and KF5. -- You are receiving this mail because: You are watching all bug changes.