GNOME Bugzilla – Bug 653595
"Segmentation fault" when using messages through libnotify
Last modified: 2020-11-26 15:30:58 UTC
Please see these(http://developer.pidgin.im/ticket/14330) bug report and debug logs for more information. I can provide other info if requested.
Anyone, anything?
Please provide a simple test case.
It's pretty random.. you receive a message, and sometimes, just sometimes, you get the 'segmentation fault'. Hope to investigate further to give you a proper log. Regards.
Here I have a log from /var/log/syslog. Just opened some conversations, close other 2. Pidgin: (10:46:30) prefs: /pidgin/conversations/im/x changed, scheduling save. (10:46:30) prefs: /pidgin/conversations/im/y changed, scheduling save. (10:46:30) accels: accel changed, scheduling save. (10:46:30) accels: accel changed, scheduling save. (10:46:30) accels: accel changed, scheduling save. (10:46:30) accels: accel changed, scheduling save. (10:46:30) accels: accel changed, scheduling save. Segmentation fault syslog: Nov 29 10:46:32 calopez-dell kernel: [ 9919.199131] pidgin[13191]: segfault at 18 ip 00007f5a6edc6e05 sp 00007fff80393a40 error 4 in pidgin[7f5a6ed63000+f3000]
This doesn't happen in gnome3, just when using unity.
Mass-fixing incorrect Default Assignee and QA contact scheme for libnotify so interested people can follow its development. (See 606365#c1 for ref.)
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all older bug reports and feature requests in GNOME Bugzilla which have not seen updates for a while. If you still use libnotify and if you still see this bug / want this feature in a recent and currently supported version, then please feel free to report it at https://gitlab.gnome.org/GNOME/libnotify/-/issues/ by following the guidelines at https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines Thank you for creating this report and we are sorry it could not be implemented so far (volunteer workforce and time is limited).