![]() ![]() Ubuntu Installation :: Adjust The Default Setting Via /etc/default/grub?.Fedora Hardware :: Setting Correct Default Permissions On /dev/parport*.Fedora :: Setting Default Browser From Terminal Command?.Fedora :: Can Computer Be Hacked When The Firewall Is In The Default Setting.Fedora :: How To Set Xscreensaver As Default.How to set xscreensaver as default I just enjoy xscreensaver, but I like to have it as default, when f12 start. But as already mentioned, this is bug#224200, which is still open.Red Hat / Fedora :: Setting The Xscreensaver As Default? Feb 6, 2010 > changed from what it was in earlier versions of KDE. > Hence there are still problems with the Screen Saver and the behaviour has > screen saver processes increase and can use up 50% processing power on an 8 > extended period of time with repeated breaks in activity, the number of > and continue to consume processing power. > that when I restore the desktop, the screen saver processes are still active > Currently with a Screen Locker Setting > Screen Saver set to Random, I find My commit turns off session management in libkscreensaver's startup code, but apparently kswarm.kss doesn't use libkscreensaver. > logout did not startup again after login with the exception of kswarm.kss. > After installing KDE 4.12.2, I found that the. >M +3 -0 kscreensaver/libkscreensaver/main.cpp >screensaver windows from popping up on login if processes were still >This patch disables session management for screensavers to prevent >disable session management for screensavers >Pushed by wbauer into branch 'KDE/4.11'. ![]() Please fix the cause and not only the symptoms. Every day or two I need to run a 'killall'! my office pc has usually an uptime of 20+ days. On desktops this might be for days and weeks. This wont solve the bug but only masquerade it.Īnd its really annoying having tons of bg processes eating up resources for as long as you're logged in. #6 0x00007fedb99ec9ef in QEventLoop::processEvents flags=.) at kernel/qeventloop.cpp:149 #5 0x00007fedb8e37c1e in QGuiEventDispatcherGlib::processEvents ( #4 0x00007fedb9a1c1f6 in QEventDispatcherGlib::processEvents (this=0x1dd0710,įlags=.) at kernel/qeventdispatcher_glib.cpp:426 I could reproduce with kswarm.kss as well. #9 0x00007f8513ef4a4a in kScreenSaverMain (argc=,Īt /usr/src/debug/kde-workspace-4.10.2/kscreensaver/libkscreensaver/main.cpp:228 #6 0x00007f85136c39ef in QEventLoop::processEvents flags=.) at kernel/qeventloop.cpp:149 This=, flags=.) at kernel/qguieventdispatcher_glib.cpp:204 #5 0x00007f8512b0ec1e in QGuiEventDispatcherGlib::processEvents ( #2 g_main_context_iterate self=) at gmain.c:3285 (Running on openSUSE 12.3 here, with KDE 4.10.2 and Qt 4.8.4) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |