You are not logged in.

#1 2020-03-09 12:10:38

Dan14
Member
Registered: 2015-11-06
Posts: 25

QT Applications no longer open. Segmentation fault (core dumped)

Hi. Some days ago I did a huge update on my system. I thought everything was ok but when I tried to open Dolphin (or any other qt application), it gives me this output:

qt5ct: using qt5ct plugin
Segmentation fault (core dumped)

Any ideas about what could it be? Thanks in advance.

Offline

#2 2020-03-10 10:12:03

xerxes_
Member
Registered: 2018-04-29
Posts: 304

Re: QT Applications no longer open. Segmentation fault (core dumped)

Output of coredumpctl and journalctl in [ code ] tags please? What DE do you use?

Offline

#3 2020-03-10 16:19:17

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

I use i3.

journalctl:

 Mar 10 12:10:00 dell-n5110 systemd[1]: Started Process Core Dump (PID 19923/UID 0).
Mar 10 12:10:00 dell-n5110 systemd-coredump[19924]: Process 19919 (dolphin) of user 1000 dumped core.
                                                    
                                                    Stack trace of thread 19919:
                                                    #0  0x00007f773e6da57c __tzfile_read (libc.so.6 + 0xbd57c)
                                                    #1  0x00007f773e6da12d tzset_internal (libc.so.6 + 0xbd12d)
                                                    #2  0x00007f773e6da23a tzset (libc.so.6 + 0xbd23a)
                                                    #3  0x00007f773e6d8f6d mktime (libc.so.6 + 0xbbf6d)
                                                    #4  0x00007f773c36fb70 _Z7qMkTimeP2tm (libQt5Core.so.5 + 0xc0b70)
                                                    #5  0x00007f773c44681e n/a (libQt5Core.so.5 + 0x19781e)
                                                    #6  0x00007f773c446eb8 n/a (libQt5Core.so.5 + 0x197eb8)
                                                    #7  0x00007f773c446fc6 n/a (libQt5Core.so.5 + 0x197fc6)
                                                    #8  0x00007f773c447460 n/a (libQt5Core.so.5 + 0x198460)
                                                    #9  0x00007f773c44954e _ZN9QDateTime18setMSecsSinceEpochEx (libQt5Core.so.5 + 0x19a54e)
                                                    #10 0x00007f773c44af71 _ZN9QDateTime19fromMSecsSinceEpochExN2Qt8TimeSpecEi (libQt5Core.so.5 + 0x19bf71)
                                                    #11 0x00007f773c44b683 _ZN9QDateTime19fromMSecsSinceEpochEx (libQt5Core.so.5 + 0x19c683)
                                                    #12 0x00007f773c48b54c _ZNK9QFileInfo8fileTimeEN11QFileDevice8FileTimeE (libQt5Core.so.5 + 0x1dc54c)
                                                    #13 0x00007f773c48b704 _ZNK9QFileInfo12lastModifiedEv (libQt5Core.so.5 + 0x1dc704)
                                                    #14 0x00007f773c4e67cc n/a (libQt5Core.so.5 + 0x2377cc)
                                                    #15 0x00007f773c4e68dc n/a (libQt5Core.so.5 + 0x2378dc)
                                                    #16 0x00007f773c4e749d n/a (libQt5Core.so.5 + 0x23849d)
                                                    #17 0x00007f773c4e7560 _ZN9QSettingsC2ERK7QStringNS_6FormatEP7QObject (libQt5Core.so.5 + 0x238560)
                                                    #18 0x00007f773506b691 _ZN16Qt5CTStylePlugin6createERK7QString (libqt5ct-style.so + 0x4691)
                                                    #19 0x00007f773d15c6ae _ZN13QStyleFactory6createERK7QString (libQt5Widgets.so.5 + 0x1d26ae)
                                                    #20 0x00007f773d183b45 n/a (libQt5Widgets.so.5 + 0x1f9b45)
                                                    #21 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    #22 0x00007f773d0e63c2 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c3c2)
                                                    #23 0x00007f773d0ef599 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x165599)
                                                    #24 0x00007f773c55b1fa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ac1fa)
                                                    #25 0x00007f773c58fb59 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e0b59)
                                                    #26 0x00007f773d183945 n/a (libQt5Widgets.so.5 + 0x1f9945)
                                                    #27 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    #28 0x00007f773d0e63c2 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c3c2)
                                                    #29 0x00007f773d0ef599 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x165599)
                                                    #30 0x00007f773c55b1fa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ac1fa)
                                                    #31 0x00007f773c58fb59 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e0b59)
                                                    #32 0x00007f773d183945 n/a (libQt5Widgets.so.5 + 0x1f9945)
                                                    #33 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    #34 0x00007f773d0e63c2 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c3c2)
                                                    #35 0x00007f773d0ef599 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x165599)
                                                    #36 0x00007f773c55b1fa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ac1fa)
                                                    #37 0x00007f773c58fb59 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e0b59)
                                                    #38 0x00007f773d183945 n/a (libQt5Widgets.so.5 + 0x1f9945)
                                                    #39 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    #40 0x00007f773d0e63c2 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c3c2)
                                                    #41 0x00007f773d0ef599 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x165599)
                                                    #42 0x00007f773c55b1fa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ac1fa)
                                                    #43 0x00007f773c58fb59 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e0b59)
                                                    #44 0x00007f773d183945 n/a (libQt5Widgets.so.5 + 0x1f9945)
                                                    #45 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    #46 0x00007f773d0e63c2 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c3c2)
                                                    #47 0x00007f773d0ef599 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x165599)
                                                    #48 0x00007f773c55b1fa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ac1fa)
                                                    #49 0x00007f773c58fb59 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e0b59)
                                                    #50 0x00007f773d183945 n/a (libQt5Widgets.so.5 + 0x1f9945)
                                                    #51 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    #52 0x00007f773d0e63c2 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c3c2)
                                                    #53 0x00007f773d0ef599 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x165599)
                                                    #54 0x00007f773c55b1fa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ac1fa)
                                                    #55 0x00007f773c58fb59 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e0b59)
                                                    #56 0x00007f773d183945 n/a (libQt5Widgets.so.5 + 0x1f9945)
                                                    #57 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    #58 0x00007f773d0e63c2 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c3c2)
                                                    #59 0x00007f773d0ef599 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x165599)
                                                    #60 0x00007f773c55b1fa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ac1fa)
                                                    #61 0x00007f773c58fb59 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e0b59)
                                                    #62 0x00007f773d183945 n/a (libQt5Widgets.so.5 + 0x1f9945)
                                                    #63 0x00007f773d184535 _ZN11QProxyStyle5eventEP6QEvent (libQt5Widgets.so.5 + 0x1fa535)
                                                    
                                                    Stack trace of thread 19920:
                                                    #0  0x00007f773e711abf __poll (libc.so.6 + 0xf4abf)
                                                    #1  0x00007f773ad4463b n/a (libxcb.so.1 + 0xc63b)
                                                    #2  0x00007f773ad4637b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
                                                    #3  0x00007f7736c43f11 n/a (libQt5XcbQpa.so.5 + 0x65f11)
                                                    #4  0x00007f773c37be96 n/a (libQt5Core.so.5 + 0xcce96)
                                                    #5  0x00007f773ad8746f start_thread (libpthread.so.0 + 0x946f)
                                                    #6  0x00007f773e71c3d3 __clone (libc.so.6 + 0xff3d3)
                                                    
                                                    Stack trace of thread 19921:
                                                    #0  0x00007f773e711abf __poll (libc.so.6 + 0xf4abf)
                                                    #1  0x00007f773a1107a0 n/a (libglib-2.0.so.0 + 0x6d7a0)
                                                    #2  0x00007f773a110871 g_main_context_iteration (libglib-2.0.so.0 + 0x6d871)
                                                    #3  0x00007f773c5b5270 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x306270)
                                                    #4  0x00007f773c559dbc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2aadbc)
                                                    #5  0x00007f773c37ad02 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcbd02)
                                                    #6  0x00007f773c80cb38 n/a (libQt5DBus.so.5 + 0x15b38)
                                                    #7  0x00007f773c37be96 n/a (libQt5Core.so.5 + 0xcce96)
                                                    #8  0x00007f773ad8746f start_thread (libpthread.so.0 + 0x946f)
                                                    #9  0x00007f773e71c3d3 __clone (libc.so.6 + 0xff3d3)
