** Changed in: xorg-server
Status: Unknown => 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/1822184
Title:
clear_console locks up video when X is running and you log out from
** Changed in: xorg-server (Debian)
Status: Unknown => Confirmed
** Changed in: xorg (Debian)
Status: Unknown => 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/1822184
Ti
** Bug watch added: Debian Bug tracker #866898
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898
** Also affects: xorg (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #810660
This bug was fixed in the package mutter - 3.32.0-1ubuntu1
---
mutter (3.32.0-1ubuntu1) disco; urgency=medium
* debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
* debian/gbp.conf: update branch to point to ubuntu/master
* debian/patc
This bug was fixed in the package gnome-control-center -
1:3.32.0.1-1ubuntu6
---
gnome-control-center (1:3.32.0.1-1ubuntu6) disco; urgency=medium
*
debian/patches/display-Don-t-always-set-the-primary-monitor-to-the-first.patch:
- Make sure the display panel primary monitor matc
*** This bug is a duplicate of bug 1576859 ***
https://bugs.launchpad.net/bugs/1576859
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1576859, so it is being marked as such. Please look
** Summary changed:
- tooltips and combo boxes in webbrowsers are all garbage
+ tooltips and combo boxes in webbrowsers are all garbage in
xserver-xorg-video-radeon 1:19.0.0-1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
http
*** This bug is a duplicate of bug 1822026 ***
https://bugs.launchpad.net/bugs/1822026
** Summary changed:
- After install, cannot boot into system unless I use nomodeset kernel parameter
+ After install, cannot boot into system unless I use nomodeset kernel
parameter (repeated kernel crashe
This bug was fixed in the package libglvnd - 1.1.1-0ubuntu1
---
libglvnd (1.1.1-0ubuntu1) disco; urgency=medium
* New upstream release. (LP: #1816004)
-- Timo Aaltonen Wed, 13 Mar 2019 20:05:49 +0200
** Changed in: libglvnd (Ubuntu)
Status: Confirmed => Fix Released
--
This bug was fixed in the package mesa - 19.0.1-1ubuntu1
---
mesa (19.0.1-1ubuntu1) disco; urgency=medium
* Merge from Debian. (LP: #1822092)
-- Timo Aaltonen Thu, 28 Mar 2019 15:51:31 +0200
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You received this
** Tags added: disco
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1822179
Title:
Resuming from sleep breaks desktop and lock screen background in G
You have been subscribed to a public bug:
CPU: AMD Ryzen 5 1600
MOBO: MSI B350M MORTAR
GPU: NVIDIA GTX 1060
Ubuntu version: 19.04
Nvidia driver version: 418.56
The system is updated with the latest updates as today, 28 March 2019
As the title says, in Ubuntu 19.04 the GNOME lockscreen gets cor
1) I believe it will work, but am currently unwilling to upgrade from the
working X stack.
2) Yes, underlying bug seems to be fixed in the 7.7.1 package version.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
h
Also experiencing same problem on a Dell Inspiron 3168. Seems as though
what should be handled by iio-sensor-proxy is not being handled for the
input part of the touchscreen.
** Also affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iio-sensor-proxy (Ub
Bug confirmed on newer versions of Ubuntu also.
--
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/1682883
Title:
Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one
To manage notifications
The bug is still present in all subsequent versions of Ubuntu (17.10,
18.04 and 18.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/1682883
Title:
Missing 2560x1440 resolution on a Dell XPS 2
The uninstall and reinstall of amdgpu-pro has not worked for me. I have
also tried to purge amdgpu-core and amdgpu-dmks which I was told by
others got around this issue. I have not been successful thus far. Any
other suggestions and or logs needed to help me find a suitable
workaround until this
>
> Hello!
>
> I will explain what I did, I have little ability, so i made some research
> to get knowledge on how I could perform the configuration of this parameter.
>
> I found a location with the instructions I followed:
>
> # sudo cat /sys/module/i915/parameters/enable_psr
>
> This command ret
Hark:
1) For one who is using 16.04, an upgrade for the X stack is available
following instructions from
https://wiki.ubuntu.com/Kernel/LTSEnablementStack . Could you please
advise to the results?
2) Regarding the package xserver-xorg-video-ati, this is fixed as per
https://bugs.launchpad.net/ubu
try linux-oem -1035 from bionic-proposed, it has ~50 commits backported
from 5.0 to i915 driver which should help with these issues
** Description changed:
I have two connected external monitors. They are connected through a
Dell Dock W15. One is connected with VGA, the other with DP. Sometim
*** This bug is a duplicate of bug 1822026 ***
https://bugs.launchpad.net/bugs/1822026
** This bug has been marked a duplicate of bug 1822026
Live USB freezes or cannot complete install when nouveau driver is loaded
--
You received this bug notification because you are a member of Ubuntu-
** Changed in: xserver-xorg-video-intel
Status: Won't Fix => Fix Released
--
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/1087582
Title:
[gen3] Bad GPU performance whil
I got fed up with my 945gm not being capabile of 60fps glxgears.
commit d938da6b132a2d6addeba4c57a67ec3c07824843
Author: Ville Syrjälä
Date: Fri Mar 22 20:08:03 2019 +0200
drm/i915: Disable C3 when enabling vblank interrupts on i945gm
The main difference compared to the older pm_qos attem
** Tags added: upgrade-software-version
--
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/1822092
Title:
FFe: Mesa 19.0.1 for disco
To manage notifications about this bug go to:
https://bugs.launc
doesn't really need a ffe since it's a bugfix release, but doesn't hurt
to have one either..
--
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/1822092
Title:
FFe: Mesa 19.0.1 for disco
To manage n
I tried xserver-xorg-video-ati and xserver-xorg-video-radeon
19.0.1-0ubuntu1~ppa1 from ~canonical-x/x-staging and it fixes the issue
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gtk+3.0 (Ubuntu)
Status: Incomplete => Invalid
*
disco will, it's on the queue and should be accepted after beta freeze
is over
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
GLVND: AARCH64 : Fix address passed to clear cach
Public bug reported:
Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0
release.
Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
glGetIntegerv(GL_MINOR_VERSION) depends on the particular driv
Public bug reported:
I have two connected external monitors. They are connected through a
Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
the VGA monitor complains about the resolution and will not work after
the screen saver has been active (and putting the monitors to slee
** Description changed:
Disco up to date
With Chrome and Firefox tooltips and combo boxes are all garbage and
make the browser unusable. Cf screenshots.
Graphics card:
- Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770]
+ Advanced Micro Devices, Inc. [AMD/ATI] Junip
This looks like something we see occasionally with radeon (and nouveau)
drivers at times.
Can you please run 'lspci -k' and send the output?
** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu)
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gtk
Hi Timo,
I am hoping we can get the latest v1.1.1 release in Cosmic Cuttlefish and Disco
Dingo as well.
Could you help update?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
@Daniel
4/5. I collected the attached drminfo.txt while at login screen.
While in tty4, I noticed that the computer would freeze for more or less
long periods of time because of some nouveau-related kernel messages
that were printed on the screen. I managed to type the command you
mentioned betwe
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
See this do
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
1/2/3. I made a fresh install.
On the first boot, device was blocked at the "Ubuntu" logo with the dots
blinking white and orange forever. Pressing Esc wouldn't do anything
(it's supposed to show the boot process) and pressing NumLock on the
numpad wouldn't light the NumLock LED (it's my to-go che
Please:
1. Clarify why you think it's not working properly.
2. Turn the airplane mode switch ON.
3. Run: rfkill > switchon.txt
4. Turn the airplane mode swith OFF.
5. Run: rfkill > switchoff.txt
6. Send us the files 'switchon.txt' and 'switchoff.txt'.
** Package changed: xorg (Ubuntu) => ubu
Please:
1. Clarify why you think it's not working properly.
2. Turn the airplane mode switch ON.
3. Run: rfkill > switchon.txt
4. Turn the airplain mode swith OFF.
5. Run: rfkill > switchoff.txt
6. Send us the files 'switchon.txt' and 'switchoff.txt'.
--
You received this bug notification
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1822047
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
Public bug reported:
airplane mode is not properly working as i switch it from my keyboard
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
.tmp.unity_support_test.0:
Apport
Please also:
4. Reproduce the problem again, hit Ctrl+Alt+F4 to log into a text
console and then run:
grep . /sys/class/drm/*/{dpms,enabled,status} > drminfo.txt
5. Send us the file 'drminfo.txt'.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
Please:
1. Confirm that "cannot boot into system" means you are seeing a purple
screen, not black.
2. Reproduce the problem (without nomodeset), reboot again using
"nomodeset" and run:
journalctl -b-1 > prevboot.txt
3. Send us the file 'prevboot.txt'.
** Changed in: xorg (Ubuntu)
Sta
If you have this issue and have a computer with a touch screen (like
Dell XPS or HP clamshells), just touch the screen to fix it.
Ref
https://youtrack.jetbrains.com/issue/JBR-563#focus=streamItem-27-2843582.0-0
--
You received this bug notification because you are a member of Ubuntu-X,
which is
To see a sample of dmesg when nouveau is activated, please refer to
lp:1822026
--
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/1822047
Title:
After install, cannot boot into system unless I use n
Public bug reported:
System: Disco (19.04 beta)
Hardware: Dell Precision 7530
After installing the system, it cannot start unless manually adding
`nomodeset` in the kernel command line at boot time.
Steps to reproduce:
1. Install disco 19.04 beta on the device. Leave all the options at default
https://bbs.archlinux.org/viewtopic.php?id=233230 is this related? It
seems it was fixed by "i915.enable_rc6=0" kernel parameter. Could you
have a try?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821882
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
62 matches
Mail list logo