Bug#941076: debsign crashes gnome on wayland session

2019-09-27 Thread Pirate Praveen 



On Wed, 25 Sep, 2019 at 13:33, Simon McVittie  wrote:

On Wed, 25 Sep 2019 at 17:23:30 +0530, Pirate Praveen wrote:



 On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen 


 wrote:
 > Let me try downgrading libgcr-base-3-1 and reproduce the crash.



 Do I need to install some -dbgsym packages?


Yes, please install at least gdb, libgcr-base-3-1-dbgsym and
libglib2.0-0-dbgsym (the versions corresponding to the libraries you
already have installed), then use

coredumpctl gdb 1648

to use gdb to inspect the core dump that was captured by
systemd-coredump. The stack traces printed by systemd-coredump are 
only

intended as a brief summary of the core dump, and detailed debugging
(including use of detached debug symbols) is outside the scope of
systemd-coredump itself.

For more details see .


 Attaching core dump.


FYI that's a stack trace, not a core dump. A core dump is a large 
binary
file, and is not usually useful or desirable to send to bugs (it is 
likely

to contain information that you would prefer to keep confidential).
You can get a more detailed stack trace from the core dump by using
gdb and -dbgsym packages, and that more detailed stack trace is what
maintainers will usually need to be able to act on crash reports.


sudo coredumpctl gdb 1660
thread apply all bt full
with set logging on

gdb.txt attached.

smcv



Thread 10 (Thread 0x7fe7cac4e700 (LWP 1672)):
#0  0x7fe7d662dd2f in __GI___poll (fds=0x7fe7bc001a10, nfds=4, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1  0x7fe7d73a50ae in g_main_context_poll (priority=, 
n_fds=4, fds=0x7fe7bc001a10, timeout=, context=0x7fe7bc00db30) 
at ../../../glib/gmain.c:4216
ret = 
errsv = 
poll_func = 0x7fe7d73b49f0 
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 4
allocated_nfds = 
fds = 0x7fe7bc001a10
#2  0x7fe7d73a50ae in g_main_context_iterate (context=0x7fe7bc00db30, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:3912
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 4
allocated_nfds = 
fds = 0x7fe7bc001a10
#3  0x7fe7d73a5413 in g_main_loop_run (loop=0x7fe7bc00dc20) at 
../../../glib/gmain.c:4111
__FUNCTION__ = "g_main_loop_run"
#4  0x7fe7d75e9676 in gdbus_shared_thread_func (user_data=0x7fe7bc00db00) 
at ../../../gio/gdbusprivate.c:279
data = 0x7fe7bc00db00
#5  0x7fe7d73cdd1d in g_thread_proxy (data=0x556f93cbaad0) at 
../../../glib/gthread.c:805
thread = 0x556f93cbaad0
__FUNCTION__ = "g_thread_proxy"
#6  0x7fe7d4fd3fb7 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140633516074752, 
-1980838052628451829, 140633524463902, 140633524463903, 140633516074752, 
140633516072000, 1967285514314788363, 1967245874865843723}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#7  0x7fe7d66382ef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fe7b3fff700 (LWP 1675)):
#0  0x7fe7d4fd9db5 in futex_wait_cancelable (private=0, expected=0, 
futex_word=0x556f93cd4d28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
__ret = -512
oldtype = 0
err = 
spin = 0
buffer = {__routine = 0x7fe7d4fd9b40 <__condvar_cleanup_waiting>, __arg 
= 0x7fe7b3ffea00, __canceltype = 0, __prev = 0x0}
cbuffer = {wseq = 0, cond = 0x556f93cd4d00, mutex = 0x556f93cd4cd8, 
private = 0}
err = 
g = 0
flags = 
g1_start = 
signals = 
result = 0
wseq = 0
seq = 0
private = 0
#1  0x7fe7d4fd9db5 in __pthread_cond_wait_common (abstime=0x0, 
mutex=0x556f93cd4cd8, cond=0x556f93cd4d00) at pthread_cond_wait.c:502
spin = 0
buffer = {__routine = 0x7fe7d4fd9b40 <__condvar_cleanup_waiting>, __arg 
= 0x7fe7b3ffea00, __canceltype = 0, __prev = 0x0}
cbuffer = {wseq = 0, cond = 0x556f93cd4d00, mutex = 0x556f93cd4cd8, 
private = 0}
err = 
g = 0
flags = 
g1_start = 
signals = 
result = 0
wseq = 0
seq = 0
private = 0
#2  0x7fe7d4fd9db5 in __pthread_cond_wait (cond=0x556f93cd4d00, 
mutex=0x556f93cd4cd8) at pthread_cond_wait.c:655
#3  0x7fe7c8734e63 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7fe7c8734bb7 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7fe7d4fd3fb7 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140633134069504, 
-1980838052628451829, 140722895835582, 140722895835583,

Bug#941076: debsign crashes gnome on wayland session

2019-09-25 Thread Simon McVittie 
On Wed, 25 Sep 2019 at 17:23:30 +0530, Pirate Praveen wrote:
> 
> 
> On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen 
> wrote:
> > Let me try downgrading libgcr-base-3-1 and reproduce the crash.

> Do I need to install some -dbgsym packages?

Yes, please install at least gdb, libgcr-base-3-1-dbgsym and
libglib2.0-0-dbgsym (the versions corresponding to the libraries you
already have installed), then use

coredumpctl gdb 1648

to use gdb to inspect the core dump that was captured by
systemd-coredump. The stack traces printed by systemd-coredump are only
intended as a brief summary of the core dump, and detailed debugging
(including use of detached debug symbols) is outside the scope of
systemd-coredump itself.

For more details see .

> Attaching core dump.

FYI that's a stack trace, not a core dump. A core dump is a large binary
file, and is not usually useful or desirable to send to bugs (it is likely
to contain information that you would prefer to keep confidential).
You can get a more detailed stack trace from the core dump by using
gdb and -dbgsym packages, and that more detailed stack trace is what
maintainers will usually need to be able to act on crash reports.

smcv

Bug#941076: debsign crashes gnome on wayland session

2019-09-25 Thread Pirate Praveen 



On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen 
 wrote:

Let me try downgrading libgcr-base-3-1 and reproduce the crash.


Attaching core dump. Do I need to install some -dbgsym packages?

Sep 25 17:10:18 andhaka systemd-coredump[3731]: Process 1648 (gnome-shell) of user 1001 dumped core.

Stack trace of thread 1648:
#0  0x7f34debe1468 n/a (libgcr-base-3.so.1)
#1  0x7f34de1858ee ffi_call_unix64 (libffi.so.6)
#2  0x7f34de1852bf ffi_call (libffi.so.6)
#3  0x7f34e064c6dc g_cclosure_marshal_generic (libgobject-2.0.so.0)
#4  0x7f34e064beb2 g_closure_invoke (libgobject-2.0.so.0)
#5  0x7f34e065f4d4 n/a (libgobject-2.0.so.0)
#6  0x7f34e066818f g_signal_emit_valist (libgobject-2.0.so.0)
#7  0x7f34e066881f g_signal_emit (libgobject-2.0.so.0)
#8  0x7f34debe13c7 n/a (libgcr-base-3.so.1)
#9  0x7f34debe28f3 n/a (libgcr-base-3.so.1)
#10 0x7f34e0797600 n/a (libgio-2.0.so.0)
#11 0x7f34e0562d8e g_main_context_dispatch (libglib-2.0.so.0)
#12 0x7f34e0563140 n/a (libglib-2.0.so.0)
#13 0x7f34e0563413 g_main_loop_run (libglib-2.0.so.0)
#14 0x7f34df973c6c meta_run (libmutter-5.so.0)
#15 0x560194238865 n/a (gnome-shell)
#16 0x7f34df722bbb __libc_start_main (libc.so.6)
#17 0x560194238a4a n/a (gnome-shell)

Stack trace of thread 1660:
#0  0x7f34df7ebd2f __poll (libc.so.6)
#1  0x7f34e05630ae n/a (libglib-2.0.so.0)
#2  0x7f34e0563413 g_main_loop_run (libglib-2.0.so.0)
#3  0x7f34e07a7676 n/a (libgio-2.0.so.0)
#4  0x7f34e058bd1d n/a (libglib-2.0.so.0)
#5  0x7f34de191fb7 start_thread (libpthread.so.0)
#6  0x7f34df7f62ef __clone (libc.so.6)

Stack trace of thread 1658:
#0  0x7f34df7ebd2f __poll (libc.so.6)
#1  0x7f34e05630ae n/a (libglib-2.0.so.0)
#2  0x7f34e05631cf g_main_context_iteration (libglib-2.0.so.0)
#3  0x7f34e0563221 n/a (libglib-2.0.so.0)
#4  0x7f34e058bd1d n/a (libglib-2.0.so.0)
#5  0x7f34de191fb7 start_thread (libpthread.so.0)
#6  0x7f34df7f62ef __clone (libc.so.6)

Stack trace of thread 1687:
#0  0x7f34de197db5 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x7f34dd7554ff _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2  0x7f34dd7556e5 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3  0x7f34dd4d2ef4 n/a (libmozjs-60.so.0)
#4  0x7f34dd4cda42 n/a (libmozjs-60.so.0)
#5  0x7f34de191fb7 start_thread (libpthread.so.0)
#6  0x7f34df7f62ef __clone (libc.so.6)

Stack trace of thread 1662:

Bug#941076: debsign crashes gnome on wayland session

2019-09-25 Thread Pirate Praveen 



On Wed, 25 Sep, 2019 at 08:54, Simon McVittie  wrote:

gnome-shell in experimental was compiled against gcr from unstable,
so a higher version in dpkg-shlibdeps wouldn't have helped here; and I
don't see any recent source changes that should have prompted a higher
build-dependency.

Not much has changed in gcr between 3.28 and 3.33 at all, although 
there

are some annotation fixes that might affect gnome-shell. Did you also
upgrade gir1.2-gcr-3, or just libgcr-base-3-1?



Just libgcr-base-3-1.

2019-09-25 11:51:40 status installed libglib2.0-0:amd64 2.62.0-1
2019-09-25 12:13:51 startup archives unpack
2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2
2019-09-25 12:13:52 status triggers-pending libc-bin:amd64 2.29-2
2019-09-25 12:13:52 status half-configured libgcr-base-3-1:amd64 
3.28.0-1

2019-09-25 12:13:52 status unpacked libgcr-base-3-1:amd64 3.28.0-1
2019-09-25 12:13:52 status half-installed libgcr-base-3-1:amd64 3.28.0-1
2019-09-25 12:13:53 status unpacked libgcr-base-3-1:amd64 3.33.4-2
2019-09-25 12:13:53 startup packages configure
2019-09-25 12:13:53 configure libgcr-base-3-1:amd64 3.33.4-2 
2019-09-25 12:13:53 status unpacked libgcr-base-3-1:amd64 3.33.4-2
2019-09-25 12:13:53 status half-configured libgcr-base-3-1:amd64 
3.33.4-2

2019-09-25 12:13:53 status installed libgcr-base-3-1:amd64 3.33.4-2
2019-09-25 12:13:53 trigproc libc-bin:amd64 2.29-2 
2019-09-25 12:13:53 status half-configured libc-bin:amd64 2.29-2
2019-09-25 12:13:53 status installed libc-bin:amd64 2.29-2



Which gcr-related packages did you upgrade in the transaction that
triggered these crashes? For example, did you upgrade gcr or 
libgcr-ui-3-1

from experimental?



See attached dpkg.log for the transaction that triggered the crash.


Which version of gnome-keyring did you have when this crash existed?



3.31.91-2 and 3.31.91-1 (both crashed, update did not fix the crash).

Presumably you already had gnome-settings-daemon 3.34.x from 
experimental

in order to satisfy gnome-shell's dependencies?



yes, 3.34.0-2

Are you able to get a backtrace from this crash? (If you install 
packages

from experimental, I would suggest installing systemd-coredump, or
corekeeper if you don't use systemd, so that you can get post-mortem
backtraces.)



Let me try downgrading libgcr-base-3-1 and reproduce the crash.


Thanks,
smcv


