[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 285434] New: Ktimetracker reached advanced level of decomposition
From:       Cristian Tibirna <tibirna () kde ! org>
Date:       2011-10-31 23:54:00
Message-ID: bug-285434-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

           Summary: Ktimetracker reached advanced level of decomposition
           Product: ktimetracker
           Version: unspecified
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: NEW
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: dev@staerk.de
        ReportedBy: tibirna@kde.org


Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

Starting ktimetracker in a virgin startup configuration gives a message "Could
not create the KTimeTracker part" then an empty window.

But the bigger problem is that, if ktimetracker is installed, Kontact uses it,
with disastruous effects, lowering considerably the user experience for Kontact
as a whole. Even if ktimetracker is not installed, Kontact displays an icon
offering time tracking but raises an error when trying to use it, to the effect
that timetracker resource is absent/not installed. In some distributions,
ktimetracker is NOT installed by default, even if kontact should require it.

As I said, when ktimetracker is used by kontact, clicking on the "Time
tracking" icon brings up a resemblence of a function GUI, but trying to add a
new task just brings forth the dialog for naming a new task but then raises the
message "Error storing new task. Your changes were not saved. Make sure you can
edit your iCalendar file. Also quit all applications using this file and remove
any lock file related to its name from ~/.kde/share/apps/kabc/lock/".

One has to fiddle a lot around to realize that the problem is that ktimetracker
is started in kontact without an open document. Opening a document manually
brings back all the functionality that we expect. Creating a new  timetracking
document with "New"  action (from menu or toolbar) is another way of rendering
ktimetracker useable inside kontact. But clicking on the "New" action doesn't
do anything visible, so it is difficult to realize that this was a necessary
step.

Let's go back to the default state of ktimetracker in kontact at startup
(seemingly active GUI but that doesn't do anything). In this state, invoking
the action "Close" makes the GUI of ktimetracker vanish (it is replaced by an
empty widget) but the search lineedit remains. Writing anything in this line
edit or trying to create a new ktimetracker document using the action "New"
crashes kontact.

Finally (but certainly not lastly, unfortunately), the menu merging is bungled.
There are two "Quit" actions in the File menu when the timetracker part is
active. This also makes the Ctrl+Q shortcut confused (says so if one tries to
use it).

IMHO either ktimetracker is fixed or it is removed from kontact.



Reproducible: Always

Steps to Reproduce:
1) Start kontact when ktimetracker is not installed. You see icon for
timetracking but there is no fonctionality available.

2) Start kontact with ktimetracker installed. Choose timetracker functionality.
Try to add a task. An error message is raised (see above)

3) Start kontact. Choose timetracker functionality. Click on "Close" (red icon
in toolbar). Type something in the remaining search lineedit => crash


4) Start kontact. Choose timetracker functionality. Click on "Close" (red icon
in toolbar). Click on the "New document" action (or "New task") => crash

5) Start kontact. Choose timetracker functionality. Look at the "File" menu.


Actual Results:  
No functioning.
Crashes.
Bungled menus


Expected Results:  
Buckled up functioning of ktimetracker inside kontact (or even outside) or
remove ktimetracker from kontact.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]