'Open in terminal' from the nautilus right-click menu fails

[Bowmore]

Open a gnome-terminal from the desktop right-click menu causes it to crash.
The terminal window opens just to immediately crash.
No crash report generated.

Open the gnome-terminal from the unity dash or via Alt-F2 works fine.

This bug is present after the upgrade to
- glib2.0 version 2.33.12-3
- glib-networking version 2.33.12-0ubuntu1

Downgrading those to
- glib2.0 version 2.33.10-0ubuntu3
- glib-networking version 2.33.10-0ubuntu1
makes nautilus-open-terminal work again from the right-click menu.

Same issue on two different quantal installs.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: nautilus-open-terminal 0.19-2build2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Thu Sep 6 13:24:58 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus-open-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

[Bowmore (bowmore)]

The upgrade concerned above is for the glib2.0 packages.
Thus, nautilus-open-terminal need to be updated to the latest glib2.0.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Peter Würtz (pwuertz)]

This affects any opened terminal from the nautilus context menu, right?

[Bowmore (bowmore)]

Not really, It's only related to nautilus-open-terminal.

Using a nautilus script works
Using nautilus actions is said to work

[Doug McMahon (mc3man)]

I believe you MAY need to have the extension rebuild, but not with the current glib. If doing so it will still fail (tested here
However on my custom install that has a newer glib & nautilus there was no issue - after a rebuild the ext. works fine

Taking a bit of a guess I think the ext. may be side affected by this bug
Bug 1051447
or more specifically the upstream bug

As a test I rebuilt the current 12.10 nautilus source against a newer glib, then rebuilt this ext. It now works fine.

For this test I used the glib packages in https://launchpad.net/~ricotz/+archive/testing

What I didn't test & should of, would the current ext. work with the upgraded glib?, Can do that in a bit..

[Doug McMahon (mc3man)]

Just to follow up -
It appears no rebuild of nautilus or the extension is needed, just the upgraded (bug fixed) glib
That should be easy to confirm by anyone by upgrading their glib to at least the packages in the ppa mentioned above
(if trying I'd just upgrade the libglib2.0-* packages

[Felix Möller (felix-derklecks)]

I can confirm. Installing
libglib2.0-0_2.33.13+git20120915.ac7dcd81-0ubuntu1~12.10~ricotz0_amd64.deb
libglib2.0-bin_2.33.13+git20120915.ac7dcd81-0ubuntu1~12.10~ricotz0_amd64.deb
solves the issue for me.

You have to run killall nautilus once after that.

[Bowmore (bowmore)]

Confirming this too.
This ricotz glib2.0 source package solves the issue.
glib2.0 2.33.13+git20120915.ac7dcd81-0ubuntu1~12.10~ricotz0

Confirmed by upgrading the following three packages:
libglib2.0-0
libglib2.0-bin
libglib2.0-dev

[Doug McMahon (mc3man)]

I have a set of the current repo glib source packages patched only for the "Fix regression in g_shell_parse_argv()" glib bug & it fixes this issue.
Specifically as seen here
http://bazaar.launchpad.net/~registry/glib/trunk/revision/12621
Apparently it causes a range of misbehavior, so this really the same as the glib bug noted in comment 6

[Jeremy Bícha (jbicha)]

It seems that this bug was fixed with glib2.0 2.33.14-1 so I'm going to go ahead and close this bug.

[alfredo (alacis)]

This still occurs. The failure appears connected to WINE.

I could launch a terminal ok, until I installed WINE: now it occurs always.

> uname -a
Linux DarkMatter 3.16.0-77-generic #99~14.04.1-Ubuntu SMP Tue Jun 28 19:17:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[Doug McMahon (mc3man)]

Start a new bug, this one is closed

On 09/12/2016 07:46 PM, alfredo wrote:
> This still occurs. The failure appears connected to WINE.
>
> I could launch a terminal ok, until I installed WINE: now it occurs
> always.
>
>> uname -a
> Linux DarkMatter 3.16.0-77-generic #99~14.04.1-Ubuntu SMP Tue Jun 28 19:17:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>