Bug 750085

Summary: Unneeded and incorrect pop-up displayed after successful exit when running as "root."
Product: [Fedora] Fedora Reporter: Peter Trenholme <PTrenholme>
Component: kateAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 16CC: jreznik, kevin, ltinkl, rdieter, rnovacek, than
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: 2013-02-13 23:18:44 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 Peter Trenholme 2011-10-30 19:00:23 UTC
Description of problem:
When kate is invoked from the KDE menu with the "advanced" option "Run as user" checked, and "root" specified, kate runs correctly as "root" but, when kate is exited, a pop-up claiming, incorrectly, that "KDEInit could not launch '/usr/libexec/kde4/kdesu'." is displayed.

Version-Release number of selected component (if applicable):
$ kate --version
Qt: 4.8.0
KDE Development Platform: 4.7.2 (4.7.2)
Kate: 3.7.2

How reproducible:
Every time

Steps to Reproduce:
1.Start kate (Superuser) from the menu
2.exit
3.
  
Actual results:
Unneeded, incorrect pop-up displayed

Expected results:
No pop-up

Additional info:
I posted this as a kate bug because, for example, when krusaer is invoked as "root" with the same menu settings, the pop-up is NOT displayed.

Comment 1 Peter Trenholme 2011-10-30 19:08:33 UTC
Oops! This may be a Lancelot bug.

I just realized that I was invoking from the Lancelot menu, not the KDE one, and, when I tried it from the standard menu, the pop-up was not displayed.

Note, however, that the Krusader program, when invoked from the Lancelot menu, did not display the erroneous pop-up.

In any case, as I noted, this is more a cosmetic "bug" than one causing some real problem.

Comment 2 Fedora End Of Life 2013-01-16 19:30:03 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" 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

Comment 3 Fedora End Of Life 2013-02-13 23:18:47 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.