Slock suspend@.service triggered only after resume

This might be some kind of X server and not systemd issue, but I was under the distinct impression that slock should always be triggered before suspend with the following, nevertheless sometimes on lid open (resume) the desktop loads appears for a brief (~.1 seconds) before switching to the slock screen). Here is my [email protected] file:
[Unit]
Description=User suspend actions
Before=sleep.target
[Service]
User=%I
#Type=forking
Environment=DISPLAY=:0
#ExecStartPre=
ExecStart=/usr/bin/slock
[Install]
WantedBy=sleep.target
Last edited by dejy (2015-06-06 10:25:17)

systemd has no way of knowing when slock has finished starting so it doesn't (can't) wait until slock is active. You could hack around this by adding a fixed delay or you could try i3lock with Type=forking (or another locker that supports something like this).

Similar Messages

Output to be triggered only after Accounting documnet is created

Hi All
I want to control that the output to be triggered only after accounting document is created not after invoice.
How to control that??
thanks
Jaagrit Hooda

Assign Routine 62 - BillDoc:ReleasePost. against to your Output type in below path., Create new billing document and check the same.
SPRO-Sales and Distribution-Basic Functions-Output Control-Output Determination-Maintain Output Determination for Billing Documents-Maintain Output Determination Procedure
Hope it helps
Regards,
Ramesh

Start the SLA clock for Service Requests Only After all Review Activities are Completed

Hi all,
I have a client who is looking for this functionality. At this stage I cannot think of a solution, certainly not a supported one.
Does anyone have any suggestions?
TIA,
Joe.

Hi,
you can define from Which date the SAL shoukd be calculated, see this Post for more Informations:
http://blogs.technet.com/b/servicemanager/archive/2012/02/07/notifying-before-sla-breaches.aspx
So, you can add a custom Field, which will be filled with a SCO Runbbok, after all RA Activity are closed.
Seidl Michael | http://www.techguy.at | twitter.com/techguyat |
facebook.com/techguyat |
youtube.com/techguyat

Labview buttons are triggered only after rerun the vi

I have a vi actually to behave like a control panel.
i created each action with a button.
for example:
Lockbutton, unlockbutton...
when run the vi, i click on lockbutton, it locks.
then after it locks, when click on unlock button, no value is parsing at unlock button.
what's is wrong with my vi?
help me..
Attachments:
Panel01.vi ‏83 KB

instead of using case structure of each button, i use event structure?
Yes - that will make things easier to manage. I would do some reading on it before you jump in, you may decide to use a producer/consumer with events should you require that the FP remain responsive when performing a time intensive operation.
about the notifier refnum, how to determine it?
each case would have its own refnum?
For this I just meant you can fork the wire for the Refnum. Something like this:
Regards,
Peter D

[Solved] Slock crash after resume

Hi there.
I recently experience something odd.
I call slock in /etc/systemd/system/[email protected] so that the screen is locked after resume.
What started only recently (I believe) is that (I assume) slock crashes about a minute after resume.
The only thing I can observe is that the lock screen is suddenly gone, without me touching anything.
If I enable slock manually this does not happen, so I assume that something kills slock.
Any ideas?
Last edited by PUE (2015-01-05 19:41:23)

