cannot shutdown laptop with Kubuntu 12.10 and other networking issues...

[John_kubuntu]

The second part of my feedback, this time about networking and CIFS.
Understand that overall I am happy with Kubuntu, but there are some long standing
issues. I hope this feedback is taken in good spirit.

1. When I shutdown the laptop, network-manager bails out before the NAS shares are dismounted.
This hangs the laptop in the shutdown message.
Internet search shows that this is a LONG standing issue with (k)ubuntu (Race condition). Will it ever be solved?
I looked into upstart but it is too obscure for me to quickly apply any of the (pre upstart era) fixes I found on the internet.

2. I want to configure my laptop to start the wireless immediately at boot, before kde is started.
How to do that?
Secrets are stored on the laptop, so it should not be a problem in principle.

3. suppose I have my laptop connected over wireless watching a movie.
Network bandwidth is insufficient, so I plug in a cable.
Movie is not automatically switched to the cable, so I have to swith of wireless.
Too bad: dolphin and my movie playback hang for 5-10 minutes before something gives (timeout)
and I can resume my movie.
Firefox etc deal with this perfectly so:
- networkmanager works
- networking is presented to the system ok.
But a kioslave or dolphin cannot handle networking interface switching -> end of usability of kde in the working place
(docking / undocking)

Should I enter bugs against kde for this?
Just an honest question:
What added value can I reasonably expect from a distro? Is this too far fetched for kubuntu to solve?
If so, tell me and I will start creating kde bugs.

[pauly]

The second part of my feedback, this time about networking and CIFS.
Understand that overall I am happy with Kubuntu, but there are some long standing
issues. I hope this feedback is taken in good spirit.

1. When I shutdown the laptop, network-manager bails out before the NAS shares are dismounted.
This hangs the laptop in the shutdown message.
Internet search shows that this is a LONG standing issue with (k)ubuntu (Race condition). Will it ever be solved?
I looked into upstart but it is too obscure for me to quickly apply any of the (pre upstart era) fixes I found on the internet.

2. I want to configure my laptop to start the wireless immediately at boot, before kde is started.
How to do that?
Secrets are stored on the laptop, so it should not be a problem in principle.

3. suppose I have my laptop connected over wireless watching a movie.
Network bandwidth is insufficient, so I plug in a cable.
Movie is not automatically switched to the cable, so I have to swith of wireless.
Too bad: dolphin and my movie playback hang for 5-10 minutes before something gives (timeout)
and I can resume my movie.
Firefox etc deal with this perfectly so:
- networkmanager works
- networking is presented to the system ok.
But a kioslave or dolphin cannot handle networking interface switching -> end of usability of kde in the working place
(docking / undocking)

Should I enter bugs against kde for this?
Just an honest question:
What added value can I reasonably expect from a distro? Is this too far fetched for kubuntu to solve?
If so, tell me and I will start creating kde bugs.

I think when your testing beta software you will need to be skilled enough to trouble shoot these issues your self. You should expect to have these problems. If I were you I would wait till the new versions have been completed and released before upgrading. You will have less problems that way. Unless your prepared to deal with a lot of these issues your self. Beta software is for experienced users and should be expected to have plenty of bugs.

[pauly]

The current stable version is 12.04 and can be found here.

http://www.kubuntu.org/getkubuntu/download

[pauly]

It also might be better to put all your concerns in one thread.

[SteveRiley]

2. I want to configure my laptop to start the wireless immediately at boot, before kde is started.
How to do that?

Enable System Connection on the interface:

3. suppose I have my laptop connected over wireless watching a movie.
Network bandwidth is insufficient, so I plug in a cable.
Movie is not automatically switched to the cable, so I have to swith of wireless.
Too bad: dolphin and my movie playback hang for 5-10 minutes before something gives (timeout)
and I can resume my movie.

Can't say that I've played with this much. Something to try: run the following command immediately after you plug in the Ethernet cable:

sudo service networking restart

[John_kubuntu]

I think when your testing beta software you will need to be skilled enough to trouble shoot these issues your self.

These problems are with me for years and all this time they are not solved by ubuntu / kubuntu / kde.
They are not related to me using beta-SW.
I think these problems are actually pretty hard to solve, or they would have been solved already

[John_kubuntu]

Enable System Connection on the interface:

This works great! Thanks :-)

Can't say that I've played with this much. Something to try: run the following command immediately after you plug in the Ethernet cable:

sudo service networking restart

Thanks for the advice!

To be sure we are clear on the scenario:
- start using wireless, use Dolphin to select movie on NAS (CIFS or NFS makes no difference), movie starts in VLC
- connect 1GB network cable. Network manager shows the cable icon, BUT:
movie and Dolphin are still using wireless, so they do not switch to wired automatically
- I use networkmanager to stop the wireless networking
- Dolphin and the movie freeze.

Now I do service networking restart -> no effect.
After about two minutes both the movie and Dolphin simultaneously start working again.

But now the start menu (Lancelot) does not work anymore.
Wait a minute, the taskbar does not react anymore. The whole of plasma seems to be stuck...
Something within the innards of KDE is not right!
Luckily I can still type "reboot now" in a terminal.

To be honest, I did not expecte restarting networking to help.
I think the networking part itself works very good -> I can immediately
browse the internet with Firefox again. I suggest that it is a higher level subsystems (kio?) that cannot
handle switching the "network backends". When it times out it re-establishes a connection to
the networking subsystem again -> bingo.

I will report this bug against kio and see what happens :-)

[John_kubuntu]

Problems 1 and 2 are now solved.
I reported problem 3 on bugs.kde.org: https://bugs.kde.org/show_bug.cgi?id=307967
Will leave this thread as unresolved.