Your message dated Wed, 11 Apr 2018 17:11:03 +0100
with message-id <20180411161103.ga31...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#712245: segfaults seen when /dev/rfkill cannot be 
opened
has caused the Debian Bug report #712245,
regarding gnome-bluetooth: various segfaults seen when /dev/rfkill cannot be 
opened
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 ow...@bugs.debian.org
immediately.)


-- 
712245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.33.12

Many segfaults are recorded in /var/syslog.

Error messages are as follows.

Jun 14 21:17:35 debian kernel: [518349.716234] bluetooth-apple[4946]: segfault 
at fbe5c ip b6d7cb88 sp bfef6b50 error 4 in
libglib-2.0.so.0.3200.4[b6cf6000+fb000]
Jun 14 21:18:18 debian kernel: [518393.324422] gnome-control-c[5021]: segfault 
at fbe5c ip b6e3ab88 sp bfd69a50 error 4 in
libglib-2.0.so.0.3200.4[b6db4000+fb000]
Jun 14 21:21:01 debian kernel: [518555.568306] bluetooth-wizar[5039]: segfault 
at fbe5c ip b6dcfb88 sp bfef7450 error 4 in
libglib-2.0.so.0.3200.4[b6d49000+fb000]


Most of them seems related to gnome-bluetooth.

The segfault by "gnome-control-c" occurred when
 I clicked bluetooth icon in Gnome Control Center.

It seems that this problem occurs only in vncserver
environment of my OLD server.

My CPU infomation is as follows.

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 11
model name      : Intel(R) Pentium(R) III CPU family      1400MHz
stepping        : 1
microcode       : 0x1c
cpu MHz         : 1396.435
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pse36 mmx fxsr sse
bogomips        : 2792.87
clflush size    : 32
cache_alignment : 32
address sizes   : 36 bits physical, 32 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 11
model name      : Intel(R) Pentium(R) III CPU family      1400MHz
stepping        : 1
microcode       : 0x1c
cpu MHz         : 1396.435
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pse36 mmx fxsr sse
bogomips        : 2793.08
clflush size    : 32
cache_alignment : 32
address sizes   : 36 bits physical, 32 bits virtual
power management:

PCI information:
00:00.0 Host bridge: Broadcom CNB20HE Host Bridge (rev 23)
00:00.1 Host bridge: Broadcom CNB20HE Host Bridge (rev 01)
00:00.2 Host bridge: Broadcom CNB20HE Host Bridge (rev 01)
00:00.3 Host bridge: Broadcom CNB20HE Host Bridge (rev 01)
00:0e.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Rage XL 
(rev 27)
00:0f.0 ISA bridge: Broadcom CSB5 South Bridge (rev 92)
00:0f.1 IDE interface: Broadcom CSB5 IDE Controller (rev 92)
00:0f.2 USB controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05)
00:0f.3 Host bridge: Broadcom CSB5 LPC bridge
02:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit Ethernet 
Controller (Copper) (rev 02)
02:04.0 SCSI storage controller: Marvell Technology Group Ltd. MV88SX6081 
8-port SATA II PCI-X Controller (rev 09)


In other machines, this problem does not occur even
with vncserver.

Thank you.

Takashi Yano

--- End Message ---
--- Begin Message ---
Version: 3.14.0-2

On Wed, 11 Apr 2018 at 21:35:53 +0900, Takashi Yano wrote:
> On Wed, 4 Apr 2018 10:30:37 +0100
> Simon McVittie <s...@debian.org> wrote:
> > Does this still happen in a more current version of Debian?
> 
> I have confirmed that this does not happen in Jessie.

Thanks, closing the bug.

> However, this still happens in most recent Wheezy.

This is very unlikely to be fixed in wheezy at this point.

    smcv

--- End Message ---

Reply via email to