Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading

Jun Jiang
Package: xfdesktop4
Version: 4.12.4-2
Severity: important

Dear Maintainer,

* What led up to the situation?

It's been some time that I experienced coredumps of xfdesktop and xfce4-panel
when upgrading.

* What exactly did you do (or not do) that was effective (or ineffective)?

Using sid, I usually run apt update and upgrade daily to keep system up-to-
date. But I've noticed that when upgrading is running, seems like usually when
post-install phases, desktop wallpaper and xfce4-panel flash and disappear and
then appear again. I first thought they were restarting due to some upgrade
packages related to them. But later I found they were indeed xfdesktop and
xfce4-panel crashes and I saw coredump files saved, weird thing is that this
happens even when the packages upgrading are not related to the desktop itself.
For example, today I only got google-chrome-stable updated and both xfdesktop
and xfce4-panel crashed and coredumped.

Below is what I got from journalctl -xe when xfdesktop crashed during google-
chrome-stable upgrade.

Aug 07 09:53:11 MyDebian systemd-coredump[5406]: Process 5159 (xfdesktop) of
user 1000 dumped core.

                                                 Stack trace of thread 5159:
                                                 #0  0x00007fc31ce4975a
g_slice_alloc (libglib-2.0.so.0)
                                                 #1  0x00007fc31ce27316
g_list_prepend (libglib-2.0.so.0)
                                                 #2  0x00007fc31daf4b87 n/a
(libwnck-1.so.22)
                                                 #3  0x00007fc31daf5b44 n/a
(libwnck-1.so.22)
                                                 #4  0x00007fc31ce2b898
g_main_context_dispatch (libglib-2.0.so.0)
                                                 #5  0x00007fc31ce2bc88 n/a
(libglib-2.0.so.0)
                                                 #6  0x00007fc31ce2bf82
g_main_loop_run (libglib-2.0.so.0)
                                                 #7  0x00007fc31d75d8e7
gtk_main (libgtk-x11-2.0.so.0)
                                                 #8  0x000055a665e6fc6c n/a
(xfdesktop)
                                                 #9  0x000055a665e700a6 n/a
(xfdesktop)
                                                 #10 0x00007fc31ce28263 n/a
(libglib-2.0.so.0)
                                                 #11 0x00007fc31ce28c9e n/a
(libglib-2.0.so.0)
                                                 #12 0x00007fc31ce2b928
g_main_context_dispatch (libglib-2.0.so.0)
                                                 #13 0x00007fc31ce2bc88 n/a
(libglib-2.0.so.0)
                                                 #14 0x00007fc31ce2bd1c
g_main_context_iteration (libglib-2.0.so.0)
                                                 #15 0x00007fc31d0aca0d
g_application_run (libgio-2.0.so.0)
                                                 #16 0x000055a665e64fad main
(xfdesktop)
                                                 #17 0x00007fc31cc1f09b
__libc_start_main (libc.so.6)
                                                 #18 0x000055a665e64fea _start
(xfdesktop)

                                                 Stack trace of thread 5162:
                                                 #0  0x00007fc31cce9819 __poll
(libc.so.6)
                                                 #1  0x00007fc31ce2bbf6 n/a
(libglib-2.0.so.0)
                                                 #2  0x00007fc31ce2bd1c
g_main_context_iteration (libglib-2.0.so.0)
                                                 #3  0x00007fc31ce2bd61 n/a
(libglib-2.0.so.0)
                                                 #4  0x00007fc31ce5489d n/a
(libglib-2.0.so.0)
                                                 #5  0x00007fc31cdc3fa3
start_thread (libpthread.so.0)
                                                 #6  0x00007fc31ccf44cf __clone
(libc.so.6)

                                                 Stack trace of thread 5163:
                                                 #0  0x00007fc31cce9819 __poll
(libc.so.6)
                                                 #1  0x00007fc31ce2bbf6 n/a
(libglib-2.0.so.0)
                                                 #2  0x00007fc31ce2bf82
g_main_loop_run (libglib-2.0.so.0)
                                                 #3  0x00007fc31d0e6e46 n/a
(libgio-2.0.so.0)
                                                 #4  0x00007fc31ce5489d n/a
(libglib-2.0.so.0)
                                                 #5  0x00007fc31cdc3fa3
start_thread (libpthread.so.0)
                                                 #6  0x00007fc31ccf44cf __clone
