[Bug 2039722] Re: "Large Text" accessibility option cannot be turned off. Text is too large
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.net/bugs/2039722 Title: "Large Text" accessibility option cannot be turned off. Text is too large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2039722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 15027] Re: gdm: Suppresses X logging with "Too much output"
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 -l 7426 And other unrelated and pointless junk, over and over again. All day. Every day. -- 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/15027 Title: gdm: Suppresses X logging with "Too much output" To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/15027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956248] Re: I get two characters in Activities when I press one key for the first key I press...
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 Ubuntu. https://bugs.launchpad.net/bugs/1956248 Title: I get two characters in Activities when I press one key for the first key I press... To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1956248/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
** 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 login/smartcard pin even if there is no smartcard authentication enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions
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 acpi_cpufreq which Debian uses. Debian (acpi_cpufreq) behaved perfectly on both Xorg and Wayland, so I enabled the amd_pstate scaling driver and this issue came up the exact same way as in Ubuntu: it seems that scaling down a much lower cpu frequency and then back up all the times can cause some performance penalties and glitches. To me it's fine because in the Xorg session I disabled the animations and the battery life is noticeably better with the amd_pstate scaling driver, but as usual ymmv! -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987209] Re: gnome-shell (Wayland) crashes when screen locker activates (jj)
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987209] Re: gnome-shell (Wayland) crashes when screen locker activates (jj)
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 upgraded to JJ. Related Oopses from this system (SegvAnalysis failed for all, no debug): https://errors.ubuntu.com/oops/a812c258-216f-11ed-9782-fa163e993415 https://errors.ubuntu.com/oops/a6ea9d2a-216f-11ed-b145-fa163ef35206 https://errors.ubuntu.com/oops/c94458b8-1def-11ed-9760-fa163e993415 https://errors.ubuntu.com/oops/5d6f040c-1dee-11ed-975f-fa163e993415 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987209] Re: gnome-shell crashes with Wayland when screen locker activates (jj)
** 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) crashes when screen locker activates (jj) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1986750] [NEW] gdm-smartcard pam config denies legitimate users, prompts for username
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 pam_succeed_if is first in the authentication stack, it will invoke the pam_get_user when the user is NULL. As gdm3 doesn't supply a user when invoking pam_start, pam_get_user invokes a conversation, causing gdm3 to collect a username. 3. If a Username of '' (empty string) is inputed, pam_succeed_if will succeed, assuming a success=ok control value. If configured with allow- missing-name, pam_sss will use the certificate on a smartcard to identify the user. If so configured, this may map to root, which defeats the pam_succeed_if.so check. I'm attaching a pam config that seems to addresses these issues by reordering the pam stack for authentication. By performing pam_sss before pam_succeed_if, pam_sss uses the certificate when the supplied user is NULL or the empty string. GDM3 only prompts for the smartcard PIN. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 16 20:39:44 2022 InstallationDate: Installed on 2022-08-12 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "gdm-smartcard pam config" https://bugs.launchpad.net/bugs/1986750/+attachment/5609220/+files/gdm3.gdm-smartcard-sssd-exclusive.pam -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1986750 Title: gdm-smartcard pam config denies legitimate users, prompts for username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1986750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772791] Re: Lock/login screen displays password in clear text occasionally
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 notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1772791/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950917] [NEW] Reporting a gimp crash
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 place, I had guessed that that was where the error came in. However, I restarted Gimp selected recover last session and tried to apply the oilify filter (this time with the layer being selected. I got the same crash. Went back in and change the image precision to 32 bit integer from 32 bit floating integer and there was no crash; and the filter applied. I think Gimp needs grey out filters when they are not designed to work under certain conditions. Note: The Gimp error dialog led me here via send report button, so I assume this is the right place to report? GNU Image Manipulation Program version 2.10.24 git-describe: GIMP_2_10_24 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 10.3.0-6ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --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 --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --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=/build/gcc-10-IAajkb/gcc-10-10.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-IAajkb/gcc-10-10.3.0/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.3.0 (Ubuntu 10.3.0-6ubuntu1) # Libraries # using babl version 0.1.88 (compiled against version 0.1.88) using GEGL version 0.4.32 (compiled against version 0.4.30) using GLib version 2.68.4 (compiled against version 2.68.3) using GdkPixbuf version 2.42.6 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.48.10 (compiled against version 1.48.7) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 263490 - Thread 263490 # [New LWP 263491] [New LWP 263492] [New LWP 263493] [New LWP 263494] [New LWP 263495] [New LWP 263496] [New LWP 263537] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=256, buf=0x7ffccb54edd0, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target IdFrame * 1Thread 0x7fe6e94a6300 (LWP 263490) "gimp"__GI___libc_read (nbytes=256, buf=0x7ffccb54edd0, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fe6e8d22640 (LWP 263491) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fe6e8521640 (LWP 263492) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fe6e7d20640 (LWP 263493) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fe6e69b1640 (LWP 263494) "gmain" 0x7fe6ea157cdf in __GI___poll (fds=0x55dcb3095800, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 6Thread 0x7fe6e61b0640 (LWP 263495) "gdbus" 0x7fe6ea157cdf in __GI___poll (fds=0x55dcb52d5830, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 7Thread 0x7fe6cd005640 (LWP 263496) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fe6c4bb1640 (LWP 263537) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 8 (Thread 0x7fe6c4bb1640 (LWP 263537) "swap writer"): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 No locals. #1 0x7fe6ea3f6e03 in g_cond_wait () from
[Bug 1356433] Re: detached tabs can not be reattached
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 reattached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1356433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
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. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
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 should have higher relevance for Ubuntu (after shifting to XWayland), is https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1016, so I've updated the remote watch for gnome-control-center. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1016 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1016 ** Changed in: gnome-control-center Importance: Medium => Unknown ** Changed in: gnome-control-center Remote watch: bugzilla.gnome.org/ #692666 => gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1016 -- 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/124440 Title: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914164] Re: [nvidia] Shell labels randomly disappear from the menu panel (top bar)
** 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. https://bugs.launchpad.net/bugs/1914164 Title: [nvidia] Shell labels randomly disappear from the menu panel (top bar) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914164] Re: [nvidia] Shell labels randomly disappear from the menu panel (top bar)
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 attached. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+attachment/5459122/+files/lspci.txt -- 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/1914164 Title: [nvidia] Shell labels randomly disappear from the menu panel (top bar) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914164] Re: Time and other labels randomly disappear from the menu panel (top bar)
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 subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914164 Title: Time and other labels randomly disappear from the menu panel (top bar) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914164] Re: Time and other labels randomly disappear from the menu panel (top bar)
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. ** Attachment added: "20210202_001051.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+attachment/5458975/+files/20210202_001051.jpg -- 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/1914164 Title: Time and other labels randomly disappear from the menu panel (top bar) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914164] [NEW] Time and other labels randomly disappear from the menu panel (top bar)
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 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Feb 1 22:09:05 tomsfastbox systemd[1]: Finished Clean php session files. Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Qt: Failed to create XKB context! Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Feb 1 22:09:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:10:32 tomsfastbox systemd-resolved[918]: message repeated 13 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:11:19 tomsfastbox gnome-shell[3626]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Feb 1 22:11:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:12:32 tomsfastbox systemd-resolved[918]: message repeated 14 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:12:49 tomsfastbox gnome-shell[3626]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x507 Feb 1 22:13:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. I'm also using a StreamDeck USB device, if that's useful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 22:16:07 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-18 (290 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-10 (206 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu
[Bug 1903292] Re: GNOME Wayland session hangs after suspend
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 last thing in kern.log is it going to sleep. This doesn't seem promising. The kernel is a custom-built 5.9.0 built from Linus' repository - I'm not expecting a lot of support with that. -- 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://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] Re: GNOME Wayland session hangs after suspend
Hi Daniel, Thanks for the follow-up. I've done the `apport-collect`, see above. I've also uploaded a potentially-related crash file from Xwayland, see https://errors.ubuntu.com/oops/39763900-226c-11eb-b3ef-fa163e102db1. I'm not absolutely certain this is related but the timestamp on it is about 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://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] monitors.xml.txt
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. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] GsettingsChanges.txt
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. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] ShellJournal.txt
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. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] ProcEnviron.txt
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. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] Re: GNOME Wayland session hangs after suspend
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 > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. - The system is still up as I can SSH into it. Killing the gdm-wayland- - session process then brings me back to the GDM login screen and I can - start a new session. + The system is still up as I can SSH into it. Killing the gdm-wayland-session process then brings me back to the GDM login screen and I can start a new session. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.10 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-10-17 (388 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 + Tags: wayland-session third-party-packages focal + Uname: Linux 5.9.0 x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-28 (194 days ago) + UserGroups: adm cdrom dip disk docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5432569/+files/Dependencies.txt -- 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://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879247] Re: [27C6:538D] goodix fingerprint is not supported.
** 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 received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1879247 Title: [27C6:538D] goodix fingerprint is not supported. To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1879247/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903292] [NEW] GNOME Wayland session hangs after suspend
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 bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland- session process then brings me back to the GDM login screen and I can start a new session. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1903292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
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 updates. If yours is a new build, you might try running all the updates. See also: https://askubuntu.com/questions/1261625/how-to-make-desktop-icons- display-on-startup-of-ubuntu-20-04-focal-fossa/1261626#1261626 which may help. -- 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/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1878392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
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 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/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1878392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
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 folder using cp /etc/skel. As explained in my earlier post, this action has removed the problem. I now feel that this issue is unlikely to be replicable by others. However in case it useful I followed your suggestion and put "journalctl -b 0" into a terminal and below is the result. I have only copies part of the output. I'm afraid I do not understand any of this myself. -- Logs begin at Wed 2020-04-29 19:21:25 BST, end at Mon 2020-05-18 16:42:40 BS> May 17 13:04:20 susan kernel: microcode: microcode updated early to revision 0x> May 17 13:04:20 susan kernel: Linux version 5.4.0-29-generic (buildd@lgw01-amd6> May 17 13:04:20 susan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-g> May 17 13:04:20 susan kernel: KERNEL supported cpus: May 17 13:04:20 susan kernel: Intel GenuineIntel May 17 13:04:20 susan kernel: AMD AuthenticAMD May 17 13:04:20 susan kernel: Hygon HygonGenuine May 17 13:04:20 susan kernel: Centaur CentaurHauls May 17 13:04:20 susan kernel: zhaoxin Shanghai May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 flo> May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE reg> May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX reg> May 17 13:04:20 susan kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]:> May 17 13:04:20 susan kernel: x86/fpu: Enabled xstate features 0x7, context siz> May 17 13:04:20 susan kernel: BIOS-provided physical RAM map: May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x-0x0005> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00058000-0x0005> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00059000-0x0009> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0009e000-0x0009> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0010-0x8b85> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b852000-0x8b85> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b859000-0x8c30> lines 1-23...skipping... -- Logs begin at Wed 2020-04-29 19:21:25 BST, end at Mon 2020-05-18 16:42:40 BST. -- May 17 13:04:20 susan kernel: microcode: microcode updated early to revision 0x27, date = 2019-02-26 May 17 13:04:20 susan kernel: Linux version 5.4.0-29-generic (buildd@lgw01-amd64-035) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 (Ubuntu 5.4.0-29.33-generic 5.4.30) May 17 13:04:20 susan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=c977975b-e6da-444a-b063-5200452dc91f ro quiet splash vt.handoff=7 May 17 13:04:20 susan kernel: KERNEL supported cpus: May 17 13:04:20 susan kernel: Intel GenuineIntel May 17 13:04:20 susan kernel: AMD AuthenticAMD May 17 13:04:20 susan kernel: Hygon HygonGenuine May 17 13:04:20 susan kernel: Centaur CentaurHauls May 17 13:04:20 susan kernel: zhaoxin Shanghai May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' May 17 13:04:20 susan kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 May 17 13:04:20 susan kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. May 17 13:04:20 susan kernel: BIOS-provided physical RAM map: May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x-0x00057fff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00058000-0x00058fff] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00059000-0x0009dfff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0009e000-0x0009] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0010-0x8b851fff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b852000-0x8b858fff] ACPI NVS May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b859000-0x8c302fff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8c303000-0x8c7fafff] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8c7fb000-0xaa02bfff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0xaa02c000-0xaa433fff] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0xaa434000-0xaa49bfff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0xaa49c000-0xaa5defff] ACPI NVS May 17 13:04:20 susan kernel: BIOS-e820: [mem
[Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
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. https://bugs.launchpad.net/bugs/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1878392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
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 I can do/should do to better explain how to replicate? -- 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/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1878392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878392] [NEW] Ubuntu 20.04 Focal Fossa desktop launchers not working
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 make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1878392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
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. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long
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 action to use contemporary (non weak) crypto fail by default, so that users will become aware of the fact they are (were) connecting insecurely, and these services can be more easily identified and fixed. In some cases, using clients (and software versions of client) which support higher TLS protocol versions can work around this problem (if remote servers support strong ciphers on higher TLS protocol versions; example: https://www.ssllabs.com/ssltest/analyze.html?d=mail.nhs.net=on ). It *may* be possible to continue to allow for insecure connections by setting the GnuTLS priority string to include LEGACY as per https://gnutls.org/manual/html_node/Priority-Strings.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767505] Re: Rhythmbox Radio - Internal Data Stream Error
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 online radio player. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1767505 Title: Rhythmbox Radio - Internal Data Stream Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767505] Re: Rhythmbox Radio - Internal Data Stream Error
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 radio player. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1767505 Title: Rhythmbox Radio - Internal Data Stream Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
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://bugzilla.gnome.org/show_bug.cgi?id=753678 ** Changed in: gnome-shell Importance: Medium => Unknown ** Changed in: gnome-shell Status: In Progress => Unknown ** Changed in: gnome-shell Remote watch: GNOME Bug Tracker #753678 => gitlab.gnome.org/GNOME/gnome-shell/issues #332 -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
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. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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 - have huge number of files, mostly from nodejs packages. 2 - am also running syncthing 3 - use " echo 10 | sudo tee /proc/sys/fs/inotify/max_user_watches " to keep hot reloading for Vue coding working -- 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 search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
*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 search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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 member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1852053 Title: Nautilus Crashes when opening search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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) File "/usr/lib/python2.7/gettext.py", line 560, in translation raise IOError(ENOENT, 'No translation file found for domain', domain) IOError: [Errno 2] No translation file found for domain: 'org.gnome.Shell.Extensions.GSConnect' Initializing nautilus-font-manager extension I see "GSConnect" there and I do have this Gnome extension. I will delete it when I can reproduce the error better. -- 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 search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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 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 search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845732] Re: nautilus --check stuck after nautilus_self_check_directory
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/1290 Importance: Unknown Status: Unknown -- 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/1845732 Title: nautilus --check stuck after nautilus_self_check_directory To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791069] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
*** 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 to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1791069 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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: Duplicate child name in GtkStack: icons (org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.790: Duplicate child name in GtkStack: icons (org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.843: Duplicate child name in GtkStack: icons [New Thread 0x7fff9b7fe700 (LWP 12372)] [New Thread 0x7fff93fff700 (LWP 12373)] [Thread 0x7fff93fff700 (LWP 12373) exited] [Thread 0x7fff9b7fe700 (LWP 12372) exited] [New Thread 0x7fff9b7fe700 (LWP 12374)] [New Thread 0x7fff93fff700 (LWP 12375)] [Thread 0x7fff9b7fe700 (LWP 12374) exited] Thread 1 "nautilus" received signal SIGSEGV, Segmentation fault. 0x7728c610 in g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (gdb) backtrace #0 0x7728c610 in g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #1 0x7726ca99 in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #2 0x555b170b in ?? () #3 0x7726fd86 in g_object_set_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x77270684 in g_object_set () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x555b5c16 in ?? () #6 0x555b2fee in ?? () #7 0x77ed1248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x77ed071e in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x77ed0ad0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x77ed0b73 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7738fb05 in g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x555a3d0b in main () -- 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 search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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 opening search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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 Ubuntu. https://bugs.launchpad.net/bugs/1852053 Title: Nautilus Crashes when opening search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
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 meantime problem persists, also after cold reboot. There is no message popping up as in the past, to report the bug. Just window disappears.. -- 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 search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852053] [NEW] Nautilus Crashes when opening search field and entering first character
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 character as first character of search pattern - Nautilus immediately crashes and window disappears immediately. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: crash nauilus search -- 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 search field and entering first character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** 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 of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751954] Re: Power > Wifi should offer powersaving mode for Wi-Fi
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 => Unknown ** Changed in: gnome-control-center Status: Confirmed => Unknown ** Changed in: gnome-control-center Remote watch: GNOME Bug Tracker #765279 => gitlab.gnome.org/GNOME/gnome-control-center/issues #681 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #53 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/53 -- 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/1751954 Title: Power > Wifi should offer powersaving mode for Wi-Fi To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751954] Re: Power > Wifi should offer powersaving mode for Wi-Fi
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 bionic, too, if GNOME can come up with a better solution. -- 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/1751954 Title: Power > Wifi should offer powersaving mode for Wi-Fi To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767995] Re: Horizontal scroll doesn't honor Natural Scrolling preference
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767995/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847633] Re: 19.10 wifi networks menu doesn't respect natural scrolling settings
** 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 scrolling settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847633/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845703] Re: Deleting starred files leaves behind starred file named ""
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 ** Changed in: nautilus Status: New => Unknown ** Changed in: nautilus Remote watch: gitlab.gnome.org/GNOME/nautilus/issues #1244 => gitlab.gnome.org/GNOME/nautilus/issues #162 -- 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 starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847633] Re: 19.10 wifi networks menu doesn't respect natural scrolling settings
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" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847633/+attachment/5296287/+files/Screenshot%20from%202019-10-10%2014-13-03.png -- 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 scrolling settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847633/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847647] Re: Launchpad report bug is broken in so many ways
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" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847647/+attachment/5296286/+files/Screenshot%20from%202019-10-10%2014-10-29.png -- 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/1847647 Title: Launchpad report bug is broken in so many ways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847647] [NEW] Launchpad report bug is broken in so many ways
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" and actually @#$(*& report a @#$( bug. Change all link text to https://help.ubuntu.com/community/ReportingBugs to "How to report bugs" or "Bug reporting FAQ", not "Report a bug". 2. You can't report a bug in "I don't know" package. This bug is proof. Got to report a bug. Click "I don't know" radio for "In what package did you find this bug?" Optional: delete the package in unselected radio button below "I don't know" Bug will still be filed under a package; in this case, evince. It should be filed under NO PACKAGE or DONTKNOW or some placeholder package for all the unknown-package bugs. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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/1847647 Title: Launchpad report bug is broken in so many ways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847633] [NEW] 19.10 wifi networks menu doesn't respect natural scrolling settings
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 anyone verify? ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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 scrolling settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847633/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845703] Re: Deleting starred files leaves behind starred file named ""
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/1244 Importance: Unknown Status: Unknown -- 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 starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845709] Re: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"
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 Importance: Unknown Status: Unknown -- 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/1845709 Title: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1721424] Re: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.
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 capacity to review all > reported bugs in a timely manner. > > Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. > I'm not sure if I'm moving this to the right package but > > Is this still an issue? Unable to reproduce here with Ubuntu 18.04. > > Paul White > [Ubuntu Bug Squad] > > > ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) > > ** Tags added: artful > > ** Changed in: gnome-settings-daemon (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1721424 > > Title: > 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it > is. > > Status in gnome-settings-daemon package in Ubuntu: > Incomplete > > Bug description: > 4.13.0-12-generic > 17.10 > XPS 9560 > > Sound works fine, headphones or speakers. I initially thought it > didn't, based on a bug I had experienced days ago in 17.04. I tried > closing the lid and re-opening, but it did nothing. Then I watched a > YouTube video about how to fix sound, and HEARD SOUND. > > So I realized the little sound indicator square that pops up when u > press volume up or volume down just isn't "booping" any sound to give > that feedback of the sound level. > > Expected behavior: boops when i press volume up or volume down > Happened: no sound upon volume up or down, volume otherwise appears to > work fine. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1721424/+subscriptions > -- 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/1721424 Title: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1721424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845749] Re: /usr/bin/yelp:11:yelp_uri_get_document_uri:action_new_window:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
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:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1845749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845750] [NEW] SegF when opening New Window on invalid URI
*** 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 on both Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: yelp 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 02:15:22 2019 InstallationDate: Installed on 2019-09-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session ** This bug has been marked a duplicate of bug 1845749 /usr/bin/yelp:11:yelp_uri_get_document_uri:action_new_window:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist -- 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/1845750 Title: SegF when opening New Window on invalid URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1845750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845732] [NEW] nautilus --check stuck after nautilus_self_check_directory
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_operations running nautilus_self_check_directory And then it just sits there. This is probably not intended. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 23:33:12 2019 GsettingsChanges: InstallationDate: Installed on 2019-09-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic eoan ** Tags added: bionic -- 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/1845732 Title: nautilus --check stuck after nautilus_self_check_directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1845732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845703] Re: Deleting starred files leaves behind starred file named ""
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_emit_valist https://errors.ubuntu.com/oops/520e475e-e15f-11e9-a69f-fa163e6cac46 -- 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 starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1845703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845703] Re: Deleting starred files leaves behind starred file named ""
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 starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1845703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845709] Re: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"
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_emit_valist https://errors.ubuntu.com/oops/520e475e-e15f-11e9-a69f-fa163e6cac46 -- 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/1845709 Title: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1845709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845709] [NEW] Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"
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 a file system object
2. Activate the "Starred" folder
3. Right-click on starred FSO
4. Select "Copy To..." from context menu
5. A new window ("Select Copy Destination") pops up, as well as the error
message in front of it.
¹ FSO: file system object, e.g. a file or folder
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
Uname: Linux 5.3.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 27 21:32:12 2019
GsettingsChanges:
InstallationDate: Installed on 2019-09-27 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
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/1845709
Title:
Selecting "Copy To..." on an object in "Starred" returns error "The
specified location is not supported"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1845709/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845703] [NEW] Deleting starred files leaves behind starred file named ""
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 Package: nautilus 1:3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 21:02:58 2019 GsettingsChanges: InstallationDate: Installed on 2019-09-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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 starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1845703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844026] Re: nautilus crashed with SIGSEGV
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://bugs.launchpad.net/bugs/1844026 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1844026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
** 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.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725017] Re: file-roller crashed with SIGSEGV in g_action_map_lookup_action()
** 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 Tracker #746829 => gitlab.gnome.org/GNOME/file-roller/issues #31 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1725017 Title: file-roller crashed with SIGSEGV in g_action_map_lookup_action() To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1725017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1436942] Re: /usr/bin/file-roller:11:g_action_map_lookup_action:fr_window_enable_action:fr_window_update_paste_command_sensitivity:fr_window_update_paste_command_sensitivity:fr_window_update_sens
*** 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 Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1436942 Title: /usr/bin/file- roller:11:g_action_map_lookup_action:fr_window_enable_action:fr_window_update_paste_command_sensitivity:fr_window_update_paste_command_sensitivity:fr_window_update_sensitivity To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1436942/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1837437] Re: disk content permanently lost when changing LUKS password
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-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1837437 Title: disk content permanently lost when changing LUKS password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1837437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1837087] Re: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed.
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 was also so for the other (to date only) three reporters, this would explain the low number of reports on errors.ubuntu.com. -- 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/1837087 Title: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837087/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
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 it locks and then goes to sleep, and of course when I open it again the SSH session is down & I have no DNS. In this state, the screen unlock is really slow. If I shut the lid not in this state, screen unlock is quick as normal. I use an Xorg session. -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 858913] Re: Can´ t drag from browser to the desktop.
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/ShellExtensions/desktop-icons/issues/22 Importance: Unknown Status: Unknown -- 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/858913 Title: Can´ t drag from browser to the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/858913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813441] Re: Can no longer drag and drop files from desktop into applications
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 applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta
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 Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1822254 Title: Can't drag and drop files to Desktop on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1822254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813441] Re: Can no longer drag and drop files from desktop into applications
** 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 Importance: Unknown Status: Unknown -- 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 applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825396] Re: "Open in Terminal" returns "Text ended before matching quote was found for '"
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: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- 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 "Text ended before matching quote was found for '" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1825396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
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 No caps lock indicator on login screen -- 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/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828123] Re: File names are percent-encoded when connect to webdav server
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828123] Re: File names are percent-encoded when connect to webdav server
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" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828123/+attachment/5262291/+files/2019-05-08%2004-45-55%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.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/1828123 Title: File names are percent-encoded when connect to webdav server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828123] [NEW] File names are percent-encoded when connect to webdav server
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 "不安与欲望", and the " "(space) in a file name is displayed as "%20". Once I copied those files to local disk, the file names are displayed correctly. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716940] Re: gvfsd-trash crashed with signal 5 in g_main_context_new()
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 crashed with signal 5 in g_main_context_new() To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1716940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825224] Re: gnome-calendar cannot add credentialed web ics calendars
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 credentialed web ics calendars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1825224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795372] Re: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed()
~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 crashed with SIGSEGV in net_device_simple_get_speed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824738] Re: gvfsd-admin crashed with signal 5
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 Status: Unknown -- 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/1824738 Title: gvfsd-admin crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1824738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825390] Re: "Open in Terminal" opens terminal in home directory
*** 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-desktop-icons via https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/105 Importance: Unknown Status: Unknown ** This bug has been marked a duplicate of bug 1825396 "Open in Terminal" returns "Text ended before matching quote was found for '" -- 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/1825390 Title: "Open in Terminal" opens terminal in home directory To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1825390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825396] Re: "Open in Terminal" returns "Text ended before matching quote was found for '"
** 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 Importance: Unknown Status: Unknown -- 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 "Text ended before matching quote was found for '" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1825396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825396] Re: "Open in Terminal" returns "Text ended before matching quote was found for '"
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-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1825396 Title: "Open in Terminal" returns "Text ended before matching quote was found for '" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1825396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825396] Re: "Open in Terminal" returns "Text ended before matching quote was found for '"
** 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 "Text ended before matching quote was found for '" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1825396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825396] [NEW] "Open in Terminal" returns "Text ended before matching quote was found for '"
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 found for '. (The text was "x-terminal-emulator --working-directory=/home/x/Desktop/aaa'bbb") This suggests improper escaping (possible security impact with command injection). Steps to reproduce: 1. On the Ubuntu 19.04.0 amd64 Desktop, right-click, and select "New folder" 2. Enter the following folder name and press Enter: aaa'bbb 3. Right-click on the newly created folder icon 4. Select "Open in Terminal" 5. The above notification pops up, no terminal window opens. The expected outcome would be: 5. A terminal window opens in directory ~/Desktop/aaa'bbb ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.1-1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 18:40:28 2019 InstallationDate: Installed on 2019-04-14 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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 "Text ended before matching quote was found for '" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1825396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825390] [NEW] "Open in Terminal" opens terminal in home directory
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 Desktop 3. Click on "Open in Terminal" 4. A terminal window opens, with a "USERNAME@HOSTNAME:~$" prompt Correctly, step 4 would be: 4. A terminal window opens, with a "USERNAME@HOSTNAME:~/Desktop/test$ prompt ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.1-1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 18:10:43 2019 InstallationDate: Installed on 2019-04-14 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1825390 Title: "Open in Terminal" opens terminal in home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1825390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
