Public bug reported:
Following the ubuntu wiki's instructions on how to enable hibernate in
16.04 resulted in no change. I created a file
/etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla
with the following contents and rebooted my computer:
[Re-enable hibernate by default
[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
[Expired for fglrx-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Same issue here on XPS 15-9530. I fixed it by switching to the nvidia
364 drivers from the graphics driver ppa:
sudo apt-get purge nvidia-361
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
sudo apt-get install nvidia-364
A full system restart (twice for some reason, power
I found something interesting that may or may not be valuable. From what
I can gather so far, we're dealing with two flicker issues. One affects
only Ubuntu MATE, the other affects regular Ubuntu as well. For me, I've
been able to work around the problem in Ubuntu MATE by disabling
tlp.service and
Public bug reported:
I have never successfully gotten the nvidia drivers to work properly.
Before I used nvidia-304 because that seemed to be the only driver other
than Nouveau that worked... the other nvidia drivers just give me a
black screen
With nvidia-361 I get a different outcome:
I get to
Dammit. Now this regression has made it into the LTS kernel. Are you
guys kidding me? Is it not possible for the changes that caused this
exceptionally annoying regression (as in my computer is now almost
entirely unusable) to be removed from the current production kernel,
pending a proper
Mikael Svensson, to see if this is already resolved, could you please
test http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?
** Tags removed: bios-outdated-a10
** Tags added: latest-bios-a10
** Changed in: xorg (Ubuntu)
Importance: Low => Medium
** Changed in: xorg
I do not know how to do it. I'll have to install again to this
recommended test?
--
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/1545510
Title:
Ubuntu 14.04 LTS black screen at login screen
To
"not found" or "no diversion"?
you can check with `dpkg -L libgbm1` if there are diversions in place
--
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/1572855
Title:
libgbm.so.1:
ernsteiswuerfel, it will help immensely if you filed a new report with Ubuntu
by ensuring you have the package xdiagnose installed, and that you click the
Yes button for attaching additional debugging information running the following
from a terminal:
ubuntu-bug xorg
Also, please feel free to
** Changed in: xorg (Ubuntu)
Status: Incomplete => Invalid
--
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/1457974
Title:
Coloured triangles on screen
To manage notifications about this
eros2, it will help immensely if you filed a new report with Ubuntu by ensuring
you have the package xdiagnose installed, and that you click the Yes button for
attaching additional debugging information running the following from a
terminal:
ubuntu-bug xorg
Also, please feel free to subscribe
Robert Tuck, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1446053/comments/5
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow
Thanks Leonard. That work around work for me. I almost want to do a
fresh install.
--
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
eezacque, to see if this is already resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ ?
** Tags added: wily
--
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/1490183
*** This bug is a duplicate of bug 1568604 ***
https://bugs.launchpad.net/bugs/1568604
** Also affects: xserver-xorg-video-intel
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
The temporary solution proposed by Leonard Samuelson (len-samuelson) in
#35 works for me. I'm on a Xubuntu 16.04 on a Lenovo T530, i5-3320M,
using Intel graphics.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
Hi Tim,
Please can you provide some information about what happened, whether the
problem is reproducible etc. Please add this information to the Bug
Description and also please change the Bug Title.
Thanks
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug
The verification of the Stable Release Update for llvm-toolchain-3.8 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package llvm-toolchain-3.8 - 1:3.8-2ubuntu3
---
llvm-toolchain-3.8 (1:3.8-2ubuntu3) xenial; urgency=medium
* rules: Allow LLVM tests to fail on i386, we know dropping AVX512 breaks
them.
llvm-toolchain-3.8 (1:3.8-2ubuntu2) xenial; urgency=medium
*
I installed xserver-xorg-video-intel and this seem good now.
--
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/1572667
Title:
Screen flickering sometimes on xenial rc
To
HI!
Would this bug cause my system to crash when using an external monitor
via HDMI? I can attach and use the monitor no problem UNTIL I suspend
and/or detach and reattach the monitor, in which case the whole system
crashes i.e.) screen freezes, keyboard, touchpad and network are all
unresponsive
*** This bug is a duplicate of bug 1568604 ***
https://bugs.launchpad.net/bugs/1568604
** This bug has been marked a duplicate of bug 1568604
Mouse cursor lost when unlocking with Intel graphics
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I have exactly the same issue with Lubuntu 16.04 with LXDE destop and a
Dell Latitude E6500.
--
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
Public bug reported:
When the computer is suspended (from within xfce), and then woken up again, the
mouse cursor disappears.
CTRL+ALT+F1 CTRL+ALT+F2 makes it appear again.
The machine has not been installed from scratch, but rather updated from
15.10.
This doesn't seem to be
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI: Synaptics
- Touch Digitizer - missing at boot".
+ Affecting this digitizer is also bug
** Changed in: xinput (Ubuntu)
Status: Confirmed => Triaged
--
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/1480673
Title:
Asus T300 CHI bluetooth Touchpad is recognized incorrectly
To
** Summary changed:
- 16,04: Asus T300 CHI: touchscreen digitiser missing at boot
+ Asus T300 CHI: Synaptics Touch Digitizer - missing at boot
** Changed in: xinput (Ubuntu)
Status: New => Triaged
** Changed in: xinput (Ubuntu)
Importance: Undecided => Medium
--
You received this
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
- touchscreen digitiser missing at boot".
+ Affecting this digitizer is also bug
I have an A8 3820 AMD cpu (HD 6550 graphics) I have the same problem.
First I want to say that I have been booting a usb hdd since 16.04
alpha. when I booted kernal 4.4.0-10 no problem, but I then booted to
4.4.0-12 that's when the problem started. Then I waited for the release
of 16.04, there
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
+
+ Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
+ touchscreen digitiser missing at boot".
Using 16.04 amd64 Ubuntu (unity).
** Description changed:
+ Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI] Synaptics
+ Touch Digitizer V04 - no multitouch".
+
The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo.
Both (touchscreen, touchpad) only work like a mouse (moving pointer, left
Public bug reported:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
touchscreen digitiser missing at boot".
Using 16.04 amd64 Ubuntu (unity).
In this case the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
I can confirm this is an actual bug as my system is affected too.
My system: Xubuntu 16.04 LTS, x86-64.
My system is an update to a 15.10 installation.
My solution is to switch to a virtual terminal (CTRL+ALT+F) and then
switch back to X session (CTRL+ALT+F7).
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
I have the same problem since upgrading from 15.10 to 16.04. Thinkpad
T450s with intel graphics.
Not sure if this is related, but I have this in dmesg/syslog:
[51153.613064] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU
pipe B FIFO underrun
[51205.851259]
Happens with an Intel NUC-5i5RYH (Core i5-5250U), Xubuntu 16.04,
DisplayPort driving Acer 2560x1440 monitor.
Another workaround: Create a keyboard shortcut to "light-locker-command
--activate". I use "ctrl-alt-C". Using the command "xset s activate"
also works. When an unlock fails to restore the
I have tried another configuration. This time, only the ASUS is active.
And on "wake up", the laptop screen activates before the OS realizes
that "oh no, this is not it, in fact only the other screen is active".
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Oh, I didn't know they were subvariants :)
I've dropped them from our llvm-3.8 for now at least..
--
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/1549849
Title:
11.2.0-rc1: llvmpipe tests fail
(In reply to Jose Fonseca from comment #6)
> It's not the first time LLVM misidentifies modern CPUs.
>
> I thought that all the logic in
> src/gallium/auxiliary/gallivm/lp_bld_misc.cpp for setting +/-foo mattrs
> would save us from this sort of grief.
For features we already know about (I think
(In reply to Timo Aaltonen from comment #8)
> Actually it wasn't avx512, that was the first one I tried :) It's enabled
> also on 3.7 and that version works fine. Only one that was added in 3.8 is
> PKU, but dropping just that didn't help.
>
> I did try dropping all non-client features (AVX512,
It's not the first time LLVM misidentifies modern CPUs.
I thought that all the logic in
src/gallium/auxiliary/gallivm/lp_bld_misc.cpp for setting +/-foo mattrs
would save us from this sort of grief.
On the other hand, I suppose that actually knowing the exact CPU model
allows it to better model
llvm-3.8 misdetects skylake features, this is fixed in 3.9-snapshot..
--
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/1549849
Title:
11.2.0-rc1: llvmpipe tests fail if built on skylake
To
Actually it wasn't avx512, that was the first one I tried :) It's
enabled also on 3.7 and that version works fine. Only one that was added
in 3.8 is PKU, but dropping just that didn't help.
I did try dropping all non-client features (AVX512, CDI, DQI, BWI, VLX,
PKU) and that worked. Maybe one of
Public bug reported:
package xserver-xorg-core 2:1.18.3-1ubuntu2 failed to install/upgrade:
trying to overwrite '/usr/lib/xorg/modules/libglamoregl.so', which is
also in package xserver-xorg-video-glamoregl 0.6.0-0ubuntu4. The error
occurred after upgrading to 16.04.
ProblemType: Package
@Tim (darkxst)
Sadly i get "not found" on all of them
--
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/1572855
Title:
libgbm.so.1: cannot open shared object file
To manage
Same problem here. Many people mention as a workaround to delete the
monitors.xml file. However, this workaround is only valid if you want to
use the default resolution at startup. For me it's not possible because
Ubuntu is trying to set a default resolution that is not supported by my
screen.
Public bug reported:
When I long press a word, it's marked and 2 blue leaves appear on
borders. I suppose that, as in Android, they should allow me to select
more or less text, but when I click on them they are not recognized and
I get same behaviour as if I was clicking anywhere else. The same
This data-race occurred in Virtualbox with 3D acceleration enabled.
Below is stack trace of this data race. This bug was fixed by upstream
three years ago but it hasn't merged into our code. I have patched my
library and Virtualbox haven't crashed since then.
Fix:
Public bug reported:
I'm running Ubuntu GNOME 16.04 on a laptop (HP Elitebook Folio 1020 G1
SE) with an external display (DELL U2713H) via HDMI, and I cannot
suspend displays with this configuration kept.
1. I type Win+L to lock the session
2. Laptop shows locked screens, then all display
55 matches
Mail list logo
