Version-Release number of selected component: bluefish-2.2.3-2.fc18 Additional info: backtrace_rating: 4 cmdline: bluefish crash_function: magazine_chain_pop_head executable: /usr/bin/bluefish kernel: 3.7.9-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:532 #1 thread_memory_magazine1_alloc at gslice.c:835 #2 g_slice_alloc at gslice.c:994 #3 g_slice_alloc0 at gslice.c:1029 #4 find_source_list_for_priority at gmain.c:934 #5 source_add_to_context at gmain.c:970 #6 g_source_attach_unlocked at gmain.c:1041 #7 g_source_attach at gmain.c:1085 #8 g_idle_add_full at gmain.c:4869 #9 gdk_threads_add_idle_full at gdk.c:877
Created attachment 702814 [details] File: backtrace
Created attachment 702815 [details] File: cgroup
Created attachment 702816 [details] File: core_backtrace
Created attachment 702817 [details] File: dso_list
Created attachment 702818 [details] File: environ
Created attachment 702819 [details] File: limits
Created attachment 702820 [details] File: maps
Created attachment 702821 [details] File: open_fds
Created attachment 702822 [details] File: proc_pid_status
Created attachment 702823 [details] File: var_log_messages
The bluefish proces had several tabs open and had been ideling for about an hour while I was "Takng a break" I was watching some videos on the youtube. After I had finished I reactivated the bluefish window and it crashed. By reactivating it I mean I just clicked on the window (it was never minimized). I do have custom appearance / theme settings for bluefish, gtk, and kde itself. My entire system has it's appearance customized. Bluefish along with kde has custom program settings. Nothing I can think of that may have caused this but I am allways up for questions to help resolve this issue. This is not the first time bluefish has crashed on me but it is the first time it has done this while reactivating the window. backtrace_rating: 4 cmdline: /usr/bin/bluefish '/home/Projects/Bash Works/Build/etc/bash-works/bash-works-info.conf' '/home/Projects/Bash Works/Build/etc/bash-works/bash-works.conf' crash_function: magazine_chain_pop_head executable: /usr/bin/bluefish kernel: 3.8.8-202.fc18.x86_64 package: bluefish-2.2.3-2.fc18 reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1
Replacing text backtrace_rating: 4 cmdline: /usr/bin/bluefish crash_function: magazine_chain_pop_head executable: /usr/bin/bluefish kernel: 3.8.8-202.fc18.x86_64 package: bluefish-2.2.3-2.fc18 reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.