[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering

2019-05-07 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=353983

--- Comment #154 from Luca Mastromatteo  ---
Is that an NVIDIA driver issue? In that case has someone got in contact with
them? Because I recently found they have a mailing list for linux bugs and it
looks like they answer unlike their forum, just to let you know

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 403740] vsync doesn't handle different refresh rate monitors and doesn't work anymore

2019-01-29 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=403740

--- Comment #2 from Luca Mastromatteo  ---
Microsoft Windows doesn't seem to do that either, but what it does is
"dynamically switching" somehow the fps cap prioritizing the desktop you are
currently working at,

For example, having a game running on the first 144Hz monitor with vsync
enabled, then moving to the 60Hz one (like moving another window in there)
causes the game to be capped at 60fps, I tested that through a fps meter
Fullscreen games doesn't seem to be affected by this, but that's another thing.

Another test I made is checking if something on the second 60Hz monitor is
vsync-capped by running a game on the 1st 144Hz monitor, then also another one
in the 2nd and even in this case the v-sync does change it's fps cap depending
on the active window, 

this happens even with some windows, if there is a v-sync activity like a game
on the 60Hz monitor, moving to the 144Hz monitor causes windows movements to be
capped at 60fps (they are v-synced too I suppose) 


So maybe it could be work-arounded somehow?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 403740] New: vsync doesn't handle different refresh rate monitors and doesn't work anymore

2019-01-29 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=403740

Bug ID: 403740
   Summary: vsync doesn't handle different refresh rate monitors
and doesn't work anymore
   Product: kwin
   Version: 5.14.90
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: xrandr
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukycroci...@gmail.com
  Target Milestone: ---

SUMMARY

When desktop vsync is enabled, having two different monitors with different
refresh rates, causes the vsync to stop working

The two monitors are set into "extend" mode


STEPS TO REPRODUCE
1. Have two monitors with different refresh rates
2. Set the first monitor to 144Hz (for example)
3. Enable desktop vsync

OBSERVED RESULT
The vsync works only in the 2nd 60Hz monitor, when switching or moving
something to the first 144Hz one, stops working even when coming back to the
60Hz monitor, you can see the fps meters goes from 60 to 100 until I disable
and re-enable the option from the 60Hz monitor

EXPECTED RESULT
The vsync should work to 144fps in the first monitor, then 60 in the second
when switching back to another


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90, Ubuntu 19.04 Disco Dingo development version
QT 5.11.3
Kernel 4.18.0
Nvidia GPU w 410.93

ADDITIONAL INFORMATION

I have to say the vsync works even wrongly (60 fps instead of 144) when just
the single 144Hz monitor is set

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 402315] New: Desktop compositing not disabled in certain apps unlike GNOME

2018-12-18 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=402315

Bug ID: 402315
   Summary: Desktop compositing not disabled in certain apps
unlike GNOME
   Product: kwin
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukycroci...@gmail.com
  Target Milestone: ---

SUMMARY
I have noticed that with some applications, in particular some games I will
list later, the desktop compositing is not disabled automatically, causing
performance issues, unlike when using the GNOME desktop, where everything works
normally. Tested in Fullscreen mode.

I listed that as a wishlist because it seems that in GNOME everything works as
it should.

Game list that have this issue: Steam: Portal, Portal 2. 
Every wine game, except when using some custom wine builds.

STEPS TO REPRODUCE
1. Open the game in fullscreen mode

OBSERVED RESULT
Desktop compositing is not disabled

EXPECTED RESULT
Desktop compositing is disabled, like the GNOME desktop does

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 4.18
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 402150] New: Desktop icons corruption after resuming from sleep

2018-12-15 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=402150

Bug ID: 402150
   Summary: Desktop icons corruption after resuming from sleep
   Product: plasmashell
   Version: 5.13.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Icon Applet
  Assignee: plasma-b...@kde.org
  Reporter: lukycroci...@gmail.com
  Target Milestone: 1.0

Created attachment 116936
  --> https://bugs.kde.org/attachment.cgi?id=116936=edit
Screenshot of teh issue

SUMMARY
After resuming from standby, the desktop icons are glitched, probably only with
NVIDIA drivers.

STEPS TO REPRODUCE
1. Put the PC to sleep
2. Resume desktop from sleep, and login

OBSERVED RESULT

Desktop icons are corrupted and glitched (See screenshot)

EXPECTED RESULT
The desktop icons should be looking fine

WORKAROUND

The only way to fix that, is to move the icon on the desktop, as you can see
from the screenshot, I moved those two before taking the screenshot, they were
previously glitched.

SOFTWARE/OS VERSIONS

