Bug 709580

Summary: bootconf break Quit menu in Kickoff menu (KDE)
Product: [Fedora] Fedora Reporter: dominique <chepioq>
Component: bootconfAssignee: Sam Varshavchik <mrsam>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: mrsam
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 17:26:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description dominique 2011-06-01 04:44:24 UTC
For test I install bootconf and bootconf-gui.

After this install and after reboot I am not able use Quit menu in my kde menu (Kickoff).
I click on different button but nothing appear.

I remove bootconf and after my kickoff menu work well.

Comment 1 Sam Varshavchik 2011-06-01 11:19:10 UTC
Cannot reproduce your bug. I can launch bootconf-gui, and log out from the KDE menu without any issues. bootconf-gui is based on pygtk, and not kde/qt. Please provide more detail, screenshots if possible.

Comment 2 dominique 2011-06-01 14:10:11 UTC
For test I re-install bootconf and bootconf-gui.
I have same problem, in .xsession-errors log I have this error when I want reload with kickoff menu:
 
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x1a034b9
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x1a034b9
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x1a034b9
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x1a034b9

I think it's not a bug but a problem with my configuration, because some french
fedora users use bootconf without any troubles...

Comment 3 Sam Varshavchik 2011-06-01 14:53:28 UTC
Ok. If you are able to come up with additional information, please update this bug. I cannot reproduce this bug.

Comment 4 Fedora End Of Life 2012-08-07 17:26:14 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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