** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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 fr
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 Ubuntu
Desktop Bugs, wh
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1928867
Title:
System freeze on bulk rena
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
https://gitlab.gnome.org/GNOME/nautil
** 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 not
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 /* 83
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
corrado@corrad
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 membe
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
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2047579
Title:
gnome-softw
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 notification
** Changed in: nautilus (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993127
Title:
/usr/bin/nautilus:11:g_list_store_find
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 beca
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 ea
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 (th
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1928867
Title:
System freeze on bulk rename
To manage notif
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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/b
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 b
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 b
Could you perhaps attach an example of file showing the issue?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2047737
Title:
Nautilus crashes when opening folders that contain fil
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
an
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 O
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 syst
25 matches
Mail list logo