Mar 10 12:10:01 dell-n5110 kernel: audit: type=1131 audit(1583856600.987:134): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@6-19923-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 

coredumpctl:

TIME                            PID   UID   GID SIG COREFILE  EXE
Tue 2020-03-10 12:10:00 -04   19919  1000  1000  11 present   /usr/bin/dolphin 

Offline

#4 2020-03-10 16:31:50

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,737

Re: QT Applications no longer open. Segmentation fault (core dumped)

output of 'locale' and 'timedatectl'?

Online

#5 2020-03-10 17:22:37

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

locale:

locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

timedatectl:

timedatectl
               Local time: Tue 2020-03-10 12:43:46 -04 
           Universal time: Tue 2020-03-10 16:43:46 UTC 
                 RTC time: Tue 2020-03-10 16:43:46     
                Time zone: America/Caracas (-04, -0400)
System clock synchronized: yes                         
              NTP service: active                      
          RTC in local TZ: no   

Offline

#6 2020-03-11 07:16:26

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,737

Re: QT Applications no longer open. Segmentation fault (core dumped)

That looks OK. We're going to need a backtrace with debug symbols to go any further.

Online

#7 2020-03-11 19:27:07

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

arojas wrote:

That looks OK. We're going to need a backtrace with debug symbols to go any further.

