LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-22-2018, 12:42 PM   #1
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 727
Blog Entries: 3

Rep: Reputation: 226Reputation: 226Reputation: 226
trap / segfaults since updating -current


When running X.. (i use awesome wm) it all loads up fine. However, as soon i run certain application, i believe using gtk/glib they randomly crash with "trap" or "segfault" messages.

I haven't been able to do much on my system the past 3 hours... i have no idea what is happening.

I have tried different Nvidia driver versions, i have tried to boot from the huge kernel, also tried rebuilding initrd etc.

Chromium seems to work without crashing. Firefox randomly gives out within a few seconds and multiple segfault messages.

Any ideas?

If i run thunar... and do nothign other than press "ctrl", this happens:
Code:
[  100.030741] traps: thunar[6222] trap int3 ip:7f82cf045535 sp:7fff3e2f38c0 error:0 in libglib-2.0.so.0.5800.2[7f82cf00e000+7b000]
firefox randomly closes and leaves this behind;
Code:
[  396.757846] traps: firefox[6440] trap int3 ip:7f8ae5815535 sp:7fff979fcbe0 error:0 in libglib-2.0.so.0.5800.2[7f8ae57de000+7b000]
[  396.785455] Chrome_~dThread[6729]: segfault at 0 ip 00007f17d9b5b4d5 sp 00007f17d80eeb00 error 6 in libxul.so[7f17d9700000+528e000]
[  396.785473] Code: 04 25 00 00 00 00 3a 02 00 00 e8 86 4f ba ff 48 89 df e8 a2 ca ff ff eb 86 48 8b 05 0d f4 27 05 48 8d 0d 86 0d 24 03 48 89 08 <c7> 04 25 00 00 00 00 fe 09 00 00 e8 5b 4f ba ff 90 55 53 48 83 ec
[  396.785795] Chrome_~dThread[6499]: segfault at 0 ip 00007f4f6f5734d5 sp 00007f4f6db06b00 error 6 in libxul.so[7f4f6f118000+528e000]
[  396.785802] Code: 04 25 00 00 00 00 3a 02 00 00 e8 86 4f ba ff 48 89 df e8 a2 ca ff ff eb 86 48 8b 05 0d f4 27 05 48 8d 0d 86 0d 24 03 48 89 08 <c7> 04 25 00 00 00 00 fe 09 00 00 e8 5b 4f ba ff 90 55 53 48 83 ec

Last edited by coralfang; 12-22-2018 at 12:43 PM.
 
Old 12-22-2018, 12:45 PM   #2
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 727

Original Poster
Blog Entries: 3

Rep: Reputation: 226Reputation: 226Reputation: 226
I am going to assume the highlighted update is responsible; has anyone else had issues since this?
Code:
Thu Dec 20 04:19:50 UTC 2018
a/kernel-firmware-20181218_0f22c85-noarch-1.txz:  Upgraded.
a/kernel-generic-4.19.11-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.19.11-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.19.11-x86_64-1.txz:  Upgraded.
ap/cups-filters-1.21.6-x86_64-1.txz:  Upgraded.
d/bison-3.2.3-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.19.11-x86-1.txz:  Upgraded.
k/kernel-source-4.19.11-noarch-1.txz:  Upgraded.
l/glib2-2.58.2-x86_64-1.txz:  Upgraded.
l/libgsf-1.14.45-x86_64-1.txz:  Upgraded.
x/libinput-1.12.4-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.

EDIT;

If i run `xwmconfig` and set to xfce... i don't get these problems. Thunar works fine, and firefox also (writing from it now).

So could it be that awesome wm is incompatible with whatever has changed recently in slackware packages?

Last edited by coralfang; 12-22-2018 at 01:04 PM.
 
Old 12-23-2018, 05:57 PM   #3
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,632

Rep: Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389
Have you tried recompiling awesome wm?
 
Old 12-24-2018, 11:01 AM   #4
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 727

Original Poster
Blog Entries: 3

Rep: Reputation: 226Reputation: 226Reputation: 226
Quote:
Originally Posted by bassmadrigal View Post
Have you tried recompiling awesome wm?
Yeah, first thing i did after upgrading.
 
Old 12-24-2018, 02:25 PM   #5
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,632

