@Nick, if the issue is easy to trigger in your setup would it be
possible to at least test on a machine if installing a recent version of
firefox would fix the issue?
as for your question about flag/profiler I don't have any suggestion
offhand and would need to investigate but again you might
Hi All,
I'm a developer with Steve's group. Thank you for taking a look at this
and linking to that other bug! I took a look through the profiler
summaries linked in the thread and it appears very similar to what we
are observing. We also captured performance profiles for the current
version of
Public bug reported:
- this is a fresh install of the latest Ubuntu 24.04
- I have fully updated the debs and snaps
- my mouse cursor is grey when it should be black
- the strange thing is the cursor looks normal when I boot off the USB
and then looks grey on first boot
- even more strange is
** Tags added: noble
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2030947
Title:
gnome-shell spams journal with `g_closure_add_invalidate_notifier:
assertion 'closure->n_inotifiers <
Let's let it close automatically... if there are no more comments in two
months.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Public bug reported:
sudo apt-get install -f
[sudo] password for gord:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
i965-va-driver
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2043177
Title:
gnome-shell crashed with SIGSEGV in wl_resource_post_error_vargs from
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2047256
** Tags added: iso-testing
--
You received this bug notification because you are a member of Desktop
Packages,
Hello,
The reported version of Firefox (100.0.2) is rather old at this point,
and could be a potential security risk: to my knowledge, Mozilla don't
backport bug fixes to older versions of Firefox (except for the current
Firefox ESR series), and many security and non-security related issues
have
** Summary changed:
- Firefox utilizins 100% of station CPU
+ Firefox utilizing 100% of station CPU
--
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/2048792
Title:
Firefox utilizing
Thank you for your bug report. We don't really change the code over
upstream and have limited resources and knowledge of the project
compared to them, it would be a good idea to check if there is a similar
issue reported on https://bugzilla.mozilla.org/ already and if not to
open also there.
We
There is a fix proposed on
https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/575
** Changed in: nautilus (Ubuntu)
Importance: Undecided => High
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Triaged
** Also affects: gnome-shell via
There is a fix proposed on
https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/575
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1928867
Title:
System freeze on bulk rename
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Triaged
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872
Importance: Unknown
Status: Unknown
--
You received this bug
Additional info:
Firefox is at version 100.0.2
It is installed as a deb package
We're running Ubuntu 20.04
--
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/2048792
Title:
Firefox
Public bug reported:
Hi
Since the end of last november, screen sharing no longer works, i get a black
screen.
here is the log i get
nouveau :01:00.0: gr: DATA_ERROR 009c [] ch 1 [02ffd8c000 gnome-
shell[1369]] subc 0 class c797 mthd 17e0 data 0030
if i install NVIDIA proprietary
Same on Ubuntu 22.04.3 LTS, I've Keybase installed. I've killed nautilus
(as "nautilus -q" didn't help), killed all keybase processes (one stuck
at [keybase] ), but didn't help either. nautilus still doesn't
start.
$ strace -f nautilus
execve("/usr/bin/nautilus", ["nautilus"], 0x7ffe661c58b8 /*
Same on Ubuntu 24.04
corrado@corrado-n9-nn-1210:~$ apt policy gnome-shell
gnome-shell:
Installed: 45.2-1ubuntu1
Candidate: 45.2-1ubuntu1
Version table:
*** 45.2-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
By burnout or overload of USB I mean I like stored more than that 2.1TB
stick could hold and if it helps it is now a drive not recognized as
being there to an extent of being usable but recognized as existing
maybe or maybe not, maybe.
--
You received this bug notification because you are a
Public bug reported:
At a high level, in certain instances we’re experiencing sustained
abnormally high (100%) CPU utilization from Firefox. This utilization
is competing with other critical application processes on the systems,
starving them of resources, causing issues in the application
This issue was fixed a couple of months later in a regular update. I'm
on 23.10 now on the same machine and haven't had any problems with snaps
since. The issue can be closed as far as I am concerned.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I now remember I got USBs at time of reinstalling OS. That means that
all USB operations were after reinstalling. I now think order was
reinstall OS, check size, reformat USB, rsync to USB and burn out, then
reformatting another USB and checking. Feel free to check like my logs
on this but I think
@lastexile7gr
The package doesn't come automatically with the updates, you have to pass "-t
mantic-proposed" when using apt.
This is the command I've used to update the mutter package in my system:
sudo apt install mutter-common -t mantic-proposed
--
You received this bug notification because
i guess rebuilding gnome snaps with proposed on arm64 and testing that
new gnome snap on mantic for pi5 & x1s would help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Title:
Thanks for the idea, however I give up with this 'bug', I will upgrade
this laptop to Xubuntu 23.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2047579
Title:
unigine tests take no parameters, just launch and run
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Title:
Backport packages for 22.04.4 HWE stack
Status in directx-headers
I agree that there is an issue with making it difficult for people to
easily and fully test -proposed updates.
I wrote a blog post about the way I install packages from -proposed.
Steps 0-3
https://jeremy.bicha.net/2022/03/29/how-to-install-a-bunch-of-debs/
--
You received this bug
Can somebody modify the description to specify exactly how to do those
tests, please? (which commands/parameters, and expected results).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
** Changed in: nautilus (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993127
Title:
Upstream: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2872
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification
What we _could_ perhaps do (because detecting a URI in a text flow is
undefined territory, with already quite a few quirks in place, such as
stripping off the trailing dot) is to strip off the trailing
":linenumber". That is, the trailing ":" if it's followed by numbers
only.
That way you could
To ubuntu 22.04, I refer to
https://roll.urown.net/desktop/network/time-sync.html.
Using NM's dispatch scripts, NetworkManager can talk with timesyncd when
configuring to use internal dhcp client.
If want to use dhclient's hook, I think you should configure NetworkManager to
use dhclient.
The problem is: according to the URI specification, there is no way to
denote the line number. In fact, the URI
"file:///full/path/to/filename.cpp:linenumber" refers to a file whose
name is literally "filename.cpp:linenumber".
Correspondingly, the entire stack that handles the opening of a URI
First, thank you to Jeremy Bicha and Steve Langasek, and anyone else
involved in bringing the update to mutter.
I've been trying for the past few days to install the update. I enabled
-proposed, but every time I try to install the newer version of mutter
(whether directly by the version name, or
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1928867
Title:
System freeze on bulk rename
Status in
This is a known upstream bug:
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1443
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1443
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1443
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this
Could you perhaps attach an example of file showing the issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2047737
Title:
Nautilus crashes when opening folders that contain files
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
By memory I know I overloaded a 2.1TB USB some time. I had a previous OS
by same USB bootable thing and almost same setup. I know I used rsync
with no exclude or -x or --one-file-system to overload that USB. I think
I overloaded it BEFORE reinstalling OS. I think order was overload USB,
reinstall
Public bug reported:
I reformatted to NTFS on another computer, I then reformatted to ext4,
could not write, then reformatted some and some took ownership, almost
always "read only". After all that and always naming it "UbuntuFilesXE"
I have a large /media/norvel/UbuntuFilesXE part of like my
41 matches
Mail list logo
