| Summary: | [abrt] claws-mail-3.7.10-5.fc16: _g_dbus_worker_ref: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexander <dragonk> | ||||||||
| Component: | glib2 | Assignee: | Matthias Clasen <mclasen> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | cwickert, mclasen | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:72f556959658b426f10be1db4d744bef7e3f7d69 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-03-20 15:09:22 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Alexander
2011-11-15 08:33:11 UTC
Created attachment 533707 [details]
File: maps
Created attachment 533708 [details]
File: backtrace
> comment: Program just crashed while it was in system tray. Not so terse, please. Where it crashed can typically be seen in the backtrace, but whether it crashes reproducibly for you is not known. Do desktop notifications work for you? Has Claws Mail's "claws-mail-plugins-notification" package worked for you before? > DESKTOP_SESSION=xfce > > :XAUTHORITY=/var/run/kdm/.Xauthxg4Bdc > :_=/usr/bin/xfce4-session That you're running XFCE and kdm is also a detail you should have commented on. > #0 _g_dbus_worker_ref (worker=0x0) at gdbusprivate.c:438 > No locals. Without looking at the source, this is likely an unexpected NULL pointer crash in gdbus code. Mission objective is to find out the _why_. Sorry for the "brief" description :) I just installed F16 and I can't say I've seen notifications working. But indeed it seems to be a problem there, since my xchat crashed in the same place. [New LWP 1876] [New LWP 2060] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `xchat'. Program terminated with signal 11, Segmentation fault. #0 _g_dbus_worker_ref (worker=0x0) at gdbusprivate.c:438 438 gdbusprivate.c: No such file or directory. in gdbusprivate.c I'll get back to you when I have some time to do some debugging on this issue. Any hints where I should start? This is what I have installed related to "notification": % rpm -qa | grep noti notify-python-0.1.1-18.fc15.x86_64 claws-mail-plugins-notification-3.7.10-7.fc16.x86_64 notification-daemon-0.7.3-2.fc16.x86_64 libnotify-0.7.4-1.fc16.x86_64 startup-notification-0.12-1.fc16.x86_64 I don't know much about XFCE, but I know there is the "xfce4-notifyd" package. I've posted a message to Fedora's xfce mailing-list about this crash. Here's some feedback: http://lists.fedoraproject.org/pipermail/xfce/2011-November/000838.html Perhaps you could join? https://admin.fedoraproject.org/mailman/listinfo/xfce I'm currently trying notification-daemon and it *seemed* to be working, until I hit bug #739750 in combination with rhythmbox :) I'll continue testing to see if I get another crash in claws or xchat. Regardless of the discussion on the Xfce mailing list I think that the lack of a running notification daemon should never cause a crash in an application. gdbusproxy.c to gdbusprivate.c is within libgio -> reassigning to glib2 I don't seem to be experiencing any crashes anymore and xfce4-notifyd is running.. I don't think I've done anything special to fix it, I'm attaching my yum.log , maybe some of the updates fixed the problem. Created attachment 534157 [details]
yum.log
> xfce4-notifyd is running.. Because you've installed it _after_ the crash? Your package list from comment 4 did not contain it. Can you remove xfce4-notifyd or at least disable it? One way to disable it is to temporarily change Exec to "/bin/true" in /usr/share/dbus-1/services/org.xfce.Notifications.service * Unable to reproduce with XFCE. I ran "yum groupinstall XFCE" in a GNOME Shell session, logged out and back in into an XFCE session, verified that claws-mail-plugins-notification is loaded and enabled, verified that neither notification-daemon nor xfce4-notifyd was running (the latter isn't installed), and I didn't get any notifications in Claws Mail but not a crash either. * Familiarity with libgio may be sufficient to tell when the NULL ptr crash in the backtrace could happen. Else a test-case will be needed. * I'm out of there. Also removing the original assignees from the Cc list. I don't see anything particularly implicating gio here. worker being NULL indicates that the connection has been disposed, which probably means that the application unreffed the shared connection one too many times. Yes I probably installed xfce4-notifyd after reporting this.. I'm unable to reproduce the bug anymore either. I tried to disable xfce4-notifyd as specified in comment #13, but I'm not getting a crash anymore. I suppose it can be closed. A test-case would be good.
Claws Mail extra plugins notification_trayicon.c:
691
692 /* Show the popup */
693 if(!notify_notification_show(popup.notification, &(popup.error))) {
694 debug_print("Notification Plugin: Failed to send notification: %s\n",
695 popup.error->message);
696 g_clear_error(&(popup.error));
-> 697 g_object_unref(G_OBJECT(popup.notification));
698 popup.notification = NULL;
699 return FALSE;
700 }
701
That's where it crashed after "Failed to send notification" (couldn't reproduce that with the stock XFCE, however).
The only other place where it unrefs the Notification object, is the popup timeout callback, where it also does:
g_object_unref(G_OBJECT(popup.notification));
popup.notification = NULL;
Backtrace analysis found this bug to be similar to bug #786490, closing as duplicate. Bugs which were found to be similar to this bug: libnotify: bug #786490 xchat: bug #761151 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 786490 *** |