Public bug reported:
(base) walid@len:~$ lspci | grep VGA
:00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01)
(base) walid@len:~$ sudo lshw -C video
[sudo] password for walid:
*-display
description: VGA compatible controller
product: Int
It is supported, just the name of the GPU is unknown in 22.04. This has
been fixed already in later Ubuntu versions and should not affect
performance at all.
** Summary changed:
- Seems like my GPU isn't supported
+ Intel PCI ID 8086:9a78 missing in pci.ids
** Package changed: xorg (Ubuntu) => p
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689
That does sound like it could be an issue for sure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bug
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689
Ah my apologies, I didn't realise I had already reported this a few
months back when updating to jammy here
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750
--
You received this bug notif
Public bug reported:
Apport cli cant open Lubuntu browser
*** Uploading problem information
The collected information is being sent to the bug tracking system.
This might take a few minutes.
99%
*** To continue, you must visit the following URL:
https://bugs.launchpad.net/ubuntu/+source/calama
Public bug reported:
Apport works, but ubuntu-bug shows internet error 500
The collected information is being sent to the bug tracking system.
This might take a few minutes.
99%
*** Error: Network problem
** Summary changed:
- Apport works, but ubuntu-bug shows internet error 500
+ ubuntu-bug shows internet error 500, but Apport works
** Description changed:
- Apport works, but ubuntu-bug shows internet error 500
+ ubuntu-bug shows internet error 500, but Apport works
The collected informati
Public bug reported:
Update required restart, before restart the display was working as
expected. After restart the system does not even detect the display,
even after unplugging and plugging back the HDMI.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSign
*** This bug is a duplicate of bug 1973470 ***
https://bugs.launchpad.net/bugs/1973470
** This bug has been marked a duplicate of bug 1973470
Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
** Package changed: apport (Ubuntu) => launchpad
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2002119
Title:
ubuntu-bug shows internet error 500, but Apport works
Status
** Tags added: jammy
** Also affects: apport (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: xdg-utils (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I second backporting this to jammy at least as it is an LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." imme
@guiverc i just tried latest iso lubuntu-22.04.1-desktop-amd64.iso and reported
Bug 2002120 that now is a duplicate of this. So its not fixed.
My bug is about Apport. Is this about ubuntu-bug? So then mine is not
duplicate, or why its the same package?
Ubuntu-bug doesnt work for me at all because
Backporting to LTS is a good idea IMHO. A few additional use cases to
consider
- Users on the threshold who experience slight initrd image growth due
to any module update
- Users who thought they might be able to continue just using older
images may fail to recognize grub will eventually remove
Cannot reproduce on Lunar. I'm suspecting this is an issue with
fontconfig as there were some changes between Jammy and Lunar.
** Also affects: guitarix (Ubuntu Lunar)
Importance: Undecided
Status: Incomplete
** Also affects: guitarix (Ubuntu Jammy)
Importance: Undecided
Statu
ubuntu-bug is a command from Apport. This bug is fixed in Ubuntu >=
22.10 (kinetic) but not in 22.04 (jammy) – yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1973470
Tit
Since there appears to be upstream patches in kernel 6.0 and Mesa 22.3.1
which fix this, perhaps it would be possible to backport those to the
versions in Ubuntu 22.10? If not, would it at least be possible to
upload such packages to Lunar so that there's an option which doesn't
involve reinstalli
Hello errors.ubuntu.com, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
I accepted 22.0.5-0ubuntu0.3 which does NOT fix this bug, so I'm
reopening it.
** Changed in: mesa (Ubuntu Jammy)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https
Hello Kai-Chuan, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
I ran update-maintainer on the mesa source and uploaded again.
Give the removal of PCI IDs, and the vague statement in the "Where
things could go wrong" section of the bug description, I'd like to see a
more clear statement saying that these IDs are already not available in
the jammy kernel, and a
** Changed in: cloud-init
Assignee: (unassigned) => James Falcon (falcojr)
** Changed in: cloud-init
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.l
The entire upload will be uploaded to all older releases but we do have
a security upload already in the unapproved queues that should go out
first, but that needs approving those first, them passing the SRU
verification, a resigning against the new signing key the new shim
needs, and finally someo
You have been subscribed to a public bug:
by wanting to change the language in the parameters it displays these
errors to me.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5
** Package changed: cryptsetup (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2002187
Title:
package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed t
These calm and quite cute little toys are the perfect alternatives as they are
the fluffiest, the cutest, and simply do not make any noises.
cow squishmallows:https://cowsquishmallow.com/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manag
Have you forwarded this patch to Debian? Debian doesn't *currently*
have any flavors that are a substring of another, but that is not a
policy in Debian, so the patch is also applicable there.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Fix Committed
--
You received this b
The bug is still present in Ubuntu 22.10 on a Gigabyte Technology Co.,
Ltd. GA-990FXA-UD3, when attached to an HK Onyx Studio 6.
Usually a work around is to restart the Bluetooth stack twice.
My wild guess is that a (ring) buffer in the Bluetooth stack is filled,
and isn't reset because the sound
29 matches
Mail list logo