The thing is. This bug is in KDE software, ought to be fixed there, will
be fixed... Only once fixed it will arrive in Ubuntu. The KDE software
compilation consists of million lines of code and it is simply
impossible for us to digg through a good part of that to fix, excuse the
word, minor issue.
Thanks, telling me to file the bug upstream is a much more useful reply
than simply marking it invalid. I shall do so.
I hope that in future Launchpad will help maintainers refile bugs
automatically? The reason I ask is that it seems unreasonable to expect
users to know where to file bugs, and
I find that this bug is already filed upstream:
https://bugs.kde.org/show_bug.cgi?id=169660
** Bug watch added: KDE Bug Tracking System #169660
http://bugs.kde.org/show_bug.cgi?id=169660
--
ktimetracker starts some karm tasks after upgrade
https://bugs.launchpad.net/bugs/288945
You received
** Changed in: kdepim (Ubuntu)
Status: Incomplete = Invalid
--
ktimetracker starts some karm tasks after upgrade
https://bugs.launchpad.net/bugs/288945
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in ubuntu.
--
kubuntu-bugs
I am unclear why merely because the user who originally reported a bug
does not wish to reinstall a program that has a sufficiently serious bug
that he no longer uses it makes the bug invalid.
As I reported above, the bug is still present in Lucid. I therefore no
longer use ktimetracker, and do
Well, it's not like we can spend time fixing something that might not
even be broken anymore, especially since you seem to be the only person
in the year and a half that this has been open that seems to have been
affected by this.
--
ktimetracker starts some karm tasks after upgrade
First, the bug is definitely still present in Lucid, as I have said
above, twice.
Secondly, I quite appreciate your point about limited resources, but
because the resources are not available to fix a bug does not mean it is
invalid! There's no point simply closing bug reports because you do not
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and
your problem may have been
As the bug was indeed still present in 10.04, I gave up and started
using gnome-time-tracker (Project Hamster) instead, so I no longer use
KTimeTracker. However, I am unaware of any relevant log (none was ever
posted by me or by apport when I originally reported the bug), and the
bug is exactly
** Changed in: kdepim (Ubuntu)
Status: Incomplete = New
--
ktimetracker starts some karm tasks after upgrade
https://bugs.launchpad.net/bugs/288945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It was, as you excellently put it, inappropriately starting previously
set tasks. Since it was a one-off bug at upgrade time (starting
ktimetracker again shows everything being well), I can't provide a
screenshot, sorry.
--
ktimetracker starts some karm tasks after upgrade
Thanks for reporting this bug. Could you describe the tasks that get
started more fully. Do they resemble tasks that you had previously set
up in karm. What I'm trying to get at is whether Karm is inappropriately
starting previously set tasks or whether it is spontaneously generating
new tasks. If
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18872224/Dependencies.txt
--
ktimetracker starts some karm tasks after upgrade
https://bugs.launchpad.net/bugs/288945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
13 matches
Mail list logo
