[master] gdebi-gtk crashed with SIGSEGV in gtk_button_set_label()

StacktraceTop:gtk_button_construct_child (button=0x89962e0)
IA__gtk_button_set_label (button=0x89962e0,
?? ()
PyEval_EvalFrameEx (f=0x8e03b14, throwflag=0)
PyEval_EvalFrameEx (f=0x8e0568c, throwflag=0)

because of many duplicates

Thanks for your bugreport.

Is there a way to reproduce this problem? I tried various install with gdebi and got no crashes so far. Any hints would be appreciated.

Not had this problem again assume its been fixed now!

Grant Allsop

2009/7/16 Michael Vogt <email address hidden>

> Thanks for your bugreport.
>
> Is there a way to reproduce this problem? I tried various install with
> gdebi and got no crashes so far. Any hints would be appreciated.
>
> --
> gdebi-gtk crashed with SIGSEGV in gtk_button_set_label()
> https://bugs.launchpad.net/bugs/377384
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in gdebi: New
> Status in “gdebi” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: gdebi
>
> Crash
>
> ProblemType: Crash
> Architecture: i386
> Date: Sat May 16 21:45:58 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/gdebi-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: gdebi 0.4.9
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive
> /home/linus/VMware\ Tools/vmwaretools_7396-122957_i386.deb
> ProcEnviron:
> PATH=(custom, no user)
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.30-5.6-generic
> Signal: 11
> SourcePackage: gdebi
> StacktraceTop:
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> gtk_button_set_label () from /usr/lib/libgtk-x11-2.0.so.0
> ?? () from /usr/lib/pymodules/python2.6/gtk-2.0/gtk/_gtk.so
> PyEval_EvalFrameEx ()
> PyEval_EvalFrameEx ()
> Title: gdebi-gtk crashed with SIGSEGV in gtk_button_set_label()
> Uname: Linux 2.6.30-5-generic i686
> UserGroups:
>

Any way to reproduce? No. The crash happened a few times in karmic but not in the "last time" (sry for my english).

I'm using jaunty and I've not this problem since it was officially released.

I'm not using karmic at the moment, probably won't upgrade until later in
the year.

I'm not sure how to reproduce, but if I remember correctly it occurred while
using the gdebi installer.

I can't remember the exact deb file I was installing at the time but I've
not had this problem again.

Grant Allsop

2009/7/17 Linus Hoppe <email address hidden>

> Any way to reproduce? No. The crash happened a few times in karmic but
> not in the "last time" (sry for my english).
>
> --
> gdebi-gtk crashed with SIGSEGV in gtk_button_set_label()
> https://bugs.launchpad.net/bugs/377384
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in gdebi: New
> Status in “gdebi” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: gdebi
>
> Crash
>
> ProblemType: Crash
> Architecture: i386
> Date: Sat May 16 21:45:58 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/gdebi-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: gdebi 0.4.9
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive
> /home/linus/VMware\ Tools/vmwaretools_7396-122957_i386.deb
> ProcEnviron:
> PATH=(custom, no user)
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.30-5.6-generic
> Signal: 11
> SourcePackage: gdebi
> StacktraceTop:
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> gtk_button_set_label () from /usr/lib/libgtk-x11-2.0.so.0
> ?? () from /usr/lib/pymodules/python2.6/gtk-2.0/gtk/_gtk.so
> PyEval_EvalFrameEx ()
> PyEval_EvalFrameEx ()
> Title: gdebi-gtk crashed with SIGSEGV in gtk_button_set_label()
> Uname: Linux 2.6.30-5-generic i686
> UserGroups:
>

I got that crash with after installing opera_10.00.4493.gcc4.qt4_amd64.deb ( newest beta )

Description: Ubuntu 9.04
Release: 9.04

opera:
  Installed: 10.00.4493.gcc4.qt4
  Candidate: 10.00.4493.gcc4.qt4
  Version table:
 *** 10.00.4493.gcc4.qt4 0
        100 /var/lib/dpkg/status

Happened again in jaunty, see duplicates

I tried a new workaround in karmic now, please let me know if 0.5.4 crashes again.

This seems fixed in 0.5.4, please reopen if it's still the case, thanks!