(libc.so.6)
-- Subject: Process 5159 (xfdesktop) dumped core
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: man:core(5)
--
-- Process 5159 (xfdesktop) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Aug 07 09:53:11 MyDebian systemd[1]: [hidden email]:
Succeeded.
-- Subject: Unit succeeded


I don't know how to backtrace so this is pretty much I can get now.




-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfdesktop4 depends on:
ii  exo-utils            0.12.6-1
ii  libc6                2.28-10
ii  libcairo2            1.16.0-4
ii  libdbus-1-3          1.12.16-1
ii  libdbus-glib-1-2     0.110-4
ii  libexo-1-0           0.12.6-1
ii  libgarcon-1-0        0.6.3-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0         2.60.6-1
ii  libgtk2.0-0          2.24.32-3
ii  libnotify4           0.7.7-4
ii  libpango-1.0-0       1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libwnck22            2.30.7-6
ii  libx11-6             2:1.6.7-1
ii  libxfce4ui-1-0       4.12.1-3
ii  libxfce4util7        4.12.1-3
ii  libxfconf-0-2        4.12.1-1+b1
ii  xfdesktop4-data      4.12.4-2

Versions of packages xfdesktop4 recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-1
ii  dbus-x11 [dbus-session-bus]                   1.12.16-1
ii  librsvg2-common                               2.44.10-2.1
ii  tumbler                                       0.2.4-1
ii  xdg-user-dirs                                 0.17-2

Versions of packages xfdesktop4 suggests:
pn  menu  <none>

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading

Bernhard Übelacker-3
Hello Jiang Jun,
I just tried to reproduce the crash. Unfortunately it
did not happen in a minimal VM.

This package google-chrome-stable is from a third-party repository?

Therefore you might be able to have a look at the
output of "coredumpctl list".
There should be a line for the crash with pid 5159.
Then you could just use "coredumpctl gdb 5159" to
enter gdb with the recorded core and issue these commands
    backtrace
    quit

If you could install the following dbgsym packages before
like described in [1] could be very helpful.
   
    apt install xfdesktop4-dbgsym libglib2.0-0-dbgsym libgtk2.0-0-dbgsym libwnck22-dbgsym

With such packages installed the output in journalctl
should also offer some more information already.


If you have rebooted since then coredumpctl might not
show cores from the previous boots.
But you can have a look into /var/lib/systemd/coredump.

    unlz4 -k /var/lib/systemd/coredump/core.xfdesktop.0.00000000000000000000000000000000.5159.0000000000000000.lz4 /tmp/core.xfdesktop
    gdb -q /usr/bin/xfdesktop --core /tmp/core.xfdesktop
        backtrace
        quit

And then forward that output to this bug.
And maybe copy the core....lz4 to a safe place or it will
get deleted automatically soon, if the maintainer have
some more questions about it.



Nevertheless, I expect that the top frames
should look something like this:

    (gdb) bt
    #0  0x00007f053483a75a in magazine_chain_pop_head () at ../../../glib/gslice.c:538
    #1  thread_memory_magazine1_alloc () at ../../../glib/gslice.c:841
    #2  g_slice_alloc () at ../../../glib/gslice.c:1015
    #3  0x00007f0534818316 in g_list_prepend () at ../../../glib/glist.c:314
    #4  0x00007f05356e2b87 in update_client_list () at screen.c:1637
    #5  do_update_now () at screen.c:2332
    #6  0x00007f05356e3b44 in update_idle () at screen.c:2355
    #7  0x00007f053481c898 in g_main_dispatch () at ../../../glib/gmain.c:3189
    ...

These frames can be reached when changing display resolution.
Does the crash appear also if you manually the resolution?


Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Reply | Threaded
Open this post in threaded view
|

Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading

Jun Jiang
In reply to this post by Jun Jiang
Thank you Bernhard!

I was mentioning google-chrome-stable just to make it clear that I was not upgrading any xfce4 desktop related packages when the crash happened, not that it had anything to do with the crash.

As for for question at the end about changing display resolution, I don't follow you. Pardon me if I am misunderstanding, are you asking whether I changed screen resolution when it happened? If that's what you mean, then no, I haven't change my screen resolution since I don't even remember when. Also, before, during or after the crash, screen resolution remained fine. In fact, all opened windows were fine except wallpaper and xfce4-panel disappeared and appeared again as I mentioned.

Anyway, I managed to get the backtrace output:

#0  0x00007fc31ce4975a in magazine_chain_pop_head (magazine_chunks=0x55a6673027e0) at ../../../glib/gslice.c:538
#1  0x00007fc31ce4975a in thread_memory_magazine1_alloc (tmem=0x55a6673027c0, ix=1) at ../../../glib/gslice.c:841
#2  0x00007fc31ce4975a in g_slice_alloc (mem_size=mem_size@entry=24) at ../../../glib/gslice.c:1015
#3  0x00007fc31ce27316 in g_list_prepend (list=list@entry=0x55a66745dd50 = {...}, data=data@entry=0x55a66741fa20)
    at ../../../glib/glist.c:314
#4  0x00007fc31daf4b87 in update_client_list (screen=0x55a6673f78a0 [WnckScreen]) at screen.c:1637
#5  0x00007fc31daf4b87 in do_update_now (screen=0x55a6673f78a0 [WnckScreen]) at screen.c:2332
#6  0x00007fc31daf5b44 in update_idle (data=<optimized out>) at screen.c:2355
#7  0x00007fc31ce2b898 in g_main_dispatch (context=0x55a66731e690) at ../../../glib/gmain.c:3189
#8  0x00007fc31ce2b898 in g_main_context_dispatch (context=context@entry=0x55a66731e690) at ../../../glib/gmain.c:3854
#9  0x00007fc31ce2bc88 in g_main_context_iterate
    (context=0x55a66731e690, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at ../../../glib/gmain.c:3927
#10 0x00007fc31ce2bf82 in g_main_loop_run (loop=0x55a6673fb780) at ../../../glib/gmain.c:4123
#11 0x00007fc31d75d8e7 in IA__gtk_main () at ./gtk/gtkmain.c:1270
#12 0x000055a665e6fc6c in xfdesktop_application_start (app=0x55a66731a150 [XfdesktopApplication])
    at xfdesktop-application.c:768
#13 0x000055a665e700a6 in cb_wait_for_window_manager_destroyed (data=0x7fc30c007b60) at xfdesktop-application.c:630
#14 0x00007fc31ce28263 in g_source_callback_unref (cb_data=0x55a667366d50) at ../../../glib/gmain.c:1553
#15 0x00007fc31ce28263 in g_source_callback_unref (cb_data=0x55a667366d50) at ../../../glib/gmain.c:1546
#16 0x00007fc31ce28c9e in g_source_destroy_internal (source=0x55a66737b2c0, context=0x55a66731e690, have_lock=1)
    at ../../../glib/gmain.c:1238
#17 0x00007fc31ce2b928 in g_main_dispatch (context=0x55a66731e690) at ../../../glib/gmain.c:3213
#18 0x00007fc31ce2b928 in g_main_context_dispatch (context=context@entry=0x55a66731e690) at ../../../glib/gmain.c:3854
#19 0x00007fc31ce2bc88 in g_main_context_iterate
    (context=context@entry=0x55a66731e690, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at ../../../glib/gmain.c:3927
#20 0x00007fc31ce2bd1c in g_main_context_iteration (context=context@entry=0x55a66731e690, may_block=may_block@entry=1)
    at ../../../glib/gmain.c:3988
#21 0x00007fc31d0aca0d in g_application_run
    (application=0x55a66731a150 [XfdesktopApplication], argc=<optimized out>, argv=0x7fff34b18268)
    at ../../../gio/gapplication.c:2516
#22 0x000055a665e64fad in main (argc=5, argv=0x7fff34b18268) at main.c:86

Regards,
Jiang Jun
Reply | Threaded
Open this post in threaded view
|

Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading

Bernhard Übelacker-3
Hello Jun Jiang,
thanks for the additional information.

> As for for question at the end about changing display resolution, I don't
> follow you. Pardon me if I am misunderstanding, are you asking whether I
> changed screen resolution when it happened? If that's what you mean, then
> no, I haven't change my screen resolution since I don't even remember when.
> Also, before, during or after the crash, screen resolution remained fine.
> In fact, all opened windows were fine except wallpaper and xfce4-panel
> disappeared and appeared again as I mentioned.

As I could not get it crashing by just doing upgrades, I tried to
inspect a running process and got into a source file named "screen.c"
and functions related to screen resolution. Then I tried to change
resolution and the xfdesktop got into a similar backtrace still without
crashing. Therefore I asked if your processes would crash, if you
try changing the resolution.


> Anyway, I managed to get the backtrace output:
>
> #0  0x00007fc31ce4975a in magazine_chain_pop_head (magazine_chunks=0x55a6673027e0) at ../../../glib/gslice.c:538
> #1  0x00007fc31ce4975a in thread_memory_magazine1_alloc (tmem=0x55a6673027c0, ix=1) at ../../../glib/gslice.c:841
> #2  0x00007fc31ce4975a in g_slice_alloc (mem_size=mem_size@entry=24) at ../../../glib/gslice.c:1015
> #3  0x00007fc31ce27316 in g_list_prepend (list=list@entry=0x55a66745dd50 = {...}, data=data@entry=0x55a66741fa20) at ../../../glib/glist.c:314
> #4  0x00007fc31daf4b87 in update_client_list (screen=0x55a6673f78a0 [WnckScreen]) at screen.c:1637
> #5  0x00007fc31daf4b87 in do_update_now (screen=0x55a6673f78a0 [WnckScreen]) at screen.c:2332
> #6  0x00007fc31daf5b44 in update_idle (data=<optimized out>) at screen.c:2355
> #7  0x00007fc31ce2b898 in g_main_dispatch (context=0x55a66731e690) at ../../../glib/gmain.c:3189
> #8  0x00007fc31ce2b898 in g_main_context_dispatch (context=context@entry=0x55a66731e690) at ../../../glib/gmain.c:3854
> #9  0x00007fc31ce2bc88 in g_main_context_iterate (context=0x55a66731e690, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:3927
> #10 0x00007fc31ce2bf82 in g_main_loop_run (loop=0x55a6673fb780) at ../../../glib/gmain.c:4123
> #11 0x00007fc31d75d8e7 in IA__gtk_main () at ./gtk/gtkmain.c:1270
> #12 0x000055a665e6fc6c in xfdesktop_application_start (app=0x55a66731a150 [XfdesktopApplication]) at xfdesktop-application.c:768
> #13 0x000055a665e700a6 in cb_wait_for_window_manager_destroyed (data=0x7fc30c007b60) at xfdesktop-application.c:630
> #14 0x00007fc31ce28263 in g_source_callback_unref (cb_data=0x55a667366d50) at ../../../glib/gmain.c:1553
> #15 0x00007fc31ce28263 in g_source_callback_unref (cb_data=0x55a667366d50) at ../../../glib/gmain.c:1546
> #16 0x00007fc31ce28c9e in g_source_destroy_internal (source=0x55a66737b2c0, context=0x55a66731e690, have_lock=1) at ../../../glib/gmain.c:1238
> #17 0x00007fc31ce2b928 in g_main_dispatch (context=0x55a66731e690) at ../../../glib/gmain.c:3213
> #18 0x00007fc31ce2b928 in g_main_context_dispatch (context=context@entry=0x55a66731e690) at ../../../glib/gmain.c:3854
> #19 0x00007fc31ce2bc88 in g_main_context_iterate (context=context@entry=0x55a66731e690, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:3927
> #20 0x00007fc31ce2bd1c in g_main_context_iteration(context=context@entry=0x55a66731e690, may_block=may_block@entry=1) at ../../../glib/gmain.c:3988
> #21 0x00007fc31d0aca0d in g_application_run (application=0x55a66731a150 [XfdesktopApplication], argc=<optimized out>, argv=0x7fff34b18268) at ../../../gio/gapplication.c:2516
> #22 0x000055a665e64fad in main (argc=5, argv=0x7fff34b18268) at main.c:86


I found a similar report was reported by another user in
    https://bugs.debian.org/933202


Unfortunately I found not yet such an error in
the upstream bugtracker neither of xfce nor libwnck.

Kind regards,
Bernhard

Reply | Threaded
Open this post in threaded view
|

Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading

Jun Jiang
Thanks again Bernhard!

> As I could not get it crashing by just doing upgrades, I tried to
> inspect a running process and got into a source file named "screen.c"
> and functions related to screen resolution. Then I tried to change
> resolution and the xfdesktop got into a similar backtrace still without
> crashing. Therefore I asked if your processes would crash, if you
> try changing the resolution.
>

No, I don't think it had anything to do with changing resolution. I
tried changing my original resolution to several others, 1680*1050,
1600*1024 and 1400*1050, none of them caused a coredump.

>
> I found a similar report was reported by another user in
>     https://bugs.debian.org/933202
>

Seems like what I am experincing. I'll keep an eye on it.

Kind regards,
Jun

Reply | Threaded
Open this post in threaded view
|

Bug#934105: another backtrace

Jun Jiang
In reply to this post by Jun Jiang
So during a upgrade this morning this happened again:

$ coredumpctl list
TIME                            PID   UID   GID SIG COREFILE  EXE
Sun 2019-08-11 08:33:45 CST    1044  1000  1000  11 present   /usr/bin/xfdesktop
Sun 2019-08-11 08:33:45 CST   32695  1000  1000  11 present
/usr/bin/xfce4-appfinder
Sun 2019-08-11 08:33:45 CST    1040  1000  1000  11 present
/usr/bin/xfce4-panel
Sun 2019-08-11 08:34:49 CST    6557  1000  1000  11 present   /usr/bin/xfdesktop
Sun 2019-08-11 08:35:10 CST    6836  1000  1000  11 present   /usr/bin/xfdesktop

$ coredumpctl info 6557
           PID: 6557 (xfdesktop)
           UID: 1000 (adam)
           GID: 1000 (adam)
        Signal: 11 (SEGV)
     Timestamp: Sun 2019-08-11 08:34:48 CST (13s ago)
  Command Line: xfdesktop --display :0.0 --sm-client-id
22a396536-a119-4d09-8614-8656bfafc117
    Executable: /usr/bin/xfdesktop
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (adam)
       Boot ID: fe9a729066a445b8a9b18c1d08fc80f6
    Machine ID: 647a0bfe1e794d9db74e8b9202aab665
      Hostname: MyDebian
       Storage:
/var/lib/systemd/coredump/core.xfdesktop.1000.fe9a729066a445b8a9b18c1d08fc80f6.6557.156548368800
0000.l
       Message: Process 6557 (xfdesktop) of user 1000 dumped core.

                Stack trace of thread 6558:
                #0  0x00007f9cafce975a g_slice_alloc
(libglib-2.0.so.0)
                #1  0x00007f9cafcee183 g_string_sized_new
(libglib-2.0.so.0)
                #2  0x00007f9cafcb5de1 n/a (libglib-2.0.so.0)
                #3  0x00007f9cafcb72c5 g_build_filename
(libglib-2.0.so.0)
                #4  0x00007f9caff9e9f8 n/a (libgio-2.0.so.0)
                #5  0x00007f9caffa48fa n/a (libgio-2.0.so.0)
                #6  0x00007f9caffa5479
g_file_monitor_source_handle_event (libgio-2.0.so.0)
                #7  0x00007f9caffb0559 n/a (libgio-2.0.so.0)
                #8  0x00007f9caffafadc n/a (libgio-2.0.so.0)
                #9  0x00007f9caffafc96 n/a (libgio-2.0.so.0)
                #10 0x00007f9caffaefe9 n/a (libgio-2.0.so.0)
                #11 0x00007f9cafccb898 g_main_context_dispatch
(libglib-2.0.so.0)
                #12 0x00007f9cafccbc88 n/a (libglib-2.0.so.0)
                #13 0x00007f9cafccbd1c g_main_context_iteration
(libglib-2.0.so.0)
                #14 0x00007f9cafccbd61 n/a (libglib-2.0.so.0)
                #15 0x00007f9cafcf489d n/a (libglib-2.0.so.0)
                #16 0x00007f9cafc63fa3 start_thread (libpthread.so.0)
                #17 0x00007f9cafb944cf __clone (libc.so.6)

                Stack trace of thread 6557:
                #0  0x00007f9cafb89819 __GI___poll (libc.so.6)
                #1  0x00007f9cafccbbf6 n/a (libglib-2.0.so.0)
                #2  0x00007f9cafccbf82 g_main_loop_run
(libglib-2.0.so.0)
                #3  0x00007f9cb05fd8e7 gtk_main (libgtk-x11-2.0.so.0)
                #4  0x000055de8878bc6c n/a (xfdesktop)
                #5  0x000055de8878c0a6 n/a (xfdesktop)
                #6  0x00007f9cafcc8263 n/a (libglib-2.0.so.0)
                #7  0x00007f9cafcc8c9e n/a (libglib-2.0.so.0)
                #8  0x00007f9cafccb928 g_main_context_dispatch
(libglib-2.0.so.0)
                #9  0x00007f9cafccbc88 n/a (libglib-2.0.so.0)
                #10 0x00007f9cafccbd1c g_main_context_iteration
(libglib-2.0.so.0)
                #11 0x00007f9caff4ca0d g_application_run
(libgio-2.0.so.0)
                #12 0x000055de88780fad main (xfdesktop)
                #13 0x00007f9cafabf09b __libc_start_main (libc.so.6)
                #14 0x000055de88780fea _start (xfdesktop)

                Stack trace of thread 6559:
                #0  0x00007f9cafb89819 __GI___poll (libc.so.6)
                #1  0x00007f9cafccbbf6 n/a (libglib-2.0.so.0)
                #2  0x00007f9cafccbf82 g_main_loop_run
(libglib-2.0.so.0)
                #3  0x00007f9caff86e46 n/a (libgio-2.0.so.0)
                #4  0x00007f9cafcf489d n/a (libglib-2.0.so.0)
                #5  0x00007f9cafc63fa3 start_thread (libpthread.so.0)
                #6  0x00007f9cafb944cf __clone (libc.so.6)


I then installed libglib2.0-0-dbgsym libgtk2.0-0-dbgsym libc6-dbg
xfdesktop4-dbgsym and did a backtrace:

(gdb)
#0  0x00007f9cafce975a in magazine_chain_pop_head
(magazine_chunks=0x7f9ca8000bf0) at ../../../glib/gslice.c:538
#1  0x00007f9cafce975a in thread_memory_magazine1_alloc
(tmem=0x7f9ca8000bd0, ix=1) at ../../../glib/gslice.c:841
#2  0x00007f9cafce975a in g_slice_alloc (mem_size=mem_size@entry=24)
at ../../../glib/gslice.c:1015
#3  0x00007f9cafcee183 in g_string_sized_new
(dfl_size=dfl_size@entry=2) at ../../../glib/gstring.c:121
#4  0x00007f9cafcee6b4 in g_string_new (init=init@entry=0x0) at
../../../glib/gstring.c:148
#5  0x00007f9cafcb5de1 in g_build_path_va
(separator=separator@entry=0x7f9cafd1af0d "/",
first_element=first_element@entry=0x55de896553d0
"/usr/share/applications", args=args@entry=0x7f9cacf65720,
str_array=str_array@entry=0x0)
    at ../../../glib/gfileutils.c:1696
#6  0x00007f9cafcb72c5 in g_build_filename_va (str_array=0x0,
args=0x7f9cacf65720, first_argument=<optimized out>) at
../../../glib/gfileutils.c:2069
#7  0x00007f9cafcb72c5 in g_build_filename
(first_element=first_element@entry=0x55de896553d0
"/usr/share/applications") at ../../../glib/gfileutils.c:2069
#8  0x00007f9caff9e9f8 in g_local_file_new_from_dirname_and_basename
(dirname=0x55de896553d0 "/usr/share/applications",
basename=basename@entry=0x7f9ca8003b30
"libreoffice-xsltfilter.desktop.dpkg-tmp") at
../../../gio/glocalfile.c:242
#9  0x00007f9caffa48fa in g_file_monitor_source_queue_event
(fms=fms@entry=0x55de89653f10,
event_type=event_type@entry=G_FILE_MONITOR_EVENT_DELETED,
child=0x7f9ca8003b30 "libreoffice-xsltfilter.desktop.dpkg-tmp",
other=other@entry=0x0)
    at ../../../gio/glocalfilemonitor.c:233
#10 0x00007f9caffa5479 in g_file_monitor_source_send_event (other=0x0,
child=<optimized out>, event_type=G_FILE_MONITOR_EVENT_DELETED,
fms=0x55de89653f10) at ../../../gio/glocalfilemonitor.c:319
#11 0x00007f9caffa5479 in g_file_monitor_source_handle_event
(fms=0x55de89653f10,
event_type=event_type@entry=G_FILE_MONITOR_EVENT_DELETED,
child=<optimized out>, rename_to=<optimized out>,
    rename_to@entry=0x0, other=other@entry=0x0,
event_time=62010549077) at ../../../gio/glocalfilemonitor.c:439
#12 0x00007f9caffb0559 in ih_event_callback (event=0x7f9ca80038d0,
sub=0x55de895ec050, file_event=<optimized out>) at
../../../gio/inotify/inotify-helper.c:206
#13 0x00007f9caffafadc in ip_event_dispatch
(dir_list=dir_list@entry=0x55de896702c0 = {...}, file_list=0x0,
event=event@entry=0x7f9ca80038d0) at
../../../gio/inotify/inotify-path.c:492
#14 0x00007f9caffafc96 in ip_event_dispatch (event=0x7f9ca80038d0,
file_list=<optimized out>, dir_list=0x55de896702c0 = {...}) at
../../../gio/inotify/inotify-path.c:547
#15 0x00007f9caffafc96 in ip_event_callback (event=0x7f9ca80038d0) at
../../../gio/inotify/inotify-path.c:547
#16 0x00007f9caffafc96 in ip_event_callback
(event=event@entry=0x7f9ca80038d0) at
../../../gio/inotify/inotify-path.c:529
#17 0x00007f9caffaefe9 in ik_source_dispatch (source=0x55de895fded0,
func=0x7f9caffafbe0 <ip_event_callback>, user_data=<optimized out>) at
../../../gio/inotify/inotify-kernel.c:324
#18 0x00007f9cafccb898 in g_main_dispatch (context=0x55de89548380) at
../../../glib/gmain.c:3189
#19 0x00007f9cafccb898 in g_main_context_dispatch
(context=context@entry=0x55de89548380) at ../../../glib/gmain.c:3854
#20 0x00007f9cafccbc88 in g_main_context_iterate
(context=context@entry=0x55de89548380, block=block@entry=1,
dispatch=dispatch@entry=1, self=<optimized out>) at
../../../glib/gmain.c:3927
#21 0x00007f9cafccbd1c in g_main_context_iteration
(context=0x55de89548380, may_block=may_block@entry=1) at
../../../glib/gmain.c:3988
#22 0x00007f9cafccbd61 in glib_worker_main (data=<optimized out>) at
../../../glib/gmain.c:5868
#23 0x00007f9cafcf489d in g_thread_proxy (data=0x55de89513630) at
../../../glib/gthread.c:805
#24 0x00007f9cafc63fa3 in start_thread (arg=<optimized out>) at
pthread_create.c:486
#25 0x00007f9cafb944cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


