(lib)gksu SIGSEGV

Bug #277189 reported by Andreas Brauchli
2
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gksu

Ubuntu intrepid (development branch) - updated as of submission time (Oct 2 2008)
gksu Installed: 2.0.0-5ubuntu3
libgksu Installed: 2.0.7-1ubuntu2

always works when first authenticating with "gksu" (without prog. to launch as argument, but entering "synaptic" into the input box labeled "Run: ") then closing synaptic and re-running with "gksu synaptic"

backtrace:
(gdb) r -d synaptic
Starting program: /usr/bin/gksu -d synaptic
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7f093c31b770 (LWP 3029)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

No ask_pass set, using default!
xauth: /tmp/libgksu-hwTSmR/.Xauthority
(no debugging symbols found)
STARTUP_ID: gksu/synaptic/3029-0-macbook_TIME100502
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: synaptic
buffer: -GNOME_SUDO_PASSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f093c31b770 (LWP 3029)]
0x00007f093bf22538 in ?? () from /usr/lib/libgksu2.so.0
(gdb) bt
#0 0x00007f093bf22538 in ?? () from /usr/lib/libgksu2.so.0
#1 0x00007f093bf22826 in ?? () from /usr/lib/libgksu2.so.0
#2 0x00007f093a06a25d in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#3 0x00007f093a07ff5d in ?? () from /usr/lib/libgobject-2.0.so.0
#4 0x00007f093a081608 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#5 0x00007f093a081b33 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#6 0x00007f093b513bc6 in gtk_widget_realize ()
   from /usr/lib/libgtk-x11-2.0.so.0
#7 0x00007f093b523dd8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x00007f093a06a25d in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#9 0x00007f093a07f878 in ?? () from /usr/lib/libgobject-2.0.so.0
#10 0x00007f093a081608 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#11 0x00007f093a081b33 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#12 0x00007f093b514b8c in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x00007f093bf1e358 in grab_keyboard_and_mouse ()
   from /usr/lib/libgksu2.so.0
#14 0x00007f093bf1e7b8 in ?? () from /usr/lib/libgksu2.so.0
#15 0x00007f093bf1fa30 in gksu_sudo_full () from /usr/lib/libgksu2.so.0
#16 0x0000000000404354 in ?? ()
#17 0x00007f0939439466 in __libc_start_main () from /lib/libc.so.6
#18 0x0000000000402f79 in ?? ()
#19 0x00007fff44343758 in ?? ()
#20 0x000000000000001c in ?? ()
#21 0x0000000000000003 in ?? ()
#22 0x00007fff443456cd in ?? ()
#23 0x00007fff443456db in ?? ()
#24 0x00007fff443456de in ?? ()
#25 0x0000000000000000 in ?? ()

Tags: sigsegv
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gksu (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Andreas Brauchli (blk) wrote :

Sorry about that, i'll do that next time.. the bug however is not present in karmic on which i'm now.

Does someone else still encounter this? Otherwise you might just close it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.