[opensuse] kdesu bug when path includes spaces (openSUSE 11.0 Beta3 KDE4 LiveCD x86_64)
Hi, I have a directory (/home/michael/openSuSE x64 Packages/) with a package (truecrypt-5.1a-0.x86_64.rpm) in it. When I click on the RPM in Dolphin, KDE su launches with the following command "/sbin/yast2 --install /home/michael/openSuSE x64 Packages/truecrypt-5.1a-0.x86_64.rpm". After I enter my root password, I get three separate errors: 1) Package Packages/truecrypt-5.1a-0.x86_64.rpm was not found on the medium. 2) Package x64 was not found on the medium. 3) Package /home/michael/openSuSE was not found on the medium. After the three errors, YaST quits. The errors are obviously related to the spaces. But I am not sure if this is openSuSE's problem or KDE's problem. I am inclined to believe that the error lies with openSuSE because kdesu has no way of knowing the last part is a path. I think there is a bug in one of the openSuSE scripts. Should I create a bug for this at bugzilla.novell.com? Also, I could use some help picking a better description since this is not really a kdesu bug in my opinion. Can anyone tell me what those "scripts" are called? Thanks in advance. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
"Michael Mientus" <michael.mientus@gmail.com> writes:
Hi,
I have a directory (/home/michael/openSuSE x64 Packages/) with a package (truecrypt-5.1a-0.x86_64.rpm) in it. When I click on the RPM in Dolphin, KDE su launches with the following command "/sbin/yast2 --install /home/michael/openSuSE x64 Packages/truecrypt-5.1a-0.x86_64.rpm". After I enter my root password, I get three separate errors: 1) Package Packages/truecrypt-5.1a-0.x86_64.rpm was not found on the medium. 2) Package x64 was not found on the medium. 3) Package /home/michael/openSuSE was not found on the medium. After the three errors, YaST quits.
The errors are obviously related to the spaces. But I am not sure if this is openSuSE's problem or KDE's problem. I am inclined to believe that the error lies with openSuSE because kdesu has no way of knowing the last part is a path. I think there is a bug in one of the openSuSE scripts.
Should I create a bug for this at bugzilla.novell.com?
Yes, please. We can always tell you it's an upstream bug.
Also, I could use some help picking a better description since this is not really a kdesu bug in my opinion. Can anyone tell me what those "scripts" are called?
The KDE team will know for sure, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Yes, please. We can always tell you it's an upstream bug.
I'll try to feel out the KDE team. But their bugtracker is irritating since it only gives 20 results at a time. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I posted in Bug 394182 about this issue. And it was marked as a duplicate of Bug 389765. I would like to try Lubos Lunak's package. But I am not sure where it is. (See comment 11: https://bugzilla.novell.com/show_bug.cgi?id=389765#c11). I have these repositories for YaST: 1) http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/openS... 2) http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/ 3) http://download.opensuse.org/update/11.0/ But I can't find his package. How can I get that package? Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-05-26 at 14:31 -0500, Michael Mientus wrote:
But I can't find his package.
How can I get that package?
You should ask this in the factory list, not here. However, if after making sure your factory is updated (zypper dup) you keep having the problem, you should consider reopening the bugzilla. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIO0BItTMYHG2NR9URApZEAKCLM5LFthP03zIgiutNa5sBSAQc2ACfXbCw MUxvK/3RF+yx74uScRNUFmo= =/BtK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michael Mientus wrote:
Hi,
I have a directory (/home/michael/openSuSE x64 Packages/) with a package (truecrypt-5.1a-0.x86_64.rpm) in it. When I click on the RPM in Dolphin, KDE su launches with the following command "/sbin/yast2 --install /home/michael/openSuSE x64 Packages/truecrypt-5.1a-0.x86_64.rpm". After I enter my root password, I get three separate errors: 1) Package Packages/truecrypt-5.1a-0.x86_64.rpm was not found on the medium. 2) Package x64 was not found on the medium. 3) Package /home/michael/openSuSE was not found on the medium. After the three errors, YaST quits.
The errors are obviously related to the spaces. But I am not sure if this is openSuSE's problem or KDE's problem. I am inclined to believe that the error lies with openSuSE because kdesu has no way of knowing the last part is a path. I think there is a bug in one of the openSuSE scripts.
Should I create a bug for this at bugzilla.novell.com?
Yes, it's a bug. However, why in the world are you making directory names with embedded spaces when you KNOW they cause problems because all commands use anywhitespace as an argument delimeter? To avoid this bug, just stop using bug-inducing directory and file names. You could have just as easily named the directory openSUSE_x64_Packages and everything would be fine.
Also, I could use some help picking a better description since this is not really a kdesu bug in my opinion. Can anyone tell me what those "scripts" are called?
They're called scripts -- without any scare-quotes :-)
Thanks in advance.
Mike
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, May 25, 2008 at 10:09 PM, Washington Irving <washton.irving@gmail.com> wrote:
To avoid this bug, just stop using bug-inducing directory and file names.
You could have just as easily named the directory openSUSE_x64_Packages and everything would be fine.
Well, on the other hand, it was my impression that linux at least pretended to be a posix system most of the time. This should have worked for the OP. If I click almost any file with embedded spaces in Kong it does the right thing and successfully opens the file using the appropriate default application, and escapes the spaces properly. I would have thought a better term would be "Bug Revealing" because the bug was always there, waiting. The bug was induced by the software coder, not the user. Further, it works with an RPM file in Kong, so there is no excuse for it failing in Dolphin. In fact it seems just one more demonstration of how stunningly bad the idea of replacing Kong with Dolphin instead of spending that development time getting all the missing pieces working in kde4. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Andreas Jaeger -
Carlos E. R. -
John Andersen -
Michael Mientus -
Washington Irving