KDE Desktop Widgets Screen Locker Crashes

Hi,
I'm running KDE 4.11.2 on an Arch x86_64 box. I looked through the KDE bug reports, but I couldn't find a bug filed about this, and I'm confused about where to start looking.
If I use the 'Simple Locker' and lock my screen, everything works wonderfully and as expected. But if I switch to the 'Desktop Widgets' screen locker and lock my screen, everything goes to pieces. The lock screen doesn't show up, and my system freezes.
I'm still able to move my mouse, but everything else is unresponsive, and I can't click on anything. I opened a TTY login to kill the screenlocker, but it wasn't running.
The only thing that worked was rebooting it.
How do I start troubleshooting this?

arojas wrote:
Kitchi wrote:Any idea if it will be fixed/dropped in next releases of KDE?
In KDE4: no, as there will be no more kde-workspace feature releases. For KDE5/Plasma2 (or whatever it will be called) it's all going to be rewritten anyway, so if it survives it will be in a very different form.
Does that include bug fixes? Apologies if that's a stupid question... I have no idea how the KDE releases work.
I guess that answers the question either way... I'm not marking the thread as solved since the issue still persists.
@Box0 - That's the bug... I did check the resolution mentioned, but it matches my screen resolution. So that can't be the problem. I'm thinking that it could be a permission conflict somehow, with the screen locker trying to access some files that have wrong permissions set.

Similar Messages

KDE 4.9 screen lock reveals desktop

Hi,
I've been experiencing a curious problem since I have upgraded to KDE 4.9. At seemingly random times, the locking the desktop shows a static image of my desktop.
I am using the blank screensaver and I didn't notice this with any previous KDE release. I am also using Intel 3000 graphics. Is anyone else having this problem?

Is there a way I can gather any more information on this issue. I feel bad submitting a bug report with just "this feature doesn't work!"
but I guess here goes.
https://bugs.kde.org/show_bug.cgi?id=305270
Last edited by ayr0 (2012-08-16 15:47:21)

How to remove Screen Lock Widget Android 5.0.2?

I think this problem may be specific to Android 5.0.2. because the instructions in the user manual no longer work.
I installed Extended Controls (great app/widget) and it seems to add it's widget to the lock screen (I have the widget on my Home screen but I added that myself). Anyway for some reason I ended up with two identical widgets on my lock screen and they take quite a bit of space. So I decided to remove one of them. I followed the instructions in the manual but found them impossible. I press and hold the widget but can't move it on it's own. It is very difficult to move at all and when it does everything else moves with it. Plus the upward swipe needed to get to the rubbish bin (which never appears anyway) unlocks the phone so I end up on my Home screen and the widget on the lock screen has not been removed.
How can I remove widgets from the lock screen?

QUOTE from the user manual
To add a widget to the lock screen
1 From your Home screen, tap , then find and tap Settings > Security
2 Mark the Allow widgets on lock screen checkbox.
3 To lock the screen, press the power key.
4 To activate the screen, briefly press the power key.
5 Swipe inwards from the upper part of the screen until appears, then tap it.
6 If required, enter your PIN code, pattern or password to unlock the screen.
7 Find and tap the widget that you want to add.
8 Follow the on-screen instructions, if necessary, to finish adding the widget.
The items that appear when you tap are available by default and cannot be modified.
To remove a widget from the lock screen
1 To activate the screen, briefly press the power key .
2 Touch and hold the widget that you want to remove, then drag it to .
The camera icon at the bottom of the screen is there by default and cannot be removed.
This clearly says you can. As I said, it doesn't work. Why not? There's no Allow widgets.on lock screen either. Why not?

Hello - can anyone tell me why my iPad (4th Gen) screen will no longer rotate. I don't have a screen lock symbol next to the battery icon. I have the rotate icon on my desktop but still can't get the screen to rotate.

Hello - can anyone tell me why my iPad (4th Gen) screen will no longer rotate. I don't have a screen lock symbol next to the battery icon. I have the rotate icon on my desktop but still can't get the screen to rotate.

Double-click the Home button and swipe Task Bar to the right. Check the Rotation Lock on the far left of Task Bar.
http://i1224.photobucket.com/albums/ee374/Diavonex/ba23c598623fe4fd062a40e349af2 18d.jpg

Start remote desktop from windows lock screen

Is it possible to invoke remote desktop from the lock screen of a host machine without interfering with any active session on that host machine? The host machine might have been locked by someone who had just walked away from it or the host machine may
be being used remotely by its regular user. But despite this i would like to use it to run a remote session to my regular machine.

Hi,
The answer is no, Lock screen aims to protect user's profile and system resources securitry, Remote desktop need to use system rescoures, such as Printer, Drives, and so on. Therefore, it's impossible to start remote desktop from Widnows lock screen.
Roger Lu
TechNet Community Support

Remove Music Widget on Lock Screen

Since upgrading to 4.3.3 today, I cannot remove the music widget from my lock screen. I've made sure the app is not open, closed all running apps, and restarted my phone. Any suggestions?

