Modifying file contents very slow on upgrade to Ubuntu 19.04How do you configure Tracker search indexing tool?After upgrading from 18.10 to 19.04, `tracker-extract` eats up so much RAM it freezes my machinePerformance issues after upgrading to 19.04Memory leak in tracker-extract?Ubuntu become very slow and unresponsive after upgrade to 12.04?Slow distro upgradeHow to stop Tracker indexing file contents?Tracker not indexing file contentsEnable search in file (PDF) contents using trackerIssues with extensions interfering with the dock in Ubuntu 19.04Upgrade Ubuntu from 18.10 to 19.04
What is the ring of invariants under the action of an arbitrary subgroup of the symmetric group?
Fix/Move Ethernet on Side of House
Novel set in the future, children cannot change the class they are born into, one class is made uneducated by associating books with pain
Glacial, Magnetic and Mossy Lures; what Pokémon do they attract?
Giving a character trauma but not "diagnosing" her?
Can a character dodge an attack that beats their Armor Class?
My professor says my digit summing code is flawed. Is he right?
Fantasy novel/series with young man who discovers he can use magic that is outlawed
Are there any rules around when something can be described as "based on a true story"?
Did Feynman cite a fallacy about only circles having the same width in all directions as a reason for the Challenger disaster?
How can demon technology be prevented from surpassing humans?
How honest to be with US immigration about uncertainty about travel plans?
What is the German word for: "It only works when I try to show you how it does not work"?
Is Having my Players Control Two Parties a Good Idea?
"Dear Stack Exchange, I am very disappointed in you" - How to construct a strong opening line in a letter?
How does paying extra on my mortgage affect my amortization schedule?
How do I weigh a kitchen island to determine what size castors to get?
Which collation should I use for biblical Hebrew?
C4_4 Reflection!
How did Ron get five hundred Chocolate Frog cards?
Is It Possible to Make a Computer Virus That Acts as an Anti-virus?
How can my hammerspace safely "decompress"?
Count number of different name in a file
How much income am I getting by renting my house?
Modifying file contents very slow on upgrade to Ubuntu 19.04
How do you configure Tracker search indexing tool?After upgrading from 18.10 to 19.04, `tracker-extract` eats up so much RAM it freezes my machinePerformance issues after upgrading to 19.04Memory leak in tracker-extract?Ubuntu become very slow and unresponsive after upgrade to 12.04?Slow distro upgradeHow to stop Tracker indexing file contents?Tracker not indexing file contentsEnable search in file (PDF) contents using trackerIssues with extensions interfering with the dock in Ubuntu 19.04Upgrade Ubuntu from 18.10 to 19.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I performed an upgrade from Ubuntu 18.10 to 19.04 and noticed that (somehow) creating, modifying, and deleting files is now much slower. Simply creating or deleting an empty file takes around 3 seconds on my relatively modern SSD.
Oddly enough, the commands themselves still run almost instantly:
$ time touch foo
real 0m0.003s
user 0m0.000s
sys 0m0.003s
Moreover, when I press the Enter key to execute the command, the cursor will stay on the same line during the 3 seconds. For these reasons I believe the issue is with Bash or the terminal hanging.
Similar behaviour can be seen when opening or saving files with Vim, except when running it in view mode.
EDIT
By request, I disabled all Gnome extensions, to no avail. The command ls -al ~/.local/share/gnome-shell/extensions shows that the directory is empty.
bash upgrade vim tracker
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
|
show 4 more comments
I performed an upgrade from Ubuntu 18.10 to 19.04 and noticed that (somehow) creating, modifying, and deleting files is now much slower. Simply creating or deleting an empty file takes around 3 seconds on my relatively modern SSD.
Oddly enough, the commands themselves still run almost instantly:
$ time touch foo
real 0m0.003s
user 0m0.000s
sys 0m0.003s
Moreover, when I press the Enter key to execute the command, the cursor will stay on the same line during the 3 seconds. For these reasons I believe the issue is with Bash or the terminal hanging.
Similar behaviour can be seen when opening or saving files with Vim, except when running it in view mode.
EDIT
By request, I disabled all Gnome extensions, to no avail. The command ls -al ~/.local/share/gnome-shell/extensions shows that the directory is empty.
bash upgrade vim tracker
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
Do you happen to be running one of the "Top Bar" gnome extensions?
– Charles Green
Apr 25 at 20:24
@CharlesGreen I don't believe so. I had a media player extension but had to disable it since it is not support on Gnome 3.32. Removing the extension and restarting did not solve the problem.
– Alessandro Power
Apr 25 at 20:34
and thetopcommand does not show any processes consuming excess CPU time?
– Charles Green
Apr 25 at 20:55
Very likely a GNOME extension problem. Go to extensions.gnome.org/local and temporarily disable ALL extensions, and either restart GNOME shell, or log out/in, and retest for slowness. Edit your question and show mels -al ~/.local/share/gnome-shell/extensions. Report back.
– heynnema
Apr 25 at 21:12
1
Could it have something to do with file indexing/tracking?
– DK Bose
Apr 26 at 3:49
|
show 4 more comments
I performed an upgrade from Ubuntu 18.10 to 19.04 and noticed that (somehow) creating, modifying, and deleting files is now much slower. Simply creating or deleting an empty file takes around 3 seconds on my relatively modern SSD.
Oddly enough, the commands themselves still run almost instantly:
$ time touch foo
real 0m0.003s
user 0m0.000s
sys 0m0.003s
Moreover, when I press the Enter key to execute the command, the cursor will stay on the same line during the 3 seconds. For these reasons I believe the issue is with Bash or the terminal hanging.
Similar behaviour can be seen when opening or saving files with Vim, except when running it in view mode.
EDIT
By request, I disabled all Gnome extensions, to no avail. The command ls -al ~/.local/share/gnome-shell/extensions shows that the directory is empty.
bash upgrade vim tracker
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
I performed an upgrade from Ubuntu 18.10 to 19.04 and noticed that (somehow) creating, modifying, and deleting files is now much slower. Simply creating or deleting an empty file takes around 3 seconds on my relatively modern SSD.
Oddly enough, the commands themselves still run almost instantly:
$ time touch foo
real 0m0.003s
user 0m0.000s
sys 0m0.003s
Moreover, when I press the Enter key to execute the command, the cursor will stay on the same line during the 3 seconds. For these reasons I believe the issue is with Bash or the terminal hanging.
Similar behaviour can be seen when opening or saving files with Vim, except when running it in view mode.
EDIT
By request, I disabled all Gnome extensions, to no avail. The command ls -al ~/.local/share/gnome-shell/extensions shows that the directory is empty.
bash upgrade vim tracker
bash upgrade vim tracker
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
edited Apr 30 at 3:35
DK Bose
19.8k13 gold badges57 silver badges111 bronze badges
19.8k13 gold badges57 silver badges111 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
asked Apr 25 at 20:15
Alessandro PowerAlessandro Power
1631 gold badge4 silver badges14 bronze badges
1631 gold badge4 silver badges14 bronze badges
Do you happen to be running one of the "Top Bar" gnome extensions?
– Charles Green
Apr 25 at 20:24
@CharlesGreen I don't believe so. I had a media player extension but had to disable it since it is not support on Gnome 3.32. Removing the extension and restarting did not solve the problem.
– Alessandro Power
Apr 25 at 20:34
and thetopcommand does not show any processes consuming excess CPU time?
– Charles Green
Apr 25 at 20:55
Very likely a GNOME extension problem. Go to extensions.gnome.org/local and temporarily disable ALL extensions, and either restart GNOME shell, or log out/in, and retest for slowness. Edit your question and show mels -al ~/.local/share/gnome-shell/extensions. Report back.
– heynnema
Apr 25 at 21:12
1
Could it have something to do with file indexing/tracking?
– DK Bose
Apr 26 at 3:49
|
show 4 more comments
Do you happen to be running one of the "Top Bar" gnome extensions?
– Charles Green
Apr 25 at 20:24
@CharlesGreen I don't believe so. I had a media player extension but had to disable it since it is not support on Gnome 3.32. Removing the extension and restarting did not solve the problem.
– Alessandro Power
Apr 25 at 20:34
and thetopcommand does not show any processes consuming excess CPU time?
– Charles Green
Apr 25 at 20:55
Very likely a GNOME extension problem. Go to extensions.gnome.org/local and temporarily disable ALL extensions, and either restart GNOME shell, or log out/in, and retest for slowness. Edit your question and show mels -al ~/.local/share/gnome-shell/extensions. Report back.
– heynnema
Apr 25 at 21:12
1
Could it have something to do with file indexing/tracking?
– DK Bose
Apr 26 at 3:49
Do you happen to be running one of the "Top Bar" gnome extensions?
– Charles Green
Apr 25 at 20:24
Do you happen to be running one of the "Top Bar" gnome extensions?
– Charles Green
Apr 25 at 20:24
@CharlesGreen I don't believe so. I had a media player extension but had to disable it since it is not support on Gnome 3.32. Removing the extension and restarting did not solve the problem.
– Alessandro Power
Apr 25 at 20:34
@CharlesGreen I don't believe so. I had a media player extension but had to disable it since it is not support on Gnome 3.32. Removing the extension and restarting did not solve the problem.
– Alessandro Power
Apr 25 at 20:34
and the
top command does not show any processes consuming excess CPU time?– Charles Green
Apr 25 at 20:55
and the
top command does not show any processes consuming excess CPU time?– Charles Green
Apr 25 at 20:55
Very likely a GNOME extension problem. Go to extensions.gnome.org/local and temporarily disable ALL extensions, and either restart GNOME shell, or log out/in, and retest for slowness. Edit your question and show me
ls -al ~/.local/share/gnome-shell/extensions. Report back.– heynnema
Apr 25 at 21:12
Very likely a GNOME extension problem. Go to extensions.gnome.org/local and temporarily disable ALL extensions, and either restart GNOME shell, or log out/in, and retest for slowness. Edit your question and show me
ls -al ~/.local/share/gnome-shell/extensions. Report back.– heynnema
Apr 25 at 21:12
1
1
Could it have something to do with file indexing/tracking?
– DK Bose
Apr 26 at 3:49
Could it have something to do with file indexing/tracking?
– DK Bose
Apr 26 at 3:49
|
show 4 more comments
2 Answers
2
active
oldest
votes
Since your issue is related to creating or deleting files, it's possible that the system's indexing/tracking activity is responsible for the delays you see.
From the release notes for Disco Dingo:
Tracker is now included by default. This allows the desktop to keep
track of recently used files and improves searching.
A graphical interface present in early versions of tracker has been removed in more recent versions, but going into Settings > Search provides an on/off switch (1 in the image below), as well as an interface to choose which folders are to be indexed (the little cog wheel icon next to 2 in the image below).
Turning Tracker on/off or adjusting its settings
Alternatively, one can use the terminal:
tracker --help points to tracker daemon and man tracker-daemon points to tracker daemon --kill as well as other options.
When I ran tracker daemon --kill, I got:
dkb@dkb-UM:~$ tracker daemon --kill
Found 3 PIDs…
Killed process 1486 — “tracker-miner-apps”
Killed process 1494 — “tracker-miner-fs”
Killed process 1496 — “tracker-store”
dkb@dkb-UM:~$ pgrep -al tracker
dkb@dkb-UM:~$
It's quite possible that tracker hogs a lot of resources in the short term just after upgrading from a system in which tracker was not in use to 19.04 where tracker is on by default.
I came across Getting Started and First 5 minutes with Tracker which are quite simple introductory articles on tracker. If one reads those articles, it should be possible to benefit from tracker.
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
1
Disablingtrackersolved the issue.
– Alessandro Power
Apr 26 at 4:18
@AlessandroPower Very interesting - I had not realized that a graphical interface has been re-implemented. I had found somewhere that deleteing thetrackerdirectories under.cacheand.local/sharealso improved tracker performance - sometimes it runs across files that it cannot index properly.
– Charles Green
Apr 26 at 15:38
add a comment
|
I have the same problem. Appears to be a bug in a gnome extension:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826604
Rename the folder of desktop-icons extension solve my problem.
answered May 11 at 17:04
donatodonato
111 bronze badge
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1138175%2fmodifying-file-contents-very-slow-on-upgrade-to-ubuntu-19-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Since your issue is related to creating or deleting files, it's possible that the system's indexing/tracking activity is responsible for the delays you see.
From the release notes for Disco Dingo:
Tracker is now included by default. This allows the desktop to keep
track of recently used files and improves searching.
A graphical interface present in early versions of tracker has been removed in more recent versions, but going into Settings > Search provides an on/off switch (1 in the image below), as well as an interface to choose which folders are to be indexed (the little cog wheel icon next to 2 in the image below).
Turning Tracker on/off or adjusting its settings
Alternatively, one can use the terminal:
tracker --help points to tracker daemon and man tracker-daemon points to tracker daemon --kill as well as other options.
When I ran tracker daemon --kill, I got:
dkb@dkb-UM:~$ tracker daemon --kill
Found 3 PIDs…
Killed process 1486 — “tracker-miner-apps”
Killed process 1494 — “tracker-miner-fs”
Killed process 1496 — “tracker-store”
dkb@dkb-UM:~$ pgrep -al tracker
dkb@dkb-UM:~$
It's quite possible that tracker hogs a lot of resources in the short term just after upgrading from a system in which tracker was not in use to 19.04 where tracker is on by default.
I came across Getting Started and First 5 minutes with Tracker which are quite simple introductory articles on tracker. If one reads those articles, it should be possible to benefit from tracker.
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
1
Disablingtrackersolved the issue.
– Alessandro Power
Apr 26 at 4:18
@AlessandroPower Very interesting - I had not realized that a graphical interface has been re-implemented. I had found somewhere that deleteing thetrackerdirectories under.cacheand.local/sharealso improved tracker performance - sometimes it runs across files that it cannot index properly.
– Charles Green
Apr 26 at 15:38
add a comment
|
Since your issue is related to creating or deleting files, it's possible that the system's indexing/tracking activity is responsible for the delays you see.
From the release notes for Disco Dingo:
Tracker is now included by default. This allows the desktop to keep
track of recently used files and improves searching.
A graphical interface present in early versions of tracker has been removed in more recent versions, but going into Settings > Search provides an on/off switch (1 in the image below), as well as an interface to choose which folders are to be indexed (the little cog wheel icon next to 2 in the image below).
Turning Tracker on/off or adjusting its settings
Alternatively, one can use the terminal:
tracker --help points to tracker daemon and man tracker-daemon points to tracker daemon --kill as well as other options.
When I ran tracker daemon --kill, I got:
dkb@dkb-UM:~$ tracker daemon --kill
Found 3 PIDs…
Killed process 1486 — “tracker-miner-apps”
Killed process 1494 — “tracker-miner-fs”
Killed process 1496 — “tracker-store”
dkb@dkb-UM:~$ pgrep -al tracker
dkb@dkb-UM:~$
It's quite possible that tracker hogs a lot of resources in the short term just after upgrading from a system in which tracker was not in use to 19.04 where tracker is on by default.
I came across Getting Started and First 5 minutes with Tracker which are quite simple introductory articles on tracker. If one reads those articles, it should be possible to benefit from tracker.
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
1
Disablingtrackersolved the issue.
– Alessandro Power
Apr 26 at 4:18
@AlessandroPower Very interesting - I had not realized that a graphical interface has been re-implemented. I had found somewhere that deleteing thetrackerdirectories under.cacheand.local/sharealso improved tracker performance - sometimes it runs across files that it cannot index properly.
– Charles Green
Apr 26 at 15:38
add a comment
|
Since your issue is related to creating or deleting files, it's possible that the system's indexing/tracking activity is responsible for the delays you see.
From the release notes for Disco Dingo:
Tracker is now included by default. This allows the desktop to keep
track of recently used files and improves searching.
A graphical interface present in early versions of tracker has been removed in more recent versions, but going into Settings > Search provides an on/off switch (1 in the image below), as well as an interface to choose which folders are to be indexed (the little cog wheel icon next to 2 in the image below).
Turning Tracker on/off or adjusting its settings
Alternatively, one can use the terminal:
tracker --help points to tracker daemon and man tracker-daemon points to tracker daemon --kill as well as other options.
When I ran tracker daemon --kill, I got:
dkb@dkb-UM:~$ tracker daemon --kill
Found 3 PIDs…
Killed process 1486 — “tracker-miner-apps”
Killed process 1494 — “tracker-miner-fs”
Killed process 1496 — “tracker-store”
dkb@dkb-UM:~$ pgrep -al tracker
dkb@dkb-UM:~$
It's quite possible that tracker hogs a lot of resources in the short term just after upgrading from a system in which tracker was not in use to 19.04 where tracker is on by default.
I came across Getting Started and First 5 minutes with Tracker which are quite simple introductory articles on tracker. If one reads those articles, it should be possible to benefit from tracker.
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
Since your issue is related to creating or deleting files, it's possible that the system's indexing/tracking activity is responsible for the delays you see.
From the release notes for Disco Dingo:
Tracker is now included by default. This allows the desktop to keep
track of recently used files and improves searching.
A graphical interface present in early versions of tracker has been removed in more recent versions, but going into Settings > Search provides an on/off switch (1 in the image below), as well as an interface to choose which folders are to be indexed (the little cog wheel icon next to 2 in the image below).
Turning Tracker on/off or adjusting its settings
Alternatively, one can use the terminal:
tracker --help points to tracker daemon and man tracker-daemon points to tracker daemon --kill as well as other options.
When I ran tracker daemon --kill, I got:
dkb@dkb-UM:~$ tracker daemon --kill
Found 3 PIDs…
Killed process 1486 — “tracker-miner-apps”
Killed process 1494 — “tracker-miner-fs”
Killed process 1496 — “tracker-store”
dkb@dkb-UM:~$ pgrep -al tracker
dkb@dkb-UM:~$
It's quite possible that tracker hogs a lot of resources in the short term just after upgrading from a system in which tracker was not in use to 19.04 where tracker is on by default.
I came across Getting Started and First 5 minutes with Tracker which are quite simple introductory articles on tracker. If one reads those articles, it should be possible to benefit from tracker.
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
edited Apr 26 at 10:42
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
answered Apr 26 at 4:17
DK BoseDK Bose
19.8k13 gold badges57 silver badges111 bronze badges
19.8k13 gold badges57 silver badges111 bronze badges
1
Disablingtrackersolved the issue.
– Alessandro Power
Apr 26 at 4:18
@AlessandroPower Very interesting - I had not realized that a graphical interface has been re-implemented. I had found somewhere that deleteing thetrackerdirectories under.cacheand.local/sharealso improved tracker performance - sometimes it runs across files that it cannot index properly.
– Charles Green
Apr 26 at 15:38
add a comment
|
1
Disablingtrackersolved the issue.
– Alessandro Power
Apr 26 at 4:18
@AlessandroPower Very interesting - I had not realized that a graphical interface has been re-implemented. I had found somewhere that deleteing thetrackerdirectories under.cacheand.local/sharealso improved tracker performance - sometimes it runs across files that it cannot index properly.
– Charles Green
Apr 26 at 15:38
1
1
Disabling
tracker solved the issue.– Alessandro Power
Apr 26 at 4:18
Disabling
tracker solved the issue.– Alessandro Power
Apr 26 at 4:18
@AlessandroPower Very interesting - I had not realized that a graphical interface has been re-implemented. I had found somewhere that deleteing the
tracker directories under .cache and .local/share also improved tracker performance - sometimes it runs across files that it cannot index properly.– Charles Green
Apr 26 at 15:38
@AlessandroPower Very interesting - I had not realized that a graphical interface has been re-implemented. I had found somewhere that deleteing the
tracker directories under .cache and .local/share also improved tracker performance - sometimes it runs across files that it cannot index properly.– Charles Green
Apr 26 at 15:38
add a comment
|
I have the same problem. Appears to be a bug in a gnome extension:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826604
Rename the folder of desktop-icons extension solve my problem.
answered May 11 at 17:04
donatodonato
111 bronze badge
add a comment
|
I have the same problem. Appears to be a bug in a gnome extension:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826604
Rename the folder of desktop-icons extension solve my problem.
answered May 11 at 17:04
donatodonato
111 bronze badge
add a comment
|
I have the same problem. Appears to be a bug in a gnome extension:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826604
Rename the folder of desktop-icons extension solve my problem.
answered May 11 at 17:04
donatodonato
111 bronze badge
I have the same problem. Appears to be a bug in a gnome extension:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826604
Rename the folder of desktop-icons extension solve my problem.
answered May 11 at 17:04
donatodonato
111 bronze badge
answered May 11 at 17:04
donatodonato
111 bronze badge
answered May 11 at 17:04
donatodonato
111 bronze badge
answered May 11 at 17:04
donatodonato
111 bronze badge
111 bronze badge
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1138175%2fmodifying-file-contents-very-slow-on-upgrade-to-ubuntu-19-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you happen to be running one of the "Top Bar" gnome extensions?
– Charles Green
Apr 25 at 20:24
@CharlesGreen I don't believe so. I had a media player extension but had to disable it since it is not support on Gnome 3.32. Removing the extension and restarting did not solve the problem.
– Alessandro Power
Apr 25 at 20:34
and the
topcommand does not show any processes consuming excess CPU time?– Charles Green
Apr 25 at 20:55
Very likely a GNOME extension problem. Go to extensions.gnome.org/local and temporarily disable ALL extensions, and either restart GNOME shell, or log out/in, and retest for slowness. Edit your question and show me
ls -al ~/.local/share/gnome-shell/extensions. Report back.– heynnema
Apr 25 at 21:12
1
Could it have something to do with file indexing/tracking?
– DK Bose
Apr 26 at 3:49