KDE responsiveness issues after laptop suspend

jdoggsc · 2014-01-04 14:37:45

Ok I had to think for probably a minute how I wanted to label this thread because I can't concisely summarize the symptoms I'm having.

Everything is normal after a fresh reboot, and sometimes after closing my laptop lid and sleeping a few times, but eventually, it's always the same. the problems eventually start after resuming from standby.

my KDE shortcut key don't work (ctrl+alt+t to open konsole)
editing/changing panels or editing an Activity makes KDE pause for a minute or so at a time, but eventually does what I told it to do.
When using a program (kate, for instance) and trying to open an "open" or "save" dialog box, it freezes, again, for a minute or so, but will eventually respond until I press "Save" or "OK" to close the box. At that point, it will freeze again for about a minute and then continue.
When closing my laptop lid (Dell Latitude E6500) it won't suspend.
- When trying to open "Power Management" in System Settings, system settings freezes and won't ever open the Power Management
When choosing "Shut down" or "Restart" from the KDE menu, it does nothing for about a minute, but will eventually show the dialog to proceed with the shutdown or restart./
When choosing "sleep" from the KDE menu, it won't ever do anything.

This isn't an exhaustive list, but it's already long enough. I'm able to shut down and reboot from the CLI, but the other problems are annoying enough.
I wish I remembered what I updated/installed before I started noticing this, but I don't.

dmesg: after one of these events:

   10.178864] hid-generic 0003:413C:8158.0005: input,hidraw3: USB HID v1.11 Mouse [HID 413c:8158] on usb-0000:00:1a.0-1.2/input0                                                   
[   10.361779] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af:                                                                                                         
[   10.363526]  clean.                                                                                                                                                              
[   10.363547] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff:                                                                                                         
[   10.364184]  excluding 0x4d0-0x4d7                                                                                                                                               
[   10.364251] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff:                                                                                                         
[   10.364803]  clean.                                                                                                                                                              
[   10.364819] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7:                                                                                                         
[   10.365207]  excluding 0xc80-0xcbf                                                                                                                                               
[   10.365298] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:                                                                                                    
[   10.365305]  excluding 0xc0000-0xcffff 0xe0000-0xfffff                                                                                                                           
[   10.365333] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:                                                                                                
[   10.365347]  clean.                                                                                                                                                              
[   10.365363] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:                                                                                                
[   10.365379]  excluding 0x60000000-0x60ffffff                                                                                                                                     
[   10.365397] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:                                                                                                         
[   10.366025]  clean.                                                                                                                                                              
[   10.656595] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input14                                                                                               
[   10.672811] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input12                                                                              
[   10.847551] nvidia: module license 'NVIDIA' taints kernel.                                                                                                                       
[   10.847557] Disabling lock debugging due to kernel taint                                                                                                                         
[   10.863020] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[   10.863469] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
[   10.863479] NVRM: loading NVIDIA UNIX x86 Kernel Module  331.20  Wed Oct 30 16:59:55 PDT 2013
[   11.649449] Adding 1977264k swap on /dev/sda4.  Priority:-1 extents:1 across:1977264k FS
[   11.672506] fuse init (API version 7.22)
[   12.058929] systemd-journald[104]: Received request to flush runtime journal from PID 1
[   14.861002] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[   14.963428] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[   14.963564] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[   14.963705] iwlwifi 0000:0c:00.0: L1 Enabled; Disabling L0S
[   14.966860] iwlwifi 0000:0c:00.0: Radio type=0x1-0x2-0x0
[   15.065251] iwlwifi 0000:0c:00.0: L1 Enabled; Disabling L0S
[   15.068387] iwlwifi 0000:0c:00.0: Radio type=0x1-0x2-0x0
[   15.094680] IPv6: ADDRCONF(NETDEV_UP): wlp12s0: link is not ready
[   27.715480] nvidia 0000:01:00.0: irq 48 for MSI/MSI-X
[   28.551345] NVRM: Your system is not currently configured to drive a VGA console
[   28.551357] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   28.551363] NVRM: requires the use of a text-mode VGA console. Use of other console
[   28.551368] NVRM: drivers including, but not limited to, vesafb, may result in
[   28.551373] NVRM: corruption and stability problems, and is not supported.
[   28.658780] dell_wmi: Received unknown WMI event (0x11)
[   30.018724] dell_wmi: Received unknown WMI event (0x11)
[   56.369636] wlp12s0: authenticate with **:**:**:**:**:**
[   56.372719] wlp12s0: send auth to **:**:**:**:**:** (try 1/3)
[   56.374597] wlp12s0: authenticated
[   56.376710] wlp12s0: associate with **:**:**:**:**:** (try 1/3)
[   56.378292] wlp12s0: RX AssocResp from **:**:**:**:**:** (capab=0x431 status=0 aid=1)
[   56.381098] wlp12s0: associated
[   56.381126] IPv6: ADDRCONF(NETDEV_CHANGE): wlp12s0: link becomes ready

