Bug#650002: network-manager-gnome: connection to WiFi leads to 'Gtk-WARNING **: cannot open display: :0.0'

2011-11-25 Thread tom
Package: network-manager-gnome
Version: 0.9.2.0-1
Severity: normal

Dear Maintainer,

connecting to wireless LAN leads to the fact that it is impossible to open any 
new window (since a dist-upgrade yesterday).
Typing a command in a previously opened terminal that normally opens a new 
window (e.g. `mousepad') 
leads to the following message:

'No protocol specified

(mousepad:3883): Gtk-WARNING **: cannot open display: :0.0'

If any further info is needed I will try to provide it.
Thanks!
Tom

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager-gnome depends on:
ii  dbus-x11 1.4.16-1  
ii  dpkg 1.16.1.1  
ii  gconf2   2.32.4-1  
ii  gnome-icon-theme 3.2.1.2-1 
ii  libatk1.0-0  2.2.0-2   
ii  libc62.13-21   
ii  libcairo-gobject21.10.2-6.1
ii  libcairo21.10.2-6.1
ii  libdbus-1-3  1.4.16-1  
ii  libdbus-glib-1-2 0.98-1
ii  libfontconfig1   2.8.0-3   
ii  libfreetype6 2.4.8-1   
ii  libgconf2-4  2.32.4-1  
ii  libgdk-pixbuf2.0-0   2.24.0-1  
ii  libglib2.0-0 2.28.8-1  
ii  libgnome-bluetooth8  3.2.1-1   
ii  libgnome-keyring03.2.0-3   
ii  libgtk-3-0   3.0.12-2  
ii  libnm-glib-vpn1  0.9.2.0-1 
ii  libnm-glib4  0.9.2.0-1 
ii  libnm-gtk0   0.9.2.0-1 
ii  libnm-util2  0.9.2.0-1 
ii  libnotify4   0.7.4-1   
ii  libpango1.0-01.29.4-2  
ii  network-manager  0.9.2.0-1 
ii  policykit-1-gnome0.105-1   

Versions of packages network-manager-gnome recommends:
ii  gnome-bluetooth3.2.1-1   
ii  iso-codes  3.30-1
ii  libpam-gnome-keyring [libpam-keyring]  3.0.3-2   
ii  mobile-broadband-provider-info 20110806-1
ii  notification-daemon0.7.3-1   
ii  xfce4-notifyd [notification-daemon]0.2.2-1   

Versions of packages network-manager-gnome suggests:
ii  network-manager-openvpn-gnome  none   
ii  network-manager-pptp-gnome none   
ii  network-manager-vpnc-gnome 0.9.2.0-1

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#650002: [Pkg-utopia-maintainers] Bug#650002: network-manager-gnome: connection to WiFi leads to 'Gtk-WARNING **: cannot open display: :0.0'

2011-11-25 Thread Michael Biebl
On 25.11.2011 14:17, tom wrote:
 Package: network-manager-gnome
 Version: 0.9.2.0-1
 Severity: normal
 
 Dear Maintainer,
 
 connecting to wireless LAN leads to the fact that it is impossible to open 
 any new window (since a dist-upgrade yesterday).
 Typing a command in a previously opened terminal that normally opens a new 
 window (e.g. `mousepad') 
 leads to the following message:
 
 'No protocol specified
 
 (mousepad:3883): Gtk-WARNING **: cannot open display: :0.0'
 

What happened most likely, is that your hostname was changed.
Could you verify that: what's the output of hostname before and after
you connect to said Wifi network.

Did the DHCP server send a hostname?
Do you have the ifupdown plugin enabled in
/etc/NetworkManager/NetworkManager.conf? What does /etc/hostname contain?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#650002: [Pkg-utopia-maintainers] Bug#650002: network-manager-gnome: connection to WiFi leads to 'Gtk-WARNING **: cannot open display: :0.0'

2011-11-25 Thread Michael Biebl
[always CC the bug report]
On 25.11.2011 15:05, blabla blabla wrote:
 Am 25.11.2011 14:38, schrieb Michael Biebl:
   On 25.11.2011 14:17, tom wrote:

  
   (mousepad:3883): Gtk-WARNING **: cannot open display: :0.0'
  
  
   What happened most likely, is that your hostname was changed.
   Could you verify that: what's the output of hostname before and after
   you connect to said Wifi network.
 
 correct, it changes from that in /etc/hostname to 'dhcppc0'.
 
   Did the DHCP server send a hostname?
 
 how can I check that?

You can run NetworkManager in debug mode [1]. But given it is set to
dhcppc0, that's most likely what happened.

   Do you have the ifupdown plugin enabled in
   /etc/NetworkManager/NetworkManager.conf?
 
 [ifupdown]
 managed=false
 
 setting it to true and restarting makes no difference.

I meant:
[main]
plugins=ifupdown


[1] https://live.gnome.org/NetworkManager/Debugging
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#650002: [Pkg-utopia-maintainers] Bug#650002: network-manager-gnome: connection to WiFi leads to 'Gtk-WARNING **: cannot open display: :0.0'

2011-11-25 Thread blabla blabla

Am 25.11.2011 15:20, schrieb Michael Biebl:

[always CC the bug report]
On 25.11.2011 15:05, blabla blabla wrote:

Am 25.11.2011 14:38, schrieb Michael Biebl:
On 25.11.2011 14:17, tom wrote:



  
(mousepad:3883): Gtk-WARNING **: cannot open display: :0.0'
  
  
What happened most likely, is that your hostname was changed.
Could you verify that: what's the output of hostname before and after
you connect to said Wifi network.

correct, it changes from that in /etc/hostname to 'dhcppc0'.

Did the DHCP server send a hostname?

how can I check that?


You can run NetworkManager in debug mode [1]. But given it is set to
dhcppc0, that's most likely what happened.


Do you have the ifupdown plugin enabled in
/etc/NetworkManager/NetworkManager.conf?

[ifupdown]
managed=false

setting it to true and restarting makes no difference.


I meant:
[main]
plugins=ifupdown


It was

[main]
plugins=keyfile

I set it to

[main]
plugins=ifupdown,keyfile

This solved the problem of changing hostnames after restart. But with 
the nice side effect that all windows were missing titles and buttons to 
control them (the cross ... usually in the upper right corner). Deleting 
~/.cache, ~/.dconf and ~/.gconf/system solved that (I deleted all at a 
time, thus I don't know which one really did it).


regards,
Tom




[1] https://live.gnome.org/NetworkManager/Debugging




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org