seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

CRT does not disown properly #234

New Issue
Open
opened 2015-03-03 17:54:30 +01:00 by 7ranceaddic7 · 0 comments
7ranceaddic7 commented 2015-03-03 17:54:30 +01:00 (Migrated from github.com)
Copy Link

I have a small script which launches Glances into a pre-configured geometry terminal window. When I execute ./start-glances.sh from gnome-terminal, the script executes properly and disowns the new terminal, returning control of the launching terminal.

This does not occur in CRT. Instead, the new terminal remains a child process and I have provided with the following:

(gnome-terminal:17838): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call will probably stop working with a future version of glib.

If I close the Glances terminal or ^C, control is restore to CRT.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9159334-crt-does-not-disown-properly?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github).
I have a small script which launches Glances into a pre-configured geometry terminal window. When I execute ./start-glances.sh from gnome-terminal, the script executes properly and disowns the new terminal, returning control of the launching terminal. This does not occur in CRT. Instead, the new terminal remains a child process and I have provided with the following: (gnome-terminal:17838): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call will probably stop working with a future version of glib. If I close the Glances terminal or ^C, control is restore to CRT. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9159334-crt-does-not-disown-properly?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github). </bountysource-plugin>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#234
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?