** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1735594
Title:
[regression] compiz crashes after Mesa upgrade
To manage
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1727401
Title:
Corruption on windowed 3D apps running on dGPU (Intel/AMD)
** Package changed: ubuntu => mesa (Ubuntu)
--
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/1752343
Title:
Problem with DRI2 and GLX - bionic 18.04
To manage notifications about this bug go to:
You have been subscribed to a public bug:
I have encountered the problem described below, after some recent
updates in my Kubuntu. After asking on "Answers" I was requested to open
a bug, so I'm doing it.
My problem was, that kwin stopped to show graphical effects. I'm using a laptop
with Intel
sounds like you're trying to mix an external ppa and debian sid, that's
not supported..
** Changed in: mesa (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/17
Public bug reported:
Under 18.04, for about a week now, my touchpad’s pointer is very hesitant and
just stops most of the time. It will only starts moving again after clicking
buttons a couple times and will work for a second or two.
I have a similar problem running Bionic 2018-02-28 Live USB.
T
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received th
Same here error with edvi's DisplayLinkManager process to get a
displaylink screen from a USB 3.0 hub/docking station like
https://www.anker.com/store/USB-3.0-Docking-Station/68ANDOCKS-BA
went back to 4.4.0-112 to work.
Will wait future 4.4.0-(>116) kernel to retry.
--
You received this bug noti
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received th
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received th
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Invalid
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received th
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received th
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received th
Fair enough, I don't get this precise problem anymore, now it only takes
a long while before I see the login screen, but there's another ticket
for it somewhere.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
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/1752307
Title:
** Summary changed:
- xorg
+ incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
--
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/1752307
Title:
incompatible configuration in
** Description changed:
- Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
+ Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
I rebooted and i get a black screen before the login screen I am unable to
login.
Thanks.
+
+ --
+ Added by diddledan:
+ --
+ From
One more - please contact me before setting this again to invalid.
English is not my native, so I'd like to be sure, that misunderstanding
is not the cause for invalidating the report.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubunt
I hope after 10 years with kubuntu I'm not trying to mix anything...
This is my sources list:
deb http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic universe
deb http://archive.u
*** This bug is a duplicate of bug 1752307 ***
https://bugs.launchpad.net/bugs/1752307
** This bug has been marked a duplicate of bug 1752307
incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
--
You received this bug notification because you are a member of Ubuntu-X
** Tags removed: single-occurrence
--
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/1752307
Title:
incompatible configuration in default nvidia-drm-outputclass-
ubuntu.conf
To manage notificati
*** This bug is a duplicate of bug 1752053 ***
https://bugs.launchpad.net/bugs/1752053
** This bug has been marked a duplicate of bug 1752053
nvidia-390 fails to boot graphical display
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
*** This bug is a duplicate of bug 1752053 ***
https://bugs.launchpad.net/bugs/1752053
** This bug is no longer a duplicate of bug 1752307
incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** This bug has been marked a duplicate of bug 1752053
nvidia-390 fails to b
Public bug reported:
The touchpad works well on Windows but stops working after few seconds
on Ubuntu.
xserver-xorg-input-synaptics version: 1.9.0-1ubuntu1
xorg version: 1:7.7+19ubuntu3
xinput version: 1:7.7+19ubuntu3
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-input-syna
** Attachment added: "dmesg_boot"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1752588/+attachment/5066096/+files/dmesg_boot
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu
** Attachment added: "dmesg_diff"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1752588/+attachment/5066097/+files/dmesg_diff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu
** Attachment added: "Xorg.0.log_diff"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1752588/+attachment/5066099/+files/Xorg.0.log_diff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1752588/+attachment/5066098/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu
As you said, and freedesktop concluded:
Installing libegl-mesa0 package from experimental repository fixes the
bug.
As that package is installed by default, that report is now useless.
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
You have been subscribed to a public bug:
When I select "gnome" on login, the session fails to start. If I select
gnome/xorg all is well.
Description:Ubuntu 17.10
Release:17.10
wayland-protocols:
Installed: 1.10-1
Candidate: 1.10-1
Version table:
*** 1.10-1 500
500 ht
seems like some KDE dependency pulled in libegl1, which is what broke it
mesa & libglvnd will migrate from -proposed soon, so this should not
happen anymore
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.n
Ekhm... why do you say "As that package is installed by default"? Maybe
in experimental Debian, but not in Ubuntu. I had to find this solution,
manually download two deb files and install them creating a mess in my
package repository just to make my kubuntu working. Do you call that
"solution"?
** Package changed: ubuntu => wayland (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1752431
Title:
Wayland crashes on startup - artful
To manage notifications about this bug go to:
** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
Importance: Critical
Status: Triaged
** Also affects: xorg-lts-transitional (Ubuntu Bionic)
Importance: Undecided
Assignee: Timo Aaltonen (tjaalton)
Status: In Progress
--
You received this bug notification because
kde is messed up right now and pulled libglvnd packages which it
shouldn't have, so the actual fix with ubuntu packages would've been to
purge libegl1/libgl1 etc. We're in the middle of a transition which
debian did 6mo ago, and everything should be fine in a day or two.
--
You received this bug
it's Qt which now depends on libegl1 and migrated out of -proposed and
is breaking systems..
--
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/1752343
Title:
Problem with DRI2 and GLX - bionic 18.0
Thanks Timo for explanation. I'm aware of all inconveniences related to
running unstable system, looks that I have just hit one of those... I'll
keep my eye on it. I'd keep the bug open till those dependencies are
fixed, but it is up to you.
--
You received this bug notification because you are a
sorry, it was actually plasma-framework that depends on libegl1 and
would pull it
--
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/1752343
Title:
Problem with DRI2 and GLX - bionic 18.04
To manag
*** This bug is a duplicate of bug 1752053 ***
https://bugs.launchpad.net/bugs/1752053
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-
** Attachment added: "Xorg log file from Kubuntu 18.04"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719038/+attachment/5066425/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchp
Public bug reported:
Trying to see if there was any issues with my graphics drivers, as my
laptops screen keeps flickering. It flickers less so on browsers etc,
but I just booted up a game on steam and it was flickering constantly,
almost enough to give me epilepsy
ProblemType: Bug
DistroRelease:
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
My apologies. I didn't think about an issue from nearly a year ago. I'll
be honest, I just worked around the issue by using the graphics drivers
PPA.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://b
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
I didn't have a reliable way of reproducing exactly this scenario, so I
can't definitively say whether or not it's still present (I'm currently
running 17.10). I have experienced similar GUI hangs (but ssh still
responds) in 17.10, but not specifically while watching an embedded
youtube video in Ch
** Tags added: noclick
** Summary changed:
- Regression: left mouse button stops working
+ Left mouse button gets stuck down (in software), usually after suspend/resume
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libinput (Ubuntu)
Importance:
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1752431
When reporting bugs in the future please use apport by using 'ubuntu-
b
*** This bug is a duplicate of bug 1752053 ***
https://bugs.launchpad.net/bugs/1752053
Current "fix" / workaround, per my own post in #1752053:
I managed to fix my setup by using the Graphics Drivers PPA
(https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) and
forcing the install of
I would like to find out if this is a problem in libinput.
Can you please try installing Unity (package 'unity-session')? Then log
in to Unity and tell us if the problem also occurs there?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Changed in: libinput (Ubuntu)
Mesa is slowly getting there...
https://www.phoronix.com/scan.php?page=news_item&px=Intel-Lands-EGL-Ctx-
Priority
Hopefully radeon and nouveau will catch up too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launc
I installed updates today and now have the same problem. After login, I
see the desktop but no dash, no launcher, no alt tab, etc.
Running:
* ubuntu 16:04
* 4.4.0-116-generic
* xserver-xorg-core: 2:1.18.4-0ubuntu0.7
* libegl1-mesa:amd64/xenial-updates 17.2.8-0ubuntu0~16.04.1 uptodate
--
You rec
This bug was fixed in the package unity -
7.5.0+18.04.20180221.1-0ubuntu1
---
unity (7.5.0+18.04.20180221.1-0ubuntu1) bionic; urgency=medium
* Unity use track_obj to safely connect to UScreen and Settings
signals (LP: #1748330) (LP: #1748330)
* CairoBaseWindow: don't try to co
80 matches
Mail list logo
