Discussion:
Bug#762906: krb5-auth-dialog debug output
Guido Günther
2014-10-11 11:25:44 UTC
Permalink
Hi,
Hi,
** (krb5-auth-dialog:2988): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
(krb5-auth-dialog:2988): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
(krb5-auth-dialog:2988): GLib-GObject-WARNING **: The property GtkImageMenuItem:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
(krb5-auth-dialog:2988): GLib-GObject-WARNING **: The property GtkImageMenuItem:accel-group is deprecated and shouldn't be used anymore. It will be removed in a future version.
(krb5-auth-dialog:2988): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
(krb5-auth-dialog:2988): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_local_command_line: Parsing local command line
Could you check if krb5-auth-dialog is already running? If so,
terminate it first and then run it again please.
Cheers,
-- Guido
Wolfgang
--
To UNSUBSCRIBE, email to debian-edu-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Archive: https://lists.debian.org/***@bogon.m.sigxcpu.org
Wolfgang Schweer
2014-10-11 19:49:35 UTC
Permalink
Post by Guido Günther
Could you check if krb5-auth-dialog is already running? If so,
terminate it first and then run it again please.
Hi Guido,

krb5-auth-dialog is running.

Terminating and running it again in an xterm:

** (krb5-auth-dialog:13982): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.

What ever that wants to tell me...

Hope you can figure it out.

Wolfgang
Guido Günther
2014-10-12 08:00:32 UTC
Permalink
Post by Wolfgang Schweer
Post by Guido Günther
Could you check if krb5-auth-dialog is already running? If so,
terminate it first and then run it again please.
Hi Guido,
krb5-auth-dialog is running.
** (krb5-auth-dialog:13982): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.
...and the process keeps runnng? Is that all the output you're seeing?
IN that case that's probably not the debug build.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-edu-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Archive: https://lists.debian.org/***@bogon.m.sigxcpu.org
Wolfgang Schweer
2014-10-12 17:35:13 UTC
Permalink
Post by Guido Günther
...and the process keeps runnng? Is that all the output you're seeing?
IN that case that's probably not the debug build.
You're right, ran it on the wrong vm. This is the output using the debug
build:

***@tjener:~$ killall -s9 krb5-auth-dialog
***@tjener:~$ krb5-auth-dialog

** (krb5-auth-dialog:3265): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.
DEBUG: ka_applet_set_property: principal:
DEBUG: ka_applet_set_property: pk-userid:
DEBUG: ka_applet_set_property: pk-anchors:
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_set_property: principal:
DEBUG: ka_applet_set_property: pk-userid:
DEBUG: ka_applet_set_property: pk-anchors:
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_local_command_line: Parsing local command line
DEBUG: ka_applet_startup: Primary application
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: monitor_ccache: Monitoring /tmp/krb5cc_1000_w9KVYa
DEBUG: ka_applet_command_line: Evaluating command line
DEBUG: credentials_expiring: Checking expiry <1800s
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: credentials_expiring: Checking expiry <1800s