2019-09-22 19:12:17 startup archives unpack
2019-09-22 19:12:17 upgrade libc-l10n:all 2.28-4 2.29-2
2019-09-22 19:12:17 status half-configured libc-l10n:all 2.28-4
2019-09-22 19:12:17 status unpacked libc-l10n:all 2.28-4
2019-09-22 19:12:17 status half-installed libc-l10n:all 2.28-4
2019-09-22 19:12:18 status unpacked libc-l10n:all 2.29-2
2019-09-22 19:12:18 upgrade locales:all 2.28-8 2.29-2
2019-09-22 19:12:18 status half-configured locales:all 2.28-8
2019-09-22 19:12:18 status unpacked locales:all 2.28-8
2019-09-22 19:12:18 status half-installed locales:all 2.28-8
2019-09-22 19:12:18 status triggers-pending man-db:amd64 2.8.5-2
2019-09-22 19:12:18 status unpacked locales:all 2.29-2
2019-09-22 19:12:18 upgrade libc6:amd64 2.28-4 2.29-2
2019-09-22 19:12:18 status triggers-pending libc-bin:amd64 2.28-4
2019-09-22 19:12:18 status half-configured libc6:amd64 2.28-4
2019-09-22 19:12:18 status unpacked libc6:amd64 2.28-4
2019-09-22 19:12:18 status half-installed libc6:amd64 2.28-4
2019-09-22 19:12:19 status unpacked libc6:amd64 2.29-2
2019-09-22 19:12:19 startup packages configure
2019-09-22 19:12:19 configure libc6:amd64 2.29-2 
2019-09-22 19:12:19 status unpacked libc6:amd64 2.29-2
2019-09-22 19:12:19 status half-configured libc6:amd64 2.29-2
2019-09-22 19:12:22 status installed libc6:amd64 2.29-2
2019-09-22 19:12:22 startup archives unpack
2019-09-22 19:12:22 upgrade libc-bin:amd64 2.28-4 2.29-2
2019-09-22 19:12:22 status half-configured libc-bin:amd64 2.28-4
2019-09-22 19:12:22 status unpacked libc-bin:amd64 2.28-4
2019-09-22 19:12:22 status half-installed libc-bin:amd64 2.28-4
2019-09-22 19:12:22 status unpacked libc-bin:amd64 2.29-2
2019-09-22 19:12:22 startup packages configure
2019-09-22 19:12:22 configure libc-bin:amd64 2.29-2 
2019-09-22 19:12:22 status unpacked libc-bin:amd64 2.29-2
2019-09-22 19:12:22 status half-configured libc-bin:amd64 2.29-2
2019-09-22 19:12:24 status installed libc-bin:amd64 2.29-2
2019-09-22 19:12:24 startup archives unpack
2019-09-22 19:12:24 upgrade libc-dev-bin:amd64 2.28-4 2.29-2
2019-09-22 19:12:24 status half-configured libc-dev-bin:amd64 2.28-4
2019-09-22 19:12:24 status unpacked libc-dev-bin:amd64 2.28-4
2019-09-22 19:12:24 status half-installed libc-dev-bin:amd64 2.28-4
2019-09-22 19:12:24 status unpacked libc-dev-bin:amd64 2.29-2
2019-09-22 19:12:24 upgrade libc6-dev:amd64 2.28-4 2.29-2
2019-09-22 19:12:24 status half-configured libc6-dev:amd64 2.28-4
2019-09-22 19:12:24 status unpacked libc6-dev:amd64 2.28-4
2019-09-22 19:12:24 status half-installed libc6-dev:amd64 2.28-4
2019-09-22 19:12:25 status unpacked libc6-dev:amd64 2.29-2
2019-09-22

Bug#941076: debsign crashes gnome on wayland session

2019-09-25 Thread Simon McVittie 
On Wed, 25 Sep 2019 at 12:33:08 +0530, Pirate Praveen wrote:
> On Wed, 25 Sep, 2019 at 12:13, Pirate Praveen 
> wrote:
> > I think I found the relevant part from the log. Attaching log from the
> > point of crash.
> > 
> > Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip
> > 7f85dbfdf468 sp 7ffda39321c0 error 4 in
> > libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]
> > 
> 
> After upgrading libgcr-base-3-1, it does not crash anymore.
> 2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2
> 
> I tried rebooting and running debsign again. So probably gcr should bump its
> dependency version.

gnome-shell in experimental was compiled against gcr from unstable,
so a higher version in dpkg-shlibdeps wouldn't have helped here; and I
don't see any recent source changes that should have prompted a higher
build-dependency.

Not much has changed in gcr between 3.28 and 3.33 at all, although there
are some annotation fixes that might affect gnome-shell. Did you also
upgrade gir1.2-gcr-3, or just libgcr-base-3-1?

