[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
[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 Desktop
Packages, which is subscribed to network-manager in
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
The Grinch’s suit and speaking style. Since the story was first published in
1957, families eagerly have been repeating the Grinch's tale every Christmas
season.
https://grinchcostume.shop/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
There is a showoff competition between squishmallow enthusiasts where they are
always looking to get an upper hand over other kids by buying some fancy
squishmallows. Your kid might also be looking at the mushroom squishmallow
collection thinking to grab one for his collection.
Pretty nice post. I just stumbled upon your weblog and wanted to say
that I have really enjoyed browsing your blog posts. After all I’ll be
subscribing to your feed and I hope you write again soon!
Learn More:https://vikingaxe.shop/
--
You received this bug notification because you are a member
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 Desktop
Packages, which is subscribed to
In this case, you need to pack a pair of frog squishmallow toys for your
kids so that they can play with them in the car and the hotel room as
well. The compact size of the this squishmallow makes things easier as
the squishmallows frog can fit even in a small backpack which allows you
to pack
The attachment "nemo_5.4.3-2ubuntu0.1.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
I have made a Pull Request for upstream.
https://github.com/intel/media-driver/pull/1588
Once this is merged and released, we should pick this up in our snap build.
By setting GFX_FEATURE_FILE and GFX_FEATURE_FILE_NEXT we can then prevent
access to /etc/ dir.
** Changed in: chromium-browser
Applied the patches, not getting any nasty messages in /var/log/syslog
** Patch added: "nemo_5.4.3-2ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1998060/+attachment/5639800/+files/nemo_5.4.3-2ubuntu0.1.debdiff
** Changed in: nemo (Ubuntu Kinetic)
Status:
Public bug reported:
auth.log:649:Jan 6 21:32:17 ice-home dbus-daemon[802]: message repeated
20 times: [ [system] Rejected send message, 0 matched rules;
type="error", sender=":1.33" (uid=1000 pid=1182
comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)"
member="(unset)" error
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
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
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 Desktop
Packages, which is subscribed to mesa in Ubuntu.
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
The proposed fix has been merged to the xserver master branch.
The author of the fix also has a patch set against a recent xserver
stable release here:
https://github.com/kerneltoast/xserver/tree/new-tearfree-21.1.5
--
You received this bug notification because you are a member of Desktop
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
I can confirm that there is a memory leak at the indicated point in the
code, though I'm surprised it is noticeable as it only happens when
tr_rc4_new() fails.
Would you mind opening a bug report in Debian for this? (Since this was
upstreamed and Ubuntu is now in sync with Debian)
--
You
Intel provided guidance on how to address this. I will make a merge
request.
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1973470
Title:
BTW, I found few app can show on the correct monitor. e.g:
google-chrome, firefox,
when start these applications in Terminal on monitor B, they can show on the
monitor B.
but most other app can not.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages,
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
Yes, I encountered same issue on Ubuntu 20.04 with Unity desktop.
e.g: a laptop (monitor A) connected with an external monitor B over HDMI.
Monitor A is on the left of monitor B.
In the "System Settings" >> Displays, I selected "Launcher Placement" as
"All displays"
In the Terminal on monitor
It seems that the patch that fixed this might have been faulty and
introduced a memory leak.
See
https://github.com/NixOS/nixpkgs/issues/207047#issuecomment-1360393405
for some details.
Should I open a new issue for this?
** Bug watch added: github.com/NixOS/nixpkgs/issues #207047
@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
** 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 Desktop
Packages, which is subscribed
Happened again today. Again, was anything pushed last night that might
have triggered this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1999308
Title:
Snap keeps uninstalling apt
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
With the flag changes[1] that went in the hwacc/edge my webcam works
again.
[1]: https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=4c051e7082153f898e46e27d56466ae497cbfdfe
--
You received this bug notification because you are a member of Desktop
** Merge proposal linked:
https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/435222
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Bram Stolk (b-stolk)
--
*** 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
*** 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 Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
excerpt from top:
4625 michael 20 0 5077584 256364 114324 S 18,3 3,2 10:32.37
gnome-shell
1500 root 20 0 1139948 121488 72424 S 10,6 1,5 7:22.24 Xorg
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) =>
Can't I just update xorg package somehow (because it is not in the
official builds repository for jammy)? Or you think that this problem
might be fixed not in xorg, but somewhere else?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
If we don't know exactly what fixed it then the only supported solutions
are:
(a) Don't use Xorg. Select a desktop environment that supports Wayland
instead (like regular Ubuntu using GNOME); or
(b) Upgrade to Lubuntu 22.10 where Xorg appears to be fixed.
--
You received this bug notification
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:
But how do I update to that without building xorg from source myself?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2000649
Title:
Xorg crashed with SIGSEGV in
That's fine, it just means Xorg crashed hard. So please report new
crashes whenever they occur again and eventually we'll have more luck.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Looks like it might have been fixed when bug 1999213 got fixed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2000649
Title:
Xorg crashed with SIGSEGV in
Thanks. This seems to be the 5th most common Xorg crash in Ubuntu 22.04
but it doesn't happen at all in 22.10. So I am thinking it got fixed in
Xorg 21.1.4
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
** Summary changed:
- Xorg crashes or freezes
+ Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from
DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
--
You received this bug
I don't see anything useful in the log:
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: sending the secret exchange:
[sx-aes-1]\npublic=4uc+8Lpm5dEaUqICltU/1RtAGdPAJRNDnjN+h4KK4+V198oPek0B866EgtZjQLXjDS9IA4iI+46VWpzNpyNd9hyBDrch5nR>
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: calling the
I tried standard Ubuntu version of xorg and it immediately crashed. I
used the `ubuntu-bug` on it and this is the id (in .uploaded file):
949ad2ac-8d9f-11ed-9cde-fa163e993415.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server
No we can't process .crash files manually.
Can you check to see if Xorg logged messages about the crash in the
seconds prior to Thu Jan 5 14:09:26 2023?... Xorg likes to handle its
own crashes which sometimes causes us problems. We don't get clean crash
reports from Xorg, or that we don't get
The journal says contains these entries:
Jan 05 14:09:26 xlap systemd[1]: Starting Process error reports when automatic
reporting is enabled...
Jan 05 14:09:26 xlap systemd[1]: Started crash report submission.
Jan 05 14:09:26 xlap whoopsie[5359]: [14:09:26] Using lock path:
Thanks. Unfortunately that's not showing the crash location, I don't
know why:
https://errors.ubuntu.com/oops/311e7093-8cfa-11ed-aae6-fa163e55efd0
Can you find the system log entries (using journalctl) from the time of
the crash? (Thu Jan 5 14:09:26 2023)
--
You received this bug notification
The file contains this ID: 311e7093-8cfa-11ed-aae6-fa163e55efd0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
50 matches
Mail list logo