output of systemctl --failed:

$ systemctl --failed
UNIT                               LOAD   ACTIVE SUB    DESCRIPTION
[b]NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online[/b]

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

But this service is a "just-in-case" service, and doesn't affect this at all.

I don't know how relevant it is, but looking through kdm.log, I see several instances of:

klauncher(354) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(338)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"

**also, I renamed my ~/.kde4 folder and started afresh and the problem still persists.

my system:

Linux mylappy 3.12.6-1-ARCH #1 SMP PREEMPT Fri Dec 20 19:54:53 CET 2013 i686 GNU/Linux

Anyone have any idea what the problem could be?

donniezazen · 2014-01-05 03:36:47

1. Ctrl+Alt+t doesn't work on my KDE install too.
2. When your system fails to shutdown, restart, sleep, hibernate, etc. check if your session (if that is a right term) actually got started at all. On my system, from time to time, autostart apps, kilpper, kmix, etc. won't start at the system boot. In that case shutdown, restart, sleep, etc. don't work either.

I recommend you explore these issues one by one and post your findings. A post full of issues seldom get answers.

jdoggsc · 2014-01-05 20:29:26

thanks for the reply.

From my point of view, this is not a post full of issues--rather it is a post of one issue with several symptoms/effects. I was hoping that one or more would help someone understand what the problem might be. All of these issues start happening at the same time.

ctrl+alt+t is not a standard shortcut in KDE. I set that up as a custom shortcut key, but described it as an example so readers would know what I meant by shortcut keys not working. I realize now that that was not clear. Sorry for the confusion.

I understand what you mean by autostart programs not starting when logging in to KDE. What about if they DID start when I logged in, but there are problems after resuming from sleep. I don't understand KDE well enough to know what it's doing at a system resume to know what might be going wrong.

planb2007 · 2015-02-04 11:32:29

Well - ive the same problem since a few weeks. Could you solve this issue by now?

jdoggsc · 2015-02-05 01:10:19

I abandoned KDE. That was my solution. KDE is so big I don't even know where to start troubleshooting.

Inxsible · 2015-02-05 15:11:37

planb2007, please do not necrobump threads. Start your own thread with the relevant information and reference this thread if you feel its related. Read the forum rules.

closing...

Arch Linux

#1 2014-01-04 14:37:45

KDE responsiveness issues after laptop suspend

#2 2014-01-05 03:36:47

Re: KDE responsiveness issues after laptop suspend

#3 2014-01-05 20:29:26

Re: KDE responsiveness issues after laptop suspend

#4 2015-02-04 11:32:29

Re: KDE responsiveness issues after laptop suspend

#5 2015-02-05 01:10:19

Re: KDE responsiveness issues after laptop suspend

#6 2015-02-05 15:11:37

Re: KDE responsiveness issues after laptop suspend

Board footer