Bug 1369594 - [abrt] xfce4-terminal: XInternAtom(): xfce4-terminal killed by SIGSEGV
Summary: [abrt] xfce4-terminal: XInternAtom(): xfce4-terminal killed by SIGSEGV
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-terminal
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:be69bf385f6b9a70551f7ceac1a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-23 21:45 UTC by Duco van Amstel
Modified: 2016-09-13 22:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-13 20:38:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (33.88 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: cgroup (242 bytes, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: core_backtrace (4.11 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: dso_list (9.44 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: environ (950 bytes, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: exploitable (112 bytes, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: limits (1.29 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: maps (43.91 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: mountinfo (3.48 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: namespaces (102 bytes, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: open_fds (1.08 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: proc_pid_status (1.09 KB, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details
File: var_log_messages (311 bytes, text/plain)
2016-08-23 21:45 UTC, Duco van Amstel
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Xfce 12785 0 None None None 2016-08-23 21:54:42 UTC

Description Duco van Amstel 2016-08-23 21:45:12 UTC
Description of problem:
No particular modifications or updates to my system.
Xfce-terminal crashes either directly on opening or on the first interaction with the newly opened terminal.

Version-Release number of selected component:
xfce4-terminal-0.6.90-1.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        xfce4-terminal
crash_function: XInternAtom
executable:     /usr/bin/xfce4-terminal
global_pid:     1974
kernel:         4.6.6-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       unknown
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 XInternAtom at IntAtom.c:174
 #1 gdk_x11_atom_to_xatom_for_display at gdkproperty-x11.c:115
 #2 gdk_x11_screen_supports_net_wm_hint at gdkscreen-x11.c:1754
 #3 terminal_window_init at terminal-window.c:388
 #4 g_type_create_instance at gtype.c:1875
 #5 g_object_new_internal at gobject.c:1781
 #6 g_object_new_valist at gobject.c:2040
 #8 terminal_window_new at terminal-window.c:1895
 #9 terminal_app_create_window at terminal-app.c:334
 #10 terminal_app_open_window at terminal-app.c:685

Comment 1 Duco van Amstel 2016-08-23 21:45:17 UTC
Created attachment 1193418 [details]
File: backtrace

Comment 2 Duco van Amstel 2016-08-23 21:45:18 UTC
Created attachment 1193419 [details]
File: cgroup

Comment 3 Duco van Amstel 2016-08-23 21:45:19 UTC
Created attachment 1193420 [details]
File: core_backtrace

Comment 4 Duco van Amstel 2016-08-23 21:45:21 UTC
Created attachment 1193421 [details]
File: dso_list

Comment 5 Duco van Amstel 2016-08-23 21:45:23 UTC
Created attachment 1193422 [details]
File: environ

Comment 6 Duco van Amstel 2016-08-23 21:45:24 UTC
Created attachment 1193423 [details]
File: exploitable

Comment 7 Duco van Amstel 2016-08-23 21:45:25 UTC
Created attachment 1193424 [details]
File: limits

Comment 8 Duco van Amstel 2016-08-23 21:45:28 UTC
Created attachment 1193425 [details]
File: maps

Comment 9 Duco van Amstel 2016-08-23 21:45:29 UTC
Created attachment 1193426 [details]
File: mountinfo

Comment 10 Duco van Amstel 2016-08-23 21:45:31 UTC
Created attachment 1193427 [details]
File: namespaces

Comment 11 Duco van Amstel 2016-08-23 21:45:32 UTC
Created attachment 1193428 [details]
File: open_fds

Comment 12 Duco van Amstel 2016-08-23 21:45:34 UTC
Created attachment 1193429 [details]
File: proc_pid_status

Comment 13 Duco van Amstel 2016-08-23 21:45:35 UTC
Created attachment 1193430 [details]
File: var_log_messages

Comment 14 Duco van Amstel 2016-08-23 21:48:30 UTC
Before this new faulty behaviour the terminal was working fine. The bug appeared without any reboot or other specific operation between two terminal start-ups. Rebooting (warm & cold boot) the system does not make the behaviour disappear.

Comment 15 Kevin Fenzi 2016-08-23 21:54:42 UTC
I've already reported this upstream. You are running in a gnome-wayland session right? 

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

workaround: 

GDK_BACKEND=wayland xfce4-terminal

Comment 16 Duco van Amstel 2016-08-24 06:07:43 UTC
Yes indeed. It's a gnome-wayland session.
Thanks for the upstream report!

Comment 17 Kevin Fenzi 2016-09-02 20:48:28 UTC
Can you try this scratch build: 

https://koji.fedoraproject.org/koji/taskinfo?taskID=15473669

and see if it works under wayland for you now?

Comment 18 Duco van Amstel 2016-09-10 08:23:23 UTC
(In reply to Kevin Fenzi from comment #17)
> Can you try this scratch build: 
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=15473669
> 
> and see if it works under wayland for you now?

Sorry for the late reply. I was away from my computer for the last week.

I've installed the scratch and my terminal is not crashing at launch or after a couple of commands (time will tell if it's solid).

However it's not supporting transparency any more as it did before the crashes even though I still have my background set to transparent. Wayland interference? Effect of the scratch build?

Tell me what info you need and I'll get it.

Comment 19 Kevin Fenzi 2016-09-10 17:07:46 UTC
Odd. Transparency is working here fine, but I am using the final new upstream release. 

It's in updates testing now, so can you try it: 

sudo dnf --enablerepo=updates-testing update xfce4-terminal

Should get you version 0.6.92-1.fc24.

Can you update to that and retest?

Comment 20 Duco van Amstel 2016-09-10 21:57:19 UTC
I've just installed the final new upstream release in updates-testing and even after reboot the transparency is not coming back.

From visual observation it seems like the terminal is opening with transparency enabled but switches to a black opaque background (i.e the 'none' background variety) after 1/4 second.

I don't have any special or funky visual tweaks on my system. Just vanilla F24 with Gnome on Wayland. And even without Wayland (i.e standard Gnome) the transparency is not coming back.

It might well be that this is a problem particular to my workstation but for the moment I don't have a clue what might have provoked this behaviour. Like said, I'd be happy to help out investigating this.

Comment 21 Kevin Fenzi 2016-09-12 02:51:46 UTC
Can you confirm for sure you have the newer build?

what does: 

rpm -q xfce4-terminal

which xfce4-terminal

rpm -V xfce4-terminal

all output? If thats verified I am not sure whats next... will try and think of what could be different.

Comment 22 Duco van Amstel 2016-09-12 22:16:01 UTC
I am running the newer build.
rpm -q xfce4-terminal returns "xfce4-terminal-0.6.92-1.fc24.x86_64"

And the path is the obvious one to the executable which also returns 0.6.92-1.fc24.x86_64 when queried with --version.

If you don't have any thoughts that's OK. My goal is not to use you as my personal debugger. As usual there's a high probability that it's specific to my machine because of some unforeseen detail, especially as yours is behaving well.

Comment 23 Kevin Fenzi 2016-09-13 22:12:23 UTC
Quick question: when you were testing this, were you just running a xfce4-terminal and looking at the background behind it? Or were there other terminals or apps behind it that didn't show up?

One quirk of the gtk3 port is that while you can see other applications behind a transparent xfce4-terminal, the background will never show up, it will just be solid if the only thing behind the terminal is the background... 

Just a stab in the dark.


Note You need to log in before you can comment on or make changes to this bug.