Changeset View
Changeset View
Standalone View
Standalone View
ksmserver/README
Show First 20 Lines • Show All 70 Lines • ▼ Show 20 Line(s) | |||||
71 | always loaded by kded, even outside of KDE session. It should used only | 71 | always loaded by kded, even outside of KDE session. It should used only | ||
72 | by kded modules which must be always running. Kded phase 1 modules are | 72 | by kded modules which must be always running. Kded phase 1 modules are | ||
73 | loaded right after kded startup, but only during KDE startup, i.e. it is | 73 | loaded right after kded startup, but only during KDE startup, i.e. it is | ||
74 | for modules that are always needed by the KDE session. Phase 2 modules | 74 | for modules that are always needed by the KDE session. Phase 2 modules | ||
75 | will be loaded later. [More information about kded modules could be | 75 | will be loaded later. [More information about kded modules could be | ||
76 | found in kdelibs/kded/HOWTO] | 76 | found in kdelibs/kded/HOWTO] | ||
77 | 77 | | |||
78 | Startkde also launches kcminit, which performs initialization done by kcontrol | 78 | Startkde also launches kcminit, which performs initialization done by kcontrol | ||
79 | modules. There are three kcminit phases, 0, 1 and 2, controlled | 79 | modules. There are two kcminit phases, 0, 1, controlled | ||
80 | by X-KDE-Init-Phase= in the .desktop file, which defaults to 1. Phase 0 kcminit | 80 | by X-KDE-Init-Phase= in the .desktop file, which defaults to 1. Phase 0 kcminit | ||
81 | modules should be only those that really need to be run early in the startup | 81 | modules should be only those that really need to be run early in the startup | ||
82 | process (and those should probably actually use kstartupconfig in startkde | 82 | process (and those should probably actually use kstartupconfig in startkde | ||
83 | to be done even before kdeinit and daemons). After executing phase 0 | 83 | to be done even before kdeinit and daemons). After executing phase 0 | ||
84 | modules kcminit returns and waits. | 84 | modules kcminit returns and waits. | ||
85 | 85 | | |||
86 | When ksmserver is launched, the first thing it does is launching | 86 | When ksmserver is launched, the first thing it does is launching | ||
87 | the window manager, as the WM is necessary before any windows are possibly | 87 | the window manager, as the WM is necessary before any windows are possibly | ||
Show All 12 Lines | |||||
100 | i.e. launching normal components of KDE that should be available right | 100 | i.e. launching normal components of KDE that should be available right | ||
101 | after KDE startup, and after this session restore is performed, | 101 | after KDE startup, and after this session restore is performed, | ||
102 | i.e. launching all applications that were running during last session | 102 | i.e. launching all applications that were running during last session | ||
103 | saving (usually logout). | 103 | saving (usually logout). | ||
104 | 104 | | |||
105 | By this time KDE session is considered to be more or less ready and | 105 | By this time KDE session is considered to be more or less ready and | ||
106 | ksmserver does the knotify startkde event (i.e. plays the login sound). | 106 | ksmserver does the knotify startkde event (i.e. plays the login sound). | ||
107 | It also tells klauncher to perform autostart phase 2, kded to load all | 107 | It also tells klauncher to perform autostart phase 2, kded to load all | ||
108 | remaining autoload (i.e. kded phase 2) modules, kcminit to execute | 108 | remaining autoload (i.e. kded phase 2) modules, and it itself executes | ||
109 | kcminit phase 2 (kcontrol modules that do initialization that can wait, | 109 | the user Autostart folder. | ||
110 | like launching daemons) and it itself executes the user Autostart folder. | | |||
111 | 110 | | |||
112 | Technical note: There's a reason why kded modules and items in autostart | 111 | Technical note: There's a reason why kded modules and items in autostart | ||
113 | default to the latest phase. Before you explicitly use a different phase, | 112 | default to the latest phase. Before you explicitly use a different phase, | ||
114 | read and understand what's above. You should also consider whether something | 113 | read and understand what's above. You should also consider whether something | ||
115 | really needs to be launched during KDE startup and can't be loaded on-demand | 114 | really needs to be launched during KDE startup and can't be loaded on-demand | ||
116 | when really needed. Abusing the phases will result in public spanking | 115 | when really needed. Abusing the phases will result in public spanking | ||
117 | for making KDE startup slower. | 116 | for making KDE startup slower. | ||
118 | 117 | | |||
▲ Show 20 Lines • Show All 44 Lines • Show Last 20 Lines |