GNOME Bugzilla – Bug 301867
weather-applet crashes when confined to a captive portal
Last modified: 2005-04-26 23:23:29 UTC
Distribution: Debian 3.1 Package: gnome-applets Severity: normal Version: GNOME2.10.1 0 Gnome-Distributor: Ubuntu Synopsis: weather-applet crashes when confined to a captive portal Bugzilla-Product: gnome-applets Bugzilla-Component: gweather Bugzilla-Version: 0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: When booting in a hotel or other location that does http redirects to capture traffic the weather app will crash every time. Steps to reproduce the crash: 1. boot in area with captive portal 2. 3. Expected Results: crash... How often does this happen? every time Additional Information: none Debugging Information: Backtrace was generated from '/usr/libexec/gweather-applet-2' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1221790016 (LWP 8662)] [New Thread -1224668240 (LWP 8675)] [New Thread -1224402000 (LWP 8674)] [New Thread -1224057936 (LWP 8673)] [New Thread -1223791696 (LWP 8672)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in ?? ()
+ Trace 58665
Thread 1 (Thread -1221790016 (LWP 8662))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-25 04:20 ------- Unknown version 0 in product gnome-applets. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-applets". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was duane@cacert.org. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
I've run into this here in Sydney too. Until you "log in" with your web browser, all port 80 requests result in an HTTP redirect to the login page, and non port 80 requests are blocked. After logging in, gweather behaves normally. Looks like a dupe of bug 170628 *** This bug has been marked as a duplicate of 170628 ***