** Changed in: unity (Ubuntu)
Status: Invalid = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the
This is most likely not related to Unity, for the same problem occurs
for me with Linux Mint 13 XFCE.
If gedit is started from terminal (just gedit, no arguments passed), it
doesn't show up, nothing is printed in terminal and thus effectively hangs in
limbo. Task Manager sees it sitting around
I've had the exact same problem since I upgraded from 12.04 to 12.10!
I've never had it before and I've been using Ubuntu since v4 with heavy
usage of gedit!!!...I can confirm all of this:
gedit 3.6.1
-open just fine when launched from Unity or the terminal
-opens the second time when
For me the problem is still present in 12.04 fully upgraded so far.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the
Bug is still present in precise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
Fix Released
For me, this problem went away after upgrade to 12.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in
Problem was fixed in 12.04 for me as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
I'm still unable to reproduce, so marking as fix released.
** Changed in: unity-2d
Status: Confirmed = Fix Released
** Changed in: unity-2d
Milestone: 5.8 = None
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in
Is this issue going to be fixed in 11.10? I still have the issue and I
install any available updates daily.
(Using Ubuntu 11.10 AMD64 Unity3D)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
Thanks for the comments Vadim Jorge!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
Fix
Gerry, I had this problem in 11.10 (comment #30), but I just installed
Precise Beta 1 and can't reproduce anymore too. Seems to be fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
About comment #36: in both cases i ran unity-2d.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in
Running Precise, I'm unable to reproduce this bug. Can anyone else using
Precise confirm?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first
Can't reproduce in Unity-2d 5.4.0-0ubuntu1 via steps from comment #25
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the
** Changed in: unity-2d
Milestone: 5.2.1 = 5.6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in
I got tired of waiting for this to be fixed, so I implemented a
workaround.
I moved the gedit binary to gedit.bin, then I created a shell-script
named gedit that calls gedit.bin with the --standalone option:
% mv /usr/bin/gedit /usr/bin/gedit.bin
% vi /usr/bin/gedit
#!/bin/sh
/usr/bin/gedit.bin
** Changed in: unity-2d
Importance: Undecided = High
** Changed in: unity-2d
Milestone: None = 5.2.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to
Thanks for all your comments. I can see how this is unfuriating. I'm
using today's trunk on Precise, and I'm not seeing this problem, but
perhaps I'm not doing the correct thing. I will investigate more.
We added the fix mentioned above (see bug 873027) on 12 Oct, but that
was too late for
I have this problem on 11.10 with unity 2d
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
Reporting a bug in Ubuntu is like trying to have a serious conversation
with /dev/null
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try,
** Changed in: unity-2d
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in
This is NOT fixed. Still an issue in ubuntu 11.10 with all the updates
up to date.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but
It´s still here on Unity-2D.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
Fix Released
I still have this in Unity 2D as well, in Precise, still as described in
bug 808918. (I haven't tested in Oneiric in a while.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Because it seems like this only happens to Unity 2D users, I added Unity
2D to affected list.
** Also affects: unity-2d
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
Similar bug 808918 has been marked as a duplicate of this bug, but the
behavior is a bit different and it persists even though this bug has
been fixed (it seems reliably reproducible on a fully updated Precise
system), so I suspect that it is not really a duplicate. I have
commented in bug 808918
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
Fix
** Tags added: iso-testing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
Fix Released
** Also affects: unity-lens-files (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try,
** Branch linked: lp:~ubuntu-desktop/unity-lens-files/ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
This bug was fixed in the package unity-lens-files - 0.6.10-0ubuntu1
---
unity-lens-files (0.6.10-0ubuntu1) oneiric; urgency=low
* New upstream release.
- Unity's files lens fails to mount bookmarked remote shares (LP: #760309)
- gedit fails to start on first try, but does
** Branch linked: lp:ubuntu/unity-lens-files
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in Unity:
** Changed in: unity
Status: Fix Committed = Fix Released
** Changed in: unity-lens-applications
Status: Fix Committed = Fix Released
** Changed in: unity-lens-files
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of
fwiw - i bet this behavioral change is related to gedit recently
switching from a dbus-glib based single-instancing to a GApplication
based one.
** Also affects: unity-lens-files
Importance: Undecided
Status: New
** Changed in: unity-lens-files
Importance: Undecided = High
**
** Branch linked: lp:unity-lens-files
** Branch linked: lp:unity-lens-applications
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but
I added the following to both apps and files lenses and now everything
starts as it should. Thanks to Michael Terry for debugging :-)
+/* Sub processes inheriting our environment may be confused if they
+ * see a starter bus set */
+Environment.unset_variable (DBUS_STARTER_ADDRESS);
+
** Also affects: unity-lens-applications (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu Oneiric)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
** Changed in: unity-lens-files
Status: Confirmed = Fix Committed
** Changed in: unity-lens-files
Milestone: None = 0.6.10
** Changed in: unity-lens-files
Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: unity
Status: Confirmed = Fix Committed
** Branch linked: lp:~ubuntu-desktop/unity-lens-applications/ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the
This bug was fixed in the package unity-lens-applications -
0.4.10-0ubuntu2
---
unity-lens-applications (0.4.10-0ubuntu2) oneiric; urgency=low
* Cherry-pick from upstream:
- gedit fails to start on first try, but does on the second (LP: #827414)
-- Didier Roche
I suppose this is not a gedit bug, as it starts up just fine from a
terminal.
** Changed in: gedit (Ubuntu Oneiric)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
** Branch linked: lp:ubuntu/unity-lens-applications
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in
@Michael: I don't see DBUS_STARTER_ADDRESS set here. I tried starting a
gnome-terminal from both the launcher and the dash...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
Sorry Michael, Seb just taught me on IRC to use 'strings /proc/$(pidof
gedit)/environ | grep DBUS', and lo and behold, my gedit *does* have the
starter address set.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
Seems like it has something to do with unity or how unity is starting
gedit at least, Mikkel it seems you started looking at it, do you want
to own the bug for the unity team? ;-) If not feel free to unassign or
reassign to somebody else in dx
** Changed in: unity (Ubuntu Oneiric)
Status:
#848631 is a duplicate. I made a comment in there that may or may not
be relevant:
In a terminal, run gedit. Nothing will happen. Then, in a second
terminal, run gedit again. Now a window pops up. The interesting thing
is the second instance exited immediately. The first instance is still
Looking at the DBus spec [1], DBUS_STARTER_ADDRESS is used when auto-
launching DBus services. So this is arguably reasonable behavior on
gedit's part, and it's confusing for applications that Unity will have
that variable set for its subprocesses.
I would argue the best fix is for Unity to
(forgot to add) ... and *only* for gedit, correct?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does on the second
Status in
Can everyone confirm that this only happens when using alt-f2, and *not*
when using the normal dash (ie. hit super and type 'gedit'). That's
the behavior I am seeing here at least.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in
correct - when trying to open gedit from Alt+F2 it only opens opens every
other time
(same as when trying to open a text file from the files lens which defaults to
gedit, if switched to another default editor then no issue in the lens
--
You received this bug notification because you are a
I can reproduce this quite easily:
1) Press Alt + F2, type gedit, press Enter
2) if gedit opens, close it
3) jump to 1)
It really works only every other time. The curious thing is that if I
kill unity-applications-daemon, and start it from the console, then the
Dash always succeeds in launching
Just to add - from the files folder lens - it's exactly every other
time here, starting with doesn't, does. doesn't does, ect.
The only exception to that is if another file is open in gedit, whether
on the same or a different workspace
--
You received this bug notification because you are a
I have not experienced this in about a month. The launchpad/console
issue is fixed, but the problem appears to have mutated. as stated above
the dash is starting gedit as a server. The window will not appear until
another instance is started either by running gedit or choosing a
document that will
** Changed in: gedit (Ubuntu Oneiric)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
Title:
gedit fails to start on first try, but does
As of my updates this morning, gedit is starting correctly from the
terminal and the launcher. I think this issue was caused by a
combination of libs that have changed. This is fixed for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
55 matches
Mail list logo