Linux: Ubuntu 18.10, Linux 4.18.0-12-generic kernel
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

Using nvidia drivers, GTX 1060, 415.23 version

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399246] Why desktop effects are still on when wine games are opened?

2018-10-31 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=399246

--- Comment #2 from Luca Mastromatteo  ---
Actually it's different than I though.

Native games disable desktop effects even if windowed, while wine games disable
desktop effects only when on fullscreen..

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399246] New: Why desktop effects are still on when wine games are opened?

2018-09-30 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=399246

Bug ID: 399246
   Summary: Why desktop effects are still on when wine games are
opened?
   Product: kwin
   Version: 5.13.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukycroci...@gmail.com
  Target Milestone: ---

That is not an annoying issue, but I've noticed the Kwin behaviour to disable
desktop effects when an OpenGL game is opened, reducing lag and increasing FPS.

However, using Steam with the Steam Play function, or running a wine game, with
DXVK or not, desktop effects are not disabled.
Seems like when a game is opened through wine, kwin does not detect it 

STEPS TO REPRODUCE
1. Open a wine game through steam play or just wine

OBSERVED RESULT
Desktop effects are not disabled like when running an opengl game without wine

EXPECTED RESULT
Desktop effects disabled

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdialog] [Bug 397069] New: Lack of options in Chromium, using kdialog

2018-08-01 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=397069

Bug ID: 397069
   Summary: Lack of options in Chromium, using kdialog
   Product: kdialog
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: lukycroci...@gmail.com
  Target Milestone: ---

Created attachment 114258
  --> https://bugs.kde.org/attachment.cgi?id=114258=edit
KDialog does not show any option when saving pages, when uninstalling kdialog,
the program whish chromium uses works

Basically I've got Kdialog installed in my system, and Chromium, when saving an
HTML page for example, uses it as it's first choice. 

The problem is that does not work properly, it integrates nicely with the
Plasma desktop but lacks in the typical chrome page-saving options, in fact,
when you save a web page in Chromium/Chrome, it lets you choose which component
you want to download, if just HTML, or HTML + Entire page, (See screenshot to
understand it better)

But, the only option I see when using kdialog is "HTML Document" and in fact it
does not save all the web page files since it does not let me to choose what to
save. So that is strange.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering

2018-05-16 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=353983

--- Comment #111 from Luca Mastromatteo <lukycroci...@gmail.com> ---
Today happened again, with no game opened, just DaVinci resolve and chromium
browser.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering

2018-05-11 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=353983

--- Comment #109 from Luca Mastromatteo <lukycroci...@gmail.com> ---
Having the same issue on an NVIDIA + Ryzen Desktop build... Sometimes I
workaround this by killing plasmashell and kwin_x11, glad to see I'm not alone.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 394146] Shell, and compositor become unusable due to opening games

2018-05-11 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=394146

--- Comment #1 from Luca Mastromatteo <lukycroci...@gmail.com> ---
Created attachment 112587
  --> https://bugs.kde.org/attachment.cgi?id=112587=edit
Video of showing a part of the issue

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 394146] New: Shell, and compositor become unusable due to opening games

2018-05-11 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=394146

Bug ID: 394146
   Summary: Shell, and compositor become unusable due to opening
games
   Product: kwin
   Version: 5.12.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukycroci...@gmail.com
  Target Milestone: ---

Summary: Hi, first of all I added this bug for kwin due to the fact that I
think it is releated to a strange kwin behaviour when stopping compositing for
games, it happens only when I open games or even steam, however it is not
always predictable. 
If I went wrong, I would kindly ask to change the product/component. Thanks.

Additional information: 
- Manjaro Linux updated to the latest version on 11/05/18
- Nvidia 396 Drivers
- Kernel 4.14

Steps to reproduce:

- Open Steam/Games, happens also with non-fullscreened games.
- Alt-Tab, or just move the mouse out the game

It happens sometimes. Like 40/50% of chance when you open an OpenGL Game. 

