gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()

[Ian Scott]

gdebi-gtk crashed on notebook turn-on (not used, but might have had unfinished business with virtualbox?)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gdebi 0.9.1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Fri Sep 20 17:36:02 2013
ExecutablePath: /usr/share/gdebi/gdebi-gtk
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /media/ian/Nemesis1/Software/Internet\ Software/Virtualbox/For\ Ubuntu\ 13.04/virtualbox-4.2_4.2.18-88780~Ubuntu~raring_amd64.deb
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
 TERM=unknown
SegvAnalysis:
 Segfault happened at: 0x7ffdb30fef8e <gtk_label_set_text+30>: cmp %rax,(%rdx)
 PC (0x7ffdb30fef8e) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gdebi
StacktraceTop:
 gtk_label_set_text () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 gtk_label_set_text (label=0x2d6e2b0, str=0x2e1ffd0 "") at /build/buildd/gtk+3.0-3.8.4/./gtk/gtklabel.c:2111
 g_closure_invoke (closure=0x2d73cb0, return_value=0x0, n_param_values=3, param_values=0x7fff1af24dc0, invocation_hint=0x7fff1af24d60) at /build/buildd/glib2.0-2.37.93/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x2d73d20, detail=detail@entry=0, instance=instance@entry=0x2d6e160, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff1af24dc0) at /build/buildd/glib2.0-2.37.93/./gobject/gsignal.c:3624
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff1af24f78) at /build/buildd/glib2.0-2.37.93/./gobject/gsignal.c:3330
 g_signal_emit (instance=instance@entry=0x2d6e160, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.37.93/./gobject/gsignal.c:3386

[Paul White (paulw2u)]

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu?

Please let us know if you do. Alternatively, this bug report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.related

Paul White
[Ubuntu Bug Squad]

[Ian Scott (arb-xfm)]

Hi Paul

Ubuntu 18.10 runs fine - the only issue it has is to run SciLab - never
opens, however on Mint no problem. I've reported this earlier.

Ian

On Wed, Dec 5, 2018 at 3:30 AM Paul White <email address hidden>
wrote:

> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
>
> Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
>
> Do you still see a problem related to the one that you reported in a
> currently supported version of Ubuntu?
>
> Please let us know if you do. Alternatively, this bug report can be left
> to expire in approximately 60 days time.
>
> Thank you for helping make Ubuntu better.related
>
> Paul White
> [Ubuntu Bug Squad]
>
> ** Changed in: gdebi (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1228383
>
> Title:
> gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()
>
> Status in gdebi package in Ubuntu:
> Incomplete
>
> Bug description:
> gdebi-gtk crashed on notebook turn-on (not used, but might have had
> unfinished business with virtualbox?)
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.10
> Package: gdebi 0.9.1ubuntu1
> ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
> Uname: Linux 3.11.0-8-generic x86_64
> ApportVersion: 2.12.4-0ubuntu1
> Architecture: amd64
> Date: Fri Sep 20 17:36:02 2013
> ExecutablePath: /usr/share/gdebi/gdebi-gtk
> InterpreterPath: /usr/bin/python2.7
> MarkForUpload: True
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive
> /media/ian/Nemesis1/Software/Internet\ Software/Virtualbox/For\ Ubuntu\
> 13.04/virtualbox-4.2_4.2.18-88780~Ubuntu~raring_amd64.deb
> ProcEnviron:
> LANGUAGE=en_NZ:en
> PATH=(custom, no user)
> LANG=en_NZ.UTF-8
> SHELL=/bin/bash
> TERM=unknown
> SegvAnalysis:
> Segfault happened at: 0x7ffdb30fef8e <gtk_label_set_text+30>:
> cmp %rax,(%rdx)
> PC (0x7ffdb30fef8e) ok
> source "%rax" ok
> destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA
> region (needed writable region)!
> SegvReason: writing unknown VMA
> Signal: 11
> SourcePackage: gdebi
> StacktraceTop:
> gtk_label_set_text () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit_valist () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1228383/+subscriptions
>

[Paul White (paulw2u)]

Thanks for your reply.
Bug report no longer valid as 13.10 EOL
Issue not confirmed by another user
No action taken on bug report
So marking "Invalid" to close