Ubuntu
synaptic package

synaptic package manager never worked in this ubuntu release

Bug #954070 reported by b49P23TIvg on 2012-03-13

This bug report is a duplicate of: Bug #894662: Synaptic closes shortly after starting GUI. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	synaptic (Ubuntu)	New	Undecided	Unassigned

Bug Description

This time I have a crash file.

Applications->Administration->Package Manager

Program asks and receives root password
The gui window displays for almost 1 second, then crashes.
Yes, I am the manager of this system and yes, I know and correctly type the root password.
Also, I'm having a bit of trouble uploading the crash file. I copied it elsewhere,
sudo cp /var/crash/* /tmp
sudo chmod +r /tmp/_usr_sbin_synaptic.0.crash
Whereas I've not had trouble uploading evolution nor empathy crash files.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: synaptic 0.75.2ubuntu8
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Mar 13 09:52:32 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: synaptic
UpgradeStatus: Upgraded to oneiric on 2011-10-17 (147 days ago)

Tags:

Revision history for this message

b49P23TIvg (b49p23tivg) wrote on 2012-03-13:

_usr_sbin_synaptic.0.crash Edit (1.2 MiB, text/plain)
CurrentDmesg.txt.txt Edit (246.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt.txt Edit (1.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt.txt Edit (11.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2012-11-22:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #894662, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.