Bug 890212 - Using GSM/HSDPA connection randomly triggers "acquiring IP address" message
Summary: Using GSM/HSDPA connection randomly triggers "acquiring IP address" message
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-plasma-networkmanagement
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-25 18:45 UTC by Germano Massullo (Thetra)
Modified: 2014-06-10 01:51 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 09:35:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot 1 (41.89 KB, image/png)
2012-12-25 18:45 UTC, Germano Massullo (Thetra)
no flags Details
Screenshot 2 (42.00 KB, image/png)
2012-12-25 18:46 UTC, Germano Massullo (Thetra)
no flags Details
Screenshot 3 (32.79 KB, image/png)
2012-12-25 18:46 UTC, Germano Massullo (Thetra)
no flags Details

Description Germano Massullo (Thetra) 2012-12-25 18:45:32 UTC
Created attachment 668977 [details]
Screenshot 1

Description of problem:
Usually while being connected to a GSM/HSDPA connection with an USB device, you can see knetworkmanager as a phone icon. Sometimes it changes into an ethernet icon, with a progress bar, like when you plugin the ethernet cable and the system is acquiring the IP address. Moreover while using a GSM/HSDPA device, on Knetworkmanager devices list, there is one more device that does not exist.

I attach three screenshots that can better explain the problem

Version-Release number of selected component (if applicable):
KDE 4.9,4

Comment 1 Germano Massullo (Thetra) 2012-12-25 18:46:07 UTC
Created attachment 668978 [details]
Screenshot 2

Comment 2 Germano Massullo (Thetra) 2012-12-25 18:46:34 UTC
Created attachment 668979 [details]
Screenshot 3

Comment 3 Kevin Kofler 2012-12-25 21:32:52 UTC
Could it be that it is simply reconnecting because you lost the connection (signal)?

Comment 4 Germano Massullo (Thetra) 2012-12-25 22:03:39 UTC
I don't think so

Comment 5 Fedora End Of Life 2013-07-04 02:51:46 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2013-08-01 09:35:09 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.