Weird problem with wireless and dcopserver
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm
Weird problem with wireless and dcopserver
Ok, this is really strange. Whenever I start my laptop or reboot it and log in, I get a message saying DCOPSERVER needs my password. Normally, it should be Knetworkmanager asking for my password right after I log in. Instead dcopserver is asking for it and not knetworkmanager which is causing knetworkmanager not to start and my wireless won't work. Also I can't start knetworkmanager manually either.
Now this is where it gets weirder. If I end the current session and go back to the log-in screen the colors are all off and strange looking. So I type my password and the screen goes black for a second and then comes back to a normal looking log in screen. Then I type my password again and it logs me back in. Then during that log-in knetworkmanager asks for my password and not dcopserver and my wireless works correctly.
I'm on a Lenovo N100 laptop with gma950 intel graphics chipset using the new intel driver. Bianca KDE edition. This just started happening since I installed Samba and started trying to get that to work. The only other thing I did right before this started was upgrade 6 packages that came up as being upgradeable in Synaptic.
Sorry for the long explanation, but it's a crazy problem. If anybody has any idea whatsoever about what's going on I'd love to atleast hear a theory. It's going to get a little old going through all that everytime I boot up my computer.
Thanks
Now this is where it gets weirder. If I end the current session and go back to the log-in screen the colors are all off and strange looking. So I type my password and the screen goes black for a second and then comes back to a normal looking log in screen. Then I type my password again and it logs me back in. Then during that log-in knetworkmanager asks for my password and not dcopserver and my wireless works correctly.
I'm on a Lenovo N100 laptop with gma950 intel graphics chipset using the new intel driver. Bianca KDE edition. This just started happening since I installed Samba and started trying to get that to work. The only other thing I did right before this started was upgrade 6 packages that came up as being upgradeable in Synaptic.
Sorry for the long explanation, but it's a crazy problem. If anybody has any idea whatsoever about what's going on I'd love to atleast hear a theory. It's going to get a little old going through all that everytime I boot up my computer.
Thanks
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm
No it shouldnt be asking for a password itself.
sounds like it is a KDE bug.
DCOPServer is how KDE desktop and apps talk to each other. It is a backend thing.
I cant check at the moment but can you reinstall it?
this also points to the updates being KDE related.
sounds like it is a KDE bug.
DCOPServer is how KDE desktop and apps talk to each other. It is a backend thing.
I cant check at the moment but can you reinstall it?
this also points to the updates being KDE related.
Now where was i going? Oh yes, crazy!
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm
Well, since I haven't had Mint installed very long, I just went ahead and reinstalled. I didn't lose too many settings since I've only had it on the laptop a couple days and haven't customized everything yet.
I think the problem stems from some packages that I upgraded. It's hard to tell which one/ones though, because I just did the whole upgrade everything routine. That's when I started getting the dcopserver problem, and also Konqueror somehow got removed.
This time around I only installed and upgraded the things I need, and it's working great at the moment. Hopefully, if I upgrade packages in smaller increments, it'll make it easier to pinpoint the problem if it happens again.
I think the problem stems from some packages that I upgraded. It's hard to tell which one/ones though, because I just did the whole upgrade everything routine. That's when I started getting the dcopserver problem, and also Konqueror somehow got removed.
This time around I only installed and upgraded the things I need, and it's working great at the moment. Hopefully, if I upgrade packages in smaller increments, it'll make it easier to pinpoint the problem if it happens again.
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm
ARGHHEH@!!! I though I had the problem fixed, but it's presented itself again. However, I think I might have found a clue to what the cause is.
It has been working fine for a while now, but this morning I used my laptop however there were no access points nearby so Knetworkmanager didn't connect to anything. Now when I rebooted back at home where I have an access point DCOPServer starts asking for my kdewallet password again.
It has been working fine for a while now, but this morning I used my laptop however there were no access points nearby so Knetworkmanager didn't connect to anything. Now when I rebooted back at home where I have an access point DCOPServer starts asking for my kdewallet password again.
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm
I am thinking roaming is the problem.
I would try setting the wireless to just your home network.
another test before turning off roaming.
turn off your laptop
Turn off your wireless router/AP, turn on your laptop and see what happens. This simulates you away from home (no AP).
turn off your laptop
turn on your wireless router/AP, give it 5min.
turn on your laptop and see if you can connect to your wireless lan. this simulates you coming home again.
This should show if roaming is the problem.
you could also repeat this test once roaming is turned off and only one static wireless network setup.
hope this helps.
I would try setting the wireless to just your home network.
another test before turning off roaming.
turn off your laptop
Turn off your wireless router/AP, turn on your laptop and see what happens. This simulates you away from home (no AP).
turn off your laptop
turn on your wireless router/AP, give it 5min.
turn on your laptop and see if you can connect to your wireless lan. this simulates you coming home again.
This should show if roaming is the problem.
you could also repeat this test once roaming is turned off and only one static wireless network setup.
hope this helps.
Now where was i going? Oh yes, crazy!
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm
- flammenwurfer
- Level 1
- Posts: 40
- Joined: Sun Jun 10, 2007 1:52 pm