[Desktop-packages] [Bug 1826604] Re: Extension causes saving files to desktop to be slow
On my systems, this bug also affected saving files from firefox, regardless of the destination! This is not about the time for downloading, I'm talking about ~1 kB files. On one machine, it took 4-5 seconds saving such files to any location (not just the desktop), on the other it took over 2 seconds. After renaming the extension, saving from firefox happened instantly again on both machines. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1826604 Title: Extension causes saving files to desktop to be slow Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: To reproduce: 1. Create a text file (foo.txt) on the desktop and open in gedit. 2. Type a few lines in the file and save it. Expected: the file saves more or less instantly. Observed: - The file takes several seconds to save. - The following lines appear in the journal: Apr 26 22:20:40 khaeru-laptop gnome-shell[3205]: JS ERROR: TypeError: fileItem is null _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17 _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89 Notes: - Repeating #1 and #2 with a file that is in another folder (i.e., not on the desktop), the file saves instantly, and the log messages do not appear. - This might be a duplicate/alternate description of lp#1816205. - Discovered while trying to diagnose lp#1826219. $ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons Description:Ubuntu 19.04 Release:19.04 gnome-shell-extension-desktop-icons: Installed: 19.01.1-1 Candidate: 19.01.1-1 Version table: *** 19.01.1-1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status 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: Fri Apr 26 22:24:04 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (562 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-04-22 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1826604/+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 1616332] Re: gnome-software using hundreds of MB of memory when not in use
Just happened to me, too (17.10 x64). RAM usage got up, system became sluggish then stopped responding completely, only MagicSysRQ got me out. After restart, the problem has left an ugly gift: syslog has grown to 6,4 GB (I won't upload that). tail syslog (repeating for at least last 100 lines): Jan 9 01:28:43 Comp gnome-software[1909]: Ignoring unexpected response Jan 9 01:28:43 Comp gnome-software[1909]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed Sometimes, the error messages overlapped, don't know if this is normal: Jan 9 01:36:59 Comp gnome-sofJan 9 01:37:49 Comp gnome-software[1909]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use Status in gnome-software package in Ubuntu: Triaged Bug description: It seems gnome-software is running in the background all the time. Not a big deal if it was lightweight, but it seems to use hundreds of MB (from smem output): PID User Command Swap USS PSS RSS 2291 jan /usr/bin/gnome-software --g 285436 112576 117982 134036 A total of over 400MB in RAM and swap combined. After killing and restarting, it takes "only" a bit over 100MB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 24 09:45:53 2016 InstallationDate: Installed on 2012-11-10 (1382 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+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 1728467] Re: All files on ntfs partitions are marked executable
Thank you very much for your offer, but I have messed up my system
trying to fix that and at this point I don't want to complicate matters
further (17.10 is quite buggy for me).
Would it be possible to submit your patch for official inclusion?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
Status in udisks2 package in Ubuntu:
Confirmed
Bug description:
This did not happen in 14.04 but somewhere since then udisks2 sets any & all
files on ntfs partitions as executable.
Additionally if file is copied over to user's ext4 partion the bit remains
set.
Can't see why this would be intentional??
In 14.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077",
"fmask=0177", NULL };
In 16.04, 17.04, 17.10,18.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Oct 29 21:20:19 2017
InstallationDate: Installed on 2017-09-16 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias:
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+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 1728467] Re: All files on ntfs partitions are marked executable
In ubuntu 16.10/17.04/17.10, handling of ntfs drives has changed compared to
14.04.5.
Now, all files on an ntfs drive are marked as executable.
This is bad for several reasons:
- it just does not make any sense, data files are not executable, windows
executables are usually not executable on linux
- if there is a linux executable on the ntfs drive, security procedure on ext
would be having to explicitly set the execute bit, why should it be "less"
secure if the file resides on a different drive.
- links (on ext, e.g. Desktop) to files residing on the ntfs drives are also
marked executable. Error message: "The link ... is broken. Move it to Trash?
This link cannot be used because its target ... doesn't exist." I first have to
remove the execute bit from each and every link (which reapears instantly),
only then they will be usable. All those links are invalid again after every
reboot.
Interestingly, if I remove the execute bit from a link AND open it using
OpenWith... (not the standard application to open it) then ALL links to ntfs
files become usable all of a sudden.
- if I download a file to an ntfs drive and then try to open it using firefox
download menu, I get a warning "Open executable file? ... is an executable
file. Executable files can contain viruses or other malicious code that could
harm your computer. Are you sure you want to execute ... ?" . This gives the
false impression of a security risk!
Please consider fixing this, if necessary by correcting the patch from
https://bugs.launchpad.net/gvfs/+bug/453605
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
Status in udisks2 package in Ubuntu:
Confirmed
Bug description:
This did not happen in 14.04 but somewhere since then udisks2 sets any & all
files on ntfs partitions as executable.
Additionally if file is copied over to user's ext4 partion the bit remains
set.
Can't see why this would be intentional??
In 14.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077",
"fmask=0177", NULL };
In 16.04, 17.04, 17.10,18.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Oct 29 21:20:19 2017
InstallationDate: Installed on 2017-09-16 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias:
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+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 1728467] Re: All files on ntfs partitions are marked executable
Please understand that this is severely affecting basic ubuntu use with ntfs
drives for basic users, while bug #453605 that is said to be the reason of the
misbehaviour has merely given more options to advanced users and was not
intended to mess up file handling in the way it presumably did.
If it's goal "easy way to configure the default umask for VFAT/NTFS" has been
reached, it should also be easy to set sane defaults for users that can't (nor
should be required to) do it for themselves.
** Changed in: udisks2 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
Status in udisks2 package in Ubuntu:
Confirmed
Bug description:
This did not happen in 14.04 but somewhere since then udisks2 sets any & all
files on ntfs partitions as executable.
Additionally if file is copied over to user's ext4 partion the bit remains
set.
Can't see why this would be intentional??
In 14.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077",
"fmask=0177", NULL };
In 16.04, 17.04, 17.10,18.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Oct 29 21:20:19 2017
InstallationDate: Installed on 2017-09-16 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias:
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+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
