option --new-window not working correctly

Bug #965510 reported by Mike L
60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Fix Released
Medium
Timothy Arceri
gedit
Fix Released
Medium
gedit (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gedit 3.3.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Mon Mar 26 13:02:15 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321)
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Mike L (mikerl) wrote :
Revision history for this message
Mike L (mikerl) wrote :
Revision history for this message
Mike L (mikerl) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

summary: - New Quicklists for Gedit not working correctly
+ option --new-window not working correctly
Changed in gedit (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue is with "gedit --new-window" running it from the command line does the same

it also prints those warnings

"** (gedit:17320): CRITICAL **: gedit_multi_notebook_get_active_tab: assertion `GEDIT_IS_MULTI_NOTEBOOK (mnb)' failed

(gedit:17320): Gtk-CRITICAL **: gtk_action_group_get_action: assertion `GTK_IS_ACTION_GROUP (action_group)' failed

(gedit:17320): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed"

Revision history for this message
Mike L (mikerl) wrote :

I don't yet have a Bugzilla account, but when I have free time, I'll get one (maybe this weekend), so I can report the bug upstream. If anyone else wants to report this bug to the GNOME team, go right ahead.

Revision history for this message
Mike L (mikerl) wrote :

I think I'll upload the bug to Gnome later today...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, let us know the bug number,url when you do!

Revision history for this message
Mike L (mikerl) wrote :

Just reported it. Here is the URL:
https://bugzilla.gnome.org/show_bug.cgi?id=673741
And the bug number is 673741.

Revision history for this message
Mike L (mikerl) wrote :

This bug is persisting in 3.4.1.

Changed in gedit:
importance: Undecided → Unknown
status: New → Unknown
Changed in gedit (Ubuntu):
status: Confirmed → Triaged
Changed in gedit:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Jakob (jodsalz2000-launchpad) wrote :

The same problem appears when I open a file in Gedit with gksu, eg. "gksu gedit /usr/share/applications/gedit.desktop". See screenshot. Using sudo is no problem, though.

Gedit 3.4.1-0ubuntu1
Unity 5.12-0ubuntu1.1
Ubuntu 12.04

Revision history for this message
Joonas Saarinen (jza) wrote :

This bug seems to be still present in gedit 3.4.2.

Changed in hundredpapercuts:
status: New → Confirmed
milestone: none → quantal-2-productivity
importance: Undecided → Medium
importance: Medium → Low
Changed in hundredpapercuts:
importance: Low → Medium
status: Confirmed → Triaged
assignee: nobody → Papercuts Ninja (papercuts-ninja)
Changed in hundredpapercuts:
milestone: quantal-2-productivity → raring-misc
assignee: Papercuts Ninja (papercuts-ninja) → Timothy Arceri (t-fridey)
Revision history for this message
Timothy Arceri (t-fridey) wrote :

Patch submitted upstream

Changed in hundredpapercuts:
status: Triaged → In Progress
Changed in hundredpapercuts:
status: In Progress → Fix Committed
Changed in gedit (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gedit - 3.6.1-0ubuntu3

---------------
gedit (3.6.1-0ubuntu3) raring; urgency=low

  * debian/patches/git_new_win_no_tab.patch:
    - don't create new instances with several tabs (lp: #965510)
 -- Sebastien Bacher <email address hidden> Mon, 12 Nov 2012 11:17:49 +0100

Changed in gedit (Ubuntu):
status: Fix Committed → Fix Released
Changed in hundredpapercuts:
status: Fix Committed → Fix Released
Revision history for this message
Timothy Arceri (t-fridey) wrote :

I'm not sure why this has been patched downstream in the 3.6 branch since upstream commited my patch to both master and 3.6

Revision history for this message
Sebastien Bacher (seb128) wrote :

> I'm not sure why this has been patched downstream in the 3.6 branch since upstream commited my patch to both master and 3.6

because there is no release with your patch out and the bug would have remained unfixed in Ubuntu until that happens

Changed in gedit:
status: New → Fix Released
Changed in hundredpapercuts:
milestone: raring-misc → raring-ee
Changed in hundredpapercuts:
milestone: app-descriptions → gedit
Revision history for this message
Jon Brase (jonathan-brase) wrote :

Is there any chance of this being fixed in Precise?

Looking at https://wiki.ubuntu.com/StableReleaseUpdates#When , it's not really a severe regression (2nd bullet point), but I believe it qualifies for "Obviously safe patch" and "Affects an application" (4th bullet point).

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

@Jon, could you please update the description with the information specified in the "Procedure" section of the SRU page https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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