Rep: Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389
Did that include its dependencies?

Code:
libxkbcommon
xcb-util-xrm
libxdg-basedir
lua
lgi
awesome
If that doesn't work, you could try building from their github. Maybe the newer code will fix the problem. It would require downloading the source tarball, and some minor modifications of the awesome.SlackBuild script.

Code:
https://github.com/awesomeWM/awesome/archive/7d09769/awesome-7d0976912e1c9fe5fe98ea0e5500c6faecfdf81f.tar.gz
Code:
diff --git a/awesome.SlackBuild b/awesome.SlackBuild
index ff29214..c929c12 100755
--- a/awesome.SlackBuild
+++ b/awesome.SlackBuild
@@ -23,7 +23,8 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=awesome
-VERSION=${VERSION:-4.2}
+VERSION=${VERSION:-7d09769}
+COMMIT=${COMMIT:-7d0976912e1c9fe5fe98ea0e5500c6faecfdf81f}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
@@ -59,9 +60,9 @@ set -e
 rm -rf $PKG
 mkdir -p $TMP $PKG $OUTPUT
 cd $TMP
-rm -rf $PRGNAM-$VERSION
-tar xvf $CWD/$PRGNAM-$VERSION.tar.xz
-cd $PRGNAM-$VERSION
+rm -rf $PRGNAM-$COMMMIT
+tar xvf $CWD/$PRGNAM-$COMMIT.tar.gz
+cd $PRGNAM-$COMMIT
 chown -R root:root .
 find -L . \
  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
 
Old 12-26-2018, 02:20 PM   #6
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 727

Original Poster
Blog Entries: 3

Rep: Reputation: 226Reputation: 226Reputation: 226
Mhmmm, i rebuilt the dependencies as usual. Although i did overlook lua.

I'll try rebuilding that, if same problem occurs i will modify the slackbuild, hopefully that will work. Thanks.

EDIT: Just used the git version as you suggested, but no differences, thunar still crashes when pressing the "ctrl" key. Also rebuilt lua beforehand.

Last edited by coralfang; 12-26-2018 at 02:34 PM.
 
Old 12-26-2018, 04:15 PM   #7
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,632

Rep: Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389
If you had to rebuild lua, make sure you also rebuild lgi and then awesome... just to make sure that any changes in those dependencies are reflected in their rebuilt versions.