$ cat /etc/systemd/system/[email protected]
[Unit]
Description=User suspend actions
Before=suspend.target
[Service]
User=%I
Type=forking
Environment=DISPLAY=:0
ExecStart=/usr/bin/slock
[Install]
WantedBy=suspend.target
There was no reference to slock in the journal. I will have to test again later. The journal output is obscured by:
...skipping...
No idea why anyone would think that it is helpful to not show part of the journal....
I have a couple of suspicious lines in there (reverse log because I don't know how to just search near the end), but I am not sure whether this is the problematic case:
Jan 04 14:29:54 eeyore systemd[1]: Stopped target Suspend.
Jan 04 14:29:54 eeyore systemd[1]: Stopping Suspend.
Jan 04 14:29:54 eeyore systemd[1]: Unit suspend.target is bound to inactive service. Stopping, too.
Jan 04 14:29:54 eeyore systemd-logind[295]: Operation finished.
Jan 04 14:29:54 eeyore systemd[1]: Reached target Suspend.
Jan 04 14:29:54 eeyore systemd[1]: Starting Suspend.
Jan 04 14:29:54 eeyore systemd[1]: [email protected] failed.
Jan 04 14:29:54 eeyore systemd[1]: Unit [email protected] entered failed state.
Jan 04 14:29:54 eeyore systemd[1]: Failed to start User suspend actions.
Jan 04 14:29:54 eeyore systemd[1]: [email protected] start operation timed out. Terminating.
Jan 04 14:28:44 eeyore systemd[469]: Time has been changed
Jan 04 14:28:44 eeyore systemd[1]: Time has been changed
Last edited by PUE (2015-01-05 17:54:01)

[WORKAROUND] Cannot connect to any WiFi network after resume

Hi, I'm having one weird problem that makes my laptop not as mobile as I'd like it to be..
Literally, I have to boot it up again after each move.
Here's the issue: if I suspend to ram, and then resume in a place with different WiFi network, it can't connect to Internet again.
I'm using NetworkManager via corresponding plasmoid in KDE (although, nmcli does not work either).
When I click a network name, I get the following:
"Configuring interface" .... -> Cannot connect to {NetworkName}
(the labels might be a bit different, as I get all notifications in my local language)
Have anyone experienced this before?
Or, AT LEAST, how can I get a bit more verbose output from NetworkManager? Is there a log file?
Here's the hardware:
05:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Here's what I've tried already (and it didn't help):
# systemctl restart NetworkManager
# modprobe -r ath9k
# ncmcli nm sleep false
WORKAROUND FOUND: When I get "Configuring interface" .... -> Cannot connect to {NetworkName} (it happens not only after resumes, btw), I type the following in the console:
sudo dhcpcd -k
So much time passed, so many updates -- still have to do this manually... %)
Last edited by mityukov (2013-12-03 10:19:12)

hadrons123 wrote:Try these methods
https://bbs.archlinux.org/viewtopic.php?pid=1241694
Here's what I've tried:
# stop NetworkManager first, just in case if it would not start anything before time
sudo systemctl stop NetworkManager
# kill wpa_supplicant (one of suggestions in the topic)
sudo killall wpa_supplicant
# re-load kernel module with nohwcrypt=1 (another suggestion in the topic):
sudo modprobe -r ath9k
sudo modprobe ath9k nohwcrypt=1
# start NetworkManager again
sudo systemctl start NetworkManager
Then tried to connect the network again: the issue is till the same. Here's the latest dmesg:
$ sudo dmesg -c
[ 3079.006749] ath9k: ath9k: Driver unloaded
[ 3111.623220] cfg80211: Calling CRDA to update world regulatory domain
[ 3111.694588] ath: phy0: ASPM enabled: 0x43
[ 3111.694594] ath: EEPROM regdomain: 0x65
[ 3111.694596] ath: EEPROM indicates we should expect a direct regpair map
[ 3111.694599] ath: Country alpha2 being used: 00
[ 3111.694600] ath: Regpair used: 0x65
[ 3111.697195] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 3111.697465] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc900140a0000, irq=16
[ 3111.717234] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3136.958046] r8169 0000:03:00.0 eth0: link down
[ 3136.958159] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3138.903691] wlan0: authenticate with 00:24:8c:65:bb:d5
[ 3138.911517] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
[ 3138.911567] wlan0: send auth to 00:24:8c:65:bb:d5 (try 1/3)
[ 3138.917180] wlan0: authenticated
[ 3138.917697] ath9k 0000:05:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 3138.917711] ath9k 0000:05:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 3138.917718] ath9k 0000:05:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 3138.918897] wlan0: associate with 00:24:8c:65:bb:d5 (try 1/3)
[ 3138.932402] wlan0: RX AssocResp from 00:24:8c:65:bb:d5 (capab=0x411 status=0 aid=3)
[ 3138.932553] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 3138.932790] wlan0: associated
[ 3139.406632] wlan0: deauthenticating from 00:24:8c:65:bb:d5 by local choice (reason=3)
[ 3139.415815] cfg80211: Calling CRDA to update world regulatory domain
[ 3143.712977] wlan0: authenticate with 00:24:8c:65:bb:d5
[ 3143.720532] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
[ 3143.720582] wlan0: send auth to 00:24:8c:65:bb:d5 (try 1/3)
[ 3143.731367] wlan0: authenticated
[ 3143.731865] ath9k 0000:05:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 3143.731882] ath9k 0000:05:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 3143.731888] ath9k 0000:05:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 3143.735093] wlan0: associate with 00:24:8c:65:bb:d5 (try 1/3)
[ 3143.748277] wlan0: RX AssocResp from 00:24:8c:65:bb:d5 (capab=0x411 status=0 aid=3)
[ 3143.748533] wlan0: associated
[ 3144.140732] wlan0: deauthenticating from 00:24:8c:65:bb:d5 by local choice (reason=3)
[ 3144.148708] cfg80211: Calling CRDA to update world regulatory domain
[ 3148.642615] wlan0: authenticate with 00:24:8c:65:bb:d5
[ 3148.650085] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
[ 3148.650132] wlan0: send auth to 00:24:8c:65:bb:d5 (try 1/3)
[ 3148.665772] wlan0: authenticated
[ 3148.666264] ath9k 0000:05:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 3148.666278] ath9k 0000:05:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 3148.666284] ath9k 0000:05:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 3148.667980] wlan0: associate with 00:24:8c:65:bb:d5 (try 1/3)
[ 3148.681955] wlan0: RX AssocResp from 00:24:8c:65:bb:d5 (capab=0x411 status=0 aid=3)
[ 3148.682212] wlan0: associated
[ 3149.016733] wlan0: deauthenticating from 00:24:8c:65:bb:d5 by local choice (reason=3)
[ 3149.031462] cfg80211: Calling CRDA to update world regulatory domain
[ 3153.648602] wlan0: authenticate with 00:24:8c:65:bb:d5
[ 3153.656323] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
[ 3153.656374] wlan0: send auth to 00:24:8c:65:bb:d5 (try 1/3)
[ 3153.659859] wlan0: authenticated
[ 3153.660389] ath9k 0000:05:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 3153.660403] ath9k 0000:05:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 3153.660410] ath9k 0000:05:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 3153.663889] wlan0: associate with 00:24:8c:65:bb:d5 (try 1/3)
[ 3153.672276] wlan0: RX AssocResp from 00:24:8c:65:bb:d5 (capab=0x411 status=0 aid=3)
[ 3153.672536] wlan0: associated
[ 3153.967817] wlan0: deauthenticating from 00:24:8c:65:bb:d5 by local choice (reason=3)
[ 3153.980619] cfg80211: Calling CRDA to update world regulatory domain

