How to change [platform] mode to [shutdown] mode in /sys/power/disk

firekage · 2015-02-04 23:06:31

Hi.

I would like to ask for help. I'm trying to solve why suspend to ram doesen't work at all on my desktop machine, while on the notebook it works (Acer AOD 270).

My spec is:

I5-4670K
Nvidia GTX 660 with nvidia 346xx drivers
Arch 64bit : 3.18.5-1-ARCH
8GB ram
10 GB swap partition

I'm trying to do a suspend to ram but it just doesen;t work at all. I don't know how to check, or debug it. I don't hace pm-suspend and pm-powersave logs because i don't have pm-utils installed. I want do only suspend to ram. Arch wiki says that suspending to ram should work out of the box but in my case, it wont. I do a suspend, computer is powering down, i see black screen and power stays with the machine, my fans are spinning, drives are working and nothing happens. In fact, computer in this moment...is freezed. I can only plug the power cord...

I though that it could be because of my arch setup, so i do a clean fresh install. I installed all basic arch packages and tried to suspend without even having gui (kde). I tried to suspend with terminal in terminal mode (text mode). I did sudo systemctl suspend and...the same thing happenden on clean arch install that happens all the time on my arch that i use with gui (kde).

Could somebody help me? Tried to check journalctl logs, kdm.log, tried to see Xorg.0.logs but they are clean. Tried to check dmesg with tail options, the same. How to check why suspend to ram even with clean install freezes computer? Black screen, nothing more, fans and drives working. I tried the same kernel, mentioned above, on notebok, mentioned above, and suspend to ram works. On desktop - doesen't. Why ? In fact, i switched from AMD platforms and ability to suspend to ram and suspend to disk with intel went away.

Last edited by firekage (2015-02-12 15:28:17)

Kinokoio · 2015-02-07 19:01:23

You tried suspending using systemctl suspend?

Your problem sounds rare.

Last edited by Kinokoio (2015-02-07 19:01:48)

frank604 · 2015-02-07 19:45:13

Can you log into TTY2 to see dmesg? If not, then do this:
1. systemctl suspend
2. you get the freeze
3. reboot
4. journalctl -b -1 <---show us this

firekage · 2015-02-08 23:52:07

Kinokoio wrote:

You tried suspending using systemctl suspend?
Your problem sounds rare.

Yes, i tried it. The same thing. My problem is rare, and frankly, don't know why on my desktop can't do it at all.

What's more funny, i tried to run s2disk - system was going to be shutted down, i see that s2disk was writing to a swap partition my session, and when it reachjed 100% of writing and should shut down, it wont. After suspend to disk it can't be shut down, only reset works. What is more funny - after reset my system is being restored correctly from swap partition.

Suspend to ram does not work at all.

firekage · 2015-02-08 23:52:59

frank604 wrote:

Can you log into TTY2 to see dmesg? If not, then do this:
1. systemctl suspend
2. you get the freeze
3. reboot
4. journalctl -b -1 <---show us this

I tried to check dmesg many times, i don't see anything wrong in that. Will check what you wrote with one small change - cant reboot, can only reset.

Last edited by firekage (2015-02-08 23:57:36)

frank604 · 2015-02-08 23:59:33

Can you show us a journalctl of when you try to suspend ? It doesn't matter if you didn't see anything wrong in journalctl, perhaps we will notice something and have actual information to go on instead of guessing. The least it would do is move on to another area for troubleshooting.

firekage · 2015-02-09 00:13:42

frank604 wrote:

Can you show us a journalctl of when you try to suspend ? It doesn't matter if you didn't see anything wrong in journalctl, perhaps we will notice something and have actual information to go on instead of guessing. The least it would do is move on to another area for troubleshooting.

Yes, of course. Don't know if i did it correctly. I typed in terminal sudo systemctl hibernate. System "went" into hibernate, writed to swap...freezed, i hit the power button, system was rebooted and restored from the saved swap paritition and than i typed journactl tyou mentioned

[firekage@arch_desktop ~]$ LANG=C journalctl -b -1
-- Logs begin at Tue 2015-01-20 02:52:00 CET, end at Tue 2015-02-24 19:07:22 CET. --
Mar 02 00:31:25 arch_desktop systemd[618]: Starting Timers.
Mar 02 00:31:25 arch_desktop systemd[618]: Reached target Timers.
Mar 02 00:31:25 arch_desktop systemd[618]: Starting Paths.
Mar 02 00:31:25 arch_desktop systemd[618]: Reached target Paths.
Mar 02 00:31:25 arch_desktop systemd[618]: Starting Sockets.
Mar 02 00:31:25 arch_desktop systemd[618]: Reached target Sockets.
Mar 02 00:31:25 arch_desktop systemd[618]: Starting Basic System.
Mar 02 00:31:25 arch_desktop systemd[618]: Reached target Basic System.
Mar 02 00:31:25 arch_desktop systemd[618]: Starting Default.
Mar 02 00:31:25 arch_desktop systemd[618]: Reached target Default.
Mar 02 00:31:25 arch_desktop systemd[618]: Startup finished in 6ms.
Mar 02 00:31:32 arch_desktop kactivitymanagerd[775]: org.kde.kactivities.activities: Starting
Mar 02 00:31:32 arch_desktop kded5[785]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:31:32 arch_desktop kded5[785]: Qt: Session management error: networkIdsList argumen
Mar 02 00:31:33 arch_desktop kded5[785]: klauncher not running... launching kdeinit
Mar 02 00:31:33 arch_desktop kdeinit5[792]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:31:33 arch_desktop kdeinit5[792]: Qt: Session management error: networkIdsList argu
Mar 02 00:31:33 arch_desktop kdeinit5[792]: Connecting to deprecated signal QDBusConnectionIn
Mar 02 00:31:33 arch_desktop kdeinit5[792]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pi
Mar 02 00:31:33 arch_desktop kbuildsycoca5[794]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:31:33 arch_desktop kbuildsycoca5[794]: kf5.kservice.sycoca: Trying to open ksycoca 
Mar 02 00:31:33 arch_desktop kbuildsycoca5[794]: checking file timestamps
Mar 02 00:31:33 arch_desktop kbuildsycoca5[794]: timestamps check ok
Mar 02 00:31:33 arch_desktop kbuildsycoca5[794]: Emitting notifyDatabaseChanged ()
Mar 02 00:31:33 arch_desktop kded5[785]: kf5.kservice.sycoca: Trying to open ksycoca from "/h
Mar 02 00:31:33 arch_desktop kdeinit5[792]: kf5.kservice.sycoca: Trying to open ksycoca from 
Mar 02 00:31:33 arch_desktop kdeinit5[792]: kf5.kinit.klauncher: "/usr/lib/kf5/kconf_update" 
Mar 02 00:31:33 arch_desktop org.kde.kded5[639]: kbuildsycoca5 running...
Mar 02 00:31:33 arch_desktop kdeinit5[792]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pi
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:31:33 arch_desktop org.kde.kded5[639]: kbuildsycoca5 running...
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: kf5.kservice.sycoca: Trying to open ksycoca 
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: Reusing existing ksycoca
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: Recreating ksycoca file ("/home/firekage/.ca
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: Still in the time dict (i.e. deleted files) 
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: Menu "applications-kmenuedit.menu" not found
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: Saving
Mar 02 00:31:33 arch_desktop kbuildsycoca5[796]: Emitting notifyDatabaseChanged ("apps")
Mar 02 00:31:33 arch_desktop kded5[785]: kf5.kservice.sycoca: Trying to open ksycoca from "/h
Mar 02 00:31:33 arch_desktop kactivitymanagerd[775]: kf5.kservice.sycoca: Trying to open ksyc
Mar 02 00:31:33 arch_desktop kactivitymanagerd[775]: Creating directory:  "/home/firekage/.lo
Mar 02 00:31:33 arch_desktop kactivitymanagerd[775]: org.kde.kactivities.application: [   OK 
Mar 02 00:31:33 arch_desktop kactivitymanagerd[775]: org.kde.kactivities.application: [   OK 
Mar 02 00:31:33 arch_desktop kactivitymanagerd[775]: org.kde.kactivities.application: [   OK 
Mar 02 00:31:33 arch_desktop kactivitymanagerd[798]: Qt: Session management error: networkIds
Mar 02 00:31:34 arch_desktop baloo_file[819]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:31:34 arch_desktop baloo_file[819]: "/home/firekage/.local/share/baloo/file/" true
Mar 02 00:31:34 arch_desktop baloo_file[819]: "/home/firekage"
Mar 02 00:31:34 arch_desktop baloo_file[819]: "/home/firekage"
Mar 02 00:31:34 arch_desktop baloo_file[819]: Successfully opened connection to inotify: 25
Mar 02 00:31:35 arch_desktop org.kde.kuiserver[639]: QDBusConnection: session D-Bus connectio
Mar 02 00:31:35 arch_desktop org.kde.kuiserver[639]: QDBusConnection: session D-Bus connectio
Mar 02 00:31:36 arch_desktop baloo_file[819]: XSync seems available and ready
Mar 02 00:31:36 arch_desktop baloo_file[819]: XSync Inited
Mar 02 00:31:36 arch_desktop baloo_file[819]: Supported, init completed
Mar 02 00:31:36 arch_desktop baloo_file[819]: Normal
Mar 02 00:31:36 arch_desktop baloo_file[819]: "/home/firekage/.xsession-errors"
Mar 02 00:31:36 arch_desktop baloo_file[819]: Created alarm 48234497
Mar 02 00:31:36 arch_desktop baloo_file[819]: Normal
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Default and alternate sample rates are the same
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Default and alternate sample rates are the same
Mar 02 00:31:40 arch_desktop baloo_file[819]: "/home/firekage/.esd_auth"
Mar 02 00:31:40 arch_desktop baloo_file[819]: Normal
Mar 02 00:31:40 arch_desktop pulseaudio[975]: GetManagedObjects() failed: org.freedesktop.DBu
Mar 02 00:31:40 arch_desktop pulseaudio[997]: Daemon already running.
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Module "module-device-manager" should be loaded
Mar 02 00:31:40 arch_desktop pulseaudio[975]: snd_pcm_avail_delay() zwr<C3><B3>ci<C5><82>o dz
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Prawdopodobnie jest to b<C5><82><C4><85>d stero
Mar 02 00:31:40 arch_desktop pulseaudio[975]: snd_pcm_dump():
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Direct Snoop PCM
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Its setup is:
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   stream       : CAPTURE
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   access       : MMAP_INTERLEAVED
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   format       : S32_LE
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   subformat    : STD
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   channels     : 2
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   rate         : 48000
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   exact rate   : 48000 (48000/1)
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   msbits       : 32
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   buffer_size  : 16384
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_size  : 1024
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_time  : 21333
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   tstamp_mode  : ENABLE
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_step  : 1
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   avail_min    : 15943
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_event : 0
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   start_threshold  : -1
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   stop_threshold   : 4611686018427387904
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   silence_threshold: 0
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   silence_size : 0
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   boundary     : 4611686018427387904
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Hardware PCM card 0 'Creative X-Fi' device 0 su
Mar 02 00:31:40 arch_desktop pulseaudio[975]: Its setup is:
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   stream       : CAPTURE
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   access       : MMAP_INTERLEAVED
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   format       : S32_LE
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   subformat    : STD
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   channels     : 2
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   rate         : 48000
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   exact rate   : 48000 (48000/1)
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   msbits       : 32
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   buffer_size  : 16384
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_size  : 1024
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_time  : 21333
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   tstamp_mode  : ENABLE
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_step  : 1
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   avail_min    : 1024
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   period_event : 0
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   start_threshold  : 1
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   stop_threshold   : 4611686018427387904
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   silence_threshold: 0
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   silence_size : 0
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   boundary     : 4611686018427387904
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   appl_ptr     : 0
Mar 02 00:31:40 arch_desktop pulseaudio[975]:   hw_ptr       : 8200
Mar 02 00:31:40 arch_desktop sudo[1054]: pam_unix(sudo:auth): conversation failed
Mar 02 00:31:40 arch_desktop sudo[1054]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:31:46 arch_desktop baloo_file[819]: "/home/firekage/.TrueCrypt-lock-firekage"
Mar 02 00:31:46 arch_desktop baloo_file[819]: Normal
Mar 02 00:31:46 arch_desktop baloo_file[819]: "/home/firekage/.TrueCrypt-lock-firekage"
Mar 02 00:31:46 arch_desktop baloo_file[819]: 4585 "/home/firekage/.TrueCrypt-lock-firekage"
Mar 02 00:31:46 arch_desktop baloo_file[819]: Normal
Mar 02 00:31:49 arch_desktop sudo[1097]: pam_unix(sudo:auth): authentication failure; logname
Mar 02 00:31:51 arch_desktop sudo[1097]: pam_unix(sudo:auth): conversation failed
Mar 02 00:31:51 arch_desktop sudo[1097]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop5" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop5"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop7" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop7"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop1" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop1"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop2" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop2"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop3" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop3"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop4" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop4"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop6" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop6"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop0" 
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/loop0"
Mar 02 00:31:56 arch_desktop baloo_file[819]: QObject::connect: Cannot connect (null)::access
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d0"
Mar 02 00:31:56 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d0"
Mar 02 00:31:56 arch_desktop baloo_file[819]: true "/org/freedesktop/UDisks2/block_devices/dm
Mar 02 00:31:57 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d1"
Mar 02 00:31:57 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d1"
Mar 02 00:31:57 arch_desktop baloo_file[819]: true "/org/freedesktop/UDisks2/block_devices/dm
Mar 02 00:31:57 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d2"
Mar 02 00:31:57 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d2"
Mar 02 00:31:57 arch_desktop baloo_file[819]: true "/org/freedesktop/UDisks2/block_devices/dm
Mar 02 00:31:58 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d3"
Mar 02 00:31:58 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d3"
Mar 02 00:31:58 arch_desktop baloo_file[819]: true "/org/freedesktop/UDisks2/block_devices/dm
Mar 02 00:31:58 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d4"
Mar 02 00:31:58 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d4"
Mar 02 00:31:58 arch_desktop baloo_file[819]: true "/org/freedesktop/UDisks2/block_devices/dm
Mar 02 00:31:59 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d5"
Mar 02 00:31:59 arch_desktop baloo_file[819]: "/org/freedesktop/UDisks2/block_devices/dm_2d5"
Mar 02 00:31:59 arch_desktop baloo_file[819]: true "/org/freedesktop/UDisks2/block_devices/dm
Mar 02 00:32:10 arch_desktop sudo[1450]: pam_unix(sudo:auth): conversation failed
Mar 02 00:32:10 arch_desktop sudo[1450]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:32:24 arch_desktop konsole[1502]: QDBusConnection: session D-Bus connection created
Mar 02 00:32:24 arch_desktop konsole[1501]: QDBusConnection: session D-Bus connection created
Mar 02 00:32:24 arch_desktop konsole[1502]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:32:24 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:32:24 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:32:29 arch_desktop konsole[1637]: QDBusConnection: session D-Bus connection created
Mar 02 00:32:29 arch_desktop konsole[1636]: QDBusConnection: session D-Bus connection created
Mar 02 00:32:29 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:32:29 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:32:37 arch_desktop konsole[1502]: kf5.kservice.sycoca: Trying to open ksycoca from 
Mar 02 00:32:40 arch_desktop sudo[1808]: pam_unix(sudo:auth): conversation failed
Mar 02 00:32:40 arch_desktop sudo[1808]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:33:11 arch_desktop sudo[1932]: pam_unix(sudo:auth): conversation failed
Mar 02 00:33:11 arch_desktop sudo[1932]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:33:41 arch_desktop sudo[2057]: pam_unix(sudo:auth): conversation failed
Mar 02 00:33:41 arch_desktop sudo[2057]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:34:12 arch_desktop sudo[2190]: pam_unix(sudo:auth): conversation failed
Mar 02 00:34:12 arch_desktop sudo[2190]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:34:43 arch_desktop sudo[2352]: pam_unix(sudo:auth): conversation failed
Mar 02 00:34:43 arch_desktop sudo[2352]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:35:01 arch_desktop sSMTP[2432]: Creating SSL connection to host
Mar 02 00:35:01 arch_desktop sSMTP[2432]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Mar 02 00:35:04 arch_desktop sSMTP[2432]: Sent mail for firekage@gmail.com (221 2.0.0 closing
Mar 02 00:35:13 arch_desktop sudo[2498]: pam_unix(sudo:auth): conversation failed
Mar 02 00:35:13 arch_desktop sudo[2498]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:35:43 arch_desktop sudo[2737]: pam_unix(sudo:auth): conversation failed
Mar 02 00:35:43 arch_desktop sudo[2737]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:36:14 arch_desktop sudo[3088]: pam_unix(sudo:auth): conversation failed
Mar 02 00:36:14 arch_desktop sudo[3088]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:36:45 arch_desktop sudo[3218]: pam_unix(sudo:auth): conversation failed
Mar 02 00:36:45 arch_desktop sudo[3218]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:37:16 arch_desktop sudo[3354]: pam_unix(sudo:auth): conversation failed
Mar 02 00:37:16 arch_desktop sudo[3354]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:37:47 arch_desktop sudo[3481]: pam_unix(sudo:auth): conversation failed
Mar 02 00:37:47 arch_desktop sudo[3481]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:38:17 arch_desktop sudo[3603]: pam_unix(sudo:auth): conversation failed
Mar 02 00:38:17 arch_desktop sudo[3603]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:38:48 arch_desktop sudo[3728]: pam_unix(sudo:auth): conversation failed
Mar 02 00:38:48 arch_desktop sudo[3728]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:39:19 arch_desktop sudo[3852]: pam_unix(sudo:auth): conversation failed
Mar 02 00:39:19 arch_desktop sudo[3852]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:39:49 arch_desktop sudo[3974]: pam_unix(sudo:auth): conversation failed
Mar 02 00:39:49 arch_desktop sudo[3974]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:40:02 arch_desktop sSMTP[4019]: Creating SSL connection to host
Mar 02 00:40:02 arch_desktop sSMTP[4019]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Mar 02 00:40:05 arch_desktop sSMTP[4019]: Sent mail for firekage@gmail.com (221 2.0.0 closing
Mar 02 00:40:19 arch_desktop sudo[4103]: pam_unix(sudo:auth): conversation failed
Mar 02 00:40:19 arch_desktop sudo[4103]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:40:49 arch_desktop sudo[4231]: pam_unix(sudo:auth): conversation failed
Mar 02 00:40:49 arch_desktop sudo[4231]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:41:20 arch_desktop sudo[4355]: pam_unix(sudo:auth): conversation failed
Mar 02 00:41:20 arch_desktop sudo[4355]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:41:50 arch_desktop sudo[4492]: pam_unix(sudo:auth): conversation failed
Mar 02 00:41:50 arch_desktop sudo[4492]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:42:21 arch_desktop sudo[4618]: pam_unix(sudo:auth): conversation failed
Mar 02 00:42:21 arch_desktop sudo[4618]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:42:51 arch_desktop sudo[4740]: pam_unix(sudo:auth): conversation failed
Mar 02 00:42:51 arch_desktop sudo[4740]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:43:22 arch_desktop sudo[4866]: pam_unix(sudo:auth): conversation failed
Mar 02 00:43:22 arch_desktop sudo[4866]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:43:41 arch_desktop baloo_file[819]: Idle
Mar 02 00:43:41 arch_desktop baloo_file[819]: Created alarm 48234501
Mar 02 00:43:52 arch_desktop sudo[4987]: pam_unix(sudo:auth): conversation failed
Mar 02 00:43:52 arch_desktop sudo[4987]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:44:22 arch_desktop sudo[5110]: pam_unix(sudo:auth): conversation failed
Mar 02 00:44:22 arch_desktop sudo[5110]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:44:53 arch_desktop sudo[5234]: pam_unix(sudo:auth): conversation failed
Mar 02 00:44:53 arch_desktop sudo[5234]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:45:01 arch_desktop sSMTP[5267]: Creating SSL connection to host
Mar 02 00:45:01 arch_desktop sSMTP[5267]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Mar 02 00:45:05 arch_desktop sSMTP[5267]: Sent mail for firekage@gmail.com (221 2.0.0 closing
Mar 02 00:45:23 arch_desktop sudo[5364]: pam_unix(sudo:auth): conversation failed
Mar 02 00:45:23 arch_desktop sudo[5364]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:45:35 arch_desktop baloo_file[819]: Normal
Mar 02 00:45:54 arch_desktop sudo[5498]: pam_unix(sudo:auth): conversation failed
Mar 02 00:45:54 arch_desktop sudo[5498]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:46:24 arch_desktop sudo[5638]: pam_unix(sudo:auth): conversation failed
Mar 02 00:46:24 arch_desktop sudo[5638]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:46:55 arch_desktop sudo[5769]: pam_unix(sudo:auth): conversation failed
Mar 02 00:46:55 arch_desktop sudo[5769]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:47:26 arch_desktop sudo[5903]: pam_unix(sudo:auth): conversation failed
Mar 02 00:47:26 arch_desktop sudo[5903]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:47:56 arch_desktop sudo[6025]: pam_unix(sudo:auth): conversation failed
Mar 02 00:47:56 arch_desktop sudo[6025]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:48:26 arch_desktop sudo[6169]: pam_unix(sudo:auth): conversation failed
Mar 02 00:48:26 arch_desktop sudo[6169]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:48:57 arch_desktop sudo[6297]: pam_unix(sudo:auth): conversation failed
Mar 02 00:48:57 arch_desktop sudo[6297]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:49:27 arch_desktop sudo[6424]: pam_unix(sudo:auth): conversation failed
Mar 02 00:49:27 arch_desktop sudo[6424]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:49:58 arch_desktop sudo[6549]: pam_unix(sudo:auth): conversation failed
Mar 02 00:49:58 arch_desktop sudo[6549]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:50:01 arch_desktop sSMTP[6564]: Creating SSL connection to host
Mar 02 00:50:01 arch_desktop baloo_file[819]: "/home/firekage/.wine"
Mar 02 00:50:01 arch_desktop baloo_file[819]: Updating :  "/home/firekage/.wine"
Mar 02 00:50:01 arch_desktop baloo_file[819]: "/home/firekage/.wine"
Mar 02 00:50:01 arch_desktop baloo_file[819]: Normal
Mar 02 00:50:01 arch_desktop baloo_file[819]: Basic queue not empty, so no file queue.
Mar 02 00:50:01 arch_desktop baloo_file[819]: Normal
Mar 02 00:50:01 arch_desktop sSMTP[6564]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Mar 02 00:50:04 arch_desktop sSMTP[6564]: Sent mail for firekage@gmail.com (221 2.0.0 closing
Mar 02 00:50:25 arch_desktop konsole[6732]: QDBusConnection: session D-Bus connection created
Mar 02 00:50:25 arch_desktop konsole[6731]: QDBusConnection: session D-Bus connection created
Mar 02 00:50:25 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:50:25 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:50:28 arch_desktop sudo[6880]: pam_unix(sudo:auth): conversation failed
Mar 02 00:50:28 arch_desktop sudo[6880]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:50:59 arch_desktop sudo[7007]: pam_unix(sudo:auth): conversation failed
Mar 02 00:50:59 arch_desktop sudo[7007]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:51:30 arch_desktop sudo[7138]: pam_unix(sudo:auth): conversation failed
Mar 02 00:51:30 arch_desktop sudo[7138]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:52:01 arch_desktop sudo[7269]: pam_unix(sudo:auth): conversation failed
Mar 02 00:52:01 arch_desktop sudo[7269]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:52:14 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: 1 instance(s) monitoring 
Mar 02 00:52:14 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting cr
Mar 02 00:52:21 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting de
Mar 02 00:52:21 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting de
Mar 02 00:52:21 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting de
Mar 02 00:52:22 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting de
Mar 02 00:52:22 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: 1 instance(s) monitoring 
Mar 02 00:52:22 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting cr
Mar 02 00:52:22 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: 1 instance(s) monitoring 
Mar 02 00:52:22 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting de
Mar 02 00:52:22 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-3" emitting cr
Mar 02 00:52:31 arch_desktop sudo[7429]: pam_unix(sudo:auth): conversation failed
Mar 02 00:52:31 arch_desktop sudo[7429]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:52:32 arch_desktop kdeinit5[792]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pi
Mar 02 00:52:32 arch_desktop kbuildsycoca5[7439]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:52:32 arch_desktop kbuildsycoca5[7439]: kf5.kservice.sycoca: Trying to open ksycoca
Mar 02 00:52:32 arch_desktop kbuildsycoca5[7439]: Reusing existing ksycoca
Mar 02 00:52:32 arch_desktop kbuildsycoca5[7439]: Recreating ksycoca file ("/home/firekage/.c
Mar 02 00:52:33 arch_desktop kbuildsycoca5[7439]: Still in the time dict (i.e. deleted files)
Mar 02 00:52:33 arch_desktop org.kde.kded5[639]: kbuildsycoca5 running...
Mar 02 00:52:33 arch_desktop kbuildsycoca5[7439]: Menu "applications-kmenuedit.menu" not foun
Mar 02 00:52:33 arch_desktop kbuildsycoca5[7439]: Saving
Mar 02 00:52:33 arch_desktop kbuildsycoca5[7439]: Emitting notifyDatabaseChanged ("apps")
Mar 02 00:52:33 arch_desktop kded5[785]: kf5.kservice.sycoca: Trying to open ksycoca from "/h
Mar 02 00:52:58 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-4" emitting de
Mar 02 00:52:58 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: 1 instance(s) monitoring 
Mar 02 00:52:58 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-4" emitting cr
Mar 02 00:52:58 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: 1 instance(s) monitoring 
Mar 02 00:52:58 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-4" emitting de
Mar 02 00:52:58 arch_desktop kded5[785]: kf5.kcoreaddons.kdirwatch: "KDirWatch-4" emitting cr
Mar 02 00:53:02 arch_desktop sudo[7569]: pam_unix(sudo:auth): conversation failed
Mar 02 00:53:02 arch_desktop sudo[7569]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:53:05 arch_desktop baloo_file[819]: "/home/firekage/.bash_history"
Mar 02 00:53:05 arch_desktop baloo_file[819]: Normal
Mar 02 00:53:08 arch_desktop kdeinit5[792]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pi
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: Could not find drkonqi at /usr/lib/drkonqi
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: kf5.kservice.sycoca: Trying to open ksycoca
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: Reusing existing ksycoca
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: Recreating ksycoca file ("/home/firekage/.c
Mar 02 00:53:09 arch_desktop org.kde.kded5[639]: kbuildsycoca5 running...
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: Still in the time dict (i.e. deleted files)
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: Menu "applications-kmenuedit.menu" not foun
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: Saving
Mar 02 00:53:09 arch_desktop kbuildsycoca5[7595]: Emitting notifyDatabaseChanged ("apps")
Mar 02 00:53:09 arch_desktop kded5[785]: kf5.kservice.sycoca: Trying to open ksycoca from "/h
Mar 02 00:53:33 arch_desktop sudo[7707]: pam_unix(sudo:auth): conversation failed
Mar 02 00:53:33 arch_desktop sudo[7707]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:54:03 arch_desktop sudo[7828]: pam_unix(sudo:auth): conversation failed
Mar 02 00:54:03 arch_desktop sudo[7828]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:54:34 arch_desktop sudo[7962]: pam_unix(sudo:auth): conversation failed
Mar 02 00:54:34 arch_desktop sudo[7962]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:55:01 arch_desktop sSMTP[8061]: Creating SSL connection to host
Mar 02 00:55:02 arch_desktop sSMTP[8061]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Mar 02 00:55:05 arch_desktop sSMTP[8061]: Sent mail for firekage@gmail.com (221 2.0.0 closing
Mar 02 00:55:05 arch_desktop sudo[8122]: pam_unix(sudo:auth): conversation failed
Mar 02 00:55:05 arch_desktop sudo[8122]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:55:36 arch_desktop sudo[8248]: pam_unix(sudo:auth): conversation failed
Mar 02 00:55:36 arch_desktop sudo[8248]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:55:55 arch_desktop konsole[8309]: QDBusConnection: session D-Bus connection created
Mar 02 00:55:55 arch_desktop konsole[8308]: QDBusConnection: session D-Bus connection created
Mar 02 00:55:55 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:55:55 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Mar 02 00:56:06 arch_desktop sudo[8489]: pam_unix(sudo:auth): conversation failed
Mar 02 00:56:06 arch_desktop sudo[8489]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 00:56:37 arch_desktop sudo[8618]: pam_unix(sudo:auth): conversation failed
Mar 02 00:56:37 arch_desktop sudo[8618]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 01:01:00 arch_desktop systemd[618]: Time has been changed
Mar 02 01:01:20 arch_desktop sSMTP[8703]: Creating SSL connection to host
Mar 02 01:01:20 arch_desktop sSMTP[8703]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Mar 02 01:01:23 arch_desktop sSMTP[8703]: Sent mail for firekage@gmail.com (221 2.0.0 closing
Mar 02 01:01:26 arch_desktop sudo[8762]: pam_unix(sudo:auth): conversation failed
Mar 02 01:01:26 arch_desktop sudo[8762]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 01:01:57 arch_desktop sudo[8890]: pam_unix(sudo:auth): conversation failed
Mar 02 01:01:57 arch_desktop sudo[8890]: pam_unix(sudo:auth): auth could not identify passwor
Mar 02 01:02:28 arch_desktop sudo[9015]: pam_unix(sudo:auth): conversation failed
Mar 02 01:02:28 arch_desktop sudo[9015]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:01:00 arch_desktop systemd[618]: Time has been changed
Jan 30 01:01:28 arch_desktop sudo[9152]: pam_unix(sudo:auth): conversation failed
Jan 30 01:01:28 arch_desktop sudo[9152]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:01:59 arch_desktop sudo[9293]: pam_unix(sudo:auth): conversation failed
Jan 30 01:01:59 arch_desktop sudo[9293]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:02:29 arch_desktop sudo[9417]: pam_unix(sudo:auth): conversation failed
Jan 30 01:02:29 arch_desktop sudo[9417]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:03:00 arch_desktop sudo[9551]: pam_unix(sudo:auth): conversation failed
Jan 30 01:03:00 arch_desktop sudo[9551]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:03:30 arch_desktop sudo[9680]: pam_unix(sudo:auth): conversation failed
Jan 30 01:03:30 arch_desktop sudo[9680]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:04:00 arch_desktop sudo[9802]: pam_unix(sudo:auth): conversation failed
Jan 30 01:04:00 arch_desktop sudo[9802]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:04:31 arch_desktop sudo[9927]: pam_unix(sudo:auth): conversation failed
Jan 30 01:04:31 arch_desktop sudo[9927]: pam_unix(sudo:auth): auth could not identify passwor
Jan 30 01:05:01 arch_desktop sSMTP[10027]: Creating SSL connection to host
Jan 30 01:05:02 arch_desktop sSMTP[10027]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Jan 30 01:05:02 arch_desktop sudo[10060]: pam_unix(sudo:auth): conversation failed
Jan 30 01:05:02 arch_desktop sudo[10060]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:05:05 arch_desktop sSMTP[10027]: Sent mail for firekage@gmail.com (221 2.0.0 closin
Jan 30 01:05:33 arch_desktop sudo[10184]: pam_unix(sudo:auth): conversation failed
Jan 30 01:05:33 arch_desktop sudo[10184]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:06:04 arch_desktop sudo[10308]: pam_unix(sudo:auth): conversation failed
Jan 30 01:06:04 arch_desktop sudo[10308]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:06:35 arch_desktop sudo[10441]: pam_unix(sudo:auth): conversation failed
Jan 30 01:06:35 arch_desktop sudo[10441]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:07:05 arch_desktop sudo[10563]: pam_unix(sudo:auth): conversation failed
Jan 30 01:07:05 arch_desktop sudo[10563]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:07:36 arch_desktop sudo[10687]: pam_unix(sudo:auth): conversation failed
Jan 30 01:07:36 arch_desktop sudo[10687]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:08:07 arch_desktop sudo[10812]: pam_unix(sudo:auth): conversation failed
Jan 30 01:08:07 arch_desktop sudo[10812]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:08:38 arch_desktop sudo[10937]: pam_unix(sudo:auth): conversation failed
Jan 30 01:08:38 arch_desktop sudo[10937]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:09:08 arch_desktop sudo[11059]: pam_unix(sudo:auth): conversation failed
Jan 30 01:09:08 arch_desktop sudo[11059]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:09:38 arch_desktop sudo[11180]: pam_unix(sudo:auth): conversation failed
Jan 30 01:09:38 arch_desktop sudo[11180]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:10:01 arch_desktop sSMTP[11255]: Creating SSL connection to host
Jan 30 01:10:01 arch_desktop sSMTP[11255]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Jan 30 01:10:04 arch_desktop sSMTP[11255]: Sent mail for firekage@gmail.com (221 2.0.0 closin
Jan 30 01:10:08 arch_desktop sudo[11309]: pam_unix(sudo:auth): conversation failed
Jan 30 01:10:08 arch_desktop sudo[11309]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:10:38 arch_desktop sudo[11431]: pam_unix(sudo:auth): conversation failed
Jan 30 01:10:38 arch_desktop sudo[11431]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:11:09 arch_desktop sudo[11555]: pam_unix(sudo:auth): conversation failed
Jan 30 01:11:09 arch_desktop sudo[11555]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:11:40 arch_desktop sudo[11682]: pam_unix(sudo:auth): conversation failed
Jan 30 01:11:40 arch_desktop sudo[11682]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:12:10 arch_desktop sudo[11804]: pam_unix(sudo:auth): conversation failed
Jan 30 01:12:10 arch_desktop sudo[11804]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:12:41 arch_desktop sudo[11928]: pam_unix(sudo:auth): conversation failed
Jan 30 01:12:41 arch_desktop sudo[11928]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:13:12 arch_desktop sudo[12052]: pam_unix(sudo:auth): conversation failed
Jan 30 01:13:12 arch_desktop sudo[12052]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:13:43 arch_desktop sudo[12177]: pam_unix(sudo:auth): conversation failed
Jan 30 01:13:43 arch_desktop sudo[12177]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:14:13 arch_desktop sudo[12298]: pam_unix(sudo:auth): conversation failed
Jan 30 01:14:13 arch_desktop sudo[12298]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:14:43 arch_desktop sudo[12420]: pam_unix(sudo:auth): conversation failed
Jan 30 01:14:43 arch_desktop sudo[12420]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:15:01 arch_desktop sSMTP[12483]: Creating SSL connection to host
Jan 30 01:15:02 arch_desktop sSMTP[12483]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Jan 30 01:15:05 arch_desktop sSMTP[12483]: Sent mail for firekage@gmail.com (221 2.0.0 closin
Jan 30 01:15:14 arch_desktop sudo[12552]: pam_unix(sudo:auth): conversation failed
Jan 30 01:15:14 arch_desktop sudo[12552]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:15:45 arch_desktop sudo[12676]: pam_unix(sudo:auth): conversation failed
Jan 30 01:15:45 arch_desktop sudo[12676]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:16:16 arch_desktop sudo[12800]: pam_unix(sudo:auth): conversation failed
Jan 30 01:16:16 arch_desktop sudo[12800]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:16:47 arch_desktop sudo[12924]: pam_unix(sudo:auth): conversation failed
Jan 30 01:16:47 arch_desktop sudo[12924]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:17:18 arch_desktop sudo[13048]: pam_unix(sudo:auth): conversation failed
Jan 30 01:17:18 arch_desktop sudo[13048]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:17:49 arch_desktop sudo[13172]: pam_unix(sudo:auth): conversation failed
Jan 30 01:17:49 arch_desktop sudo[13172]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:18:20 arch_desktop sudo[13297]: pam_unix(sudo:auth): conversation failed
Jan 30 01:18:20 arch_desktop sudo[13297]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:18:50 arch_desktop sudo[13418]: pam_unix(sudo:auth): conversation failed
Jan 30 01:18:50 arch_desktop sudo[13418]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:19:19 arch_desktop konsole[13515]: QDBusConnection: session D-Bus connection create
Jan 30 01:19:19 arch_desktop konsole[13514]: QDBusConnection: session D-Bus connection create
Jan 30 01:19:19 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Jan 30 01:19:19 arch_desktop konsole[1502]: The font for use in the terminal has not been mat
Jan 30 01:19:21 arch_desktop sudo[13659]: pam_unix(sudo:auth): conversation failed
Jan 30 01:19:21 arch_desktop sudo[13659]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:19:51 arch_desktop sudo[13787]: pam_unix(sudo:auth): conversation failed
Jan 30 01:19:51 arch_desktop sudo[13787]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:20:01 arch_desktop sSMTP[13827]: Creating SSL connection to host
Jan 30 01:20:01 arch_desktop sSMTP[13827]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Jan 30 01:20:05 arch_desktop sSMTP[13827]: Sent mail for firekage@gmail.com (221 2.0.0 closin
Jan 30 01:20:22 arch_desktop sudo[13923]: pam_unix(sudo:auth): conversation failed
Jan 30 01:20:22 arch_desktop sudo[13923]: pam_unix(sudo:auth): auth could not identify passwo
Jan 30 01:20:31 arch_desktop baloo_file[819]: "/home/firekage/.bash_history"
Jan 30 01:20:31 arch_desktop baloo_file[819]: Normal
Jan 30 01:20:42 arch_desktop baloo_file[819]: SQL Committed
Jan 30 01:20:43 arch_desktop kded5[785]: The X11 connection broke (error 1). Did the X11 serv
Jan 30 01:20:43 arch_desktop kdeinit5[791]: kdeinit5: Fatal IO error: client killed
Jan 30 01:20:43 arch_desktop kdeinit5[792]: The X11 connection broke (error 1). Did the X11 s
Jan 30 01:20:43 arch_desktop org.gtk.vfs.Daemon[639]: A connection to the bus can't be made
Jan 30 01:20:43 arch_desktop org.gtk.vfs.Daemon[639]: g_dbus_connection_real_closed: Remote p
Jan 30 01:20:43 arch_desktop org.kde.kded5[639]: klauncher: Exiting on signal 15
Jan 30 01:20:43 arch_desktop org.a11y.Bus[639]: g_dbus_connection_real_closed: Remote peer va
Jan 30 01:20:43 arch_desktop org.kde.kuiserver[639]: kuiserver: Fatal IO error: client killed
Jan 30 01:20:43 arch_desktop systemd[618]: Stopping Default.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopped target Default.
Jan 30 01:20:43 arch_desktop systemd[618]: Starting Shutdown.
Jan 30 01:20:43 arch_desktop systemd[618]: Reached target Shutdown.
Jan 30 01:20:43 arch_desktop systemd[618]: Starting Exit the Session...
Jan 30 01:20:43 arch_desktop systemd[618]: Stopping Basic System.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopped target Basic System.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopping Timers.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopped target Timers.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopping Paths.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopped target Paths.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopping Sockets.
Jan 30 01:20:43 arch_desktop systemd[618]: Stopped target Sockets.
Jan 30 01:20:43 arch_desktop systemd[619]: pam_unix(systemd-user:session): session closed for
Jan 30 01:20:43 arch_desktop systemd[618]: Received SIGRTMIN+24 from PID 14045 (kill).
lines 441-478/478 (END)

http://pastebin.com/yzhtY7y5

Forget to mention.

I have one doubt about uswsusp. In Archwiki in uswsusp faq there is something like:

SLEEP_MODULE=uswsusp

but the same thing is for one time written like that

SLEEP_MODULE=uswsusp

and for another time like that

SLEEP_MODULE="uswsusp"

Dont know if it is revelat to the matter. It is written with "" and without "" in two faqs about suspend and hibernate, pm-utils and suswsusp in archwiki.

Last edited by firekage (2015-02-09 00:20:09)

frank604 · 2015-02-09 00:16:51

This is the log for when suspend freezes for you? The date is jan 30-march 02? Read the archwiki and show us the journalctl that shows you doing systemctl suspend and getting the freeze

firekage · 2015-02-09 00:32:34

-- Logs begin at Tue 2015-01-20 02:52:00 CET, end at Tue 2015-02-24 19:07:22 CET. --
Feb 09 01:20:02 arch_desktop sSMTP[4030]: Creating SSL connection to host
Feb 09 01:20:02 arch_desktop sSMTP[4030]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:20:05 arch_desktop sudo[4073]: pam_unix(sudo:auth): conversation failed
Feb 09 01:20:05 arch_desktop sudo[4073]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:20:05 arch_desktop sSMTP[4030]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection lf3sm1543682lbc.2 - gsmtp) uid=1000 username=firekage outbytes=1321
Feb 09 01:20:36 arch_desktop sudo[4201]: pam_unix(sudo:auth): conversation failed
Feb 09 01:20:36 arch_desktop sudo[4201]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:21:07 arch_desktop sudo[4328]: pam_unix(sudo:auth): conversation failed
Feb 09 01:21:07 arch_desktop sudo[4328]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:21:38 arch_desktop sudo[4452]: pam_unix(sudo:auth): conversation failed
Feb 09 01:21:38 arch_desktop sudo[4452]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:22:09 arch_desktop sudo[4578]: pam_unix(sudo:auth): conversation failed
Feb 09 01:22:09 arch_desktop sudo[4578]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:22:39 arch_desktop sudo[4701]: pam_unix(sudo:auth): conversation failed
Feb 09 01:22:39 arch_desktop sudo[4701]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:23:10 arch_desktop sudo[4842]: pam_unix(sudo:auth): conversation failed
Feb 09 01:23:10 arch_desktop sudo[4842]: pam_unix(sudo:auth): auth could not identify password for [firekage]
-- Reboot --
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Sockets.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Sockets.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Timers.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Timers.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Paths.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Paths.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Basic System.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Basic System.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Default.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Default.
Feb 09 01:25:31 arch_desktop systemd[667]: Startup finished in 45ms.
Feb 09 01:25:37 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.activities: Starting the KDE Activity Manager daemon QDateTime("2015-02-09 01:25:37.353 CET Qt::LocalTime")
Feb 09 01:25:37 arch_desktop kded5[767]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:37 arch_desktop kded5[767]: Qt: Session management error: networkIdsList argument is NULL
Feb 09 01:25:37 arch_desktop kded5[767]: klauncher not running... launching kdeinit
Feb 09 01:25:37 arch_desktop kdeinit5[774]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:37 arch_desktop kdeinit5[774]: Qt: Session management error: networkIdsList argument is NULL
Feb 09 01:25:37 arch_desktop kdeinit5[774]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Feb 09 01:25:37 arch_desktop kdeinit5[774]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pid 776) up and running.
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:37 arch_desktop org.kde.kded5[688]: kbuildsycoca5 running...
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: checking file timestamps
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: timestamp changed: "/usr/share/kservicetypes5"
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Reusing existing ksycoca
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Recreating ksycoca file ("/home/firekage/.cache/ksycoca5", version 300)
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Still in the time dict (i.e. deleted files) ("apps")
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Menu "applications-kmenuedit.menu" not found.
Feb 09 01:25:38 arch_desktop kbuildsycoca5[776]: Saving
Feb 09 01:25:38 arch_desktop kbuildsycoca5[776]: Emitting notifyDatabaseChanged ("apps")
Feb 09 01:25:38 arch_desktop kded5[767]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kdeinit5[774]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kdeinit5[774]: kf5.kinit.klauncher: "/usr/lib/kf5/kconf_update" (pid 777) up and running.
Feb 09 01:25:38 arch_desktop kdeinit5[774]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pid 778) up and running.
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:38 arch_desktop org.kde.kded5[688]: kbuildsycoca5 running...
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Reusing existing ksycoca
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Recreating ksycoca file ("/home/firekage/.cache/ksycoca5", version 300)
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Still in the time dict (i.e. deleted files) ("apps")
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Menu "applications-kmenuedit.menu" not found.
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Saving
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Emitting notifyDatabaseChanged ("apps")
Feb 09 01:25:38 arch_desktop kded5[767]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [   OK   ] loaded:   "Szablony dzia<C5><82>a<C5><84>"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: Creating directory:  "/home/firekage/.local/share/kactivitymanagerd/resources/"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [   OK   ] loaded:   "Podajnik Sqlite"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [   OK   ] loaded:   "Share-Like-Connect"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[780]: Qt: Session management error: networkIdsList argument is NULL
Feb 09 01:25:39 arch_desktop baloo_file[794]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:39 arch_desktop baloo_file[794]: "/home/firekage/.local/share/baloo/file/" true
Feb 09 01:25:39 arch_desktop baloo_file[794]: "/home/firekage"
Feb 09 01:25:39 arch_desktop baloo_file[794]: "/home/firekage"
Feb 09 01:25:39 arch_desktop baloo_file[794]: Successfully opened connection to inotify: 25
Feb 09 01:25:40 arch_desktop baloo_file[794]: XSync seems available and ready
Feb 09 01:25:40 arch_desktop baloo_file[794]: XSync Inited
Feb 09 01:25:40 arch_desktop baloo_file[794]: Supported, init completed
Feb 09 01:25:40 arch_desktop baloo_file[794]: Normal
Feb 09 01:25:40 arch_desktop org.kde.kuiserver[688]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:40 arch_desktop org.kde.kuiserver[688]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:42 arch_desktop baloo_file[794]: "/home/firekage/.xsession-errors"
Feb 09 01:25:42 arch_desktop baloo_file[794]: Created alarm 37748737
Feb 09 01:25:42 arch_desktop baloo_file[794]: Normal
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Default and alternate sample rates are the same.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Default and alternate sample rates are the same.
Feb 09 01:25:45 arch_desktop baloo_file[794]: "/home/firekage/.esd_auth"
Feb 09 01:25:45 arch_desktop baloo_file[794]: Normal
Feb 09 01:25:45 arch_desktop pulseaudio[964]: Daemon already running.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Module "module-device-manager" should be loaded once at most. Refusing to load.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: snd_pcm_avail_delay() zwr<C3><B3>ci<C5><82>o dziwne warto<C5>ci: op<C3><B3><C5><BA>nienie 0 jest mniejsze ni<C5><BC> korzy<C5><C4><87> 12.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Prawdopodobnie jest to b<C5><82><C4><85>d sterownika ALSA "snd_ctxfi". Prosz<C4><99> zg<C5><82>osi<C4><87> ten problem programistom us<C5><82>ugi ALSA.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: snd_pcm_dump():
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Direct Snoop PCM
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Its setup is:
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stream       : CAPTURE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   access       : MMAP_INTERLEAVED
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   format       : S32_LE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   subformat    : STD
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   channels     : 2
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   rate         : 48000
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   exact rate   : 48000 (48000/1)
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   msbits       : 32
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   buffer_size  : 16384
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_size  : 1024
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_time  : 21333
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   tstamp_mode  : ENABLE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_step  : 1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   avail_min    : 15943
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_event : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   start_threshold  : -1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stop_threshold   : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_threshold: 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_size : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   boundary     : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Hardware PCM card 0 'Creative X-Fi' device 0 subdevice 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Its setup is:
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stream       : CAPTURE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   access       : MMAP_INTERLEAVED
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   format       : S32_LE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   subformat    : STD
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   channels     : 2
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   rate         : 48000
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   exact rate   : 48000 (48000/1)
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   msbits       : 32
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   buffer_size  : 16384
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_size  : 1024
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_time  : 21333
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   tstamp_mode  : ENABLE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_step  : 1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   avail_min    : 1024
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_event : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   start_threshold  : 1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stop_threshold   : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_threshold: 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_size : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   boundary     : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   appl_ptr     : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   hw_ptr       : 8212
Feb 09 01:25:45 arch_desktop sudo[976]: pam_unix(sudo:auth): conversation failed
Feb 09 01:25:45 arch_desktop sudo[976]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:25:49 arch_desktop konsole[997]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:49 arch_desktop konsole[993]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:49 arch_desktop konsole[997]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:49 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:25:49 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:26:15 arch_desktop sudo[1215]: pam_unix(sudo:auth): conversation failed
Feb 09 01:26:15 arch_desktop sudo[1215]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:28:02 arch_desktop systemd[667]: Time has been changed
Feb 09 01:28:15 arch_desktop sudo[1425]: pam_unix(sudo:auth): conversation failed
Feb 09 01:28:15 arch_desktop sudo[1425]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:28:19 arch_desktop konsole[1445]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:28:19 arch_desktop konsole[1441]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:28:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:28:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:28:44 arch_desktop sudo[1663]: pam_unix(sudo:auth): conversation failed
Feb 09 01:28:44 arch_desktop sudo[1663]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:29:00 arch_desktop konsole[997]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:29:15 arch_desktop sudo[1788]: pam_unix(sudo:auth): conversation failed
Feb 09 01:29:15 arch_desktop sudo[1788]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:29:46 arch_desktop sudo[1914]: pam_unix(sudo:auth): conversation failed
Feb 09 01:29:46 arch_desktop sudo[1914]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:30:01 arch_desktop sSMTP[1967]: Creating SSL connection to host
Feb 09 01:30:01 arch_desktop sSMTP[1967]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:30:04 arch_desktop sSMTP[1967]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection rn9sm1787240lbb.23 - gsmtp) uid=1000 username=firekage outbytes=895
Feb 09 01:30:17 arch_desktop sudo[2047]: pam_unix(sudo:auth): conversation failed
Feb 09 01:30:17 arch_desktop sudo[2047]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "[firekage@arch_desktop ~]$ LANG=C journalctl --since "2015-02-09 01:20" -- Logs begin at Tue 2015-01-20 02:52:00 CET, end at Tue 2015-02-24 19:07:22 CET. -- Feb 09 01:20
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Keywords Engine: Loading config...
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Web Shortcuts Enabled:  true
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Default Shortcut:  ""
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Keyword Delimiter:  :
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:47 arch_desktop sudo[2246]: pam_unix(sudo:auth): conversation failed
Feb 09 01:30:47 arch_desktop sudo[2246]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:31:17 arch_desktop sudo[2385]: pam_unix(sudo:auth): conversation failed
Feb 09 01:31:17 arch_desktop sudo[2385]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:31:19 arch_desktop konsole[2398]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:31:19 arch_desktop konsole[2397]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:31:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:31:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:31:48 arch_desktop sudo[2627]: pam_unix(sudo:auth): conversation failed
Feb 09 01:31:48 arch_desktop sudo[2627]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:32:18 arch_desktop sudo[2751]: pam_unix(sudo:auth): conversation failed
Feb 09 01:32:18 arch_desktop sudo[2751]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:32:48 arch_desktop sudo[2879]: pam_unix(sudo:auth): conversation failed
Feb 09 01:32:48 arch_desktop sudo[2879]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:33:19 arch_desktop sudo[3004]: pam_unix(sudo:auth): conversation failed
Feb 09 01:33:19 arch_desktop sudo[3004]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:33:50 arch_desktop sudo[3129]: pam_unix(sudo:auth): conversation failed
Feb 09 01:33:50 arch_desktop sudo[3129]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:34:21 arch_desktop sudo[3256]: pam_unix(sudo:auth): conversation failed
Feb 09 01:34:21 arch_desktop sudo[3256]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:34:52 arch_desktop sudo[3380]: pam_unix(sudo:auth): conversation failed
Feb 09 01:34:52 arch_desktop sudo[3380]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:34:59 arch_desktop baloo_file[794]: "/home/firekage/.bash_history"
Feb 09 01:34:59 arch_desktop baloo_file[794]: Normal
Feb 09 01:35:01 arch_desktop konsole[3413]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:35:01 arch_desktop konsole[3412]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:35:01 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:35:01 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:35:02 arch_desktop sSMTP[3532]: Creating SSL connection to host
Feb 09 01:35:02 arch_desktop sSMTP[3532]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:35:04 arch_desktop su[3545]: (to root) firekage on pts/3
Feb 09 01:35:04 arch_desktop su[3545]: pam_unix(su:session): session opened for user root by firekage(uid=1000)
Feb 09 01:35:06 arch_desktop sSMTP[3532]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection uh6sm1791561lac.5 - gsmtp) uid=1000 username=firekage outbytes=1576
Feb 09 01:35:22 arch_desktop sudo[3632]: pam_unix(sudo:auth): conversation failed
Feb 09 01:35:22 arch_desktop sudo[3632]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:35:52 arch_desktop sudo[3757]: pam_unix(sudo:auth): conversation failed
Feb 09 01:35:52 arch_desktop sudo[3757]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:36:23 arch_desktop sudo[3885]: pam_unix(sudo:auth): conversation failed
Feb 09 01:36:23 arch_desktop sudo[3885]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:36:54 arch_desktop sudo[4009]: pam_unix(sudo:auth): conversation failed
Feb 09 01:36:54 arch_desktop sudo[4009]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:37:25 arch_desktop sudo[4138]: pam_unix(sudo:auth): conversation failed
Feb 09 01:37:25 arch_desktop sudo[4138]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:37:31 arch_desktop su[3545]: pam_unix(su:session): session closed for user root
Feb 09 01:37:31 arch_desktop baloo_file[794]: "/home/firekage/.bash_history"
Feb 09 01:37:31 arch_desktop baloo_file[794]: Normal
Feb 09 01:37:33 arch_desktop konsole[4169]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:37:33 arch_desktop konsole[4168]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:37:33 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:37:33 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:37:37 arch_desktop su[4292]: (to root) firekage on pts/3
Feb 09 01:37:37 arch_desktop su[4292]: pam_unix(su:session): session opened for user root by firekage(uid=1000)
Feb 09 01:37:56 arch_desktop sudo[4383]: pam_unix(sudo:auth): conversation failed
Feb 09 01:37:56 arch_desktop sudo[4383]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:38:23 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "lut 09 01:25:28 arch_desktop polkitd[429]: Loading rules from directory /usr/share/polkit-1/r lut 09 01:25:28 arch_desktop polkitd[429]: Finished loading, compiling and 
Feb 09 01:38:27 arch_desktop sudo[4510]: pam_unix(sudo:auth): conversation failed
Feb 09 01:38:27 arch_desktop sudo[4510]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:38:58 arch_desktop su[4292]: pam_unix(su:session): session closed for user root
Feb 09 01:38:58 arch_desktop sudo[4641]: pam_unix(sudo:auth): conversation failed
Feb 09 01:38:58 arch_desktop sudo[4641]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:38:59 arch_desktop konsole[4651]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:38:59 arch_desktop konsole[4650]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:38:59 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:38:59 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:39:22 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "-- Logs begin at Tue 2015-01-20 02:52:00 CET, end at Tue 2015-02-24 19:07:22 CET. -- Feb 09 01:20:02 arch_desktop sSMTP[4030]: Creating SSL connection to host Feb 09 01:
Feb 09 01:39:28 arch_desktop sudo[4886]: pam_unix(sudo:auth): conversation failed
Feb 09 01:39:28 arch_desktop sudo[4886]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:39:35 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [ OK ] loaded: "Podajnik Sqlite" Feb 09 01:25:38 arch_desktop kactivitymanagerd[761
Feb 09 01:39:39 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [ OK ] loaded: "Podajnik Sqlite" Feb 09 01:25:38 arch_desktop kactivitymanagerd[761
Feb 09 01:39:51 arch_desktop baloo_file[794]: "/home/firekage/.bash_history"
Feb 09 01:39:51 arch_desktop baloo_file[794]: Normal
Feb 09 01:39:58 arch_desktop sudo[5007]: pam_unix(sudo:auth): conversation failed
Feb 09 01:39:58 arch_desktop sudo[5007]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:40:01 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "Feb 09 01:25:45 arch_desktop pulseaudio[914]: stop_threshold : 4611686018427387904 Feb 09 01:25:45 arch_desktop pulseaudio[914]: silence_threshold: 0 Feb 09 01:25:45 arc
Feb 09 01:40:01 arch_desktop sSMTP[5022]: Creating SSL connection to host
Feb 09 01:40:01 arch_desktop sSMTP[5022]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:40:04 arch_desktop sSMTP[5022]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection ba3sm1785567lbc.35 - gsmtp) uid=1000 username=firekage outbytes=1224
-- Reboot --

Last edited by firekage (2015-02-09 00:40:30)

frank604 · 2015-02-09 00:39:31

First of all your log is truncated, second of all, are you sure that this is the log with you doing systemctl suspend? There should be an entry like systemd-sleep: suspending system... or at least that is what I think.

firekage · 2015-02-09 00:41:38

frank604 wrote:

First of all your log is truncated, second of all, are you sure that this is the log with you doing systemctl suspend? There should be an entry like systemd-sleep: suspending system... or at least that is what I think.

I'm not an expert when comes to a journalctl, i added it again. I thing that --since does not work the way i was expecting.

-- Logs begin at Tue 2015-01-20 02:52:00 CET, end at Tue 2015-02-24 19:07:22 CET. --
Feb 09 01:20:02 arch_desktop sSMTP[4030]: Creating SSL connection to host
Feb 09 01:20:02 arch_desktop sSMTP[4030]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:20:05 arch_desktop sudo[4073]: pam_unix(sudo:auth): conversation failed
Feb 09 01:20:05 arch_desktop sudo[4073]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:20:05 arch_desktop sSMTP[4030]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection lf3sm1543682lbc.2 - gsmtp) uid=1000 username=firekage outbytes=1321
Feb 09 01:20:36 arch_desktop sudo[4201]: pam_unix(sudo:auth): conversation failed
Feb 09 01:20:36 arch_desktop sudo[4201]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:21:07 arch_desktop sudo[4328]: pam_unix(sudo:auth): conversation failed
Feb 09 01:21:07 arch_desktop sudo[4328]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:21:38 arch_desktop sudo[4452]: pam_unix(sudo:auth): conversation failed
Feb 09 01:21:38 arch_desktop sudo[4452]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:22:09 arch_desktop sudo[4578]: pam_unix(sudo:auth): conversation failed
Feb 09 01:22:09 arch_desktop sudo[4578]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:22:39 arch_desktop sudo[4701]: pam_unix(sudo:auth): conversation failed
Feb 09 01:22:39 arch_desktop sudo[4701]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:23:10 arch_desktop sudo[4842]: pam_unix(sudo:auth): conversation failed
Feb 09 01:23:10 arch_desktop sudo[4842]: pam_unix(sudo:auth): auth could not identify password for [firekage]
-- Reboot --
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Sockets.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Sockets.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Timers.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Timers.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Paths.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Paths.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Basic System.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Basic System.
Feb 09 01:25:31 arch_desktop systemd[667]: Starting Default.
Feb 09 01:25:31 arch_desktop systemd[667]: Reached target Default.
Feb 09 01:25:31 arch_desktop systemd[667]: Startup finished in 45ms.
Feb 09 01:25:37 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.activities: Starting the KDE Activity Manager daemon QDateTime("2015-02-09 01:25:37.353 CET Qt::LocalTime")
Feb 09 01:25:37 arch_desktop kded5[767]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:37 arch_desktop kded5[767]: Qt: Session management error: networkIdsList argument is NULL
Feb 09 01:25:37 arch_desktop kded5[767]: klauncher not running... launching kdeinit
Feb 09 01:25:37 arch_desktop kdeinit5[774]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:37 arch_desktop kdeinit5[774]: Qt: Session management error: networkIdsList argument is NULL
Feb 09 01:25:37 arch_desktop kdeinit5[774]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Feb 09 01:25:37 arch_desktop kdeinit5[774]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pid 776) up and running.
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:37 arch_desktop org.kde.kded5[688]: kbuildsycoca5 running...
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: checking file timestamps
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: timestamp changed: "/usr/share/kservicetypes5"
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Reusing existing ksycoca
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Recreating ksycoca file ("/home/firekage/.cache/ksycoca5", version 300)
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Still in the time dict (i.e. deleted files) ("apps")
Feb 09 01:25:37 arch_desktop kbuildsycoca5[776]: Menu "applications-kmenuedit.menu" not found.
Feb 09 01:25:38 arch_desktop kbuildsycoca5[776]: Saving
Feb 09 01:25:38 arch_desktop kbuildsycoca5[776]: Emitting notifyDatabaseChanged ("apps")
Feb 09 01:25:38 arch_desktop kded5[767]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kdeinit5[774]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kdeinit5[774]: kf5.kinit.klauncher: "/usr/lib/kf5/kconf_update" (pid 777) up and running.
Feb 09 01:25:38 arch_desktop kdeinit5[774]: kf5.kinit.klauncher: "/usr/bin/kbuildsycoca5" (pid 778) up and running.
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:38 arch_desktop org.kde.kded5[688]: kbuildsycoca5 running...
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Reusing existing ksycoca
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Recreating ksycoca file ("/home/firekage/.cache/ksycoca5", version 300)
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Still in the time dict (i.e. deleted files) ("apps")
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Menu "applications-kmenuedit.menu" not found.
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Saving
Feb 09 01:25:38 arch_desktop kbuildsycoca5[778]: Emitting notifyDatabaseChanged ("apps")
Feb 09 01:25:38 arch_desktop kded5[767]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [   OK   ] loaded:   "Szablony dzia<C5><82>a<C5><84>"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: Creating directory:  "/home/firekage/.local/share/kactivitymanagerd/resources/"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [   OK   ] loaded:   "Podajnik Sqlite"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [   OK   ] loaded:   "Share-Like-Connect"
Feb 09 01:25:38 arch_desktop kactivitymanagerd[780]: Qt: Session management error: networkIdsList argument is NULL
Feb 09 01:25:39 arch_desktop baloo_file[794]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:39 arch_desktop baloo_file[794]: "/home/firekage/.local/share/baloo/file/" true
Feb 09 01:25:39 arch_desktop baloo_file[794]: "/home/firekage"
Feb 09 01:25:39 arch_desktop baloo_file[794]: "/home/firekage"
Feb 09 01:25:39 arch_desktop baloo_file[794]: Successfully opened connection to inotify: 25
Feb 09 01:25:40 arch_desktop baloo_file[794]: XSync seems available and ready
Feb 09 01:25:40 arch_desktop baloo_file[794]: XSync Inited
Feb 09 01:25:40 arch_desktop baloo_file[794]: Supported, init completed
Feb 09 01:25:40 arch_desktop baloo_file[794]: Normal
Feb 09 01:25:40 arch_desktop org.kde.kuiserver[688]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:40 arch_desktop org.kde.kuiserver[688]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:42 arch_desktop baloo_file[794]: "/home/firekage/.xsession-errors"
Feb 09 01:25:42 arch_desktop baloo_file[794]: Created alarm 37748737
Feb 09 01:25:42 arch_desktop baloo_file[794]: Normal
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Default and alternate sample rates are the same.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Default and alternate sample rates are the same.
Feb 09 01:25:45 arch_desktop baloo_file[794]: "/home/firekage/.esd_auth"
Feb 09 01:25:45 arch_desktop baloo_file[794]: Normal
Feb 09 01:25:45 arch_desktop pulseaudio[964]: Daemon already running.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Module "module-device-manager" should be loaded once at most. Refusing to load.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: snd_pcm_avail_delay() zwr<C3><B3>ci<C5><82>o dziwne warto<C5>ci: op<C3><B3><C5><BA>nienie 0 jest mniejsze ni<C5><BC> korzy<C5><C4><87> 12.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Prawdopodobnie jest to b<C5><82><C4><85>d sterownika ALSA "snd_ctxfi". Prosz<C4><99> zg<C5><82>osi<C4><87> ten problem programistom us<C5><82>ugi ALSA.
Feb 09 01:25:45 arch_desktop pulseaudio[914]: snd_pcm_dump():
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Direct Snoop PCM
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Its setup is:
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stream       : CAPTURE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   access       : MMAP_INTERLEAVED
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   format       : S32_LE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   subformat    : STD
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   channels     : 2
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   rate         : 48000
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   exact rate   : 48000 (48000/1)
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   msbits       : 32
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   buffer_size  : 16384
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_size  : 1024
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_time  : 21333
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   tstamp_mode  : ENABLE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_step  : 1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   avail_min    : 15943
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_event : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   start_threshold  : -1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stop_threshold   : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_threshold: 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_size : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   boundary     : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Hardware PCM card 0 'Creative X-Fi' device 0 subdevice 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]: Its setup is:
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stream       : CAPTURE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   access       : MMAP_INTERLEAVED
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   format       : S32_LE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   subformat    : STD
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   channels     : 2
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   rate         : 48000
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   exact rate   : 48000 (48000/1)
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   msbits       : 32
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   buffer_size  : 16384
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_size  : 1024
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_time  : 21333
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   tstamp_mode  : ENABLE
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_step  : 1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   avail_min    : 1024
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   period_event : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   start_threshold  : 1
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   stop_threshold   : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_threshold: 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   silence_size : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   boundary     : 4611686018427387904
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   appl_ptr     : 0
Feb 09 01:25:45 arch_desktop pulseaudio[914]:   hw_ptr       : 8212
Feb 09 01:25:45 arch_desktop sudo[976]: pam_unix(sudo:auth): conversation failed
Feb 09 01:25:45 arch_desktop sudo[976]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:25:49 arch_desktop konsole[997]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:49 arch_desktop konsole[993]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:25:49 arch_desktop konsole[997]: Could not find drkonqi at /usr/lib/drkonqi
Feb 09 01:25:49 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:25:49 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:26:15 arch_desktop sudo[1215]: pam_unix(sudo:auth): conversation failed
Feb 09 01:26:15 arch_desktop sudo[1215]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:28:02 arch_desktop systemd[667]: Time has been changed
Feb 09 01:28:15 arch_desktop sudo[1425]: pam_unix(sudo:auth): conversation failed
Feb 09 01:28:15 arch_desktop sudo[1425]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:28:19 arch_desktop konsole[1445]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:28:19 arch_desktop konsole[1441]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:28:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:28:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:28:44 arch_desktop sudo[1663]: pam_unix(sudo:auth): conversation failed
Feb 09 01:28:44 arch_desktop sudo[1663]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:29:00 arch_desktop konsole[997]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/firekage/.cache/ksycoca5"
Feb 09 01:29:15 arch_desktop sudo[1788]: pam_unix(sudo:auth): conversation failed
Feb 09 01:29:15 arch_desktop sudo[1788]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:29:46 arch_desktop sudo[1914]: pam_unix(sudo:auth): conversation failed
Feb 09 01:29:46 arch_desktop sudo[1914]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:30:01 arch_desktop sSMTP[1967]: Creating SSL connection to host
Feb 09 01:30:01 arch_desktop sSMTP[1967]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:30:04 arch_desktop sSMTP[1967]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection rn9sm1787240lbb.23 - gsmtp) uid=1000 username=firekage outbytes=895
Feb 09 01:30:17 arch_desktop sudo[2047]: pam_unix(sudo:auth): conversation failed
Feb 09 01:30:17 arch_desktop sudo[2047]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "[firekage@arch_desktop ~]$ LANG=C journalctl --since "2015-02-09 01:20" -- Logs begin at Tue 2015-01-20 02:52:00 CET, end at Tue 2015-02-24 19:07:22 CET. -- Feb 09 01:20
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Keywords Engine: Loading config...
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Web Shortcuts Enabled:  true
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Default Shortcut:  ""
Feb 09 01:30:34 arch_desktop konsole[997]: org.kde.kurifilter-ikws: Keyword Delimiter:  :
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:34 arch_desktop kded5[767]: kf5.kded: Failed to load module for  "favicons"
Feb 09 01:30:47 arch_desktop sudo[2246]: pam_unix(sudo:auth): conversation failed
Feb 09 01:30:47 arch_desktop sudo[2246]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:31:17 arch_desktop sudo[2385]: pam_unix(sudo:auth): conversation failed
Feb 09 01:31:17 arch_desktop sudo[2385]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:31:19 arch_desktop konsole[2398]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:31:19 arch_desktop konsole[2397]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:31:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:31:19 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:31:48 arch_desktop sudo[2627]: pam_unix(sudo:auth): conversation failed
Feb 09 01:31:48 arch_desktop sudo[2627]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:32:18 arch_desktop sudo[2751]: pam_unix(sudo:auth): conversation failed
Feb 09 01:32:18 arch_desktop sudo[2751]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:32:48 arch_desktop sudo[2879]: pam_unix(sudo:auth): conversation failed
Feb 09 01:32:48 arch_desktop sudo[2879]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:33:19 arch_desktop sudo[3004]: pam_unix(sudo:auth): conversation failed
Feb 09 01:33:19 arch_desktop sudo[3004]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:33:50 arch_desktop sudo[3129]: pam_unix(sudo:auth): conversation failed
Feb 09 01:33:50 arch_desktop sudo[3129]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:34:21 arch_desktop sudo[3256]: pam_unix(sudo:auth): conversation failed
Feb 09 01:34:21 arch_desktop sudo[3256]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:34:52 arch_desktop sudo[3380]: pam_unix(sudo:auth): conversation failed
Feb 09 01:34:52 arch_desktop sudo[3380]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:34:59 arch_desktop baloo_file[794]: "/home/firekage/.bash_history"
Feb 09 01:34:59 arch_desktop baloo_file[794]: Normal
Feb 09 01:35:01 arch_desktop konsole[3413]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:35:01 arch_desktop konsole[3412]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:35:01 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:35:01 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:35:02 arch_desktop sSMTP[3532]: Creating SSL connection to host
Feb 09 01:35:02 arch_desktop sSMTP[3532]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:35:04 arch_desktop su[3545]: (to root) firekage on pts/3
Feb 09 01:35:04 arch_desktop su[3545]: pam_unix(su:session): session opened for user root by firekage(uid=1000)
Feb 09 01:35:06 arch_desktop sSMTP[3532]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection uh6sm1791561lac.5 - gsmtp) uid=1000 username=firekage outbytes=1576
Feb 09 01:35:22 arch_desktop sudo[3632]: pam_unix(sudo:auth): conversation failed
Feb 09 01:35:22 arch_desktop sudo[3632]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:35:52 arch_desktop sudo[3757]: pam_unix(sudo:auth): conversation failed
Feb 09 01:35:52 arch_desktop sudo[3757]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:36:23 arch_desktop sudo[3885]: pam_unix(sudo:auth): conversation failed
Feb 09 01:36:23 arch_desktop sudo[3885]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:36:54 arch_desktop sudo[4009]: pam_unix(sudo:auth): conversation failed
Feb 09 01:36:54 arch_desktop sudo[4009]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:37:25 arch_desktop sudo[4138]: pam_unix(sudo:auth): conversation failed
Feb 09 01:37:25 arch_desktop sudo[4138]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:37:31 arch_desktop su[3545]: pam_unix(su:session): session closed for user root
Feb 09 01:37:31 arch_desktop baloo_file[794]: "/home/firekage/.bash_history"
Feb 09 01:37:31 arch_desktop baloo_file[794]: Normal
Feb 09 01:37:33 arch_desktop konsole[4169]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:37:33 arch_desktop konsole[4168]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:37:33 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:37:33 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:37:37 arch_desktop su[4292]: (to root) firekage on pts/3
Feb 09 01:37:37 arch_desktop su[4292]: pam_unix(su:session): session opened for user root by firekage(uid=1000)
Feb 09 01:37:56 arch_desktop sudo[4383]: pam_unix(sudo:auth): conversation failed
Feb 09 01:37:56 arch_desktop sudo[4383]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:38:23 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "lut 09 01:25:28 arch_desktop polkitd[429]: Loading rules from directory /usr/share/polkit-1/r lut 09 01:25:28 arch_desktop polkitd[429]: Finished loading, compiling and 
Feb 09 01:38:27 arch_desktop sudo[4510]: pam_unix(sudo:auth): conversation failed
Feb 09 01:38:27 arch_desktop sudo[4510]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:38:58 arch_desktop su[4292]: pam_unix(su:session): session closed for user root
Feb 09 01:38:58 arch_desktop sudo[4641]: pam_unix(sudo:auth): conversation failed
Feb 09 01:38:58 arch_desktop sudo[4641]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:38:59 arch_desktop konsole[4651]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:38:59 arch_desktop konsole[4650]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Feb 09 01:38:59 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:38:59 arch_desktop konsole[997]: The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
Feb 09 01:39:22 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "-- Logs begin at Tue 2015-01-20 02:52:00 CET, end at Tue 2015-02-24 19:07:22 CET. -- Feb 09 01:20:02 arch_desktop sSMTP[4030]: Creating SSL connection to host Feb 09 01:
Feb 09 01:39:28 arch_desktop sudo[4886]: pam_unix(sudo:auth): conversation failed
Feb 09 01:39:28 arch_desktop sudo[4886]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:39:35 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [ OK ] loaded: "Podajnik Sqlite" Feb 09 01:25:38 arch_desktop kactivitymanagerd[761
Feb 09 01:39:39 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "Feb 09 01:25:38 arch_desktop kactivitymanagerd[761]: org.kde.kactivities.application: [ OK ] loaded: "Podajnik Sqlite" Feb 09 01:25:38 arch_desktop kactivitymanagerd[761
Feb 09 01:39:51 arch_desktop baloo_file[794]: "/home/firekage/.bash_history"
Feb 09 01:39:51 arch_desktop baloo_file[794]: Normal
Feb 09 01:39:58 arch_desktop sudo[5007]: pam_unix(sudo:auth): conversation failed
Feb 09 01:39:58 arch_desktop sudo[5007]: pam_unix(sudo:auth): auth could not identify password for [firekage]
Feb 09 01:40:01 arch_desktop konsole[997]: org.kde.kurlfilter-ikws: "Feb 09 01:25:45 arch_desktop pulseaudio[914]: stop_threshold : 4611686018427387904 Feb 09 01:25:45 arch_desktop pulseaudio[914]: silence_threshold: 0 Feb 09 01:25:45 arc
Feb 09 01:40:01 arch_desktop sSMTP[5022]: Creating SSL connection to host
Feb 09 01:40:01 arch_desktop sSMTP[5022]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 09 01:40:04 arch_desktop sSMTP[5022]: Sent mail for firekage@gmail.com (221 2.0.0 closing connection ba3sm1785567lbc.35 - gsmtp) uid=1000 username=firekage outbytes=1224
-- Reboot --

I do a sudo systemctl suspend in terminal (using pm-utils and uswsusp packages, i did set up according to archwiki).

Yes, i do it with systemctl hibernate

firekage@arch_desktop log]$ LANG=C cat pm-powersave.log
Running hook /usr/lib/pm-utils/power.d/hal-cd-polling false:

/usr/lib/pm-utils/power.d/hal-cd-polling false: success.
Running hook /etc/pm/power.d/harddrive false:

/etc/pm/power.d/harddrive false: success.
Running hook /usr/lib/pm-utils/power.d/intel-audio-powersave false:
Setting power savings for snd_hda_intel to 0...Done.

/usr/lib/pm-utils/power.d/intel-audio-powersave false: success.
Running hook /usr/lib/pm-utils/power.d/journal-commit false:
Setting journal commit time for / to 0...Done.
Setting journal commit time for /mnt/hd/3000GB_4_WCC4N6ZY0D8R to 0...Done.
Setting journal commit time for /mnt/hd/3000GB_3_WCC4N6APEALD to 0...Done.
Setting journal commit time for /mnt/hd/2000GB_2_W1E1WBW0 to 0...Done.
Setting journal commit time for /mnt/hd/2000GB_1_Z1E6H7Q4 to 0...Done.
Setting journal commit time for /mnt/hd/3000GB_2_WCC4NEKJ1RDK to 0...Done.
Setting journal commit time for /mnt/hd/3000GB_1_WCC4N4K44PDK to 0...Done.
Setting journal commit time for /mnt/hd/0680GB_F1_dane_ext4 to 0...Done.
Setting journal commit time for /var to 0...Done.
Setting journal commit time for /home to 0...Done.

/usr/lib/pm-utils/power.d/journal-commit false: success.
Running hook /usr/lib/pm-utils/power.d/laptop-mode false:
Laptop mode disabled.

/usr/lib/pm-utils/power.d/laptop-mode false: success.
Running hook /usr/lib/pm-utils/power.d/pcie_aspm false:
/usr/lib/pm-utils/power.d/pcie_aspm: linia 9: echo: błąd zapisu: Operacja niedozwolona

/usr/lib/pm-utils/power.d/pcie_aspm false: success.
Running hook /usr/lib/pm-utils/power.d/readahead false:
Setting readahead for /dev/sde3 to 256...Done.
Setting readahead for /dev/sdf1 to 256...Done.
Setting readahead for /dev/sdi3 to 256...Done.
Setting readahead for /dev/sdg1 to 256...Done.
Setting readahead for /dev/sdd1 to 256...Done.
Setting readahead for /dev/sdc1 to 256...Done.
Setting readahead for /dev/sdb1 to 256...Done.
Setting readahead for /dev/sda1 to 256...Done.
Setting readahead for /dev/sdi4 to 256...Done.
Setting readahead for /dev/sdh4 to 256...Done.
Setting readahead for /dev/sdh2 to 256...Done.
Setting readahead for /dev/sdh3 to 256...Done.

/usr/lib/pm-utils/power.d/readahead false: success.
Running hook /usr/lib/pm-utils/power.d/sata_alpm false:
Setting SATA APLM on host4 to max_performance...Done.
Setting SATA APLM on host5 to max_performance...Done.
Setting SATA APLM on host6 to max_performance...Done.
Setting SATA APLM on host7 to max_performance...Done.
Setting SATA APLM on host8 to max_performance...Done.
Setting SATA APLM on host9 to max_performance...Done.

/usr/lib/pm-utils/power.d/sata_alpm false: success.
Running hook /usr/lib/pm-utils/power.d/sched-powersave false:
**sched policy powersave OFF

/usr/lib/pm-utils/power.d/sched-powersave false: success.
Running hook /usr/lib/pm-utils/power.d/wireless false:

/usr/lib/pm-utils/power.d/wireless false: success.
Running hook /usr/lib/pm-utils/power.d/xfs_buffer false:

/usr/lib/pm-utils/power.d/xfs_buffer false: success.
[firekage@arch_desktop log]$

Edit: i did something more. I installed fresh arch without nvidia drivers, only mesa. I changed even kernel - 3.14 aka LTS. Suspend to ram does not work again. The same thing happen. System is freezed after switching to black screen with blinking cursor at the left right corner. What's more funny, i was able to hibernate (suspend to disk) with my current Arch but it is tricky - it freezes after writing to disk, had to press power off, and after switching it by forcing power off by switching it off, when i start it again, it resumes without problems...

Can something be done?

Edit. I wante to ask for one thing - it comes to my mind. I have these packages installed:

i have these packages installed:
extra/nvidia 346.35-5 [zainstalowano]
NVIDIA drivers for linux
xtra/nvidia-libgl 346.35-2 [zainstalowano]
NVIDIA drivers libraries symlinks
extra/nvidia-utils 346.35-2 [zainstalowano]
NVIDIA drivers utilities
extra/opencl-nvidia 346.35-2 [zainstalowano]
community/nvidia-cg-toolkit 3.1-3 [zainstalowano]
NVIDIA Cg libraries
multilib/lib32-libcl 1.1-1 [zainstalowano]
OpenCL library and ICD loader from NVIDIA (32-bit)
multilib/lib32-libvdpau 0.9-1 [zainstalowano]
Nvidia VDPAU library
ultilib/lib32-nvidia-cg-toolkit 3.1-4 [zainstalowano]
NVIDIA Cg libraries
multilib/lib32-nvidia-libgl 346.35-1 [zainstalowano]
NVIDIA drivers libraries symlinks (32-bit)
multilib/lib32-nvidia-utils 346.35-1 [zainstalowano]
NVIDIA drivers utilities (32-bit)
multilib/lib32-opencl-nvidia 346.35-1 [zainstalowano]
xtra/glu 9.0.0-3 [zainstalowano]
Mesa OpenGL Utility library
extra/mesa 10.4.3-1 [zainstalowano]
an open-source implementation of the OpenGL specification
extra/mesa-demos 8.2.0-4 [zainstalowano]
Mesa demos and tools
multilib/lib32-glu 9.0.0-2 [zainstalowano]
Mesa OpenGL utility library (32 bits)
multilib/lib32-libtxc_dxtn 1.0.1-5 [zainstalowano]
S3 Texture Compression (S3TC) library for Mesa (32-bit)
multilib/lib32-mesa 10.4.3-1 [zainstalowano]
an open-source implementation of the OpenGL specification (32-bit)
multilib/lib32-mesa-demos 8.2.0-2 [zainstalowano]
Mesa demos and tools (32-bit)

Do you thing that some of them could conflict with others? Maybe i should have only few of them, like nvidia, nvidia-utils, nvidia-headers and lastly mesa, nothing more?

Last edited by firekage (2015-02-10 16:27:16)

firekage · 2015-02-11 20:41:28

Sorry for refreshing but i would like to ask only for one thing - im near close enough to solve my problem.

What's strange, this link helped me a lot
https://help.ubuntu.com/community/Power … /Hibernate

Here they talk about this:
https://bugs.launchpad.net/ubuntu/+sour … bug/237458

/sys/power/disk needs "shutdown" instead of "platform"

They wrote:

swsusp

In Ubuntu, the default method of hibernation is to use swsusp which is built into the kernel. Gnome and pm-utils will use this method unless configured otherwise.

The way you manually trigger hibernation using this 'kernel' method is to write 'disk' to /sys/power/state. There are two modes of 'kernel' hibernation: platform and shutdown. If one does not work, you can try the other:

sudo -s
echo platform > /sys/power/disk
echo disk > /sys/power/state

Or:

sudo -s
echo shutdown > /sys/power/disk
echo disk > /sys/power/state

Platform is the default and recommended mode of hibernation. Unfortunately, the "platform" mode of hibernation does not work on some systems with a broken BIOS. In such cases the "shutdown" mode of hibernation might work.

I tried first this

cat /sys/power/disk 
[platform] shutdown reboot suspend 
[root@arch_desktop firekage]

I changed it with

echo shutdown > /sys/power/disk

than checked it again

[root@arch_desktop firekage]# cat /sys/power/disk 
platform [shutdown] reboot suspend

After it i did the last thing:

[root@arch_desktop firekage]# echo disk > /sys/power/state

My system was saved to swap partition, correctly shutted down, and after hitting space, was resumed correctly.

I thing that problem is with "platform" settings in /sys/power/disk. It is strange that overwriting it with settings in /etc/pm/config.d/config whre i put "SLEEP_MODE=shutdown" does not work. It must be done with the order that i posted here.

My question is: what to do to have selected "shtudown" instead "platform" mode in /sys/power/disk? Could somebody help? It is possible to add something to kernel line in grub? I think that my problem with suspending to ram are also because of "platform" not "shutdown".

Sorry for refreshing but i had to write it for You to see that. I'm near solving my problem with suspend to ram and disk. Could you help me? Don't have english word for describing how glad i'm that i nearly solved it.

I did another thing in order to find why i cant suspend to ram. I removed almost all of my hard disk drives (2x2TB Seagate F14, and 4x3TB WD Green EZRX) and...with removed suspend to ram with s2ram -f -a 1 works perfeclty, but as soon as i connedt these hard drives, it fails, freezes everything. Strange - maybe it is due to disable head parking for WD drives but suspend to disk works. Strange. Strange. Strange.

Last edited by firekage (2015-02-15 01:18:37)

Arch Linux

#1 2015-02-04 23:06:31

How to change [platform] mode to [shutdown] mode in /sys/power/disk

#2 2015-02-07 19:01:23

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#3 2015-02-07 19:45:13

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#4 2015-02-08 23:52:07

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#5 2015-02-08 23:52:59

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#6 2015-02-08 23:59:33

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#7 2015-02-09 00:13:42

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#8 2015-02-09 00:16:51

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#9 2015-02-09 00:32:34

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#10 2015-02-09 00:39:31

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#11 2015-02-09 00:41:38

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

#12 2015-02-11 20:41:28

Re: How to change [platform] mode to [shutdown] mode in /sys/power/disk

Board footer