Bug 794954 - f17 alpha tc2 kde live-cd nm no session found for uid 1000 (cannot connect to either wifi nor 3g)
Summary: f17 alpha tc2 kde live-cd nm no session found for uid 1000 (cannot connect to...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-18 04:00 UTC by Reartes Guillermo
Modified: 2012-03-26 12:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-26 12:59:38 UTC
Type: ---


Attachments (Terms of Use)
kde live-cd, tried to connect to wifi and to a 3g modem (152.96 KB, text/plain)
2012-02-18 04:00 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2012-02-18 04:00:00 UTC
Created attachment 564038 [details]
kde live-cd, tried to connect to wifi and to a 3g modem

Description of problem:

It is not possible to use a 3g modem (huaweii e173s-6) or a wifi connection from 
the live cd. also there is this after login:

"warning: cannot open consolekit session: unable to open session: unable to get information about the calling process"

after pression ok, KDE continues loading.

Version-Release number of selected component (if applicable):
F17aTC2


How reproducible:
allways

Steps to Reproduce:
1. boot

Comment 1 Reartes Guillermo 2012-02-21 20:29:40 UTC
I tested the alpha tc3 KDE LiveCD and:

* i am able to connect to a wifi network (protected)
* i am able to connect to a internet via an usb 3g modem (huawei 173s-6)

so, network manager seems to be usable. (i only tested one laptop).

the "consolekit" message is still there but it may not be related.

Thanks.

Comment 2 Reartes Guillermo 2012-02-23 21:24:25 UTC
This issue seems to be fixed, an installed and updated system does not experience this message.


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