If you'd rather not have a Lock on your screen you could go into settings >> security & screen lock, screen lock then choose none.. then when you tap the screen it will be at your home screen..

Screen Lock glitch, shows desktop

I noticed a random problem that has been showing up with the screen locking option. I have it set to lock my screen after about 15 minutes. A few times i've walked back to the computer and when i move my mouse, the windows shows up asking for my password. The glitch is that it doesn't black out the screen! I can still see and use the stuff on my desktop, just the logon window shows up on top! its defiantly a security flaw and a weird problem. i can't seem to recreate it, it just happens randomly. Nothing notable shows up in Console either. Any ideas on how to fix this problem? I lock after 15 minutes and sometimes lock using the Keychain shortcut in the toolbar.
Thanks,
Greg

You could report the issue to Apple by sending feedback.
You could try using a faster loading screen saver like Spectrum or "computer name." Another option might be to use sleep screen instead of screen saver. (System Preferences, Energy Saver, Display Sleep) I
Message was edited by: TeenTitan

System Preferences Crashes When "Desktop and Screen Saver" Selected

Help. My System Preferences crashes shortly after "Desktop and Screen Saver" is selected. I'm running 10.4.10 and the firmware is up to date. I have also repaired the permissions.

This issue is often caused by a plist file which is corrupt or contains an invalid setting. To fix this issue, create a new folder on the desktop and then choose Go to Folder from the Finder's Go menu. Enter ~/Library/Preferences/ByHost/ as the folder's path and drag everything with a name containing com.apple.screensaver to the folder on the desktop. If the issue persists, return to the ByHost folder, press the Command and Up keys simultaneously, and then move the file named com.apple.desktop.plist to the folder you created earlier. If everything works properly with both files in the folder you created, it is safe to throw it away.
(22465)

Desktop Widgets (Windows 7/8 and Mac)

I'd like to see a floaty desktop widget or sidebar similar to what's on Android that just shows current song, play, skip, pause, etc without having to launch the full spotify client.

Ok so small on top window a la itunes is a must for me. i teach guitar and work on a macbook so i need to be able to check arrangements and pause songs whilst i prepare scores. premium users should get a ittle upgrade p thank youath to a small skin always on top thing that lets you pause and play and click next or previous.
seeing as how you guys have sort of cloned and then improved on itunes by making it much more user friendly and cutting edge just take the next step and make a transperent play pause floating bar that can lock to the top of the screen. it could even have a scrolling text to tell you when a new album is released by your favourite artist etc.
Im sure this has been suggested before but it is a must happen thing.
Rock on.
Other tha that i love the new layout and particularely like the playlists with the current top 50 best new pop or whatever style. discovering a whole bunch of new acts and its so eas to use. Thanks!!
martynnorman wrote:
I'd like to see a floaty desktop widget or sidebar similar to what's on Android that just shows current song, play, skip, pause, etc without having to launch the full spotify client.

[Solved] KDE Desktop Effects no longer working

