[Bug 171136] New: Trying to add scripts not ending in ".sh" to run on "Pre-KDE startup" generates no warning

Michael Liddle michael at liddle.net.nz
Tue Sep 16 06:52:13 BST 2008


http://bugs.kde.org/show_bug.cgi?id=171136

           Summary: Trying to add scripts not ending in ".sh" to run on
                    "Pre-KDE startup" generates no warning
           Product: systemsettings
           Version: 4.1
          Platform: SuSE RPMs
        OS/Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: michael at liddle.net.nz


Version:            (using KDE 4.1.1)
Installed from:    SuSE RPMs

Bahaviour:
---------

- In the Autostart module, I add a script whose name does not end in ".sh", and
set it to be run "Pre-KDE startup". 
- I log out and log in again. 
- KWrite opens with the script that I added. 
- A dialog appears saying that "KLauncher could not be reached via D-BUS
etc..."
- I click OK, and am _immediately logged out_.
- Subsequent investigation showed that the script was instead added to the
Autostart directory.

Expected:
--------

The documentation states that only scripts ending in ".sh" can be added to the
Pre-KDE startup. 

This is an esoteric restriction in Unix and should either be removed, or when a
user tries to add such a script it should fail, at add time, with a message
explaining why...


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list