This?

 (gdb) run dolphin
Starting program: /usr/bin/dolphin dolphin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffef93c700 (LWP 27027)]
qt5ct: using qt5ct plugin
[New Thread 0x7fffeef0a700 (LWP 27028)]

Thread 1 "dolphin" received signal SIGSEGV, Segmentation fault.
0x00007ffff7d6a4c5 in __tzfile_read () from /usr/lib/libc.so.6 

Offline

#8 2020-03-16 20:09:41

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

Any ideas? I still haven't found a solution...

Offline

#9 2020-03-16 20:09:41

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

Maybe the qt5ct package is kinda buggy? I use the repo test.

Last edited by Dan14 (2020-03-16 20:11:00)

Offline

#10 2020-03-16 21:00:42

xerxes_
Member
Registered: 2018-04-29
Posts: 304

Re: QT Applications no longer open. Segmentation fault (core dumped)

You can reinstall qt5ct package and update system both at once by command 'pacman -Syu qt5ct' and see if that resolve your problem.

If that don't help, print here 'set | less' or search in that output if you have such environment variables set and to what values: QT_STYLE_OVERRIDE, QT_SELECT, QT_QPA_PLATFORMTHEME or other QT variables (beware they are case sensitive).

Offline

#11 2020-03-16 21:26:29

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

xerxes_ wrote:

You can reinstall qt5ct package and update system both at once by command 'pacman -Syu qt5ct' and see if that resolve your problem.

If that don't help, print here 'set | less' or search in that output if you have such environment variables set and to what values: QT_STYLE_OVERRIDE, QT_SELECT, QT_QPA_PLATFORMTHEME or other QT variables (beware they are case sensitive).

The only thing that appears is this: QT_QPA_PLATFORMTHEME=qt5ct

By reinstalling qt5ct package doesn't do anything. However if I uninstall it, Dolphin opens successfully but with the gtk theme (I think).

Offline

#12 2020-03-16 22:13:48

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 10,076
Website

Re: QT Applications no longer open. Segmentation fault (core dumped)

Dan14 wrote:

I use the repo test.

Please include that sort of information up front: https://wiki.archlinux.org/index.php/Of … positories

Mod note: Moving to testing.


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#13 2020-03-17 10:50:27

xerxes_
Member
Registered: 2018-04-29
Posts: 304

Re: QT Applications no longer open. Segmentation fault (core dumped)

You may read this thread with sublinks. Maybe you will figure out solution for yourself.

Offline

#14 2020-03-27 05:10:33

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

xerxes_ wrote:

You may read this thread with sublinks. Maybe you will figure out solution for yourself.

Thanks, I had already configured the environment variable as QT_QPA_PLATFORMTHEME=qt5ct, before this problem, but that hasn't fixed the problem hmm. I found out something though, there's a qt5ct.conf located in

 ~.config/qt5ct/qt5ct.conf 

