Re: [Zeitgeist] [Bug 626056] Re: zeitgeist crash when opening activity journal
sure.. python -V : Python 2.6.6 python -c "import time; print time.gmtime(0)" : time.struct_time(tm_year=1970, tm_mon=1, tm_mday=1, tm_hour=0, tm_min=0, tm_sec=0, tm_wday=3, tm_yday=1, tm_isdst=0) 2010/9/7 Markus Korn > Raised importance as other users seem to be affected by this bug too > (see duplicate) > > @xof32, > as you are the reporter of the same issue, can you also please give me the > output of > > python -V > and > > python -c "import time; print time.gmtime(0)" > > > Thanks, > Markus > > ** Changed in: zeitgeist (Ubuntu) > Importance: Undecided => Low > > -- > zeitgeist crash when opening activity journal > https://bugs.launchpad.net/bugs/626056 > You received this bug notification because you are a direct subscriber > of a duplicate bug (632279). > > Status in “zeitgeist” package in Ubuntu: Incomplete > > Bug description: > Binary package hint: zeitgeist > > zeitgest crash when opening activity journal and it dosent display any > information > > ProblemType: Crash > DistroRelease: Ubuntu 10.10 > Package: zeitgeist-datahub 0.5.0-0ubuntu2 > ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 > Uname: Linux 2.6.35-19-generic i686 > Architecture: i386 > Date: Sat Aug 28 17:18:53 2010 > ExecutablePath: /usr/bin/zeitgeist-datahub > InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) > InterpreterPath: /usr/bin/python2.6 > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-datahub > ProcEnviron: > SHELL=/bin/bash > LANG=es_MX.utf8 > PythonArgs: ['/usr/bin/zeitgeist-datahub'] > SourcePackage: zeitgeist > Title: zeitgeist-datahub crashed with OverflowError in () > UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/626056/+subscribe > -- zeitgeist-datahub crash when opening activity journal https://bugs.launchpad.net/bugs/626056 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Incomplete Status in “zeitgeist” package in Ubuntu: Incomplete Bug description: Binary package hint: zeitgeist zeitgest crash when opening activity journal and it dosent display any information ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: zeitgeist-datahub 0.5.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 Architecture: i386 Date: Sat Aug 28 17:18:53 2010 ExecutablePath: /usr/bin/zeitgeist-datahub InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-datahub ProcEnviron: SHELL=/bin/bash LANG=es_MX.utf8 PythonArgs: ['/usr/bin/zeitgeist-datahub'] SourcePackage: zeitgeist Title: zeitgeist-datahub crashed with OverflowError in () UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Merge] lp:~zeitgeist/zeitgeist/HACKING.bugtriaging into lp:zeitgeist
Looks great to me, except for Critical which sounds a bit too melodramatic :P. Good work Markus! -- https://code.launchpad.net/~zeitgeist/zeitgeist/HACKING.bugtriaging/+merge/34840 Your team Zeitgeist Framework Team is requested to review the proposed merge of lp:~zeitgeist/zeitgeist/HACKING.bugtriaging into lp:zeitgeist. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Translation template import - zeitgeist in Zeitgeist Framework 0.3
Hello Zeitgeist Framework Team, On 2010-09-08 09:52z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-09-08 09:52z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 602211] Re: Monitoring for new files
The more I think about it, the more I see this bug has no place here. I agree with Markus now that the bug should be if handled then by the Zeitgeist Datahub, or Nautilus or so sending us the info directly. Thus I am marking it as invalid. ** Changed in: zeitgeist Status: New => Invalid ** Changed in: zeitgeist-datahub Status: New => Incomplete -- Monitoring for new files https://bugs.launchpad.net/bugs/602211 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Invalid Status in Zeitgeist Datahub: Incomplete Bug description: I was thinking on how tracker monitors new files to index. Turns out they monitor directories using inotify. Recurse XDG dirs and single iterate $HOME Does this make sense to us? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 630593] Re: Replace old datahub with vala port
** Changed in: zeitgeist Status: New => In Progress ** Changed in: zeitgeist-datahub Status: New => In Progress -- Replace old datahub with vala port https://bugs.launchpad.net/bugs/630593 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Status in Zeitgeist Datahub: In Progress Bug description: Now with mhr3's vala datahub port, I think we should get rid of the python version ASAP. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 607504] Re: zeitgeist-datahub crashed with ImportError in ()
** Changed in: zeitgeist Status: New => Incomplete -- zeitgeist-datahub crashed with ImportError in () https://bugs.launchpad.net/bugs/607504 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Incomplete Status in “zeitgeist” package in Ubuntu: Incomplete Bug description: Binary package hint: zeitgeist Ubuntu 10.10 alpha, updated to midnight 20th july ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: zeitgeist-datahub 0.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5 Uname: Linux 2.6.35-9-generic i686 Architecture: i386 Date: Mon Jul 19 17:17:34 2010 ExecutablePath: /usr/bin/zeitgeist-datahub InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-datahub ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.utf8 PythonArgs: ['/usr/bin/zeitgeist-datahub'] SourcePackage: zeitgeist Title: zeitgeist-datahub crashed with ImportError in () Traceback: Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/gtk-2.0/gi/__init__.py", line 23, in from ._gi import _API ImportError: libgirepository-1.0.so.0: cannot open shared object file: No such file or directory UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 626056] Re: zeitgeist-datahub crash when opening activity journal
** Changed in: zeitgeist Status: New => Incomplete -- zeitgeist-datahub crash when opening activity journal https://bugs.launchpad.net/bugs/626056 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Incomplete Status in “zeitgeist” package in Ubuntu: Incomplete Bug description: Binary package hint: zeitgeist zeitgest crash when opening activity journal and it dosent display any information ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: zeitgeist-datahub 0.5.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 Architecture: i386 Date: Sat Aug 28 17:18:53 2010 ExecutablePath: /usr/bin/zeitgeist-datahub InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-datahub ProcEnviron: SHELL=/bin/bash LANG=es_MX.utf8 PythonArgs: ['/usr/bin/zeitgeist-datahub'] SourcePackage: zeitgeist Title: zeitgeist-datahub crashed with OverflowError in () UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 628678] Re: Add bugtriaging guidlines to HACKING
** Branch linked: lp:~zeitgeist/zeitgeist/HACKING.bugtriaging -- Add bugtriaging guidlines to HACKING https://bugs.launchpad.net/bugs/628678 You received this bug notification because you are a member of Zeitgeist Framework Team, which is a bug assignee. Status in Zeitgeist Framework: Confirmed Bug description: I've discussed the bugtriaging topic with Seif on irc yesterday, it turned out that we have different opinions on how to triage bugs for the zeitgeist project. We agreed that this needs some discussion, and the final words should be put in our HACKING document. Here is an extract of our discussion: seif_: can you please tell me what your criteria for choosing the importance of a bugreport is? I think we should have one definition for importance level throught the whole team thekorn, yeah thekorn, if its a build problem or a crash then its critical :P if its a wrong functionality then its high and medium,low or wishlist? if its an incomplete feature its medium low and wishlist are intuition :P seif_: so if someone tries to build zeitgeist on some very rare linux system, but the build fails, this bug will automatically be critical? yeah it means we cant delivder but ofcourse define rare only one affected user hmm i think it should be seen on a distro level thekorn, what distro is he using actually wrong if he is using our dependencies then it should work seif_: also, what dos "fix committed" mean for you? there is a fix in the branches in which branch? lp:~thekorn/+junk/boo.bar.baz? any branch proposed for merging ok, and fix released means: the fix landed in lp:zeitgeist? so lp:zeitgeist is our release target, and we do not really care about release tarballs? thekorn, nope i thought u said trunk always has to be stable thus we work in branches IMHO, fix releasedm eans: we have a tarball release which shipps this fix and fix committed means it's in lp:zeitgeist in progress means, there is a fix somewhere thekorn, ok ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Merge] lp:~zeitgeist/zeitgeist/HACKING.bugtriaging into lp:zeitgeist
Markus Korn has proposed merging lp:~zeitgeist/zeitgeist/HACKING.bugtriaging into lp:zeitgeist. Requested reviews: Zeitgeist Framework Team (zeitgeist) Related bugs: #628678 Add bugtriaging guidlines to HACKING https://bugs.launchpad.net/bugs/628678 I started working on adding information about bugtriaging in the zeitgeist project to HACKING, I'm sure this still needs some fixing, and discussions. but it seems to me that the merge proposal is the right forum to discuss it as we can easily see the diff. So, comment, thoughts, fixes welcome. -- https://code.launchpad.net/~zeitgeist/zeitgeist/HACKING.bugtriaging/+merge/34840 Your team Zeitgeist Framework Team is requested to review the proposed merge of lp:~zeitgeist/zeitgeist/HACKING.bugtriaging into lp:zeitgeist. === modified file 'HACKING' --- HACKING 2010-09-06 14:43:18 + +++ HACKING 2010-09-08 09:02:45 + @@ -92,3 +92,75 @@ 12. Now you deserve a treat! +Bugs + + +The zeitgeist project is using the bugtracker on launchpad.net. To report +a bug please visit https://bugs.edge.launchpad.net/zeitgeist/+filebug +and describe the issues you are having. Please also add useful information +like the version of zeitgeist you are using and the python version. +Appart from classical bugreport describing an an issue or failure, the +zeitgeist team is using the bugtracker to discuss new features and +implementation details. + +Bugtriaging +*** + +The zeitgeist project is using bug status as described below: + * New: no bugtriager had a look at this bugreport + * Incomplete: the zeitgeist team has asked an explicit question + to get a better understanding of the bug and is waiting for + an answer from the original reporter or anyobne having the same issue + * Invalid: It turned out that the issue is not a bug in zeitgeist, or + cannot be fixed in zeitgeist. + * Won't Fix: based on the information we got on the bugreport we decided + that we don't want to fix this bug in a reasonable timeframe. + * Triaged: Based on the information in the bugreport zeitgeist developers + understand the issue and are able to start fixing it. + * In Progress: Someone is working on a fix. There should be a branch + attached to the bugreport, and the zeitgeist task should be assigned to + the developer who is working on the fix. + * Fix Committed: The fix for this bug has been merged into lp:zeitgeist. + When setting this status the triager should add information about the + revision in which the fix landed, and also ask the reporter and other + affected user to test the fix. + * Fix Released: The fix was released in a release of zeitgeist. +The 'Opinion' status is not used by zeitgeist. + +The importance of a bug is set by following this criterias: + * Undecided: No decission has been made. + * Wishlist: we are marking feature requests as wishlist + * Low: issues affecting only a small number of users are marked as Low + * Medium: bugs which are affecting a significantly number of users are + of medium importance. + * High: This class of bugs must be fixed before the next release, esp. + failures of our testsuite are resulting in bugs which are marked as + 'High'. Also different kind of regressions (crashes, performance etc.) + are marked with this importance. + * Critical: This bug status is very carefully used by zeitgeist, + whenever this status is set all development ressources are put into + fixing this bug, no changes to lp:zeitgeist are allowed until this + bug get fixed. Example for this kind of bugs include build errors, + undocumented API changes or instantaneous crashes of the + zeitgeist-daemon. + +Milestones: + * If we plan to fix a big with a status of 'Wishlist', 'Low' or 'Medium' + we should target this bug to a milestone + * 'High' and 'Critical' rated bugs will always be targeted to the next + milestone. + +Related policies: + * Every bug of status 'Triaged' or higher should have an importance other + than 'Undecided'. + * Each bug with status higher than 'In Progress' should get an assignee. + Assigning a bug to a dev should never be done without talking to him/her. + +Blueprints +** + +Blueprints are used in the zeitgeist project to describe a development +story. Whenever a certain feature requires fixes for multiple bugs or +multiple branches to be merged we use blueprints to organize the efforts +under one central umbrella. The assignee of a blueprint is leading all +the work to get this blueprint and all its features/fixes implemented. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 628678] Re: Add bugtriaging guidlines to HACKING
I never said we are shipping it with 0.5.1 tarball. I meant it should exist before we start working on 0.6 On Tue, Sep 7, 2010 at 7:25 PM, Markus Korn wrote: > Seif, we are not shipping HACKING in our release tarball, so it does not > really matter *when* changes to the HACKING document enter lp:zeitgeist. > So my idea is, let's get 0.5.1 out first, then discuss this topic further, > and once our bug triaging process is described in HACKING it takes effect. > > -- > Add bugtriaging guidlines to HACKING > https://bugs.launchpad.net/bugs/628678 > You received this bug notification because you are subscribed to The > Zeitgeist Project. > > Status in Zeitgeist Framework: Confirmed > > Bug description: > I've discussed the bugtriaging topic with Seif on irc yesterday, it turned > out that we have different opinions on how to triage bugs for the zeitgeist > project. We agreed that this needs some discussion, and the final words > should be put in our HACKING document. > > Here is an extract of our discussion: > > seif_: can you please tell me what your criteria for choosing the > importance of a bugreport is? > I think we should have one definition for importance level > throught the whole team > thekorn, yeah > thekorn, if its a build problem or a crash then its critical > :P > if its a wrong functionality then its high > and medium,low or wishlist? > if its an incomplete feature its medium > low and wishlist are intuition > :P > seif_: so if someone tries to build zeitgeist on some very rare > linux system, but the build fails, this bug will automatically be critical? > yeah > it means we cant delivder > but ofcourse define rare > only one affected user > hmm > i think it should be seen on a distro level > thekorn, what distro is he using > actually wrong > if he is using our dependencies > then it should work > seif_: also, what dos "fix committed" mean for you? > there is a fix in the branches > in which branch? > lp:~thekorn/+junk/boo.bar.baz? > any branch proposed for merging > ok, and fix released means: the fix landed in lp:zeitgeist? > so lp:zeitgeist is our release target, and we do not really care > about release tarballs? > thekorn, nope > i thought u said trunk always has to be stable > thus we work in branches > IMHO, fix releasedm eans: we have a tarball release which shipps > this fix > and fix committed means it's in lp:zeitgeist > in progress means, there is a fix somewhere > thekorn, ok > > > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- Add bugtriaging guidlines to HACKING https://bugs.launchpad.net/bugs/628678 You received this bug notification because you are a member of Zeitgeist Framework Team, which is a bug assignee. Status in Zeitgeist Framework: Confirmed Bug description: I've discussed the bugtriaging topic with Seif on irc yesterday, it turned out that we have different opinions on how to triage bugs for the zeitgeist project. We agreed that this needs some discussion, and the final words should be put in our HACKING document. Here is an extract of our discussion: seif_: can you please tell me what your criteria for choosing the importance of a bugreport is? I think we should have one definition for importance level throught the whole team thekorn, yeah thekorn, if its a build problem or a crash then its critical :P if its a wrong functionality then its high and medium,low or wishlist? if its an incomplete feature its medium low and wishlist are intuition :P seif_: so if someone tries to build zeitgeist on some very rare linux system, but the build fails, this bug will automatically be critical? yeah it means we cant delivder but ofcourse define rare only one affected user hmm i think it should be seen on a distro level thekorn, what distro is he using actually wrong if he is using our dependencies then it should work seif_: also, what dos "fix committed" mean for you? there is a fix in the branches in which branch? lp:~thekorn/+junk/boo.bar.baz? any branch proposed for merging ok, and fix released means: the fix landed in lp:zeitgeist? so lp:zeitgeist is our release target, and we do not really care about release tarballs? thekorn, nope i thought u said trunk always has to be stable thus we work in branches IMHO, fix releasedm eans: we have a tarball release which shipps this fix and fix committed means it's in lp:zeitgeist in progress means, there is a fix somewhere thekorn, ok ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 626056] Re: zeitgeist-datahub crash when opening activity journal
** Summary changed: - zeitgeist crash when opening activity journal + zeitgeist-datahub crash when opening activity journal -- zeitgeist-datahub crash when opening activity journal https://bugs.launchpad.net/bugs/626056 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Status in “zeitgeist” package in Ubuntu: Incomplete Bug description: Binary package hint: zeitgeist zeitgest crash when opening activity journal and it dosent display any information ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: zeitgeist-datahub 0.5.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 Architecture: i386 Date: Sat Aug 28 17:18:53 2010 ExecutablePath: /usr/bin/zeitgeist-datahub InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-datahub ProcEnviron: SHELL=/bin/bash LANG=es_MX.utf8 PythonArgs: ['/usr/bin/zeitgeist-datahub'] SourcePackage: zeitgeist Title: zeitgeist-datahub crashed with OverflowError in () UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
