GNOME Bugzilla – Bug 658100
With elevated privileges, gedit opens an existing file and an untitled document in a new tab.
Last modified: 2012-07-31 16:08:26 UTC
Reproducable via terminal. gksudo gedit /etc/apt/sources.list It opens the requested file and beside an untitled document in a new tab. Expected. Only open the requested file. ## Above behaviour doesn't occur with regular user permissions via terminal and previous version of gedit 2.30.4. e.g. gedit /home/<user>/documents/<file> Bug reported there first. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/838404
You shouldn't start GNOME programmes with elevated privileges, it's not supported. In any case, not a gnome-terminal bug.
Is this bug a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=653563 ?
(In reply to comment #1) > You shouldn't start GNOME programmes with elevated privileges, it's not > supported. In any case, not a gnome-terminal bug. As a user of this program for over a decade, and not experiencing this problem until V3.0.x, AND not being a corporate user (I use Linux at home, and ALWAYS log in as root, because I am tired of typing my password literally every time I want to do something in MY computer.), I am very disturbed at your statement that elevated users should not be using the editor. Text editors are mandatory at ALL levels! Since when do YOU feel that you have to dictate how others use their computers? SE Linux is available to drive the security in a system, and admins are capable of setting rights to, disabling, and even uninstalling it. Instead of blowing people off, why not do something constructive, and either assign the problem to someone who actually cares about it, or just not post such derogatory statements. I also posted a comment on the original bug report (id=653563), that I experience the problem in all levels. Not just root, or high level log-ins.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 653563 ***