Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #981266

Bug#932250: 932250

From Paul Kerry <p.kerry@sheffield.ac.uk>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#932250: 932250
Date 2019-10-28 15:20 +0100
Message-ID <yWe2d-2LM-5@gated-at.bofh.it> (permalink)
References <ykF3r-69x-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Hi

We are experiencing the same issues as the o/p, with random segfaults 
like this with the same "Code" values...

[252199.319638] xfdesktop[7276]: segfault at b ip 00007fea64a219ea sp 
00007ffcf0678c00 error 4 in libglib-2.0.so.0.5800.3[7fea649d1000+7e000]
[252199.319662] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 
8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 
00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89

when using xfce 4.12.5 on debian 10 buster amd64.

"xfce4-panel" and "gmain" are sometimes shown as well as/instead of 
"xfdesktop" in the dmesg output.


This is happening on standalone debian 10 machines and also on 10x/30x 
systems in a network of debian 10 machines. The same segfault is shown 
at random times, but mainly after login. Some machines are using nvidia 
proprietary graphics, but the majority are using intel modesetting from 
the kernel. We are using a 4.19.80 custom kernel built from vanilla 
sources. This also happens with a brand new user profile.

When searching online, I came across several references to the segfault 
but with older versions of libglib2.0-0 like this for instance...

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783865

and also these bugs look relevant...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933202
and...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934105

but I don't really want to build and upgrade to xfce 4.14 as mentioned 
in those bug reports.


I presume this would suggest this is a problem with the newer libglib2 
2.58.3-2+deb10u1 which is in debian 10?

I'm temporarily testing using libglib2.0-0:amd64 2.62.1-1 from the 
bullseye testing repo and haven't had a segfault as yet (fingers crossed).


Perhaps re-assign this bug to libglib2.0-0 ?


Cheers
Paul.
--

Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread


Thread

Bug#932250: 932250 Paul Kerry <p.kerry@sheffield.ac.uk> - 2019-10-28 15:20 +0100

csiph-web