Bug 8114 - OpenBox opens but can't close itself
Summary: OpenBox opens but can't close itself
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-17 22:29 CET by ra oeai
Modified: 2015-02-12 00:49 CET (History)
2 users (show)

See Also:
Source RPM: OpenBox
CVE:
Status comment:


Attachments

Description ra oeai 2012-11-17 22:29:02 CET
Description of problem:
i've installed x64 mageia with @Other desktop
well the lxde is working
i've installed compiz then and tried drak3d +compiz 3d effects - select then lxde - nothing happened the display is the same while i've tried this in x32 and something was different i saw some kind of buggy display since that was through qemu  and i've decided that it works, under (virtualbox not qemu) x64 there was no any display change.
then i've tried to boot openbox - just the black screen (so maybe it is working? i'm not sure), then i've disabled the 3d desktop and booted openbox normally
and then
both x32 and x64 cannot properly exit the openbox session

and probably something wrong with compiz 3d desktop under x64.

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

How reproducible:


Steps to Reproduce:
1. Install other desktop
2. boot lxde desktop relogin to openbox
3. press lmb menu exit
Comment 1 Manuel Hiebel 2012-11-28 22:53:55 CET
any logs in your .xsession-errors file ?

Component: Release (media or process) => RPM Packages

Comment 2 ra oeai 2012-11-29 00:13:57 CET
i think that there's simply no command "exit-session" for exit button in OB-Menu, not really sure, ll check it later
Comment 3 Nic Baxter 2015-02-12 00:49:20 CET
Unable to reproduce in Mageia 5. In new installation of openbox on Virtualbox, right click on Desktop gives logout option. Works.

Status: NEW => RESOLVED
CC: (none) => nic
Resolution: (none) => FIXED


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