Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 520245 - openbox needs subpackages for GNOME and KDE
Summary: openbox needs subpackages for GNOME and KDE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openbox
Version: 15
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: LXDE
TreeView+ depends on / blocked
 
Reported: 2009-08-29 17:12 UTC by Christoph Wickert
Modified: 2011-05-10 03:24 UTC (History)
4 users (show)

Fixed In Version: openbox-3.4.11.2-8.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-10 03:24:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Patch for openbox.spec in devel (1.83 KB, patch)
2009-08-29 17:12 UTC, Christoph Wickert
no flags Details | Diff
Updated patch for openbox.spec in devel (2.00 KB, patch)
2009-08-29 17:18 UTC, Christoph Wickert
no flags Details | Diff
Updated patch for openbox.spec in devel (2.28 KB, patch)
2009-08-29 21:10 UTC, Christoph Wickert
no flags Details | Diff

Description Christoph Wickert 2009-08-29 17:12:15 UTC
Created attachment 359160 [details]
Patch for openbox.spec in devel

Description of problem:
/usr/share/xsessions/openbox-gnome.desktop
/usr/bin/openbox-gnome-session
and
/usr/share/xsessions/openbox-kde.desktop
/usr/bin/openbox-kde-session

are installed no matter if their dependencies are actually met. This will cause trouble for people who just install openbox or LXDE.

Version-Release number of selected component (if applicable):
openbox-3.4.7.2-8.fc11

Steps to Reproduce:
1. Do a fresh install of Fedora with only openbox and slim as login manager. you can also select
2. restart and login
3. slim-dynwm tries to start openbox-gnome as first session. Didn't try GDM and KDM, but I guess they behave similar.

Actual results:
black screen after login, nothing happens.

Additional info:
$ repoquery --whatrequires openbox-libs
openbox-0:3.4.7.2-8.fc11.x86_64
openbox-devel-0:3.4.7.2-8.fc11.x86_64
openbox-devel-0:3.4.7.2-8.fc11.i586

So what's the use of the openbox-libs package?

Comment 1 Christoph Wickert 2009-08-29 17:18:04 UTC
Created attachment 359161 [details]
Updated patch for openbox.spec in devel

This one also moves the manpages into their subpackages.

Comment 2 Christoph Wickert 2009-08-29 17:19:48 UTC
I forgot to increase the release in the above patches. Sorry.

Comment 3 Christoph Wickert 2009-08-29 21:10:23 UTC
Created attachment 359171 [details]
Updated patch for openbox.spec in devel

Ok, this is the correct one. I forget to require the base openbox package.

Comment 4 Miroslav Lichvar 2009-08-31 11:15:54 UTC
The menu entries should be shown only when the binaries specified (gnome-session and startkde) in TryExec exist, so I'd say this is a slim bug.

Comment 5 Christoph Wickert 2009-08-31 12:20:00 UTC
I agree this is a slim bug because update_slim_wmlist doesn't check if the binaries are actually installed.

Nevertheless I'd prefer subpackages because even if the desktop files are not shown you still have the commands themselves installed without their dependencies.

Comment 6 Bug Zapper 2010-04-28 10:03:59 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 7 Bug Zapper 2010-06-28 14:22:52 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 Fedora Update System 2011-05-06 15:45:10 UTC
openbox-3.4.11.2-8.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/openbox-3.4.11.2-8.fc15

Comment 9 Fedora Update System 2011-05-07 15:09:37 UTC
Package openbox-3.4.11.2-8.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openbox-3.4.11.2-8.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/openbox-3.4.11.2-8.fc15
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2011-05-10 03:24:03 UTC
openbox-3.4.11.2-8.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


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