gnome-shell crashed with signal 5 in g_log_default_handler()

Bug #1761910 reported by Jack Peterson on 2018-04-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)

Bug Description

I plugged in my third display.

echo "setting frame buffer" &&
xrandr --fb 12800x2880 &&
echo "setting laptop monitor" &&
xrandr --output eDP-1-1 --mode 3840x2160 --rate 60 --pos 0x0 --primary &&
echo "setting 27 inch monitor" &&
xrandr --output DP-0.2 --mode 2560x1440 --scale-from 5120x2880 --panning 5120x2880+3840+0 --pos 3840x0 &&
echo "setting the samsung monitor" &&
xrandr --output DP-0.1 --mode 1920x1080 --scale-from 3840x2160 --panning 3840x2160+8960+0 --pos 8960x0 &&
echo "setting global scaling to 2x" &&
gsettings set org.gnome.desktop.interface scaling-factor 2
cat <<EOF >~/.config/monitors.xml
<monitors version="2">
          <product>ASUS PB278</product>

is my display configuration. Three screens. Third is problematic in Linux.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Apr 6 18:41:52 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell

InstallationDate: Installed on 2018-03-28 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
ProcCmdline: /usr/bin/gnome-shell
 PATH=(custom, no user)
Signal: 5
SourcePackage: gnome-shell
 ?? () from /lib/x86_64-linux-gnu/
 g_log_default_handler () from /lib/x86_64-linux-gnu/
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/
 g_log () from /lib/x86_64-linux-gnu/
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: No upgrade log present (probably fresh install)

Jack Peterson (jack-peterson) wrote :

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers