[Bug 1948599] Re: Nautilus icon missing from taskbar (21.10; Xorg)
journalctl errors show while opening nautilus: ``` 11月 06 10:21:20 laptop dbus-daemon[2693]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.5577' (uid=1000 pid=1013168 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") 11月 06 10:21:20 laptop gnome-shell[9951]: JS ERROR: TypeError: dockManager is null getRunningApps@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:653:9 wrapWindowsManagerApp/fileManagerApp._updateWindows@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:258:9 wrapWindowsManagerApp/windowsChangedId<@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:250:24 11月 06 10:21:20 laptop gnome-shell[9951]: JS ERROR: TypeError: dockManager is null getRunningApps@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:653:9 wrapWindowsManagerApp/fileManagerApp._updateWindows@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:258:9 wrapWindowsManagerApp/windowsChangedId<@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:250:24 11月 06 10:21:20 laptop gnome-shell[9951]: JS ERROR: TypeError: dockManager is null getRunningApps@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:653:9 wrapWindowsManagerApp/fileManagerApp._updateWindows@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:258:9 wrapWindowsManagerApp/windowsChangedId<@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:250:24 11月 06 10:21:20 laptop gnome-shell[9951]: JS ERROR: TypeError: dockManager is null getRunningApps@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:653:9 wrapWindowsManagerApp/fileManagerApp._updateWindows@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:258:9 wrapWindowsManagerApp/windowsChangedId<@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:250:24 11月 06 10:21:20 laptop gnome-shell[9951]: JS ERROR: TypeError: dockManager is null getRunningApps@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:653:9 wrapWindowsManagerApp/fileManagerApp._updateWindows@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:258:9 wrapWindowsManagerApp/windowsChangedId<@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:250:24 ``` -- 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/1948599 Title: Nautilus icon missing from taskbar (21.10; Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
So the upload in the focal queue: - adds a debian/patches/series entry - for a patch that was already included in the previous upload - that was released because the test case in the bug description was reported to have passed with the version in -proposed And there have been no changes to the test case. What is this upload actually fixing? ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: In Progress => Incomplete -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950026] [NEW] gnome-shell leaks mem, 13.8G virt, 1.3G reserved after few days of uptime
Public bug reported: gnome-shell leaks memory like crazy. after 4 days of uptime it uses 13.8G virt and 1.3G reserved mem. This is after I switched to wayland to mitigate the same issue, but on X.org it was much more crazier - about 20G virt / 1.5G reserved after one-two days of uptime, only the leak was in X.org process (2 of them, greeter and main), not gnome-shell. p.s. I do understand that gnome is the best piece of software, and I just use it incorrectly - likely I have some extension or application that is at fault. The bug report is sort of rhetorical. p.p.s. Unmodified LTS system (focal). Started to manifest about a month ago, out of the blue, no changes... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sat Nov 6 01:50:41 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) monitors.xml: Error: path contained symlinks. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-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/1950026 Title: gnome-shell leaks mem, 13.8G virt, 1.3G reserved after few days of uptime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950018] Re: package fonts-noto-extra 20200323-1build1~ubuntu20.04.1 failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/fonts-noto-extra.list-new« kann nicht angelegt werden: Vorgang nicht
Thanks for your report. It sounds as a hardware issue, though. Please try to reinstall the package: sudo apt install --reinstall fonts-noto-extra and let us know if it helps. ** Changed in: fonts-noto (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1950018 Title: package fonts-noto-extra 20200323-1build1~ubuntu20.04.1 failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/fonts-noto-extra.list- new« kann nicht angelegt werden: Vorgang nicht zulässig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1950018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950018] [NEW] package fonts-noto-extra 20200323-1build1~ubuntu20.04.1 failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/fonts-noto-extra.list-new« kann nicht angelegt werden: Vorgang nic
Public bug reported: ass ProblemType: Package DistroRelease: Ubuntu 20.04 Package: fonts-noto-extra 20200323-1build1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 5 22:22:31 2021 Dependencies: ErrorMessage: Neue Datei »/var/lib/dpkg/info/fonts-noto-extra.list-new« kann nicht angelegt werden: Vorgang nicht zulässig InstallationDate: Installed on 2021-09-02 (64 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: fonts-noto Title: package fonts-noto-extra 20200323-1build1~ubuntu20.04.1 failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/fonts-noto-extra.list-new« kann nicht angelegt werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-noto (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1950018 Title: package fonts-noto-extra 20200323-1build1~ubuntu20.04.1 failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/fonts-noto-extra.list- new« kann nicht angelegt werden: Vorgang nicht zulässig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1950018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870597]
Was this patch sent to the maintainers? If so, was it applied? -- 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/1870597 Title: libinput says "your system is too slow" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915910] Re: evince does not print
** Tags added: apparmor hirsute ** Summary changed: - evince does not print + evince does not print (apparmor, pxgsettings) -- 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/1915910 Title: evince does not print (apparmor, pxgsettings) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759526] Re: Enabling 'Auto-hide the Dock' moves the clock and desktop icons
I'm not sure this is actually a bug. We supported moving the clock to the center in case the dock is in panel mode, but I think in the auto-hide case, there will be always a case where people will prefer to have it centered to the desktop (when it's mostly hidden) or to the actual workarea. So, I think this can be closed. We can continue the discussion upstream. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1759526 Title: Enabling 'Auto-hide the Dock' moves the clock and desktop icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1759526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Description changed: [Impact] - * Gdm crashed and user need to be an expert to know how to work around, -or need to reboot to fix. + * Gdm crashed and user need to be an expert to know how to work around, + or need to reboot to fix. - * OEM projects got certain SKU that can reliably reproduce this issue. + * OEM projects got certain SKU that can reliably reproduce this issue. - * A merged patch in upstream fix the race condition. + * A merged patch in upstream fix the race condition. [Test Plan] - * Use the SKU that can reliably reproduce this issue. - * Do a cold boot, and wait for 5 mins. The monitor should turned-black -but showing the Machine Vendor logo that was previously -displayed by plythmouth. - * Try to dog-food the deb from the proposed channel and make sure -all input events still properly propagate. + * Use the SKU that can reliably reproduce this issue. + * Do a cold boot, and wait for 5 mins. The monitor should turned-black + but showing the Machine Vendor logo that was previously + displayed by plymouth. + * Try to dog-food the deb from the proposed channel and make sure + all input events still properly propagate. [Where problems could occur] - * If the patch is not properly working as expected, per the file this -patch touch, the user desktop session could stop responding to -mouse, keyboard, and touch screen input. + * If the patch is not properly working as expected, per the file this + patch touch, the user desktop session could stop responding to + mouse, keyboard, and touch screen input. [Other Info] - - * Can't think of any for now. + + * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
Correction of gnome-shell-extension-desktop-icons uploaded to focal unapproved queue. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
This bug was fixed in the package mutter - 40.5-1ubuntu3 --- mutter (40.5-1ubuntu3) jammy; urgency=medium [ Yuan-Chen Cheng ] * d/p/mutter-wayland-seat-race-fix.patch: - Fix Xwayland crash Xwayland crash in gdm as screen off and touchscreen detach (cherry picked commits — LP: #1948894) [ Marco Trevisan (Treviño) ] * debian/patches: Refresh -- Marco Trevisan (Treviño) Wed, 03 Nov 2021 19:37:09 +0100 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949845] Re: Toggle enable/disable dock autohide gives glitches
Tested on a Xorg session, where i cannot reproduce the glitches -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949966] [NEW] sshfs randomly corrupts files
Public bug reported: /usr/bin/sshfs the way it is packaged now is broken, tested on 20.04 focal and 21.10 impish. This issue is not present on Debian Sid or Arch Linux. The way the issue shows is that majority of the time, a 40MB .zip file I download from an SFTP server is broken. The stat is identical, filesize is identical to the byte, but the inside is a garbled mess that refuses to unzip anymore. Tested via (and almost always getting a random checksum): md5sum /mnt/file.zip && umount /mnt/sftp && mount /mnt/sftp && md5sum /mnt/file.zip I used a definition in fstab but also manually mounted via 'sshfs -o allow_other,default_permissions' This is not a kernel issue, this is not a network issue, I have tested in containers and across servers. Unfortunately, I do not have administrative access to the server I am testing against, so this is the only idea I have about it: Remote protocol version 2.0, remote software version CrushFTPSSHD The workaround is to replace the /usr/bin/sshfs binary(and adding an accompanying libfuse3.so to the correct path) from Arch Linux. This should be an sshfs issue, not a libfuse issue, as copying libfuse2 from Arch does not make the issue disappear. ** Affects: sshfs-fuse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to sshfs-fuse in Ubuntu. https://bugs.launchpad.net/bugs/1949966 Title: sshfs randomly corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/1949966/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922548] Re: The admin backend is broken
fixed in jammy by corrado@corrado-jj-1023:~$ apt policy gvfs gvfs: Installed: 1.48.1-2ubuntu2 Candidate: 1.48.1-2ubuntu2 Version table: *** 1.48.1-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-jj-1023:~$ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: The admin backend is broken To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1922548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
As mentioned in comment #37, the original test case is likely to pass in 3.36.9+ even without the patch correctly applied. So the new second test case should be to verify that the patch is correctly applied. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
I proposed a fixup here: https://salsa.debian.org/gnome-team/shell- extensions/gnome-shell-extension-desktop-icons/-/merge_requests/11 Best to start with git. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949845] Re: Toggle enable/disable dock autohide gives glitches
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1949845 ** Tags added: iso-testing -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
You appear to be right :( My patch in comment #28 is correct, but the one we actually released is not: https://launchpadlibrarian.net/563648801/gnome-shell-extension-desktop- icons_20.04.0-3~ubuntu20.04.3_20.04.0-3~ubuntu20.04.4.diff.gz ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: Fix Released => In Progress -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
@vanvugt, I checked the latest source code of gnome-shell-extension-desktop- icons, found the desktopManager-Avoid-scheduling-multiple- _layoutChil.patch was not applied, there are not this file in debian/patches/series. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949845] Re: Toggle enable/disable dock autohide gives glitches
There are two glitches here: 1. Selecting the Appearance tab for the first time causes the Dock to disappear briefly. 2. Toggling the "Auto-hide the Dock" setting causes the Dock (plus the Settings icon) and the Application menu to flash and re-render. Screencasts are attached below. Pay attention to the Dock (plus the Settings icon) and the Application menu. ** Attachment added: "bug_1949845.tar" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+attachment/5538338/+files/bug_1949845.tar -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1143282] Re: Unable to add podcasts in rhythmbox
Had a similar problem as described at the top of this page I was trying to access link: http://feeds.feedburner.com/se-radio The solution on my end was to add .xml to the end of the link http://feeds.feedburner.com/se-radio.xml -- 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/1143282 Title: Unable to add podcasts in rhythmbox To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1143282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949845] Re: Toggle enable/disable dock autohide gives glitches
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
