systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file

#1

Hi,
i have some issues with xfwm4 ( The Xfce window manager that draws decorations (borders and title bar) around windows, controls the placement and behavior of windows, and governs how keyboard and mouse focus behaves in the desktop environment. )
lightdm and lightlocker.
Unlocking the desktop with light-locker is buggy. And sometimes lightdm + or xfwm4 have back traces.

Kernel: 5.0.9-2-MANJARO, and 5.0.10-2-MANJARO
inxi version: Xfce 4.13.3git-UNKNOWN
lightdm --version lightdm 1.28.0

xfwm4 --version
This is xfwm4 version 4.13.1git.UNKNOWN (revision UNKNOWN) for Xfce 4.13
	Released under the terms of the GNU General Public License.
	Compiled against GTK+-3.24.5, using GTK+-3.24.8.

	Build configuration and supported features:
	- Startup notification support:                 Yes
	- XSync support:                                Yes
	- Render support:                               Yes
	- Xrandr support:                               Yes
	- Xpresent support:                             Yes
	- Embedded compositor:                          Yes
	- Epoxy support:                                Yes
	- KDE systray proxy (deprecated):               No

It is reproducible:
A) Press the screen lock button from the manjaro start-menue and unlock it with your password

B)

  1. automated screen-lock locks the screen after x minutes (OK)
  2. screensaver comes after x minutes and screen is going to be black. (OK)
  3. Everytime i unlock my locked screen (after the screensaver kicked in) i got this: systemd-coredump (NOT OK)
journalctl -p 3 -xb
Apr 29 20:42:45  lightdm[2152]: gkr-pam: unable to locate daemon control file
Apr 29 20:42:49  systemd-coredump[2325]: Process 699 (xfwm4) of user 1000 dumped core.
                                                
                                                Stack trace of thread 699:
                                                #0  0x00007effe904a186 n/a (libglib-2.0.so.0)
                                                #1  0x00007effe9047f5c g_log_writer_default (libglib-2.0.so.0)
                                                #2  0x00007effe903ea49 g_log_structured_array (libglib-2.0.so.0)
                                                #3  0x00007effe9046f0d g_log_structured_standard (libglib-2.0.so.0)
                                                #4  0x00007effe93a354e n/a (libgdk-3.so.0)
                                                #5  0x00007effe93b06e5 n/a (libgdk-3.so.0)
                                                #6  0x00007effe8ccb52a _XError (libX11.so.6)
                                                #7  0x00007effe8cc83f8 n/a (libX11.so.6)
                                                #8  0x00007effe8cc84a5 n/a (libX11.so.6)
                                                #9  0x00007effe8cc9410 _XReply (libX11.so.6)
                                                #10 0x00007effe9b6c742 XIQueryDevice (libXi.so.6)
                                                #11 0x00007effe93a01bd n/a (libgdk-3.so.0)
                                                #12 0x00007effe93ab36d n/a (libgdk-3.so.0)
                                                #13 0x00007effe93aae36 n/a (libgdk-3.so.0)
                                                #14 0x00007effe9373ea2 gdk_display_get_event (libgdk-3.so.0)
                                                #15 0x00007effe93aaaa4 n/a (libgdk-3.so.0)
                                                #16 0x00007effe90507bf g_main_context_dispatch (libglib-2.0.so.0)
                                                #17 0x00007effe9052739 n/a (libglib-2.0.so.0)
                                                #18 0x00007effe90536d2 g_main_loop_run (libglib-2.0.so.0)
                                                #19 0x00007effe967be6f gtk_main (libgtk-3.so.0)
                                                #20 0x0000564453a91765 n/a (xfwm4)
                                                #21 0x00007effe877ace3 __libc_start_main (libc.so.6)
                                                #22 0x0000564453a9195e n/a (xfwm4)
                                                
                                                Stack trace of thread 710:
                                                #0  0x00007effe88470d1 __poll (libc.so.6)
                                                #1  0x00007effe9052690 n/a (libglib-2.0.so.0)
                                                #2  0x00007effe905277e g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007effe90527d2 n/a (libglib-2.0.so.0)
                                                #4  0x00007effe902dc21 n/a (libglib-2.0.so.0)
                                                #5  0x00007effe8923a92 start_thread (libpthread.so.0)
                                                #6  0x00007effe8851cd3 __clone (libc.so.6)
                                                
                                                Stack trace of thread 711:
                                                #0  0x00007effe88470d1 __poll (libc.so.6)
                                                #1  0x00007effe9052690 n/a (libglib-2.0.so.0)
                                                #2  0x00007effe90536d2 g_main_loop_run (libglib-2.0.so.0)
                                                #3  0x00007effe815e568 n/a (libgio-2.0.so.0)
                                                #4  0x00007effe902dc21 n/a (libglib-2.0.so.0)
                                                #5  0x00007effe8923a92 start_thread (libpthread.so.0)
                                                #6  0x00007effe8851cd3 __clone (libc.so.6)
                                                
                                                Stack trace of thread 847:
                                                #0  0x00007effe8929bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                #1  0x00007effdf9721e4 n/a (nouveau_dri.so)
                                                #2  0x00007effdf971f08 n/a (nouveau_dri.so)
                                                #3  0x00007effe8923a92 start_thread (libpthread.so.0)
                                                #4  0x00007effe8851cd3 __clone (libc.so.6)