System freeze after resume from suspend to RAM

Hi,
since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
kernel: sas: trying to find task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
kernel: sas: trying to find task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
kernel: sas: ata7: end_device-0:0: cmd error handler
kernel: sas: ata8: end_device-0:1: cmd error handler
kernel: sas: ata7: end_device-0:0: dev error handler
kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
kernel: ata7.00: status { DRDY }
kernel: ata7: hard resetting link
kernel: sas: ata8: end_device-0:1: dev error handler
kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
kernel: ata8.00: status { DRDY }
kernel: ata8: hard resetting link
This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
Here's my setup:
$ lsblk -St
NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs Recovery 567437B974379B27
├─sda2 vfat DC2D-099E /boot
├─sda3
├─sda4 ntfs FEBED982BED933BD
├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
└─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
sdb
└─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
sdc
└─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
sdd
└─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
Any ideas on how I could narrow down this issue? Thanks a lot!
EDIT
I just checked and confirmed that this issue is originating from the OCZ Revodrive:
$ dmesg | grep ata7.00 | head
[ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.146442] ata7.00: configured for UDMA/133
$ dmesg | grep ata8.00 | head
[ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.320022] ata8.00: configured for UDMA/133
Last edited by tuttiarch (2015-01-31 15:54:29)

Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

No sound in Flash after resuming from suspend

After I resume from a suspend or sleep there is no sound in Flash and there is no networking.
The only way is to restart my browser to reestablish the sound.
Is there a solution for this problem?
Thanks.

