Bug 1283213 - gnome-terminal won't start (DBus problem?)
Summary: gnome-terminal won't start (DBus problem?)
Keywords:
Status: CLOSED DUPLICATE of bug 1281675
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-18 13:09 UTC by Horst H. von Brand
Modified: 2015-12-04 22:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-04 22:03:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Horst H. von Brand 2015-11-18 13:09:50 UTC 
Description of problem:
Starting gnome-terminal from an xterm crashes:

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 10

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

How reproducible:
Always

Steps to Reproduce:
1. gnome-terminal
2.
3.

Actual results:

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 10

Expected results:
Usable gnome-terminal


Additional info:
Workaround is to install and use e.g. xterm
Comment 1 Michal Jaegermann 2015-11-19 02:24:13 UTC 
This "Error constructing proxy for org.gnome.Terminal:...." looks familiar from bug 1060388; but now possibly the reason is quite different.
Comment 2 Joachim Frieben 2015-11-19 07:24:01 UTC 
This is a duplicate of bug 1281675.
Comment 3 Adam Williamson 2015-12-04 22:03:09 UTC 

*** This bug has been marked as a duplicate of bug 1281675 ***
Note You need to log in before you can comment on or make changes to this bug.