-- Subject: Speicherabbild f├╝r Prozess 699 (@COREDUMP_COMM) generiert
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Prozess 699 (xfwm4) ist abgebrochen worden und
-- ein Speicherabbild wurde generiert.
-- 
-- ├ťblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.
Apr 29 21:08:37  lightdm[2482]: gkr-pam: unable to locate daemon control file
Apr 29 21:08:40  systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core.
                                                
                                                Stack trace of thread 2326:
                                                #0  0x00007f35c1525186 n/a (libglib-2.0.so.0)
                                                #1  0x00007f35c1522f5c g_log_writer_default (libglib-2.0.so.0)
                                                #2  0x00007f35c1519a49 g_log_structured_array (libglib-2.0.so.0)
                                                #3  0x00007f35c1521f0d g_log_structured_standard (libglib-2.0.so.0)
                                                #4  0x00007f35c187e54e n/a (libgdk-3.so.0)
                                                #5  0x00007f35c188b6e5 n/a (libgdk-3.so.0)
                                                #6  0x00007f35c11a652a _XError (libX11.so.6)
                                                #7  0x00007f35c11a33f8 n/a (libX11.so.6)
                                                #8  0x00007f35c11a34a5 n/a (libX11.so.6)
                                                #9  0x00007f35c11a4410 _XReply (libX11.so.6)
                                                #10 0x00007f35c2047742 XIQueryDevice (libXi.so.6)
                                                #11 0x00007f35c187b1bd n/a (libgdk-3.so.0)
                                                #12 0x00007f35c188636d n/a (libgdk-3.so.0)
                                                #13 0x00007f35c1885e36 n/a (libgdk-3.so.0)
                                                #14 0x00007f35c184eea2 gdk_display_get_event (libgdk-3.so.0)
                                                #15 0x00007f35c1885aa4 n/a (libgdk-3.so.0)
                                                #16 0x00007f35c152b7bf g_main_context_dispatch (libglib-2.0.so.0)
                                                #17 0x00007f35c152d739 n/a (libglib-2.0.so.0)
                                                #18 0x00007f35c152e6d2 g_main_loop_run (libglib-2.0.so.0)
                                                #19 0x00007f35c1b56e6f gtk_main (libgtk-3.so.0)
                                                #20 0x000055dba8e9a765 n/a (xfwm4)
                                                #21 0x00007f35c0c55ce3 __libc_start_main (libc.so.6)
                                                #22 0x000055dba8e9a95e n/a (xfwm4)
                                                
                                                Stack trace of thread 2328:
                                                #0  0x00007f35c0d220d1 __poll (libc.so.6)
                                                #1  0x00007f35c152d690 n/a (libglib-2.0.so.0)
                                                #2  0x00007f35c152e6d2 g_main_loop_run (libglib-2.0.so.0)
                                                #3  0x00007f35c0639568 n/a (libgio-2.0.so.0)
                                                #4  0x00007f35c1508c21 n/a (libglib-2.0.so.0)
                                                #5  0x00007f35c0dfea92 start_thread (libpthread.so.0)
                                                #6  0x00007f35c0d2ccd3 __clone (libc.so.6)
                                                
                                                Stack trace of thread 2339:
                                                #0  0x00007f35c0e04bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                #1  0x00007f35bc8411e4 n/a (nouveau_dri.so)
                                                #2  0x00007f35bc840f08 n/a (nouveau_dri.so)
                                                #3  0x00007f35c0dfea92 start_thread (libpthread.so.0)
                                                #4  0x00007f35c0d2ccd3 __clone (libc.so.6)
                                                
                                                Stack trace of thread 2327:
                                                #0  0x00007f35c0d220d1 __poll (libc.so.6)
                                                #1  0x00007f35c152d690 n/a (libglib-2.0.so.0)
                                                #2  0x00007f35c152d77e g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007f35c152d7d2 n/a (libglib-2.0.so.0)
                                                #4  0x00007f35c1508c21 n/a (libglib-2.0.so.0)
                                                #5  0x00007f35c0dfea92 start_thread (libpthread.so.0)
                                                #6  0x00007f35c0d2ccd3 __clone (libc.so.6)