Hello,
I just did an update, (I didn't think it was a major one, I don't recall seeing graphics update, though I'm not sure how to confirm - is there a way to see recently updated packages in yaourt?) and after a brief issue with powertop that was solved by a restart (https://bbs.archlinux.org/viewtopic.php?id=179789 - it may be unrelated though) I found that when I restarted, KWin Crashed, and since then, my desktop effects are not working.
I have gone to the KDE Desktop Effects Settings Menu, and under the advanced menu, set the compositing type back to OpenGL 3.1, clicked apply, and confirmed that I wanted to try it even though it had evidently crashed Kwin. I then received a message stating "21 desktop effects could not be loaded". When I clicked details, a popup window said:
"For technical reasons it is not possible to determine all possible error causes.
Desktop effect system is not running."
For the record, I am on a Thinkpad X201 with intel graphics.
Any ideas?
Last edited by TheGuyWithTheFace (2014-04-19 07:35:43)

Some Extra information:
I just tried a restart, that didn't work.
I then went back into effect settings, and saw that "enable effects at startup" was not checked. I also saw that under the advanced settings, Qt Graphics system was set to raster. Since I'm not sure which it was supposed to be on originally, but the current configuration wasn't working, I also set that to Native, and then clicked apply. KWin then crashed, here is the output:
Application: KWin (kwin), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
To enable execution of this file add
add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.19-gdb.py
line to your configuration file "/home/perry/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/perry/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
[Current thread is 1 (Thread 0x7fafaa788800 (LWP 796))]
Thread 4 (Thread 0x7faf8beb3700 (LWP 797)):
#0 0x00007fafa3f7e3f8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007fafa420a034 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2 0x00007fafa41fd745 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fafa4209b7f in ?? () from /usr/lib/libQtCore.so.4
#4 0x00007fafa3f7a0a2 in start_thread () from /usr/lib/libpthread.so.0
#5 0x00007fafa9fa9d1d in clone () from /usr/lib/libc.so.6
Thread 3 (Thread 0x7faf8b27a700 (LWP 798)):
#0 0x00007fafa3f7e3f8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007fafa420a034 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2 0x00007fafa41fd745 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fafa4209b7f in ?? () from /usr/lib/libQtCore.so.4
#4 0x00007fafa3f7a0a2 in start_thread () from /usr/lib/libpthread.so.0
#5 0x00007fafa9fa9d1d in clone () from /usr/lib/libc.so.6
Thread 2 (Thread 0x7faf8a878700 (LWP 799)):
#0 0x00007fafa9fa2fd3 in select () from /usr/lib/libc.so.6
#1 0x00007fafa42e6c13 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007fafa4209b7f in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fafa3f7a0a2 in start_thread () from /usr/lib/libpthread.so.0
#4 0x00007fafa9fa9d1d in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7fafaa788800 (LWP 796)):
[KCrash Handler]
#5 0x00007fafa9ef9389 in raise () from /usr/lib/libc.so.6
#6 0x00007fafa9efa788 in abort () from /usr/lib/libc.so.6
#7 0x00007fafa9ef24a6 in __assert_fail_base () from /usr/lib/libc.so.6
#8 0x00007fafa9ef2552 in __assert_fail () from /usr/lib/libc.so.6
#9 0x00007fafa7d6f8d9 in ?? () from /usr/lib/libX11.so.6
#10 0x00007fafa7d6f96e in ?? () from /usr/lib/libX11.so.6
#11 0x00007fafa7d6fc4d in _XEventsQueued () from /usr/lib/libX11.so.6
#12 0x00007fafa7d72905 in _XGetRequest () from /usr/lib/libX11.so.6
#13 0x00007fafa4dfe587 in ?? () from /usr/lib/libGL.so.1
#14 0x00007fafa4dfbf6b in ?? () from /usr/lib/libGL.so.1
#15 0x00007faf89bef6db in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#16 0x00007faf89befa33 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#17 0x00007faf89befb8b in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#18 0x00007faf89b89ef6 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#19 0x00007fafa4dfd898 in ?? () from /usr/lib/libGL.so.1
#20 0x00007fafa4dd804c in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1
#21 0x00007fafaa34e479 in ?? () from /usr/lib/libkdeinit4_kwin.so
#22 0x00007fafaa350029 in ?? () from /usr/lib/libkdeinit4_kwin.so
#23 0x00007fafaa34aefc in ?? () from /usr/lib/libkdeinit4_kwin.so
#24 0x00007fafaa32f4b5 in ?? () from /usr/lib/libkdeinit4_kwin.so
#25 0x00007fafaa2b6c75 in ?? () from /usr/lib/libkdeinit4_kwin.so
#26 0x00007fafa431d6ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#27 0x00007fafa41fa958 in QFutureWatcherBase::event(QEvent*) () from /usr/lib/libQtCore.so.4
#28 0x00007fafa3491f0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#29 0x00007fafa34984d0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#30 0x00007fafa8bfa88a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#31 0x00007fafa4309a6d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#32 0x00007fafa430caad in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#33 0x00007fafa352f71c in ?? () from /usr/lib/libQtGui.so.4
#34 0x00007fafa43086cf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0x00007fafa43089c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0x00007fafa430dae9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#37 0x00007fafaa2e7896 in kdemain () from /usr/lib/libkdeinit4_kwin.so
#38 0x00007fafa9ee5b05 in __libc_start_main () from /usr/lib/libc.so.6
#39 0x00000000004006fe in _start ()

Windows 8.1 Lock Screen drops network connectivity when screen locked using Win+L

Hi!
I was sent here from Microsoft Community forum. The question is:
Since Windows NT 4.0 I'm using Lock Screen to prevent people from accessing my computer when I'm leaving my room. First I was using CTRL+ALT+DEL / Lock Screen, then switched to Win+L keyboard shortcut when it was first introduced.
Everything was fine until I switched to Windows 8.1 computer (Sony Vaio Duo 13 with Broadcom wireless network controller). This machine is 8.1, not 8.0 upgraded to 8.1.
My problem is that when I hit Win+L combo the Lock Screen (with clock etc.) is displayed. Then, despite I have configured not to turn off display, the screen goes blank (after 30 seconds since lock) and network connectivity is cut off from desktop
apps (I suspect the system goes into Active Standby mode, because Modern UI apps like Tune-In radio keep working fine).
100% repeatable scenarios:
## Scenario 1 ##
1) Log in
2) Open desktop app that uses network connectivity. Outlook 2013 from Office365 subscription
3) Check that it has connected
4) Lock screen (Win+L)
5) Wait for 30 seconds (first incorrectly posted as few minutes) as screen goes black
6) Unlock screen (using password)
7) In right corner of Outlook app you will see "Unable to connect with Exchange server" and few seconds later it will reconnect sucessfuly
## Scenario 2 - the more annoying ##
1) Log in to Win 8.1 computer
2) Connect to it using SMB (in my case I wanted to transfer 30 GB of files from local hard drive C: to server) \\COMPUTER-NAME\c$ from Windows Server 2012 R2
3) Start copying files from computer to server
4) Lock the screen on computer
5) As soon as screen goes black server displays message "Lost connection to the resource. Try again?"
6) Unlock screen on the computer
7) Click "Try again" and it will continue copying files
My power settings are set to go into stand by after 5 hours and if I not lock the screen it doesn't go to sleep before 5 hours.
When I lock the screen using Win+L it goes into (probably Active) Standby mode.
Is there any way to prevent it from going to Active Standby when locking screen? I need the screen lock for security reasons but I don't want it to drop my network connectivity on remote desktops, file transfers and other desktop activities before 5 hour
timeout.
This issue is not related to more or less known wireless network connectivity problem that happens to many Intel Haswell computers. Mine doesn't exhibit those problems. I can easly push 100 - 200 GB of wireless data without network drops.
Computer information:
Sony Vaio Duo 13: SVD1322C5E
Intel Core i5-4200U
8 GB RAM
Windows 8.1 Pro 64-bit
Broadcom 802.11n SDIO network adapter
Originally posted at: http://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/windows-81-lock-screen-drops-network-connectivity/099f16bd-b00d-4ba9-b833-48bf1d55ffe4
Best regards,
Sergiusz

