launcspad: yeah, thats because its a NM bug :) ... anyway, 3.0.1 lets
you set a preference called toolkit.networkmanager.disable ... so if you
dont want the NM online state to be considered in firefox go to
about:config, and set that preference to true.
** Description changed:
Binary package h
i added two workarounds to the summary. The first is for firefox, the
second should make NM to always expose "online" as state.
Could someone please verify that those work and comment here?
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are
Alexander: the second workaround did not work. The first (about: config)
I don't know how. Please tell me more details! (Step-by-step.) Thanks!
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bu
The Firefox workaround works! Thanks a lot, now starts my Firefox ONLINE
with USB modem.
My /etc/network/interfaces file is:
auto lo
iface lo inet loopback
iface eth1000 inet dhcp
# And this 3 lines are followed by lines with "#" at the beginning -- I
think, these are only comments.
--
[MASTE
The 'iface eth1000 inet dhcp' trick didn't quite wok for me, but I'm not
entirely sure I have the same issue. I'm using Ubuntu 8.04 with a
wireless connection (Intel 3945), and I use Opera rather than firefox,
and what I've been experiencing is when I boot Ubuntu, the network
manager applet shows
I have Linux Mint Elyssa which is based on Ubuntu Hardy. I use dial-up
modem with serial to usb connector. There wasn't a way for me to create
a connection via Network Administration Tool>Network Settings as there
is no ttyUSB0 choice (there is in KPPP) so I use wvdial to connect to
the internet.
Hi Alexander
Thanks for suggestions.
Sadly neither workaround works for me. Probably as I am using an Orange
linebox - using the method described here
http://www.orangeproblems.co.uk/phpBB2/viewtopic.php?p=19235&sid=2975a93d5718ea39cf1a04afd0de8d98
as the livebox is odd. My Hardy Heron is stil
** Also affects: firefox-3.0 (Baltix)
Importance: Undecided
Status: New
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.launchpad.net/bugs/191889
You received this bug notificatio
I'm also using a CDMA connection using PPP and Firefox always starts in
offline mode. This is extremely annoying, but not really a big problem.
However, this also means that no Prism-applications work at all, because
it also starts in offline mode, and doesn't have a way to switch.
--
[MASTER] [W
I have hacked network-manager to check every second whether any
interface is up or not, besides the loopback interface. It worked
perfectly for my ppp connection. Both firefox and pidgin starts up with
the proper state, and even get notified when my ppp connection dies.
Comments welcomed.
Note th
could you plese minimize your patch (e.g. the .orig files are included
for instance).
Do you also check whether the interface has an IP assigned?
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https:/
NM 0.7 should fix most use cases. But i admit that there are still
missed cases, which i am in favour of forcing NM to interpret as online
as as any _unmanaged_ device has an ip.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
Status: Confirmed => Triaged
--
[MA
Here you go:
1. its a quilt patch
2. using libnl (using existing structures from nm-netlink-monitor.c)
3. minimal changes
4. checks for POINTOPOINT in the flags (this can be easily removed, but I guess
most of us have problems with ppp devices)
5. only handle unmanaged devices
6. utilize the mode
** Changed in: firefox
Status: Confirmed => Fix Released
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.launchpad.net/bugs/191889
You received this bug notification because you are
thanks for your patch. I would like to consider this. Just one comment
for now:
+nm_device_other_update_ppp (NMData *data,
+ gboolean is_connected)
isnt that a new function which should be declared in some header?
Is it only ppp that causes issues? I think the most fail
all this is still not a firefox issue. upstream backedn out NM support
in development head. but once we have the proposed patches in upstream
NM tree, we hopefully can enable that feature everwhere again.
** Changed in: firefox-3.0 (Ubuntu)
Status: In Progress => Invalid
** Changed in: fir
i would like to get a solution for NM in intrepid and hardy.
** Changed in: network-manager (Ubuntu Hardy)
Importance: Undecided => High
Status: New => Triaged
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of
milestoning NM intrepid task for 8.10 final.
** Changed in: network-manager (Ubuntu Intrepid)
Target: None => ubuntu-8.10
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.launchpad.n
options we have for pidgin are a) drop NM support and b) wait for fixed
NM. Obviously i prefer b). keeping task open anyway.
** Changed in: pidgin (Ubuntu Hardy)
Status: New => Confirmed
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that
It's not just with ppp. I use iwconfig and dhclient to connect to WEP
networks due to some outstanding bugs with iwl*+NM+WEP, and Firefox and
Evolution are in Offline mode when I do that.
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are m
Changes to the previous patch:
- the function nm_device_other_update_ppp is changed to
nm_device_update_unmanaged and defined in the header file
- now it monitors all unmanaged devices instead of just ppp devices
- now it checks whether the unmanaged device have an IP address before
signaling as
Sorry for two patches in quick succession. After some thought and
testing, this is a better patch.
** Attachment added: "50_monitor_unmanaged.patch"
http://launchpadlibrarian.net/18003776/50_monitor_unmanaged.patch
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
In my syslog I get also "NetworkManager: Unmanaged Device found;
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)"
when I try to connect to Ubuntu One. Ubuntu One can't establish a
connection. All other network related things are working, I can only see
this with Ubuntu One. We
In my syslog I get also "NetworkManager: Unmanaged Device found;
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)"
when I try to connect to Ubuntu One. Ubuntu One can't establish a
connection. All other network related things are working, I can only see
this with Ubuntu One. We
In my syslog I get also "NetworkManager: Unmanaged Device found;
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)"
when I try to connect to Ubuntu One. Ubuntu One can't establish a
connection. All other network related things are working, I can only see
this with Ubuntu One. We
Benjamin,
Seeing that message is normal when you have new virtual interfaces such
as 'vboxnet0' from VirtualBox, see comment #266.
Have you run updates since your installation of Karmic? There was one
know problem with Ubuntu One and synchronization was disabled for the
release. You would see an
ntrack looks promissing. we should look into using that in firefox and
other apps next cycle to tackle this problem.
** Also affects: ntrack
Importance: Undecided
Status: New
** Changed in: ntrack
Importance: Undecided => Wishlist
** Changed in: ntrack
Status: New => Triaged
In Karmic Koala same problem with Network manager if manual i manual
editing Interfaces and Resolv.conf with static address. Else all ok.
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.lau
In Karmic Koala same problem with Network manager if manual i manual
editing Interfaces and Resolv.conf with static address. Else all ok.
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.lau
In Karmic Koala same problem with Network manager if manual i manual
editing Interfaces and Resolv.conf with static address. Else all ok.
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.lau
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Launchpad kept giving me an information-free error popup whenever I hit
"post" and so I did not know it was actually posting until I hit
refresh. Sorry (but it's not my fault really, is it).
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are
** Tags added: metabug
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.launchpad.net/bugs/191889
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I have three boxes all running Lucid and all fully updated as of 5 Sept
2010. All three have unmanaged interfaces via /etc/network/interfaces
entries. On this box Firefox works normally. On the other two it always
comes up in offline mode, and Workaround 1 listed in comment 1 of this
report has no
I have three boxes all running Lucid and all fully updated as of 5 Sept
2010. All three have unmanaged interfaces via /etc/network/interfaces
entries. On this box Firefox works normally. On the other two it always
comes up in offline mode, and Workaround 1 listed in comment 1 of this
report has no
Update to comment 456:
Workaround 2 had no effect either, but inverting the setting of
Workaround 1 from "false" to "true" did solve the problem on the test
system. It no longer comes up in "work offline" mode.
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: empathy (Ubuntu Hardy)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu Hardy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
De
I was also directed to this bug report by the following entry in my
syslog:
NetworkManager: Unmanaged Device found; state CONNECTED forced.
(see http://bugs.launchpad.net/bugs/191889)
Although I didn't even have Firefox open at the time. Is this bug report
even relevant to this issue?
--
[MAS
** Changed in: network-manager
Assignee: (unassigned) => Duke (ers-duke16)
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.launchpad.net/bugs/191889
You received this bug notification
I have this issue, it appears to be caused by Network manager not being
able to cope with previously defined debian interface files.
I saw this for the first time when upgrading/installing via net-
installer to jaunty. lspci, lshal and nm-tool info attached . my
/etc/network/interfaces is just aut
aenertia, this is not your bug. this bug is about applications thinking
that you are offline, meaning pidgin doesnt try to connecte because it
thinks its offline or firefox starting in offline status even though you
are online. Your issue is just an applet display glitch, which is less
severe and k
I have a Dell Latitude which works both windows xp and Kubuntu. I had
Kubuntu 8.04 and I have upgraded tu 9.04 (jaunty). When I used 8.04 I
had configured my wireless card (a Broadcom BCM4312) with its Windows
module by Ndiswrapper. After a little bit of work it was worked fine.
But when I change t
you can just stop NM by
sudo /etc/init.d/NetworkManager stop
and then everything should work , or maybe start it when you want again
by
sudo /etc/init.d/NetworkManager start
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outsi
or "service" alternative
sudo service NetworkManager stop
sudo service NetworkManager start
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.launchpad.net/bugs/191889
You received this bug n
I am here because there is an entry in KSystemlog inviting me to see
this bug report.
" Unmanaged Device found; state CONNECTED forced. (see
http://bugs.launchpad.net/bugs/191889) "
But I don't know what to do.
This message started appearing after I configured my wireless network with WPA
encr
Another possible solution would be just to add a mechanism to
NetworkManager (and the applet) to explicitly inform it of the existence
of a connected interface. I'm using adb from the Android SDK to start a
ppp session with my G1 phone, and ppp0 comes online with no trouble but
NetworkManager doesn
** Changed in: firefox
Importance: Unknown => High
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are managed outside of network manager.
https://bugs.launchpad.net/bugs/191889
You received this bug notification because you are a member o
kelargo wrote:
> # cat /etc/network/interfaces
> auto lo eth0
> iface eth0 inet static
> address 192.168.0.99
> netmask 255.255.255.0
> gateway 192.168.0.1
> iface eth0 inet static
> address 192.168.0.99
> netmask 255.255.255.0
> network 192.168.0.0
> broabcast 192.168.0.255
> gateway 192.168.0.10
mbeccaria wrote:
> I am experiencing that the network-manager is reporting my wired
> connection as disconnected and not managed, whenever the wired
> connection is changed through the "old" network-admin tool.
>
>
what really matters for most applications (!= the applet, which is known
to show
Klaus,
I filed bug for FF lacking way to defeat off line mode, several months ago.
People refused to see that most users might never use or need off line mode.
People refused to change FF behavior to avoid users switching to browser with
less vexing behavior. Finally they combined my bug with
On Tue, Dec 23, 2008 at 11:57:34PM -, Klaus Thorn wrote:
> Firefox 3.0.5 starts in offline mode, failing to detect that I am online
> (with a connection which Opera, ping and apt-get all know to use well).
>
> The online connection that is not detected by firefox (nor network
> manager) is via
>I have this thing called a kiosk with a web-app in the background of the
>box. It has no network connectivity - it doesn't need to, there is this
>strange thing on Linux since like 1970 called loopback (for the Firefox
>developers, this can be found at http://127.0.0.1).
I didn't know that linux
On Monday 06 October 2008 16:57:29 Shellster wrote:
> I found an easy solution to the problem. Just remove the network
> manager package and the associated gnome package. Then your network
> setting will rely solely on /etc/network/interfaces like that ought to.
I found an easy solution, revert
I just upgraded to Intrepid and NM 0.7 works wonderfully for me. It
automatically detects my Bluetooth Pan (no more hacking around to set it up!
:-D ) and everything starts online as it should. Only problem is it is not
detected as a Mobile Broadband connection, but who cares as long as I get
pro
Logging out didn't help. I tried reinstalling network-manager and
network-manager-gnome, it prompted me to restart, which I did, and still
nothing. I went to my Sessions Preferences and the Network Manager Applet
was listed there with a command "nm-applet --sm-disable"
I checked my System Monito
if you have it,
sudo /etc/init.d/NetworkManager start
On Sun, Oct 12, 2008 at 03:02:25AM -, Jonathan wrote:
> I just noticed that you said there should be a process called
> "NetworkManager". That process is not running and I don't know how to
> start it. I tried sudo NetworkManager but it
On Thu, Oct 16, 2008 at 03:51:19PM -, chewearn wrote:
> Additional info:
> Evolution is working. It started in online mode and able to send/receive
> mails.
> Pidgin in not working. It get stuck trying to connect.
>
please do a restart of your system, reproduce and attach the complete
sysl
Thanks for the info. My problem with the NetworkManager was different. It
would not allow me to call up either of my 2 usb 56k dialup modems (Zoom and
US Robotics). The failure only happened under Ubuntu 9.10 as 9.04 worked
fine. I needed to remove the
software (sudo apt-get remove networkmanag
On Wed, Nov 26, 2008 at 11:28:50AM -, mbeccaria wrote:
> I am experiencing that the network-manager is reporting my wired
> connection as disconnected and not managed, whenever the wired
> connection is changed through the "old" network-admin tool.
>
Yes, in intrepid (0.7) this shouldnt make
On Wednesday 17 December 2008 21:27:47 kevin_405 wrote:
> I had to set workaround 1 to true not false
>
> Workaround 1: (since ffox 3.0.1) ->
> set toolkit.networkmanager.disable to true in about:config
Fresh install of kubuntu 8.10 with all updates has cellular modem connected
via kppp, then
On Thu, Dec 18, 2008 at 12:25:47PM -, Eric Lee Elliott wrote:
> On Wednesday 17 December 2008 21:27:47 kevin_405 wrote:
> > I had to set workaround 1 to true not false
> >
> > Workaround 1: (since ffox 3.0.1) ->
> > set toolkit.networkmanager.disable to true in about:config
> Fresh install
nukedathlonman & antistress: this bug specifically refers to problems with
firefox (and pidgin and others) not connecting to the internet when Network
Manger thinks it is offline. This bug has been solved and fixed.
On Mon, May 3, 2010 at 6:10 AM, antistress
wrote:
> Concerning my comment #432 i
No worries
On 30 Mar 2010, at 22:30, Sergio Zanchetta wrote:
> I realized I had made a mistake, Intrepid Ibex 8.10 "will reach" EOL
> on
> 30 "APRIL" 2010.
>
> Sorry for this.
>
> Anyway, I think that one month doesn't make any difference now.
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" featu
Thanks. I will print this message and follow the directions.
John
On Wed, Jan 25, 2012 at 4:59 AM, David Scott
<191...@bugs.launchpad.net>wrote:
> After reading this entire post, and finding nothing useful. The only
> useful posting was the one about updating (searching for the poster,
> crashe
On Sat, Jul 12, 2008 at 4:46 AM, wpshooter <[EMAIL PROTECTED]> wrote:
> I have my sister waiting for a computer that I have told her that I
> would configure for her use on a dialup ISP basis (she has no access to
> broadband) and now I can not get the thing to work.
>
> This is sort of embarrassin
On Thu, Jul 17, 2008 at 11:41:51AM -, forza wrote:
> Thats it for me. I've had enough of firefox and I am looking for a
> better browser without this bug.
>
These kind of statements dont make a difference and dont contribute
anything here. Please keep them out of bugs.
- Alexander
--
[MAS
On Sun, Jul 20, 2008 at 07:07:11PM -, launcspad wrote:
> Alexander: the second workaround did not work. The first (about: config)
> I don't know how. Please tell me more details! (Step-by-step.) Thanks!
>
Please post your /etc/network/interfaces file for the (not-working)
2nd-workaround attem
cubbie wrote:
> I have Linux Mint Elyssa which is based on Ubuntu Hardy. I use dial-up
> modem with serial to usb connector. There wasn't a way for me to create
> a connection via Network Administration Tool>Network Settings as there
> is no ttyUSB0 choice (there is in KPPP) so I use wvdial to co
On Tue, Aug 12, 2008 at 12:09:08PM -, Jo-Erlend Schinstad wrote:
> I'm also using a CDMA connection using PPP and Firefox always starts in
> offline mode. This is extremely annoying, but not really a big problem.
> However, this also means that no Prism-applications work at all, because
> it al
Thanks for the summary of your efforts. I experience the "offline"
condition for
FireFox only during a dialup connection. Using the DSL network connection
with a router
and DSL adapter Firefox works normally. My dialup connection for Ubuntu
9.04 and 9.10 has been gnome-ppp.
On Sun, Sep 5, 2010
That message is saying that NM is pretending the unmanaged device is online
since it can't tell if it is or not to avoid people here seeing Firefox
offline.
It's perfectly safe to ignore.
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that ar
As I understand, the internet connection is one issue, the browser
communicating with the DSL or PPP
software is another issue. I have no problem with the browser starting
right away on my DSL, but the ppp
won't talk to my browser until I go to Firefox "file" and drag down to
uncheck "offline."
J
Thank you for your reply.
John Kohler
On Tue, Aug 4, 2009 at 7:24 PM, Duke wrote:
> ** Changed in: network-manager
> Assignee: (unassigned) => Duke (ers-duke16)
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside
On Fri, Jan 30, 2009 at 03:39:50AM -, drizad wrote:
>
> Solution (maybe temporary) with Ubuntu Intrepid 8.10:
> 1. remove network-manager
> sudo apt-get remove network manager
>
> 2. Install wicd
> http://www.ubuntugeek.com/wicd-wired-and-wireless-network-manager-for-ubuntu.html
>
This isnt
An easier solution, if your FF3 is updated to current, is to type
"about:config" in a blank tab. Click OK to the scary message. Type
tool in the filter line.
You will find the below one ending in false. click on the line to
change to true. This is not a FF problem but they found a fix for i
Actually this is not a firefox / nm interaction issue at all ( I have seen
this one, and know how to work around it).
It is purely network-manager failing to correctly manage network devices. It
is more an issue of not having populated device entries correctly and then
not being able to manage the
101 - 184 of 184 matches
Mail list logo