Actual result: The plasma shell becames unusuable, the windows tabs on the
taskbar doesn't update, the clock and other components too, they are like in a
"freezed" state like before I opened that game, If I click however it seem to
minimize/maximize windows but the content list does not update, if I close some
other window except the game, it remains the same. Another strange thing is
that for fullscreened games the compositing does not always turn off, in fact
there is a noticeable input delay (Don't always comes with the "freezed state"
plasma shell.

Workaround: Close the game fixes it every time, or killing the kwin_x11 process
or sometimes even the plasmashell process. Also sometimes CTRL + MAIUSC + F12
fixes the problem, other times not *

*There is even a strange thing, always "Sometimes" when even after I close the
game, pressing CTRL+MAIUSC+F12 which disables the compositor, turns back plasma
shell to the "freezed" state, but the OLD one. Even if I open other games
after. And doing that command once again it always SOMETIMES fix the "problem"
and everything goes back into normal when the compositor is either on or off, I
made a video for that. It is harder to explain and debug than the way it comes
out...

Expected result: Even with compositing off, the plasma shell should be usuable,
the window list in the taskbar usuable. CTRL+MAIUSC+F12 should just disable the
compositor, and fullscreen games should turn of the compositor without mess.


I was not able to to extract some logs due to the fact it does not always
happen, and I don't know the tools to use (gdb?) maybe they are wrong, I would
kindly ask the ones I have to use in order to (or at least try) to debug it
correctly.

They are a lot hard to debug due to the fact they are not predictable, however
I will do my best.

* In the video I show after an hour I played that game, pressing
CTRL+MAIUSC+F12 for turning off the compositing, even if I don't even
alt-tabbed once, made the usual shell freeze problem, and a second time
renabling the compositing "fixes" the problem, I don't know if it always works
for fixing

-- 
You are receiving this mail because:
You are watching all bug changes.

[user-manager] [Bug 362558] Better resize of user login avatar and/or option to resize it

2017-10-24 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=362558

Luca Mastromatteo <lukycroci...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksysguard] [Bug 383243] New: Processor usage table broken when the system has 12 cores

2017-08-07 Thread Luca Mastromatteo
https://bugs.kde.org/show_bug.cgi?id=383243

Bug ID: 383243
   Summary: Processor usage table broken when the system has 12
cores
   Product: ksysguard
   Version: 5.10.4
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: lukycroci...@gmail.com
  Target Milestone: ---

Created attachment 107128
  --> https://bugs.kde.org/attachment.cgi?id=107128=edit
Screenshot

I've recently upgraded my system to an AMD ryzen 5 1600 which has 6 cores and
12 threads. Coming from an i5, opening Ksysguard in the CPU usage graph nothing
is displayed correctly

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-07 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

--- Comment #2 from Luca Mastromatteo <lukycroci...@gmail.com> ---
Nothing interesting from the dmesg. 
And yes, it seems to be the blur effect, no artifacts after disabling it. 
I didn't know where to put this since I didn't had problems with this driver
since I've encountered in this.

Output of the command https://paste.kde.org/pg6yqrbf9

Running kwin from the terminal, with and without the option enabled in kwinrc
didn't changed anything.

QXcbConnection: XCB error: 3 (BadWindow), sequence: 176, resource id: 10485766,
major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1531, resource id: 88080425,
major code: 42 (SetInputFocus), minor code: 0
OpenGL vendor string:   X.Org
OpenGL renderer string: Gallium 0.4 on AMD TONGA (DRM 3.1.0,
LLVM 3.7.1)
OpenGL version string:  4.1 (Core Profile) Mesa 11.2.1
OpenGL shading language version string: 4.10
Driver: Unknown
GPU class:  Unknown
OpenGL version: 4.1
GLSL version:   4.10
Mesa version:   11.2.1
X server version:   1.18.3
Linux kernel version:   4.5.2
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1753, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1754, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1755, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1756, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1757, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1758, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1759, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1760, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1763, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1764, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1765, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1766, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1767, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1768, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1769, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1770, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QMetaProperty::read: Unable to handle unregistered datatype
'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface'

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 362788] New: Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-07 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

Bug ID: 362788
   Summary: Artifacts in the logout effect using amdgpu driver and
opengl renderer
   Product: kwin
   Version: unspecified
  Platform: Archlinux Packages
   URL: http://imgur.com/a/zcAzO
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: scene-opengl
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukycroci...@gmail.com

I've got two archlinux running on two different pcs, one running with an AMD R9
380 using the amdgpu driver, and the other one running an integrated skylake
iGPU. 
Basically, i've got artifacts when I push the logout button to exit my session,
this does not happen into the other PC running the intel iGPU.
The great thing is that this problem seems to occur only with the OpenGL
Renderer, and not with the XRender one. 
I was able to take some screenshots.

Reproducible: Always

Steps to Reproduce:
1. Press the logout button using the openGL renderer
2. Have a video card with the AMDGPU driver
3.

Actual Results:  
The fade animation has artifacts.

Expected Results:  
The animation should be normal

-- 
You are receiving this mail because:
You are watching all bug changes.


[systemsettings] [Bug 362558] New: Better resize of user login avatar and/or option to resize it

2016-05-01 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362558

Bug ID: 362558
   Summary: Better resize of user login avatar and/or option to
resize it
   Product: systemsettings
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: lukycroci...@gmail.com