This does not happen with Firefox in Ubuntu, as an example. So something must be wrong somewhere.
I can confirm this happens to me in Arch with Firefox 4.0b7 and Chromium 7.0.517.44. I noticed that after resuming from suspend, not only sound (in Flash) is missing, but Flash is behaving weirdly (YouTube video plays much faster) and CPU usage goes crazy without doing any particular action.
Last edited by Niavlys (2010-12-05 23:34:30)

[Solved] No sound after resuming from suspend

After suspending and resuming I no longer have any sound output (through headphone jack or my laptop speaker). The laptop is a toshiba portege r835. I can't say how long this has been happening, since I've only tried to play any sounds after resuming recently.
Searching the forums I found the following thread: https://bbs.archlinux.org/viewtopic.php?id=151001
I haven't tried this because it isn't exactly the same problem, but mostly because I'm currently stuck on kernel 3.5.6 because of the sandy bridge power regression issues.
Does anyone have any other ideas on how to possibly fix this problem?
Thanks!!
Last edited by twistedcubic (2012-12-31 22:20:20)

Solved, sort of.
I had some double suspend issue: I had set up suspend with systemd before using xfce and then after installing xfce I set my power settings so that the computer would suspend after shutting the lid, so I would have to open the lid, shut it, and then open it again for the computer to actually resume. After turning off the suspend setting in the xfce power manager, and just using the systemd suspend, the sound works fine on resume (both headphones and speakers)!

Network has weird problem after Resume from suspend...

hi guys,
I have a ThinkPad T60 laptop with archlinux at home. and I have a router with wlan supported for the internet. Suspend/Resuming (pm-utils) works. Recently after resuming, the network-manager says WLAN connected with ESSID, but internet connection was lost. it is weird:
I can really connect the WLAN, e.g. I can ping another computer's IP and exchange files with it,
I can see my wlan by iwlist,
but I cannot reach the IP address of the router by Ping.
I tried restarting network-manager, switching off and on the wireless adapter neither worked. the only way I found to bring the network back is restarting the router.
I list the stuff that I thought would be helpful here, hope someone can give some hints.
thanks in advance.
kent$ uname -a
Linux ArchT60 3.0-ARCH #1 SMP PREEMPT Wed Aug 17 20:24:07 UTC 2011 i686 Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz GenuineIntel GNU/Linux
part of my rc.conf:
MODULES=(acpi-cpufreq cpufreq_ondemand iwl3945 fuse radeon vboxdrv !floppy !pcspkr)
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.254"
ROUTES=(gateway)
DAEMONS=(syslog-ng !network @acpid @alsa netfs @crond hal @cups !dbus networkmanager @sshd tpfand gdm)
the last suspend/resuming log (/var/log/pm-suspend.log)
There errors when it was waked up. one with alsa, the other two about hal and tpfand. I thought that it has nothing to do with network.
And I didn't install netcfg. So the netcfg11 hook does actually nothing.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
... uname, lsmod and free output are omitted ...
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /etc/pm/sleep.d/09tpfand suspend suspend:
:: Stopping ThinkPad fan control daemon [BUSY] [DONE]
/etc/pm/sleep.d/09tpfand suspend suspend: success.
Running hook /etc/pm/sleep.d/10hal suspend suspend:
:: Stopping Hardware Abstraction Layer [BUSY] [DONE]
/etc/pm/sleep.d/10hal suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /etc/pm/sleep.d/91alsa suspend suspend:
/etc/pm/sleep.d/91alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Aug 25 01:39:30 CEST 2011: performing suspend
Thu Aug 25 21:11:44 CEST 2011: Awake.
Thu Aug 25 21:11:44 CEST 2011: Running hooks for resume
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
/usr/lib/pm-utils/sleep.d/95led resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /etc/pm/sleep.d/91alsa resume suspend:
ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused
aplay: main:660: audio open error: Connection refused
/etc/pm/sleep.d/91alsa resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
/usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
Running hook /etc/pm/sleep.d/90alsa resume suspend:
ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused
aplay: main:660: audio open error: Connection refused
/etc/pm/sleep.d/90alsa resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg resume suspend:
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: success.
Running hook /etc/pm/sleep.d/10hal resume suspend:
A daemon is starting another daemon, this is unlikely to work as intended.\n
:: Starting Hardware Abstraction Layer [BUSY] [DONE]
/etc/pm/sleep.d/10hal resume suspend: success.
Running hook /etc/pm/sleep.d/09tpfand resume suspend:
A daemon is starting another daemon, this is unlikely to work as intended.\n
:: Starting ThinkPad fan control daemon [BUSY] [DONE]
/etc/pm/sleep.d/09tpfand resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub resume suspend:
/usr/lib/pm-utils/sleep.d/01grub resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
Thu Aug 25 21:11:46 CEST 2011: Finished.
Last edited by sk1418 (2011-08-26 20:08:39)