Wolfgang
Guido Günther
2014-10-20 07:42:29 UTC
Permalink
Hi Wolfgang,
Post by Wolfgang Schweer
Post by Guido Günther
...and the process keeps runnng? Is that all the output you're seeing?
IN that case that's probably not the debug build.
You're right, ran it on the wrong vm. This is the output using the debug
** (krb5-auth-dialog:3265): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_local_command_line: Parsing local command line
DEBUG: ka_applet_startup: Primary application
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: monitor_ccache: Monitoring /tmp/krb5cc_1000_w9KVYa
DEBUG: ka_applet_command_line: Evaluating command line
DEBUG: credentials_expiring: Checking expiry <1800s
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: credentials_expiring: Checking expiry <1800s
Thanks. I can reproduce it here now (you just have to clear the
principal names from the preferences). The bug doesn't seem to be in
krb5-auth-dialog itself since we get the prompt passed in from the
Kerberos libs and it's already lacking the username. I'll investigate
further.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-edu-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Archive: https://lists.debian.org/***@bogon.m.sigxcpu.org
Guido Günther
2014-10-20 08:14:35 UTC
Permalink
Post by Guido Günther
Hi Wolfgang,
Post by Wolfgang Schweer
Post by Guido Günther
...and the process keeps runnng? Is that all the output you're seeing?
IN that case that's probably not the debug build.
You're right, ran it on the wrong vm. This is the output using the debug
** (krb5-auth-dialog:3265): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_local_command_line: Parsing local command line
DEBUG: ka_applet_startup: Primary application
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: monitor_ccache: Monitoring /tmp/krb5cc_1000_w9KVYa
DEBUG: ka_applet_command_line: Evaluating command line
DEBUG: credentials_expiring: Checking expiry <1800s
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: credentials_expiring: Checking expiry <1800s
Thanks. I can reproduce it here now (you just have to clear the
principal names from the preferences). The bug doesn't seem to be in
krb5-auth-dialog itself since we get the prompt passed in from the
Kerberos libs and it's already lacking the username. I'll investigate
further.
The attached patch should fix this.
-- Guido
Wolfgang Schweer
2014-10-20 13:23:24 UTC
Permalink
Post by Guido Günther
Post by Guido Günther
Thanks. I can reproduce it here now (you just have to clear the
principal names from the preferences). The bug doesn't seem to be in
krb5-auth-dialog itself since we get the prompt passed in from the
Kerberos libs and it's already lacking the username. I'll investigate
further.
The attached patch should fix this.
-- Guido
diff --git a/src/ka-kerberos.c b/src/ka-kerberos.c
index fc6d63f..a17dee3 100644
--- a/src/ka-kerberos.c
+++ b/src/ka-kerberos.c
@@ -649,6 +649,10 @@ ka_parse_name (KaApplet *applet, krb5_context krbcontext,
krb5_free_principal (krbcontext, *kprinc);
g_object_get (applet, KA_PROP_NAME_PRINCIPAL, &principal, NULL);
+ if (principal[0] == '\0') {
+ g_free (principal);
+ principal = g_strdup (g_get_user_name());
+ }
ret = krb5_parse_name (krbcontext, principal, kprinc);
g_free (principal);
With the patch applied, the tray icon now disappears if clicked.

krb5-auth-dialog (with patch) compiled again with '--enable-debug' and
running it out of a terminal shows that the reason is a segmentation
fault.

Wolfgang
Wolfgang Schweer
2014-10-20 14:40:10 UTC
Permalink
Post by Wolfgang Schweer
With the patch applied, the tray icon now disappears if clicked.
krb5-auth-dialog (with patch) compiled again with '--enable-debug' and
running it out of a terminal shows that the reason is a segmentation
fault.
This is the output of 'valgrind krb5-auth-dialog' with the tray icon
clicked:
----------------------------------------------
==21299== Memcheck, a memory error detector
==21299== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==21299== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==21299== Command: krb5-auth-dialog
==21299==

** (krb5-auth-dialog:21299): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.

DEBUG: ka_applet_set_property: principal:
DEBUG: ka_applet_set_property: pk-userid:
DEBUG: ka_applet_set_property: pk-anchors:
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
==21299== Conditional jump or move depends on uninitialised value(s)
==21299== at 0x5BAC57D: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.32.6)
==21299== by 0x5B8F211: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.32.6)
==21299== by 0x5B3E76A: pixman_image_composite32 (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.32.6)
==21299== by 0x54584C7: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x54A28DA: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x5493069: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x5493BF4: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x549490B: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x544A6A9: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x545C79A: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x549834D: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x54539A8: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299==
==21299== Conditional jump or move depends on uninitialised value(s)
==21299== at 0x5BAC7CD: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.32.6)
==21299== by 0x5B8F211: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.32.6)
==21299== by 0x5B3E76A: pixman_image_composite32 (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.32.6)
==21299== by 0x54584C7: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x54A28DA: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x5493069: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x5493BF4: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x5494C66: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x544A7AC: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x545C7D2: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x5498475: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299== by 0x5453E58: ??? (in /usr/lib/i386-linux-gnu/libcairo.so.2.11200.16)
==21299==
==21299== Conditional jump or move depends on uninitialised value(s)
==21299== at 0x99727A2: ??? (in /usr/lib/i386-linux-gnu/librsvg-2.so.2.40.4)
==21299== by 0x9973625: rsvg_handle_get_pixbuf_sub (in /usr/lib/i386-linux-gnu/librsvg-2.so.2.40.4)
==21299== by 0x99736C9: rsvg_handle_get_pixbuf (in /usr/lib/i386-linux-gnu/librsvg-2.so.2.40.4)
==21299== by 0x8043AC0: ??? (in /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so)
==21299== by 0x527E998: gdk_pixbuf_loader_close (in /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1)
==21299== by 0x527A671: ??? (in /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1)
==21299== by 0x527C58C: gdk_pixbuf_new_from_stream_at_scale (in /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1)
==21299== by 0x43479D3: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x4347CA3: gtk_icon_info_load_icon (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x4349042: gtk_icon_info_load_symbolic_for_context (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x433F6D4: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x433F91D: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299==
DEBUG: ka_applet_set_property: principal:
DEBUG: ka_applet_set_property: pk-userid:
DEBUG: ka_applet_set_property: pk-anchors:
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_local_command_line: Parsing local command line
DEBUG: ka_applet_startup: Primary application
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: monitor_ccache: Monitoring /tmp/krb5cc_1000_NFyZSs
DEBUG: ka_applet_command_line: Evaluating command line
DEBUG: credentials_expiring: Checking expiry <1800s
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: ka_tray_icon_on_click: Trayicon clicked: 1800
==21299== Invalid read of size 1
==21299== at 0x804E51A: ??? (in /usr/bin/krb5-auth-dialog)
==21299== by 0x804EE0B: ka_grab_credentials (in /usr/bin/krb5-auth-dialog)
==21299== by 0x8050997: ??? (in /usr/bin/krb5-auth-dialog)
==21299== by 0x4B244E6: g_cclosure_marshal_VOID__VOIDv (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B22A5E: ??? (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B3C7F8: g_signal_emit_valist (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B3D0D4: g_signal_emit (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4203D86: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x420444B: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x4386B95: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x4B2283A: g_closure_invoke (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B34854: ??? (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==21299==
==21299==
==21299== Process terminating with default action of signal 11 (SIGSEGV)
==21299== Access not within mapped region at address 0x0
==21299== at 0x804E51A: ??? (in /usr/bin/krb5-auth-dialog)
==21299== by 0x804EE0B: ka_grab_credentials (in /usr/bin/krb5-auth-dialog)
==21299== by 0x8050997: ??? (in /usr/bin/krb5-auth-dialog)
==21299== by 0x4B244E6: g_cclosure_marshal_VOID__VOIDv (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B22A5E: ??? (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B3C7F8: g_signal_emit_valist (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B3D0D4: g_signal_emit (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4203D86: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x420444B: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x4386B95: ??? (in /usr/lib/i386-linux-gnu/libgtk-3.so.0.1400.1)
==21299== by 0x4B2283A: g_closure_invoke (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== by 0x4B34854: ??? (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4200.0)
==21299== If you believe this happened as a result of a stack
==21299== overflow in your program's main thread (unlikely but
==21299== possible), you can try to increase the size of the
==21299== main thread stack using the --main-stacksize= flag.
==21299== The main thread stack size used in this run was 8388608.
==21299==
==21299== HEAP SUMMARY:
==21299== in use at exit: 2,844,399 bytes in 62,049 blocks
==21299== total heap usage: 441,018 allocs, 378,969 frees, 45,448,507 bytes allocated
==21299==
==21299== LEAK SUMMARY:
==21299== definitely lost: 6,324 bytes in 27 blocks
==21299== indirectly lost: 16,453 bytes in 938 blocks
==21299== possibly lost: 71,568 bytes in 2,062 blocks
==21299== still reachable: 2,582,770 bytes in 57,564 blocks
==21299== suppressed: 0 bytes in 0 blocks
==21299== Rerun with --leak-check=full to see details of leaked memory
==21299==
==21299== For counts of detected and suppressed errors, rerun with: -v
==21299== Use --track-origins=yes to see where uninitialised values come from
==21299== ERROR SUMMARY: 51 errors from 4 contexts (suppressed: 0 from 0)
Getötet (i.e. killed)

Wolfgang
Guido Günther
2014-10-21 08:54:52 UTC
Permalink
Post by Wolfgang Schweer
Post by Guido Günther
Post by Guido Günther
Thanks. I can reproduce it here now (you just have to clear the
principal names from the preferences). The bug doesn't seem to be in
krb5-auth-dialog itself since we get the prompt passed in from the
Kerberos libs and it's already lacking the username. I'll investigate
further.
The attached patch should fix this.
-- Guido
diff --git a/src/ka-kerberos.c b/src/ka-kerberos.c
index fc6d63f..a17dee3 100644
--- a/src/ka-kerberos.c
+++ b/src/ka-kerberos.c
@@ -649,6 +649,10 @@ ka_parse_name (KaApplet *applet, krb5_context krbcontext,
krb5_free_principal (krbcontext, *kprinc);
g_object_get (applet, KA_PROP_NAME_PRINCIPAL, &principal, NULL);
+ if (principal[0] == '\0') {
+ g_free (principal);
+ principal = g_strdup (g_get_user_name());
+ }
ret = krb5_parse_name (krbcontext, principal, kprinc);
g_free (principal);
With the patch applied, the tray icon now disappears if clicked.
krb5-auth-dialog (with patch) compiled again with '--enable-debug' and
running it out of a terminal shows that the reason is a segmentation
fault.
Can you get me a backtrace with gdb (gdb -c core
src/krb5-auth-dialog)? I can only assume that principal is NULL which
shouldn't happen. I doesn't crash here of course.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-edu-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Archive: https://lists.debian.org/***@bogon.m.sigxcpu.org
Wolfgang Schweer
2014-10-21 14:40:30 UTC
Permalink
Hi Guido.
Post by Guido Günther
Can you get me a backtrace with gdb (gdb -c core
src/krb5-auth-dialog)? I can only assume that principal is NULL which
shouldn't happen. I doesn't crash here of course.
Here it is:
------------------------------------------------
Reading symbols from src/krb5-auth-dialog...done.

warning: core file may not match specified executable file.
[New LWP 24527]
[New LWP 24531]
[New LWP 24534]
[New LWP 24535]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `krb5-auth-dialog'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0804e51a in ka_parse_name (applet=0x9e4e8d8, krbcontext=0x9f885a0,
kprinc=0x805fb7c <kprincipal>)
at /skole/tjener/home0/test/krb5-auth-dialog-3.12.0/./src/ka-kerberos.c:651
651 g_object_get (applet, KA_PROP_NAME_PRINCIPAL, &principal, NULL);
(gdb)
----------------------------------------------------

Wolfgang
Guido Günther
2014-10-23 17:31:40 UTC
Permalink
Hi Wolfgang,
Post by Wolfgang Schweer
Hi Guido.
Post by Guido Günther
Can you get me a backtrace with gdb (gdb -c core
src/krb5-auth-dialog)? I can only assume that principal is NULL which
shouldn't happen. I doesn't crash here of course.
Could you check if the 3.12.0-2 crashes for you too? I've tested under
gnome-shell and xfce4 without any issues. If it crashes it'd be
awesome to see any possible console output.
Cheers
-- Guido
--
To UNSUBSCRIBE, email to debian-edu-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Archive: https://lists.debian.org/***@bogon.m.sigxcpu.org
Mike Gabriel
2014-10-22 08:23:17 UTC
Permalink
Hi Guido, hi Sam,
Post by Guido Günther
Post by Guido Günther
Hi Wolfgang,
Post by Wolfgang Schweer
Post by Guido Günther
...and the process keeps runnng? Is that all the output you're seeing?
IN that case that's probably not the debug build.
You're right, ran it on the wrong vm. This is the output using the debug
** (krb5-auth-dialog:3265): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_set_property: pw-prompt-mins: 30
DEBUG: ka_applet_set_property: tgt-forwardable: False
DEBUG: ka_applet_set_property: tgt-proxiable: False
DEBUG: ka_applet_set_property: tgt-renewable: False
DEBUG: ka_applet_set_property: conf-tickets: False
DEBUG: ka_applet_local_command_line: Parsing local command line
DEBUG: ka_applet_startup: Primary application
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: monitor_ccache: Monitoring /tmp/krb5cc_1000_w9KVYa
DEBUG: ka_applet_command_line: Evaluating command line
DEBUG: credentials_expiring: Checking expiry <1800s
DEBUG: ka_nm_client_state_changed_cb: Network connected
DEBUG: credentials_expiring: Checking expiry <1800s
Thanks. I can reproduce it here now (you just have to clear the
principal names from the preferences). The bug doesn't seem to be in
krb5-auth-dialog itself since we get the prompt passed in from the
Kerberos libs and it's already lacking the username. I'll investigate
further.
The attached patch should fix this.
-- Guido
It seems this bug (#762906) is a duplicate of #764669 [1].

Right? Please confirm and merge, if so.

Mike

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764669
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: ***@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
Sam Hartman
2014-10-22 11:15:01 UTC
Permalink
Perhaps, although I'll note that the krb5 maintainers are unaware of
what's exactly going on in 764669.
So, feel free to merge, but if you actually have an idea of the problem,
please enlighten us, as we don't see that behavior at all.

--Sam
--
To UNSUBSCRIBE, email to debian-edu-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Archive: https://lists.debian.org/0000014937912a32-7934dee7-f4ac-4a18-b9d4-623271c73402-***@email.amazonses.com
Guido Günther
2014-10-22 13:38:21 UTC
Permalink
Post by Mike Gabriel
Post by Guido Günther
Post by Guido Günther
Thanks. I can reproduce it here now (you just have to clear the
principal names from the preferences). The bug doesn't seem to be in
krb5-auth-dialog itself since we get the prompt passed in from the
Kerberos libs and it's already lacking the username. I'll investigate
further.
The attached patch should fix this.
-- Guido
It seems this bug (#762906) is a duplicate of #764669 [1].
Right? Please confirm and merge, if so.
#762906 is purely krb5-auth-dialog related, #764669 seems to also
affect kinit.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-edu-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Archive: https://lists.debian.org/***@bogon.m.sigxcpu.org
Loading...