Description of problem: The KDE Plasma panel is freezing every so often so I cannot use the task switcher, menu launcher or panel applets and the clock is frozen at a certain time and not refreshing either. The rest of the desktop workspace is functioning normally. Version-Release number of selected component (if applicable): Fedora 21 KDE Plasma 5.2 64 bit How reproducible: Happening intermittently - do not know precise steps to reproduce. Steps to Reproduce: 1. After a lengthy period of normal KDE use, the panel freezes up. 2. 3. Actual results: You cannot use the KDE Menu, click on apps to switch via the task switcher or click on panel applets (like the volume control). The clock appears "frozen" so it is not refreshing with the current time. Expected results: The panel should not freeze. The panel clock should display the correct time. Additional info: I can still task switch using alt-tab and launch applications via alt-F2 so normal desktop functionality is not impeded. It is only the panel that appears "frozen". I have not tried killing the process and restarting it at this stage.
Could you please run plasma with following: QT_LOGGING_RULES="* = true qt.* = false" plasmashell &> plasmashell.log (the newline in the env var is intentional and necessary) and provide the log when Plasma freezes? Maybe it will give us some idea. It would also be great if you could try to get a backtrace of the plasmashell process when it freezes.
Assuming intel drivers here, helio got a backtrace: #0 0x0000003846a0c590 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x0000003bc9a0a3d9 in _xcb_conn_wait (c=c@entry=0x147d4f0, cond=cond@entry=0x119f99a8, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:427 #2 0x0000003bc9a0b639 in xcb_wait_for_special_event (c=c@entry=0x147d4f0, se=0x119f9980) at xcb_in.c:716 #3 0x0000003bcb24e034 in dri3_find_back (c=c@entry=0x147d4f0, priv=priv@entry=0x89442e0) at dri3_glx.c:1263 #4 0x0000003bcb24e71d in dri3_get_buffer (format=format@entry=4107, buffer_type=buffer_type@entry=dri3_buffer_back, loaderPrivate=loaderPrivate@entry=0x89442e0, driDrawable=0x8f3fc50) at dri3_glx.c:1289 #5 0x0000003bcb24f38a in dri3_get_buffers (driDrawable=driDrawable@entry=0x8f3fc50, format=4107, stamp=stamp@entry=0x8f3fc80, loaderPrivate=loaderPrivate@entry=0x89442e0, buffer_mask=<optimized out>, buffer_mask@entry=1, buffers=buffers@entry=0x7ffd03e437a0) at dri3_glx.c:1466 #6 0x00007f7be3baae97 in intel_update_renderbuffers (drawable=0x8f3fc50, brw=0x24b3a78) at brw_context.c:1475 #7 0x00007f7be3baae97 in intel_update_renderbuffers (context=context@entry=0x24aaad0, drawable=drawable@entry=0x8f3fc50) at brw_context.c:1167 #8 0x00007f7be3bab1c5 in intel_prepare_render (brw=brw@entry=0x24b3a78) at brw_context.c:1188 #9 0x00007f7be3b9fbad in brw_clear (ctx=0x24b3a78, mask=50) at brw_clear.c:234 #10 0x0000003217f336b7 in QSGBatchRenderer::Renderer::renderBatches() (this=this@entry=0x6095eb0) at /usr/src/debug/qtdeclarative-opensource-src-5.4.1/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:2402 and seems to match upstream bugs, https://bugs.kde.org/show_bug.cgi?id=341951 https://bugs.freedesktop.org/show_bug.cgi?id=84252
I can confirm this in both F21 and F22, and only on Intel graphics chips. I was just attempting to turn compositing off when my plasmashell locked up hard - the only thing responding is the mouse cursor, and only to move around the screen. It will not click on anything, or activate any mouseover events. A segfault was recorded in the journal: Apr 2 15:31:00 dmfedora kernel: [97423.099872] QXcbEventReader[14400]: segfault at 7f9833b02959 ip 00007f9833b02959 sp 00007f9831310d60 error 14 in locale-archive[7f9833b92000+6573000] Apr 2 15:31:00 dmfedora kernel: QXcbEventReader[14400]: segfault at 7f9833b02959 ip 00007f9833b02959 sp 00007f9831310d60 error 14 in locale-archive[7f9833b92000+6573000] Apr 2 15:31:01 dmfedora abrt-server: Package 'plasma-systemsettings' isn't signed with proper key Apr 2 15:31:01 dmfedora abrt-server: 'post-create' on '/var/tmp/abrt/ccpp-2015-04-02-15:31:00-14399' exited with 1 Apr 2 15:31:01 dmfedora abrt-server: Deleting problem directory '/var/tmp/abrt/ccpp-2015-04-02-15:31:00-14399'
Triaging to intel driver, per upstream bugs, https://bugs.kde.org/show_bug.cgi?id=341951 https://bugs.freedesktop.org/show_bug.cgi?id=84252
Gents, I have just returned to this bug. Apologies for the delay in responding. I am running a Lenovo T540p. With regard to graphics card information, lspci -v tells me this: *************************** 0:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) Subsystem: Lenovo Device 2210 Flags: bus master, fast devsel, latency 0 Capabilities: <access denied> Kernel modules: ie31200_edac 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 2210 Flags: bus master, fast devsel, latency 0, IRQ 28 Memory at f0000000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Lenovo Device 2210 Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at f1630000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device 2210 Flags: bus master, medium devsel, latency 0, IRQ 25 Memory at f1620000 (64-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Lenovo Device 2210 Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f1639000 (64-bit, non-prefetchable) [size=16] Capabilities: <access denied> Kernel driver in use: mei_me Kernel modules: mei_me 00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller (rev 04) (prog-if 02 [16550]) Subsystem: Lenovo Device 2210 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17 I/O ports at 40b0 [size=8] Memory at f1640000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: serial 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04) Subsystem: Lenovo Device 2210 Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at f1600000 (32-bit, non-prefetchable) [size=128K] Memory at f163f000 (32-bit, non-prefetchable) [size=4K] I/O ports at 4080 [size=32] Capabilities: <access denied> Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: Lenovo Device 2210 Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f163e000 (32-bit, non-prefetchable) [size=1K] Capabilities: <access denied> Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) Subsystem: Lenovo Device 2210 Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f1634000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: f1500000-f15fffff Capabilities: <access denied> Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 17 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 Memory behind bridge: f1400000-f14fffff Capabilities: <access denied> Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 18 Bus: primary=00, secondary=05, subordinate=0c, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: f0c00000-f13fffff Prefetchable memory behind bridge: 00000000f0400000-00000000f0bfffff Capabilities: <access denied> Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) (prog-if 20 [EHCI]) Subsystem: Lenovo Device 2210 Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at f163d000 (32-bit, non-prefetchable) [size=1K] Capabilities: <access denied> Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04) Subsystem: Lenovo Device 2210 Flags: bus master, medium devsel, latency 0 Capabilities: <access denied> Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: Lenovo Device 2210 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 24 I/O ports at 40a8 [size=8] I/O ports at 40bc [size=4] I/O ports at 40a0 [size=8] I/O ports at 40b8 [size=4] I/O ports at 4060 [size=32] Memory at f163c000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied> Kernel driver in use: ahci 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) Subsystem: Lenovo Device 2210 Flags: medium devsel, IRQ 18 Memory at f1638000 (64-bit, non-prefetchable) [size=256] I/O ports at efa0 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) Subsystem: Lenovo Device 2210 Flags: bus master, fast devsel, latency 0, IRQ 26 Memory at f1500000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at f1400000 (64-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi *************************** I have upgraded to the Fedora 22 Beta and I am still seeing this behaviour. It seems to happen after I have locked and unlocked my desktop 2-3 times. I have set it up to trace so I will capture it for you the next time it happens. Thanks. :)
Created attachment 1020783 [details] It just froze again so I have attached the plasmashell.log that Daniel Vrátil requested. As per my last comment, it froze after I had locked the Desktop for an hour when I was away from the screen.
I have had this happen overnight on my desktop, which has a radeon card in it.
This is happening to me upon login. Can't run gnome nor kde as of the last couple of weeks. Also yum doesn't work, it wants to download f22 instead of f21 packages, while dnf seems to work.
Just noticed upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=84252 is against xcb, reassigning to proper component
F22 scratch build with patch from, # https://bugs.freedesktop.org/show_bug.cgi?id=84252#c49 http://koji.fedoraproject.org/koji/taskinfo?taskID=9793022
Fresh scratch builds to trump recently submitted libxcb updates: F22: http://koji.fedoraproject.org/koji/taskinfo?taskID=9805670 F21: http://koji.fedoraproject.org/koji/taskinfo?taskID=9805676
Hi, I am seeing similar behavior with the "panel" at the bottom of the desktop AND right button click in the desktop fails to produce the usual popup menu. I am trapping the output from the startx command and am seeing a ton of messages like this one but there's NO timestamp on any of these messages so who knows when they happens? QXcbConnection: XCB error: 3 (BadWindow), sequence: 58618, resource id: 100663297, major code: 18 (ChangeProperty), minor code: 0 /var/log/Xorg.0.log has messages and maybe what is a timestanp but whatever it is is indecypherable. Maybe a timestamp in human readable format would be a good idea? [444240.941] (II) SYN_DROPPED event from "Logitech Logitech USB Optical Mouse" - some input events have been lost.
*** Bug 1223172 has been marked as a duplicate of this bug. ***
Hi, With this latest round of KDE updates, the problem(s) seem to still exist. I'm gonna try abandoning my current .kde directory/files and see where this leads. I'll post the results here. George...
Hi, I had to "stash" .config and .local to get a "brand new" KDE setup. So far, configuration seems to be functioning. I'll try saving a session later and post my results. Using Plasma/Breeze. George...
Fwiw, I've not experienced a single plasmashell hang since upgrading to dri2-enabled intel driver in linked bug #1223477 https://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.99.917-9.20150520.fc22 I think we may have a winner there.
(In reply to Rex Dieter from comment #11) > Fresh scratch builds to trump recently submitted libxcb updates: > > F22: http://koji.fedoraproject.org/koji/taskinfo?taskID=9805670 > F21: http://koji.fedoraproject.org/koji/taskinfo?taskID=9805676 Haven't seen any plasma freeze since upgrading to this xcb scratch build.
Hi, I don't know if this is a plasmashell problem but my panel at the bottom of the desktop is dead or frozen. There's a strip across the bottom of the desktop (all 3 for me) just about the size of the panel. I have a startx.log with a bazillian messages like this one: QXcbConnection: XCB error: 3 (BadWindow), sequence: 29690, resource id: 104857601, major code: 18 (ChangeProperty), minor code: 0 Also, the desktop menu is NOT responsive. This system has been up for two days and eleven minutes. Plasmashell is still in the runlist but and is spending a lot of time in "futex" according to strace IF this is the problem. Do you need more info? George...
Yes, plasmashell froze for you. What video driver are you using? I just experienced a deadlock this morning, first one since updating to dri2-enabled intel driver, Thread 1 (Thread 0x7f19b1061900 (LWP 1649)): #0 0x00007f19a8f4566d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f19af335182 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00007f19af336aa7 in wait_for_reply () at /lib64/libxcb.so.1 #3 0x00007f19af336bb1 in xcb_wait_for_reply () at /lib64/libxcb.so.1 #4 0x00007f19af7a21f7 in _XReply (dpy=dpy@entry=0x20cf100, rep=rep@entry=0x7ffc3be08160, extra=extra@entry=0, discard=discard@entry=0) at xcb_io.c:602 #5 0x00007f19a83e718a in DRI2GetBuffersWithFormat (dpy=0x20cf100, drawable=48234519, width=width@entry=0x8050198, height=height@entry=0x805019c, attachments=0x7ffc3be08270, count=1, outCount=0x7ffc3be0824c) at dri2.c:490 #6 0x00007f19a83e74c7 in dri2GetBuffersWithFormat (driDrawable=<optimized out>, width=0x8050198, height=0x805019c, attachments=<optimized out>, count=<optimized out>, out_count=0x7ffc3be0824c, loaderPrivate=0x88058f0) at dri2_glx.c:900 #7 0x00007f1989409c1b in intel_update_renderbuffers (buffer_count=0x7ffc3be0824c, buffers=<synthetic pointer>, drawable=0x8050170, brw=0x371dfe8) at brw_context.c:1307 #8 0x00007f1989409c1b in intel_update_renderbuffers (drawable=0x8050170, brw=0x371dfe8) at brw_context.c:1123 #9 0x00007f1989409c1b in intel_update_renderbuffers (context=context@entry=0x21b5230, drawable=drawable@entry=0x8050170) at brw_context.c:1179 #10 0x00007f198940a135 in intel_prepare_render (brw=brw@entry=0x371dfe8) at brw_context.c:1198 #11 0x00007f19893fe670 in brw_clear (ctx=0x371dfe8, mask=50) at brw_clear.c:234 #12 0x00007f19ae472baa in QSGBatchRenderer::Renderer::renderBatches() (this=this@entry=0x4b79fa0) at /usr/src/debug/qtdeclarative-opensource-src-5.4.1/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:2402
Rex, nouveau is disabled on my system via blacklist because of the mouse pointer problems. As far as I can tell, the driver is Intel, at least this is what the startx.log file I create whenever I startx says. modeset=0 is also in the /boot/grub2/grub.cfg linux16 /vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/sda2 ro LANG=en_US.UTF-8 modeset=0 George...
Rex, I just had to force a reboot of my system due to an apparent freeze. I let it sit for over an hour, thinking it might be severely memory constrained but EVERYTHING seemed to be frozen. I run xosview and iostat and iotop and they were frozen too... mouse pointer frozen... ctrl-alt-f2 was unresponsive. Is this similar to what you've seen? Regards, George...
OK, your latest issue (full freeze) is different that this one. This bug is about *only* plasmashell freezing (panel, desktop, application menu), applications, mouse, krunner still work.
*** Bug 1226371 has been marked as a duplicate of this bug. ***
I've got the plasma-shell freeze where only the bottom bar is frozen, plus whatever notification occurred while the screen was locked. Intel graphics controller: 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
+ F22 , last updates for current day; Intel CoreDuo, ATI Radeon HD2400, mesa-dri-drivers.
Rex, I'm looking at an almost total freeze of my system. Do you have any ideas? When I unplug/replug the mouse/keyboard the disk light flashes. Likewise with the network wire. SSHD responds but I can't login. Is there something I can do to recover from this or capture enough data to make a bug report for this? Thanks, George...
libxcb has more candidate fixed, I'll see about making another scratch build for testing. George, the deadlock here is *just* plasmashell, krunner (ALT-F2), as well as any already-open apps should still respond normally... to recover, restart plasmashell: ALT-F2: killall plasmashell; sleep 2; plasmashell if it's more than just plasmashell freezing, then you're seeing something different (not this bug), possibly bug #1228779 ? (or some driver issue)
Rex, Thanks for your response. The system will NOT respond except as I noted in the bug post. Usually I have to power cycle the system but the last time I did that my XFS 4TB drive got crazy. xfs_repair noted all kinds of errors... Orphan inodes, directory blocks in error, empty inodes... I'm trying to migrate away from xfs but it's REALLY slow. stat() on files for almost EVERY operation makes it slow. There's an option for mkfs.xfs but you have to reformat the drive (and loose all data there)... sigh... What do people do in this situation? 1228779 does not describe anything I'm seeing here. George...
OK, then your issue is different than either this or bug #1228779 I'd suspect something lower level, possibly kernel and/or some system driver (video?)
As threatened in comment #28: F-22 build with recent upstream commit included: https://koji.fedoraproject.org/koji/buildinfo?buildID=645737 commit reference: http://cgit.freedesktop.org/xcb/libxcb/commit/?id=f85661c3bca97faa72431df92a3867be39a74e23
*** Bug 1232802 has been marked as a duplicate of this bug. ***
That libxcb version from koji used in my report #1232802 which you just mark as duplicate. Problem reproducible.
Fwiw, I just created a copr for testing experimental/candidate upstream fixes: https://copr.fedoraproject.org/coprs/rdieter/libxcb/
Thank you Rex. I'll try it.
It does not help me. Freeze again happened.
*** Bug 1234832 has been marked as a duplicate of this bug. ***
libxcb-1.11-8.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libxcb-1.11-8.fc22
Package libxcb-1.11-8.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libxcb-1.11-8.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10920/libxcb-1.11-8.fc22 then log in and leave karma (feedback).
Ok, may be highjacking this problem report, but the symptom I see looks quite like the one described here from a users point of view. kplasmashell hangs with 100% cpu every now and then. Here with the intel driver. I have tried several of the libxcb builds mentioned here combined with forcing either DRI2 or DRI3 via an explicit driver configuration. All these configurations tend to hang the kde desktop after some minutes. Finally I have found an other problem for my hang which you might want to know about. My machine ends in a pure endless cpu loop somewhere in qt5-declerative. A patch working around these symptoms and makes the hangs here disappear is attached. The patch probably only papers over an even different problem, but it helps for me in the short term and might give you a hint to a different problem probably not fixed by the libxcb change but looking quite the same from the users/testers point of view. Mathias
Created attachment 1044606 [details] The qt5-declarative change mentioned.
Please file a separate bug (assuming your deadlock backtraces did not involve dri calls and xcb_wait_for_reply or xcb_wait_for_special_event )
Ok, done: 1237269 Mathias
*** Bug 1238712 has been marked as a duplicate of this bug. ***
I just got a freeze again (both plasmashell and kscreenlocker_greet at the same time), probably due to a notification while the screen was locked. I'm using DRI3, so this isn't the default config, but the xcb fix was supposed to fix xcb_wait_for_special_event too. The two backtraces are similar : #0 0x00000035130f666d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0000003d9c60a182 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7ffe1eecb730) at /usr/include/bits/poll2.h:46 #2 0x0000003d9c60a182 in _xcb_conn_wait (c=c@entry=0x1007ff0, cond=cond@entry=0x58bc8f8, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x0000003d9c60bd49 in xcb_wait_for_special_event (c=c@entry=0x1007ff0, se=0x58bc8d0) at xcb_in.c:744 #4 0x0000003708e49e72 in dri3_find_back (c=c@entry=0x1007ff0, priv=priv@entry=0x87cd3a0) at dri3_glx.c:1263 #5 0x0000003708e4ac8f in dri3_get_buffers (driDrawable=0x87cd3a0, loaderPrivate=0x87cd3a0, buffer_type=dri3_buffer_back, format=4107) at dri3_glx.c:1289 #6 0x0000003708e4ac8f in dri3_get_buffers (driDrawable=driDrawable@entry=0x463e0a0, format=4107, stamp=stamp@entry=0x463e0d0, loaderPrivate=loaderPrivate@entry=0x87cd3a0, buffer_mask=<optimized out>, buffer_mask@entry=1, buffers=buffers@entry=0x7ffe1eecb980) at dri3_glx.c:1466 #7 0x00007f09f73ae14b in intel_update_renderbuffers (drawable=0x463e0a0, brw=0x2b06018) at brw_context.c:1527 #8 0x00007f09f73ae14b in intel_update_renderbuffers (context=context@entry=0x2af37b0, drawable=drawable@entry=0x463e0a0) at brw_context.c:1242 #9 0x00007f09f73ae4a1 in intel_prepare_render (brw=brw@entry=0x2b06018) at brw_context.c:1263 #10 0x00007f09f73a21c0 in brw_clear (ctx=0x2b06018, mask=50) at brw_clear.c:234 #11 0x0000003715f28bfa in QSGBatchRenderer::Renderer::renderBatches() (this=this@entry=0x8730b40)
Can you verify what libxcb you have installed ? rpm -q libxcb
(In reply to Rex Dieter from comment #46) > Can you verify what libxcb you have installed ? > > rpm -q libxcb libxcb-1.11-8.fc22.x86_64 I got a new freeze, again both plasmashell and kscreenlocker_greet.
I have a little more info that may help to diagnose the cause. plasmashell enters a hard loop every time a popup notification is displayed - it draws the outline of the message then 'hangs' plasmashell. What may be significant is that this only occurs when using the Fedora Twenty Two look and feel option. If I change over to the Breeze look and feel option the problem goes away. I'm not sure that the libxcb version is significant but I'm using libxcb-1.11-5.fc22
libxcb-1.11-8.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
upgraded to libxcb-1.11-8.fc22 and now both Breeze and Fedora Twenty Two workspace themes work properly.
This is still happening for me and is reproducible: 1) in the Energy Saving settings, change switch off after to a small number like 1 minute. 2) open 2 dolphin windows. 1 with a large source file that will take over a minute to copy such as from ftp. 1 to a scratch destination. 3) Initiate a copy. The notification goes to spinning with a 1 in it. 4) don't touch anything and let the screen turn off. 5) wait a while longer. 6) move the mouse and find the plasmashell hung. The only thing I have non-stock is I have skype running with a system tray icon. libxcb-1.11-8.fc22.i686 libxcb-1.11-8.fc22.x86_64 xorg-x11-drv-intel-2.99.917-12.20150615.fc22.x86_64
If you're still seeing the problem, please file a new bug (ideally with a backtrace of the hung plasmashell process)
I just got it today, again a notification when screen was locked (or just before or after suspend). It seems to be more difficult to reproduce now, but I only have one screen currently. I saved the callstack, but I will wait before filing a new bug, as I was using my git snapshot of xorg-x11-drv-intel instead of the official package (and DRI3 too), I will test with the new version in updates-testing.
Yes, I'm still seeing it here, with stock F22 xorg-x11 packages.
I changed my compositor to use: Scale Method: Smooth Backend: OpenGL 2.0 Interface: GLX and I haven't seen an issue since.
I filed https://bugzilla.redhat.com/show_bug.cgi?id=1256082, I can reproduce the freeze with DRI3 (it doesn't seem to happen with DRI2).
I'm still seeing this and the backtrace suggests DRI2 not DRI3 (but I dunno, correct me if I'm wrong): (gdb) bt #0 0x0000003959af72fd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x000000395e20a182 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x000000395e20ba17 in wait_for_reply () at /lib64/libxcb.so.1 #3 0x000000395e20bb21 in xcb_wait_for_reply () at /lib64/libxcb.so.1 #4 0x000000395da431f7 in _XReply () at /lib64/libX11.so.6 #5 0x0000003a5b2442fa in DRI2GetBuffersWithFormat () at /lib64/libGL.so.1 #6 0x0000003a5b244637 in dri2GetBuffersWithFormat () at /lib64/libGL.so.1 #7 0x00007f63a280c67b in intel_update_renderbuffers () at /usr/lib64/dri/i965_dri.so #8 0x00007f63a280cb91 in intel_prepare_render () at /usr/lib64/dri/i965_dri.so #9 0x00007f63a2800870 in brw_clear () at /usr/lib64/dri/i965_dri.so #10 0x0000003d157263fa in QSGBatchRenderer::Renderer::renderBatches() () at /lib64/libQt5Quick.so.5 #11 0x0000003d1572bde2 in QSGBatchRenderer::Renderer::render() () at /lib64/libQt5Quick.so.5 #12 0x0000003d15737adf in QSGRenderer::renderScene(QSGBindable const&) () at /lib64/libQt5Quick.so.5 #13 0x0000003d1573832b in QSGRenderer::renderScene(unsigned int) () at /lib64/libQt5Quick.so.5 #14 0x0000003d1574871e in QSGRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /lib64/libQt5Quick.so.5 #15 0x0000003d1579265b in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /lib64/libQt5Quick.so.5 #16 0x0000003d1576301b in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #17 0x0000003d15764121 in QSGGuiThreadRenderLoop::event(QEvent*) () at /lib64/libQt5Quick.so.5 #18 0x0000003d09b544ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #19 0x0000003d09b59976 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #20 0x0000003d0808361b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #21 0x0000003d080d8bad in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #22 0x0000003d080d90b1 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #23 0x000000395be49a8a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #24 0x000000395be49e20 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #25 0x000000395be49ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #26 0x0000003d080d9d8f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #27 0x0000003d08080daa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #28 0x0000003d08088e6c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #29 0x000000000042ef16 in main ()
Bug 1258084 filed with the above backtrace.
Anyone still experiencing plasmashell deadlocks, can test a proposed xorg-x11-server patch, http://lists.x.org/archives/xorg-devel/2015-September/047304.html available in copr builds hosted at: https://copr.fedoraproject.org/coprs/rdieter/libxcb/
Still happens in F25 beta. And with DRI2... Should I open a new bug? libxcb-1.12-1.fc25.i686 xorg-x11-drv-intel-2.99.917-26.20160929.fc25.i686 Thread 1 (Thread 0xb19992c0 (LWP 7331)): #0 0xb779dd05 in __kernel_vsyscall () #1 0xb4b875ef in poll () from /lib/libc.so.6 #2 0xb713ae18 in _xcb_conn_wait () from /lib/libxcb.so.1 #3 0xb713cfdc in wait_for_reply () from /lib/libxcb.so.1 #4 0xb713d1be in xcb_wait_for_reply64 () from /lib/libxcb.so.1 #5 0xb71af8f5 in _XReply () from /lib/libX11.so.6 #6 0xb47251ef in DRI2GetBuffersWithFormat () from /lib/libGL.so.1 #7 0xb4725564 in dri2GetBuffersWithFormat () from /lib/libGL.so.1 #8 0xabf9885a in old_intel_update_renderbuffers () from /usr/lib/dri/i915_dri.so #9 0xabf98d3d in old_intel_prepare_render () from /usr/lib/dri/i915_dri.so #10 0xabf97f75 in intelClear () from /usr/lib/dri/i915_dri.so #11 0xabc42d4b in _mesa_Clear () from /usr/lib/dri/i915_dri.so #12 0xb6d6727b in QSGBatchRenderer::Renderer::renderBatches() () from /lib/libQt5Quick.so.5 #13 0xb6d6ced7 in QSGBatchRenderer::Renderer::render() () from /lib/libQt5Quick.so.5 #14 0xb6d79da9 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/libQt5Quick.so.5 #15 0xb6d7a6e3 in QSGRenderer::renderScene(unsigned int) () from /lib/libQt5Quick.so.5 #16 0xb6d8d1cc in QSGRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/libQt5Quick.so.5 #17 0xb6de26a8 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /lib/libQt5Quick.so.5 #18 0xb6da75cf in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) () from /lib/libQt5Quick.so.5 #19 0xb6dee1b9 in QQuickWindow::event(QEvent*) () from /lib/libQt5Quick.so.5 #20 0xb77453ec in PlasmaQuick::Dialog::event(QEvent*) () from /lib/libKF5PlasmaQuick.so.5 #21 0xabb2afdc in ToolTipDialog::event(QEvent*) () from /usr/lib/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
a new bug yes (against intel driver), this one is closed
Hello. I am a user of KDE, but on Kubuntu. I experienced the same behaviour, only I do not think this is related in any way to the video driver. I am only leaving this as a hint, hoping it will help make KDE better: I noticed that the freeze occurs when I access remote (slow) locations via NFS (using autofs). This seems to be a general problem in KDE, as I have another team mate experiencing the same problem on OpenSuse. Sometimes, the panel will actually recover when I'm done transferring files via NFS...