Comment 2 for bug 868501

Yes, just knowing that it is set should be sufficient. This came up because of bug 848915 and here is some discussion around it.

08:50 < mvo> cjwatson: this sounds like DISPLAY is not set
08:50 < cjwatson> hm, you've commented I see
08:51 -!- robbiew [~RobbieWil@99-156-84-159.lightspeed.austtx.sbcglobal.net] has joined #ubuntu-meeting
08:51 < mvo> cjwatson: this was the only way I managed to reproduce
08:51 < cjwatson> distinctly odd since the reporters seem to be using the GTK frontend though
08:51 < bdmurray> duplicate bug 867629 has a test case
08:51 < ubottu> Launchpad bug 848915 in update-manager (Ubuntu Oneiric) "duplicate for #867629 update-manager crashed with RuntimeError in /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py: Gtk couldn't be initialized" [High,Incomplete] https://launchpad.net/bugs/848915
08:51 < cjwatson> surely they couldn't have got that far ...
08:51 < mvo> bdmurray: oh, nice!
08:52 < mvo> bdmurray: gksu then most likely
08:53 < cjwatson> yeah, gksu will be sanitising the environment
08:53 < slangasek> yeah, why would gksu need DISPLAY...
08:53 < slangasek> :)
08:55 -!- laoshi [~flemming@85.218.199.31] has quit [Remote host closed the connection]
08:55 < slangasek> someone's triaging that one to gksu then? someone want to work on it?
08:55 < jhunt> bdmurray, cjwatson, mvo: maybe apport could be changed to include DISPLAY in 'ProcEnviron'?