abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: osmo comment: I began using Osmo a few days ago. This crashing has been a big problem, and this is the third time today it has happened. component: osmo crash_function: raise executable: /usr/bin/osmo global_uuid: 79415447d1b0ab9e8f35a54fd7095c88fa991737 kernel: 2.6.33.5-124.fc13.i686 package: osmo-0.2.10-1.fc13 rating: 4 reason: Process /usr/bin/osmo was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Launched Osmo and postponed 3 tasks via the buttons on the notification popups. 2. Two of the task reminders appeared several minutes later. 3. When I clicked "Remind me later" on one of the tasks, Osmo crashed.
Created attachment 427027 [details] File: backtrace
Sorry for the late reply. Is the sox package installed?
(In reply to comment #2) > Sorry for the late reply. Is the sox package installed? $ rpm -qa | grep sox sox-14.3.0-1.fc13.i686 It is now. Not sure if what was at the time of the bug report, though. Is there any way I can check that? I don't think the "Software log viewer" records things that were installed from the command line using yum.
rpm -qa --last | grep sox
Neat, thanks! $ rpm -qa --last | grep sox sox-14.3.0-1.fc13 Sat 29 May 2010 03:38:05 PM MDT
OK, this means it was already installed. Some more questions: 1. Does osmo still crash and can you reproduce the crash reliably? 2. What version of gtk2 are/were you using?
1. I stopped using osmo shortly after I began experiencing these crashes. However, I reinstalled it and started it up again for the purpose of this bug report. Upon launching osmo, several reminders for my old tasks popped up. I clicked "Remind me later" to make each of the notifications go away. Several minutes later the reminders appeared again. I clicked "Remind me later" on one of those, and osmo crashed. So, the steps outlined in my original bug report do indeed reproduce the crash. I suppose one question is: Is there something about the way I created or managed these particular tasks that is causing the crash? I created a new dummy task to see if the same "Remind me later" procedure would trigger the crash. Osmo did not crash in this case. 2. $ rpm -qa --last | grep gtk2 libcanberra-gtk2-0.24-1.fc13 Fri 28 May 2010 11:56:18 PM MDT gtk2-immodule-xim-2.20.1-1.fc13 Tue 18 May 2010 05:25:06 PM MDT gtk2-engines-2.20.1-1.fc13 Tue 18 May 2010 05:24:40 PM MDT pygtk2-libglade-2.17.0-3.fc13 Tue 18 May 2010 05:24:04 PM MDT pygtk2-2.17.0-3.fc13 Tue 18 May 2010 05:24:04 PM MDT gtk2-2.20.1-1.fc13 Tue 18 May 2010 05:24:03 PM MDT
Thanks, now I have all necessary info for forwarding the bug to the upstream developers. You can see the bug report at https://sourceforge.net/tracker/?func=detail&aid=3030691&group_id=206587&atid=998196 Feel free to add comments or subscribe to the upstream bug report in order to follow any changes. Even if you don't, will be notified once this bug is resolved in Fedora. If I need more information, I will get back to you. I'm now closing the bug UPSTREAM because this is where further investigation should take place. Thanks for reporting this bug.