Which gcr-related packages did you upgrade in the transaction that
triggered these crashes? For example, did you upgrade gcr or libgcr-ui-3-1
from experimental?

Which version of gnome-keyring did you have when this crash existed?

Presumably you already had gnome-settings-daemon 3.34.x from experimental
in order to satisfy gnome-shell's dependencies?

Are you able to get a backtrace from this crash? (If you install packages
from experimental, I would suggest installing systemd-coredump, or
corekeeper if you don't use systemd, so that you can get post-mortem
backtraces.)

Thanks,
smcv

Bug#941076: debsign crashes gnome on wayland session

2019-09-25 Thread Pirate Praveen 




On Wed, 25 Sep, 2019 at 12:13, Pirate Praveen 
 wrote:
I think I found the relevant part from the log. Attaching log from 
the point of crash.


Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip 
7f85dbfdf468 sp 7ffda39321c0 error 4 in 
libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]




After upgrading libgcr-base-3-1, it does not crash anymore.
2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2

I tried rebooting and running debsign again. So probably gcr should 
bump its dependency version.

Bug#941076: debsign crashes gnome on wayland session

2019-09-25 Thread Pirate Praveen 
I think I found the relevant part from the log. Attaching log from the 
point of crash.


Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip 
7f85dbfdf468 sp 7ffda39321c0 error 4 in 
libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]


11:44:47 andhaka systemd[1532]: Started GnuPG cryptographic agent and passphrase cache.
Sep 25 11:44:47 andhaka gpg-agent[2869]: gpg-agent (GnuPG) 2.2.17 starting in supervised mode.
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 3 for std socket (/run/user/1001/gnupg/S.gpg-agent)
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 4 for browser socket (/run/user/1001/gnupg/S.gpg-agent.browser)
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 5 for ssh socket (/run/user/1001/gnupg/S.gpg-agent.ssh)
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 6 for extra socket (/run/user/1001/gnupg/S.gpg-agent.extra)
Sep 25 11:44:47 andhaka gpg-agent[2869]: listening on: std=3 extra=6 browser=4 ssh=5
Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip 7f85dbfdf468 sp 7ffda39321c0 error 4 in libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]
Sep 25 11:44:47 andhaka kernel: Code: 00 00 48 83 c4 28 5b 5d 41 5c 41 5d c3 0f 1f 44 00 00 48 8b 44 24 08 48 8d 15 74 13 03 00 48 8d 3d 5f b2 02 00 be 80 00 00 00 <4c> 8b 40 08 48 8b 08 31 c0 e8 6a 6d fe ff eb b4 0f 1f 84 00 00 00
Sep 25 11:44:47 andhaka gsd-keyboard[1701]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka evolution-alarm[1752]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmXsmpServer: ice_io_error_handler (0x55beb2fda320)
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmXsmpServer: ice_io_error_handler (0x55beb2fda320)
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmXSMPClient: IceProcessMessagesIOError on '0x55beb2feb880 [gnome-shell 10560d616c8277f60d15693920738597020016180069]'
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: unable to find application for client - not restarting
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmStore: Unreffing object: 0x55beb2feb880
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x55beb2feb880 [gnome-shell 10560d616c8277f60d15693920738597020016180069])
Sep 25 11:44:47 andhaka gsd-wacom[1690]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmXSMPClient: IceProcessMessagesIOError on '0x55beb2feb880 [gnome-shell 10560d616c8277f60d15693920738597020016180069]'
Sep 25 11:44:47 andhaka gsd-color[1671]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client
Sep 25 11:44:47 andhaka gnome-terminal-[2496]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka systemd[1532]: gsd-wacom.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmManager: unable to find application for client - not restarting
Sep 25 11:44:47 andhaka systemd[1532]: gsd-wacom.service: Failed with result 'exit-code'.
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client19
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect for app 'wacom'
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: unable to find application for client - not restarting
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmStore: Unreffing object: 0x7fcc78003420
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client19
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]:

Bug#941076: debsign crashes gnome on wayland session

2019-09-25 Thread Pirate Praveen 
From sudo journalctl -ab >journal.log Is there another specific thing 
I should check in the log?


Sep 25 11:18:09 andhaka gsd-keyboard[18299]: Unable to init server: 
Could not connect: Connection refused

Sep 25 11:18:09 andhaka gsd-keyboard[18299]: Cannot open display:
Sep 25 11:18:09 andhaka systemd[17334]: gsd-keyboard.service: Main 
process exited, code=exited, status=1/FAILURE
Sep 25 11:18:09 andhaka systemd[17334]: gsd-keyboard.service: Failed 
with result 'exit-code'.
Sep 25 11:18:09 andhaka systemd[17334]: Failed to start GNOME Keyboard 
handling.
Sep 25 11:18:09 andhaka systemd[17334]: Dependency failed for GNOME 
Keyboard handling.
Sep 25 11:18:09 andhaka systemd[17334]: gsd-keyboard.target: Job 
gsd-keyboard.target/start failed with result 'dependency'.
Sep 25 11:18:09 andhaka gnome-session-failed[18294]: Unable to init 
server: Could not connect: Connection refused

Sep 25 11:18:09 andhaka unknown[18294]: Cannot open display:
Sep 25 11:18:09 andhaka systemd[17334]: gnome-session-failed.service: 
Main process exited, code=exited, status=1/FAILURE
Sep 25 11:18:09 andhaka systemd[17334]: Stopped target GNOME Session 
Failed.

Bug#941076: debsign crashes gnome on wayland session

2019-09-24 Thread Pirate Praveen 




On Wed, 25 Sep, 2019 at 10:47, Pirate Praveen 
 wrote:



On Tue, 24 Sep, 2019 at 11:16, Simon McVittie  wrote:
Control: retitle -1 [GNOME 3.34] debsign crashes gnome on wayland 
session

Control: tags -1 + experimental moreinfo

On Tue, 24 Sep 2019 at 15:33:05 +0530, Pirate Praveen wrote:

 After updating gnome to 2.34


I'm fairly sure you mean 3.34. There was no GNOME 2.34 release: GNOME
2.32 was in 2010, and was followed by 3.0.



That was a typo, sorry about that, it is 3.34 indeed.

Key GNOME 3.34 components, including gnome-session and gnome-shell, 
are

currently only in experimental. You're welcome to try it, but please
make sure that bug reports are complete, precise and actionable.



Since this was a crash of the desktop I was not really sure which 
component this will belong to.



 I'm not able to use debsign, it crashes the
 desktop. I'm logged out after screen is blacked out.


Please send details of the package versions involved, and whatever
backtraces and system log entries are available.

For what it's worth, I have not experienced similar crashes when 
using
debsign and pinentry-gnome3 in conjunction with a smart card 
(Nitrokey

Pro) in either a GNOME 3.30 or 3.34 environment. I assume most of the
other people uploading GNOME 3.34 for the GNOME team are also using
debsign and pinentry-gnome3 in that environment.



I looked at apt list --upgradeable | grep gpg and upgraded all the 
components listed (earlier I tried to update all gnome components 
thinking it was an issue with gnome).


gpg-agent/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-client/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-server/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgconf/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgsm/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgv/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
libgpg-error-dev/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpg-error0/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpgme11/unstable 1.13.1-1 amd64 [upgradable from: 1.12.0-6]

After this upgrade there is no crash. pinentry-gnome3 has 
libgpg-error0 (>= 1.16) and I wonder if this should be bumped?




Though it did not crash in the same session, it crashed again after a 
reboot.


Versions of packages pinentry-gnome3 depends on:
ii  gcr  3.28.0-1
ii  libassuan0   2.5.1-2
ii  libc62.29-2
ii  libgcr-base-3-1  3.28.0-1
ii  libglib2.0-0 2.62.0-1
ii  libgpg-error01.36-7
ii  libncursesw6 6.1+20180210-4
ii  libsecret-1-00.18.6-2
ii  libtinfo66.1+20180210-4

Versions of packages pinentry-gnome3 recommends:
ii  dbus-user-session  1.12.8-3

Versions of packages gnome-session depends on:
ii  gnome-session-bin  3.34.0-1
ii  gnome-session-common   3.34.0-1
ii  gnome-settings-daemon  3.34.0-2
ii  gnome-shell3.34.0-1

gnome-session recommends no packages.

Versions of packages gnome-session suggests:
ii  desktop-base   10.0.3
ii  gnome-keyring  3.31.91-1


smcv

Bug#941076: debsign crashes gnome on wayland session

2019-09-24 Thread Pirate Praveen 




On Tue, 24 Sep, 2019 at 11:16, Simon McVittie  wrote:
Control: retitle -1 [GNOME 3.34] debsign crashes gnome on wayland 
session

Control: tags -1 + experimental moreinfo

On Tue, 24 Sep 2019 at 15:33:05 +0530, Pirate Praveen wrote:

 After updating gnome to 2.34


I'm fairly sure you mean 3.34. There was no GNOME 2.34 release: GNOME
2.32 was in 2010, and was followed by 3.0.



That was a typo, sorry about that, it is 3.34 indeed.

Key GNOME 3.34 components, including gnome-session and gnome-shell, 
are

currently only in experimental. You're welcome to try it, but please
make sure that bug reports are complete, precise and actionable.



Since this was a crash of the desktop I was not really sure which 
component this will belong to.



 I'm not able to use debsign, it crashes the
 desktop. I'm logged out after screen is blacked out.


Please send details of the package versions involved, and whatever
backtraces and system log entries are available.

For what it's worth, I have not experienced similar crashes when using
debsign and pinentry-gnome3 in conjunction with a smart card (Nitrokey
Pro) in either a GNOME 3.30 or 3.34 environment. I assume most of the
other people uploading GNOME 3.34 for the GNOME team are also using
debsign and pinentry-gnome3 in that environment.



I looked at apt list --upgradeable | grep gpg and upgraded all the 
components listed (earlier I tried to update all gnome components 
thinking it was an issue with gnome).


gpg-agent/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-client/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-server/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgconf/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgsm/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgv/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
libgpg-error-dev/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpg-error0/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpgme11/unstable 1.13.1-1 amd64 [upgradable from: 1.12.0-6]

After this upgrade there is no crash. pinentry-gnome3 has libgpg-error0 
(>= 1.16) and I wonder if this should be bumped?



smcv

Bug#941076: debsign crashes gnome on wayland session

2019-09-24 Thread Simon McVittie 
Control: retitle -1 [GNOME 3.34] debsign crashes gnome on wayland session
Control: tags -1 + experimental moreinfo

On Tue, 24 Sep 2019 at 15:33:05 +0530, Pirate Praveen wrote:
> After updating gnome to 2.34

I'm fairly sure you mean 3.34. There was no GNOME 2.34 release: GNOME
2.32 was in 2010, and was followed by 3.0.

Key GNOME 3.34 components, including gnome-session and gnome-shell, are
currently only in experimental. You're welcome to try it, but please
make sure that bug reports are complete, precise and actionable.

> I'm not able to use debsign, it crashes the
> desktop. I'm logged out after screen is blacked out.

Please send details of the package versions involved, and whatever
backtraces and system log entries are available.

For what it's worth, I have not experienced similar crashes when using
debsign and pinentry-gnome3 in conjunction with a smart card (Nitrokey
Pro) in either a GNOME 3.30 or 3.34 environment. I assume most of the
other people uploading GNOME 3.34 for the GNOME team are also using
debsign and pinentry-gnome3 in that environment.

smcv

Processed: Re: Bug#941076: debsign crashes gnome on wayland session

2019-09-24 Thread Debian Bug Tracking System 
Processing control commands:

> retitle -1 [GNOME 3.34] debsign crashes gnome on wayland session
Bug #941076 [gnome-session,pinentry-gnome3] debsign crashes gnome on wayland 
session
Changed Bug title to '[GNOME 3.34] debsign crashes gnome on wayland session' 
from 'debsign crashes gnome on wayland session'.
> tags -1 + experimental moreinfo
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
Added tag(s) moreinfo and experimental.

-- 
941076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#941076: debsign crashes gnome on wayland session

2019-09-24 Thread Pirate Praveen 

Package: gnome-session,pinentry-gnome3
severity: critical

After updating gnome to 2.34 I'm not able to use debsign, it crashes 
the desktop. I'm logged out after screen is blacked out. Tried updating 
task-gnome-desktop and *wayland* packages but no effect. GNOME on Xorg 
works, it still shows a black screen when launching debsign but I don't 
lose the session.


It is possibly a bug in pinentry-gnome3 or gnome-keyring. I can use 
debsign with curses pinentry screen if I switch to a virtual terminal 
(control+alt+f2).