Written by Arioch the 28 Feb 08 at 15:26.

I propose to the development team (both Ubuntu and by extension Gnome) to work on the improvement of boot up times in Ubuntu systems.

I propose to the development team (both Ubuntu and by extension Gnome) to work on the improvement of boot up times in Ubuntu systems.

Written by tchalvakspam the 23 Jan 09 at 21:53.

In addition to speeding up the processes involved, which is key, make it simple for the user to streamline their own bootup. Installing different software can -always- slow down a bootup, no matter how fast it was initially.

Thus, to -keep- boot time short for the many different ways that people use ubuntu, provide the ubuntu user with a simple default tool to remove, delay the start of, or uninstall software that take the most time during startup. The combination of a default boot-time analysis tool and the current session startup manager would provide allow easy boot streamlining, and to a lesser extent so would showing on-screen indicators of what things are being started up over the course of the normal ubuntu boot load.
Allowing user analysis is the key feature missing to make streamlining available to the individual in addition to the developer.

In addition to speeding up the processes involved, which is key, make it simple for the user to streamline their own bootup. Installing different software can -always- slow down a bootup, no matter how fast it was initially. Thus, to -keep- boot time short for the many different ways that people use ubuntu, provide the ubuntu user with a simple default tool to remove, delay the start of, or uninstall software that take the most time during startup. The combination of a default boot-time analysis tool and the current session startup manager would provide allow easy boot streamlining, and to a lesser extent so would showing on-screen indicators of what things are being started up over the course of the normal ubuntu boot load. Allowing user analysis is the key feature missing to make streamlining available to the individual in addition to the developer.

Written by aadityabhatia the 29 Jan 09 at 04:57.

Some programs take too long and are not required immediately upon boot. For example, sendmail takes forever to start and a regular desktop user usually wants to see a login screen asap, so sendmail can wait. Such programs could be identified and their initiation can be delayed while rest of the system continues booting up.

Some programs take too long and are not required immediately upon boot. For example, sendmail takes forever to start and a regular desktop user usually wants to see a login screen asap, so sendmail can wait. Such programs could be identified and their initiation can be delayed while rest of the system continues booting up.

Written by aadityabhatia the 29 Jan 09 at 05:04.

There is a contrast in the comments: some machines take more time before login screen, some do after. In many cases it's the compiz and in some it's dbus or a part of gnome.

The idea is to have a profiler start at the beginning of boot process, on demand, and measure the time taken by each program at startup, writing it to a log file. This will help users figure out what part takes the most time, and will simplify profiling the boot process.

Not sure how much effort is involved, but sounds possible. Any takers?

There is a contrast in the comments: some machines take more time before login screen, some do after. In many cases it's the compiz and in some it's dbus or a part of gnome. The idea is to have a profiler start at the beginning of boot process, on demand, and measure the time taken by each program at startup, writing it to a log file. This will help users figure out what part takes the most time, and will simplify profiling the boot process. Not sure how much effort is involved, but sounds possible. Any takers?

Written by Id2ndR the 15 Feb 09 at 16:10.

The programs that are loaded just after the login are always the same : gnome-session, gnome-daemons etc.

What take time to load the session is to read them from the hard drive. So as we are sure they will be loaded, we can prefetch them.

This can be extended to user's programs just after he give his name to gdm (so while he is entering his password).

The programs that are loaded just after the login are always the same : gnome-session, gnome-daemons etc. What take time to load the session is to read them from the hard drive. So as we are sure they will be loaded, we can prefetch them. This can be extended to user's programs just after he give his name to gdm (so while he is entering his password).

Written by kleytonn the 2 Mar 08 at 12:40.

Turn fast and light the Gnome enviroment with a fast boot. Today, a login in GDM cost 10 or 20 seconds to load a user desktop in one fast computer.
KDE 4.0.1 is new but is visible more light than Gnome.

Turn fast and light the Gnome enviroment with a fast boot. Today, a login in GDM cost 10 or 20 seconds to load a user desktop in one fast computer. KDE 4.0.1 is new but is visible more light than Gnome.

Written by slsolaris the 23 Mar 09 at 17:11.

gnome is too slow, it need a lot of implrovements, like when u see icons overlap any other, gnome panel bar is not real transparent, and i bring this things in mind just because i can not understand how xfce that does have this features is faster and and lighter...

i mean gnome should work in hand with them and give them things that they already do not have and they could give us some very important help to improve things

gnome is too slow, it need a lot of implrovements, like when u see icons overlap any other, gnome panel bar is not real transparent, and i bring this things in mind just because i can not understand how xfce that does have this features is faster and and lighter... i mean gnome should work in hand with them and give them things that they already do not have and they could give us some very important help to improve things

Written by pioneer the 11 Apr 08 at 10:55.

Ubuntu Brainstorm was updated in January 2009. Since the idea #6833 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #6833 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by puyo the 16 Feb 10 at 12:15.

Whenever default apps are changed in Xfce, KDE or Gnome, the change is made for all three environments, such that apps written for any environment use the newly configured default app.

That way, KDE apps used in Gnome will behave in a predictable way, and vice versa.

Whenever default apps are changed in Xfce, KDE or Gnome, the change is made for all three environments, such that apps written for any environment use the newly configured default app. That way, KDE apps used in Gnome will behave in a predictable way, and vice versa.

Written by edgimar the 2 Dec 10 at 09:38.

The specification described at

http://wiki.lxde.org/en/Desktop_Preferred_Applications_Specification

deals with this problem. Ubuntu should work to ensure that something like this is followed, regardless of which desktop-environment is in use (e.g. KDE, Gnome, LXDE, Xmonad, Fluxbox, etc.).

The specification described at http://wiki.lxde.org/en/Desktop_Preferred_Applications_Specification deals with this problem. Ubuntu should work to ensure that something like this is followed, regardless of which desktop-environment is in use (e.g. KDE, Gnome, LXDE, Xmonad, Fluxbox, etc.).

Written by maltepalte the 18 Sep 08 at 02:51.

Ubuntu Brainstorm was updated in January 2009. Since the idea #13365 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #13365 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!