Bug 37558

Summary: updating to startup-notitification-0.12 makes claws-mail crash
Product: libstartup-notification Reporter: Ionut Biru <biru.ionut>
Component: generalAssignee: XDG Bugs <xdg-bugs>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Ionut Biru 2011-05-24 17:52:28 UTC
(gdb) run
Starting program: /usr/bin/claws-mail 
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0xb6cce468 in XGetXCBConnection (dpy=0x84550b0) at x11_xcb.c:9
9		return dpy->xcb->connection;
(gdb) bt full
#0  0xb6cce468 in XGetXCBConnection (dpy=0x84550b0) at x11_xcb.c:9
No locals.
#1  0xb77f4619 in sn_display_new (xdisplay=0x84550b0, push_trap_func=0x814fb24 <sn_error_trap_push>, pop_trap_func=0x814fb31 <sn_error_trap_pop>) at sn-common.c:77
        display = 0xb77f45fc
#2  0x0814fbd5 in startup_notification_complete (with_window=0) at main.c:335
        xdisplay = 0x84550b0
        hack = 0x0
#3  0x081521b7 in main (argc=1, argv=0xbffff854) at main.c:1620
        connection = 0x848348c
        error = 0x0
        userrc = 0x8489ac8 "/home/ioni/.claws-mail/imapcache"
        mainwin = 0x84a1d28
        folderview = 0x8554708
        icon = 0x848dcb0
        crash_file_present = 1
        num_folder_class = 1
        asked_for_migration = 0
        start_done = 1
        gui_manager = 0x8482050
        plug_list = 0x0
        never_ran = 0
        start = {tv_sec = 1306284707, tv_usec = 840551}
        end = {tv_sec = -1224952103, tv_usec = -1224881756}
        diff = {tv_sec = 7103860, tv_usec = -1224881756}
        timing_name = 0x8305ea6 "startup"
        __FUNCTION__ = "main"
Comment 1 Ionut Biru 2011-05-25 01:09:03 UTC
turns out is a bug in claws
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2414

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.