Bug 706641

Summary: Synaptic crash on package reload. Terminate called after throwing an instance of 'std::length_error'. Program exited with code 0206.
Product: [Fedora] Fedora Reporter: yzubkov
Component: synapticAssignee: Panu Matilainen <pmatilai>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 14CC: axel.thimm, pmatilai
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:06:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description yzubkov 2011-05-21 21:23:27 UTC
Description of problem:
There is a crash in Synaptic that occurs only after the packages get refreshed. I believe this is a separate bug from all the others reported here, because the other bugs deal with initial crash when synaptic is opened. I do get the same message in the console "(synaptic:6119): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed", but in my case this does not crash synaptic and I am able to proceed to manage packages. But, whenever I try to reload the package lists with "Reload" button, it connects, loads all the file lists to 100%/Done and then silently crashes.

I had issues receiving stack traces or core dumps from the crash. ABRT is not picking up the crash, so I tried GDB, but it does not provide stack traces even when logged in as root. Below is the complete terminal output.
=================Begin Terminal Output==========================
[root@LENOVO fedora]# gdb synaptic
GNU gdb (GDB) Fedora (7.2-51.fc14)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/synaptic...Reading symbols from /usr/lib/debug/usr/bin/consolehelper.debug...done.
done.
(gdb) run
Starting program: /usr/bin/synaptic 
[Thread debugging using libthread_db enabled]
process 7084 is executing new program: /usr/bin/consolehelper-gtk
[Thread debugging using libthread_db enabled]
Detaching after fork from child process 7087.
[New Thread 0xb7ddab70 (LWP 7088)]

(synaptic:7091): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
terminate called after throwing an instance of 'std::length_error'
  what():  basic_string::_S_create
[Thread 0xb7ddab70 (LWP 7088) exited]

Program exited with code 0206.
(gdb) thread apply all bt full
(gdb) bt
No stack.
(gdb) quit
==================End Terminal Output===========================

I did manage to hunt down one core file generated by the crash in the user folder. Here is what I did with it. Again, terminal output below:
=================Begin Terminal Output==========================
[root@LENOVO fedora]$ gdb synaptic /home/fedora/core.5655
Reading symbols from /usr/bin/synaptic...Reading symbols from /usr/lib/debug/usr/bin/consolehelper.debug...done.
done.
[New Thread 5655]
Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.13.so.debug...done.
done.
Loaded symbols for /lib/ld-linux.so.2
Core was generated by `synaptic'.
Program terminated with signal 6, Aborted.
#0  0x00b56416 in __kernel_vsyscall ()
==================End Terminal Output===========================

After an initial crash, on any subsequent loads, the synaptic presents a popup with some errors. This popup can be dismissed just fine, but package reloading still causes a crash.
================Begin Synaptic Popup Errors=======================
E: opening /var/lib/apt/lists/download.fedoraproject.org_pub_fedora_linux_updates_14_i386_repodata_b9a8f440285c3d1cbf5e204b2cbaa7dd7c43e2ac294e5a1bb6dff955a1a3f7d9-primary.sqlite db failed
E: Unsupported database scheme (0)
E: opening /var/lib/apt/lists/download.fedoraproject.org_pub_fedora_linux_releases_14_Everything_i386_os_repodata_72f870f3e28571eda6bed2c260d245a970fcc74786c5445e847a40890e1c471f-primary.sqlite db failed
E: Unsupported database scheme (0)
E: The package lists or status file could not be parsed or opened.
=================End Synaptic Popup Errors=========================


Version-Release number of selected component (if applicable):
Fedora Release 14
Kernel Linux 2.6.35.13-91.fc14.i686
GNOME 2.32.0
Synaptic 0.57.2-23.fc13 (i686)

How reproducible:
100%

Steps to Reproduce:
1. Open synaptic
2. Press "Reload" button
3. Witness a crash after file lists complete download.
  
Actual results:
Synaptic crashes

Expected results:
Synaptic would not crash, but will update package lists

Additional info:

Comment 1 Fedora End Of Life 2012-08-16 15:06:29 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping