This also happens if you run a shell in screen, then log out of gnome
(the shell is detached from) log back in, reattach to the shell and try
to run meld from that shell. Most anything else will run just fine.
There must be some stale environment variables or something like that cause
problems
[Expired for meld (Ubuntu) because there has been no activity for 60
days.]
** Changed in: meld (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/269787
** Changed in: meld (Ubuntu)
Status: Invalid = Confirmed
** Changed in: meld (Ubuntu)
Status: Confirmed = Incomplete
--
meld crashed with GError in __init__()
https://bugs.launchpad.net/bugs/269787
You received this bug notification because you are a member of Ubuntu
Bugs, which
I didn't mean won't fix nor do I believe that the numerous ways of
getting to the root user that I listed are workarounds. Tools like
gksudo exist *explicitly* to account for the cases like this where the
environment needs to be taken care of - which the venerable su
doesn't.
--
meld crashed
Works fine (on Maverick Meerkat) when using gksudo, sudo -i, sudo
su and sudo su -. As per https://help.ubuntu.com/community/RootSudo
gksudo is preferred.
As such, marking as Invalid.
** Changed in: meld (Ubuntu)
Status: Incomplete = Invalid
--
meld crashed with GError in __init__()
I got an update regarding this bug being modified and, although I don't
care about it any more really, I must comment.
The bug is about a *crash* when starting a program from a terminal as
user root. Since when does the existence of a workaround make a bug
invalid?
I assume you mean won't fix -
I recently ran into this problem, and there's a workaround. Turns out,
changing to root with 'su -' instead of 'su' allows meld to work...
--
meld crashed with GError in __init__()
https://bugs.launchpad.net/bugs/269787
You received this bug notification because you are a member of Ubuntu
Bugs,
OK. Luckily, I have recently (last weekend) reverted to 8.10 from 9.04.
Things did not work out ...
So - I have dbus-x11 version (already present) :
1.2.4-0ubuntu1
Up to date 8.10 intrepid.
Open a terminal
su (become root)
meld /etc/network/interfaces /etc/network/interfaces
CRASH
waiting for info from the original opener of the bug report
** Changed in: meld (Ubuntu)
Status: New = Incomplete
--
meld crashed with GError in __init__()
https://bugs.launchpad.net/bugs/269787
You received this bug notification because you are a member of Ubuntu
Bugs, which is
is the package named dbus-x11 is installed ?
if not, retry after installing it, this seemed to fix a similar bug in fedora
--
meld crashed with GError in __init__()
https://bugs.launchpad.net/bugs/269787
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Visibility changed to: Public
--
meld crashed with GError in __init__()
https://bugs.launchpad.net/bugs/269787
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
11 matches
Mail list logo
