Bug 1759620

Summary: [abrt] firewall-applet: qt_message_fatal(): python3.7 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Pat Kelly <pmkellly72>
Component: firewalldAssignee: Eric Garver <egarver>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: awilliam, egarver, psutter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/839526d6332fc043ebf0057c7e6415a54577a154
Whiteboard: abrt_hash:2e89dc2374b8c5fc61b3fffd61248a24e1ecd286;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-06 15:30:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Pat Kelly 2019-10-08 17:21:32 UTC 
Version-Release number of selected component:
firewall-applet-0.7.2-1.fc31

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/gnome\x2dsession\x2dmanager.slice/gnome-session-manager
cmdline:        /usr/bin/python3 /usr/bin/firewall-applet
crash_function: qt_message_fatal
executable:     /usr/bin/python3.7
journald_cursor: s=c054ba2d76f24c8bb750ff1c88a5b924;i=77a8;b=c6e01da06657442ab43cbdfada7641b0;m=ca8c551d1;t=59468c43fdf27;x=cf50bbc1fb75234e
kernel:         5.3.2-300.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Pat Kelly 2019-10-08 17:21:36 UTC 
Created attachment 1623532 [details]
File: backtrace
Comment 2 Pat Kelly 2019-10-08 17:21:37 UTC 
Created attachment 1623533 [details]
File: core_backtrace
Comment 3 Pat Kelly 2019-10-08 17:21:38 UTC 
Created attachment 1623534 [details]
File: cpuinfo
Comment 4 Pat Kelly 2019-10-08 17:21:39 UTC 
Created attachment 1623535 [details]
File: dso_list
Comment 5 Pat Kelly 2019-10-08 17:21:40 UTC 
Created attachment 1623536 [details]
File: environ
Comment 6 Pat Kelly 2019-10-08 17:21:41 UTC 
Created attachment 1623537 [details]
File: limits
Comment 7 Pat Kelly 2019-10-08 17:21:44 UTC 
Created attachment 1623538 [details]
File: maps
Comment 8 Pat Kelly 2019-10-08 17:21:45 UTC 
Created attachment 1623539 [details]
File: mountinfo
Comment 9 Pat Kelly 2019-10-08 17:21:46 UTC 
Created attachment 1623540 [details]
File: open_fds
Comment 10 Pat Kelly 2019-10-08 17:21:47 UTC 
Created attachment 1623541 [details]
File: proc_pid_status
Comment 11 Adam Williamson 2019-10-08 22:25:54 UTC 
Did this crash show up at the same time as the Shell crash? This one looks like it might have been caused simply by the Shell unexpectedly disappearing underneath the applet (note error "The Wayland connection broke. Did the Wayland compositor die?" in the backtrace).
Comment 12 Pat Kelly 2019-10-13 15:34:59 UTC 
I think firewall-applet has it's own problem. There were no more gnome-shell crashes, but I did not get the connection notification on any subsequent restarts. I am now testing the 1012 drop and have had no gnome-shell crashes, but firewall-applet does not frovide the connection notification. The System Monitor application shows firewall applet loaded with a PID, normal priority with 25.9MB memory. I looked at firewall configuration to see if there is now a setting to activate the applet, but there doesn't seem to be anything like that.
Comment 13 Pat Kelly 2019-10-15 22:30:48 UTC 
The problem as described in comment 12 above still persists in the 1015 drop.
Comment 14 Adam Williamson 2019-10-16 00:13:24 UTC 
If it's not actually crashing, then we should probably track that separately. Are you sure if the applet has *ever* worked in GNOME Shell, or at least recently? If it's a panel applet that just follows the old FDO standards, I'm not sure if those are actually handled at all in current GNOME Shell. It might be worth seeing if it works in Xfce or something...
Comment 15 Pat Kelly 2019-10-16 12:55:36 UTC 
Yes, the firewall applet has worked fine under gnome for many Fedora releases now. F30 is running on the PCs here with Gnome as the desktop. I just ran updates on the PCs and after the updates there is a restart. When the PC's are coming back up the firewall-applet presents a notification about the network connection being made successfully. Under F29 the applet also put an icon in the top bar where you could initiate various actions in regard to the firewall. In F30 that icon is no longer present, but it still provides the connection notification.

I will download the F31 Xfce and try it. I have no familiarity with Xfce so it might take a while.
Comment 16 Adam Williamson 2019-10-16 15:04:37 UTC 
Don't worry, it's not necessary any more - if the notification worked in F30 I'd expect it to still work in F31. So, can you file a separate bug for that, assuming you're not still getting crash notifications for the daemon? Thanks!
Comment 17 Pat Kelly 2019-10-16 20:01:53 UTC 
Sorry for taking so long. I installed F31 Xfce on my test machine. Then I installed the firewall-applet. The applet worked great! I got the connection notification on restart or power up start. I also got the icon in the top bar that provides the left and right click actions someone might want to do quickly in regard to the firewall. So it would seem that the firewall-applet works fine in a friendly environment. I'll file a new bug.
Comment 18 Pat Kelly 2019-10-16 20:25:57 UTC 
This bug should be closed not reference no RHBA Bug#1762485
Comment 19 Pat Kelly 2020-01-05 16:45:35 UTC 
I think this bug should be closed. If I haven't heard different in a week, I will go ahead and close it.
Comment 20 Pat Kelly 2020-01-06 15:30:32 UTC 
This bug is being closed in favor of RHBZ # 1762485.

*** This bug has been marked as a duplicate of bug 1654802 ***