-- Subject: Speicherabbild f├╝r Prozess 2326 (@COREDUMP_COMM) generiert
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Prozess 2326 (xfwm4) ist abgebrochen worden und
-- ein Speicherabbild wurde generiert.
-- 
-- ├ťblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.

inxi -Fxzc0

System:    Host:  Kernel: 5.0.9-2-MANJARO x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Xfce 4.13.3git-UNKNOWN 
           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: P5WD2-Premium v: Rev 1.xx serial: <filter> BIOS: American Megatrends v: 0422 
           date: 05/27/2005 
CPU:       Topology: Single Core model: Intel Pentium 4 bits: 64 type: MT arch: Netburst Smithfield rev: 3 L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 bogomips: 11244 
           Speed: 2810 MHz min/max: N/A Core speeds (MHz): 1: 2810 2: 2810 
Graphics:  Device-1: NVIDIA GT215 [GeForce GT 240] driver: nouveau v: kernel bus ID: 08:00.0 
           Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: modesetting resolution: 1920x1080~60Hz 
           OpenGL: renderer: NVA3 v: 3.3 Mesa 19.0.3 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Device-2: NVIDIA High Definition Audio driver: snd_hda_intel v: kernel bus ID: 08:00.1 
           Sound Server: ALSA v: k5.0.9-2-MANJARO 
Network:   Device-1: Marvell 88E8001 Gigabit Ethernet vendor: ASUSTeK driver: skge v: 1.14 port: 7800 bus ID: 01:05.0 
           IF: enp1s5 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82573V Gigabit Ethernet vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: 9800 bus ID: 03:00.0 
           IF: enp3s0 state: down mac: <filter> 
Drives:    Local Storage: total: 298.09 GiB used: 16.17 GiB (5.4%) 
           ID-1: /dev/sda vendor: Western Digital model: WD3200BPVT-24JJ5T0 size: 298.09 GiB 
