Bug 140498 - Caught a segmentation fault while loading plugin file: /usr/lib/gstreamer-0.8/libgstalsa.so
Summary: Caught a segmentation fault while loading plugin file: /usr/lib/gstreamer-0.8...
Keywords:
Status: CLOSED DUPLICATE of bug 140081
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer-plugins
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Colin Walters
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-23 04:09 UTC by Corey T.
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Corey T. 2004-11-23 04:09:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
Recently all of sudden on login to Gnome I started getting messages of
"eggcups can't start" and "gnome-volume-manager" can't start. I don't
know if these are related, but the first time I saw these error I got
a message error about gnome-volume-control applet crashing. Then it
asked me if I wanted to try reloading the applet, I said yes but I had
no luck. Then I tried to load gnome-volume-manager from a terminal, it
give me the following message when I try to load it:

gnome-volume-control

ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.8/libgstalsa.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.

This is bizzare, and I'm sure why this is happening. Help!

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Not sure what caused the crashing in the first place, used to work fine
2.
3.
    

Additional info:

Comment 1 Colin Walters 2004-11-23 04:16:05 UTC
Try running prelink on it:

prelink /usr/lib/gstreamer-0.8/libgstalsa.so
(as root)


Comment 2 Corey T. 2004-11-23 05:26:00 UTC
I ran prelink as you suggested and not gnome-volume-control works
properly. Do I have to do this each time I restart or should it be
okay now? Would this be a result of installing packages like
rhythmbox-xine and totem-xine from freshrpms? Cause this seemed to
have started happening after I installed those packages. I also
upgraded the kernel around that time so maybe that caused some things
to be unlinked (?). Weird. Thanks for the fix!

Comment 3 Corey T. 2004-11-23 05:27:11 UTC
Sorry, I meant gnome-volume control works properly now (not not as I
said above).

Comment 4 Colin Walters 2004-11-23 05:32:46 UTC
It's a prelink bug, hopefully an update will come out soon.


*** This bug has been marked as a duplicate of 140081 ***

Comment 5 Red Hat Bugzilla 2006-02-21 19:07:14 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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