Summary: | X11 Dies From Kodi Fullscreen Switch, Snowballing To pulseaudio, kactivitymanage, ksmserver | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | vindicator <nroycea+kde> |
Component: | core | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | arojas, nroycea+kde |
Priority: | NOR | Flags: | thomas.luebking:
Intel+
|
Version: | 5.5.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=92505 | ||
See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=92505 | ||
Latest Commit: | Version Fixed In: |
Description
vindicator
2016-02-04 17:55:38 UTC
Looks like the X11 server crashes/crashed. Check /var/log/Xorg.*.log for backtraces - the information you posted is w/o value. The crash is probably in the driver and could be induced by a context switch. Try to suspend the compositor before running kodi (SHIFT+Alt+F12) and see whether it still happens. Attach /var/log/Xorg.*.log's in any case - the bug is unlikely in KWin or KDE. RE: kwin_x11[13555]: QXcbConnection: XCB error: 9 (BadDrawable) I had journalctl -f to see what happens live, and even just simply hovering my mouse over something like the Application Launcher causes the "baddrawable". Qt seems to have a distaste with something about my newish system. You can ignore that error - it means KWin wanted to adjust a window that's already gone. This causes a server error, but is harmless, and the alternative is to grab the server all the time (as window managers exclusively deal with windows with unknown lifetime) - what means your desktop would kinda lag ;-) The "bug" here is the excessive default debug output. Ya, you're right about that Thomas: *****(Xorg.log.old) [ 13101.768] (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawable [ 13101.797] (EE) [ 13101.797] (EE) Backtrace: [ 13101.798] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x598499] [ 13101.798] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f82052df67f] [ 13101.798] (EE) 2: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0xf413f) [0x7f8200044aaf] [ 13101.798] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0xf6727) [0x7f8200049637] [ 13101.799] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x64e60) [0x7f81fff26380] [ 13101.799] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x68b30) [0x7f81fff2de20] [ 13101.799] (EE) 6: /usr/lib/xorg-server/Xorg (WakeupHandler+0xaa) [0x43adca] [ 13101.799] (EE) 7: /usr/lib/xorg-server/Xorg (WaitForSomething+0x1ef) [0x590caf] [ 13101.799] (EE) 8: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x10e) [0x43609e] [ 13101.799] (EE) 9: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x453) [0x43a293] [ 13101.799] (EE) 10: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f82052cc610] [ 13101.799] (EE) 11: /usr/lib/xorg-server/Xorg (_start+0x29) [0x4245c9] [ 13101.800] (EE) 12: ? (?+0x29) [0x29] [ 13101.800] (EE) [ 13101.800] (EE) Segmentation fault at address 0x0 [ 13101.800] (EE) Fatal server error: [ 13101.800] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 13101.800] (EE) ***** *****(Xorg.log) [ 13102.047] (II) LoadModule: "intel" [ 13102.047] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 13102.047] (II) Module intel: vendor="X.Org Foundation" [ 13102.047] compiled for 1.18.0, module version = 2.99.917 [ 13102.047] Module class: X.Org Video Driver [ 13102.047] ABI class: X.Org Video Driver, version 20.0 [ 13102.047] (II) LoadModule: "modesetting" [ 13102.048] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 13102.048] (II) Module modesetting: vendor="X.Org Foundation" [ 13102.048] compiled for 1.18.0, module version = 1.18.0 [ 13102.048] Module class: X.Org Video Driver [ 13102.048] ABI class: X.Org Video Driver, version 20.0 [ 13102.048] (II) LoadModule: "fbdev" [ 13102.048] (WW) Warning, couldn't open module fbdev [ 13102.048] (II) UnloadModule: "fbdev" [ 13102.048] (II) Unloading fbdev [ 13102.048] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 13102.048] (II) LoadModule: "vesa" [ 13102.048] (WW) Warning, couldn't open module vesa [ 13102.048] (II) UnloadModule: "vesa" [ 13102.048] (II) Unloading vesa [ 13102.048] (EE) Failed to load module "vesa" (module does not exist, 0) [ 13102.048] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 13102.048] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 13102.048] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 13102.048] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 [ 13102.048] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 13102.048] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20150731 [ 13102.048] (II) intel(0): SNA compiled from 2.99.917-519-g8229390 [ 13102.049] (WW) Falling back to old probe method for modesetting [ 13102.049] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics [ 13102.049] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 2 threads [ 13102.049] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 13102.049] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 13102.049] (==) intel(0): RGB weight 888 [ 13102.049] (==) intel(0): Default visual is TrueColor [ 13102.049] (II) intel(0): Output VGA1 has no monitor section [ 13102.049] (II) intel(0): Enabled output VGA1 [ 13102.049] (II) intel(0): Output HDMI1 has no monitor section [ 13102.049] (II) intel(0): Enabled output HDMI1 [ 13102.049] (II) intel(0): Output HDMI2 has no monitor section [ 13102.049] (II) intel(0): Enabled output HDMI2 [ 13102.049] (--) intel(0): Using a maximum size of 256x256 for hardware cursors [ 13102.049] (II) intel(0): Output VIRTUAL1 has no monitor section [ 13102.049] (II) intel(0): Enabled output VIRTUAL1 [ 13102.049] (--) intel(0): Output HDMI1 using initial mode 1920x1080 on pipe 0 [ 13102.049] (==) intel(0): TearFree disabled [ 13102.049] (==) intel(0): DPI set to (96, 96) [ 13102.049] (II) Loading sub module "dri2" [ 13102.049] (II) LoadModule: "dri2" [ 13102.049] (II) Module "dri2" already built-in [ 13102.049] (II) Loading sub module "present" [ 13102.049] (II) LoadModule: "present" [ 13102.049] (II) Module "present" already built-in [ 13102.049] (II) UnloadModule: "modesetting" [ 13102.049] (II) Unloading modesetting [ 13102.049] (==) Depth 24 pixmap format is 32 bpp [ 13102.049] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend [ 13102.050] (==) intel(0): Backing store enabled [ 13102.050] (==) intel(0): Silken mouse enabled [ 13102.050] (II) intel(0): HW Cursor enabled [ 13102.050] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 13102.050] (==) intel(0): DPMS enabled [ 13102.050] (==) intel(0): Display hotplug detection enabled [ 13102.050] (II) intel(0): [DRI2] Setup complete [ 13102.050] (II) intel(0): [DRI2] DRI driver: i965 [ 13102.050] (II) intel(0): [DRI2] VDPAU driver: va_gl [ 13102.050] (II) intel(0): direct rendering: DRI2 enabled [ 13102.050] (II) intel(0): hardware support for Present enabled ***** Outside of Vesa and fbdev not being found, it seems ok with the Intel drivers being used. Would you say I should go ahead and submit this to Xorg or is there an alternative that is already in existence? I say it like that because KDE with wayland just isn't usable yet with my desktop. I've read it's really just meant for touch currently. My mouse weirded out when trying it. It looks like Hawaii might be the nearest alternative with wayland if you might suggest I try that route. Thanks Antonio. I just was about to view that but saw https://bbs.archlinux.org/viewtopic.php?id=208252 first (which references the uxa in your link). I now know where to focus. Thank's ya'll. And FYI, the fix for me (which isn't a fix really) is to create the following file with section, then reboot. I've been able to switch Kodi to/from fullscreen with no issues. It isn't a "fix" per-se because sna is meant to replace uxa, so you're really just using an older accelmethod. /etc/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier "Intel Graphics" Driver "intel" Option "Accel" "true" Option "AccelMethod" "uxa" EndSection And while I haven't tried, you could probably try setting "accel" to "false" and just not deal with any hardware acceleration. But so far I'm happy with uxa. |