Ubuntu
synaptic package

synaptic crashed with SIGSEGV in RGWindow::windowCloseCallback()

Bug #927501 reported by Lockal
148
This bug affects 16 people
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Happened for me once while closing synaptic version 0.75.2ubuntu7 (12.04 alpha 2)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.2ubuntu9
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 6 12:55:26 2012
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: /usr/sbin/synaptic
SegvAnalysis:
 Segfault happened at: 0x44c338: mov (%rdx),%rdx
 PC (0x0044c338) ok
 source "(%rdx)" (0x00000081) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.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
Title: synaptic crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Lockal (lockal) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 RGWindow::windowCloseCallback (window=<optimized out>, event=<optimized out>) at rgwindow.cc:35
 _gtk_marshal_BOOLEAN__BOXED (closure=0x3c1d380, return_value=0x7fffe88c7300, n_param_values=<optimized out>, param_values=0x4c94550, invocation_hint=<optimized out>, marshal_data=<optimized out>) at /build/buildd/gtk+2.0-2.24.8/gtk/gtkmarshalers.c:86
 g_closure_invoke (closure=0x3c1d380, return_value=0x7fffe88c7300, n_param_values=2, param_values=0x4c94550, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.14/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x7fffe88c7440, instance_and_params=0x4c94550) at /build/buildd/glib2.0-2.31.14/./gobject/gsignal.c:3302
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fffe88c74a8) at /build/buildd/glib2.0-2.31.14/./gobject/gsignal.c:3043

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in synaptic (Ubuntu):
importance: Undecided → Medium
summary: - synaptic crashed with SIGSEGV in g_closure_invoke()
+ synaptic crashed with SIGSEGV in RGWindow::windowCloseCallback()
tags: removed: need-amd64-retrace
Lockal (lockal)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in synaptic (Ubuntu):
status: New → Confirmed
Revision history for this message
Bob Bib (bobbib) wrote :

Precise Beta 1: tried to install some packages; closely to 100%, progress window became unresponsive, and stayed so for >15 min; it crashed after attempt to close it.

Apport retracing service (apport)
tags: added: bugpattern-needed
tags: added: quantal
Revision history for this message
LAZA (laza74) wrote :

Synaptics crashed after uninstalling old kernel packages.

Crash report is attached.

.

Xubuntu 12.04.2

Revision history for this message
Bob Bib (bobbib) wrote : Re: [Bug 927501] Re: synaptic crashed with SIGSEGV in RGWindow::windowCloseCallback()

LAZA:
> Synaptics crashed after uninstalling old kernel packages.
>
> Crash report is attached.
>
> .
>
> Xubuntu 12.04.2
>
> ** Attachment added: "_usr_sbin_synaptic.0.crash"
> https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/927501/+attachment/3662734/+files/_usr_sbin_synaptic.0.crash

Generally, you should report a new bug and let the Apport system to process the crashdump,
instead of attaching a HUGE crashdump to the old bug reports.

I suggest you to report a new bug, post the new bug number here, and then remove this crashfile.

Revision history for this message
LAZA (laza74) wrote :

@Bob:

Thanks for the suggestion, but since Precise(?) Apport does not work as expected and does not report crash files!
So i had to do it by hand...

New Bug:
https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1175890

Revision history for this message
Bob Bib (bobbib) wrote :

LAZA:
> @Bob:
>
> Thanks for the suggestion, but since Precise(?) Apport does not work as expected and does not report crash files!

Oh, it looks like your Apport problem is already known as #994921, and you can make a vote for it;
try to apply the workaround, then reboot and try to report your Synaptic crash, this time it should work.

> So i had to do it by hand...
>
> New Bug:
> https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1175890

Manual attaching of unprocessed crash files is not a good approach though:
Launchpad's Apport retracing service doesn't seem to be able to process them directly.

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

Other bug subscribers

Remote bug watches

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