, which has the following configuration:

 
[Appearance]
color_scheme_path=/home/dany/.config/qt5ct/colors/test.conf
custom_palette=false
icon_theme=Papirus-Dark
style=gtk2

If I change the ''style'' to gtk3, as in: style=gtk3, Dolphin does open, but with a weird style. But if I leave it with the gtk2, I still get the ''segmentation fault''. Any clues of what this could be?

Offline

#15 2020-03-27 15:45:18

xerxes_
Member
Registered: 2018-04-29
Posts: 304

Re: QT Applications no longer open. Segmentation fault (core dumped)

In the above thread that I point you I was trying to switch from gtk2 (or I even have gtk without number?) to qt5ct and I was able to display all possible styles that I could switch in terminal, but I forgot how I was doing that (there was a lot of styles, don't remember whether all worked). Did you look into the links posted in that thread?

Now part of my qt5ct.conf you mentioned looks like this:

[Appearance]
color_scheme_path=/usr/share/qt5ct/colors/airy.conf
custom_palette=false
icon_theme=Numix-Square
standard_dialogs=default
style=Fusion

Offline

#16 2020-03-27 17:47:40

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

xerxes_ wrote:

In the above thread that I point you I was trying to switch from gtk2 (or I even have gtk without number?) to qt5ct and I was able to display all possible styles that I could switch in terminal, but I forgot how I was doing that (there was a lot of styles, don't remember whether all worked). Did you look into the links posted in that thread?

Now part of my qt5ct.conf you mentioned looks like this:

[Appearance]
color_scheme_path=/usr/share/qt5ct/colors/airy.conf
custom_palette=false
icon_theme=Numix-Square
standard_dialogs=default
style=Fusion

Yeah, I looked at the links posted on those threads. I figured something out when you send me your configuration. Apparently the style I had in ''gtk2'' it's like it doesn't have any theme set (or something like that). I ran qt5ct on the terminal, and I changed the style to ''kvantum-dark'' (which of course overwrote the qt5ct file to kvantum-dark). Now, something strange happened. when I did that, Transmission-qt had kvantum-dark. But Dolphin and Kate had another theme called ''Arc-Dark''. How can I look at the configuration files separately of each apps and see which themes are they taking?

Offline

#17 2020-03-27 21:30:22

xerxes_
Member
Registered: 2018-04-29
Posts: 304

Re: QT Applications no longer open. Segmentation fault (core dumped)

I don't have this progs installed, so I can't tell you whether they create config files or what can you find in them, but you may look in directly in your home dir like:

/home/dany/.kate
/home/dany/.config/kate
/home/dany/.cache/kate
/home/dany/.local/share/kate

etc. same for dolphin.

Also maybe something interesting you could find in 'man kate', 'man dolphin' and in 'pacman -Ql kate/dolphin | less' search for: config, docbook, kcfg, and other things what look interesting.

Offline

#18 2020-03-28 05:18:27

Dan14
Member
Registered: 2015-11-06
Posts: 25

Re: QT Applications no longer open. Segmentation fault (core dumped)

xerxes_ wrote:

I don't have this progs installed, so I can't tell you whether they create config files or what can you find in them, but you may look in directly in your home dir like:

/home/dany/.kate
/home/dany/.config/kate
/home/dany/.cache/kate
/home/dany/.local/share/kate

etc. same for dolphin.

Also maybe something interesting you could find in 'man kate', 'man dolphin' and in 'pacman -Ql kate/dolphin | less' search for: config, docbook, kcfg, and other things what look interesting.

Thanks, I just tried that. I went for every file, but unfortunately couldn't find anything regarding the theme. It's really weird, I realized that every qt applications it does have the kvantum-dark. But only Kate and Dolphin have the ''Arc-Dark''.

I'll leave this image to show the difference between the programs. I opened Ksysguard to show the difference: https://imgur.com/a/1HAw0eN

Offline

#19 2020-06-07 18:52:02

Sturmgewehr
Member
Registered: 2012-06-12
Posts: 5

Re: QT Applications no longer open. Segmentation fault (core dumped)

It's easier to delete the config and reset the appearance (graphical) settings:
https://bbs.archlinux.org/viewtopic.php?pid=1908917

Offline

Board footer

Powered by FluxBB