Same issue here using Surface 3 Pro with either internal WLAN or MS USB LAN Adapter. I'm frequently used to keep open connections over SSH to some servers. On switching to lock screen explicitly by pressing Win+L or implicitly due to idle timeout all
connections to servers are lost. In addition, I don't get any notifications on incoming Skype messages (using Skype for desktop) when lock screen is active.
Neither NIC is showing "Power Management Tab" according to step 5 of instructions above.
Additionally observing USB LAN NIC seems to be kept active after activating lock screen, but traffic stops (according to its flashing light) when lock screen is switching off display. Blanking display doesn't seem to be adjustable in System Settings (Energy
Options accessed through Win+X).
Find attached log file of powercfg -energy -duration 300 ...
Log file is in German. It basically claims unset timeouts for deactivating display while running attached to power supply though lock screen is turning off displays within 1-2 minutes.
Energieeffizienzdiagnose-Bericht
Computername
KRITIAS
Überprüfungszeit
2015-01-10T15:07:47Z
Überprüfungsdauer
353 Sekunden
Systemhersteller
Microsoft Corporation
Systemproduktname
Surface Pro 3
BIOS-Datum
10/16/2014
BIOS-Version
3.11.0350
Betriebssystembuild
9600
Plattformrolle
PlatformRoleSlate
Netzbetrieb
true
Prozessanzahl
67
Threadanzahl
1319
Berichts-GUID
{1a168801-c189-46fe-811c-235e6bf2bd0d}
Analyseergebnisse
Fehler
Energierichtlinie:Verdunkelungszeitlimit ist deaktiviert (Netzbetrieb)
Der Bildschirm ist nicht so konfiguriert, dass er nach einer Zeit der Inaktivität verdunkelt wird.
Energierichtlinie:Standbyzeitlimit ist deaktiviert (Netzbetrieb)
Der Computer ist nicht so konfiguriert, dass nach einer Zeit der Inaktivität automatisch der Wechsel in den Standbymodus erfolgt.
CPU-Auslastung:Prozessorauslastung ist hoch
Die durchschnittliche Prozessorauslastung während der Ablaufverfolgung war sehr hoch. Das System verbraucht weniger Energie, wenn die durchschnittliche Prozessorauslastung sehr niedrig ist. Überprüfen Sie die Prozessorauslastung für einzelne Prozesse,
um festzustellen, welche Anwendungen und Dienste den größten Anteil an der Gesamtprozessorauslastung haben.
Durchschnittliche Auslastung (%)
45.31
Warnungen
Plattform-Zeitgeberauflösung:Plattform-Zeitgeberauflösung
Die standardmäßige Plattform-Zeitgeberauflösung beträgt 15,6 ms (15625000 ns) und sollte immer dann verwendet werden, wenn sich das System im Leerlauf befindet. Wenn die Zeitgeberauflösung erhöht wird, sind die Technologien zur Prozessorenergieverwaltung
möglicherweise nicht wirksam. Die erhöhte Zeitgeberauflösung kann auf eine Multimediawiedergabe oder Grafikanimationen zurückzuführen sein.
Aktuelle Zeitgeberauflösung (100-ns-Einheiten)
10007
Maximale Zeitgeberperiode (100-ns-Einheiten)
156250
Plattform-Zeitgeberauflösung:Ausstehende Zeitgeberanforderung
Von einem Programm oder Dienst wurde eine Zeitgeberauflösung angefordert, die kleiner als die maximale Zeitgeberauflösung der Plattform ist.
Angeforderter Zeitraum
10000
ID des anfordernden Prozesses
3476
Pfad des anfordernden Prozesses
\Device\HarddiskVolume4\Program Files (x86)\Adobe\Adobe Creative Cloud\ACC\Creative Cloud.exe
Energierichtlinie:Bildschirmzeitlimit ist lang (Netzbetrieb)
Der Bildschirm ist so konfiguriert, dass er nach mehr als 10 Minuten Inaktivität ausgeschaltet wird.
Zeitlimit (Sekunden)
900
USB-Standbymodus:Vom USB-Gerät wird nur selten in den Modus für selektives Energiesparen gewechselt.
Von diesem Gerät wurde während der Ablaufverfolgung nur unregelmäßig in den Modus für selektives Energiesparen gewechselt. Die Prozessorenergieverwaltung ist möglicherweise nicht möglich, wenn sich dieses USB-Gerät nicht im Modus für selektives Energiesparen
befindet. Dieses Problem verhindert jedoch nicht den Wechsel des Systems in den Standbymodus.
Gerätename
USB-Verbundgerät
Hostcontroller-ID
PCI\VEN_8086&DEV_9C31
Hostcontrollerspeicherort
PCI bus 0, device 20, function 0
Geräte-ID
USB\VID_05AC&PID_0250
Portpfad
1,2
Standbydauer (%)
14
USB-Standbymodus:Vom USB-Gerät wird nur selten in den Modus für selektives Energiesparen gewechselt.
Von diesem Gerät wurde während der Ablaufverfolgung nur unregelmäßig in den Modus für selektives Energiesparen gewechselt. Die Prozessorenergieverwaltung ist möglicherweise nicht möglich, wenn sich dieses USB-Gerät nicht im Modus für selektives Energiesparen
befindet. Dieses Problem verhindert jedoch nicht den Wechsel des Systems in den Standbymodus.
Gerätename
Surface Ethernet Adapter
Hostcontroller-ID
PCI\VEN_8086&DEV_9C31
Hostcontrollerspeicherort
PCI bus 0, device 20, function 0
Geräte-ID
USB\VID_045E&PID_07AB
Portpfad
1,1
Standbydauer (%)
5
USB-Standbymodus:Vom USB-Gerät wird nur selten in den Modus für selektives Energiesparen gewechselt.
Von diesem Gerät wurde während der Ablaufverfolgung nur unregelmäßig in den Modus für selektives Energiesparen gewechselt. Die Prozessorenergieverwaltung ist möglicherweise nicht möglich, wenn sich dieses USB-Gerät nicht im Modus für selektives Energiesparen
befindet. Dieses Problem verhindert jedoch nicht den Wechsel des Systems in den Standbymodus.
Gerätename
Generischer USB-Hub
Hostcontroller-ID
PCI\VEN_8086&DEV_9C31
Hostcontrollerspeicherort
PCI bus 0, device 20, function 0
Geräte-ID
USB\VID_05AC&PID_1006
Portpfad
1
Standbydauer (%)
5
USB-Standbymodus:Vom USB-Gerät wird nur selten in den Modus für selektives Energiesparen gewechselt.
Von diesem Gerät wurde während der Ablaufverfolgung nur unregelmäßig in den Modus für selektives Energiesparen gewechselt. Die Prozessorenergieverwaltung ist möglicherweise nicht möglich, wenn sich dieses USB-Gerät nicht im Modus für selektives Energiesparen
befindet. Dieses Problem verhindert jedoch nicht den Wechsel des Systems in den Standbymodus.
Gerätename
USB-Eingabegerät
Hostcontroller-ID
PCI\VEN_8086&DEV_9C31
Hostcontrollerspeicherort
PCI bus 0, device 20, function 0
Geräte-ID
USB\VID_045E&PID_0797
Portpfad
1,3
Standbydauer (%)
14
CPU-Auslastung:Einzelner Prozess mit erheblicher Prozessorauslastung
Auf diesen Prozess ist ein erheblicher Anteil der Gesamtprozessorauslastung zurückzuführen, die während der Ablaufverfolgung aufgezeichnet wurde.
Prozessname
firefox.exe
PID
5968
Durchschnittliche Auslastung (%)
1.57
Modul
Durchschnittliche Modulauslastung (%)
\Device\HarddiskVolume4\Program Files (x86)\Mozilla Firefox\xul.dll
0.60
\Device\HarddiskVolume4\Program Files (x86)\Mozilla Firefox\mozjs.dll
0.27
\SystemRoot\system32\ntoskrnl.exe
0.16
CPU-Auslastung:Einzelner Prozess mit erheblicher Prozessorauslastung
Auf diesen Prozess ist ein erheblicher Anteil der Gesamtprozessorauslastung zurückzuführen, die während der Ablaufverfolgung aufgezeichnet wurde.
Prozessname
System
PID
4
Durchschnittliche Auslastung (%)
0.59
Modul
Durchschnittliche Modulauslastung (%)
\SystemRoot\system32\ntoskrnl.exe
0.24
\SystemRoot\system32\DRIVERS\igdkmd64.sys
0.12
\SystemRoot\system32\DRIVERS\avc3.sys
0.07
CPU-Auslastung:Einzelner Prozess mit erheblicher Prozessorauslastung
Auf diesen Prozess ist ein erheblicher Anteil der Gesamtprozessorauslastung zurückzuführen, die während der Ablaufverfolgung aufgezeichnet wurde.
Prozessname
dwm.exe
PID
6264
Durchschnittliche Auslastung (%)
0.47
Modul
Durchschnittliche Modulauslastung (%)
\SystemRoot\system32\ntoskrnl.exe
0.10
\Device\HarddiskVolume4\Windows\System32\dwmcore.dll
0.09
\SystemRoot\System32\drivers\dxgkrnl.sys
0.06
CPU-Auslastung:Einzelner Prozess mit erheblicher Prozessorauslastung
Auf diesen Prozess ist ein erheblicher Anteil der Gesamtprozessorauslastung zurückzuführen, die während der Ablaufverfolgung aufgezeichnet wurde.
Prozessname
Skype.exe
PID
11008
Durchschnittliche Auslastung (%)
0.26
Modul
Durchschnittliche Modulauslastung (%)
\Device\HarddiskVolume4\Program Files (x86)\Skype\Phone\Skype.exe
0.11
\SystemRoot\system32\ntoskrnl.exe
0.05
\SystemRoot\System32\win32k.sys
0.04
CPU-Auslastung:Einzelner Prozess mit erheblicher Prozessorauslastung
Auf diesen Prozess ist ein erheblicher Anteil der Gesamtprozessorauslastung zurückzuführen, die während der Ablaufverfolgung aufgezeichnet wurde.
Prozessname
svchost.exe
PID
1528
Durchschnittliche Auslastung (%)
0.25
Modul
Durchschnittliche Modulauslastung (%)
\SystemRoot\system32\ntoskrnl.exe
0.16
\Device\HarddiskVolume4\Windows\System32\ntdll.dll
0.02
\SystemRoot\system32\drivers\ndis.sys
0.01
Informationen
Plattform-Zeitgeberauflösung:Zeitgeberanforderungsstapel
Der Stapel mit den Modulen, die für die niedrigste Plattform-Zeitgebereinstellung in diesem Prozess verantwortlich sind.
Angeforderter Zeitraum
10000
ID des anfordernden Prozesses
3476
Pfad des anfordernden Prozesses
\Device\HarddiskVolume4\Program Files (x86)\Adobe\Adobe Creative Cloud\ACC\Creative Cloud.exe
Aufrufender Modulstapel
\Device\HarddiskVolume4\Windows\SysWOW64\ntdll.dll
\Device\HarddiskVolume4\Windows\SysWOW64\kernel32.dll
\Device\HarddiskVolume4\Windows\SysWOW64\d3d9.dll
\Device\HarddiskVolume4\Program Files (x86)\Adobe\Adobe Creative Cloud\CEF\libcef.dll
\Device\HarddiskVolume4\Windows\SysWOW64\kernel32.dll
\Device\HarddiskVolume4\Windows\SysWOW64\ntdll.dll
Energierichtlinie:Aktiver Energieplan
Der derzeit verwendete Energieplan.
Planname
Ausbalanciert (OEM)
Plan-GUID
{381b4222-f694-41f0-9685-ff5bb260df2e}
Energierichtlinie:Energieplancharakter (Akkubetrieb)
Der Charakter des aktuellen Energieplans, wenn das System im Akkubetrieb ausgeführt wird.
Charakter
Ausbalanciert
Energierichtlinie:Videoqualität (Akkubetrieb)
Ermöglicht Windows Media Player, bei der Videowiedergabe die Qualität und die Energieeinsparung zu optimieren.
Qualitätsmodus
Videoqualität und Energieeinsparung ausbalancieren
Energierichtlinie:Energieplancharakter (Netzbetrieb)
Der Charakter des aktuellen Energieplans, wenn das System im Netzbetrieb ausgeführt wird.
Charakter
Ausbalanciert
Energierichtlinie:802.11-Energierichtlinie für Drahtlosverbindungen ist "Maximale Leistung" (Netzbetrieb)
Die aktuelle Energierichtlinie für 802.11-kompatible Drahtlosnetzwerkadapter ist nicht für die Verwendung von Energiesparmodi konfiguriert.
Energierichtlinie:Videoqualität (Netzbetrieb)
Ermöglicht Windows Media Player, bei der Videowiedergabe die Qualität und die Energieeinsparung zu optimieren.
Qualitätsmodus
Für hohe Videoqualität optimieren
Systemverfügbarkeitsanforderungen:Erfolgreiche Analyse
Die Analyse war erfolgreich. Es wurden keine Energieeffizienzprobleme festgestellt und keine Informationen zurückgegeben.
Akku:Akkuinformationen
Akku-ID
1F11LGC_LGCX863568
Hersteller
LGC_LGC
Seriennummer
1F11
Chemie
LION
Langfristig
1
Versiegelt
0
Zyklusanzahl
33
Vorgesehene Akkukapazität
42157
Letzte vollständige Aufladung
44209
Funktionen der Plattformenergieverwaltung:Unterstützte Standbystatus
Mithilfe von Standbystatus kann der Computer nach einer Zeit der Inaktivität in einen Energiesparmodus wechseln. Der S3-Standbystatus ist der standardmäßige Standbystatus für Windows-Plattformen. Im S3-Standbystatus verbraucht der Computer nur die Energie,
die notwendig ist, um den Arbeitsspeicherinhalt zu bewahren und die Arbeit mit dem Computer schnell fortsetzen zu können. Sehr wenige Plattformen unterstützen den S1- oder S2-Standbystatus.
S1-Standbymodus unterstützt
false
S2-Standbymodus unterstützt
false
S3-Standbymodus unterstützt
false
S4-Standbymodus unterstützt
true
Funktionen der Plattformenergieverwaltung:Unterstützung von Verbindungsstandby
Mit dem Verbindungsstandby kann der Computer in einen Stromsparmodus wechseln, in dem er immer eingeschaltet und verbunden ist. Der Verbindungsstandby wird soweit unterstützt anstelle der Systemstandbystatus verwendet.
Verbindungsstandby unterstützt
true
Funktionen der Plattformenergieverwaltung:Die adaptive Bildschirmhelligkeit wird unterstützt.
Dieser Computer ermöglicht die automatische Helligkeitsregelung der integrierten Anzeige durch Windows.
Funktionen der Plattformenergieverwaltung:Funktionen zur Prozessorenergieverwaltung
Mithilfe einer effektiven Prozessorenergieverwaltung kann der Computer Leistung und Energieverbrauch automatisch ausbalancieren.
Gruppieren
0
Index
0
Leerlaufstatus - Anzahl
11
Leerlaufstatustyp
Micro-Energiemodul-Plug-In
Nennfrequenz (MHz)
2301
Prozentuale maximale Leistung
100
Prozentuale niedrigste Leistung
32
Prozentuale niedrigste Drosselung
3
Leistungssteuerelementtyp
ACPI-Leistungszustände (P)/ACPI-Drosselungszustände (T)
Funktionen der Plattformenergieverwaltung:Funktionen zur Prozessorenergieverwaltung
Mithilfe einer effektiven Prozessorenergieverwaltung kann der Computer Leistung und Energieverbrauch automatisch ausbalancieren.
Gruppieren
0
Index
1
Leerlaufstatus - Anzahl
11
Leerlaufstatustyp
Micro-Energiemodul-Plug-In
Nennfrequenz (MHz)
2301
Prozentuale maximale Leistung
100
Prozentuale niedrigste Leistung
32
Prozentuale niedrigste Drosselung
3
Leistungssteuerelementtyp
ACPI-Leistungszustände (P)/ACPI-Drosselungszustände (T)
Funktionen der Plattformenergieverwaltung:Funktionen zur Prozessorenergieverwaltung
Mithilfe einer effektiven Prozessorenergieverwaltung kann der Computer Leistung und Energieverbrauch automatisch ausbalancieren.
Gruppieren
0
Index
2
Leerlaufstatus - Anzahl
11
Leerlaufstatustyp
Micro-Energiemodul-Plug-In
Nennfrequenz (MHz)
2301
Prozentuale maximale Leistung
100
Prozentuale niedrigste Leistung
32
Prozentuale niedrigste Drosselung
3
Leistungssteuerelementtyp
ACPI-Leistungszustände (P)/ACPI-Drosselungszustände (T)
Funktionen der Plattformenergieverwaltung:Funktionen zur Prozessorenergieverwaltung
Mithilfe einer effektiven Prozessorenergieverwaltung kann der Computer Leistung und Energieverbrauch automatisch ausbalancieren.
Gruppieren
0
Index
3
Leerlaufstatus - Anzahl
11
Leerlaufstatustyp
Micro-Energiemodul-Plug-In
Nennfrequenz (MHz)
2301
Prozentuale maximale Leistung
100
Prozentuale niedrigste Leistung
32
Prozentuale niedrigste Drosselung
3
Leistungssteuerelementtyp
ACPI-Leistungszustände (P)/ACPI-Drosselungszustände (T)
Gerätetreiber:Erfolgreiche Analyse
Die Analyse war erfolgreich. Es wurden keine Energieeffizienzprobleme festgestellt und keine Informationen zurückgegeben.

