The verification of the Stable Release Update for glib2.0 has completed
successfully and the package is now being 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 encounter a
This bug was fixed in the package glib2.0 - 2.76.4-0ubuntu1
---
glib2.0 (2.76.4-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2028082)
-- Jeremy Bícha Tue, 18 Jul 2023 15:39:46 -0400
** Changed in: glib2.0 (Ubuntu Lunar)
Status: Fix Committed => Fix
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
review all reported bugs in a timely manner.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
I'm setting the status of this bug to 'Incomplete'
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
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to
In case if noone can find where is the problem just instal fresh OS and run
nslookup google.com
Then check the validity of the symlink on resolv.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
You have been subscribed to a public bug:
Sometimes happens when I leave it (probably screen lock), sometimes
happens when I about to shutdown, sometimes happens when running. The
log shows it is related to xorg or nvidia.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2045722
Title:
Ubuntu freeze randomly
Status in xorg package in Ubuntu:
New
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
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
review all reported bugs in a timely manner.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Looking at this bug report in 2023 I can't
Hello Paul :),
The bug is still here as can be seen in the screenshot I just took and attached
to this comment.
I just downloaded the "sample script to reproduce the bug" I attached 9 years
ago and opened it with Vim on my laptop.
You can see that the commands inside parentheses are white
laurent@laurent-GL73-8SD:~$ vim --version
VIM - Vi IMproved 9.0 (2022 Jun 28, compilé Oct 16 2023 18:21:01)
Rustines incluses : 1-1672, 1840, 1846-1848, 1857-1858, 1873, 1969, 1992, 2010
Modifié par team+...@tracker.debian.org
Compilé par team+...@tracker.debian.org
Énorme version sans interface
That bug was filed before we fixed Jammy on 2023-11-20
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2023322
Title:
GTK internal browser does not render
@enr0n Nick, did you compare the full path of what i wrote? Also what do
you mean if I could provide specific example? As i wrote in main
question you dont need anything specific as i tried in fresh brand new
Ubuntu 22.04. Just install fresh new operating system and try to resolve
google.com and
** Tags added: architecture-s39064 bugnameltc-204450 severity-medium
targetmilestone-inin---
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't
Public bug reported:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8
What is the recommended source/target version that should nowadays be
used?
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Milestone: None => 2.28.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
That comment was sparked by duplicate bug 2041664 on jammy. Either it's
not really a duplicate or not a sufficiently new enough revision of 2.42
to contain the fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
So I managed to create a tar file with an extended attribute name of
length of ~ 36 bytes long (the largest I can do without exceeding
the existing check on maximum extended header lengths it seems) but this
is not able to trigger the vuln - so if you are able to share your PoC
that would be
Actually I just got it working - no need to send PoC @kerneldude - I
made my own.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/2029464
Title:
A stack overflow in GNU Tar
** Tags added: oem-priority originate-from-2045516
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2045621
Title:
Improve power consumption on Framework systems
Status in
** Changed in: oem-priority
Assignee: (unassigned) => Artur Pak (artur-at-work)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2045621
Title:
Improve power
I have the same problem, this bug has been around for quite some time as
it seems. Is there no fix available?
I have this problem with multiple machines, but I don't even find any
useful information about the copymods package aside from this bugreport
and the related posts.
--
You received this
Hi Artur,
We may want to use systemd-hwe to support this.
** Also affects: systemd-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: Artur Pak (artur-at-work) =>
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd-hwe (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd-hwe (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags added: amd originate-from-2044861
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2045621
Title:
Improve power consumption on Framework systems
Status in OEM
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Mantic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd-hwe (Ubuntu Mantic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
- As reported in the following question, Ubuntu 22.04 is currently missing the
CMake installation files from tinyxml version 9.0.0.
+ As reported in the following question, Ubuntu 22.04 is currently missing the
CMake installation files from tinyxml version 9.0.0.
** Description changed:
[ Impact ]
* Framework systems that have DP or HDMI cards connected will have
increased power consumption even when nothing is connected to DP or HDMI
ports since the cards don't default to autosuspend.
- * Backporting upstream patch that adds rules in
+ *
for Jammy
** Patch added: "systemd_249.11-0ubuntu3.12.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045621/+attachment/5726376/+files/systemd_249.11-0ubuntu3.12.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~ogayot/ubuntu/+source/lomiri-download-manager/+git/lomiri-download-manager/+merge/456875
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
Access to the vendor CI's won't happen anytime soon, so I'll expand the
test case for this stack.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Title:
Backport
** Description changed:
[Impact]
The graphics HWE stack from mantic needs to be backported for 22.04.4
directx-headers
- build-dep of the new Mesa
mesa
- new major release (23.2.x)
- new HW support, Meteor Lake..
[Test case]
- We want to cover at least 2-3 different,
** Merge proposal linked:
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1489489
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being 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 encounter a
For Jammy, Lunar, and Mantic, the correct fix is to add these rules in a
90-ubuntu-autosuspend.hwdb file in systemd-hwe.
** Changed in: systemd (Ubuntu Jammy)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu Lunar)
Status: Confirmed => Won't Fix
** Changed in: systemd
** Description changed:
[Impact]
The graphics HWE stack from mantic needs to be backported for 22.04.4
directx-headers
- build-dep of the new Mesa
mesa
- new major release (23.2.x)
- new HW support, Meteor Lake..
[Test case]
- Install the new mesa on various hw, see that
*** This bug is a duplicate of bug 2045621 ***
https://bugs.launchpad.net/bugs/2045621
It seems bug (bug 2045621) has been opened which is proposing the same
thing. That one has the SRU info required, so let's carry on there
instead.
** This bug has been marked a duplicate of bug 2045621
** Merge proposal linked:
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2045668
Title:
** Merge proposal unlinked:
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1489489
ubuntu 23.10
kernel 6.5.0-14-generic
ASUS Vivobook X1504VA
new installation (in 22.04 I first tried it didn't recognize wifi either, so I
installed 23.10)
issue: bluetooth cannot startup. it says "turn on bluetooth to connect devices"
expected: to be able to turn on bluetooth and connect to
We believe the original bug is fixed in webkit2gtk 2.42.2 and higher on
Ubuntu 22.04 LTS and newer with disable-dmabuf-nvidia.patch
My understanding is that Ubuntu's Nvidia drivers include libnvidia-egl-
gbm1 but Debian's drivers do not so that shouldn't be an issue.
If you are still
** Changed in: lomiri-download-manager (Ubuntu)
Status: New => In Progress
** Changed in: lomiri-download-manager (Ubuntu)
Assignee: (unassigned) => Olivier Gayot (ogayot)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
You have been subscribed to a public bug:
Finally with Ubuntu 12.10 the full VIM is installed by default. However,
the package vim-tiny is _also_ installed, and frustratingly it is the
vim-tiny binary that is used when typing 'vim' on the CLI. Please remove
the vim-tiny package from the default
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
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to
Further to comment #3:
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
All currently supported releases as of today's date, that is focal and
later, include this patch so I'm closing this bug report as being fixed.
** Changed in: vim (Ubuntu)
Status: Confirmed =>
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
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to
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
review all reported bugs in a timely manner.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
I'm closing this as 'Invalid' as neither the
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
review all reported bugs in a timely manner.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
An almost 11 year old bug report against an Ubuntu
It's working fine for me in Kubuntu 22.04 LTS now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1965439
Title:
[SRU] kdesu fails to authenticate with sudo from Jammy
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
This bug report has been filed against the 'vim' package but according
to the bug description vim is not installed so I'm closing this as
'Invalid'.
If the reported problem is still an issue while using a currently
supported
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
review all reported bugs in a timely manner.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
I'm setting the status of this bug to
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
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to
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
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to
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
review all reported bugs in a timely manner.
No version information has been given and with no comments for over nine
years I'm closing this as 'Invalid'. If
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
This issue may well 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
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still
** Changed in: vim (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/788481
Title:
Unity can't handle two GVIM's at the same time
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Probably just a bad package download for which:
apt-get clean, apt-get update, apt-get install vim-common
would have fixed the issue.
** Changed in: vim (Ubuntu)
Status: New => Invalid
--
You received this bug
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
review all reported bugs in a timely manner.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
I'm setting the status of this bug to
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
review all reported bugs in a timely manner.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 16.04 (xenial) reached
No version information given as to which Ubuntu release was affected by
the reported issue.
I'm closing this as 'Fixed Released' as in 2023 all currently supported
releases of Ubuntu will include the Vim patch referred to in the bug
description.
** Changed in: vim (Ubuntu)
Status: New =>
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Patch will be included in all currently supported releases of Ubuntu so closing
as being fixed.
** Tags added: vivid
** Bug watch added: Debian Bug tracker #774492
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774492
** Also
Same issue here as well, fresh install, but it's 23.10 Ubuntu Mate.
Shall it be reported separately for mantic ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
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
review all reported bugs in a timely manner.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
I'm setting the status of this bug to
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.
A sixteen year old bug report with few subsequent comments is of little
use to Ubuntu's
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
I'm closing this as 'Invalid' as no version information has been
provided and there has been no comments for over sixteen years.
** Changed in: vim
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
review all reported bugs in a timely manner.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
I'm setting the status of this bug to 'Incomplete'
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
review all reported bugs in a timely manner.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
I'm setting the status of this bug to 'Incomplete'
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
review all reported bugs in a timely manner.
I'm closing this bug report as 'Invalid' as no version information was
given for either Vim or Ubuntu and as
In 2023, does this bug have any relevance in a currently supported
release?
** Tags added: natty oneiric trusty
** Changed in: vim (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
Also thanks for the pointers. According to the upstream discussion this
is the needed fix:
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=d290630d31f4517ab26392d00753d1397f9a4114
It is included in
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
review all reported bugs in a timely manner.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
and the Xubuntu flavour around two
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
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to
*** This bug is a duplicate of bug 1144486 ***
https://bugs.launchpad.net/bugs/1144486
** This bug has been marked a duplicate of bug 1144486
package vim-gnome 2:7.3.429-2ubuntu2.1 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned error exit
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
review all reported bugs in a timely manner.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
I'm setting the status of this bug to 'Incomplete'
Closing as 'Invalid' as a 10 year old bug report with no version
information and no comments for some time is of little use to the
developers of currently supported releases of Ubuntu.
** Changed in: vim (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
** Also affects: vim via
https://github.com/vim/vim/issues/8015
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1903057
Title:
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
review all reported bugs in a timely manner.
This bug report has been filed against 'vim' but the bug description says that
vim is not installed.
You say
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
review all reported bugs in a timely manner.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
I'm setting the status of this bug to 'Invalid' as
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
review all reported bugs in a timely manner.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
I'm setting the status of this bug to 'Incomplete'
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
review all reported bugs in a timely manner.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
I'm setting the status of this bug to 'Incomplete'
*** This bug is a duplicate of bug 1754999 ***
https://bugs.launchpad.net/bugs/1754999
** This bug has been marked a duplicate of bug 1754999
Error detected while processing /usr/share/vim/vim80/debian.vim:
--
You received this bug notification because you are a member of Ubuntu
Touch
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
review all reported bugs in a timely manner.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
I'm setting the status of this bug to
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
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to
Closing as 'Invalid' but should be 'Wont Fix' as Ubuntu 8.04 was EOL in
2011.
** Changed in: vim (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
Untagging rls-nn-incoming based on insights from the MIR team in
#ubuntu-devel [1]
schopin: ogayot: usr-is-merged seems to be an empty meta-package. It's
source package src:usrmerge is already in main
does that mean we can just ask an AA to promote it, no paperwork?
so I'd say this doesn't
** Package changed: vim (Ubuntu) => ubuntu-seeds
** Project changed: ubuntu-seeds => ubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1069413
Title:
Tagging rls-nn-incoming so that we can discuss the new dependency on
usr-is-merged (>= 38).
While src:usrmerge is in main, usr-is-merged is currently in universe.
usrmerge | 9 | xenial/universe | source, all
usrmerge | 17| bionic/universe | source, all
usrmerge | 23|
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
I'm setting the status of this
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
A fourteen year old bug report which details an upgrade between releases
which were both 'end of life' over twelve years ago is not useful in
2023 so
Using Ubuntu 20.04 and 22.04 I'm not seeing the reported issue.
There have been no comments supporting the reported bug for over 11
years so as the status is 'Confirmed' I'm closing this as being fixed.
** Tags added: precise
** Changed in: vim (Ubuntu)
Status: Confirmed => Fix Released
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
review all reported bugs in a timely manner.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
I'm setting the status of this bug to 'Incomplete' as
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1
---
mesa (23.2.1-1ubuntu3.1) mantic; urgency=medium
* patches: Avoid crashing virglrenderer when the host doesn't support
PIPE_CAP_CLEAR_TEXTURE (LP: #2038834)
-- Mate Kukri Tue, 07 Nov 2023 15:41:32
+0200
**
Public bug reported:
1.14.10-3
Published in sid-release on 2023-10-30
dbus (1.14.10-3) unstable; urgency=medium
* d/control: dbus Depends on usr-is-merged (>= 38~).
Non-merged /usr has been unsupported since Debian 12, as per Technical
Committee resolutions #978636 and #994388 (please
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
review all reported bugs in a timely manner.
However, no Ubuntu version or flavour information has been given and as
there has been no comment on the bug
1 - 100 of 110 matches
Mail list logo