Skip to content
This repository has been archived by the owner on Nov 21, 2023. It is now read-only.

Segmentation fault opening gnome-control-center #49

Closed
jfernandz opened this issue Oct 19, 2019 · 23 comments
Closed

Segmentation fault opening gnome-control-center #49

jfernandz opened this issue Oct 19, 2019 · 23 comments

Comments

@jfernandz
Copy link
Contributor

I'm getting a segmentation fault (core dumped) message when I try to open gnome-control-center binary.
@jcstr
Copy link
Member

jcstr commented Oct 20, 2019

did you update to the latest versions of the GNOME packages? days ago have been updated.

@jfernandz
Copy link
Contributor Author

jfernandz commented Oct 20, 2019 •
edited

Of course, I'm in 3.34.1 version. My whole system is usually upgraded and I'm having the issue in two different computers (desktop and laptop)

@jcstr
Copy link
Member

jcstr commented Oct 22, 2019

This is weird, personally don't have any kind of issue, this is only related with GNOME control center?

@jfernandz
Copy link
Contributor Author

jfernandz commented Oct 22, 2019 •
edited

well, the strange thin is when I start gnome with gdm it does work as expected, but not in i3-gnome

Here the gdb output:

gdb gnome-control-center
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 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 gnome-control-center...
(No debugging symbols found in gnome-control-center)
(gdb) r
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe9c02700 (LWP 15476)]
[New Thread 0x7fffe9401700 (LWP 15477)]
[New Thread 0x7fffe2100700 (LWP 15482)]
[New Thread 0x7fffe18ff700 (LWP 15483)]
[New Thread 0x7fffe1051700 (LWP 15485)]
[New Thread 0x7fffcffff700 (LWP 15499)]

Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
0x00005555556725c0 in cc_display_config_set_minimum_size ()
(gdb) c
Continuing.
Couldn't get registers: No existe el proceso.
Couldn't get registers: No existe el proceso.
(gdb) [Thread 0x7fffcffff700 (LWP 15499) exited]
[Thread 0x7fffe1051700 (LWP 15485) exited]
[Thread 0x7fffe18ff700 (LWP 15483) exited]
[Thread 0x7fffe2100700 (LWP 15482) exited]
[Thread 0x7fffe9401700 (LWP 15477) exited]
[Thread 0x7fffe9c02700 (LWP 15476) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
q

And here the journald log when I run gnome-control-center:

oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): LG Electronics LG FULL HD (CRT-0): connected
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): LG Electronics LG FULL HD (CRT-0): 400.0 MHz maximum pixel clock
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0):
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): DFP-0: disconnected
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0):
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): DFP-1: disconnected
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
oct 22 08:36:37 GibyArch /usr/lib/gdm-x-session[13970]: (--) NVIDIA(GPU-0):
oct 22 08:36:37 GibyArch kernel: gnome-control-c[18837]: segfault at 0 ip 000056320c0d55c0 sp 00007fffc5855278 error 4 in gnome-control-center[56320c002000+103000]
oct 22 08:36:37 GibyArch kernel: Code: 08 31 c0 ff 15 49 29 31 00 e9 48 ff ff ff ff 15 ce 23 31 00 66 0f 1f 44 00 00 48 8b 07 ff a0 d0 00 00 00 0f 1f 80 00 00 00 00 <48> 8b 07 ff a0 c8 00 00 00 0f 1f 80 00 00 00 00 48 8b 05 29 92 31
oct 22 08:36:37 GibyArch kernel: audit: type=1701 audit(1571726197.865:135): auid=1000 uid=1000 gid=100 ses=6 pid=18837 comm="gnome-control-c" exe="/usr/bin/gnome-control-center" sig=11 res=1
oct 22 08:36:37 GibyArch audit[18837]: ANOM_ABEND auid=1000 uid=1000 gid=100 ses=6 pid=18837 comm="gnome-control-c" exe="/usr/bin/gnome-control-center" sig=11 res=1
oct 22 08:36:37 GibyArch systemd[1]: Started Process Core Dump (PID 18844/UID 0).
oct 22 08:36:37 GibyArch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@8-18844-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
oct 22 08:36:37 GibyArch kernel: audit: type=1130 audit(1571726197.905:136): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@8-18844-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
oct 22 08:36:38 GibyArch systemd-coredump[18845]: Process 18837 (gnome-control-c) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 18837:
                                                  #0  0x000056320c0d55c0 cc_display_config_set_minimum_size (gnome-control-center)
                                                  #1  0x000056320c0dd6e2 n/a (gnome-control-center)
                                                  #2  0x000056320c0dde91 n/a (gnome-control-center)
                                                  #3  0x00007f9c83003d3a g_closure_invoke (libgobject-2.0.so.0)
                                                  #4  0x00007f9c82ff188e n/a (libgobject-2.0.so.0)
                                                  #5  0x00007f9c82ff598a g_signal_emit_valist (libgobject-2.0.so.0)
                                                  #6  0x00007f9c82ff67f0 g_signal_emit (libgobject-2.0.so.0)
                                                  #7  0x000056320c0d557c n/a (gnome-control-center)
                                                  #8  0x00007f9c830e7c24 n/a (libgio-2.0.so.0)
                                                  #9  0x00007f9c830ed447 n/a (libgio-2.0.so.0)
                                                  #10 0x00007f9c8309cc15 n/a (libgio-2.0.so.0)
                                                  #11 0x00007f9c830e7c24 n/a (libgio-2.0.so.0)
                                                  #12 0x00007f9c830e7c59 n/a (libgio-2.0.so.0)
                                                  #13 0x00007f9c82f172cf g_main_context_dispatch (libglib-2.0.so.0)
                                                  #14 0x00007f9c82f19211 n/a (libglib-2.0.so.0)
                                                  #15 0x00007f9c82f19251 g_main_context_iteration (libglib-2.0.so.0)
                                                  #16 0x00007f9c830ca9de g_application_run (libgio-2.0.so.0)
                                                  #17 0x000056320c0023fe main (gnome-control-center)
                                                  #18 0x00007f9c83205153 __libc_start_main (libc.so.6)
                                                  #19 0x000056320c00244e _start (gnome-control-center)
                                                  
                                                  Stack trace of thread 18843:
                                                  #0  0x00007f9c832d7e9d syscall (libc.so.6)
                                                  #1  0x00007f9c82eca11b g_cond_wait_until (libglib-2.0.so.0)
                                                  #2  0x00007f9c82f47f63 n/a (libglib-2.0.so.0)
                                                  #3  0x00007f9c82eef13b n/a (libglib-2.0.so.0)
                                                  #4  0x00007f9c82ef5c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f9c814bf4cf start_thread (libpthread.so.0)
                                                  #6  0x00007f9c832dd2d3 __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 18841:
                                                  #0  0x00007f9c832d7e9d syscall (libc.so.6)
                                                  #1  0x00007f9c82eca11b g_cond_wait_until (libglib-2.0.so.0)
                                                  #2  0x00007f9c82f47f63 n/a (libglib-2.0.so.0)
                                                  #3  0x00007f9c82eef13b n/a (libglib-2.0.so.0)
                                                  #4  0x00007f9c82ef5c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f9c814bf4cf start_thread (libpthread.so.0)
                                                  #6  0x00007f9c832dd2d3 __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 18840:
                                                  #0  0x00007f9c832d29ef __poll (libc.so.6)
                                                  #1  0x00007f9c82f19180 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f9c82f19251 g_main_context_iteration (libglib-2.0.so.0)
                                                  #3  0x00007f9c6d4cbe5e n/a (libdconfsettings.so)
                                                  #4  0x00007f9c82ef5c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f9c814bf4cf start_thread (libpthread.so.0)
                                                  #6  0x00007f9c832dd2d3 __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 18842:
                                                  #0  0x00007f9c832d7e9d syscall (libc.so.6)
                                                  #1  0x00007f9c82eca11b g_cond_wait_until (libglib-2.0.so.0)
                                                  #2  0x00007f9c82f47f63 n/a (libglib-2.0.so.0)
                                                  #3  0x00007f9c82eef13b n/a (libglib-2.0.so.0)
                                                  #4  0x00007f9c82ef5c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f9c814bf4cf start_thread (libpthread.so.0)
                                                  #6  0x00007f9c832dd2d3 __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 18838:
                                                  #0  0x00007f9c832d29ef __poll (libc.so.6)
                                                  #1  0x00007f9c82f19180 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f9c82f19251 g_main_context_iteration (libglib-2.0.so.0)
                                                  #3  0x00007f9c82f192a2 n/a (libglib-2.0.so.0)
                                                  #4  0x00007f9c82ef5c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f9c814bf4cf start_thread (libpthread.so.0)
                                                  #6  0x00007f9c832dd2d3 __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 18839:
                                                  #0  0x00007f9c832d29ef __poll (libc.so.6)
                                                  #1  0x00007f9c82f19180 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f9c82f1a123 g_main_loop_run (libglib-2.0.so.0)
                                                  #3  0x00007f9c83087b48 n/a (libgio-2.0.so.0)
                                                  #4  0x00007f9c82ef5c11 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f9c814bf4cf start_thread (libpthread.so.0)
                                                  #6  0x00007f9c832dd2d3 __clone (libc.so.6)