KDE desktop does not come up after log out

I have updated KDE to the lastest version using the Arch packages. It worked wonderfully the first time, all of my widgits were intact and my desktop was just as I had left it, custom background and everything. Then, however, I logged out to make sure Fluxbox worked. Now, even after rebooting, the KDE desktop doesn't come up. It will bring up Pidgin which was running before but the taskbar and all of the widgets are gone and it has this grey background that is the same as the one in the KDM.
No errors are produced, although it does now ask for the password for a Wallet that "Plasma Desktop" wants to access. I recognise the name of the wallet (kdewallet) and input the password correctly after this, two notifications pop up with informational thing. One is about some indexing service being "rebuilt" for new features and the other is saying that it's falling back on a different sound output. None of this seems to have an impact on the limited usability I have.
Has anyone else expereinced this? Are there any log files where errors would be outputted to?
Any help would be appreciated.
Thanks in advance.

I have found the relevent messages. They are at a pastebin. http://pastebin.ca/1522805
I'm not entirely sure what is going on here.
After the top line of that post, there are a LOT of errors related to "No block with decorrelation terms" in fact the vast majority of that file are those things. All other "errors" are warnings related to my Fluxbox session which is working fine.
Lines 1, 11 and 12 seem to be the most severe errors:
[0xa2412b0] main input error: ES_OUT_RESET_PCR called
"/usr/bin/dolphin(4560)" Error in thread 3049428752 : "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files"
"/usr/bin/dolphin(4560)" Error in thread 3049428752 : "QLocalSocket::connectToServer: Invalid name"
I have no idea where to even begin fixing them. However it is Nepomuk that comes up with the rebuilding message i mentioned in my previous post.
Last edited by guitarMan666 (2009-08-09 10:10:05)