The usual manner of adding an avatar for users on the PC, makes the result
avatar image very ugly. There is the need everytime to resize it manually using
GIMP or other programs.

There should be a better system to resize the image correctly, making it less
pixelated, or implement builtin resize/crop system, something like that is
already implemented in GNOME.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 362556] Right click on legacy GTK tray icons does not work.

2016-05-01 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362556

Luca Mastromatteo <lukycroci...@gmail.com> changed:

   What|Removed |Added

Summary|Right click on tray icon|Right click on legacy GTK
   |does not work.  |tray icons does not work.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 362556] New: Right click on tray icon does not work.

2016-05-01 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362556

Bug ID: 362556
   Summary: Right click on tray icon does not work.
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: lukycroci...@gmail.com

Right clicking on the legacy GTK icons, in the icon tray, nothing happens. 

Reproducible: Always

Steps to Reproduce:
1. Have a GTK program which uses GTK legacy icon trays. (Like Pamac, or
redshift)
2.
3.

Actual Results:  
Nothing happens.

Expected Results:  
After right clicking on them, there should be a dropdown menu.

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 356581] Bad performance even with "Suspend effects with fullscreen windows" in opengl games using fglrx

2015-12-13 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356581

--- Comment #4 from Luca Mastromatteo <lukycroci...@gmail.com> ---
and that's only for fglrx?

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 356581] Bad performance even with "Suspend effects with fullscreen windows" in opengl games using fglrx

2015-12-13 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356581

--- Comment #3 from Luca Mastromatteo <lukycroci...@gmail.com> ---
Really? So maybe was a placebo but months ago I wasn't having any
performance/input lag problem with some games, also with compiz, I don't need
to disable it. So I have to manually remove the compositor effects? With mate
desktop I'm not having this problem, the reason is clear.

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 356581] New: Bad performance even with "Suspend effects with fullscreen windows" in opengl games using fglrx

2015-12-12 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356581

Bug ID: 356581
   Summary: Bad performance even with "Suspend effects with
fullscreen windows" in opengl games using fglrx
   Product: kwin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: scene-opengl
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukycroci...@gmail.com

As I said, opengl fullscreen games have bad performance even if I checked the
"disable effetcs with fullscreen window", I'm using fglrx drivers.
The solution is disable effetcs with shift+alt+f12

Reproducible: Always

Steps to Reproduce:
1. Install fglrx driver
2. Check or uncheck the "Disable effects in fullscreen windows"
3. The performance in fullscreen games are always bad

Actual Results:  
Bad performance

Expected Results:  
The performance should be better

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 356366] Huge performance drop in opengl game after window change (No kwin-releated)

2015-12-07 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356366

--- Comment #1 from Luca Mastromatteo <lukycroci...@gmail.com> ---
UPDATE= The problem seems to occur also if I simply hover the cursor to the
game icon and then alt+tab to it.
Another way to fix instead of killing plasmashell is to hover to another icon
instead of the game one and then alt+tab. (ALT+TAB BEFORE HOVERING TO ANOTHER
ICON STILL CAUSE THE PERFORMANCE PROBLEM)

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 356366] New: Huge performance drop in opengl game after window change (No kwin-releated)

2015-12-07 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356366

Bug ID: 356366
   Summary: Huge performance drop in opengl game after window
change (No kwin-releated)
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
   URL: https://www.youtube.com/watch?v=0CnvDjhunDk
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lukycroci...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

That's an annoying problem, it only occurs in KDE Plasma, with fglrx drivers,
also changing the desktop compositor from kWIn to openbox. I'm not having this
problem with the open source drivers.
Basically, opening a game (Team fortress 2 in this case) and then alt+tab and
then clicking the taskbar icon to return to it, causes a huge performance drop
and input lag in the game. About from 300~fps to 150~
With just using alt+tab when returning to it the problem does not occur.
If I click the game from the taskbar once, alt+tab again to exit from it, and
return to it also with alt+tab still the same problem. (That means that the
problem occurs after i pressed once the icon in the taskbar to return to it,
also if I alt+tab again still the same problem, unless I kill the "plasmashell"
process. Here we return back to the beginning.)
That problem does not seem to be kwin/desktop compositor releated.

Reproducible: Always

Steps to Reproduce:
1.Install fglrx drivers
2.Run an opengl game (I was using Team Fortress 2 through Steam)
3.Alt+Tab
4.click on the game icon in the taskbar to return to it


Actual Results:  
The frame-per-second of the game dropped from 300~fps to 150~ 

Expected Results:  
The performance should be the same.

Arch Linux, latest version
Latest catalyst-test package from the AUR (also tried with other catalysts)

-- 
You are receiving this mail because:
You are watching all bug changes.