after it waked up, I did tried ifconfig down/up wlan0, didn't work.
I will try to bring down the wlan0 before suspend tomorrow.
some new test from yesterday
Router IP: 192.168.0.254
DNS:192.168.0.254
another PC: 192.168.0.1
one of Google IP:74.125.39.104
after waked up
ping 192.168.0.254 , failed.
ping 192.168.0.1 OK
ping 74.125.39.104 OK
ping www.google.com Failed
I changed the DNS to google DNS:8.8.8.8, then I can access website in browser, also ping www.google.com OK.
I even REBOOTed my laptop, I still cannot reach my router by ping 192.168.0.254.... accessing internet is ok...
if I restart router, everything is fine...
what is the problem!!! weird!
Last edited by sk1418 (2011-08-30 22:59:31)

Cannot connect to X server after resume from suspend

Hello,
i'm a happy user of arch and i3, one and only thing that is not working correctly is that sometimes after resume from sleep (closing the lid, and then opening) I am not able to start any programs. this happens about 50% of the time. when it happens i have to exit i3 and login again, and everything works ok then.
I'd be grateful for any suggestion how can I debug and solve this problem.
y
Last edited by yemu (2014-04-09 08:53:12)

the error was, after running xterm:
No protocol specified
xterm: Xt error: Can't open display: :0.0
after running scrot
No protocol specified
giblib error: Can't open X display. It *is* running, yeah?
after running firefox
(process:2559): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
No protocol specified
No protocol specified
Error: cannot open display: :0.0
but I think I was able to fix the problem.
when I was browsing the internet for solution, I stumbled upon an info about similar problem caused by the hostname set to localhost. I checked my system, and apparently I haven't set my host name during install, and it was still localhost, so I changed it. and after that I tried suspending several times, and the problem never occured. I'll test in upcoming days, and if it works I will change the thread title to [SOLVED].
Last edited by yemu (2014-04-10 07:40:47)

[SOLVED]pc freezes after resuming from suspend.

