[opensuse] 13.1 Can't start new session
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this?
Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/17/2015 05:57 PM, Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252
Yeah, that's it, but it didn't happen that long ago. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott írta:
On 07/17/2015 05:57 PM, Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252
Yeah, that's it, but it didn't happen that long ago.
It happened to me also, when I had Xvnc display running. See: http://lists.opensuse.org/opensuse/2015-05/msg01046.html I guess the background might be the same bug. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/07/2015 11:16, Istvan Gabor a écrit :
It happened to me also, when I had Xvnc display running.
I noticed yesterday than my session is on F8, not F7 as usual, may be this is the problem (I can't either open a new session) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/18/2015 05:24 AM, jdd wrote:
I noticed yesterday than my session is on F8, not F7 as usual, may be this is the problem (I can't either open a new session)
No, that happens for one of a number of reasons. For me, its if i flip VTs while booting; impatient and want to see all that's going on. Somehow VT7 gets 'occupied' and so X start on VT8. Of course you can change your config to make it start on whatever VT you want ... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/17/2015 05:57 PM, Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252
The guy who's responsible for this seems to think we don't need this and so it won't be fixed. As I mentioned in the bug report, it works in 12.1, but not 13.1. Is there anyone who can get this guy off his butt to acknowledge there is a problem and do something about it, instead of saying we don't need it? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
works for me On 07/18/2015 05:47 PM, James Knott wrote:
On 07/17/2015 05:57 PM, Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252 The guy who's responsible for this seems to think we don't need this and so it won't be fixed. As I mentioned in the bug report, it works in 12.1, but not 13.1. Is there anyone who can get this guy off his butt to acknowledge there is a problem and do something about it, instead of saying we don't need it?
tnx jk
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
What version are you running? Others here have posted they also experience the problem. On 07/18/2015 06:11 PM, Hans Krueger wrote:
works for me
On 07/18/2015 05:47 PM, James Knott wrote:
On 07/17/2015 05:57 PM, Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252 The guy who's responsible for this seems to think we don't need this and so it won't be fixed. As I mentioned in the bug report, it works in 12.1, but not 13.1. Is there anyone who can get this guy off his butt to acknowledge there is a problem and do something about it, instead of saying we don't need it?
tnx jk
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Linux 3.11.10-29-desktop openSUSE 13.1 (Bottle) (x86_64 kde 4.11.5 On 07/18/2015 06:16 PM, James Knott wrote:
What version are you running? Others here have posted they also experience the problem.
On 07/18/2015 06:11 PM, Hans Krueger wrote:
works for me
On 07/18/2015 05:47 PM, James Knott wrote:
On 07/17/2015 05:57 PM, Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252 The guy who's responsible for this seems to think we don't need this and so it won't be fixed. As I mentioned in the bug report, it works in 12.1, but not 13.1. Is there anyone who can get this guy off his butt to acknowledge there is a problem and do something about it, instead of saying we don't need it?
tnx jk
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 19/07/2015 00:16, James Knott a écrit :
What version are you running? Others here have posted they also experience the problem.
for me it's on 13.2! on F7 I have the xorg logs and on F8 the actual session, so there is no other place for x session (I can open a simple F1 terminal) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 19/07/2015 12:58, jdd a écrit :
Le 19/07/2015 00:16, James Knott a écrit :
What version are you running? Others here have posted they also experience the problem.
for me it's on 13.2!
on F7 I have the xorg logs and on F8 the actual session, so there is no other place for x session (I can open a simple F1 terminal)
jdd
is I go to the kde menu (other user), I get the kdesu prompt, then nothing happen jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-19 12:58, jdd wrote:
on F7 I have the xorg logs and on F8 the actual session, so there is no other place for x session (I can open a simple F1 terminal)
Are you using plymouth? I think it does that. I always remove it. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWriZ4ACgkQja8UbcUWM1yAUQD9F4m2dmzVvlRve9oK+pQturO4 mQkda5Re507IycLUqaYA/1saMgqCHwEdgIsBnD77xMFO+uQI+Dz0Bjr+qqwIavjs =SIDj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 19/07/2015 13:27, Carlos E. R. a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-07-19 12:58, jdd wrote:
on F7 I have the xorg logs and on F8 the actual session, so there is no other place for x session (I can open a simple F1 terminal)
Are you using plymouth? I think it does that. I always remove it.
no idea. my 13.2 is no more stock (I use it to test things I answer on), but I only noticed this change user problem right now, I use it from time to time to test a fresh config thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-19 14:22, jdd wrote:
Le 19/07/2015 13:27, Carlos E. R. a écrit :
Are you using plymouth? I think it does that. I always remove it.
no idea. my 13.2 is no more stock (I use it to test things I answer on), but I only noticed this change user problem right now, I use it from time to time to test a fresh config
Well, the default is having it enabled. There is an option you can edit in grub (kernel line) to disable it for this boot (sorry, I searched for it but could not locate it in my notes), or remove the package. I do the later. You need to run mkinitrd to make the change. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWrmGMACgkQja8UbcUWM1x42wD/Yr93Q2S5mM1zhcAaqbBXWmaj bBeUD8v+zM2ctYSgkQkA/3XBdkdSeT5Az0FU9ykZnuTtinabmDSHRYvh5HntlbPD =ZazD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 19 Jul 2015 14:30, Carlos E. R. wrote:
On 2015-07-19 14:22, jdd wrote:
Le 19/07/2015 13:27, Carlos E. R. a écrit :
Are you using plymouth? I think it does that. I always remove it.
no idea. my 13.2 is no more stock (I use it to test things I answer on), but I only noticed this change user problem right now, I use it from time to time to test a fresh config
Well, the default is having it enabled. There is an option you can edit in grub (kernel line) to disable it for this boot (sorry, I searched for it but could not locate it in my notes), or remove the package. I do the later. You need to run mkinitrd to make the change.
(Search past mails....) Add this (without quotes, seperated by a space) to the kernel command line: "plymouth.enable=0", either temporary manual at boot time, or more permanent by adding it to the grub config file and running the needed command to write the modifed grub config. For the next shutdown after this, do not use suspend or hibernate, but reboot or halt (need to be said, pebkac is persitent). - Yamaban.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-19 14:46, Yamaban wrote:
On Sun, 19 Jul 2015 14:30, Carlos E. R. wrote:
(Search past mails....)
Thanks! - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWr1qoACgkQja8UbcUWM1x+JgD9ELjCjEdQ4UwNRYm9hcKYLJZ0 DZVj7SG5/QIrZmCqW+oA/iBBi08ILFDfEbrFaZV8IumhMTGm6oGsIAAh3z3U4khj =EKZT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/07/15 23:47, James Knott wrote:
On 07/17/2015 05:57 PM, Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this? Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252
The guy who's responsible for this seems to think we don't need this and so it won't be fixed. As I mentioned in the bug report, it works in 12.1, but not 13.1. Is there anyone who can get this guy off his butt to acknowledge there is a problem and do something about it, instead of saying we don't need it?
tnx jk
In my experience of reading this mailing list and other sources over several years, the developer you refer to is one of those few who does actually 'get off his butt' to resolve problems. However, as he states in the bug report, it's a very strange use case that is liable to cause no end of problems elsewhere. If you had it working under 12.1 that may be a miracle more than a result of precision engineering. I get frustrated too with the number of WONTFIX and lack of developer input elsewhere, but on this occasion I'll just offer my advice that I don't think claiming that this developer would have been fired if he worked for a commercial entity rather than off his own good will for nothing at all, is going to reap dividends. ;) gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/18/2015 06:31 PM, gumb wrote:
I'll just offer my advice that I don't think claiming that this developer would have been fired if he worked for a commercial entity
Having worked at IBM, I can state with certainty that would be grounds for a severe reprimand, if not dismissal. If I couldn't fix something, I had to document why and provide a work around if possible. This you don't need it so I won't fix it attitude would soon see me heading out the door. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2015-07-18 17:47 (UTC-0400):
Felix Miata wrote:
James Knott composed on 2015-07-17 17:16 (UTC-0400):
I lately noticed that I can no longer start a new desktop session in 13.1. When I try, I wind up back in the original session. Has anyone else noticed this?
Maybe like this? https://bugzilla.opensuse.org/show_bug.cgi?id=877252
The guy who's responsible for this seems to think we don't need this and so it won't be fixed. As I mentioned in the bug report, it works in 12.1, but not 13.1.
If 12.1 worked for same user, and known about, that probably would have been considered a bug by upstream and the OS devs other than Wooninck. Remote desktop failure is even further distinct. If there isn't one already, file one, if you can, or you can get someone else to, duplicate the problem in 13.2 or TW or Leap. For 13.1 we're stuck where we are except for security fixes, particularly for long feature-frozen KDM.
Is there anyone who can get this guy off his butt to acknowledge there is a problem and do something about it, instead of saying we don't need it?
For other users, it's a different bug, as Wooninck wrote in the bug. What exactly is the failure mode for other users, crash? Error message? Dumped back to current user? Maybe the only problem is kdmrc needs adjusting. For currently logged in user, I agree it's a bad idea and agree WONTFIX is appropriate, shouldn't be supported by the login manager. What happens if you login on a vtty and try 'startx -- :1'? If that works, you might try a different login manager. If using KDM4, try KDM3 or TDM for familiarity, or LXDM, or even GDM. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/18/2015 06:36 PM, Felix Miata wrote:
For currently logged in user, I agree it's a bad idea and agree WONTFIX is appropriate, shouldn't be supported by the login manager.
DUH? Suppose this wasn't X Suppose it was just logging in, à la plain old UNIX from the PDP-11 days, with a VT100 over a RS-232 line. The go to the next seat in the terminal room and log in again using the same ID. Now suppose you're at some conference in the late 1990s where the terminal room is full of X terminals (think: 'thin clients' running X) courtesy of SUN, HP or more likely Network Computing Devices (who lasted until 2004). You log in on one of those. Now, one gain, you move to the next seat and log in again. In each of those use-cases you can log in with the same ID/credentials to the same host machine. I won't presume to go into WHY you want to do that any more than the fact that I have six tabs open on my konsole and a root login on VT1 and a another root login on VT2 running Htop. I think that "why would you want to do that" as a straight forward question, as might be asked to many issues on this forum is reasonable. Sometimes we might offer a better way or a work around. But asking it as a put down, claiming without asking details that your use case is unreasonable, ridiculous or similar, especially when it comes from someone as experienced as James seems to me to be a bit ... well ... off. We all know that there are many later version programs, games are a good example, that have to replicate idiosyncrasies & shortcomings of the original on another platform. A poster boy for that might be OpenOffice having to replicate many of the idiosyncrasies of MS-Word. UNIX has a long history of very good, very powerful word processing. A key part of its ancestry/justification was being the document processing system for the legal department at Bell Labs. One of the problems of OpenOffice was that it nested indents/bullet-lists/subparagraphs properly whereas MS-word didn't. OUCH. But then different versions of MS-Word formatted pages differently too! Again, even though VIM as a rewrite of the old VI of Bill Joy of 1976 era cleaning up same horrible code (I recall in 1983 having to patch it under SYSTEM V) and adding many capabilities, but had to have a "compatibility mode" to replicate the original VI's shortcomings and bugs for the applications that depended on it. Personally I think James is in the right here when he asks for this to have consistent behaviour. Mind you, calling the developer unprofessional when he's dealing with FOSS rather than a BigCorp with more vigour conformance, reporting and testing, is a bit overstepping the mark. If the developer has said "I don't have tome to fix it, how about you do it", then that's another matter. That's what FOSS is about. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2015-07-19 08:36 (UTC-0400):
Felix Miata wrote:
For currently logged in user, I agree it's a bad idea and agree WONTFIX is appropriate, shouldn't be supported by the login manager.
DUH?
Suppose this wasn't X
Not X is a different mix of issues. Any power user can be expected to have >1 concurrent vtty login, but each is conventionally WRT settings dynamics doing something independent from what others are doing, and all are not necessarily active simultaneously or otherwise stepping on other I/O process space. OTOH, the WM is constantly accounting for changes in various changes in windows open, window sizes, window movements and focus changes. Unless the WM is specifically designed to manage having all that going on simultaneously in separate instances one can expect various types of errant and unwanted behavior as logging in and out and opening and closing and moving windows proceeds. Unless upsteam WM is specifically supporting multiple X sessions by same user, it's emminently reasonable for a packager not to try to provide such support himself. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On July 19, 2015 5:36:13 AM PDT, Anton Aylward
On 07/18/2015 06:36 PM, Felix Miata wrote:
For currently logged in user, I agree it's a bad idea and agree WONTFIX is appropriate, shouldn't be supported by the login manager.
DUH?
Suppose this wasn't X Suppose it was just logging in, à la plain old UNIX from the PDP-11 days, with a VT100 over a RS-232 line. The go to the next seat in the terminal room and log in again using the same ID.
Now suppose you're at some conference in the late 1990s where the terminal room is full of X terminals (think: 'thin clients' running X) courtesy of SUN, HP or more likely Network Computing Devices (who lasted until 2004). You log in on one of those. Now, one gain, you move to the next seat and log in again.
In each of those use-cases you can log in with the same ID/credentials to the same host machine.
I won't presume to go into WHY you want to do that any more than the fact that I have six tabs open on my konsole and a root login on VT1 and a another root login on VT2 running Htop.
I think that "why would you want to do that" as a straight forward question, as might be asked to many issues on this forum is reasonable. Sometimes we might offer a better way or a work around. But asking it as a put down, claiming without asking details that your use case is unreasonable, ridiculous or similar, especially when it comes from someone as experienced as James seems to me to be a bit ... well ... off.
We all know that there are many later version programs, games are a good example, that have to replicate idiosyncrasies & shortcomings of the original on another platform. A poster boy for that might be OpenOffice having to replicate many of the idiosyncrasies of MS-Word. UNIX has a long history of very good, very powerful word processing. A key part of its ancestry/justification was being the document processing system for the legal department at Bell Labs. One of the problems of OpenOffice was that it nested indents/bullet-lists/subparagraphs properly whereas MS-word didn't. OUCH. But then different versions of MS-Word formatted pages differently too!
Again, even though VIM as a rewrite of the old VI of Bill Joy of 1976 era cleaning up same horrible code (I recall in 1983 having to patch it under SYSTEM V) and adding many capabilities, but had to have a "compatibility mode" to replicate the original VI's shortcomings and bugs for the applications that depended on it.
Personally I think James is in the right here when he asks for this to have consistent behaviour. Mind you, calling the developer unprofessional when he's dealing with FOSS rather than a BigCorp with more vigour conformance, reporting and testing, is a bit overstepping the mark. If the developer has said "I don't have tome to fix it, how about you do it", then that's another matter. That's what FOSS is about.
A long but well spoken rant. Quoted full length here to point out just how long it was. But also quoted full length in the hope some will find this thread via the Google Spider and realize that when the historical expectation suddenly stops working people have a reasonable expectation of an explanation rather than an implied "stop doing that (you idiot)" Linux has always been a multi user, AND multi session system and multi login sessions have worked right up to recent-ish times. There was no announced dropping of this capability. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-19 14:36, Anton Aylward wrote:
On 07/18/2015 06:36 PM, Felix Miata wrote:
For currently logged in user, I agree it's a bad idea and agree WONTFIX is appropriate, shouldn't be supported by the login manager.
DUH?
Suppose this wasn't X Suppose it was just logging in, à la plain old UNIX from the PDP-11 days, with a VT100 over a RS-232 line. The go to the next seat in the terminal room and log in again using the same ID.
Now suppose you're at some conference in the late 1990s where the terminal room is full of X terminals (think: 'thin clients' running X) courtesy of SUN, HP or more likely Network Computing Devices (who lasted until 2004). You log in on one of those. Now, one gain, you move to the next seat and log in again.
Yes, you can do this today, log in one Linux machine to a session in another Linux machine, graphically. I have done this in the past, it should work, but I haven't tried recently. However, this is not login in the same "seat" or machine. That is, one session in terminal 7, another in terminal 8. And I wonder if current desktop designers have thought much about this scenario, because then they must separate temporary files according to the seat, not the user. But what to do about configuration and preference files, that are "per user"? It is a bit of a problem, so I wouldn't be surprised some consider this as "not supported". - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWr2CMACgkQja8UbcUWM1xDfwD+MWZKO4tsXqgJaayhxN2bcQVm lbkHhtdIwNU472TeZaEA/2XHEZl+y42wa+XaISBMZ+YMekbtzZNglwDs4pH31y/f =/6Hg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Anton Aylward
-
Carlos E. R.
-
Felix Miata
-
gumb
-
Hans Krueger
-
Istvan Gabor
-
James Knott
-
jdd
-
John Andersen
-
Yamaban