I hope this is helpful.

Regard,
Jun

Reply | Threaded
Open this post in threaded view
|

Bug#934105: another backtrace

Yves-Alexis Perez-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, 2019-08-11 at 09:28 +0800, Jun Jiang wrote:
> I hope this is helpful.

Hi,

could it be that the crashes started occurring after a glib update?

Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1VWiMACgkQ3rYcyPpX
RFthtwf/bgI1PpRgepKq1+2jWcjo73bMg3uX41TNj0Vi2aZMN/G0fjYhnR1Vev7o
evAe89db1FqU8FqXJ1ddijJCYezTcjTYoePUwnbwJmyDm4OTZ1TpNStydupuDWMU
UMCpQCBS9cV7ESS0v41W+7GGE1wFswlP427clRIf6ik70C6vdZvdwciw2iy+j0Wn
cNkpScfiK1U9ulTOtwtZ0XWS+u1pBOA5cYR5w/2mAaJx1kDzMeAuobKtgaiJHIcR
7IgGpSwWWHvD+1C92fB06KOrEqpNQvrjd4m50NpAdWFVl8JLXr89sgi3Ug57eNuq
5bOYTVWWrzYUKWy6/tsU2CYfCjt+Jg==
=i6RY
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Bug#934105: another backtrace

Jun Jiang
>
> could it be that the crashes started occurring after a glib update?
>

Sorry for the late reply.
It's hard to say as it's been like this for some time as I've
mentioned in the original  report. But since xfce 4.14 is coming and
so I am thinking about testing after sid upgrade to newer version of
xfce4. And I've noticed indeed that after upgrade to xfce 4.14 and the
crash and core dumps never happened anymore. I am thinking it''s time
to close this bug report for now. I'll keep an eye on this and in case
it happens again, may god help me it won't, I'll file a new report.

Regards,
Jun