Bug 253527 - Gnome crash on install with package manager - esound problem?
Summary: Gnome crash on install with package manager - esound problem?
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pirut
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-20 12:52 UTC by Troy Deierling
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-21 14:19:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
crash report from package manager (888 bytes, text/plain)
2007-08-20 12:52 UTC, Troy Deierling
no flags Details

Description Troy Deierling 2007-08-20 12:52:07 UTC
Running F8 on a new Dell Vostro 1500 notebook.

Can't select gnome from package manager.  Get following error then crash of
package manager.

pulseaudio-esound-compat conflicts with esound

See attached crash report.

Thanks

Comment 1 Troy Deierling 2007-08-20 12:52:08 UTC
Created attachment 161870 [details]
crash report from package manager

Comment 2 Bastien Nocera 2007-08-20 12:55:43 UTC
Comment on attachment 161870 [details]
crash report from package manager

Please mark text attachments as such

Comment 3 Bastien Nocera 2007-08-20 13:01:21 UTC
Pirut shouldn't crash, but pulseaudio should have the esound package as an
obsoletes (filed as bug 253528).

Comment 4 Jeremy Katz 2007-08-20 18:09:37 UTC
What version of pirut is this with?

Comment 5 Troy Deierling 2007-08-20 22:06:36 UTC
Hi,

It's 1.3.11-1.fc8.noarch



Comment 6 Troy Deierling 2007-08-20 22:09:26 UTC
Had another problem at the same time... related?  Bug 253471

Comment 7 Troy Deierling 2007-08-21 00:25:32 UTC
Oh, sound is dead too as well as the desktop background.

Comment 8 Jeremy Katz 2007-08-21 14:19:36 UTC
Okay, fixed up the problem in pirut CVS.  Will be in 1.3.12


Note You need to log in before you can comment on or make changes to this bug.