[Bug 1925732] [NEW] new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
Public bug reported: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. ** Affects: ubuntu Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
Don't get the crash any longer. Den tors 22 apr. 2021 kl 16:41 skrev Launchpad Bug Tracker < 1820...@bugs.launchpad.net>: > This bug was fixed in the package nautilus - 1:3.38.2-1ubuntu2 > > --- > nautilus (1:3.38.2-1ubuntu2) hirsute; urgency=medium > > * d/p/19_unity_open_location_xid: > - Do not update opened locations on bus connection. > Nautilus may connect to the bus when the application is already about > shut down, however at that point its implementation is destroyed but > Gio doesn't handle this gracefully as per GNOME/GLib!2056. > To prevent this, we can safely reduce the delta of the distro-patch > by > avoiding updating the opened locations on bus acquired, as we > already do > it in all the cases a window actually changes its state. (LP: > #1820859) > > -- Marco Trevisan (Treviño) Wed, 21 Apr 2021 > 07:03:29 +0200 > > ** Changed in: nautilus (Ubuntu Hirsute) >Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1820859 > > Title: > nautilus --version segfaults in > g_application_impl_get_dbus_object_path > > Status in nautilus package in Ubuntu: > Fix Released > Status in nautilus source package in Hirsute: > Fix Released > > Bug description: > * Impact > > nautilus hits a segfault when called with the version argument, which > was annoying but became problematic in hirsute since the desktop icons > ng calls that command to check if nautilus is available > > * Test case > > $ nautilus --version > shouldn't segfault > > * Regression potential > > The change is in a patch which was added to expose open locations to > Unity for the benefit of the launcher and which is also used by the > dashtodock one now. Check that the launcher correctly indicates which > windows are active, especially when dealing with external devices. > > -- > > > The Ubuntu Error Tracker has been receiving reports about a problem > regarding nautilus. This problem was most recently seen with package > version 1:3.31.90-1ubuntu2, the problem page at > https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 > contains more details, including versions of packages affected, stacktrace > or traceback, and individual crash reports. > If you do not have access to the Ubuntu Error Tracker and are a software > developer, you can request it at http://forms.canonical.com/reports/. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions > -- Skickat från min Sony Xperia eller Ubuntu -- 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/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Forget about the messages that I show in the previous post: it seems that this problem is also happening in Ubuntu 20.10 groovy and are unrelated to the original bug. I didn't realize these messages before because in groovy these messages are way less informative than in hirsute. In groovy it only show: abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat' abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat' So it's probably happening since ages... Thank you very much for the quick fix and happy releasing. -- 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/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
BTW: as I said the problem is solved with the proposed builds. So, the indicator-multiload app is working as expected. But I just realized that is throwing another messages at its start, messages that it's not throwing in Ubuntu 20.10 groovy. These are the messages: amd64: -- abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: JS ERROR: Exception in callback for signal: shown: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _showDone@resource:///org/gnome/shell/ui/overview.js:604:14 onComplete@resource:///org/gnome/shell/ui/overview.js:589:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 arm64: -- abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Exception in callback for signal: shown: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _showDone@resource:///org/gnome/shell/ui/overview.js:604:14 onComplete@resource:///org/gnome/shell/ui/overview.js:589:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _updateWorkspacesActualGeometry/this._syncActualGeometryLater<@resource:///org/gnome/shell/ui/workspacesView.js:716:22 But, as I said, I think these messages are not having impact in the execution of indicator-multiload app. At least I didn't notice any problem. Just wanted to comment it, just in case. -- 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/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Just tested amd64 packages with the same results than arm64: problem is solved. Thanks and best regards. -- 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/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Hello Brian,
Just tested arm64 build; updated these packages:
- gjs_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy gjs
gjs:
Instalados: 1.67.2-2ubuntu2
Candidato: 1.67.2-2ubuntu2
Tabla de versión:
*** 1.67.2-2ubuntu2 100
100 /var/lib/dpkg/status
1.67.2-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
- libgjs0g_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy libgjs0g
libgjs0g:
Instalados: 1.67.2-2ubuntu2
Candidato: 1.67.2-2ubuntu2
Tabla de versión:
*** 1.67.2-2ubuntu2 100
100 /var/lib/dpkg/status
1.67.2-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
And, after reboot, the problem reported is solved:
1./ Test case:
fprietog@fpgrpi:~$ gjs -c
"imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype, 'delete_async',
'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && echo
GJS works
[object Promise]
GJS works
2./ The error shown in every boot as also gone.
3./ The indicator-multiload app now is working as expected
I'll test amd64 build when available.
--
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/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Hello fprietog, or anyone else affected, Accepted gjs into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.67.2-2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gjs (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Please test proposed package
Hello fprietog, or anyone else affected, Accepted gjs into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.67.2-2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925379] Re: Auto-Correct does not work since upgrade to Hirsute
I can confirm this issue and it is caused by the current gtk+-3.0 package. Running with gtk+-3.0 3.24.28+git fixes the issue locally for me. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct does not work since upgrade to Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925683] Re: Cursor Tracking with Gnome Shell Magnifier on Wayland
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112 -- 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/1925683 Title: Cursor Tracking with Gnome Shell Magnifier on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925683] [NEW] Cursor Tracking with Gnome Shell Magnifier on Wayland
Public bug reported:
Affected version
GNOME 3.36 - 3.40.
Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
Wayland only.
Bug summary
When running GNOME shell with Wayland, the cursor and focus tracking
functionality of the magnifier (a11y feature) do not correctly compute the
cursor/focus location. The position is calculated from the top left of the
window but the windows position is not included. This causes the magnifier to
track the wrong location when the window is not maximiser or is on a second
monitor.
I suspect this is related to the way in which wayland is designed. But
my experience in this area is minimal. When using X11 this feature works
correctly.
The wiki page states that under wayland the cursor and focus tracking
work but this information is either out dated or was not tested
correctly.
Steps to reproduce
>From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by
>opening the activities overlay and searching for "terminal".
Press super + left arrow key to maximize the terminal window on the left side
of the screen.
Activity the magnifier by pressing super + alt + 8.
Type text into the terminal window. The magnified view will move with the text
cursor.
Press super + right arrow key to maximize the terminal windows on the right
side of the screen.
Type text into the terminal. The magnified view will move but it will not show
the text cursor. It will move when text is entered but will focus on the left
side of the screen.
What happened
The magnified view does not follow the text/focus cursor correctly.
What did you expect to happen
The magnified view should follow the cursor and show the cursor as it does when
the widnows is maximized. The correct behaviour can also be seen in Gnome shell
running with X11.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 22 20:55:25 2021
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-04-22 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute wayland-session
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4112
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112
--
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/1925683
Title:
Cursor Tracking with Gnome Shell Magnifier on Wayland
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925683/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925680] [NEW] Accessing the filesystem hangs unless µI kill gvfsd-trash
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 gvfs: Installed: 1.44.1-1ubuntu1 Randomly my filesystem hangs during 30s when I'm trying to open a file from an application, lauching a file manager or doing something which requires some access to my filesystem. I've a Synology Drive mounted with a classic `mount -t cifs`. When the filesystem start hanging I need to either reboot my computer or kill the gvfsd-trash process. I've no clue on how to fix that. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1925680 Title: Accessing the filesystem hangs unless µI kill gvfsd-trash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1925680/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922548] Re: The admin backend is broken
The issue is fixed in upstream git https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/122/ ** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Changed in: gvfs (Ubuntu) Status: Confirmed => Fix Committed -- 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/1922548 Title: The admin backend is broken To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1922548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922548] Re: The admin backend is broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (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/bugs/1922548 Title: The admin backend is broken To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1922548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922548] Re: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid
** Changed in: nautilus (Ubuntu) Status: New => Invalid ** Package changed: policykit-1 (Ubuntu) => gvfs (Ubuntu) ** Summary changed: - Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set] + The admin backend is broken -- 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/1922548 Title: The admin backend is broken To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1922548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925464] Re: Cannot open /boot/efi
*** This bug is a duplicate of bug 1922548 *** https://bugs.launchpad.net/bugs/1922548 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922548, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1922548 The admin backend is broken -- 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/1925464 Title: Cannot open /boot/efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1925464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901391] Re: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement)
I'm on Ubuntu 21.04, upgraded to Gnome 40. My system should be fully up to date, but this problem is still there for me. Is this normal, or should the fix have reached my machine by now? I had the problem in 20.10 as well, though it worked on 20.04. Always in Wayland. When trying to run pipewire in the terminal I get the following error, which may or may not be related: ``` [E][02893.342993][module-protocol-native.c:578 lock_socket()] server 0x56383cd9dfe0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running) [E][02893.343190][conf.c:309 load_module()] config 0x56383cd834e0: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable [E][02893.343234][conf.c:383 create_object()] can't find factory spa-node-factory ``` -- 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/1901391 Title: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1901391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925271] Re: GIMP Crash
** Summary changed: - ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1Target: x86_64-linux-gnuConfigured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnuThread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) using babl version 0.1.72 (compiled against version 0.1.72) using GEGL version 0.4.18 (compiled against version 0.4.18) using GLib version 2.56.4 (compiled against version 2.56.4) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.40.14 (compiled against version 1.40.14) using Fontconfig version 2.12.6 (compiled against version 2.12.6) using Cairo version 1.15.10 (compiled against version 1.15.10) ``` > fatal error: Aborted Stack trace: ``` /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x327)[0x7f2e708b3fc7] gimp-2.10(+0xd7ab4)[0x5617580c3ab4] gimp-2.10(+0xd80b8)[0x5617580c40b8] gimp-2.10(+0xd87c7)[0x5617580c47c7] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f2e6d443980] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f2e6d07efb7] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f2e6d080921] /lib/x86_64-linux-gnu/libc.so.6(+0x3048a)[0x7f2e6d07048a] /lib/x86_64-linux-gnu/libc.so.6(+0x30502)[0x7f2e6d070502] /usr/lib/x86_64-linux-gnu/libX11.so.6(+0x3de3a)[0x7f2e6cb41e3a] /usr/lib/x86_64-linux-gnu/libX11.so.6(+0x3dede)[0x7f2e6cb41ede] /usr/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5d)[0x7f2e6cb421cd] /usr/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x5d)[0x7f2e6cb33ced] /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x58085)[0x7f2e71565085] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1f1)[0x7f2e6dc3e101] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c690)[0x7f2e6dc3e690] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xc2)[0x7f2e6dc3ea82] gimp-2.10(app_run+0x350)[0x5617580c3470] gimp-2.10(main+0x37c)[0x5617580c2d3c] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f2e6d061bf7] gimp-2.10(_start+0x2a)[0x5617580c2eda] ``` + GIMP Crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1925271 Title: GIMP Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1925271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925530] Re: Backport Metro Exodus Mesa fix into Hirsute
The fix will also (most likely) be included in Mesa 21.0.4 after it is released in a week or two. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1925530 Title: Backport Metro Exodus Mesa fix into Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1925530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925530] [NEW] Backport Metro Exodus Mesa fix into Hirsute
Public bug reported: Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to hang or crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. ** Affects: hundredpapercuts Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Tags added: hirsute ** Description changed: Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to - hang on crash after playing for some time. + hang or crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1925530 Title: Backport Metro Exodus Mesa fix into Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1925530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925530] [NEW] Backport Metro Exodus Mesa fix into Hirsute
You have been subscribed to a public bug by AsciiWolf (asciiwolf): Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to hang on crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- Backport Metro Exodus Mesa fix into Hirsute https://bugs.launchpad.net/bugs/1925530 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
** Description changed:
+ [ Impact ]
+
+ As per glib commit
+ https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
+ Gio.File.new_for_path("") returns a GDummyFile implementation, while
+ Gio._promisify relies on it being a LocalFile, so we don't promisify the
+ right methods.
+
+ [ Test case ]
+
+ gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
+print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
+
+ Should write on terminal:
+
+ [object Promise]
+ GJS works
+
+ In the bugged version would instead just:
+
+ (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
+ @:2:48
+
+ (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script threw
+ an exception
+
+
+ [ Regression potential ]
+
+ Gjs apps are slower in starting up, or not act properly when / is not a
+ local location.
+
+ ---
+
+
Problem tested in two different environments:
- - Ubuntu 21.04 Beta amd64
+ - Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload,
Impossible to read image from path '/run/user/1026/multiload-icons-
Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method
Gio.File.read_async: At least 3 arguments required, but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
--
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/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
** Summary changed: - indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 + Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) -- 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/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925518] [NEW] Evince is using 100% cpu
Public bug reported: Evince is using 100% cpu most likely related to https://bugs.launchpad.net/ubuntu/+source/evince/+bug/384062 removing pdf files from currently active "Files" window resolves issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 16:31:25 2021 InstallationDate: Installed on 2021-03-16 (36 days ago) InstallationMedia: Ubuntu 18.04.5 2020.11.30 LTS am "Custom Bionic Beaver" (20201130) KernLog: [685319.390960] SGI XFS with ACLs, security attributes, realtime, no debug enabled SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: Evince is using 100% cpu most likely related to https://bugs.launchpad.net/ubuntu/+source/evince/+bug/384062 + + removing pdf files from currently active "Files" window resolves issue + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 16:31:25 2021 InstallationDate: Installed on 2021-03-16 (36 days ago) InstallationMedia: Ubuntu 18.04.5 2020.11.30 LTS am "Custom Bionic Beaver" (20201130) KernLog: [685319.390960] SGI XFS with ACLs, security attributes, realtime, no debug enabled SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1925518 Title: Evince is using 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1925518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
This bug was fixed in the package nautilus - 1:3.38.2-1ubuntu2 --- nautilus (1:3.38.2-1ubuntu2) hirsute; urgency=medium * d/p/19_unity_open_location_xid: - Do not update opened locations on bus connection. Nautilus may connect to the bus when the application is already about shut down, however at that point its implementation is destroyed but Gio doesn't handle this gracefully as per GNOME/GLib!2056. To prevent this, we can safely reduce the delta of the distro-patch by avoiding updating the opened locations on bus acquired, as we already do it in all the cases a window actually changes its state. (LP: #1820859) -- Marco Trevisan (Treviño) Wed, 21 Apr 2021 07:03:29 +0200 ** Changed in: nautilus (Ubuntu Hirsute) 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/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
Hello errors.ubuntu.com, or anyone else affected, Accepted nautilus into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.38.2-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-hirsute -- 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/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925464] [NEW] Cannot open /boot/efi
Public bug reported: Get this error message when trying to open /boot/efi "gdbus error freedesktop policykit1 error failed unix process subject does not have uuid set" ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 12:24:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'355' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-04-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "error message" https://bugs.launchpad.net/bugs/1925464/+attachment/5490958/+files/Screenshot%20from%202021-04-22%2012-29-55.png -- 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/1925464 Title: Cannot open /boot/efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1925464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925409] Re: the screen just blink. somewhat look crash
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1925409 Title: the screen just blink. somewhat look crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1925409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
