libgl1-mesa-dri:amd64 23.0.4-0ubuntu1~22.04.1
--
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/1989964
Title:
Segmentation fault crocus_dri.so (X server dies)
To manage notifications about this
The problem still exists:
Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Backtrace:
Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 0:
/usr/lib/xorg/Xorg (?+0x0) [0x5614c77b0939]
Aug 29 18:35:21
@oibaf, read your request. unfort i just started rebuilding my profile
from scratch. i'm in the process of re-adding all the applets, and other
X stuff. will keep you posted.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
I'm seeing the exact same error on 450-server, 470-server, 510-server
and 515-server in the glibc autopkgtests
https://autopkgtest.ubuntu.com/results/autopkgtest-
lunar/lunar/amd64/n/nvidia-graphics-
drivers-450-server/20230217_153300_3ba46@/log.gz
There's also other failures on 470, 510 and 515
also on libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1
--
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/1989964
Title:
Segmentation fault crocus_dri.so (X server dies)
To manage notifications
It looks like Debian autosync already took care of this. Please don't
hesitate to resubscribe ~ubuntu-sponsors if there's anything else we can
do.
Thanks!
** Changed in: intel-media-driver (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
reported upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7626
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
is this read/followed by upstream? or should i find upstream myself to
report 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/1989964
Title:
Segmentation fault crocus_dri.so (X server dies)
** Tags added: foundations-triage-discuss
--
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/1991761
Title:
Backport packages for 22.04.2 HWE stack
To manage notifications about this bug go to:
[335842.604] (WW) glamor: Failed to allocate 128x88 FBO due to GL_OUT_OF_MEMORY.
[335842.604] (WW) glamor: Expect reduced performance.
[335844.555] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glMapBuffer(map failed)
followed by
[335844.561] (EE) glamor0: GL error: GL_INVALID_OPERATION in
Public bug reported:
The desktop session is running for 0 or more days. Suddenly the X server
dies, and login screen reappears.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux
Versions tested against jammy (retrieved via jammy-proposed updates):-
ii xserver-xorg-video-ati 1:19.1.0-2ubuntu1
ii xserver-xorg-video-radeon 1:19.1.0-2ubuntu1
Tried these updates alone, tried in combination with other jammy-proposed too.
Tried on previously-crashing radeon system. Tried on
I can confirm the same crash happening with 22.04 Xorg and radeon card:-
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar
[Radeon HD 5000/6000/7350/8350 Series]
... when trying to rotate... which always used to work before e.g. in
20.04LTS.
--
You received this bug
I've found a workaround that was tested on Ubuntu 20.04:
$ cat /etc/systemd/system/systemd-logind.service.d/override.conf
# XXX: required to have /proc mounted with hidepid=2,gid=pidgrp
[Service]
SupplementaryGroups=pidgrp
--
You received this bug notification because you are a member of
Public bug reported:
When having more than one window open, e.g. Firefox and a terminal and
then to swap between the two. The clicking with the mouse stops working
but it still moves. For instance when I hover over text or not the
cursor does not change. Sometimes I can still click or select text
I am also affected by this bug. I am running Linuxmint and Cinnamon just
keeps crashing. Most of the times it is the result of clicking a few
things and opening / closing guake at the same time.
Installing the proposed packages does not fix the problem though, I am
still encountering frequent
*** This bug is a duplicate of bug 1920632 ***
https://bugs.launchpad.net/bugs/1920632
This has been marked as a duplicate of bug #1920632 (which it may well
be) - however I am experiencing these crashes on kernel 5.4.0-70-generic
(i.e. the GA kernel for 20.04.2) - is it possible to get the
Ubuntu 20.04 still has this bug with mutter 3.36.7+git20201123-0.20.04.1 amd64
and nvidia-340.
The workaround to set the wallpaper resolution to the screen resolution does
work though! Thanx for that!
--
You received this bug notification because you are a member of Ubuntu-X,
which is
It's "Won't fix" only for the component xorg, because it won't/can't be
fixed in that component.
The fix has already landed in the relevant package (xfce4-panel).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Solved this (and some other issues) for me by installing the mainline kernel
Used the "mainline" script for that
e.g. with instructions from
https://www.linuxuprising.com/2018/10/2-utilities-to-install-latest-kernel-in.html
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You
Public bug reported:
When booting, the log on screen shortly appears, but then (after less
than a second) disappears, leaving a black screen with a single
underline cursor.
Uncommenting "WaylandEnable=false" in /etc/gdm3/custom.conf fixes the
problem.
Graphics card: AMD Radeon RX 580
This effects me also:
ubuntu 20.04
GeForce GTX 1050 Ti Mobile
4k monitor - usb-c port
That work find in ubuntu 19.10 and same driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
This also happens in 20.04.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1826597
Title:
Synaptic touchpad not responding in ubuntu 19.04 when using nvidia
drivers
Hi.
Everything freezes. The clock on my screen shows the seconds. which has
also frozen. Pressing ctrl-alt-f2 etc, to get to a login prompt doesn't
work. Only a hard reset can clear it.
I have installed the amdgpu pro drivers, supplied by AMD, and will see if
that helps resolve the issue.
On
Public bug reported:
I can't provide much in the way of detail as the freezes are seemingly
random. They happen with different software being used.
Release: Ubuntu 18.04.2 LTS
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu
UPDATE:
Solved by disabling bluetooth in bios according to:
https://askubuntu.com/questions/1028883/ubuntu-18-04-systemd-udevd-uses-
high-cpu-conflict-with-wifi
It is silent and cool now.
Under the link you can find guys saying that this systemd-udevd 100% cpu
usage is because of the dell
UPDATE:
After blacklisting nuoveau and installing nvidia driver, there was no overheat
shutdown, but the cpu is on full speed all the time. and the tempetature is 87
celsius constantly.
I tried disabling pstate, using tlp, neither worked so far.
Here is a usual frame from top:
top - 21:19:30 up
Uploaded.
For the future, please make sure to use the -v argument when generating
your source.changes file for merges.
Thanks!
** Changed in: xkeyboard-config (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which
Ubuntu offered me a security update. It was offering it for a long time
and I didn't want to take it, because I didn't wanted to mess it up. But
installed all, and it messed it up with kernel 4.15: it couldn't install
the 340 nvidia driver I need into the new kernel. It became an endless
loop when
Left out: the kernel which is working now is the same, that had the
overheat with nouveau: 4.15
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1768976
Title:
Ubuntu 18.04
The issue persists in version 18.10
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1768976
Title:
Ubuntu 18.04 is overheating after upgrade from 16.04
To manage
Has the same issue with Linux Mint 19.1, I read that it is based on
Ubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1768976
Title:
Ubuntu 18.04 is overheating
The uncommenting #WaylandEnable=false worked a treat for me as with the
previous posters. This is the answer to this problem and needs pinning
to the thread!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Not sure it's helpful to add all panel-like applications that are
affected by this problem to the bugreport - unless of course you want to
track which applications implemented the same workaround (which seems to
be the only known workaround anyway - if you don't want to intercept
X11's signals
)
Importance: Undecided
Status: New
** Changed in: xfce4-panel (Ubuntu)
Assignee: (unassigned) => Simon Steinbeiß (ochosi)
--
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/1795
So obviously this is a known bug and literally every panel-like
application is affected. It also seems there is no good solution so far
apart from the aforementioned workaround of switching away from xinput2
via the environment variable.
** Bug watch added: freedesktop.org Bugzilla #92681
Hi guys, this problem is still present in Ubuntu 18.04, Portugese Apple
wired USB keyboard.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/214786
Title:
Apple USB ISO keyboard has
UPDATE:
I wanted to try out installing 18.04.1
After having the live mode started and opening the menu my laptop shutted down
suddenly and it is hot now.
Also it somehow messing up the fan. I have to restart from Windows to have it
sound and work fine.
Windows is running like charm, no
I had the same issue with clean install of Ubuntu 18.04.
16.04 was working fine with my laptop.
Laptop: Dell Studio XPS 1340, Processor: Intel Core 2 Duo P8600, VC: GeForce
9400MGE
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Package changed: xterm (Ubuntu) => nm-tray (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1782579
Title:
lubuntu 32bit daily image 2018-07-18 nmtui-edit won't show; needs
xterm
Better?
** Patch added: "2-1.4.0-1-to-1.4.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1779531/+attachment/5160201/+files/2-1.4.0-1-to-1.4.0-1ubuntu1.debdiff
** Changed in: xinit (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug
Here is a debdiff applicable to 1.4.0-1.
** Patch added: "1-1.4.0-1-to-1.4.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1779531/+attachment/5158304/+files/1-1.4.0-1-to-1.4.0-1ubuntu1.debdiff
--
You received this bug notification because you are a member of
-tty.patch, 08_pick-free-display.patch:
delete, applied upstream
-- Julien Cristau Mon, 19 Mar 2018 08:41:43
+0100
** Affects: xinit (Ubuntu)
Importance: Wishlist
Assignee: Simon Quigley (tsimonq2)
Status: In Progress
--
You received this bug notification because you
** Changed in: x11proto-core (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11proto-core in Ubuntu.
https://bugs.launchpad.net/bugs/120788
Title:
(needs x11 protocol update) XKB cannot map
Please create a new issue if needed but refrain from posting questions
like that here. This is not a mailing list.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1308105
Title:
** Also affects: nvidia-graphics-drivers-384 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1743094
Title:
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Reversing the status change because Lyn informed me she is still
affected.
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => New
** Changed in: xserver-xorg-input-mouse (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
This is fixed for me in the latest set up 18.04 updates. It's wonderful.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1749689
Title:
Lenovo Yoga 11S touchpad is jittery
To manage
Public bug reported:
Please sync libinput 1.10.3-2 (main) from Debian unstable (main). It
contains a handful of useful touchpad fixes that would be good to have
in the LTS.
Changelog entries since current bionic version 1.10.1-1:
libinput (1.10.3-2) unstable; urgency=medium
[ Jeremy Bicha ]
I added a link to the upstream bug, thanks for the guidance Daniel.
** Bug watch added: freedesktop.org Bugzilla #105508
https://bugs.freedesktop.org/show_bug.cgi?id=105508
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=105508
Importance: Unknown
Finally found what changed. I updated /etc/fstab to have /proc mounted
with hidepid=2,gid=sudo for added security. This works perfectly on
16.04 but totally breaks on 17.10.
To recap: mounting /proc with "nodev,noexec,nosuid" works but adding
"hidepid=2,gid=sudo" breaks.
** Tags added:
** Summary changed:
- Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1
(Permission denied)
+ mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole:
Cannot open virtual console 1 (Permission denied)
--
You received this bug notification because you
11:12 .
drwxr-xr-x 14 root root 4096 Aug 1 2017 ..
-rw-r- 1 root whoopsie 560003 Mar 7 13:16
_lib_systemd_systemd-udevd.0.crash
-rwxrwxrwx 1 root whoopsie0 Mar 9 11:11 .lock
-rw-r- 1 simon whoopsie 1585974 Mar 9 11:12 _opt_atom_atom.1000.crash
-rw-r- 1
Christopher, thanks for responding so quickly!
It took me a while to download the newest ISO.
I've been able to narrow it down a bit more as well: the log out only
happens if I have my second monitor plugged in. Sometimes (but not
always) the second monitor will flash the "logged out" screen for
Public bug reported:
This is a new bug report for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362075
I am running Ubuntu 16.04.4 LTS 64-bit + gnome, the standard
installation as downloaded from the Ubuntu website, on a Lenovo ThinkPad
T440s.
When I close the lid of my laptop, my
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Qt 5.9.4 is now in bionic-proposed.
** Tags removed: block-proposed
--
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/1749472
Title:
mesa 18.0.0 will cause rendering errors in Qt applications
To
That would be the ideal way to do it because the fix is already
installable in the CI Train PPA for the next Qt transition:
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3113/+packages
That should be in -proposed before Feature Freeze, if not before then.
Is there a compelling
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => Wishlist
--
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/1653828
Title:
Grammatical mistake in
block-proposed still belongs for mesa, having it blocked for other
reasons isn't good enough because this bug will break the Kubuntu and
Lubuntu Next desktops.
** No longer affects: qtbase-opensource-src (Ubuntu Bionic)
** No longer affects: qtbase-opensource-src (Ubuntu)
** Tags added:
** Changed in: sddm (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1668722
Title:
60x11-common_xdg_path uses $DESKTOP_SESSION which
)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: xorg (Ubuntu Bionic)
Importance: High => Wishlist
** Changed in: xorg (Ubuntu Bionic)
Assignee: Simon Quigley (tsimonq2) => (unassigned)
** Changed
** Changed in: xorg (Ubuntu Bionic)
Milestone: None => ubuntu-18.02
--
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/1668722
Title:
60x11-common_xdg_path uses $DESKTOP_SESSION which needs a
** Changed in: xorg (Ubuntu)
Importance: Undecided => High
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.ne
** Tags removed: rls-bb-incoming
--
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/1668722
Title:
60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check
To manage notifications
** Tags added: rls-bb-incoming
--
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/1668722
Title:
60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check
To manage notifications
1 - 100 of 587 matches
Mail list logo
