Bug 374393 - Radeon: Freeze for long periods, until an action like Alt+Shift+F12 wakes it up
Summary: Radeon: Freeze for long periods, until an action like Alt+Shift+F12 wakes it up
Status: RESOLVED DUPLICATE of bug 373427
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.8.4
Platform: Debian testing Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-31 12:15 UTC by Alex Dănilă
Modified: 2017-01-19 02:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Dănilă 2016-12-31 12:15:19 UTC
On 2 laptops with Radeon graphics, all things related to Plasma panel (taskbar, clock, launcher, tray) freeze for an indefinite period of time; actually hang, they may start working again. The processor usage stays at 0, and Plasma can also be triggered to work correctly again:
- press Ctrl+Alt+F1 and Ctrl+Alt+F7 again
- press Alt+shift+f12 to change compositing settings
- restart process plasmashell

Other functions appear to work correctly (Alt+Tab switches windows correctly, Alt+CapsLock switches the input language, although the indicator remains still).

May be Radeon related, doesn't happen on other computers with Intel or Nvidia graphics. Also seems more likely to happen if an video is displayed in a browser, but may not be relevant.

Both on Debian Testing and Unstable.
Comment 1 Alex Dănilă 2016-12-31 12:28:08 UTC
More notes:
- Alt+F2 (Krunner) works correctly during this type of freeze
- right click on the desktop has no effect and the small square with three lines on the upper left doesn't work (but showing the window list by moving the cursor in the corner works correctly).
Comment 2 Alex Dănilă 2017-01-01 12:47:06 UTC
plasmashell process can be stopped with "kill", there's no need for "kill -9", I just notice today.
Comment 4 David Edmundson 2017-01-19 02:42:07 UTC

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