Bug 1289488

Summary: Can't launch gnome-terminal
Product: [Fedora] Fedora Reporter: Giulio 'juliuxpigface' <juliux.pigface>
Component: gnome-terminalAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: debarshir, mclasen, zeenix
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-08 10:02:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Giulio 'juliuxpigface' 2015-12-08 09:48:32 UTC
Description of problem:
I'm testing the 20151204 Rawhide: I can't launch gnome-terminal from the desktop Overview.


Launching it from lxterminal, results in:
"Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Errore nel chiamare StartServiceByName per org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 10"

"Errore nel chiamare StartServiceByName" could be translated as "Error in issuing/calling StartServiceByName"


Version-Release number of selected component (if applicable):
gnome-terminal-3.18.2-1.fc24.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Clean boot the system and log in to a Gnome+Wayland session
2.Try to launch gnome-terminal from Gnome Shell's Overview.

Actual results:
1.The icon on the panel loops, but the app doesn't actually start

Expected results:
1.gnome-terminal should be successfully available

Additional info:
It's a Gnome+Wayland session and the system is a qemu-kvm guest

Comment 1 Giulio 'juliuxpigface' 2015-12-08 10:02:13 UTC
I'm closing this. I found an already reported bug. Sorry for the duplicate.

*** This bug has been marked as a duplicate of bug 1281675 ***