Bug 963619 - [abrt] cinnamon-1.8.2-4.fc19: magazine_chain_pop_head: Process /usr/bin/cinnamon was killed by signal 11 (SIGSEGV)
Summary: [abrt] cinnamon-1.8.2-4.fc19: magazine_chain_pop_head: Process /usr/bin/cinna...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cinnamon
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:205d1396a2f3487421440603dde...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-16 09:13 UTC by D. Charles Pyle
Modified: 2015-02-17 15:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:15:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (53.21 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: cgroup (140 bytes, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: core_backtrace (680 bytes, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: dso_list (19.71 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: environ (1.81 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: limits (1.29 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: maps (92.45 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: open_fds (5.04 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: proc_pid_status (929 bytes, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: var_log_messages (1.86 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details
File: xsession_errors (1.49 KB, text/plain)
2013-05-16 09:13 UTC, D. Charles Pyle
no flags Details

Description D. Charles Pyle 2013-05-16 09:13:15 UTC
Description of problem:
I placed my mouse into the lower left corner to bring up the menu.  Following that a crash occurred.  I do not know the cause and I cannot get it to repeat at the moment.  I am submitting as much information as possible with this report, however.

Version-Release number of selected component:
cinnamon-1.8.2-4.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        cinnamon --replace
crash_function: magazine_chain_pop_head
executable:     /usr/bin/cinnamon
kernel:         3.9.2-301.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 magazine_chain_pop_head at gslice.c:532
 #1 magazine_chain_prepare_fields at gslice.c:613
 #2 magazine_cache_push_magazine at gslice.c:684
 #3 private_thread_memory_cleanup at gslice.c:770
 #4 __nptl_deallocate_tsd at pthread_create.c:156

Comment 1 D. Charles Pyle 2013-05-16 09:13:17 UTC
Created attachment 748684 [details]
File: backtrace

Comment 2 D. Charles Pyle 2013-05-16 09:13:22 UTC
Created attachment 748685 [details]
File: cgroup

Comment 3 D. Charles Pyle 2013-05-16 09:13:25 UTC
Created attachment 748686 [details]
File: core_backtrace

Comment 4 D. Charles Pyle 2013-05-16 09:13:27 UTC
Created attachment 748687 [details]
File: dso_list

Comment 5 D. Charles Pyle 2013-05-16 09:13:28 UTC
Created attachment 748688 [details]
File: environ

Comment 6 D. Charles Pyle 2013-05-16 09:13:30 UTC
Created attachment 748689 [details]
File: limits

Comment 7 D. Charles Pyle 2013-05-16 09:13:33 UTC
Created attachment 748690 [details]
File: maps

Comment 8 D. Charles Pyle 2013-05-16 09:13:35 UTC
Created attachment 748691 [details]
File: open_fds

Comment 9 D. Charles Pyle 2013-05-16 09:13:37 UTC
Created attachment 748692 [details]
File: proc_pid_status

Comment 10 D. Charles Pyle 2013-05-16 09:13:39 UTC
Created attachment 748693 [details]
File: var_log_messages

Comment 11 D. Charles Pyle 2013-05-16 09:13:42 UTC
Created attachment 748694 [details]
File: xsession_errors

Comment 12 D. Charles Pyle 2013-05-16 15:52:45 UTC
I wanted to add that there was something else that was going on at the time of the crash.  Yumex was running and doing updates, one of which was for gnome-shell.  I do not know whether or not that was responsible but thought I would mention it.  Another update for gnome-shell and for muffin were pushed today so will see if the crashes continue.

Comment 13 Fedora End Of Life 2015-01-09 18:08:01 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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.

Comment 14 Fedora End Of Life 2015-02-17 15:15:24 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


Note You need to log in before you can comment on or make changes to this bug.