Bug 174020 - kcron with administrator privilegs crashes with SIGSEGV
Summary: kcron with administrator privilegs crashes with SIGSEGV
Status: RESOLVED FIXED
Alias: None
Product: kcron
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Gary Meyer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-01 10:11 UTC by Ákos Mattiassich
Modified: 2010-10-20 02:00 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ákos Mattiassich 2008-11-01 10:11:17 UTC 
Version:           unknown (using 4.1.2 (KDE 4.1.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.24-21-generic

If i try to run kdesudo systemsettings and i click on task scheduler (kcron), the application crashes.

If i call it from konsole, i get the following output:
(hungarian locale)

systemsettings(24292) MainWindow::selectionChanged: Selected item:  "Feladatütemező"
systemsettings(24292) MainWindow::selectionChanged: Comment:        "Időzített feladatok beállítása"
systemsettings(23581) MainWindow::selectionChanged: Needs root privs: false
systemsettings(23581) CTGlobalCron::CTGlobalCron: Initializing CTGlobalCron
systemsettings(23581) CrontabWidget::setupActions: Setup actions
systemsettings(23581) CrontabWidget::setupActions: Actions initialized
systemsettings(23581) CrontabWidget::initialize: Begin view refresh
systemsettings(23581) CrontabWidget::initialize: Creating Tasks list...
systemsettings(23581) GenericListWidget::GenericListWidget: Generic list created
systemsettings(23581) CTHost::findCurrentUserCron: Unable to find the current user Cron. Please report this bug and your crontab config to the developers
KCrash: Application 'systemsettings' crashing...
Comment 1 Pino Toscano 2008-11-01 12:40:31 UTC 
Hello Ákos,

it would be useful if you could post a backtrace if the crash.
You can find instructions about generating one in the following page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Ákos Mattiassich 2008-11-02 19:06:32 UTC 
Here is the backtrace:
Alkalmazás: Rendszerbeállítások (systemsettings), szignál: SIGSEGV
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb61a36c0 (LWP 25291)]
[New Thread 0xb4582b90 (LWP 29505)]
[KCrash handler]
#6  CTCron::isMultiUserCron (this=0x85597a0)
    at /build/buildd/kdeadmin-4.1.2/kcron/src/crontablib/ctcron.cpp:412
#7  0xb45f292e in TasksWidget::refreshHeaders (this=0x85597a0)
    at /build/buildd/kdeadmin-4.1.2/kcron/src/tasksWidget.cpp:239
#8  0xb45f39b4 in TasksWidget (this=0x85597a0, crontabWidget=0x8556328)
    at /build/buildd/kdeadmin-4.1.2/kcron/src/tasksWidget.cpp:60
#9  0xb46033c7 in CrontabWidget::initialize (this=0x8556328)
    at /build/buildd/kdeadmin-4.1.2/kcron/src/crontabWidget.cpp:228
#10 0xb4603627 in CrontabWidget (this=0x8556328, parent=0x854b858, 
    ctHost=0x854c578)
    at /build/buildd/kdeadmin-4.1.2/kcron/src/crontabWidget.cpp:120
#11 0xb460b316 in KCMCron (this=0x854b858, parent=0x833a928)
    at /build/buildd/kdeadmin-4.1.2/kcron/src/kcmCron.cpp:95
#12 0xb460bb91 in KGenericFactory<KCMCron, QWidget>::createObject (
    this=0x8548850, parent=0x833a928, className=0xb7d52f20 "KCModule", 
    args=@0xbfc794a4) at /usr/include/kgenericfactory.tcc:162
#13 0xb79d2cd0 in KPluginFactory::create (this=0x8548850, 
    iface=0xb7d52f20 "KCModule", parentWidget=0x0, parent=0x833a928, 
    args=@0xbfc79690, keyword=@0xbfc79540)
    at /build/buildd/kde4libs-4.1.2/kdecore/util/kpluginfactory.cpp:174
#14 0xb7d964f6 in KService::createInstance<KCModule> (service=@0xbfc7968c, 
    parent=0x833a928, args=@0xbfc79690, error=0xbfc79694)
    at /build/buildd/kde4libs-4.1.2/kdecore/util/kpluginfactory.h:515
#15 0xb7d95362 in KCModuleLoader::loadModule (mod=@0x8543a68, 
    report=KCModuleLoader::Inline, parent=0x833a928, args=@0x8543a50)
    at /build/buildd/kde4libs-4.1.2/kutils/kcmoduleloader.cpp:90
#16 0xb7d9b6ed in KCModuleProxyPrivate::loadModule (this=0x8543a50)
    at /build/buildd/kde4libs-4.1.2/kutils/kcmoduleproxy.cpp:107
#17 0xb7d9c813 in KCModuleProxy::realModule (this=0x833a928)
    at /build/buildd/kde4libs-4.1.2/kutils/kcmoduleproxy.cpp:83
#18 0xb7d9c848 in KCModuleProxy::minimumSizeHint (this=0x833a928)
    at /build/buildd/kde4libs-4.1.2/kutils/kcmoduleproxy.cpp:346
#19 0xb6e30491 in qSmartMinSize () from /usr/lib/libQtGui.so.4
#20 0xb722becb in ?? () from /usr/lib/libQtGui.so.4
#21 0xb722c3f4 in QScrollArea::setWidget () from /usr/lib/libQtGui.so.4
#22 0x080559f5 in _start ()
#0  0xb8079430 in __kernel_vsyscall ()
Comment 3 Christoph Feck 2010-10-20 02:00:18 UTC 
The part where it crashed has been rewritten for KDE 4.2, so I assume it is fixed.