oct 22 08:36:38 GibyArch systemd[1]: systemd-coredump@8-18844-0.service: Succeeded.
oct 22 08:36:39 GibyArch kernel: audit: type=1131 audit(1571726198.979:137): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@8-18844-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
oct 22 08:36:38 GibyArch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@8-18844-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

@jfernandz
Copy link
Contributor Author

This is weird, personally don't have any kind of issue, this is only related with GNOME control center?

only with gnome-control-center right, other components like gnome-calculator or gnome-calendar works pretty fine. I cannot start gnome-control-center even from plain i3 (instead of i3-gnome, I mean). I've also tried starting i3-gnome from gdm but still the same.

How do you start i3-gnome, @jcstr ?

@muktupavels
Copy link
Member

Do you have something that provides org.gnome.Mutter.DisplayConfig D-Bus interface?

@jfernandz
Copy link
Contributor Author

@muktupavels

Do you have something that provides org.gnome.Mutter.DisplayConfig D-Bus interface?

I've installed mutter, but I don't know if it is providing org.gnome.Mutter.DisplayConfig instance, how can I check that?

@muktupavels
Copy link
Member

If you are not using mutter as window manager then it does not and can not provide that interface. You can try to use gnome-flashback...

@jfernandz
Copy link
Contributor Author

@muktupavels

I'm using i3 as window manager, that's what is i3-gnome for! Ain't it?

@muktupavels
Copy link
Member

gnome-flashback is not window manager! You need something that will provide mentioned interface... Even if it would not crash, you would not be able to configure your display/monitors.

Can you start GNOME Control Center with gnome-control-center sound?

@jfernandz
Copy link
Contributor Author

Yes, I know the window manager is mutter; but I didn't know that gnome-flashback would provide that interface.

You are right, I'm able to open gnome-control-center from sound config, and the issue is solved with gnome-flashback

Thank you so much, @muktupavels ;-)

@jfernandz
Copy link
Contributor Author

Anyway, I've noticed ... gnome-flashback crashes when I switch between or manage displays, it is working fine in your case? @muktupavels

@muktupavels
Copy link
Member

Have not seen crashes. Can you provide steps that I could try to see if same thing works for me?

@jfernandz
Copy link
Contributor Author

jfernandz commented Oct 30, 2019 •
edited

Well @muktupavels, first of all you must

  1. Add exec --no-startup-id gnome-flashback in i3 config (obviously)
  2. Start i3-gnome by adding exec i3-gnome to your .xinitrc and doing startx in a tty (I mean, I'm not using gdm)

but then

  1. Take a laptop and plug in an extra display to hdmi output
  2. start i3-gnome from the tty
  3. (you could even to get a horizontal half split display even) but by default it will be always in Join Displays mode
  4. Change to single display and choose HDMI output and apply
  5. gnome-flashback crashes

@muktupavels
Copy link
Member

I am not using i3... Anyway, gnome-flashback crashing is upstream problem/bug. Can you report this crash here - https://gitlab.gnome.org/GNOME/gnome-flashback/issues. I will try to reproduce when I have more time. If you can, please attach also stacktrace.

@jfernandz
Copy link
Contributor Author

@muktupavels I'm not sure, because I've not tested gnome-flashback working in the gnome environment. I get also a crash when I start my i3-gnome with the secondary display plugged in and (since gnome-control-center display is loading by default in Join Displays mode) when I close the laptop lid to work only with HDMI output; then gnome-flashback crashes. Yes I know I must provide the stacktraces/backtraces. But I would like if you could certify this.

Anyway ... I don't like to much the integration between gnome-control-center display and i3wm.

Particularly i3wm working on multiple displays setup is not attractive to me. I think it is a complete mess, because by default you only can assign dynamically workspaces to displays (this is a complete mess because depends on which display you are, the next ws switch will be in there), the other possibility is fix workspaces for a particular display in the i3 config file; but this is also a mess but more restrictive.

I would like to get an extra space (the extra display) in each workspace and don't fight against which display is showing which workspace. But I guess this is a i3wm thing, I'm going to talk with i3wm people to see if I can get the behaviour desired.

I would like to be possible load by default gnome-control-center display in single display mode due this i3 messy behaviour. Though when I change the showed display gnome-flashback crashes ...

Another important detail I've realized is ... telegram system tray icon disappears when I load gnome-flashback, that's really bad.

@muktupavels
Copy link
Member

gsettings set org.gnome.gnome-flashback status-notifier-watcher false might help with tray icon.

gnomesysadmins pushed a commit to GNOME/gnome-flashback that referenced this issue Oct 31, 2019
@muktupavels
backends: initialize current_mode variable
5e00c43 
i3-gnome/i3-gnome#49
gnomesysadmins pushed a commit to GNOME/gnome-flashback that referenced this issue Oct 31, 2019
@muktupavels
backends: initialize current_mode variable
26a4c9f 
i3-gnome/i3-gnome#49
gnomesysadmins pushed a commit to GNOME/gnome-flashback that referenced this issue Oct 31, 2019
@muktupavels
backends: initialize current_mode variable
c4c1d08 
i3-gnome/i3-gnome#49
@muktupavels
Copy link
Member

I was able to reproduce crash on laptop, if it was same problem then fixed by https://gitlab.gnome.org/GNOME/gnome-flashback/commit/5e00c43dff14cb0c77498d39507e69176a377780.

@jfernandz
Copy link
Contributor Author

jfernandz commented Nov 1, 2019 •
edited

gsettings set org.gnome.gnome-flashback status-notifier-watcher false might help with tray icon.

@muktupavels thank you for that suggestion, I've found also the whole gnome-flashback config in dconf-editor and might be helpful for other things ---like disable sound-applet to use pasystray instead---

Also... when do you think your fix will be released? Which version I mean? Not for 3.34.0 I guess, but maybe the next, right?

@muktupavels
Copy link
Member

Already done - https://gitlab.gnome.org/GNOME/gnome-flashback/commit/a845b1c7416a85a915935d889f855517eb359184.

@jfernandz
Copy link
Contributor Author

Already done - https://gitlab.gnome.org/GNOME/gnome-flashback/commit/a845b1c7416a85a915935d889f855517eb359184.

Oh, yeah, but that's for 3.34.2, I'm in 3.34.0 in Arch Linux, so I guess I must wait to devs update the package or maybe using asp I could repackage for the 3.34.2 tag

@jcstr
Copy link
Member

jcstr commented Nov 10, 2019

is this issue fixed?

@jfernandz
Copy link
Contributor Author

I think it might be marked as closed, right.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@muktupavels @jfernandz @jcstr