[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#765673: marked as done (libglib2.0-0:amd64: segfaulting and ending X session (xfce4-session))

Your message dated Tue, 18 Aug 2020 13:32:22 +0200
with message-id <1e805c0916d8689bd03a7a90a4c674b0ffa09c98.camel@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#765673: libglib2.0-0:amd64: segfaulting and ending X session (xfce4-session)
has caused the Debian Bug report #765673,
regarding libglib2.0-0:amd64: segfaulting and ending X session (xfce4-session)
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.)


-- 
765673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765673
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libglib2.0-0
Version: 2.40.0-4
Severity: important

Dear Maintainer,

Occasionally XFCE4 suddenly logs me out. I /think/ it tends to happen as a new
application window is appearing. In looking for smoking guns, all I can see
is that syslog reports entries like,

Oct 16 08:41:38 ls28101 kernel: [  932.383539] xfce4-session[3632]: segfault at ffffffff00000000 ip 00007fc394174875 sp 00007fff12180ad0 error 5 in libglib-2.0.so.0.4000.0[7fc39410e000+109000]
Oct 16 16:41:13 ls28101 kernel: [29670.295541] xfce4-session[4591]: segfault at ffffffff00000000 ip 00007fa316bf8875 sp 00007fff7f1ba5d0 error 5 in libglib-2.0.so.0.4000.0[7fa316b92000+109000]
Oct 17 09:06:59 ls28101 kernel: [ 2960.407805] xfce4-session[3598]: segfault at ffffffff00000000 ip 00007f2af283b875 sp 00007fff928502f0 error 5 in libglib-2.0.so.0.4000.0[7f2af27d5000+109000]

at what looks like pretty much the right times / frequency.

Cheers,

Mark

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (600, 'stable'), (500, 'stable-updates'), (50, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libglib2.0-0:amd64 depends on:
ii  libc6              2.19-9
ii  libffi6            3.1-2
ii  libpcre3           1:8.35-3
ii  libselinux1        2.1.9-5
ii  multiarch-support  2.13-38+deb7u4
ii  zlib1g             1:1.2.7.dfsg-13

Versions of packages libglib2.0-0:amd64 recommends:
ii  libglib2.0-data   2.33.12+really2.32.4-5
ii  shared-mime-info  1.0-1+b1

libglib2.0-0:amd64 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 2014-10-22 at 12:32 +0100, Mark Carroll wrote:
> I seem to be no longer seeing this bug since downgrading libglib2.0-0
> from 2.40.0-4 to 2.33.12+really2.32.4-5 (also downgraded related
> packages like the glib-networking-* stuff). So, at least for now, I'm
> happy at least.

Hi, sorry for the lack of action in the past nearly 6 years (!). I'm closing
this bug following the above, if you still manage to reproduce feel free to
chime in.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl87vEcACgkQ3rYcyPpX
RFvr2wgA6r29SD49ScYFrNWtl7LQGzdrFA0/9ZTVG3l2NS6cmA+FOrQasT2ZMFZl
UjFX4pzu4d2op80tMp66itNHp/BK7r+J/8jL3SzHpkZxBaJygbZ7qdGMT/H/HhPA
ciCmkA9xE/ELnq2BRx1qmGp2bWUvPmP81R62ii8aavA4N2fjZUUF/PtVQ4UBkidK
88M6LG5ovQ426HC0KjgZt8LMy359dVbR1Ns/RJY0kboE9wiBSz30z5h6xbeGvK7G
qSXm5p5BwHtduKzZhMMdSbYpfC4z+IgkoMOHYiENAM+wDnlM3sLD2jDFRyapXfox
v2aIMIc0SjB1E9Km74nQW5urWCVQsA==
=wMkN
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: