Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

2019-10-25 Thread handsome_feng 
Tags:  moreinfo


Hi, Faris,


Can you show me the hardware environment? such as 'lspci', 'cat /proc/cpuinfo'. 
Also the OpenGL info: 'dpkg -l | grep mesa'. Since we can't reproduce here. 


Thanks!
handsome_feng

Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

2019-10-10 Thread Faris Xiao 
Thanks for you feedback!

在 2019/10/10 上午3:38, Andreas Beckmann 写道:

> testing and sid now have 1.1.11-1+b2 - does the crash still happen with
> these versions that were rebuilt against newer libraries? (Don't forget
> to upgrade the libukwm-1-0 package, too.)

After I upgrade to the newer versions in testing,the crash still happen.

[四 10月 10 15:40:06 2019] ukwm[4221]: segfault at 38 ip b5baf084 sp
bfaba2dc error 4 in libukwm-cogl-1.so[b5b71000+68000]
[四 10月 10 15:40:06 2019] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b
40 48 85 c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00
8b 44 24 04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c
c3 8d b4
[四 10月 10 15:42:15 2019] ukwm[4330]: segfault at 38 ip b5bc4084 sp
bfc38b6c error 4 in libukwm-cogl-1.so[b5b86000+68000]
[四 10月 10 15:42:15 2019] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b
40 48 85 c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00
8b 44 24 04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c
c3 8d b4


My packages version is following:

apt search ukwm
Sorting... Done
Full Text Search... Done
gir1.2-ukwm-1/testing,now 1.1.11-1+b2 i386 [installed]
  GObject introspection data for Ukwm

libukwm-1-0/testing,now 1.1.11-1+b2 i386 [installed]
  window manager library from the Ukwm window manager

libukwm-1-dev/testing 1.1.11-1+b2 i386
  Development files for the Ukwm window manager

ukwm/testing,now 1.1.11-1+b2 i386 [installed,automatic]
  lightweight GTK+ window manager

ukwm-common/stable,testing,now 1.1.11-1 all [installed]
  shared files for the Ukwm window manager

>
>

> Can you reproduce the segfault in a clean stable environment?

Yes.The segfault can reproduce in a clean stable environment.Infact,I
find this bug in stable at first.

[  286.489542] show_signal_msg: 2 callbacks suppressed
[  286.489552] ukwm[925]: segfault at 38 ip b5b73084 sp bfe25b8c error 4
in libukwm-cogl-1.so[b5b35000+68000]
[  286.489577] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b 40 48 85
c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 44 24
04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c c3 8d b4
[  412.498816] fcitx-dbus-watc[902]: segfault at 70725 ip b7e906b7 sp
bfdd11a0 error 4 in libdbus-1.so.3.19.11[b7e6c000+31000]
[  412.498842] Code: fd ff 83 c4 10 5b 5e 5f c3 8d b4 26 00 00 00 00 8d
76 00 53 e8 da d6 fd ff 81 c3 ca f1 02 00 83 ec 08 8b 44 24 10 85 c0 74
11 <0f> b6 40 20 83 e0 01 83 c4 08 5b c3 8d 74 26 00 90 8d 83 0b 2d fe
[  853.126075] e100 :02:08.0 enp2s8: NIC Link is Up 100 Mbps Full Duplex
[  853.126224] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s8: link becomes ready
[ 1412.900840] ukwm[2667]: segfault at 38 ip b5b5e9f4 sp bfafd97c error
4 in libukwm-cogl-1.so[b5b2+68000]
[ 1412.900869] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b 40 48 85
c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 44 24
04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c c3 8d b4

The following is my clean stable environment about ukwm packages version
info:

apt search ukwm
Sorting... Done
Full Text Search... Done
gir1.2-ukwm-1/stable 1.1.11-1 i386
  GObject introspection data for Ukwm

libukwm-1-0/stable,now 1.1.11-1 i386 [installed,automatic]
  window manager library from the Ukwm window manager

libukwm-1-dev/stable 1.1.11-1 i386
  Development files for the Ukwm window manager

ukwm/stable,now 1.1.11-1 i386 [installed]
  lightweight GTK+ window manager

ukwm-common/stable,now 1.1.11-1 all [installed,automatic]
  shared files for the Ukwm window manager

Is there possible  about hardware issue,or kernel driver bug,or gl bug?

>
>
> Andreas

-- 
肖盛文  Faris Xiao
Debian 中文套件一键安装 https://gitee.com/atzlinux/debian-cn




signature.asc
Description: OpenPGP digital signature

Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

2019-10-09 Thread Andreas Beckmann 
Control: tag -1 moreinfo unreproducible

On Fri, 27 Sep 2019 19:14:16 +0800 xiao shengwen  wrote:
> Package: ukwm
> Version: 1.1.11-1+b1

Note: This is not the version from stable (which has 1.1.11-1), but from
testing some time ago, now superseded by 1.1.11-1+b2

