closing the bug since that works now
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete => Fix Released
--
Gtk+ applications slow when local (lo) network interface not upped
https://bugs.launchpad.net/bugs/231384
You received this bug notification because you are a member of Ubuntu
Bugs,
No, it is no longer an issue. A workaround was well known. Close this bug
report. Thanks, Ayan
- Original Message
From: Sebastien Bacher
To: ay...@yahoo.com
Sent: Wednesday, April 22, 2009 12:02:34 PM
Subject: [Bug 231384] Re: Gtk+ applications slow when local (lo) network
interface
could you try if that's still an issue in jaunty?
** Changed in: gtk+2.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: gtk+2.0 (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
Gtk+ applications slow when local (lo) network interface not upped
https://bugs.
Ayan
- Original Message
From: paddy2706
To: ay...@yahoo.com
Sent: Thursday, February 5, 2009 6:03:24 PM
Subject: [Bug 231384] Re: Gtk+ applications slow when local (lo) network
interface not upped
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You rep
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
--
Gtk+ appl
> Do you remember why "lo" interface is not setup?
> Did you tweak that manually?
Yes, I did. My WLAN-USB-stick (Ralink) did not work so I modified the
configuration file manually.
I simply forgot to setup the lo interface again.
> How did you install your ubuntu?
> - Alexander
I downloaded the
I confirm that networkmanager does not start the lo interface when I'm
using a static IP configuration on eth1 (at work). This causes several
GTK applications, including firefox, to be extremely slow. When using
the wireless (wlan0, at home), lo is started automatically and I don't
have this proble
ayan: in case you didn't avoid gui-applications on purpose, there's
always firestarter or guarddog to help you configure a firewall. you
probably knew that anyway :-)
alexander: the installation was made under feisty i believe and upgraded
to gutsy, then hardy. i didn't tweak anything in there, th
ayan: in case you didn't avoid gui-applications on purpose, there's
always firestarter or guarddog to help you configure a firewall. you
probably knew that anyway :-)
alexander: the installation was made using feisty (regular cd
installation replacing an upgraded dapper->edgy installation) i belie
I followed Andrea's interface cleaning. I just deleted all the contents
of interface, but firefox still won't work. Then I remembered that one
of my friends helped me set up a firewall. The content of that file is:
#!/bin/sh
iptables -P OUTPUT ACCEPT
iptables -P FORWARD DROP
iptables -P INPUT DROP
10 matches
Mail list logo
