xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()

Bug #1785143 reported by Spass on 2018-08-02
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Xfwm4
Confirmed
Medium
xfce4-settings (Ubuntu)
Medium
Unassigned

Bug Description

I was changing some options in the Window Manager settings (xfwm4 4.13.1). It started behaving strangely - when I clicked somewhere in the Window Manager settings window it brought me back to the main settings window, I clicked on Window Manager icon, WM settings window showed up and the crash report opened.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xfce4-settings 4.13.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Aug 3 00:59:43 2018
ExecutablePath: /usr/bin/xfce4-settings-manager
InstallationDate: Installed on 2018-08-01 (1 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180801)
ProcCmdline: xfce4-settings-manager
SegvAnalysis:
 Segfault happened at: 0x7f088d2db1ed <gtk_drag_finish+29>: mov (%rbx),%rdx
 PC (0x7f088d2db1ed) ok
 source "(%rbx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-settings
StacktraceTop:
 gtk_drag_finish () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Spass (malysps) wrote :
information type: Private → Public

StacktraceTop:
 gtk_drag_finish (context=0x8, success=0, del=0, time=6) at ../../../../gtk/gtkdnd.c:961
 gtk_drag_drop_finished (info=0x560a3ecfbd60, result=result@entry=GTK_DRAG_RESULT_TIMEOUT_EXPIRED, time=<optimized out>) at ../../../../gtk/gtkdnd.c:2593
 gtk_drag_abort_timeout (data=<optimized out>) at ../../../../gtk/gtkdnd.c:3265
 gdk_threads_dispatch (data=0x560a3ea53f20, data@entry=<error reading variable: value has been optimized out>) at ../../../../gdk/gdk.c:755
 g_timeout_dispatch (source=source@entry=0x560a3ecdeac0, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4650

Changed in xfce4-settings (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
In , Spass (malysps) wrote :

Created attachment 7885
terminal output

Hello, I'm testing Xubuntu 18.10 with xfwm4 4.13.1 installed in VirtualBox VM. I have an issue with xfwm4-settings (opened separately and within the xfce4-settings-manager) window crashing when I change the button layout, just by dragging it's elements.

There are some issues with "gtk_widget_size_allocate" and most important:
xfwm4-settings: ../../../../src/cairo-surface.c:1734: cairo_surface_mark_dirty_rectangle: Assertion `! _cairo_surface_has_mime_data (surface)' failed.
(full terminal output attached)

Besides the window closing/crashing, when I open Window Manager settings from Settings Manager (and only then) and when I change the button layout, the buttons are disappearing from that section (see here - https://ibb.co/mXtPBU ). Probably related to "gtk_widget_size_allocate".

In , Spass (malysps) wrote :

Also, this is my Launchpad bug report related to this issue, maybe it will be useful:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143

Changed in xfwm4:
importance: Unknown → Medium
status: Unknown → Confirmed
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1785143

tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.