[Ubuntu-x-swat] [Bug 1673329] [NEW] Reports receive

Public bug reported: Here's the report that I've reinstall the Ubuntu OS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 .tmp.unity_support_test.0: ApportVersion:

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.x

Might need testing the newer version: https://lists.freedesktop.org/archives/xorg/2017-March/058662.html -- 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/1671799 Title: FFe: xserver 1.19.x

[Ubuntu-x-swat] [Bug 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

Unassigned, because technically kdub is working on the prerequisite work only right now. And I don't want to get into the situation again where we are arguing over whether VM support is "done". So will assign this when the plan is closer to completion. ** Changed in: mir Assignee: Kevin

[Ubuntu-x-swat] [Bug 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on

[Ubuntu-x-swat] [Bug 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

I have followed #58 comment to verify this bug, it can update successfully. Unit: Gladiator 2 Image: stella-datong140729-trusty-amd64-20141230-1 Original Kernel version: 3.13.0-34-generic New Kernel version: 3.13.0-113-generic New fglrx installed: 2:15.201.2-0ubuntu0.14.04.1 -- You received

[Ubuntu-x-swat] [Bug 1673308] [NEW] steam software package will not install-it is there but can not be detected

Public bug reported: steam software package can not be detected even though it is showing as installed, therefore i can not install the steam package in order to activate fsxsteam ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu

[Ubuntu-x-swat] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort()

Crash occurred while running benchmark inside Dirt Rally (xubuntu 17.04 Beta 1). Description:Ubuntu Zesty Zapus (development branch) Release:17.04 xserver-xorg-core: Installed: 2:1.18.4-1ubuntu9 Candidate: 2:1.18.4-1ubuntu9 Version table: *** 2:1.18.4-1ubuntu9 500 500

[Ubuntu-x-swat] [Bug 1672949] Re: nautilus 'Desktop' window on Xmir is transparent

** Changed in: canonical-devices-system-image 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/1672949 Title: nautilus 'Desktop' window on Xmir is

[Ubuntu-x-swat] [Bug 1673061] Re: weak performance

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.x

Pretty simple here - Will only successfully boot to greeter, ect. when nvidia drivers are installed. If the drivers aren't installed then it either 'hangs' right after the fs check on sandybridge or goes to low graphics pop up on haswell. Once the nvidia drivers are installed then boot ups

[Ubuntu-x-swat] [Bug 1489483] Re: Enable llvmpipe on libgl-mesa-dri

This bug was fixed in the package mesa - 17.0.1-1ubuntu1 --- mesa (17.0.1-1ubuntu1) zesty; urgency=medium * Merge from Debian. - enable llvmpipe on ppc64el (LP: #1489483) -- Timo Aaltonen Fri, 10 Mar 2017 14:25:48 +0200 ** Changed in: mesa (Ubuntu)

[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not work in rootless mode on nvidia proprietary drivers (GNOME)

Here is another observation (my old workaround): - KMS is enabled, gdm starts in wayland mode. Trying to start gnome- shell in Xorg mode fails (gnome-shell/mutter crash). - Switch to tty (ctrl+alt+f2), login and start: - $ sudo lightdm --test-mode - lightdm is starting, nvidia logo appears for

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.x

Hangs how? This stack has been in debian for some time now, so I believe it's your hybrid configuration that is somehow busted. -- 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/1671799

[Ubuntu-x-swat] [Bug 1673203] [NEW] computer suspend test

Public bug reported: it did not pass the test. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 Uname: Linux 4.10.3-041003-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a

[Ubuntu-x-swat] [Bug 1673194] [NEW] Prime Synchronization not enabled after enabling closed NVidia driver

Public bug reported: This affects all versions and derivatives of Ubuntu on any Optimus laptop running Xorg (to the best of my knowledge). Mir and Wayland don't work with closed drivers to any testable extent so it is unknown how this affects those graphical servers. After enabling

[Ubuntu-x-swat] [Bug 1673194] Re: Prime Synchronization not enabled after enabling closed NVidia driver

You'll notice nvidia-drm.modeset=1 added on the command line Linux line ** Attachment added: "Altered grub" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1673194/+attachment/4838384/+files/grub ** Description changed: This affects all versions and derivatives of

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.x

Tested on Lenovo Yoga 20FY that has an Optimus setup (Intel HD 520 and Nvidia 540M Card). Used Ubuntu 17.04 daily and added PPA: https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging. Test 1 - No restricted/closed drivers Upgrade worked with no packages broken, etc.. Unfortunately,

[Ubuntu-x-swat] [Bug 1511301] Please test proposed package

Hello Kai-Heng, or anyone else affected, Accepted fglrx-installer-updates into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /fglrx-installer-updates/2:15.201.2-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please

[Ubuntu-x-swat] [Bug 1511301] Please test proposed package

Hello Kai-Heng, or anyone else affected, Accepted fglrx-installer into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fglrx- installer/2:15.201.2-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing

[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not work in rootless mode on nvidia proprietary drivers (GNOME)

Tim, indeed, if KMS is enabled, gdm starts perfectly in wayland mode and you can use gnome-shell wayland session (glx is however broken). But if you would like to use gnome-shell Xorg session, then gnome-shell will crash, because apparently gdm starts xorg in rootless mode (I presume uid of user

[Ubuntu-x-swat] [Bug 1517046] Re: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest

I've changed my HDMI cable and discovered that part of the problem or the problem as a whole is due to the HDMI cable that I was using. The monitor stated that the frequency was out of range when I used a DVI adapter so I tried playing around with various frequencies to no avail. Finally I

[Ubuntu-x-swat] [Bug 1672949] Re: nautilus 'Desktop' window on Xmir is transparent

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (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.

[Ubuntu-x-swat] [Bug 1672949] Re: nautilus 'Desktop' window on Xmir is transparent

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (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.

[Ubuntu-x-swat] [Bug 1517046] Re: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest

I'm sorry, I made a mistake and said it doesn't list the native resolution. This was wrong. The displays application lists the native 1920x1080 but the display goes blank when this is selected. Using a lower setting (1280x720) works. Adding a higher setting (2048x1152) fails for obvious reasons.

[Ubuntu-x-swat] [Bug 1517046] Re: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest

@yuval can fix the issue by creating a ~/.xprofile file with the xrandr lines (change the lines to match your configuration): xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync xrandr --addmode eDP-1 1920x1080 use "cvt 1920 1080 60" to get the --newmode