Bug 213147 - x11/mate: Session crashes when moving Chromium windows around in a VNC remote connection
Summary: x11/mate: Session crashes when moving Chromium windows around in a VNC remote...
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-01 23:53 UTC by ccradu
Modified: 2018-09-11 23:12 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (gnome)

Attachments
dmesg log (5.89 KB, text/plain)
2016-10-01 23:53 UTC, ccradu 		no flags Details
X log (31.07 KB, text/plain)
2016-10-01 23:54 UTC, ccradu 		no flags Details
X configuration (1.12 KB, text/plain)
2016-10-01 23:54 UTC, ccradu 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ccradu 2016-10-01 23:53:21 UTC 
Created attachment 175346 [details]
dmesg log

I installed MATE 1.12 inside the latest TrueOS snapshot (2016-09-29-x64, from http://download.trueos.org/master/amd64/
The, when I connect to a MATE session over VNC, the session crashes when moving the Chromium window around with the mouse.
Initially this happened on a Skylake i5 PC, but I could reproduce in VirtualBox as well (see below).

Steps to reproduce:
- Install TrueOS in VirtualBox using TrueOS-Desktop-2016-09-29-x64-DVD.iso
- Enable VNC in Login Manager Settings, enable port 5900 in firewall
- Install MATE and Chromium
- Connect to the MATE session over VNC
- Open Chromium, move the window with the mouse
- Result: Session crashes

Attached are dmesg and X logs and X config file.
Comment 1 ccradu 2016-10-01 23:54:01 UTC 
Created attachment 175347 [details]
X log
Comment 2 ccradu 2016-10-01 23:54:27 UTC 
Created attachment 175348 [details]
X configuration
Comment 3 ccradu 2016-10-01 23:56:15 UTC 
Relevant X log section:
[   402.050] (EE) Bus error at address 0x4cc76d
[   402.050] (EE) 
Fatal server error:
[   402.050] (EE) Caught signal 10 (Bus error). Server aborting
[   402.050] (EE) 
[   402.050] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   402.050] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   402.050] (EE) 
[   402.428] (EE) Server terminated with error (1). Closing log file.
Comment 4 Carlos J. Puga Medina freebsd_committer freebsd_triage 2018-08-26 16:15:58 UTC 
Can you reproduce this issue with Mate 1.20?