Assigning to 'affects' against GSD, for lack of better understanding.
** Package changed: ubuntu => gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad
** Tags added: amdgpu multimonitor
--
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/1987209
Title:
gnome-shell (Wayland) crashes when screen locker activates (jj)
To manage noti
Summary from my IRC support session with francois-lafont:
gnome-shell (Wayland) reproducibly segfaults on this amd64 system
whenever the no-user-interaction timeout is reached and the screen
locker kicks in. Not reproducible on Xorg.
This is an amd64 Intel CPU, 2x AMD GPU system, recently upgrade
** Summary changed:
- Automatic lock screen doesn't lock my session but closes it because of a
gnome-shell crash
+ gnome-shell crashes with Wayland when screen locker activates (jj)
** Summary changed:
- gnome-shell crashes with Wayland when screen locker activates (jj)
+ gnome-shell (Wayland)
For gnome-control-center, this bug report was watching
https://bugzilla.gnome.org/show_bug.cgi?id=692666 so far. While still
relevant, the Gnome Project has stopped using this bug tracker and has
since shifted to their Gitlab instance for bug tracking.
A closely related upstream bug report, which
** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #196
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/196
** Also affects: libfprint via
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/196
Importance: Unknown
Status: Unknown
--
You r
There is no easy way to gracefully handle weak crypto. It has been known
for more than five years that 1024 bit (or rather <2048 bit) DH primes
need to be considered weak and should not be used - https://weakdh.org/
- GnuTLS > 3.2 does the right thing in having services which still have
not taken a
Watch existing bug on GNOME Gitlab. Previously, this was
https://bugzilla.gnome.org/show_bug.cgi?id=753678
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #332
https://gitlab.gnome.org/GNOME/gnome-shell/issues/332
** Bug watch added: bugzilla.gnome.org/ #753678
https://bugzill
It's now also filed at
https://gitlab.gnome.org/GNOME/nautilus/issues/1290 - thanks Sebastian.
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1290
https://gitlab.gnome.org/GNOME/nautilus/issues/1290
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/12
*** This bug is a duplicate of bug 1764417 ***
https://bugs.launchpad.net/bugs/1764417
Please note that I have unsubscribed off this bug report because I am no
longer experiencing it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
** Changed in: gnome-terminal
Importance: Medium => Unknown
** Changed in: gnome-terminal
Status: Confirmed => Unknown
** Changed in: gnome-terminal
Remote watch: GNOME Bug Tracker #780622 => bugzilla.gnome.org/ #780622
--
You received this bug notification because you are a member o
Point to currently open bug on GNOME Gitlab (which has further
references to related bug reports)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #681
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/681
** Changed in: gnome-control-center
Importance: Medium
This appears to have been partially fixed upstream at
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/53
However, the description is still ambiguous as reported at
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/681 (now tracked
here)
It would be nice to see this fixed in
At https://gitlab.gnome.org/GNOME/nautilus/issues/1244 it was determined
that this is a duplicate report for upstream bug
https://gitlab.gnome.org/GNOME/nautilus/issues/162
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #162
https://gitlab.gnome.org/GNOME/nautilus/issues/162
** Cha
Thanks, Seb. I have reported this upstream at
https://gitlab.gnome.org/GNOME/nautilus/issues/1244
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1244
https://gitlab.gnome.org/GNOME/nautilus/issues/1244
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues
I just reported it upstream at
https://gitlab.gnome.org/GNOME/nautilus/issues/1243
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1243
https://gitlab.gnome.org/GNOME/nautilus/issues/1243
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/1243
Import
Please refer to the duplicate bug 1845750 for a reproducer.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/1845749
Title:
/usr/bin/yelp:11:yelp_uri_get_document_uri:action_new_window
*** This bug is a duplicate of bug 1845749 ***
https://bugs.launchpad.net/bugs/1845749
Public bug reported:
Steps to reproduce:
1. Run "yelp :"
2. Yelp opens with an empty document / no document.
3. From the menu, select "New Window"
4. Yelp crashes with a segmentation fault.
This happens o
Public bug reported:
According to
nautilus --help
there is an option
-c, --checkPerform a quick set of self-check tests.
Running 'nautilus --check' on the 19.10 beta or on 18.04.3 prints:
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operation
Confirming the error message enables the user to continue. If the user
then chooses to create a new folder, Nautilus crashes with:
https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus%3A11%3Acheck_valid_child_name%3Anew_folder_name_changed%3Ag_closure_invoke%3Asignal_emit_unlocked_R%3Ag_signal_e
Please ignore the previous comment, this wa snot meant to be posted
here.
--
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/1845703
Title:
Deleting starred files leaves behind starre
Confirming the error message enables the user to continue. If the user
then chooses to create a new folder, Nautilus crashes with:
https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus%3A11%3Acheck_valid_child_name%3Anew_folder_name_changed%3Ag_closure_invoke%3Asignal_emit_unlocked_R%3Ag_signal_e
Public bug reported:
While in "Starred" right-clicking on a FSO¹ and selecting "Copy to.." brings up
a new window to choose the destination, but this window shows an error message:
The folder contents could not be displayed
The specified location is not supported
Steps to reproduce:
1. Star
Public bug reported:
On the 19.10 beta, deleting a starred file leaves behind a file named ""
in Starred.
It does not matter whether the file is first moved to trash, then trash
expunged, or whether the file is immediately deleted using Shift-Delete.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
This apparently made it into 19.10 beta1, my UEFI booted 19.04 beta1 VM
(running on VirtualBox 6.0.12, Ubuntu 18.04.3 / Linux 5.3 host) reported
a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://b
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1764417
Title:
Unrecoverable failure in required component
org.gnome.SettingsDaemon.Color.deskto
** Bug watch added: gitlab.gnome.org/GNOME/file-roller/issues #31
https://gitlab.gnome.org/GNOME/file-roller/issues/31
** Changed in: file-roller
Importance: Medium => Unknown
** Changed in: file-roller
Status: Confirmed => Unknown
** Changed in: file-roller
Remote watch: GNOME Bug
*** This bug is a duplicate of bug 1725017 ***
https://bugs.launchpad.net/bugs/1725017
** This bug has been marked a duplicate of bug 1725017
file-roller crashed with SIGSEGV in g_action_map_lookup_action()
--
You received this bug notification because you are a member of Ubuntu
Desktop B
Possible Workaround (untested):
This only applies if you have not rebooted / closed the LUKS volume. Follow
steps 7 to 9 of https://www.thegeekstuff.com/2016/03/cryptsetup-lukskey/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome
When I returned to my computer (AMD RX580 graphics, amdgpu) after a
while (the screen had entered power saving mode), the gnome-shell
process (on XWayland) failed.
Unfortunately this crash was not automatically reported by whoopsie /
apport and required manual re-submission (bug 1792643). If this
Possible duplicates: #1813441 #1822254
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#22
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExt
Possible duplicates: #1822254 #858913
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1813441
Title:
Can no longer drag and drop files from desktop into
Possible duplicates: #1813441 #858913
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#22
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
Impor
I tested version 19.01.3-1~ubuntu19.04.1 (from -proposed) on a fully
updated 19.04, and can no longer reproduce this issue: The terminal
window opens - as expected - in directory ~/Desktop/aaa'bbb/. Injecting
commands as discussed in comment 2 appears to be no longer possible.
** Tags removed: ver
The way I understand Mustafa's report this is about the general lack of
a caps lock state indicator on (so primarily post-login, in gnome-
shell). Bug #1734887 rather discusses the lack of an indicator pre-login
(gdm), so is a different issue.
** This bug is no longer a duplicate of bug 1734887
It is an issue for me on 18.04.2, see my recent duplicate reports.
What happened to the upstream bug report?
--
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/1716940
Title:
gvfsd-trash
I think the other bug report you meant to point to is actually bug
#1825227.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1825224
Title:
gnome-calendar cannot add credenti
~seb128: Since this also affects 18.04.2 via #1827295, is an SRU
possible / needed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1795372
Title:
gnome-control-center
Thanks Sebastien, I've filed it at Gnome's Gitlab and added the bug
tracker.
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #395
https://gitlab.gnome.org/GNOME/gvfs/issues/395
** Also affects: gvfs via
https://gitlab.gnome.org/GNOME/gvfs/issues/395
Importance: Unknown
Stat
*** This bug is a duplicate of bug 1825396 ***
https://bugs.launchpad.net/bugs/1825396
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#105
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/105
** Also affects: gnome-shell-extension-deskto
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#111
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/111
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/111
Im
As discussed on IRC, command injection is actually possible here.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-deskto
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1825396
Title:
"Open in Terminal" returns "Tex
Public bug reported:
Attempting to open a Desktop folder named "aaa'bbb" (without double
quotes) using the "Open in Terminal" option from the context menu
produces a notification message stating:
Execution of "x-terminal-emulator --working-directory=/home/...
Text ended before matching quote was
Public bug reported:
The desktop folder context menu option "Open in Terminal" opens a new
terminal, but the working directory is the home directory when it should
be the folder context.
To reproduce:
1. Create a folder "test" on the Desktop
2. Right-click on the "test" folder icon on the Deskto
Reported upstream on the Gnome projects' new 'bug tracker' (Gitlab) - for which
no bug watch exists in Launchpad (to date):
https://gitlab.gnome.org/GNOME/file-roller/issues/31
** Bug watch added: GNOME Bug Tracker #746829
https://bugzilla.gnome.org/show_bug.cgi?id=746829
** Also affects: fil
Off-topic but possibly necessary context:
Ubuntu (major) releases are time based. The time of the release is indicated in
the release version. As such, Ubuntu 18.10 will be released in year (20)18,
month 10.
More precise release dates are provided at https://wiki.ubuntu.com/Releases
Point rele
** Changed in: gvfs (Ubuntu)
Status: Incomplete => Confirmed
--
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/1752091
Title:
gvfsd-metadata[1703]: g_udev_device_has_property: ass
*** This bug is a duplicate of bug 1764417 ***
https://bugs.launchpad.net/bugs/1764417
Public bug reported:
This is a duplicate of #1764417 (and probably also of #1663839), I'd
like to provide extra logs and not clutter the existing report.
Roughly two minutes after logging in, I was confron
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356
Just a note (mostly to self):
The OP and I discussed this issue today on #ubuntu between 5:30 am and 8:15 am
(UTC).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This is not fixed. What we have is a reliable workaround to a bug which
apparently affects all Ubuntu 16.04 LTS users with the dbus-user-session
package installed.
Flatpak packages provided by the PPA at
https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak (and possibly
others) indirectly de
Oneiric is also affected. A SRU would be nice to have.
While it's not clear to me how to reliably reproduce this bug I'll be happy to
test a Oneiric fix if it becomes available before Precise does (and possibly
after).
--
You received this bug notification because you are a member of Ubuntu
De
53 matches
Mail list logo
