Package: thunar Version: 1.2.3-4+b1 Severity: normal On initial launch the Thunar file manager takes approximately 30 seconds to start and opens two windows on a Wheezy install. I believe this is related to the "network" feature. The network feature is something that I personally do not use. There is a bug #650206, but I feel it may be a different issue. I have cc'd the bluefish debian maintainer since one of my questions involves that package.
I start with a clean AMD64 wheezy install and only install the base system during the install process (no standard package list, desktop packages, etc.). I have a apt.conf file with Apt::Install-Recommends "false"; and Aptitude::Recommends-Important "false"; and use the official debian repos for installing wheezy plus security packages. I start by installing a minimalist desktop environment using openbox, xorg, sakua, leafpad, tango-icon-theme, consolekit, policykit-1, libpam-ck-connector, gvfs, and thuanr. Once in an X11 session, if I launch thunar, then it starts within a second and no network icon is in the side pane. I continue customizing my system with programs that I frequently use which includes blusfish. The bluefish package pulls in gvfs-backends. Once APT finihes configuring the packages Thunar starts slowly and with two instances on first launch. Also, the network icon is now visible in the side pane. This behavior will continue to happen upon subsequent reboots or log off / ons. After searching Internet forums, a possible workaround is to edit as root the following file and change the automount option from true to false: /usr/share/gvfs/mounts/network.mount. This does solve the behavior issue but also results in the "network" icon showing a paper with red square with an "x". If a user does double click the network icon then an error box shows a failed to open "Network" message with a DBus error. Okay, so I figured out that bluefish was the reason for the slow thunar behavior since it pulled in the gvfs-backends package. I was looking through the changelog of bluefish and noticed that on June 29, 2010 the gvfs-backends package was adjusted to a "Depends" from "Suggest" (if I read that correctly). I was wondering the following: Can bluefish's depends on gvfs-backends be changed to Recommends instead? This in my opinion would be the easiest method, but there may have been a strong reason for the initial change. Is there a way to disable network support in thunar without recompiling the package on the user's end? Use the workaround mentioned above and remove the network icon from the side pane? I apologize for the rather long bug report and look forward to hearing your thoughts. Thank You. --Michael P. Carr Jr.
