Bug 1226371 - Plasmashell hangs randomly in futex during overnight periods of inactivity
Summary: Plasmashell hangs randomly in futex during overnight periods of inactivity
Keywords:
Status: CLOSED DUPLICATE of bug 1193742
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-29 15:01 UTC by Penelope Fudd
Modified: 2015-06-02 06:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-02 06:48:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Penelope Fudd 2015-05-29 15:01:36 UTC
Frequently I unlock my screen to find the plasmashell panel has locked up (clock stopped updating, nothing clickable).  If I kill plasmashell and restart it, it starts working again and I can continue my session.  plasma-workspace-5.3.0-6.fc22.x86_64.rpm

Comment 1 Rex Dieter 2015-05-29 15:06:55 UTC
Depending on your driver, it could be dup of bug #1193742 or one of it's friends.

Are you using intel video driver?

Comment 2 Penelope Fudd 2015-06-02 06:48:01 UTC
Apparently (lspci -v), yes I am:

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	DeviceName:  Onboard IGD
	Subsystem: ZOTAC International (MCO) Ltd. Device b211
	Flags: bus master, fast devsel, latency 0, IRQ 29
	Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
	Kernel modules: i915

I guess this makes this a duplicate of bug #1193742.

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


Note You need to log in before you can comment on or make changes to this bug.