When I upgraded kernel from linux-3.3.8-1 to linux-3.4.2-2 or later , PC freezes after resuming.
Monitor comes back and kde requires passward , but after few seconds , everything freezes.
keyboard and mouse won't respond.
There is no log after resuming.
Is there anybody who have same trouble?
CPU intel core i7 2600k
MB asrock H67M-GE
/var/log/pm-suspend.log
Initial commandline parameters:
Thu Jun 21 16:52:33 JST 2012: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux myhost 3.4.3-1-ARCH #1 SMP PREEMPT Mon Jun 18 08:28:29 CEST 2012 x86_64 GNU/Linux
Module Size Used by
w83627ehf 31388 0
hwmon_vid 3196 1 w83627ehf
xt_hl 1369 6
ip6t_rt 2112 3
nf_conntrack_ipv6 6650 7
nf_defrag_ipv6 6401 1 nf_conntrack_ipv6
ipt_REJECT 2281 1
xt_LOG 11975 9
xt_limit 2041 12
xt_tcpudp 2503 18
xt_addrtype 2853 4
xt_state 1295 14
ip6table_filter 1396 1
ip6_tables 18198 2 ip6table_filter,ip6t_rt
nf_conntrack_netbios_ns 1077 0
nf_conntrack_broadcast 1285 1 nf_conntrack_netbios_ns
nf_nat_ftp 1668 0
nf_nat 15100 1 nf_nat_ftp
nf_conntrack_ipv4 6871 9 nf_nat
nf_defrag_ipv4 1339 1 nf_conntrack_ipv4
nf_conntrack_ftp 6261 1 nf_nat_ftp
nf_conntrack 61584 8 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_state,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_ipv6
iptable_filter 1456 1
ip_tables 16946 1 iptable_filter
x_tables 16954 12 ip6table_filter,xt_hl,ip_tables,xt_tcpudp,xt_limit,xt_state,xt_LOG,iptable_filter,ip6t_rt,ipt_REJECT,ip6_tables,xt_addrtype
snd_hda_codec_hdmi 23672 1
snd_hda_codec_realtek 60377 1
vboxdrv 1792262 0
acpi_cpufreq 5933 1
aesni_intel 43154 0
mperf 1267 1 acpi_cpufreq
snd_hda_intel 24053 4
aes_x86_64 7508 1 aesni_intel
ppdev 5902 0
aes_generic 26138 2 aesni_intel,aes_x86_64
ghash_clmulni_intel 4237 0
r8169 49354 0
i915 438164 3
video 11307 1 i915
i2c_i801 8180 0
i2c_algo_bit 5391 1 i915
drm_kms_helper 33051 1 i915
drm 208958 4 i915,drm_kms_helper
parport_pc 30765 0
intel_agp 10936 1 i915
mei 32152 0
psmouse 70792 0
pcspkr 1899 0
processor 26567 1 acpi_cpufreq
evdev 9754 6
button 4502 1 i915
intel_gtt 14047 3 i915,intel_agp
parport 31395 2 ppdev,parport_pc
i2c_core 20369 5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
serio_raw 4653 0
cryptd 8741 2 ghash_clmulni_intel,aesni_intel
coretemp 5654 0
iTCO_wdt 12813 0
mii 4123 1 r8169
iTCO_vendor_support 1929 1 iTCO_wdt
snd_hda_codec 94273 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
crc32c_intel 1987 0
snd_hwdep 6300 1 snd_hda_codec
snd_pcm 74958 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
snd_timer 18966 2 snd_pcm
snd 58997 13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5410 1 snd
microcode 12185 0
ext4 424175 2
crc16 1359 1 ext4
jbd2 73919 1 ext4
mbcache 5977 1 ext4
usbhid 36430 0
hid 85285 1 usbhid
ehci_hcd 41154 0
usbcore 147533 3 ehci_hcd,usbhid
usb_common 954 1 usbcore
floppy 58615 0
sr_mod 14823 0
cdrom 35648 1 sr_mod
sd_mod 29239 4
ahci 20549 4
libahci 20023 1 ahci
libata 167611 2 ahci,libahci
scsi_mod 132942 3 libata,sd_mod,sr_mod
total used free shared buffers cached
Mem: 7900332 743308 7157024 0 34932 257560
-/+ buffers/cache: 450816 7449516
Swap: 15359996 0 15359996
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Jun 21 16:52:33 JST 2012: performing suspend
Last edited by remingtontonpon (2012-07-25 01:58:04)

In my case, monitor freezes too.
And I have only one PC, so i can't try ssh.
I logged into runlevel3 and try
sudo pm-suspend
and it works fine. So it seems this trouble caused only in runlevel5.
I also tried following command in runlevel5
# echo freezer > /sys/power/pm_test
# echo mem > /sys/power/state
# echo devices > /sys/power/pm_test
# echo mem > /sys/power/state
# echo platform > /sys/power/pm_test
# echo mem > /sys/power/state
# echo processors > /sys/power/pm_test
# echo mem > /sys/power/state
# echo core > /sys/power/pm_test
# echo mem > /sys/power/state
Everything works fine but sudo pm-suspend failed.
Last edited by remingtontonpon (2012-06-25 08:18:26)

Display corruption after resume from suspend-to-disk

Garbage is also visible on the display immediately before entering suspend-to-RAM, but it resumes successfully, so that's not a priority.
The resume process (using uswsusp) appears to complete (reaches 100%) but then the display is replaced by garbage (including ttys). If on an X display, the mouse is visible as a roughly 128x128 square of garbage pixels that I can move around the screen. If I switch to a tty, login and reboot (blindly, as the screen is garbage) then it successfully reboots and runs without issue.
My laptop is a Dell Studio 1555 (with Mobility Radeon 4570).
Using vbetool to save and restore VBIOS state before and after hibernating (via hibernate-script) makes no difference that I can see.
How would I go about figuring out what's going wrong here?

I did try reinstalling, actually. But I did not think to remove the battery and the ram... I'm very curious now: what is the rationale / intuition for that? Or is it just that empirical evidence suggests this may be a good idea?
Anyhow, the reinstall by itself did not help. I tried it out with a pretty bare-bones setup and had the same results. Here are a few other things I noticed:
- After the suspend, one of the cores is always running at the maximum clock frequency, according to powertop (although, according to ps aux, no one is doing any work).
- Even if I ssh to a nearby machine, I get the same experience when running `ls`. The screen fills very slowly. That narrows things down a little bit, but I was already guessing it would be graphics-related.
I have also tried a few random kernel boot parameters after reading things online, but none of those worked, and several stopped the machine from booting at all.
Thanks for your help.

[SOLVED] After resume from suspend to RAM, system is slow / unstable

Hello,
I have come across some strangeness when trying to suspend my system. The
computer is a lenovo U350. I have read a lot of threads on these subjects,
but I never found one that quite matched the experiences I'm having, so I felt
compelled to make a new post.
Here's what's going on: I boot into the terminal, and then run pm-suspend.
Within a few seconds, the computer goes to sleep, just as I had hoped. The
problem is that my computer seems a little groggy when I wake it back up.
Usually, when running a command like ps aux | less, the screen fills up very
quickly. After I resume from sleep, running ps aux | less is noticeably slow.
It takes a full second (+/- epsilon) to fill the screen. Other symptoms: if I
suspend / resume in the terminal, and then start a window manager (KDE), the
graphics will be slow and choppy, and when I try to exit the window manager, I
usually end up having to perform the dreaded REISUB after getting stuck on a
blank screen with a non-blinking cursor in the upper left hand corner.
Suspend / resume from KDE will result in either the black, non-responsive
screen as soon as I try to resume, or in the choppy graphics, followed by the
non-responsive black screen when I log out.
I looked at the process list before and after, and noticed that when the
system is first resumed, there are around 50-60 additional kworker processes
running than when I put it to sleep. I don't know if this is normal or not.
Also, hci0 has been killed, and a new hci0 process has taken its place. The
same goes for one of the udevd processes. About 40-50 of the kworker
processes finish after a few minutes, but this does not change the slowness of
ps aux | less, nor does it help with my window manager issues.
I ran a few (not so precise) performance tests before and after doing a
suspend, and got the same results (the test was just to compile some LaTeX,
which took about 4-5 seconds either way).
I examined the pm-suspend.log, and everything looked peachy. All of the
hooks returned success for the suspend, as well as the resume. I'm happy to
post this if needed. I did not change any of the default settings for
pm-suspend.
Anyhow, I've read a lot of threads, and seen a lot of suggestions, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=137682
https://bbs.archlinux.org/viewtopic.php?id=136292 (use vbetool?)
https://bbs.archlinux.org/viewtopic.php?id=126174 (suspend tons of modules?)
https://bbs.archlinux.org/viewtopic.php?id=131827 (hpet=disable ?)
However, I'm not that confident in any of them, since no one had quite the
same issue. I was hoping that someone could point me in the right direction
before I start blindly walking through all the candidate fixes and risk
unleashing chaos into my system. Many thanks in advance for your help.
Oh, and in case this post was not yet long enough, here is some system
information:
lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
lsmod:
Module Size Used by
aes_x86_64 7508 3
cryptd 8309 0
aes_generic 26138 1 aes_x86_64
coretemp 5590 0
cpufreq_ondemand 6164 2
acpi_cpufreq 5877 1
mperf 1275 1 acpi_cpufreq
freq_table 2515 2 acpi_cpufreq,cpufreq_ondemand
arc4 1410 2
joydev 9895 0
snd_hda_codec_hdmi 24121 1
iwlwifi 248196 0
i915 420018 3
snd_hda_codec_conexant 47300 1
uvcvideo 64311 0
mac80211 228527 1 iwlwifi
videodev 82101 1 uvcvideo
snd_hda_intel 23375 0
snd_hda_codec 89389 3 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
broadcom 7270 0
tg3 134884 0
ideapad_laptop 8534 0
snd_hwdep 6389 1 snd_hda_codec
snd_pcm 74780 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
snd_page_alloc 7153 2 snd_pcm,snd_hda_intel
snd_timer 19544 1 snd_pcm
snd 59214 7 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
iTCO_wdt 11885 0
v4l2_compat_ioctl32 8316 1 videodev
i2c_i801 8187 0
i2c_algo_bit 5263 1 i915
drm_kms_helper 26137 1 i915
intel_agp 10904 1 i915
btusb 11385 0
cfg80211 172260 2 mac80211,iwlwifi
bluetooth 151999 1 btusb
sparse_keymap 3120 1 ideapad_laptop
soundcore 6210 1 snd
drm 188499 4 drm_kms_helper,i915
rfkill 15498 3 bluetooth,cfg80211,ideapad_laptop
serio_raw 4429 0
iTCO_vendor_support 1961 1 iTCO_wdt
media 10597 2 videodev,uvcvideo
psmouse 61311 0
libphy 16985 2 tg3,broadcom
i2c_core 20492 6 drm,drm_kms_helper,i2c_algo_bit,i2c_i801,videodev,i915
intel_gtt 14519 3 intel_agp,i915
pcspkr 1819 0
evdev 9530 8
thermal 7799 0
wmi 8475 0
battery 6453 0
ac 2344 0
video 11164 1 i915
button 4470 1 i915
processor 25582 3 acpi_cpufreq
ext4 420412 3
crc16 1359 2 ext4,bluetooth
jbd2 71499 1 ext4
mbcache 5881 1 ext4
sd_mod 28307 5
ahci 20037 4
libahci 19559 1 ahci
libata 166654 2 libahci,ahci
scsi_mod 133676 2 libata,sd_mod
uhci_hcd 23116 0
ehci_hcd 40698 0
usbcore 146113 5 ehci_hcd,uhci_hcd,btusb,uvcvideo
usb_common 954 1 usbcore
Last edited by wes (2012-04-06 21:34:43)

I did try reinstalling, actually. But I did not think to remove the battery and the ram... I'm very curious now: what is the rationale / intuition for that? Or is it just that empirical evidence suggests this may be a good idea?
Anyhow, the reinstall by itself did not help. I tried it out with a pretty bare-bones setup and had the same results. Here are a few other things I noticed:
- After the suspend, one of the cores is always running at the maximum clock frequency, according to powertop (although, according to ps aux, no one is doing any work).
- Even if I ssh to a nearby machine, I get the same experience when running `ls`. The screen fills very slowly. That narrows things down a little bit, but I was already guessing it would be graphics-related.
I have also tried a few random kernel boot parameters after reading things online, but none of those worked, and several stopped the machine from booting at all.
Thanks for your help.

Touchpad permanently not working after resuming from suspend

I lost touchpad and trackpoint functionality after resuming from suspend on my ThinkPad E530 (3259CTO).
Even after a complete power off (with the battery removed), the touchpad is detected but doesn't send any event, and the trackpoint is not detected.
In Windows, in the UltraNav control panel, the touchpad is marked as enabled and cannot be disabled, the trackpoint is grayed.
In Linux, I can see the difference is kernel traces when the driver is loaded.
Before : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
Now : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x0/0x0
After looking at https://gerrit.chromium.org/gerrit/#/c/31105/ and Synaptics public documentation, I was able to get more information : the device status register (F01_RMI_Data0) is 0x45, which means the touchpad is in flash programming mode since there is a firmware CRC failure.
It looks like http://code.google.com/p/chromium-os/issues/detail?id=24298, so it's probably not a Lenovo specific problem, but a bug in Synaptics firmware.
Can Lenovo provide the firmware to flash like http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X220-Touchpad-jumpy-response-when-used-with-90... which would hopefully make my touchpad working again ?
The original firmware should work, but an updated one would be better, if it avoids losing the touchpad again later.

I don't know why, but this made me think of the episode of the simpsons when home tries to get over 300 pounds so he can work from home. When he tries to dial the phone he hist all the buttons and gets a recording that says "We're sorry, you're fingers are too fat. To obtain a special dialing wand, please mash the keypad now."
BTW, sorry I can't help... but at least I am entertained easily.

Slock suspend@.service triggered only after resume

Similar Messages

Maybe you are looking for