Windows 2008 R2 Screen Lock Issue (GPO)

Scenario: We will be deploying POS machines at our stores that will have Windows 2008 R2 as the preferred OS. The function of this POS machine is for POS administration and not for ringing up sales. The machines have been configured to autologin a specific
user via GPO for POS functions. Also, a specific POS desktop environment shell has been configured to launch instead of Explorer (explorer.exe) shell environment at autologon.
Everything seems to be working as expected except for the session of the user locking. Since the POS environment needs to be up at all times with the specific user profile, we do not want the OS to lock the user session. I've timed it and it seems to lock
the screen (not log off) at approximately 15 minutes of inactivity, we do not want this.
So far, these are the GPOs I have configured that have not fixed the issue:
Computer Configuration>Policies>Windows Settings>Security Settings>Local Policies>Security Options>Microsoft Network Server: Amount of idle time required before suspending session = 99999 minutes
Computer Configuration>Policies>Administrative Templates>System>Power Management>Sleep Settings>Allow applications to prevent automatic sleep (plugged in) = Enabled
Computer Configuration>Policies>Administrative Templates>System>Power Management>Sleep Settings>Require a password when a computer wakes (plugged in) = Disabled
Computer Configuration>Policies>Administrative Templates>System>Power Management>Sleep Settings>Turn off hybrid sleep (plugged in) = Enabled
Computer Configuration>Policies>Administrative Templates>System>Power Management>Sleep Settings>Turn on the ability for applications to prevent sleep transitions (plugged in) = Enabled
Computer Configuration>Policies>Administrative Templates>System>Power Management>Video and Display Settings>Turn off the display (plugged in) = Enabled = 99999 seconds
User Configuration>Policies>Administrative Templates>Control Panel>Personalization>Enable screen saver = Disabled
User Configuration>Policies>Administrative Templates>Control Panel>Personalization>Password protect the screen saver = Disabled
User Configuration>Policies>Administrative Templates>System>Ctrl+Alt+Del Options>Remove Lock Computer = Enabled
User Configuration>Preferences>Windows Settings>Registry>HKCU>Control Panel>Desktop>ScreenSaveActive = 0
What are we doing wrong? How do I configure the OS to not lock the user session but keep it active at all times?
As a side note: We have Windows 7 POS machines also that will be ringing up sales that we do not have the screen lock issue.

