http://bugzilla.opensuse.org/show_bug.cgi?id=877252
http://bugzilla.opensuse.org/show_bug.cgi?id=877252#c6
--- Comment #6 from Raymond Wooninck
1) I mentioned this issue on the openSUSE mail list, where others also said they had the same problem, one pointed me to this thread. Whether it's one user or more than one trying to start a new session is irrelevant, as it used to work with either.
Well, there is a difference. Starting a new session as the same user could have quite some impact on the whole system. How would the system now which temp file belongs to which session. Opening the same temp-file twice could result in unwanted behavior and therefore this could have been blocked by the developers.
3) I have worked in IT for over 40 years, including 3rd level support at IBM Canada. If I ever told someone that they didn't need something that broke, instead of making some attempt to fix it, I would have been fired!
Good for you. But please do not compare that situation with the reality here. You were PAID to do that job, while we are talking now about volunteers that in their FREE TIME doing something that they are not getting paid for and on top of it the work they do is unappreciated. All these volunteers have a normal PAID job that has nothing to do with openSUSE/SUSE, so keep this in mind !!
Now, both multiple sessions and remote desktops used to work. Now neither do. So, why are they now broken and why aren't they being fixed.
I'm running stock 13.1 evergreen.
That means you are running with a KDE version that is no longer supported upstream. I know that you will come up with the fact that evergreen is supported, blablablah. But this also heavily depends if we have developers/programmers who can actually fix those things. For KDE we do not have this luxury and the volunteers here are relying on the KDE developers upstream. That is also why I mentioned to file a bug report upstream. For KDM the supported
FWIW, I just popped a live 12.1 disc into my notebook computer and I can create more than one session with the same ID. So, this clearly worked in 12.1, but is broken in 13.1. Why is that???
One again, this is a real defect. Please stop marking it WONTFIX. Just get going and investigate it. Your attitude would have got you fired at IBM and elsewhere. Well, then you start paying for support. You demand support like IBM and others will provide. You are indicating that you would fire me, from a job that I do not even have nor get paid for. But on the other hand you are not willing to
Good question.And that is why I asked to test it with another login manager, to see if this is KDM's issue or that it something else in the system. pay for the product. Do you really believe that IBM would support a product that customers are not paying for ? Just to stay in the comparison that you are trying to make. I have several dealing with IBM and I know for sure that a free product comes with the guarantee that commercial companies will not support. The volunteers are doing the best they can, but it seems that the support requested should be equal or even better than a paying job. Real fair, right. -- You are receiving this mail because: You are on the CC list for the bug.