[opensuse] kde network manager plasmoid pain
12.1 I have to give the root password and the wpa password every time I turn on my laptop. click on the plasmoid -> manage connections Choose connection and hit edit A popup appears BEHIND the window (so you have no idea it's there) asking for the root password. A popup appears 'No agents were available for this request' Click OK The Edit network connection window appears. Click on wireless security. The password has been deleted. Reenter the password and it finally connects. You have to do this evert time you boot. What a pain! There is no easy workaround I can find. I see that this was the same in Factory with 12.1 trials. I thought about wicd but it's not easy to install on 12.1. Anyone found a fix? Thanks L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
12.1
I have to give the root password and the wpa password every time I turn on my laptop.
click on the plasmoid -> manage connections
Choose connection and hit edit
A popup appears BEHIND the window (so you have no idea it's there) asking for the root password.
A popup appears 'No agents were available for this request'
Click OK
The Edit network connection window appears. Click on wireless security. The password has been deleted.
Reenter the password and it finally connects.
You have to do this evert time you boot. What a pain!
There is no easy workaround I can find. I see that this was the same in Factory with 12.1 trials. I thought about wicd but it's not easy to install on 12.1.
Anyone found a fix?
Thanks L x
There is a bug report for requiring a password for configuring a wireless link. Even Linus Torvalds has filed a report about how incredibly stupid that is, as his kids can't connect elsewhere. I pointed out how it's a show stopper for corporate users. I believe a fix is in the works for that. However, I don't recall any problem with having to do that each time. In my experience, once it's configured it works, though there is a but where sometimes WiFi fails. There are definitely some real problems in plasmoid network manager and elsewhere in 12.1 which make me seriously question the amount of testing that was put into this release. Some of the bugs would have been caught with a minimal amount of testing. Another example is postfix, which simple does not run. Given that Linux is often used for mail servers, how could this have possibly made it into a release distro? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Nov 27, 2011 at 14:37, James Knott <james.knott@rogers.com> wrote:
network manager and elsewhere in 12.1 which make me seriously question the amount of testing that was put into this release.
Did you contribute to the testing?
Some of the bugs would have been caught with a minimal amount of testing
There was a lot of testing done, but with a small number of people doing the actual testing, they cannot hope to cover all use cases. 12.2 is on its way in under 8 months. Step up and test the bits that concern you. Don't leave it to "someone else" or the things you find annoying will probably still be not working right come release day
Another example is postfix, which simple does not run. Given that Linux is often used for mail servers, how could this have possibly made it into a release distro?
From my side.. easy, I don't use postfix... so I didn't test it. Did you test postfix in the 12.1 alpha, beta and RC runs? Did you (or anyone else that could have tested postfix) open bug reports on the bits pf postfix that are not working
We all, as regular users, have a responsibility to our favorite distribution to help out... it IS a community distribution after all. Not all of us are developers, but we are all users, and we can ALL test... every one of us, even if it means installing a virtual machine on a Sunday afternoon during the RC phase... commenting about how it wasn't tested enough doesn't help matters one iota. :-( C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
C wrote:
network manager and elsewhere in 12.1 which make me seriously question the
amount of testing that was put into this release.
Did you contribute to the testing?
I installed both RC versions and reported bugs on both. I also used to do testing at IBM and would have been fired for allowing some of the problems that happened with 12.1. The problem Lynn referred to isn't even an error. It's an extremely serious design flaw that shows someone didn't consider real world use when they designed it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Nov 27, 2011 at 15:40, James Knott <james.knott@rogers.com> wrote:
network manager and elsewhere in 12.1 which make me seriously question the
amount of testing that was put into this release.
Did you contribute to the testing?
I installed both RC versions and reported bugs on both.
I also used to do testing at IBM and would have been fired for allowing some of the problems that happened with 12.1. The problem Lynn referred to isn't even an error. It's an extremely serious design flaw that shows someone didn't consider real world use when they designed it.
Cool... so many people complain about the testing, but do absolutely none of the testing themselves. Too many of us forget that openSUSE needs all of us to help out. :-) and we need that reminder a little more often I think. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 27 November 2011, James Knott wrote:
C wrote:
network manager and elsewhere in 12.1 which make me seriously question the
amount of testing that was put into this release.
Did you contribute to the testing?
I installed both RC versions and reported bugs on both.
I also used to do testing at IBM and would have been fired for allowing some of the problems that happened with 12.1.
Repeatedly asking across different threads for _someone_ should fire you? Someone should do it finally. You're fired! cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/27/2011 08:55 AM, C pecked at the keyboard and wrote:
On Sun, Nov 27, 2011 at 14:37, James Knott<james.knott@rogers.com> wrote:
network manager and elsewhere in 12.1 which make me seriously question the amount of testing that was put into this release.
Did you contribute to the testing?
Some of the bugs would have been caught with a minimal amount of testing
There was a lot of testing done, but with a small number of people doing the actual testing, they cannot hope to cover all use cases. 12.2 is on its way in under 8 months. Step up and test the bits that concern you. Don't leave it to "someone else" or the things you find annoying will probably still be not working right come release day
Another example is postfix, which simple does not run. Given that Linux is often used for mail servers, how could this have possibly made it into a release distro?
From my side.. easy, I don't use postfix... so I didn't test it. Did you test postfix in the 12.1 alpha, beta and RC runs? Did you (or anyone else that could have tested postfix) open bug reports on the bits pf postfix that are not working
The problem does not reside with postfix but with systemd. "systemd" is the culprit that should _not_ have been forced as the default until it was ready. Does this sound the same as zypper, kde4 and pulseaudio that were forced as defaults _before_ they were ready. Does anyone see a pattern here?
We all, as regular users, have a responsibility to our favorite distribution to help out... it IS a community distribution after all. Not all of us are developers, but we are all users, and we can ALL test... every one of us, even if it means installing a virtual machine on a Sunday afternoon during the RC phase... commenting about how it wasn't tested enough doesn't help matters one iota. :-(
C.
-- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Ken Schneider - openSUSE wrote:
The problem does not reside with postfix but with systemd. "systemd" is the culprit that should _not_ have been forced as the default until it was ready.
Does this sound the same as zypper, kde4 and pulseaudio that were forced as defaults _before_ they were ready. Does anyone see a pattern here?
Quite so. When you make a major change, such as this, you'd better be prepared to do a lot of testing to make sure it doesn't cause so many severe problems. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Ken Schneider - openSUSE said the following on 11/27/2011 09:49 AM:
The problem does not reside with postfix but with systemd. "systemd" is the culprit that should _not_ have been forced as the default until it was ready.
That's not entirely fair. As I've said here before, I also run Fedora-15 which uses SystemD and Grub2 and works well. What puzzles me is why, when there is a pioneer to learn from - fedora - the followers such as openSuse don't seem to benefit.
Does this sound the same as zypper, kde4 and pulseaudio that were forced as defaults _before_ they were ready. Does anyone see a pattern here?
I wasn't running Fedora when pulseaudio came out. Yes I had a problem with it on 11.2 but Felix solved that for me. Thank you Felix. KDE4 was another matter. .0 though .3 were definitely "beta", but without that how would the problems have been worked out.? Lets face it, people here are going on about "adequate testing" and the only way to test all cases and a variety of hardware is to push out the "alpha" and "beta" and release candidates and have people test them. Here we have KDE4.4 that was great. Here we have 11.4 which is great. My worry: we have 12.1 which is really 12.0 and its going what KDE did. I look forward to the "great" 12.4 but I'm told that won't happen, it will be 13.1 (which will really be 13.0). OUCH OUCH OUCH Maybe I should by another drive and install 12.1 on it and do a sdiff against fedora to see all the places 12.1 has the SystemD packages in the wrong place (and so don't start properly) or has the dependency wrong (so they don't start properly). OBTW: I've removed Postfix from my Fedora machine and am using esmtp instead. If anyone can help me do that with 11.4 or tell me how I will have to do it with 12.x I will be grateful. Because Postfix is removed from the fedora box I'm sorry I can't tell you where/what it should be under 12.1, but if you want to ask about other SystemD config, then a) put fedora 15 or 16 up on your own virtual machine and take a look how redhat does it -- they have it working b) be one of the first 8 people to ask me. I can't spend all my time replying but I'll answer 8 and only 8 specific questions about how it is on my redhat machine. Guys; there's nothing wrong with SystemD. It does some nice stuff. It gets round many problems and the startup time is amazing! Yes its a learning curve, one I'm still on, but I'm pleased with it. OK, I met it on a system - fedora 15 - where it "just works". But we should be able to learn from that.
We all, as regular users, have a responsibility to our favorite distribution to help out... it IS a community distribution after all.
Indeed. openSuse is still my favourite and favoured distribution. I run others for historic reasons and for learning/amusement. In this case I'd rather learn SystemD on a system where it works :-)
Not all of us are developers, but we are all users, and we can ALL test... every one of us, even if it means installing a virtual machine on a Sunday afternoon during the RC phase... commenting about how it wasn't tested enough doesn't help matters one iota. :-(
Indeed. And comparing something that doesn't work with something that does work to discover the differences is also a good exercise. I different circumstances I'd run two VMs :-) Sadly my laptop, my stable 11.4, doesn't have enough disk and memory for that, so I'm using a Salvation Army clunker to run Fedora with a small disk and lots of stuff NFS mounted to the laptop to make up for the lack of space :-/ Don't laugh; it works! And it demonstrates the flexibility and power of Linux. If you *DO* have the space to run two VMs and do a side-by-side then try it. -- You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions. -- Naguib Mahfouz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
Not all of us are developers, but we are all users, and we can ALL
test... every one of us, even if it means installing a virtual machine on a Sunday afternoon during the RC phase... commenting about how it wasn't tested enough doesn't help matters one iota.:-(
Indeed. And comparing something that doesn't work with something that does work to discover the differences is also a good exercise. I different circumstances I'd run two VMs:-) Sadly my laptop, my stable 11.4, doesn't have enough disk and memory for that, so I'm using a Salvation Army clunker to run Fedora with a small disk and lots of stuff NFS mounted to the laptop to make up for the lack of space :-/ Don't laugh; it works! And it demonstrates the flexibility and power of Linux.
If you*DO* have the space to run two VMs and do a side-by-side then try it.
I have a spare desktop system, where I normally install a new distro, before installing it on my main systems. However, in this case, I bought a new computer that wasn't fully supported in an earlier distro, so I installed 12.1 RC1 & 2, before the released version, so I used it for my testing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Nov 27, 2011 at 12:59:03PM +0100, lynn wrote:
12.1
Arch and desktopp environment are missing. Details of a report missing result in minus 20 points. ;)
I have to give the root password and the wpa password every time I turn on my laptop.
click on the plasmoid -> manage connections
plasmoid sounds like KDE. From a discussion on list or IRC - unfortunately I can't remember any longer - I have in mind a fix is on the way. Checked bugzilla and had not been able to find this one.
Choose connection and hit edit
A popup appears BEHIND the window (so you have no idea it's there) asking for the root password.
A popup appears 'No agents were available for this request'
Click OK
The Edit network connection window appears. Click on wireless security. The password has been deleted.
Reenter the password and it finally connects.
You have to do this evert time you boot. What a pain!
There is no easy workaround I can find. I see that this was the same in Factory with 12.1 trials. I thought about wicd but it's not easy to install on 12.1.
Anyone found a fix?
I only found this report and after reading all of what you wrote I'm no longer sure if this is the same issue as you see https://bugzilla.novell.com/show_bug.cgi?id=717158 If it is not please feel free to file a fresh one and in this case also quote the bug ID for reference here. Thanks. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Sunday 27 November 2011 12:59:03 lynn wrote:
12.1
I have to give the root password and the wpa password every time I turn on my laptop.
click on the plasmoid -> manage connections
Choose connection and hit edit
A popup appears BEHIND the window (so you have no idea it's
https://bugzilla.novell.com/show_bug.cgi?id=716291 (system default permissions bug, affects both KDE and GNOME, online update just released) there) https://bugzilla.novell.com/show_bug.cgi?id=732955 (fixed already, online update pending)
asking for the root password.
What is it asking for the root password for?
A popup appears 'No agents were available for this request'
Can you check if there is a process named polkit-kde-authentication-agent-1 running before you try to connect? (ctrl-escape to bring up the kde process list window)
Click OK
The Edit network connection window appears. Click on wireless security. The password has been deleted.
Reenter the password and it finally connects.
You have to do this evert time you boot. What a pain!
This sounds like you were unable to authorise storing the connection. a) this should not even be necessary, see bug 716291 linked above and b) if the auth agent crashed for some reason, it was not restarted, meaning subsequent auth requests failed. I have another online update pending for this issue. This is indicated if the auth agent is not present before you try to connect. Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, November 29, 2011 09:26:08 AM Will Stephenson wrote:
On Sunday 27 November 2011 12:59:03 lynn wrote:
12.1
I have to give the root password and the wpa password every time
I turn
on my laptop.
click on the plasmoid -> manage connections
Choose connection and hit edit
https://bugzilla.novell.com/show_bug.cgi?id=716291 (system default permissions bug, affects both KDE and GNOME, online update just released)
A popup appears BEHIND the window (so you have no idea it's
there)
https://bugzilla.novell.com/show_bug.cgi?id=732955 (fixed already, online update pending)
asking for the root password.
What is it asking for the root password for?
A popup appears 'No agents were available for this request'
Can you check if there is a process named polkit-kde-authentication-agent-1 running before you try to connect? (ctrl-escape to bring up the kde process list window)
Click OK
The Edit network connection window appears. Click on wireless
security.
The password has been deleted.
Reenter the password and it finally connects.
You have to do this evert time you boot. What a pain!
This sounds like you were unable to authorise storing the connection. a) this should not even be necessary, see bug 716291 linked above and b) if the auth agent crashed for some reason, it was not restarted, meaning subsequent auth requests failed. I have another online update pending for this issue. This is indicated if the auth agent is not present before you try to connect.
Will Yay! Lots of bug-fixes! -- Roger Luedecke openSUSE Ambassador Ind. Repairs and Consulting **Looking for a C++ etc. mentor*** -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Anton Aylward -
C -
James Knott -
Ken Schneider - openSUSE -
Lars Müller -
lynn -
Roger Luedecke -
Rüdiger Meier -
Will Stephenson