bzr uncommit expects a display
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar GTK+ Frontends |
Fix Released
|
High
|
Jelmer Vernooij |
Bug Description
I was logged in remotely on my laptop.
I ran the following:
[thomas@otto object-views]$ bzr uncommit
25 Thomas Vander Stichele 2010-11-16 [merge]
add comment to clarify
The above revision(s) will be removed.
Are you sure [y/N]? y
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
local=local)
File "/usr/lib/
revno=revno, local=local)
File "/usr/lib/
hook_new_tip)
File "/usr/lib/
from bzrlib.plugins.gtk import commit
File "/usr/lib/
import gtk
File "/usr/lib/
_init()
File "/usr/lib/
_gtk.
RuntimeError: could not open display
bzr 2.0.5 on python 2.6.2 (Linux-
arguments: ['/usr/bin/bzr', 'uncommit']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.UTF-8'
plugins:
gtk /usr/lib/
launchpad /usr/lib/
netrc_
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
including this traceback and a description of the problem.
[thomas@otto object-views]$
I do not expect bzr to open a gui; if it tries to, it should gracefully fail and proceed to uncommit.
I suggest a unit/integration test suite that gets run without display under something like buildbot to catch this kind of stuff.
Changed in bzr-gtk: | |
status: | Triaged → Fix Released |
assignee: | nobody → Jelmer Vernooij (jelmer) |
This is not bzr itself, but rather a plugin that hooks into bzr that's causing problems.