Bug#934105: marked as done (xfdesktop4: xfdesktop crashes and coredump when upgrading)
Your message dated Sun, 25 Aug 2019 18:27:18 +0200
with message-id <449853bef14b08e33cdbeba8de9f33b713648e39.camel@debian.org>
and subject line Re: Bug#934105: another backtrace
has caused the Debian Bug report #934105,
regarding xfdesktop4: xfdesktop crashes and coredump when upgrading
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
934105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934105
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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]: systemd-coredump@9-5351-0.service:
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
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sat, 2019-08-24 at 16:11 +0800, Jun Jiang wrote:
> > 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.
>
Ok, closing. Feel free to reopen or open a new bug if needed.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1ituYACgkQ3rYcyPpX
RFuHfQf/WB6/ZZz0uNqOUXE2mM60x5ZJNguxFpWvTvRdHwCYr9WgixGcsW6I/Gn7
T0y3mQeNgywM1aU1h2y38eqAMCSot6b8ocXCgv/KS9TMCmPkWTv+E80wg2G4aCxR
hfhapi0dFzR36Au7bfz2uwBqhFLzVzkQFTgos18Te6cw0XXjzpL+f0icR2D9gghY
EKtY/7WWXtz/UPRO6UU8oHmc4FZoH/9LhxH2eEloyYHbW+E24DvdtbeByvyvgSG9
FkRSSvg/hgWWno0rE6Z6weaeYxGGOrG//iBaqqBS0t0D/kp/lvSfszMfvsvbbtHl
cNRdqVTEFr9piUnfO4x4mCI1mt/zlA==
=7q9a
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: