[Breezy] Synaptic segfaults at startup

Bug #17402 reported by JP Foster
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Fix Released
Critical
Michael Vogt

Bug Description

Just dist-upgraded a new synaptic this afternoon (23rd May)
synpatic segfaults, seems to be down to some missing message files, see attached

# sudo strace synaptic 2>&1 | tail
open("/usr/share/locale/en.utf8/LC_MESSAGES/synaptic.mo", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/synaptic.mo", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/usr/share/locale-langpack/en_GB.UTF-8/LC_MESSAGES/synaptic.mo", O_RDONLY)
= -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_GB.utf8/LC_MESSAGES/synaptic.mo", O_RDONLY)
= -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_GB/LC_MESSAGES/synaptic.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/synaptic.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.utf8/LC_MESSAGES/synaptic.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en/LC_MESSAGES/synaptic.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
#

--
JP

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

I uploaded a new apt/synaptic today, please tell me if that fixes the problem
(should be available tomorrow) and close the bug if it does :)

Thanks,
 Michael

Revision history for this message
JP Foster (jeepster) wrote :

That's done the trick thanks.

Revision history for this message
Corey Burger (corey.burger) wrote :

Ok, with the C++ transition I have a seg fault at boot, and reinstalling
synaptic yeilded this:

The following packages will be REMOVED:
  libsigc++-1.2-5c102
The following NEW packages will be installed:
  libsigc++-1.2-5

It worked after I did this, but is this correct?

Revision history for this message
Hervé Cauwelier (bug tracking) (debian-oursours) wrote :

Yes, that's precisely the effect of the C++ transition, marking library package
names when they are transitioned. "c102" was the marker of the previous transition.

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.