After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 95041 - Nautilus changes related to the new gemdia_* applications path
Nautilus changes related to the new gemdia_* applications path
Status: RESOLVED INVALID
Product: nautilus
Classification: Core
Component: general
unspecified
Other Solaris
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-10-07 04:32 UTC by Narayana Pattipati
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Proposed patch which looks for media_* applications in $prefix path. (2.68 KB, patch)
2002-10-11 07:26 UTC, Narayana Pattipati 		none Details | Review

Description Narayana Pattipati 2002-10-07 04:32:26 UTC 
This is a solaris specific bug. Location of gmedia_* applications should be
$prefix/lib not $prefix/bin. As of now, g_find_program_in_path is used to
find the gmedia_* applications in the user's PATH. 

Changes have to be made to nautilus code to make sure that gmedia_*
applications are looked for in $prefix/lib path instead of $prefix/bin
path.
Comment 1 Narayana Pattipati 2002-10-11 07:26:05 UTC 
Created attachment 11488 [details] [review]
Proposed patch which looks for media_* applications in $prefix path.
Comment 2 Kjartan Maraas 2003-10-28 21:04:16 UTC 
Is this patch still relevant for 2.4.x and later?
Comment 3 Narayana Pattipati 2003-10-29 04:09:53 UTC 
Yeah, the patch is still relavent.

This patch is one of the Solaris removable media patches pending with
Campd. I have made the changes for this bug as part of one big
consolidated patch uploaded to bug#90634. Will mark this bug as
resolved once that patch goes in.
Comment 4 Narayana Pattipati 2004-02-21 07:36:30 UTC 
This patch is for fixing removable media related problem in Solaris.
It does not apply on HEAD anymore as volume management code has
changed in HEAD. Hence closing the bug. Will raise a new bug if the
same problem is found to be there on Solaris running HEAD/2.6.