Bug 313617 - kdevelop4 fails to install when using the 'kdesu' utility
Summary: kdevelop4 fails to install when using the 'kdesu' utility
Status: RESOLVED WORKSFORME
Alias: None
Product: kdesu
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdesu bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-21 13:06 UTC by Christian Reiner
Modified: 2023-01-31 05:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Reiner 2013-01-21 13:06:52 UTC
When configuring kdevelop to use the 'kdesu' utility and 'install as root', installation of an application fails. The same installation started from command line succeeds. So I'd say the system in general is sane, kdesu works as expected (I use it for other purposes too). 
My impression is that there is a communication problem between kdevelop and kdesu. When starting the installation kdesu pops up a password dialog. After entering the password the installation fails however. Here is the output of an installation attempt as taken from the kdevelop internal console: 

kdesu(24349)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /home/abuild/rpmbuild/BUILD/kdelibs-4.9.5/kdesu/process.cpp : 293 ]  Running "/usr/bin/su"
kdesu(24349)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /home/abuild/rpmbuild/BUILD/kdelibs-4.9.5/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(24349)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /home/abuild/rpmbuild/BUILD/kdelibs-4.9.5/kdesu/process.cpp : 293 ]  Running "/usr/bin/su"
kdesu(24349)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /home/abuild/rpmbuild/BUILD/kdelibs-4.9.5/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(24349)/kdesu (kdelibs) KDESu::PtyProcess::WaitSlave: [ /home/abuild/rpmbuild/BUILD/kdelibs-4.9.5/kdesu/process.cpp : 379 ]  Child pid 24355
kdesu(24349)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /home/abuild/rpmbuild/BUILD/kdelibs-4.9.5/kdesu/su.cpp : 259 ]  Read line ""
kdesu(24349)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /home/abuild/rpmbuild/BUILD/kdelibs-4.9.5/kdesu/su.cpp : 259 ]  Read line "kdesu_stub"
*** Failure: Exit code 2 ***

Note that the password dialog is opened only once. It appears like kdesu is not able to use the (correct) password as expected. However as written kdesu succeeds with the same command using the same password when started from command line.

This issue is not new. I experienced this issue for more than a year now, maybe even several years. 

Reproducible: Always
Comment 1 Aleix Pol 2013-06-12 01:41:36 UTC
Using kdesu from the console works as expected? Seems to me like a kdesu bug...
Comment 2 Christian Reiner 2013-06-12 06:29:55 UTC
Unlike noted before kdesu shows the same misbehaviour when used directly from the command line.
Comment 3 Andrew Crouthamel 2018-11-10 03:16:14 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-20 04:03:38 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2023-01-01 04:20:06 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Christian Reiner 2023-01-01 08:50:44 UTC
Are you serious? Really? After only 10 years you ask me if I could please reproduce the issue?
Sorry no, can't help there, obviously. 

I would suggest that you simply close bug entries you fail to deal with after a year. 
For certain this one should simply get closed.
Comment 7 Bug Janitor Service 2023-01-16 05:13:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-31 05:05:44 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!