You are not logged in.

#1 2016-03-08 21:41:05

Daviljoe193
Member
From: the boring old Fall River M.A
Registered: 2015-06-24
Posts: 36

[Solved] Can't use GPG, frozen TTY2-6 after first run.

Recently, GPG just stopped working all together, throwing this message...

gpg: AES encrypted data
gpg: waiting for lock (held by 4616) ...
gpg: waiting for lock (held by 4616) ...
gpg: waiting for lock (held by 4616) ...
gpg: waiting for lock (held by 4616) ...
gpg: waiting for lock (held by 4616) ...
gpg: waiting for lock (held by 4616) ...
gpg: waiting for lock (held by 4616) ...
gpg: waiting for lock (held by 4616) ...
^C
gpg: signal Interrupt caught ... exiting

...and immediately after running GPG, TTYs 2-6 just stop updating, and visually freeze at whatever they were at prior to running GPG, but still work afterwards (Can run commands like espeak, but the screen doesn't update.). This isn't happening on any of my other Arch Linux installs, and a quick Google search isn't providing anything helpful. Any and all help would be heavily appreciated. sad

EDIT: Forgot to mention, rebooting doesn't fix the issue.

Last edited by Daviljoe193 (2016-03-09 03:54:15)


I'm a noob, a noob that has installed Arch (And Gentoo.) several times on obscure hardware, and a noob that has used Linux exclusively for 6 years now, but I'm still just a noob.
Main Computer: Dell Inspiron 11 - 4GB ram, 500 GB spinning rust, plain Arch X86-64, UEFI

Offline

#2 2016-03-08 21:50:43

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,797

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

I would have been asking myself, what  is process 4616? 

ps -ef  | grep 4616

If you try it again, you will need use the new PID

Last edited by ewaller (2016-03-08 21:50:59)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2016-03-08 21:58:48

respiranto
Member
Registered: 2015-05-15
Posts: 479
Website

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

I actually sometimes experience the same symptoms - the "frozen" TTYs, though I cannot relate it to GPG.
I only use GPG in conjunction with Enigmail, whose invocation does not appear to correlate to this.

It's been happening for a few days now, however I have not found the time to look for the cause yet.

Offline

#4 2016-03-08 21:59:52

Daviljoe193
Member
From: the boring old Fall River M.A
Registered: 2015-06-24
Posts: 36

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

ewaller wrote:

I would have been asking myself, what  is process 4616? 

ps -ef  | grep 4616

If you try it again, you will need use the new PID

Nothing, just sees the grep process, and the PID stays the same after multiple reboots.

daviljo+ 31552 31277  0 16:54 pts/9    00:00:00 grep 4616

And I might've found the solution to get GPG to work, apparently there was a .lock file in .gnupg, and removing it made GPG work, but TTYs 2-6 are still frozen. Half solved. :\

EDIT: Spelling error, was typing this on my laptop whilst standing up, so it was inevitable.

Last edited by Daviljoe193 (2016-03-08 22:01:48)


I'm a noob, a noob that has installed Arch (And Gentoo.) several times on obscure hardware, and a noob that has used Linux exclusively for 6 years now, but I'm still just a noob.
Main Computer: Dell Inspiron 11 - 4GB ram, 500 GB spinning rust, plain Arch X86-64, UEFI

Offline

#5 2016-03-08 22:04:10

Daviljoe193
Member
From: the boring old Fall River M.A
Registered: 2015-06-24
Posts: 36

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

respiranto wrote:

I actually sometimes experience the same symptoms - the "frozen" TTYs, though I cannot relate it to GPG.
I only use GPG in conjunction with Enigmail, whose invocation does not appear to correlate to this.

It's been happening for a few days now, however I have not found the time to look for the cause yet.

Again, the TTYs only freeze AFTER running GPG, but work just fine prior, so there's definitely something happening with GPG to cause this.


I'm a noob, a noob that has installed Arch (And Gentoo.) several times on obscure hardware, and a noob that has used Linux exclusively for 6 years now, but I'm still just a noob.
Main Computer: Dell Inspiron 11 - 4GB ram, 500 GB spinning rust, plain Arch X86-64, UEFI

Offline

#6 2016-03-08 22:05:18

respiranto
Member
Registered: 2015-05-15
Posts: 479
Website

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

How exactly do you invocate gpg, so I could try to reproduce?

Offline

#7 2016-03-08 22:10:55

Daviljoe193
Member
From: the boring old Fall River M.A
Registered: 2015-06-24
Posts: 36

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

respiranto wrote:

How exactly do you invocate gpg, so I could try to reproduce?

Doesn't seem to matter how I run it, though I use GPG specifically for password storage/management, as a LastPass alternative...

echo -n `gpg -d ~/Desktop/GPGed\ Passwords/amazon\ password.gpg` | xclip -selection c.

I'm a noob, a noob that has installed Arch (And Gentoo.) several times on obscure hardware, and a noob that has used Linux exclusively for 6 years now, but I'm still just a noob.
Main Computer: Dell Inspiron 11 - 4GB ram, 500 GB spinning rust, plain Arch X86-64, UEFI

Offline

#8 2016-03-08 22:26:09

respiranto
Member
Registered: 2015-05-15
Posts: 479
Website

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

Unfortunately, I can not reproduce this by running `gpg -d somefile.gpg`.
I do not have xclip installed, though.

Offline

#9 2016-03-08 23:39:15

Daviljoe193
Member
From: the boring old Fall River M.A
Registered: 2015-06-24
Posts: 36

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

respiranto wrote:

Unfortunately, I can not reproduce this by running `gpg -d somefile.gpg`.
I do not have xclip installed, though.

Well, it seems to have only started after my laptop randomly shut down on me (GPG wasn't even in use when it happened.), and the weird thing is that the laptop didn't overheat or run out of battery power, and journalctl listed that it was a normal reboot, even though the laptop didn't actually reboot. Here's what journalctl says happened when the laptop decided being on was too much of a task to handle.

Mar 05 08:59:38 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:00:26 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:00:29 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:01:01 localhost CROND[23686]: (root) CMD (run-parts /etc/cron.hourly)
Mar 05 09:04:08 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:04:29 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:06:01 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:06:20 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:06:35 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:08:03 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:08:31 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:09:04 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:09:06 localhost kernel: caja[917]: segfault at c40000013e ip 0000000000556579 sp 00007ffc99c1e250 error 4 in caja[400000+1d4000]
Mar 05 09:09:06 localhost systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Mar 05 09:09:06 localhost systemd[1]: Started Process Core Dump (PID 23901/UID 0).
Mar 05 09:09:14 localhost systemd-coredump[23902]: Process 917 (caja) of user 1000 dumped core.
                                                   
                                                   Stack trace of thread 917:
                                                   #0  0x0000000000556579 caja_icon_canvas_item_get_image (caja)
                                                   #1  0x0000000000507305 n/a (caja)
                                                   #2  0x00007f2b4d989f45 g_closure_invoke (libgobject-2.0.so.0)
                                                   #3  0x00007f2b4d99bf91 n/a (libgobject-2.0.so.0)
                                                   #4  0x00007f2b4d9a4d2c g_signal_emit_valist (libgobject-2.0.so.0)
                                                   #5  0x00007f2b4d9a5525 g_signal_emit_by_name (libgobject-2.0.so.0)
                                                   #6  0x00007f2b4f03cf4a n/a (libgtk-x11-2.0.so.0)
                                                   #7  0x00000000004fa850 n/a (caja)
                                                   #8  0x00007f2b4ef06bbc n/a (libgtk-x11-2.0.so.0)
                                                   #9  0x00007f2b4d989f45 g_closure_invoke (libgobject-2.0.so.0)
                                                   #10 0x00007f2b4d99c53e n/a (libgobject-2.0.so.0)
                                                   #11 0x00007f2b4d9a47c9 g_signal_emit_valist (libgobject-2.0.so.0)
                                                   #12 0x00007f2b4d9a505f g_signal_emit (libgobject-2.0.so.0)
                                                   #13 0x00007f2b4f01e52c n/a (libgtk-x11-2.0.so.0)
                                                   #14 0x00007f2b4ef05354 gtk_propagate_event (libgtk-x11-2.0.so.0)
                                                   #15 0x00007f2b4ef0570b gtk_main_do_event (libgtk-x11-2.0.so.0)
                                                   #16 0x00007f2b4eb7a48c n/a (libgdk-x11-2.0.so.0)
                                                   #17 0x00007f2b4d6b5d87 g_main_context_dispatch (libglib-2.0.so.0)
                                                   #18 0x00007f2b4d6b5fe0 n/a (libglib-2.0.so.0)
                                                   #19 0x00007f2b4d6b6302 g_main_loop_run (libglib-2.0.so.0)
                                                   #20 0x00007f2b4ef04787 gtk_main (libgtk-x11-2.0.so.0)
                                                   #21 0x000000000044a4a1 main (caja)
                                                   #22 0x00007f2b4c509710 __libc_start_main (libc.so.6)
                                                   #23 0x000000000044a5a9 _start (caja)
                                                   
                                                   Stack trace of thread 997:
                                                   #0  0x00007f2b4c5c7c3d poll (libc.so.6)
                                                   #1  0x00007f2b4d6b5f7c n/a (libglib-2.0.so.0)
                                                   #2  0x00007f2b4d6b608c g_main_context_iteration (libglib-2.0.so.0)
                                                   #3  0x00007f2b4353325d n/a (libdconfsettings.so)
                                                   #4  0x00007f2b4d6dc795 n/a (libglib-2.0.so.0)
                                                   #5  0x00007f2b4c891424 start_thread (libpthread.so.0)
                                                   #6  0x00007f2b4c5d0cbd __clone (libc.so.6)
                                                   
                                                   Stack trace of thread 23896:
                                                   #0  0x00007f2b4c5cc7f9 syscall (libc.so.6)
                                                   #1  0x00007f2b4d6fa8aa g_cond_wait_until (libglib-2.0.so.0)
                                                   #2  0x00007f2b4d68aa19 n/a (libglib-2.0.so.0)
                                                   #3  0x00007f2b4d6dd106 n/a (libglib-2.0.so.0)
                                                   #4  0x00007f2b4d6dc795 n/a (libglib-2.0.so.0)
                                                   #5  0x00007f2b4c891424 start_thread (libpthread.so.0)
                                                   #6  0x00007f2b4c5d0cbd __clone (libc.so.6)
                                                   
                                                   Stack trace of thread 998:
                                                   #0  0x00007f2b4c5c7c3d poll (libc.so.6)
                                                   #1  0x00007f2b4d6b5f7c n/a (libglib-2.0.so.0)
                                                   #2  0x00007f2b4d6b608c g_main_context_iteration (libglib-2.0.so.0)
                                                   #3  0x00007f2b4d6b60c9 n/a (libglib-2.0.so.0)
                                                   #4  0x00007f2b4d6dc795 n/a (libglib-2.0.so.0)
                                                   #5  0x00007f2b4c891424 start_thread (libpthread.so.0)
                                                   #6  0x00007f2b4c5d0cbd __clone (libc.so.6)
                                                   
                                                   Stack trace of thread 999:
                                                   #0  0x00007f2b4c5c7c3d poll (libc.so.6)
                                                   #1  0x00007f2b4d6b5f7c n/a (libglib-2.0.so.0)
                                                   #2  0x00007f2b4d6b6302 g_main_loop_run (libglib-2.0.so.0)
                                                   #3  0x00007f2b4def8186 n/a (libgio-2.0.so.0)
                                                   #4  0x00007f2b4d6dc795 n/a (libglib-2.0.so.0)
                                                   #5  0x00007f2b4c891424 start_thread (libpthread.so.0)
                                                   #6  0x00007f2b4c5d0cbd __clone (libc.so.6)
                                                   
                                                   Stack trace of thread 23899:
                                                   #0  0x00007f2b4c5cc7f9 syscall (libc.so.6)
                                                   #1  0x00007f2b4d6fa8aa g_cond_wait_until (libglib-2.0.so.0)
                                                   #2  0x00007f2b4d68aa19 n/a (libglib-2.0.so.0)
                                                   #3  0x00007f2b4d6dd106 n/a (libglib-2.0.so.0)
                                                   #4  0x00007f2b4d6dc795 n/a (libglib-2.0.so.0)
                                                   #5  0x00007f2b4c891424 start_thread (libpthread.so.0)
                                                   #6  0x00007f2b4c5d0cbd __clone (libc.so.6)
                                                   
                                                   Stack trace of thread 23900:
                                                   #0  0x00007f2b4c5cc7f9 syscall (libc.so.6)
                                                   #1  0x00007f2b4d6fa8aa g_cond_wait_until (libglib-2.0.so.0)
                                                   #2  0x00007f2b4d68aa19 n/a (libglib-2.0.so.0)
                                                   #3  0x00007f2b4d6dd106 n/a (libglib-2.0.so.0)
                                                   #4  0x00007f2b4d6dc795 n/a (libglib-2.0.so.0)
                                                   #5  0x00007f2b4c891424 start_thread (libpthread.so.0)
                                                   #6  0x00007f2b4c5d0cbd __clone (libc.so.6)
Mar 05 09:09:48 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:09:57 localhost kernel: cyapa 0-0067: failed to read report data, (-121)
Mar 05 09:10:24 localhost dbus-daemon[858]: Activating service name='org.freedesktop.Notifications'
Mar 05 09:10:24 localhost dbus-daemon[858]: Successfully activated service 'org.freedesktop.Notifications'
-- Reboot --
Mar 05 09:19:53 localhost systemd-journald[165]: Runtime journal (/run/log/journal/) is 8.0M, max 194.8M, 186.8M free.
Mar 05 09:19:53 localhost systemd-journald[165]: System journal (/var/log/journal/) is 24.0M, max 24.0M, 0B free.
Mar 05 09:19:53 localhost systemd-journald[165]: Time spent on flushing to /var is 24.926ms for 2 entries.
Mar 05 09:19:53 localhost kernel: microcode: CPU0 microcode updated early to revision 0x1d, date = 2015-08-13
Mar 05 09:19:53 localhost kernel: Initializing cgroup subsys cpuset
Mar 05 09:19:53 localhost kernel: Initializing cgroup subsys cpu
Mar 05 09:19:53 localhost kernel: Initializing cgroup subsys cpuacct
Mar 05 09:19:53 localhost kernel: Linux version 4.4.3-1-ARCH (builduser@tobias) (gcc version 5.3.0 (GCC) ) #1 SMP PREEMPT Fri Feb 26 15:09:29 CET 2016
Mar 05 09:19:53 localhost kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/sda1 rw resume=/dev/sda2 tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_pci i915.semaphores=1 intel_idle.max_cstate=1

I'm guessing this was why the lock file got stuck there, but it still doesn't make sense, since again, GPG wasn't in use when this incident happened.


I'm a noob, a noob that has installed Arch (And Gentoo.) several times on obscure hardware, and a noob that has used Linux exclusively for 6 years now, but I'm still just a noob.
Main Computer: Dell Inspiron 11 - 4GB ram, 500 GB spinning rust, plain Arch X86-64, UEFI

Offline

#10 2016-03-09 02:10:06

branch
Member
Registered: 2014-03-16
Posts: 209

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

Look for stale lock files.

ls -l ~/.gnupg/*.lock

Any that are older than $(uptime) are stale and should be deleted.

Offline

#11 2016-03-09 03:53:55

Daviljoe193
Member
From: the boring old Fall River M.A
Registered: 2015-06-24
Posts: 36

Re: [Solved] Can't use GPG, frozen TTY2-6 after first run.

branch wrote:

Look for stale lock files.

ls -l ~/.gnupg/*.lock

Any that are older than $(uptime) are stale and should be deleted.

That worked (I mentioned trying that in this post), though I still don't get why this happened. After a reboot (Which I didn't try until just a couple minutes ago), GPG no longer visually locks TTY 2-6. I guess this is solved, though this doesn't really help out @respiranto with the frozen TTY issue. Hopefully he can find the source of the issue (Since it seems to be stemming from something else on his install.), because having no TTY access (Blindly typing in an invisible terminal doesn't count) really sucks. Anyway, I'm marking this as solved, many thanks to everybody who offered help.


I'm a noob, a noob that has installed Arch (And Gentoo.) several times on obscure hardware, and a noob that has used Linux exclusively for 6 years now, but I'm still just a noob.
Main Computer: Dell Inspiron 11 - 4GB ram, 500 GB spinning rust, plain Arch X86-64, UEFI

Offline

Board footer

Powered by FluxBB