Hi,
>>Please see my setting indicated in my original post. We have Turn Off the Display set to 99999 seconds.
I understand that we have set the Turn Off the Display for this amount of time. However, just for double check, we can go to the power plan we are using to check if the setting has been applied successfully. If the setting has been applied successfully,
it should be grayed out. Or, we can run command gpresult/h gpreport.html
with admin privileges to collect group policy result report to check this.
Besides, do we use other third party software to protect our computer? We can try to clean boot the server to see if the situation persists.
Regarding how to perform a clean boot, the following article can be referred to for more information.
How to perform a clean boot in Windows
http://support.microsoft.com/KB/929135
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Best regards,
Frank Shen

Plasma 5 screen lock

There seems to be no way to disable screen locking in the new Plasma 5 interface. The System Settings section for screen locking only allows a max value of 99 min and there is no section for disabling screen locking altogether.
Does anyone know of a method to completely disable screen locking?

It's not possible to enter "Never" there, it's a counter field. I wonder what KDE devs were thinking when they introduced screen locking that it's not possible to disable.
It changes to 0 automatically when you input 0, so that should solve this.
Last edited by perk11 (2015-05-02 14:11:15)

Screen lock activating immediately instead of waiting for inactivity

I have activated Screen Lock so that it requires a password when waking from sleep after 1 hour of inactivity. The problem is that it requires the password immediately no matter how long the computer has been inactive. Screen lock seems to not be waiting the proper time before activating. There must be some sort of bug because anytime the screen lock activates sooner than the selected 1 hour, all i have to do is hit the cancel (X) button at the bottom of the lock screen and my display will go back to sleep and then moving the cursor will wake the computer without requiring password...So Weird!

Screen Lock is not related to inactivity. It is realted to Sleep or Screen Saver starting. So if the Mac is put to sleep, or the Screen Saver is activated, then you will need to enter your password to unlock the screen.
In System Preferences -> Security -> General you can specify a delay after Screen Saver or Sleep is started before the password is required, in case the screen saver starts and you quickly move the mouse to kill it. I use 5 seconds. But this is not idle related, just start of sleep or start of screen saver.
System Preferences -> Desktop & Screen Saver allows you to specify when to start after the system has been idle/inactive.
It is possible you have used mixed terms which are confusing me, so if you could clarify, that would be helpful.

KDE Desktop Widgets Screen Locker Crashes

Similar Messages

Maybe you are looking for