Bug 979682

Created attachment 766836 [details]
File: backtrace

Created attachment 766837 [details]
File: cgroup

Created attachment 766838 [details]
File: core_backtrace

Created attachment 766839 [details]
File: dso_list

Created attachment 766840 [details]
File: environ

Created attachment 766841 [details]
File: limits

Created attachment 766842 [details]
File: maps

Created attachment 766843 [details]
File: open_fds

Created attachment 766844 [details]
File: proc_pid_status

Created attachment 766845 [details]
File: var_log_messages

What were you doing when this happened?

Can you duplicate it?

Happens to me during boot.

Happened to me in F19 during boot.

It does not happen during resume from suspend but 
happens after login after powercylce boot when XFCE comes up for the user.

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.

There is also crash on the Fedora 20

Top frames from backtrace:
#0  0x0000003b71a504e9 in g_logv (log_domain=0x306607efa6 "Gdk", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7fff3ac279a0) at gmessages.c:989
        domain = 0x0
        data = 0x0
        depth = 1
        log_func = 0x3b71a4fc80 <g_log_default_handler>
        domain_fatal_mask = <optimized out>
        masquerade_fatal = 0
        test_level = <optimized out>
        was_fatal = <optimized out>
        was_recursion = <optimized out>
        msg = 0x20fa140 "The program 'wrapper' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n  (Details: serial 269 error_code 3 request_"...
        msg_alloc = 0x20fa140 "The program 'wrapper' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n  (Details: serial 269 error_code 3 request_"...
        i = 2
#1  0x0000003b71a5063f in g_log (log_domain=log_domain@entry=0x306607efa6 "Gdk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x306609daf4 "%s") at gmessages.c:1025
        args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area = 0x7fff3ac27a80, reg_save_area = 0x7fff3ac279c0}}
#2  0x000000306606866b in gdk_x_error (display=<optimized out>, error=<optimized out>) at gdkmain-x11.c:486
        buf = "BadWindow (invalid Window parameter)", '\000' <repeats 27 times>
        msg = <optimized out>

I can provide full abrt report if you want.

I forgot to mention version of the package:
bash$ rpm -q xfce4-panel
xfce4-panel-4.10.1-3.fc20.x86_64

Lukas: If you can attach the full backtrace that would help... the top few there isn't enough to really see where it's dying. ;( 

Thanks.

Created attachment 854240 [details]
Full abrt report for comment 979682#c16

Thank you very much for fast response.

In my experience, I know it is better to analyse coredump than backtrace.
I hope it helps you to solve problem.

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.