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.
This still happens, ex
Apr 19 14:34:35 lego.house /usr/libexec/gdm-x-session[3605]: discarding
unsupported packet "kdeconnect.mpris" for "Nexus 7"
$ journalctl | wc -l
156428
$ journalctl | grep 'discarding unsupported packet' |wc -l
4461
tchiverton@lego:~$ journalctl | grep gdm-x-session| wc
Also seen on 22.04 LTS running gnome-shell 42.5-0ubuntu1. Seen for the
first time today; as noted above, restarting the shell fixes the issue,
at least temporarily.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
** Changed in: gnome-shell (Ubuntu)
Status: Fix Released => Confirmed
--
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/1933027
Title:
Gdm3 with smartcard asks for
After using GNOME 43 Xorg with Debian Bookworm 5.19, I rebooted into Ubuntu
22.04 Xorg 5.15, did some checks and found out that on my Ryzen laptop this was
caused by the amd_pstate scaling driver which lowers the minimum CPU frequency
down to 400 Mhz instead of the 1400 Mhz default on the
** 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
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
** 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)
Public bug reported:
I'm encountering three issues when using a smartcard to login into gdm3.
The root of the issues is gdm-smartcard-sssd-exclusive PAM configuration
for authentication:
1. The gdm-smartcard denies access to legitimate users as no success
control value is configured.
2. Because
Is there any update about it?
--
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/1772791
Title:
Lock/login screen displays password in clear text occasionally
To manage
Public bug reported:
```
The "Gimp" crash happened when try to apply the oilify filter to an image
layer. I had tried to apply it to the top layer. It was not turned on. So I
turned the layer on and then used from the Gimp menu "re-apply" oilify filter.
Since it was never applied in the first
Is this feature ever going to come back? I miss it. Affecting me
currently in 20.04.
--
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/1356433
Title:
detached tabs can not be
I confirm the bug is still present (and very annoying, making me lose a
lot of time) on Ubuntu 21.10.
--
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.
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
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+attachment/5459123/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This is a desktop computer so I don't suspend and resume. However I do
lock the screen regularly, but I could not reproduce the problem by
locking and unlocking the screen.
The problem seems to occur after a certain amount of uptime, though I
have not measured how much uptime.
Requested output
Additional screenshot attached
** Attachment added: "20210202_001423.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+attachment/5458976/+files/20210202_001423.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
1. I don't think something is covering the clock, because it's not just
the clock that has problems. The text on other controls on menu panel is
also affected, see attached photos.
2. Attached
3. bug 1876632 seems similar, however the text is not corrupted, it has
simply disappeared.
**
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
gnome-shell:
Installed: 3.36.4-1ubuntu1~20.04.2
Candidate: 3.36.4-1ubuntu1~20.04.2
Version table:
*** 3.36.4-1ubuntu1~20.04.2 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
I've done the full-upgrade and disabled the non-Ubuntu extensions and
then re-triggered the crash with `echo mem > /sys/power/state`. This
now causes a hard hang of the whole system - its no longer accessible
over the network when it tries to wake up. There is no new log in
/var/crash and the
right.
Regards,
Tom
--
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/1903292
Title:
GNOME Wayland session hangs after suspend
To manage notifications about this bug go to:
https
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5432575/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5432571/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5432574/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5432573/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5432572/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected third-party-packages
** Description changed:
I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega
Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2.
When I trigger a suspend with `echo mem >
** 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
Public bug reported:
I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega
Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2.
When I trigger a suspend with `echo mem > /sys/power/state` the system
appears to go into mem suspend correctly. Hitting a key should
Sorry to hear of the problem. I followed the procedure mentioned in my
initial post to create my launchers. I "solved" the problem by
recreating my whole user profile. But the problem came back in limited
forms. But not as bad. I am now largely free of issues and I put that
down to software
Hi Seb, I'm really sorry but that user is gone. Unless another user
develops the same issue, I feel it may be appropriate to put this down
as an aberration in Ubuntu but close the bug entry. (I do not know how
to do that).
Thanks again for your help. It is much appreciated.
Tom
--
You
Thank you Seb
Once I realised that mine was the only user account on my home desktop
PC with this problem, I tried deleting all hidden config files that
included the words "Nautilus" or "Gnome". This did not help so I
created another sudoer and removed my home folder. I then recreated my
home
The behaviour of Nautilus desktop remains baffling. But I have resolved
the problem on my PC by recreating my user profile and home user folder.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Sorry, I'm afraid I'n not very familiar with this.
The steps I followed where in the link I gave:
https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-
ubuntu-20-04-focal-fossa-linux
There is now a YouTube showing the problem:
https://youtu.be/irZME1Tt-EA
Is there anything else
Public bug reported:
Using the procedure here =
https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux
AND OTHERWISE
I have successfully created launchable desktop app shortcuts. But they
stop working: (1) no launch; (2) no right click context to
My Asus ZenBook UX370UAF worked straight out of the box with Ubuntu
18.04. Since upgrading to Focal Fossa 20.04 it does not show.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
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
Seeing the issue still with Version: 3.4.2-4ubuntu1. Radio streams just stop
with the "internal data stream error". Other players such (VLC, TuneIn app)
play the same stations/URLs just fine.
It takes at most a few minutes for the error to occur so it renders Rhythmbox
completely useless as
Seeing the issue still with Version: 3.4.2-4ubuntu1. Radio streams just stop
with the "internal data stream error". Other players such (TuneIn app) play the
same stations/URLs just fine.
It takes at most a few minutes for the error to occur so it renders Rhythmbox
completely useless as online
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
I'm experiencing the same bug since 2 weeks. Using Ubuntu 19.10,
Libreoffice Calc 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1.
Please help!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Ok, maybe some progress. It appears I can search among a maximal number
of hits. So that depends per folder. And as soon as Nautilus start to
crash, I have to start all over by rebooting, as even small searches
then crash. (Logging out/in does not make a difference.)
For what it is worth, I:
1 -
*3 Sorry, " sudo cat /proc/sys/fs/inotify/max_user_watches " now gives:
524288
--
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/1852053
Title:
Nautilus Crashes when opening
Well, it definitely is not gsconnect, as I disabled a week ago and the
crashing is back in full force.
I am trying to find some kind of pattern to make it predictable. But
it's mind-boggling so far. I wish few others had same issue ;)
--
You received this bug notification because you are a
The problem is back. But not frequent enough yet to let me catch it
properly, I did get after running 'nautilius -q":
Traceback (most recent call last):
File
"/home/tom/.local/share/nautilus-python/extensions/nautilus-gsconnect.py", line
49, in
localedir=LOCALE_DIR)
To my surprise, the bug stopped happening few days ago so I cant
replicate. Search works again as intended.
It might have been an update but I am not even sure which one could have
fixed the issue;
So, until further notice, for me it seems solved...
--
You received this bug notification
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
*** 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
I did that:
- In Nautilus I press Ctrl-F and a character and then N freezes and gdb reports
segmetation fault. -(gdb) backtrace
[...]
(org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.526: Duplicate child name
in GtkStack: icons
(org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.579:
Is it possible the crash report auto-uploaded ( cb12411a-045e-11ea-
afb5-fa163e983629 ) ?
--
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/1852053
Title:
Nautilus Crashes when
Randomly tried this :
apport-retrace --gdb _usr_bin_nautilus.1000.crash
But that gave me: "ERROR: report file does not contain one of the
required fields: Package"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
Sorry I spend about 30 minutes trying to understand how to open a crash
report program. I followed your link and Googled, but these
"explanations" are so unclear that I cant get any further. I use Ubuntu
since version 11 I think and it's remarkable how complex that crash
reporting remained...
In
Public bug reported:
Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
changed as far as I know. But now:
- click in Dock on the file stack icon to open Nautilus
- stay in Home or browse to any folder
- click Ctrl-F to open search field at the top of window
- enter any
** 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
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:
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
Still in 19.10
--
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/1767995
Title:
Horizontal scroll doesn't honor Natural Scrolling preference
To manage notifications
** Changed in: evince (Ubuntu)
Status: Incomplete => Confirmed
--
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/1847633
Title:
19.10 wifi networks menu doesn't respect natural
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
**
re: evince -->
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847647
Screenshot attached. The Select Network screen, just like I originally
reported.
** Attachment added: "Screenshot from 2019-10-10 14-13-03.png"
Screenshot -- I promise I just clicked submit IMMEDIATELY after this
screenshot, no funny business like retyping "evince" in the unselected
radio button text field and selecting it...
** Attachment added: "Screenshot from 2019-10-10 14-10-29.png"
Public bug reported:
1. You can't easily go to report a bug on launchpad.net.
Go to https://bugs.launchpad.net/ubuntu/
Click Report a Bug
Expected Behavior: report a bug
Actual behavior: Taken to stupid words
Fix: Put a link on ALL major launchpad.net pages where you can click on "Report
a Bug"
Public bug reported:
Steps to reproduce
Be in 19.10
Set natural scrolling to on/true/yes for mouse/touchpad
Go to select network
on the list of wifi SSIDs, scroll down. It won't move. Scroll up. It scrolls
down.
I've only tested this with touchpad, but I'm guessing it affects mice
too? Can
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
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
It's inconsistent, so very hard to reproduce, but I've experienced it
intermittently at least up to 19.04. Maybe close it if it's not
reproducible, I'm not sure what is best.
On Fri, Oct 4, 2019, 07:01 Paul White <1721...@bugs.launchpad.net>
wrote:
> We are sorry that we do not always have the
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:
*** 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
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
Confirming the error message enables the user to continue. If the user
then chooses to create a new folder, Nautilus crashes with:
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
Confirming the error message enables the user to continue. If the user
then chooses to create a new folder, Nautilus crashes with:
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.
** 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
** 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
*** 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
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
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
I have this same problem on 18.04. It's very noticeable that when my
network has no DNS working, screen unlock takes a long time - as much as
a minute or two.
I notice this because I often manually configure my network to do DNS
lookups over an SSH tunnel. If I just close the lid of my laptop
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
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
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:
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
I have already opened an issue there. Thank you!
--
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/1828123
Title:
File names are percent-encoded when connect to webdav server
To
I'm using nautilus 3.32 on Ubuntu 19.04. "gio list dav://..." works
perfectly fine, so the issue is specific to nautilus. Please see the
following screenshot.
** Attachment added: "2019-05-08 04-45-55 的屏幕截图.png"
Public bug reported:
When I connected to a Webdav server set up by nginx using the default
file manager, some non-English characters in file and folder names are
displayed as percent-encoded(url-encoded). For example,
"%E4%B8%8D%E5%AE%89%E4%B8%8E%E6%AC%B2%E6%9C%9B" is displayed instead of
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:
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
~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
*** 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:
** 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
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
** 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
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
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
1 - 100 of 1445 matches
Mail list logo
