Comment 3 for bug 696937
Revision history for this message
| Eliah Kagan (degeneracypressure) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
You may be right. I am not confident that this is really a bug. (And I certainly take no issue with it having "wishlist" severity.)
However, there are two reasons why I think this may be an issue for inexperienced users:
(1) Searching the web for "gparted" and text from the error message that is written to the command line when it's run as a non-root user turns up recurring posts by novices asking why they can't get gparted to work.
(2) Even an inexperienced user, especially one who is at all familiar with the command-line, may try to run gparted by pressing Alt+F2 and typing "gparted" (it works for the PolicyKit-using system configuration tools), or by typing "gparted" into a command-line textbox panel applet. This produces silent failure. I think many users find menus provided by desktop environments (whether they be on Ubuntu or other operating systems) to be cumbersome and confusing, and prefer run their less frequently used programs by typing in their names.