update-manager assert failure: python2.6: ../../src/xcb_io.c :183 : process_responses: L'assertion « !(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0)) » a échoué.

Bug #553110 reported by philuser
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: update-manager

upgrade from karamic to lucid beta1

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: update-manager 1:0.133.9
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
Architecture: amd64
AssertionMessage: python2.6: ../../src/xcb_io.c :183 : process_responses: L'assertion « !(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0)) » a échoué.
Date: Wed Mar 31 13:15:10 2010
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager --dist-upgrade
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: update-manager
StacktraceTop:
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
Title: update-manager assert failure: python2.6: ../../src/xcb_io.c :183 : process_responses: L'assertion « !(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0)) » a échoué.
UserGroups:
---
Architecture: amd64
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
NonfreeKernelModules: nvidia
Package: update-manager 1:0.142.22
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=fr_FR:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-28.49-server 2.6.35.11
Tags: maverick
Uname: Linux 2.6.35-28-server x86_64
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare

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

StacktraceTop:
 *__GI_raise (sig=<value optimized out>)
 *__GI_abort () at abort.c:92
 *__GI___assert_fail (
 process_responses (dpy=0x1d6cef0,
 _XReply (dpy=0x1d6cef0, rep=0x7fea787cacc0,

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 update-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel Hahler (blueyed)
visibility: private → public
Revision history for this message
Tim Casey (tjcasey) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

It would help us a lot if you could test a current, supported, Ubuntu version. If you test it, and it is still an issue, we would appreciate if you could upload updated logs by running the following command in a terminal window;

apport-collect 553110

We'd also appreciate you uploading the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments.

Please let us know if you need assistance uploading the log files, and thanks again for helping us out.

Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
philuser (philuser) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
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.