[Ubuntu-x-swat] [Bug 1603904] Re: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start
Basically any app with a menu bar will be super slow to start :( -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1603904 Title: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1603904/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603904] Re: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start
(sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-7HXS9fyRLw: Connection refused GConf Error: No D-BUS daemon running (sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused GConf Error: No D-BUS daemon running (sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused GConf Error: No D-BUS daemon running (sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused GConf Error: No D-BUS daemon running (sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused GConf Error: No D-BUS daemon running -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1603904 Title: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1603904/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603904] Re: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start
Confirmed there's a regression on 16.10 where dbus functionality is missing. This causes complex apps like Firefox and Nautilus/GTK apps to hang on start-up. But it doesn't impact simpler native X apps (like bitmap or xedit). ** Summary changed: - libertine apps don't work anymore + X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1603904 Title: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1603904/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603904] Re: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1603904 Title: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1603904/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1581626] Re: Switching to USB sound device stops USB mouse clicks from registering
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1581626 Title: Switching to USB sound device stops USB mouse clicks from registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581626/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603904] Re: libertine apps don't work anymore
It appears again that Xmir is crashing after the client has failed to start and not vice-versa. That Xmir crash is fixed here: https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=f72fad2cd4b8d6fbdef0335fbfa11e2ca38d3f86 But the Xmir crash is not causing the client start-up failure. The client start-up failure is causing the Xmir crash. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1603904 Title: libertine apps don't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1603904/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1444880] Re: xrandr report inverted gamma values
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1444880 Title: xrandr report inverted gamma values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444880/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603336] Re: Nvidia bug and maybe xinput??? PLZ FIX
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1603336 Title: Nvidia bug and maybe xinput??? PLZ FIX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1603336/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
Another thing I just noticed : with or without the patch, the only thing that works with two screen is the extended mode. When I try to go from two screen extended to two screen clone mode, both screens switch off and cannot be switched back on. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1271238] Re: Typo in comment
** Changed in: xkeyboard-config (Ubuntu) Assignee: William Skinner (alias-sync) => (unassigned) ** Changed in: xkeyboard-config (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1271238 Title: Typo in comment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1271238/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1604150] [NEW] package libsm6:i386 2:1.2.2-1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 127
Public bug reported: Error Installing Wine ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsm6:i386 2:1.2.2-1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: libsm6: Configure apturl: Configure libxt6: Configure python3-urllib3: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 18 17:31:29 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 127 InstallationDate: Installed on 2016-07-08 (10 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libsm Title: package libsm6:i386 2:1.2.2-1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libsm in Ubuntu. https://bugs.launchpad.net/bugs/1604150 Title: package libsm6:i386 2:1.2.2-1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsm/+bug/1604150/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1604077] Re: Performance regression and no DRI3 acceleration in xserver-xorg-video-radeon-lts-wily
Further information here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598593 (Please advise if I should mark this as duplicate or refer the previous report to someone else) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-lts-transitional in Ubuntu. https://bugs.launchpad.net/bugs/1604077 Title: Performance regression and no DRI3 acceleration in xserver-xorg-video- radeon-lts-wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1604077/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1604077] [NEW] Performance regression and no DRI3 acceleration in xserver-xorg-video-radeon-lts-wily
Public bug reported: Performance regression and no DRI3 acceleration in xserver-xorg-video- radeon-lts-wily, unless one specifies Option "DRI3" "1" in xorg.conf. Then, performance is *even worse*, in comparison to xserver-xorg-video-radeon-lts-vivid: Desktop is laggy, video playback is choppy, tearing occurs. Package is official Ubuntu 14.04. I've been sticking to the -lts-vivid stack for stability, but when upgrading to the -lts-wily stack for kernel 4.2, while the system runs a bit smoother, video performance is severely affected. System is a dual-core x86 Pentium laptop, 2Gb RAM. This report was previously dismissed ad invalid. I'm reporting it again, as it is not. Please test both scenarios, without and with xorg.conf enabling DRI3; running glmark2 showed correlation with performance degradation. ** Affects: xorg-lts-transitional (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-lts-wily (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-lts-wily (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-lts-transitional in Ubuntu. https://bugs.launchpad.net/bugs/1604077 Title: Performance regression and no DRI3 acceleration in xserver-xorg-video- radeon-lts-wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1604077/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1604070] [NEW] Xorg freeze
Public bug reported: Sometimes after resuming from suspend the screen becomes black with a single text line: [ 8483.420032] [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO underrun The computer does not respond any further and the fan starts working full strength. I have to press the power button to turn off the computer and boot again. This does not happen after each suspend, but happens occasionally and I could not find any particular pattern that would cause it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 18 19:26:13 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed btusb-lp1600623, 0.1, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GK208M [GeForce 920M] [1043:246a] InstallationDate: Installed on 2016-07-08 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X556UJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=73a9e974-ef96-4d81-aa12-68ea97b2c0ad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UJ.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UJ.302:bd12/09/2015:svnASUSTeKCOMPUTERINC.:pnX556UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jul 18 18:58:49 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1604070 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1604070/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603655] Re: After update, xorg will not boot
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1603655 Title: After update, xorg will not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603655/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1587913] Re: Ubuntu 16.04 Two finger scrolling/multitouch not working
Same issue on ASUS TP200SA -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1587913 Title: Ubuntu 16.04 Two finger scrolling/multitouch not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1587913/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1078068] Re: Video blinking blue during incoming call
I had the same problem on my HP ProBook 450 G3 with Intel® HD Graphics 520 integrated card and AMD Radeon R7 M340. I saw blue blinking not only in Skype but on VLC as well. Looks like it is a bug in the overlay in open source intel graphics driver or in its default settings. In case of VLC, as workaround, you can switch overlays off, but there is no way to do it with Skype. Finally I found solution here https://github.com/linuxenko/ubuntu-skylake-i915-video-fix Technically this fix just adds an instruction file 20-intel.conf, that tells how does Skylake should work. So, just add this file and reboot. After that my video works normally. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1078068 Title: Video blinking blue during incoming call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/skype/+bug/1078068/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603989] [NEW] Radeon R7 not work in ubuntu xenial
Public bug reported: the screen get a black flash or some deformation then the system get frozen I get log [ 866.763340] [drm] RC6 on [ 896.751558] [drm] RC6 on [ 910.775616] [drm] RC6 on [ 927.763796] [drm] RC6 on [ 956.751827] [drm] RC6 on [ 975.764282] [drm] RC6 on [ 1016.752731] [drm] RC6 on [ 1030.739433] [drm] RC6 on [ 1047.761923] [drm] RC6 on [ 1556.388062] audit_printk_skb: 33 callbacks suppressed [ 1556.388065] audit: type=1400 audit(1468793461.220:23): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/mission-control-5" pid=6478 comm="apparmor_parser" [ 1556.388411] audit: type=1400 audit(1468793461.220:24): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-*" pid=6478 comm="apparmor_parser" [ 1556.388666] audit: type=1400 audit(1468793461.220:25): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-*//pxgsettings" pid=6478 comm="apparmor_parser" [ 1556.388842] audit: type=1400 audit(1468793461.220:26): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-*//sanitized_helper" pid=6478 comm="apparmor_parser" [ 1556.389041] audit: type=1400 audit(1468793461.220:27): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-ofono" pid=6478 comm="apparmor_parser" [ 1560.381247] [drm] PCIE GART of 4096M enabled (table at 0x0004). [ 1560.627183] [drm:gfx_v8_0_hw_init [amdgpu]] *ERROR* amdgpu: cp failed to lock ring (-2). [ 1560.627192] [drm] ring test on 0 succeeded in 2 usecs [ 1560.627371] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 1 (-2). [ 1560.627382] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 2 (-2). [ 1560.627391] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 3 (-2). [ 1560.627400] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 4 (-2). [ 1560.627409] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 5 (-2). [ 1560.627418] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 6 (-2). [ 1560.627426] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 7 (-2). [ 1560.627435] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 8 (-2). [ 1560.627463] [drm] ring test on 9 succeeded in 7 usecs [ 1560.627478] [drm:sdma_v2_4_ring_test_ring [amdgpu]] *ERROR* amdgpu: dma failed to lock ring 10 (-2). [ 1560.627484] [drm:amdgpu_resume [amdgpu]] *ERROR* resume 5 failed -2 [ 1560.627491] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed (-2). [ 1579.303762] [drm] PCIE GART of 4096M enabled (table at 0x0004). [ 1579.545498] [drm:gfx_v8_0_hw_init [amdgpu]] *ERROR* amdgpu: cp failed to lock ring (-2). [ 1579.545512] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 0 (-2). [ 1579.545519] [drm:amdgpu_resume [amdgpu]] *ERROR* resume 4 failed -2 [ 1579.545526] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed (-2). [ 1592.083876] [drm] PCIE GART of 4096M enabled (table at 0x0004). [ 1592.338484] [drm:gfx_v8_0_hw_init [amdgpu]] *ERROR* amdgpu: cp failed to lock ring (-2). [ 1592.338498] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 0 (-2). [ 1592.338505] [drm:amdgpu_resume [amdgpu]] *ERROR* resume 4 failed -2 [ 1592.338512] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed (-2). [ 1592.379381] amdgpu :01:00.0: couldn't schedule ib [ 1592.379436] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 1592.379487] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 1592.386175] amdgpu :01:00.0: couldn't schedule ib [ 1592.386201] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 1592.386221] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 1592.437156] amdgpu :01:00.0: couldn't schedule ib [ 1592.437198] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 1592.437231] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 1592.437236] amdgpu :01:00.0: couldn't schedule ib [ 1592.437265] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 1592.437291] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 1592.437294] amdgpu :01:00.0: couldn't schedule ib [ 1592.437319] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 1592.437344] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 1592.437347] amdgpu :01:00.0: couldn't schedule ib [ 1592.437371] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 1592.437387] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 1592.437389] amdgpu :01:00.0: couldn't
[Ubuntu-x-swat] [Bug 1603904] Re: libertine apps don't work anymore
Looks to be a potential regression in Xmir due to the backtrace in the Firefox log. Adding that package to the bug. ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags added: xmir -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1603904 Title: libertine apps don't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1603904/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
In the next comment, you will findthe output of xrandr --verbose, when both monitors are enabled, with the original (non patched) drivers. I must say that the patch you posted in comment #47 works perfectly when it comes to wake the monitor after some time of sleep. Only the problem of black screens when switching from one to two screens enabled remains. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity
** Attachment added: "Xrandr output" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4702793/+files/xrandr -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1577170 Title: screen cannot be turned back on after being switched off after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1577162] Re: Screens briefly blacks out at lightdm prompt
There is no flickering of the login prompt with the latest Ubuntu 16.10. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1577162 Title: Screens briefly blacks out at lightdm prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577162/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1585942] Re: Mesa causes a segmentation fault on arm64 (wrong count of uniform locations)
** Tags added: qt5.6 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1585942 Title: Mesa causes a segmentation fault on arm64 (wrong count of uniform locations) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1585942/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Regarding new bug, subscribed to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1568604 . Will notify if I still observed this bug (1547077). I don't understand why this bug no longer happens (which is good anyway). xserver-xorg-video-nouveau is still 1:1.0.12-1build2 Perhaps bug is actually in another package and was fixed? @gr-ubuntu-0 are you still affected? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Bug observed on Asus n551jk using nouveau driver with latest updates applied. Suspend not needed, locking is enough. Ctrl-Alt-F1 then Ctrl-Alt-F7 works around, until next lock. Thank you for your attention. LC_ALL=C lshw -c video 2>/dev/null | grep configuration configuration: driver=nouveau latency=0 configuration: driver=i915 latency=0 lspci -nn | egrep -i '(vga|3d)' 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 850M] [10de:1391] (rev a2) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1603917] [NEW] [enhancement] Implement smooth scrolling in Xmir (like Xwayland)
Public bug reported: [enhancement] Implement smooth scrolling in Xmir (like Xwayland) I haven't checked if this works, but just as a reminder, we should consider copying this enhancement: http://anonscm.debian.org/cgit/pkg-xorg/xserver/xorg- server.git/commit/?id=d8a39245d6cff6accf5eaeae7a1ac15eb1eb048a ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: enhancement xmir -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1603917 Title: [enhancement] Implement smooth scrolling in Xmir (like Xwayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1603917/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1480755] Re: [regression] Some EGL clients don't get bypassed any more in fullscreen
Got it. Unity8 is bypassed just fine on desktop. The trick is to create a file: /etc/lightdm/lightdm.conf.d/mir-compositor-report.conf: [Seat:*] unity-compositor-command=/usr/bin/env MIR_SERVER_COMPOSITOR_REPORT=log /usr/sbin/unity-system-compositor and then: tail -f /var/log/lightdm/unity-system-compositor.log ** Changed in: unity8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1480755 Title: [regression] Some EGL clients don't get bypassed any more in fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1480755/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Summary: on reinstall on same CPU/motherboard/etc (only storage changed), bug no longer observed. Hello, After observing problems on the main storage of the laptop where the bug was observed, I bought a new storage and installed Ubuntu 16.04 from scratch on the new storage but the same laptop. Surprisingly, this bug **no longer happens**, but another one happens instead, which is much less of a problem. The new bug symptom is: after lock/unlock, the mouse pointer no longer appears. Mouse features actually work, as one can see hover effects on buttons and menu items, semi-blindly click, etc. An efficient workaround is to press Ctrl- Alt-F1 then Ctrl-Alt-F7, and voilà mouse pointer is back again. LC_ALL=C lshw -c video 2>/dev/null | grep configuration configuration: driver=nouveau latency=0 configuration: driver=i915 latency=0 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1480755] Re: [regression] Some Mir EGL demos don't get bypassed any more in fullscreen
Adding a Unity8 task as I suspect this bug will cause Unity8 to never get bypassed on desktop. We wouldn't really notice as both bypass and OpenGL compositing and relatively fast. But it would be nice to ensure it's bypassed for the best performance (and one frame lower latency). While giving unity-system-compositor environment MIR_SERVER_COMPOSITOR_REPORT=log would answer this question, that doesn't work because lightdm clobbers the environment and never lets you modify it. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [regression] Some Mir EGL demos don't get bypassed any more in fullscreen + [regression] Some EGL clients don't get bypassed any more in fullscreen ** Tags added: performance -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1480755 Title: [regression] Some EGL clients don't get bypassed any more in fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1480755/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1473901] Re: egl-platform-mir.patch: Incorrect (backwards) pixel formats are accepted
upstream enabled support for XBGR, but I'll drop the other one from the patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1473901 Title: egl-platform-mir.patch: Incorrect (backwards) pixel formats are accepted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1473901/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1473901] Re: egl-platform-mir.patch: Incorrect (backwards) pixel formats are accepted
UPDATE: Starting in Mesa 12.x, GBM_FORMAT_XBGR is supported. So we only need to remove GBM_FORMAT_ABGR to solve this bug. https://cgit.freedesktop.org/mesa/mesa/tree/src/gbm/backends/dri/gbm_dri.c?h=12.0#n542 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1473901 Title: egl-platform-mir.patch: Incorrect (backwards) pixel formats are accepted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1473901/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1573470] Re: BQ M10 tablet. Libreoffice Impress presentation mode displays wrong colors
It's no mistake either: https://lists.freedesktop.org/archives/mesa-dev/2016-April/113657.html The change in Mesa 12.0 is specifically designed to support Android pixel formats. :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1573470 Title: BQ M10 tablet. Libreoffice Impress presentation mode displays wrong colors To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573470/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1573470] Re: BQ M10 tablet. Libreoffice Impress presentation mode displays wrong colors
Good news! Maybe... In comment #13 I said "We can't immediately make Mesa use Android's preferred XBGR format." Turns out though that the imminent new Mesa 12 release adds the missing GBM_FORMAT_XBGR that Android prefers: https://cgit.freedesktop.org/mesa/mesa/tree/src/gbm/backends/dri/gbm_dri.c?h=12.0#n542 It only appears in the Mesa 12 source code and not Mesa 11 (except by accident of our own making where the colours will appear backwards -> bug 1473901). So it would appear that Mesa accepting the unsupported pixel format was a Mir bug 1473901. But that shouldn't matter starting in Mesa 12.x because upstream Mesa *seems* to support little endian GBM_FORMAT_XBGR properly (which to Android is the same thing as big endian HAL_PIXEL_FORMAT_RGBX_). Assuming it works and is not a mistake, Mesa 12.x will finally speak the same pixel format as Android, which might solve this bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1573470 Title: BQ M10 tablet. Libreoffice Impress presentation mode displays wrong colors To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573470/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1581093] Re: unity8 desktop freeze on lid closure or selecting "suspend"
** Summary changed: - unity8 desktop didn't survive laptop lid closure + unity8 desktop freeze on lid closure or selecting "suspend" ** Description changed: running xenial + stable-phone-overlay, unity8 had hexchat open and focused, terminal app and browser also open closed lid, seemed to enter retention fine open lid, ui responded for a bit, i toggled apps to terminal then back to hexchat then ui/cursor froze, eventual reboot on its own there were 2 related crash files, 1 for unity8 and 1 for Xmir, both were corrupt + + updating to include that selecting "suspend" from the system icon causes + the same -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1581093 Title: unity8 desktop freeze on lid closure or selecting "suspend" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1581093/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Hello, This bug seems to be invalidly set as "Fix Released" in the Debian tracker, since it's only been archived. I'm guessing the launchpad bug is just trying to mirror the status of that one? But the issue seems to be still present. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1593586] Re: Issue with two external screens
When I boot the Laptop with open lid the issue is gone. The latest updates now in place. ** Description changed: Hello, I use Ubuntu 16.04 LTS with latest updates. - When I boot my Laptop (Dell latitude 7470 + Dell E-Port Plus II docking - station) with two external Dell screens attached (via Display port, each - separate connected) at the beginning of my session everything works - fine. + When I boot my Laptop (Dell latitude 7470 + Dell E-Port Plus II docking station) with two external Dell screens attached (via Display port, each separate connected) at the beginning of my session everything works fine. + The lid is closed while booting. After starting Firefox Webbrowser the focus of the mouse is some how lost. Then for example it is not possible to open the context menu of Firefox or typed letters appear on the other screen. I found a workaround to have a working setup. I boot the laptop at the beginning with only one attached screen (cable disconnected). After login I attach the second screen and open the "Displays" configuration menu and click on something without changing the configuration. After a few seconds the second screen appears and everything works fine. Sadly the focus is also lost when I remove the Laptop from the dockingstation and attach it back to the docking station. The focus works always fine when only the build in display is used. Regards, Michael ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 17 08:16:07 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06dc] InstallationDate: Installed on 2016-06-10 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jun 17 08:04:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1168 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.2 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1593586 Title: Issue with two external screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1593586/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
