Ubuntu

Thunar SLOW

Asked by Evan Langlois

I'm using Ubuntu-Studio with Cairo-Dock as the "Desktop" without much else. Thunar (from XFCE) is the file manager. Every time I open a new window it seems to take forever. My old 8Mhz Atari could pop open a window in 1/4 of the time, so why is a quad-core 1.6Ghz machine taking so long?

Anyone know what's going on or how to diagnose it? I have plenty of RAM, but I don't want to install another file manager because every time I install something it pulls in 100 files to set up a desktop (like Unity) that gets in my way and causes conflicts with how I have things set up.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Evan Langlois
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Have you tried other file managers, like pcmanfm?

Revision history for this message
Evan Langlois (uudruid74) said : 		#2

Installed that one and tried it. If its a second or two faster, its still
too long. After playing around - the problem isn't specific to
filemanagers (need to amend the bug report). Its all X apps. I just
expected it with large apps. Running a calculator or gvim is taking
forever - by menu or by terminal. Only panel-apps (which are already
loaded) open normally. Text apps are fine - something in X? Its fine once
its loaded.

On Fri, Jun 20, 2014 at 3:22 AM, actionparsnip <
<email address hidden>> wrote:

> Your question #250500 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/250500
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Have you tried other file managers, like pcmanfm?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/250500
>
> You received this question notification because you asked the question.
>

Revision history for this message
Evan Langlois (uudruid74) said : 		#3

Adding a desktop environment fixes this issue. It must spend time on start-up looking for something that isn't there. I just needed to have MORE running, not less.