Using Zenity in conjuntion with workspace switch command causes segmentation fault in budgie-wm

Bug #1735917 reported by Tom Holmes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zenity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu Release: 17.04 with Budgie-Remix installed
Zenity Version: 3.24.0-0ubuntu1
Wmctrl Version: 1.07-7

When using wmctrl or zenity separately, they both work fine. Put them together however and budgie window manager crashes with a segmentation fault.

This happens using both "wmctrl -s 0" and "xdotool set_desktop 0". They work fine on their own but not in combination with Zenity.

Expected Result: Running the script from workspace 0 switches to workspace 3 and opens firefox. Running again prompts the user to ask if they're sure, then switches back to workspace 0 if they click yes.

Actual Result: Running the script from workspace 0 switches to workspace 3 and opens firefox. Running again prompts the user to ask if they're sure, then budgie window manager crashes with a segmentation fault if they click yes.

Code to replicate:

    #!/bin/bash

    desktop=$(xdotool get_desktop) #Get current workspace id

    if [ "${desktop}" -eq 0 ] #If workspace == 0
    then
      wmctrl -s 3 #Switch to workspace 3
      firefox --new-window "http://www.reddit.com"
    else
        zenity --question --title "Switch Workspace?" --text "Are you sure you wish to return to previous workspace?"
        if ! $? #If response Yes
        then
          wmctrl -s 0 #Switch back
        else
          notify-send "Operation Aborted" "User canceled workspace return."
        fi
    fi

Example of working code when `wmctrl` command is used alone:

    #!/bin/bash

    desktop=$(xdotool get_desktop) #Get current workspace id

    if [ "${desktop}" -eq 0 ] #If workspace == 0
    then
      wmctrl -s 3 #Switch to workspace 3
      firefox --new-window "http://www.reddit.com"
    else
      wmctrl -s 0 #Switch back
    fi

Log file:

    Dec 02 11:17:54 main budgie-wm.desktop[20079]: Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp
    Dec 02 11:17:54 main kernel: budgie-wm[20079]: segfault at 18 ip 00007fa255e8dfc1 sp 00007fff13189710 error 4 in libmutter-0.so.0.0.0[7fa255df0000+131000]
    Dec 02 11:17:55 main gnome-session-binary[19810]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
    Dec 02 11:17:55 main gnome-session[19810]: gnome-session-binary[19810]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
    Dec 02 11:17:55 main ckb.desktop[20137]: QXcbConnection: XCB error: 148 (Unknown), sequence: 423, resource id: 0, major code: 140 (Unknown), minor code: 20
    Dec 02 11:17:56 main budgie-wm[21537]: invalid (NULL) pointer instance
    Dec 02 11:17:56 main budgie-wm[21537]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

Tags: zesty
Tom Holmes (thaibossaw)
summary: - Using wmctrl with zenity prompt causes budgie-wm segmentation fault
+ Switching workspaces via bash with zenity prompt causes budgie-wm
+ segmentation fault
description: updated
Tom Holmes (thaibossaw)
summary: - Switching workspaces via bash with zenity prompt causes budgie-wm
- segmentation fault
+ Using Zenity in conjuntion with workspace switch command causes
+ segmentation fault in budgie-wm
tags: added: zesty
Revision history for this message
dino99 (9d9) wrote :
Changed in zenity (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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