swaywm / sway

i3-compatible Wayland compositor
https://swaywm.org
MIT License
14.66k stars 1.11k forks source link

Firefox crashes with SIGSEGV #977

Closed L-as closed 7 years ago

L-as commented 7 years ago

Tested both nightly aurora and standard. Only happens on sway, also tested on GNOME with wayland.

ddevault commented 7 years ago

Unable to reproduce. Please provide more information:

rosekunkel commented 7 years ago

This happens to me as well on Arch Linux. It crashes in sway but not orbment.

Versions

sway --version:

sway version (2016-10-25, branch "")

wlc version: 0.0.7-1

Steps to reproduce

  1. run sway
  2. open a terminal
  3. run firefox or firefox --safe-mode

The only output I get is

Segmentation fault (core dumped)

Firefox stack trace

I'm not sure how to get a useful stack trace from Firefox. I got this by just running under gdb but it seems to be missing a lot of symbols:

stacktrace.txt

Sway config file

Basically the default config but with HiDPI settings and a different terminal:

# Default config for sway
#
# Copy this to ~/.config/sway/config and edit it to your liking.
#
# Read `man 5 sway` for a complete reference.

### Variables
#
# Logo key. Use Mod1 for Alt.
set $mod Mod4
# Home row direction keys, like vim
set $left h
set $down j
set $up k
set $right l
# Your preferred terminal emulator
set $term roxterm
# Your preferred application launcher
set $menu dmenu_run

### Output configuration
#
# Default wallpaper (more resolutions are available in /usr/share/sway/)
output * bg /usr/share/sway/Sway_Wallpaper_Blue_1920x1080.png fill
#
# Example configuration:
#
#   output HDMI-A-1 resolution 1920x1080 position 1920,0
#
# You can get the names of your outputs by running: swaymsg -t get_outputs
output WLC-1 scale 2
output eDP-1 scale 2

### Input configuration
#
# Example configuration:
#
#   input "2:14:SynPS/2_Synaptics_TouchPad" {
#       dwt enabled
#       tap enabled
#       natural_scroll enabled
#       middle_emulation enabled
#   }
#
# You can get the names of your inputs by running: swaymsg -t get_inputs
# The escape symbol "\" has to be removed.
# Read `man 5 sway-input` for more information about this section.

### Key bindings
#
# Basics:
#
    # start a terminal
    bindsym $mod+Return exec $term

    # kill focused window
    bindsym $mod+Shift+q kill

    # start your launcher
    bindsym $mod+d exec $menu

    # Drag floating windows by holding down $mod and left mouse button.
    # Resize them with right mouse button + $mod.
    # Despite the name, also works for non-floating windows.
    # Change normal to inverse to use left mouse button for resizing and right
    # mouse button for dragging.
    floating_modifier $mod normal

    # reload the configuration file
    bindsym $mod+Shift+c reload

    # exit sway (logs you out of your wayland session)
    bindsym $mod+Shift+e exit
#
# Moving around:
#
    # Move your focus around
    bindsym $mod+$left focus left
    bindsym $mod+$down focus down
    bindsym $mod+$up focus up
    bindsym $mod+$right focus right
    # or use $mod+[up|down|left|right]
    bindsym $mod+Left focus left
    bindsym $mod+Down focus down
    bindsym $mod+Up focus up
    bindsym $mod+Right focus right

    # _move_ the focused window with the same, but add Shift
    bindsym $mod+Shift+$left move left
    bindsym $mod+Shift+$down move down
    bindsym $mod+Shift+$up move up
    bindsym $mod+Shift+$right move right
    # ditto, with arrow keys
    bindsym $mod+Shift+Left move left
    bindsym $mod+Shift+Down move down
    bindsym $mod+Shift+Up move up
    bindsym $mod+Shift+Right move right
#
# Workspaces:
#
    # switch to workspace
    bindsym $mod+1 workspace 1
    bindsym $mod+2 workspace 2
    bindsym $mod+3 workspace 3
    bindsym $mod+4 workspace 4
    bindsym $mod+5 workspace 5
    bindsym $mod+6 workspace 6
    bindsym $mod+7 workspace 7
    bindsym $mod+8 workspace 8
    bindsym $mod+9 workspace 9
    bindsym $mod+0 workspace 10
    # move focused container to workspace
    bindsym $mod+Shift+1 move container to workspace 1
    bindsym $mod+Shift+2 move container to workspace 2
    bindsym $mod+Shift+3 move container to workspace 3
    bindsym $mod+Shift+4 move container to workspace 4
    bindsym $mod+Shift+5 move container to workspace 5
    bindsym $mod+Shift+6 move container to workspace 6
    bindsym $mod+Shift+7 move container to workspace 7
    bindsym $mod+Shift+8 move container to workspace 8
    bindsym $mod+Shift+9 move container to workspace 9
    bindsym $mod+Shift+0 move container to workspace 10
    # Note: workspaces can have any name you want, not just numbers.
    # We just use 1-10 as the default.