Partition: ID-1: / size: 286.06 GiB used: 16.17 GiB (5.7%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 6.45 GiB used: 2.8 MiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Info:      Processes: 167 Uptime: 5h 16m Memory: 2.93 GiB used: 1.34 GiB (45.7%) Init: systemd Compilers: gcc: 8.3.0 
           Shell: bash v: 5.0.3 inxi: 3.0.33 

journalctl -p 3 | grep light

Apr 23 20:58:02 lightdm[1629]: gkr-pam: unable to locate daemon control file
Apr 23 21:42:30 lightdm[14577]: gkr-pam: unable to locate daemon control file
Apr 24 12:18:05 lightdm[16857]: gkr-pam: unable to locate daemon control file
Apr 24 12:18:44 lightdm[17024]: gkr-pam: unable to locate daemon control file
Apr 24 12:59:08 lightdm[1726]: gkr-pam: unable to locate daemon control file
Apr 24 13:00:54 systemd-coredump[2004]: Process 1924 (light-locker) of ... 1000 dumped core.
#4 0x000055c8d5e98cb4 n/a (light-locker)
#9 0x000055c8d5e9b4f3 gs_listener_new (light-locker)
#10 0x000055c8d5e97484 n/a (light-locker)
#15 0x000055c8d5e97b03 gs_monitor_new (light-locker)
#16 0x000055c8d5e96339 main (light-locker)
#18 0x000055c8d5e9648e _start (light-locker)
Apr 24 13:14:33 lightdm[1366]: gkr-pam: unable to locate daemon control file
Apr 24 22:36:29 lightdm[1428]: gkr-pam: unable to locate daemon control file
Apr 24 22:36:38 lightdm[1500]: gkr-pam: unable to locate daemon control file
Apr 24 22:38:11 systemd-coredump[1713]: Process 1632 (light-locker) of ... 1000 dumped core.
#4 0x0000562c8001acb4 n/a (light-locker)
#9 0x0000562c8001d4f3 gs_listener_new (light-locker)
#10 0x0000562c80019484 n/a (light-locker)
#15 0x0000562c80019b03 gs_monitor_new (light-locker)
#16 0x0000562c80018339 main (light-locker)
#18 0x0000562c8001848e _start (light-locker)
Apr 26 12:24:28 lightdm[1041]: gkr-pam: unable to locate daemon control file
Apr 26 12:46:57 lightdm[1541]: gkr-pam: unable to locate daemon control file
Apr 26 13:30:13 lightdm[1936]: gkr-pam: unable to locate daemon control file
Apr 27 11:52:15 lightdm[5396]: gkr-pam: unable to locate daemon control file
Apr 27 12:40:44 lightdm[5938]: gkr-pam: unable to locate daemon control file
Apr 27 13:22:02 lightdm[6350]: gkr-pam: unable to locate daemon control file
Apr 27 14:38:29 lightdm[1029]: gkr-pam: unable to locate daemon control file
Apr 27 14:51:35 lightdm[1147]: gkr-pam: unable to locate daemon control file
Apr 27 14:51:43 lightdm[1159]: gkr-pam: unable to locate daemon control file

see:
the-cavalry/light-locker#139

see
https://bugzilla.xfce.org/show_bug.cgi?id=15339

LF
(The reason i track this: a) curiosity b) System fails have often one than more errors. So one error is often harmless. But if 2 or 3 errors happen simultaneously, something else is crashing badly.)

[Unstable Update] 2019-04-30 - Systemd, Lightdm, Falkon
#2

A lot of people have been getting 'gkr-pam: unable to locate daemon control file' on login over the past month. But all other reports that I've seen have considered it harmless.

For your reference: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28
See also: https://bugs.archlinux.org/task/62140

1 Like
#3

Hi,
i was hunting desktop freezes on xfce+light-locker. For the xwm4 component, i worked out a solution with the xfce guys. But there were still other undeterministic freezes, right after unlocking password.
After a freeze, i got these error logs. The timestamps got me suspicious. Just after gkr-pam .... occured, the light-locker sw dumped...

Apr 24 12:59:08 lightdm[1726]: gkr-pam: unable to locate daemon control file
Apr 24 13:00:54 systemd-coredump[2004]: Process 1924 (light-locker) of ... 1000 dumped core.
#4 0x000055c8d5e98cb4 n/a (light-locker)

Time difference for the 2 coredumps:
grafik

At the moment i do not know if lightdm or light-locker is the main cause? or both?

#4
Steps to reproduce:
1. Let lightdm launch
2. Check systemd journal

Ahh thanx

hmmm.. Gnome maybe has no errors, but with xfce? Its another desktop. So an other environment, with other cases? I cannot see which desktop the arch post has?

#5

I get that error, too...

Desktop: i3 4.16.1 info: i3bar dm: LightDM 1.28.0 Distro: Manjaro Linux

Pure i3...not i3 over anything.

#6

Trying to find the correct project/ email list...

light-locker project has not responded yet

lightdm project has not responded yet

XFCE guys are saying: its a gtk Bug, i filed a new bug at their bugtracker
https://bugzilla.xfce.org/show_bug.cgi?id=15339

systemd-devel list are saying: xfwm4 is crashing and...

Something like this is generally a task for maintainers of the
distribution to figure out. Please either nag the maintainers or
switch to a different distribution.

At last this was the funniest reaction...:rofl:

#7

Aha, no xwfm4 crash with kernel 4.14.114 but still gkr-pam: unable to locate daemon control file:

uname -a
Linux  4.14.114-1-MANJARO #1 SMP PREEMPT Sat Apr 27 15:53:51 UTC 2019 x86_64 GNU/Linux



journalctl -p 3 -xb
-- Logs begin at Tue 2019-04-23 19:06:48 CEST, end at Tue 2019-04-30 10:22:53 CEST. --
Apr 30 10:21:23  kernel: ACPI Error: Method parse/execution failed \_PR.CPU1._PDC, AE_INVALID_TABLE_LENGTH (20170728/psparse-550)
Apr 30 10:21:23  kernel: ACPI Error: Method parse/execution failed \_PR.CPU2._PDC, AE_INVALID_TABLE_LENGTH (20170728/psparse-550)
Apr 30 10:21:29  kernel: nouveau 0000:08:00.0: bios: OOB 1 d7500086 d7500086
Apr 30 10:21:48  colord-sane[521]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Apr 30 10:22:52  lightdm[922]: gkr-pam: unable to locate daemon control file
#8

Also no Xfwm4 crash at the other computer at STABLE BRANCH with kernel 5.0.9
but two

 lightdm[]: gkr-pam: unable to locate daemon control file
 lightdm[]: gkr-pam: unable to locate daemon control file

messages after unlocking the screen.

But crashes at TESTING-BRANCH with 4.20

uname -a
Linux  4.20.17-1-MANJARO #1 SMP PREEMPT Tue Mar 19 18:07:36 UTC 2019 x86_64 GNU/Linux
xfwm4 dumped core
Apr 30 18:37:04  lightdm[1037]: gkr-pam: unable to locate daemon control file
Apr 30 18:37:08  systemd-coredump[1042]: Process 690 (xfwm4) of user 1000 dumped core.
                                                
                                                Stack trace of thread 690:
                                                #0  0x00007f4aaf99d186 n/a (libglib-2.0.so.0)
                                                #1  0x00007f4aaf99af5c g_log_writer_default (libglib-2.0.so.0)
                                                #2  0x00007f4aaf991a49 g_log_structured_array (libglib-2.0.so.0)
                                                #3  0x00007f4aaf999f0d g_log_structured_standard (libglib-2.0.so.0)
                                                #4  0x00007f4aafcf654e n/a (libgdk-3.so.0)
                                                #5  0x00007f4aafd036e5 n/a (libgdk-3.so.0)
                                                #6  0x00007f4aaf61e52a _XError (libX11.so.6)
                                                #7  0x00007f4aaf61b3f8 n/a (libX11.so.6)
                                                #8  0x00007f4aaf61b4a5 n/a (libX11.so.6)
                                                #9  0x00007f4aaf61c410 _XReply (libX11.so.6)
                                                #10 0x00007f4ab04bf742 XIQueryDevice (libXi.so.6)
                                                #11 0x00007f4aafcf31bd n/a (libgdk-3.so.0)
                                                #12 0x00007f4aafcfe36d n/a (libgdk-3.so.0)
                                                #13 0x00007f4aafcfde36 n/a (libgdk-3.so.0)
                                                #14 0x00007f4aafcc6ea2 gdk_display_get_event (libgdk-3.so.0)
                                                #15 0x00007f4aafcfdaa4 n/a (libgdk-3.so.0)
                                                #16 0x00007f4aaf9a37bf g_main_context_dispatch (libglib-2.0.so.0)
                                                #17 0x00007f4aaf9a5739 n/a (libglib-2.0.so.0)
                                                #18 0x00007f4aaf9a66d2 g_main_loop_run (libglib-2.0.so.0)
                                                #19 0x00007f4aaffcee6f gtk_main (libgtk-3.so.0)
                                                #20 0x000055ea1c733765 n/a (xfwm4)
                                                #21 0x00007f4aaf0cdce3 __libc_start_main (libc.so.6)
                                                #22 0x000055ea1c73395e n/a (xfwm4)
                                                
                                                Stack trace of thread 702:
                                                #0  0x00007f4aaf19a0d1 __poll (libc.so.6)
                                                #1  0x00007f4aaf9a5690 n/a (libglib-2.0.so.0)
                                                #2  0x00007f4aaf9a66d2 g_main_loop_run (libglib-2.0.so.0)
                                                #3  0x00007f4aaeab1568 n/a (libgio-2.0.so.0)
                                                #4  0x00007f4aaf980c21 n/a (libglib-2.0.so.0)
                                                #5  0x00007f4aaf276a92 start_thread (libpthread.so.0)
                                                #6  0x00007f4aaf1a4cd3 __clone (libc.so.6)
                                                
                                                Stack trace of thread 701:
                                                #0  0x00007f4aaf19a0d1 __poll (libc.so.6)
                                                #1  0x00007f4aaf9a5690 n/a (libglib-2.0.so.0)
                                                #2  0x00007f4aaf9a577e g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007f4aaf9a57d2 n/a (libglib-2.0.so.0)
                                                #4  0x00007f4aaf980c21 n/a (libglib-2.0.so.0)
                                                #5  0x00007f4aaf276a92 start_thread (libpthread.so.0)
                                                #6  0x00007f4aaf1a4cd3 __clone (libc.so.6)
                                                
                                                Stack trace of thread 851:
                                                #0  0x00007f4aaf27cbac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                #1  0x00007f4aa6d691e4 n/a (nouveau_dri.so)
                                                #2  0x00007f4aa6d68f08 n/a (nouveau_dri.so)
                                                #3  0x00007f4aaf276a92 start_thread (libpthread.so.0)
                                                #4  0x00007f4aaf1a4cd3 __clone (libc.so.6)
-- Subject: Speicherabbild f├╝r Prozess 690 (@COREDUMP_COMM) generiert
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Prozess 690 (xfwm4) ist abgebrochen worden und
-- ein Speicherabbild wurde generiert.
-- 
-- ├ťblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.

#9

you mean kernel 4.16.1 ?

#10

No; v5.0.10 and v5.1rc5/6/7

#11

Hmmm??? which version of xfwm4 do we have?
There are shown 3 different versions at the same system???

pacman -Si xfwm4

Repository      : extra
Name            : xfwm4
Version         : 4.12.5-1
Description     : Xfce window manager
Architecture    : x86_64
URL             : http://www.xfce.org/
Licenses        : GPL2
Groups          : xfce4
Provides        : None
Depends On      : libxfce4ui  libwnck  libdrm  hicolor-icon-theme
Optional Deps   : None
Conflicts With  : None
Replaces        : None
Download Size   : 491.47 KiB
Installed Size  : 2028.00 KiB
Packager        : Evangelos Foutras <evangelosNOSPAMfoutrelis.com>
Build Date      : Sun Jul 29 15:24:36 2018
Validated By    : MD5 Sum  SHA-256 Sum  Signature

xfwm4 --version
This is xfwm4 version 4.13.1git.UNKNOWN (revision UNKNOWN) for Xfce 4.13
Released under the terms of the GNU General Public License.
Compiled against GTK+-3.24.5, using GTK+-3.24.8.

Build configuration and supported features:
- Startup notification support:                 Yes
- XSync support:                                Yes
- Render support:                               Yes
- Xrandr support:                               Yes
- Xpresent support:                             Yes
- Embedded compositor:                          Yes
- Epoxy support:                                Yes
- KDE systray proxy (deprecated):               No

inxi -Fxzc0
System: Host: Kernel: 5.0.10-2-MANJARO x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Xfce 4.13.3git-UNKNOWN
Distro: Manjaro Linux

#12

Some fixes for xfwm4 is upstream in their git. I'll update our sources next week when I'm back from my vacation.

1 Like
#13

Thank you,

We have found a RenderBadPicture() error. so far..
https://bugzilla.xfce.org/show_bug.cgi?id=15339#c25

The Xfce guys need to know the exact version we use, to get a look at the source code.
https://bugzilla.xfce.org/show_bug.cgi?id=15339#c27

EDIT:
Is there a way to get DEBUGGING SYMBOLS ?

playing with

coredumpctl gdb processnumer
 coredumpctl gdb 776
           PID: 776 (xfwm4)
           UID: 1000 (...)
           GID: 1001 (...)
        Signal: 5 (TRAP)
     Timestamp: Fri 2019-05-03 10:55:06 CEST (1min 25s ago)
  Command Line: xfwm4
    Executable: /usr/bin/xfwm4
 Control Group: /....slice/...-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: ...-1000.slice
       Session: 1
     Owner UID: 1000 (...)
       Boot ID: db9a793faba443749d00588f4beae1fd
    Machine ID: 3ae900826b38438aaa6ea18a934f9130
      Hostname: ...
       Storage: /var/lib/systemd/coredump/core.xfwm4.1000.db9a793faba443749d00588f4beae1fd.776.1556873706000000.lz4
       Message: Process 776 (xfwm4) of ... 1000 dumped core.
                
                Stack trace of thread 776:
                #0  0x00007f0cbbd06186 n/a (libglib-2.0.so.0)
                #1  0x00007f0cbbd03f5c g_log_writer_default (libglib-2.0.so.0)
                #2  0x00007f0cbbcfaa49 g_log_structured_array (libglib-2.0.so.0)
                #3  0x00007f0cbbd02f0d g_log_structured_standard (libglib-2.0.so.0)
                #4  0x00007f0cbc05f54e n/a (libgdk-3.so.0)
                #5  0x00007f0cbc06c6e5 n/a (libgdk-3.so.0)
                #6  0x00007f0cbb98752a _XError (libX11.so.6)
                #7  0x00007f0cbb9843f8 n/a (libX11.so.6)
                #8  0x00007f0cbb9844a5 n/a (libX11.so.6)
                #9  0x00007f0cbb985410 _XReply (libX11.so.6)
                #10 0x00007f0cbc828742 XIQueryDevice (libXi.so.6)
                #11 0x00007f0cbc05c1bd n/a (libgdk-3.so.0)
                #12 0x00007f0cbc06736d n/a (libgdk-3.so.0)
                #13 0x00007f0cbc066e36 n/a (libgdk-3.so.0)
                #14 0x00007f0cbc02fea2 gdk_display_get_event (libgdk-3.so.0)
                #15 0x00007f0cbc066aa4 n/a (libgdk-3.so.0)
                #16 0x00007f0cbbd0c7bf g_main_context_dispatch (libglib-2.0.so.0)
                #17 0x00007f0cbbd0e739 n/a (libglib-2.0.so.0)
                #18 0x00007f0cbbd0f6d2 g_main_loop_run (libglib-2.0.so.0)
                #19 0x00007f0cbc337e6f gtk_main (libgtk-3.so.0)
                #20 0x000055bedce6e765 n/a (xfwm4)
                #21 0x00007f0cbb436ce3 __libc_start_main (libc.so.6)
                #22 0x000055bedce6e95e n/a (xfwm4)
                
                Stack trace of thread 789:
                #0  0x00007f0cbb5030d1 __poll (libc.so.6)
                #1  0x00007f0cbbd0e690 n/a (libglib-2.0.so.0)
                #2  0x00007f0cbbd0f6d2 g_main_loop_run (libglib-2.0.so.0)
                #3  0x00007f0cbae1a568 n/a (libgio-2.0.so.0)
                #4  0x00007f0cbbce9c21 n/a (libglib-2.0.so.0)
                #5  0x00007f0cbb5dfa92 start_thread (libpthread.so.0)
                #6  0x00007f0cbb50dcd3 __clone (libc.so.6)
                
                Stack trace of thread 788:
                #0  0x00007f0cbb5030d1 __poll (libc.so.6)
                #1  0x00007f0cbbd0e690 n/a (libglib-2.0.so.0)
                #2  0x00007f0cbbd0e77e g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f0cbbd0e7d2 n/a (libglib-2.0.so.0)
                #4  0x00007f0cbbce9c21 n/a (libglib-2.0.so.0)
                #5  0x00007f0cbb5dfa92 start_thread (libpthread.so.0)
                #6  0x00007f0cbb50dcd3 __clone (libc.so.6)
                
                Stack trace of thread 931:
                #0  0x00007f0cbb5e5bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x00007f0cb323a1e4 n/a (nouveau_dri.so)
                #2  0x00007f0cb3239f08 n/a (nouveau_dri.so)
                #3  0x00007f0cbb5dfa92 start_thread (libpthread.so.0)
                #4  0x00007f0cbb50dcd3 __clone (libc.so.6)

GNU gdb (GDB) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/xfwm4...(no debugging symbols found)...done.
[New LWP 776]
[New LWP 789]
[New LWP 788]
[New LWP 931]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `xfwm4'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0  0x00007f0cbbd06186 in ?? () from /usr/lib/libglib-2.0.so.0
[Current thread is 1 (Thread 0x7f0cb9d03980 (LWP 776))]
(gdb) 

is saying at the end:
Reading symbols from /usr/bin/xfwm4...(no debugging symbols found)...done.
So debug symbols are needed either in xfwm4 package or in a libglib-2.0* package?

XFCE people suggestion:

1. Make sure to install the debug symbols (no idea how to do that with Manjaro,
but it's a requirement)

2. Run xfwm4 in sync mode:
     
    export GDK_SYNCHRONIZE environment
    GDK_SYNCHRONIZE=1 xfwm4 --replace &

3. reproduce the issue

4. Check the backtrace (it must contain symbols otherwise it will be useless to
me)

LF

#14

@philm
XCE people are asking for the source code that was used to produce the binary package of xfwm4 as shipping with Manjaro.

Where can i find this?

see:
https://bugzilla.xfce.org/show_bug.cgi?id=15339#c29

#15

XFCE people provided me already with debug symbols. So i can debug on :grinning:

`--- Comment #33 from Olivier Fourdan <fourdanNOSPAMxfce.org> --- I've built xfwm4 for Manjaro from the latest code in git master, and did not strip the so we have the symbols available.

1. Try the latest build as-is:

Then try to reproduce the issue with light-locker just as usual, see if it
fails.

2. If it still fails the same, capture a backtrace of the failure:

  • $ GDK_SYNCHRONIZE=1 ./xfwm4 --replace &*

Then try to reproduce the issue with light-locker again, just as usual, and
once it failed, copy the stacktrace in here.
`

#16

There is a new build which seems to solve this bug.
https://bugzilla.xfce.org/show_bug.cgi?id=15339#c50
But i'll test it for some more days to be sure.

LF

#17

@jonathon
This one is solved :slight_smile:

This git commit can be taken into the next testing cycle. It solved a RenderBadPicture() from the xfwm4 window manager.
https://bugzilla.xfce.org/show_bug.cgi?id=15339#c64

LF

1 Like