Bug 712640

Summary: Some gnome apps fail outside of the gnome desktop (e.g. rhythmbox)
Product: [Fedora] Fedora Reporter: Dave Blackburn <blackburn>
Component: libgnomeAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:38:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave Blackburn 2011-06-12 03:05:25 UTC
Description of problem:
rhythmbox works fine when running in the gnome desktop at runlevel 5.
It fails when running under a runlevel 3 fvwm environment.
From google searching it appears that some people are able to run rhythmbox in connection with fvwm.

It would be desirable to have all or most gnome apps readily operate outside of gnome desktop environment.

Perhaps there is documentation explaining how to run gnome apps such as rhythmbox outside of the gnome desktop. If so, perhaps it could be made easier to find.

Version-Release number of selected component (if applicable):
libgnome 2.32.0-1.fc14

How reproducible:
run rhythmbox within an fvwm runlevel 3 environment.


Steps to Reproduce:
1. login to a runlevel 3 environment
2. telinit 5
3. verify rhythmbox works in a gnome desktop environment
4. telinit 3
5. bring up fvwm environment
6. run rhythmbox using same selection from play list
  
Actual results:
selection will not play.

Expected results:
selection to play.

Additional info:

Ran the following:
g (gnome)
strace -f rhythmbox  > ~/rhythmbox-strace-gnome 2>&1
f (fvwm)
strace -f rhythmbox  > ~/rhythmbox-strace 2>&1

First succeeds (gnome), second fails (fvwm).

common
[pid  2794] mkdir("/tmp/orbit-blackburn", 0700) = -1 EEXIST (File exists)
[pid  2794] stat64("/tmp/orbit-blackburn", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
[pid  2794] utime("/tmp/orbit-blackburn", [0, 0]) = 0

g (gnome)
[pid  2794] connect(14, {sa_family=AF_FILE, path="/tmp/orbit-blackburn/linc-91a-0-627bfc9a8f14c"}, 48) = 0

f (fvwm)
[pid  3967] bind(11, {sa_family=AF_FILE, path="/tmp/orbit-blackburn/linc-f7f-0-33167a22ce79d"}, 48) = 0
[pid  3967] getsockname(11, {sa_family=AF_FILE, path="/tmp/orbit-blackburn/linc-f7f-0-33167a22ce79d"}, [48]) = 0
[pid  3967] connect(14, {sa_family=AF_FILE, path="/tmp/orbit-blackburn/linc-d55-0-54b5cef116b07"}, 48) = -1 ECONNREFUSED (Connection refused)
[pid  3967] connect(17, {sa_family=AF_FILE, path="/tmp/orbit-blackburn/linc-d24-0-17d85b97d4ee"}, 47) = -1 ENOENT (No such file or directory)
Many ECONNREFUSED or ENOENT
Never succeeds

Running on 32bit single cpu laptop with:
cat /proc/asound/cards
 0 [I82801DBICH4   ]: ICH4 - Intel 82801DB-ICH4
                      Intel 82801DB-ICH4 with VIA1612A at irq 17
 1 [Modem          ]: ICH-MODEM - Intel 82801DB-ICH4 Modem


Perhaps there is a dependency on something in the gnome environment that can be set up for an fvwm (or other non-gnome) environment. Maybe a specific document could be developed.

Comment 1 Fedora End Of Life 2012-08-16 15:38:19 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping