Bug 1065495

Created attachment 863380 [details]
File: backtrace

Created attachment 863381 [details]
File: cgroup

Created attachment 863383 [details]
File: core_backtrace

Created attachment 863385 [details]
File: dso_list

Created attachment 863386 [details]
File: environ

Created attachment 863388 [details]
File: exploitable

Created attachment 863389 [details]
File: limits

Created attachment 863392 [details]
File: maps

Created attachment 863394 [details]
File: open_fds

Created attachment 863396 [details]
File: proc_pid_status

Created attachment 863397 [details]
File: var_log_messages

Another user experienced a similar problem:

just wanted to fire up a new terminator instance (I have it bound to CTRL-ALT-t). Pressed that key combination, and bam!

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        cinnamon --replace
crash_function: gdk_window_has_impl
executable:     /usr/bin/cinnamon
kernel:         3.14.8-200.fc20.x86_64
package:        cinnamon-2.2.13-5.fc20
reason:         cinnamon killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

(In reply to Sankalp Khare from comment #12)
> Another user experienced a similar problem:
> 
> just wanted to fire up a new terminator instance (I have it bound to
> CTRL-ALT-t). Pressed that key combination, and bam!
> 

This isn't reproducible here.

Another user experienced a similar problem:

it's happened to me each time I restart computer and log to my account. login process takes ~ 20s to 50s. 

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        cinnamon --replace
crash_function: gdk_window_has_impl
executable:     /usr/bin/cinnamon
kernel:         3.14.9-200.fc20.x86_64
package:        cinnamon-2.2.13-5.fc20
reason:         cinnamon killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.

Getting the exact same bug in Fedora 24. Cinnamon-Version is 3.0.6.

Please reopen the bug. I'd upload my info but the reporting tool always says my stacktrace is unusable. If you need anything else, I'll be there.

(In reply to robi from comment #17)

> Please reopen the bug.

No!

There is no usable steps to reproduce the issue here!