#
# Layout stuff:
#
    # You can "split" the current object of your focus with
    # $mod+b or $mod+v, for horizontal and vertical splits
    # respectively.
    bindsym $mod+b splith
    bindsym $mod+v splitv

    # Switch the current container between different layout styles
    bindsym $mod+s layout stacking
    bindsym $mod+w layout tabbed
    bindsym $mod+e layout toggle split

    # Make the current focus fullscreen
    bindsym $mod+f fullscreen

    # Toggle the current focus between tiling and floating mode
    bindsym $mod+Shift+space floating toggle

    # Swap focus between the tiling area and the floating area
    bindsym $mod+space focus mode_toggle

    # move focus to the parent container
    bindsym $mod+a focus parent
#
# Scratchpad:
#
    # Sway has a "scratchpad", which is a bag of holding for windows.
    # You can send windows there and get them back later.

    # Move the currently focused window to the scratchpad
    bindsym $mod+Shift+minus move scratchpad

    # Show the next scratchpad window or hide the focused scratchpad window.
    # If there are multiple scratchpad windows, this command cycles through them.
    bindsym $mod+minus scratchpad show
#
# Resizing containers:
#
mode "resize" {
    # left will shrink the containers width
    # right will grow the containers width
    # up will shrink the containers height
    # down will grow the containers height
    bindsym $left resize shrink width 10 px or 10 ppt
    bindsym $down resize grow height 10 px or 10 ppt
    bindsym $up resize shrink height 10 px or 10 ppt
    bindsym $right resize grow width 10 px or 10 ppt

    # ditto, with arrow keys
    bindsym Left resize shrink width 10 px or 10 ppt
    bindsym Down resize grow height 10 px or 10 ppt
    bindsym Up resize shrink height 10 px or 10 ppt
    bindsym Right resize grow width 10 px or 10 ppt

    # return to default mode
    bindsym Return mode "default"
    bindsym Escape mode "default"
}
bindsym $mod+r mode "resize"

#
# Status Bar:
#
# Read `man 5 sway-bar` for more information about this section.
bar {
    position top
    colors {
        statusline #ffffff
        background #323232
        inactive_workspace #32323200 #32323200 #5c5c5c
    }
}

# You may want this:
#
# include ~/.config/sway/conf.d/*
#
# Protip:
#
# include ~/.config/sway/`hostname`/*

Notes

I saw this same behavior when trying to run firefox under weston without enabling xwayland. I've also been having issues running other X applications (google chrome, emacs), so it may be that xwayland is not working correctly.

ddevault commented 7 years ago

What happens if you try it without hidpi?

L-as commented 7 years ago

Given that I used the default config and had the exact same symptoms and issues, I'm pretty sure it's not because of HiDPI.

Den 23/12/2016 17.28 skrev "Drew DeVault" notifications@github.com:

What happens if you try it without hidpi?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SirCmpwn/sway/issues/977#issuecomment-269014087, or mute the thread https://github.com/notifications/unsubscribe-auth/AVDX0L4HfB9hQ18d_8L1SDR_zre41L-iks5rK_bBgaJpZM4K9jGn .

rosekunkel commented 7 years ago

I see the same behavior with and without HiDPI.

ddevault commented 7 years ago

Can you provide a sway log as well, and a firefox core dump?

rosekunkel commented 7 years ago

Sway log: swaylog.txt Firefox core dump: coredump.zip

ddevault commented 7 years ago

Thanks. Will have a look when I get the chance.

ddevault commented 7 years ago

Firefox version?

rosekunkel commented 7 years ago

Firefox version is 50.1.0

rosekunkel commented 7 years ago

I just updated to the latest version of sway from the Arch repos and can confirm that this still happens with sway version sway version (2016-12-27, branch "").

Timidger commented 7 years ago

Not sure how much help this is, but running Firefox 50.1.0 on my Arch machine, with wlc v0.0.7 does not break on either Sway or Way Cooler. Given it happens with other X apps, probably an XWayland / other non-wlc environment issue.

rosekunkel commented 7 years ago

@Timidger I just tried out Firefox on Way Cooler and it ran fine. I think it is some sort of issue specifically with Sway and XWayland, but I have no idea how to go about diagnosing that. Do you have any suggestions?

Timidger commented 7 years ago

Hmmmm I'm not sure. Potentially Sway is doing something extra with X apps, or setting some flags firefox doesn't like but only @SirCmpwn can say for sure. The logs don't say much unfortunately.

ddevault commented 7 years ago

All I'm going to do when I have the spare time is grab that core dump and debug firefox. Anyone else could do that, too.

hesiod commented 7 years ago

@wkunkel: Have you set GDK_BACKEND to wayland (as suggested in the sway wiki)? Firefox segfaults on my machine if I try to run without GDK_BACKEND=x11, I think its simply because Firefox doesn't support Wayland yet.

rosekunkel commented 7 years ago

@hesiod I haven't set GDK_BACKEND to anything, although I did try setting it to wayland temporarily when I was first troubleshooting. Running Sway as GDK_BACKEND=x11 sway does seem to allow Firefox to run. Unfortunately it also forces every other GTK app to run through X, even those which support Wayland directly. Trying to just run Firefox as GDK_BACKEND=x11 firefox while in Sway doesn't work. I guess this leaves two questions:

ddevault commented 7 years ago

Do you still experience this?

L-as commented 7 years ago

Nope

soredake commented 7 years ago

@SirCmpwn for me it's still crashing (torbrowser 7.0.6), i'll wait for wlroots to replace wlc and then re-test.