[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
Second post, as I can only upload one file per comment. A quick screen recording to further demonstrate the reproducible issues. Worth noting that beyond the appended/suffixed text issue, drag and drop seems to struggle with location context too. Drag and drop fails multiple times through standard user permissions, but succeeds 100% of the time through root permissions. ** Attachment added: "Nautilus_Bug_Video.mp4" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+attachment/5702483/+files/Nautilus_Bug_Video.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
As no fix has been released yet... Echoing Alejandro's #10 comment, when attempting to drag and drop images from "Files" to Google Chrome or Slack, the following (seemingly random) garbage text is appended / suffixed to the file extension: .jpg0:~28:478:44 .png0:~22:478:44 .png0:~7:460:44 As a result of the appended text, the destination app returns an error indicating the file path/type is invalid: Google Chrome: Your file couldn't be accessed It may have been moved, edited, or deleted. ERR_FILE_NOT_FOUND Slack: File unsupported Sorry, is a type of file not supported by Slack Try uploading a .zip version of this file instead. [OK] In the case of Google Chrome, where the file path can be edited in the address bar, removing the characters improperly suffixed onto the file extension and attempting the navigation again by hitting Enter, the file renders as expected. A fresh installation of Ubuntu on a beefy Dell Precision 5680 laptop: OS Name: Ubuntu 22.04.3 LTS OS Type: 64-bit GNOME Version: 42.9 Windows System: Wayland Standard app installs, two different methods: Google Chrome: $ sudo apt install ./google-chrome-stable_current_amd64.deb Google Chrome Version 117.0.5938.88 (Official Build) (64-bit) Slack: $ sudo snap install slack Snap 4.34.115 64-bit StackExchange got me over to this bug filing: https://unix.stackexchange.com/questions/714305/unable-to-drag-and-drop-files-into-other-applications-on-ubuntu-22-04 And as "0xheartcode" posted there, it does seem to be a permissions issue: "It is a permission issue/feature with Ubuntu 22.04. Opening folders with sudo nautilus /home/user/ or sudo xdg-open /home/user/ fixes this." When executing "$ sudo nautilus /home/" from Terminal, supplying my password, and using the newly launched "Files" window to perform drag and drop into Slack, I can no longer reproduce the issue. With standard permissions, I encounter the improperly suffixed characters and upload error within one to three drag and drop attempts. As root, I can drag and drop upload 25+ images to Slack (10 at a time, per Slack's file upload limitations) without encountering the bug/permissions issue once. ** Attachment added: "Screenshot_References.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+attachment/5702482/+files/Screenshot_References.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
I'm experiencing this same issue as well. Syslog grew to >100GB overnight. My configuration: - Fresh install of Ubuntu 18.04.1 - HP z800 workstation with 2x Xeon X5680 - NVidia GTX 1070 Ti w/ 3 screens attached I need to stick with LTS releases but if there is a way to install a particular version of gnome-shell with the bug addressed I'd be happy to give it a try. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 --- I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), has been already finalized. Impossible to set any property to it. May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100
[Desktop-packages] [Bug 1808420] Re: gnome-system-monitor from Snap does not hide /dev/loop* mounts
** Attachment added: "system_resources.png" https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1808420/+attachment/5222128/+files/system_resources.png ** Description changed: - The `gnome-system-monitor` package preinstalled with Ubuntu 18.04 - appears to have a problem with excluding `/dev/loop*` mounts from the - File System tab. - - This is a screenshot of what it shows on my system: - - https://i.imgur.com/SHwXcsR.png - - As you can see, there's a lot of `/dev/loop*` entries, and a lot of + The gnome-system-monitor package preinstalled with Ubuntu 18.04 appears + to have a problem with excluding /dev/loop* mounts from the File System + tab. + + Attached is a screenshot of what it shows on my system. + + As you can see, there's a lot of /dev/loop* entries, and a lot of duplication of available disk space percentage. - This is a pastebin of `$ mount`: https://paste.ubuntu.com/p/T4ZKz99CdK/ + This is a pastebin of $ mount: + + sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) + proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) + udev on /dev type devtmpfs (rw,nosuid,relatime,size=8101140k,nr_inodes=2025285,mode=755) + devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) + tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1627500k,mode=755) + /dev/nvme0n1p3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) + securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) + tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) + tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) + tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) + cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) + cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) + pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) + efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) + cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) + cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) + cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) + cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) + cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) + cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) + cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) + cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) + cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) + cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) + cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) + mqueue on /dev/mqueue type mqueue (rw,relatime) + debugfs on /sys/kernel/debug type debugfs (rw,relatime) + systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=45,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22759) + hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) + sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime) + fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) + configfs on /sys/kernel/config type configfs (rw,relatime) + nfsd on /proc/fs/nfsd type nfsd (rw,relatime) + /var/lib/snapd/snaps/gnome-3-26-1604_74.snap on /snap/gnome-3-26-1604/74 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/telegram-desktop_384.snap on /snap/telegram-desktop/384 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/gnome-3-26-1604_70.snap on /snap/gnome-3-26-1604/70 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/gnome-calculator_180.snap on /snap/gnome-calculator/180 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/core_6034.snap on /snap/core/6034 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/gnome-calculator_238.snap on /snap/gnome-calculator/238 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/skype_63.snap on /snap/skype/63 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/gnome-characters_103.snap on /snap/gnome-characters/103 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/core_5897.snap on /snap/core/5897 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/gnome-characters_139.snap on /snap/gnome-characters/139 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/gnome-system-monitor_57.snap on /snap/gnome-system-monitor/57 type squashfs (ro,nodev,relatime,x-gdu.hide) + /var/lib/snapd/snaps/gnome-system-monitor_51.snap on
[Desktop-packages] [Bug 1808420] [NEW] gnome-system-monitor from Snap does not hide /dev/loop* mounts
Public bug reported: The `gnome-system-monitor` package preinstalled with Ubuntu 18.04 appears to have a problem with excluding `/dev/loop*` mounts from the File System tab. This is a screenshot of what it shows on my system: https://i.imgur.com/SHwXcsR.png As you can see, there's a lot of `/dev/loop*` entries, and a lot of duplication of available disk space percentage. This is a pastebin of `$ mount`: https://paste.ubuntu.com/p/T4ZKz99CdK/ And this is a pastebin of my current `snap` version and `$ cat /proc/self/mountinfo`: https://paste.ubuntu.com/p/3wvsFmnygw/ # How to reproduce If your version of `gnome-system-monitor` is the default installed with Ubuntu 18.04, you should already have this problem. If not, try removing the current version `sudo apt remove gnome-system-monitor`, and installing it from the snap store `sudo snap install gnome-system- monitor` to have the problem show up. It could be helpful to look into `$ cat /run/mount/utab` (I'm mentioning this only because it was suggested to me to mention it). Unfortunately I didn't do that before removing the snap package, so I don't have the output available. # Expected behaviour I would expect to only see the actual partitions in my system, in my case: `/`, `/home`, and `/boot/efi`, since I have `/home` on its own partition. # Workaround A workaround to get rid of this problem is to remove the snap package and install it via apt `sudo snap remove gnome-system-monitor && sudo apt install gnome-system-monitor`. It worked for me, and after that I only had the three partitions mentioned above showing up in the File System tab. Plus, I do have the output for `$ cat /run/mount/utab` this time: https://paste.ubuntu.com/p/tJwqjDW6T6/ ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1808420 Title: gnome-system-monitor from Snap does not hide /dev/loop* mounts Status in gnome-system-monitor package in Ubuntu: New Bug description: The `gnome-system-monitor` package preinstalled with Ubuntu 18.04 appears to have a problem with excluding `/dev/loop*` mounts from the File System tab. This is a screenshot of what it shows on my system: https://i.imgur.com/SHwXcsR.png As you can see, there's a lot of `/dev/loop*` entries, and a lot of duplication of available disk space percentage. This is a pastebin of `$ mount`: https://paste.ubuntu.com/p/T4ZKz99CdK/ And this is a pastebin of my current `snap` version and `$ cat /proc/self/mountinfo`: https://paste.ubuntu.com/p/3wvsFmnygw/ # How to reproduce If your version of `gnome-system-monitor` is the default installed with Ubuntu 18.04, you should already have this problem. If not, try removing the current version `sudo apt remove gnome-system-monitor`, and installing it from the snap store `sudo snap install gnome-system- monitor` to have the problem show up. It could be helpful to look into `$ cat /run/mount/utab` (I'm mentioning this only because it was suggested to me to mention it). Unfortunately I didn't do that before removing the snap package, so I don't have the output available. # Expected behaviour I would expect to only see the actual partitions in my system, in my case: `/`, `/home`, and `/boot/efi`, since I have `/home` on its own partition. # Workaround A workaround to get rid of this problem is to remove the snap package and install it via apt `sudo snap remove gnome-system-monitor && sudo apt install gnome-system-monitor`. It worked for me, and after that I only had the three partitions mentioned above showing up in the File System tab. Plus, I do have the output for `$ cat /run/mount/utab` this time: https://paste.ubuntu.com/p/tJwqjDW6T6/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1808420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
