[Bug 279968] New: KDE complete lockup with admin autostart script

[9bv1tu2a]

https://bugs.kde.org/show_bug.cgi?id=279968

           Summary: KDE complete lockup with admin autostart script
           Product: kde
           Version: 4.6
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: 9bv1tu2a at cogeco.ca


Version:           4.6 (using KDE 4.6.5) 
OS:                Linux

Hello ...

Got a problem with start-stop-daemon not starting cron and at on bootup so I
wrote an admin script which has two lines, cron start and aptitude
update/full-upgrade and lodged it in autostart folder.

Unfortunately with this arrangement KDE never fully completes loading. I
usually end up with a partial freeze and a partially populated system tray. I
can secondary click the desktop and get the menu but clicking Leave does
nothing. KDE fully locks up. The bottom panel with autohide never shows. Hard
reboot (power off/on) necessary to recover.


Reproducible: Always

Steps to Reproduce:
Power up KDE with admin autostart script

Actual Results:  
KDE freezes at some stage prior to fully loading all apps in the system tray.
It appears that the script with a request for password stops KDE fully loading
and thus crashes KDE.

Expected Results:  
KDE should load normally and does fully load when the startup script is
removed.

I suspect that the problem is when the autostart item loads. I assumed,
incorrectly that the item started after everything was loaded but that is not
the case. Many of the items that I have in the system tray are loaded after the
main KDE component is loaded so my admin script loads prior to some of the
items in the system tray thus causing the crash.

My workaround is to manually start the script with a click after everything is
loaded. Kalarm seeems to load last on my setup so I tried it but the option to
start a script on startup is non-existent.

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