** Changed in: oem-priority
Status: New => Incomplete
** Changed in: oem-priority
Assignee: Yuan-Chen Cheng (ycheng-twn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/b
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: 2.20.1-0ubunt
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
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 DuBoi
** 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 Tr
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 thi
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 4.8.0-42.45-g
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 h
** 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 transparen
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 privile
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 work
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)
Status: Fix Commit
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 a
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
Title:
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 direc
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 restricted/clo
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 Ub
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, Ubunt
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 hel
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
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 b
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 switched
22 matches
Mail list logo