> [  306.124994] ukwm[1159]: segfault at 38 ip b5b57084 sp bf9b2d0c error 4 in 
> libukwm-cogl-1.so[b5b19000+68000]

> -- System Information:
> Debian Release: 10.1
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
> Architecture: i386 (i686)

You seem to running a mixture of stable and testing, which is not a
supported setup. I tried in a chroot, but could not reproduce any segfaults.

testing and sid now have 1.1.11-1+b2 - does the crash still happen with
these versions that were rebuilt against newer libraries? (Don't forget
to upgrade the libukwm-1-0 package, too.)

Can you reproduce the segfault in a clean stable environment?


Andreas

Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

2019-09-27 Thread xiao shengwen 
Package: ukwm
Version: 1.1.11-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

ukwm can't start,crash.The dmesg has the following error info:

[  306.124994] ukwm[1159]: segfault at 38 ip b5b57084 sp bf9b2d0c error 4 in 
libukwm-cogl-1.so[b5b19000+68000]
[  306.125015] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b 40 48 85 c0 74 
02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 44 24 04 <8b> 40 38 
c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c c3 8d b4

I run ukwm on console,It has display the following error:   

InitDBusCommunicationServer: Server started.
name_acquired_cb call, Acquired bus name: org.ukui.ukwm.UkwmPlugin.
Gtk-Message: 19:01:46.511: Failed to load module "topmenu-gtk-module"
Window manager warning: Failed to allocate shadow texture: Failed to create 
texture 2d due to size/format constraints
Window manager warning: Failed to allocate shadow texture: Failed to create 
texture 2d due to size/format constraints
段错误


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-6-686 (SMP w/1 CPU core)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ukwm depends on:
ii  gsettings-desktop-schemas  3.28.1-1
ii  libc6  2.28-10
ii  libglib2.0-0   2.58.3-2+deb10u1
ii  libukwm-1-01.1.11-1+b1
ii  libx11-6   2:1.6.7-1
ii  libxcomposite1 1:0.4.4-2
ii  libxrandr2 2:1.5.1-1
ii  ukui-settings-daemon   1.1.7-2
ii  ukwm-common1.1.11-1
ii  zenity 3.30.0-2

Versions of packages ukwm recommends:
ii  ukui-window-switch  1.1.2-1

Versions of packages ukwm suggests:
ii  ukui-control-center  1.1.6-2
ii  xdg-user-dirs0.17-2

-- no debconf information

The whole dmesg:

[0.00] Linux version 4.19.0-6-686 (debian-ker...@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
[0.00] Disabled fast string operations
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000d8000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x1f6d] usable
[0.00] BIOS-e820: [mem 0x1f6e-0x1f6ebfff] ACPI data
[0.00] BIOS-e820: [mem 0x1f6ec000-0x1f6f] ACPI NVS
[0.00] BIOS-e820: [mem 0x1f70-0x1fff] reserved
[0.00] BIOS-e820: [mem 0xfec1-0xfec1] reserved
[0.00] BIOS-e820: [mem 0xff80-0xffbf] reserved
[0.00] BIOS-e820: [mem 0xfc00-0x] reserved
[0.00] Notice: NX (Execute Disable) protection missing in CPU!
[0.00] SMBIOS 2.3 present.
[0.00] DMI: Sony Corporation VGN-B99C, BIOS R0042G9 01/19/2005
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 1587.905 MHz processor
[0.019677] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.019682] e820: remove [mem 0x000a-0x000f] usable
[0.019693] last_pfn = 0x1f6e0 max_arch_pfn = 0x10
[0.019702] MTRR default type: uncachable
[0.019704] MTRR fixed ranges enabled:
[0.019707]   0-9 write-back
[0.019709]   A-B uncachable
[0.019710]   C-C7FFF write-protect
[0.019712]   C8000-E uncachable
[0.019714]   F-F write-protect
[0.019716] MTRR variable ranges enabled:
[0.019718]   0 base 0 mask FE000 write-back
[0.019721]   1 base 01F70 mask 0 uncachable
[0.019723]   2 base 01F80 mask FFF80 uncachable
[0.019724]   3 disabled
[0.019725]   4 disabled
[0.019727]   5 disabled
[0.019728]   6 disabled
[0.019729]   7 disabled
[0.020403] x86/PAT: PAT not supported by CPU.
[0.020572] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC  
[0.045264] initial memory mapped: [mem 0x-0x0dff]
[0.045327] BRK [0x0daaf000, 0x0daa] PGTABLE
[0.045358] RAMDISK: [mem 0x1c7a5000-0x1e9cbfff]
[0.045369] ACPI: Early table checksum verification disabled
[0.046070] ACPI: RSDP 0x000F69B0 14 (v00 SONY  )
[0.046076] ACPI: RSDT 0x1F6E79DF 30 (v01 SONY   G9   
20050119 PTL  )
[0.046087] ACPI: FACP 0x1F6EBEC2 84 (v02 SONY   G9   
20050119 PTL  0050)
[0.046098] ACPI: DSDT 0x1F6E7E7B 004047 (v01 SONY   G9