If that doesn't work, you could either try Alien Bob's Slackware Live and see if it and its dependencies will compile and work (letting you know it's something on your own install causing the problem) or you can post on the SBo scripts not building on -current post and see if others can replicate it.
 
Old 12-26-2018, 04:50 PM   #8
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 727

Original Poster
Blog Entries: 3

Rep: Reputation: 226Reputation: 226Reputation: 226
Quote:
Originally Posted by bassmadrigal View Post
If you had to rebuild lua, make sure you also rebuild lgi and then awesome... just to make sure that any changes in those dependencies are reflected in their rebuilt versions.
I just double checked, rebuilding all dependencies again, but same issue occurs.

Testing with Thunar again; still randomly crashes after a few seconds of input (mouse hovering/clicking), or immediately when pressing "ctrl" key;


Code:
$ thunar

(thunar:20733): Gdk-ERROR **: 21:47:46.836: The program 'thunar' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 5397 error_code 8 request_code 2 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
 
Old 01-03-2019, 05:52 AM   #9
Samuel88
LQ Newbie
 
Registered: Feb 2017
Posts: 6

Rep: Reputation: Disabled
Same problem with awesome and a lot of gtk application like firefox, thunar, google-chrome.
Any suggestion to resolve the problem.

Code:
(thunar:17159): Gdk-ERROR **: 11:40:09.645: The program 'thunar' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 7402 error_code 8 request_code 2 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
fish: 'thunar .' terminated by signal SIGTRAP (Trace or breakpoint trap)
 
1 members found this post helpful.
Old 01-04-2019, 11:12 PM   #10
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 727

Original Poster
Blog Entries: 3

Rep: Reputation: 226Reputation: 226Reputation: 226
Quote:
Originally Posted by Samuel88 View Post
Same problem with awesome and a lot of gtk application like firefox, thunar, google-chrome.
Any suggestion to resolve the problem.

Code:
(thunar:17159): Gdk-ERROR **: 11:40:09.645: The program 'thunar' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 7402 error_code 8 request_code 2 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
fish: 'thunar .' terminated by signal SIGTRAP (Trace or breakpoint trap)

Thanks for confirming it's not just my system! I'll open an issue on their github to ask about this. Cheers

Edit; Here's the issue
https://github.com/awesomeWM/awesome/issues/2549

Last edited by coralfang; 01-04-2019 at 11:29 PM. Reason: link
 
Old 01-05-2019, 12:26 AM   #11
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 727

Original Poster
Blog Entries: 3

Rep: Reputation: 226Reputation: 226Reputation: 226
Turns out it is indeed a regression with gtk/glib, workaround is quite simple;

Run awesome (for now) with;
Code:
 --no-argb
You will lose transparency effects with awesome, and your terminals though.

So for Slackware, patch /etc/X11/xinit/xinitrc.awesome;
(i created a xinitrc.awesome-no-argb and selected that with `xwmconfig`)

Code:
--- xinitrc.awesome	2019-01-05 05:23:30.340845166 +0000
+++ xinitrc.awesome-no-argb	2019-01-05 05:24:20.060178138 +0000
@@ -14,7 +14,7 @@
 
 # Start the window manager:
 if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
-  ck-launch-session dbus-launch --exit-with-session awesome
+  ck-launch-session dbus-launch --exit-with-session awesome --no-argb
 else
-  awesome
+  awesome --no-argb
 fi
 
Old 01-05-2019, 03:15 PM   #12
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,632

Rep: Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389
Apparently it can also be completely fixed with this patch to gtk.

Code:
From e3a1593a0984cc0156ec1892a46af8f256a64878 Mon Sep 17 00:00:00 2001
From: Daniel Boles <dboles.src@gmail.com>
Date: Thu, 13 Dec 2018 17:20:13 +0100
Subject: [PATCH] x11: Fix deprecation macro use

G_GNUC_END_IGNORE_DEPRECATIONS terminates the if statement and does not
consider the following block to be part of the if. So that block was
always taken irregardless of the pattern.

Fixes #1280
---
 gdk/x11/gdkwindow-x11.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gdk/x11/gdkwindow-x11.c b/gdk/x11/gdkwindow-x11.c
index 97ada6d739..764e39495f 100644
--- a/gdk/x11/gdkwindow-x11.c
+++ b/gdk/x11/gdkwindow-x11.c
@@ -2985,6 +2985,7 @@ gdk_window_x11_set_background (GdkWindow      *window,
   double r, g, b, a;
   cairo_surface_t *surface;
   cairo_matrix_t matrix;
+  cairo_pattern_t *parent_relative_pattern;
 
   if (GDK_WINDOW_DESTROYED (window))
     return;
@@ -2997,8 +2998,10 @@ gdk_window_x11_set_background (GdkWindow      *window,
     }
 
 G_GNUC_BEGIN_IGNORE_DEPRECATIONS
-  if (pattern == gdk_x11_get_parent_relative_pattern ())
+  parent_relative_pattern = gdk_x11_get_parent_relative_pattern ();
 G_GNUC_END_IGNORE_DEPRECATIONS
+
+  if (pattern == parent_relative_pattern)
     {
       GdkWindow *parent;
 
-- 
2.18.1
 
1 members found this post helpful.
Old 01-08-2019, 04:09 AM   #13
Samuel88
LQ Newbie
 
Registered: Feb 2017
Posts: 6

Rep: Reputation: Disabled
Seems to work well with this patch to gtk package.

If someone needs, I made the gtk package (gtk+3-3.24.2-x86_64-1.txz) with this patch applied

https://drive.google.com/file/d/1Wze...ew?usp=sharing

Last edited by Samuel88; 01-08-2019 at 08:31 AM.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
how to send snmp trap & recieve trap in C program minil Programming 3 07-10-2010 10:22 AM
[SOLVED] Ash segfaults on second backspace 64-current GazL Slackware 15 04-02-2010 05:40 AM
Slackware64-current: Creation of LUKS encrypted partition segfaults titopoquito Slackware 16 08-16-2009 05:02 AM
Kernel trap (Fatal trap 12) m!k@EL *BSD 4 09-06-2007 12:58 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:37 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration