/usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup

Bug #2041831 reported by errors.ubuntu.com bug bridge
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pygobject (Ubuntu)
New
Undecided
Unassigned
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:23.10.1, the problem page at https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Revision history for this message
Benjamin Drung (bdrung) wrote :

#5 report for foundations-bugs on mantic (144 reports in the past month)

tags: added: rls-mm-incoming
Revision history for this message
Julian Andres Klode (juliank) wrote :

I believe this seems like a pygobject issue for desktop to investigate, probably a type declared wrong somewhere?

Revision history for this message
Tormod Volden (tormodvolden) wrote (last edit ):

A.k.a "Unchecking packages in update-manager causes SIGSEGV" bug #2027941

Revision history for this message
Tormod Volden (tormodvolden) wrote (last edit ):

It happens if packages are deselected with a mouse click. If the keyboard spacebar is used instead (with focus on the package name or whole line, not the checkbox) it doesn't crash AFAICS.

Revision history for this message
Nathan Teodosio (nteodosio) wrote :

I can confirm #4 on Oracular.

I cannot even send the crash report though, 'apport-bug /var/crash/_usr_bin_update-manager.1000.crash' returns without sending it (as far as I can tell).

Revision history for this message
Brian Murray (brian-murray) wrote :

In /var/crash do you have a _usr_bin_update-manager.1000.upload file and a _usr_bin_update-manager.1000.uploaded file?

If you do you have a .uploaded file please cat it and paste the UUID here for further investigation.

Does the .crash file contain a Traceback from a python application? I've recently heard from the current apport maintainer that there are some issues with python tracebacks being reported.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Apport didn't work for me either, so I ran gdb python manually. The traceback is identical to the OP one in bug #2027941.

Revision history for this message
Nathan Teodosio (nteodosio) wrote : Re: [Bug 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup

> In /var/crash do you have a _usr_bin_update-manager.1000.upload file and
> a _usr_bin_update-manager.1000.uploaded file?

No.

--->
% \ls /var/crash/*upload*
/var/crash/_usr_share_apport_whoopsie-upload-all.0.crash
<---

> Does the .crash file contain a Traceback from a python application? I've

I used apport-unpack to verify that the *Stacktrace* files did not contain
tracebacks from Python.

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.