Bug 544344
| Summary: | Assertion failure in PyGILState_Release inside IA__g_closure_invoke running /usr/lib64/hamster-applet/hamster-applet | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Stoykov <M.Stoikov> | ||||||
| Component: | hamster-applet | Assignee: | Mads Villadsen <maxx> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | adalsaady, dmalcolm, fedora, ivazqueznet, james.antill, jonathansteffan, katzj, lmacken, marcus, maxx, me, ralston, sdodson | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:20dd25a3245817dfb4bff0cb23a3bbad6bb92a25 | ||||||||
| Fixed In Version: | hamster-applet-2.28.3-0.1.20100215git.fc12 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-01-21 16:17:11 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Michael Stoykov
2009-12-04 17:06:42 UTC
Created attachment 376129 [details]
File: backtrace
Thank you for reporting this bug. How reproducable is this problem? If you run the program from a terminal, is an error message printed? What version of hamster-applet do you have installed? Looking at the backtrace, it looks like an assertion failed inside frame 2 of the program's single thread inside PyGILState_Release. Reassigning component from "python" to "hamster-applet" # rpm -q hamster-applet.x86_64 hamster-applet-2.29.3-1.fc13.x86_64 $ python /usr/lib64/hamster-applet/hamster-applet --oaf-activate-iid=OAFIID:Hamster_Applet_Factory --oaf-ior-fd=48 /usr/lib64/hamster-applet/hamster-applet:147: Warning: g_set_prgname() called multiple times applet_factory) IOR:010000001e00000049444c3a426f6e6f626f2f47656e65726963466163746f72793a312e30000000030000000054424f580000000101020005000000554e4958000000000a0000006c6f63616c686f73740000002e0000002f746d702f6f726269742d6d73746f696b6f762f6c696e632d346165662d302d3439623439303334646261333500000000000000caaedfba58000000010102002e0000002f746d702f6f726269742d6d73746f696b6f762f6c696e632d346165662d302d343962343930333464626133350000001c00000000000000807a8c60574268a8dd29282828282828060000001073bb2b01000000480000000100000002000000050000001c00000000000000807a8c60574268a8dd29282828282828060000001073bb2b01000000140000000100000001000105000000000901010000000000 as far as I have restarted for the last two-three days - every time :) (around 5 times as I have tried the new .32 kernel (nfs broken)) *** Bug 548730 has been marked as a duplicate of this bug. *** *** Bug 549224 has been marked as a duplicate of this bug. *** This comment https://bugzilla.redhat.com/show_bug.cgi?id=549224#c2 : > The problem is hamster-applet-2.28.2-1.fc12.x86_64. > > If I revert to hamster-applet-2.28.1-1.fc12.x86_64, it works just fine. makes me think that this error: python: Python/pystate.c:626: PyGILState_Release: Assertion `oldstate == PyGILState_UNLOCKED' failed. (which characterizes this bug) is a threading issue specific to hamster-applet, and introduced in 2.28.2, rather than an issue with Python itself. (I'm not an expert an hamster-applet though) Hope this is helpful (In reply to comment #2) > Thank you for reporting this bug. > > How reproducable is this problem? If you run the program from a terminal, is > an error message printed? > > What version of hamster-applet do you have installed? $ rpm -qi hamster-applet Name : hamster-applet Relocations: (not relocatable) Version : 2.28.2 Vendor: Fedora Project Release : 1.fc12 Build Date: Wed 16 Dec 2009 07:58:10 PM BRST To reproduce you need to "Add to panel" (gnome-panel) a "Time Tracker" (Hamster) application. Best regards hamster-applet-2.29.5 works fine on F12. I rebuild from http://koji.fedoraproject.org/koji/buildinfo?buildID=150641 Regargs *** Bug 556393 has been marked as a duplicate of this bug. *** *** Bug 555172 has been marked as a duplicate of this bug. *** *** Bug 554306 has been marked as a duplicate of this bug. *** Great news that the bug appears to have been fixed in 2.29.5. Could anyone else try out the builds for F12 I made here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1930272 to see if the problem goes away? (In reply to comment #12) > Great news that the bug appears to have been fixed in 2.29.5. > > Could anyone else try out the builds for F12 I made here: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=1930272 > > to see if the problem goes away? Mads, Sorry about the wrong information. I think that I was updated but rpm failed to complete. It's not working yet. Best regards Opened a bug upstream: https://bugzilla.gnome.org/show_bug.cgi?id=607366 Created attachment 385259 [details] errors that occur when attempting to add Time Track (hamster-applet-2.29.5-1.fc12.x86_64) to panel Mads, I downloaded this package: http://koji.fedoraproject.org/koji/getfile?taskID=1930274&name=hamster-applet-2.29.5-1.fc12.x86_64.rpm Not only did it fail (see the attached errors), but it blew away all of the data in its SQLite database. :( (Fortunately, I keep redundant copies of the database, so I didn't lose anything I couldn't easily restore.) The database has been moved to $HOME/.local/share/hamster-applet so you shouldn't have lost anything. However the crasher bug may have been fixed in git upstream. I have built packages here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1934808 If you could please try them out and report back whether or not it fixes your problem. works for me :) fc13 btw :) Thank you all This package fixes it in F12 as well, though not sure we want to go with a 2.30 unstable package in F12 unless it's hard to backport the fix to 2.28. I am closing the bug then. It will be fixed in F13 with the next official release of hamster-applet (which should be Jan 27). For F12 I will most likely keep the package at 2.28.1 which doesn't have the problem. 2.28.2 was only ever in updates-testing, and contained only minor fixes anyway. *** Bug 552651 has been marked as a duplicate of this bug. *** *** Bug 558090 has been marked as a duplicate of this bug. *** Could someone try out this new build of hamster-applet 2.28 for Fedora 12? It should fix the problem, and if it does I will push it out as an update for Fedora 12. http://koji.fedoraproject.org/koji/taskinfo?taskID=1989203 Mads, That build works for me. Works for me. This is the first time I can run hamster since F12. hamster-applet-2.28.3-0.1.20100215git.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/hamster-applet-2.28.3-0.1.20100215git.fc12 hamster-applet-2.28.3-0.1.20100215git.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |