[Bug 715265] New: Unable to Remote Login from Greeter
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c0 Summary: Unable to Remote Login from Greeter Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: 64bit OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: cmcgrath5035@comcast.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 System is Linux PVE-LinuxSRV5 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux I recently upgraded to KDE4.7 from the 11.4/kde47 repository. When at the KDE Greeter (login) dialog screen, I select Menu-Remote Login (or alt-R, same result). An XDMCP Host Window opens displaying other machines on my network that are up and willing to accept Xdmcp login. When I move the mouse over the XDMCP Host Window to select a remote host, the widow closes and I am returned to the normal login screen. I have the same result on three different systems once upgraded to KDE47. All worked fine when KDE46 and earlier. I am able to login to the remote machines via the CLI using ssh ipaddress Reproducible: Always Steps to Reproduce: 1.Boot openSuSE 11.4/KDE47 2.AT Greeter (login) screen, select Menu-Remote Login (or alt-R) 3.XDMCP Host Window opens, displaying hosts willing to accept login 4. Move mouse over the XDMCP Host Window, window disappears. Actual Results: The XDMCP Host Window disappears, I am back at the normal login window. I am able to login to the local machine. Expected Results: I should be able to select a remote machine and start a remote X session This procedure worked KDE46 and earlier -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c1 James Knott <james.knott@rogers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |james.knott@rogers.com --- Comment #1 from James Knott <james.knott@rogers.com> 2011-10-28 02:42:22 UTC --- This is also happening in 12.1 RC1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c2 --- Comment #2 from James Knott <james.knott@rogers.com> 2011-11-04 22:21:50 UTC --- And now 12.1 RC2. It sure would be nice if this bug is fixed, as this is something I use frequently. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c James Knott <james.knott@rogers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |728478 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c3 --- Comment #3 from Christian Trippe <ctrippe@opensuse.org> 2011-11-05 05:05:24 UTC --- *** Bug 728478 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=728478 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c Christian Trippe <ctrippe@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ctrippe@opensuse.org Component|KDE4 Workspace |KDE4 Workspace Version|Final |RC 1 Product|openSUSE 11.4 |openSUSE 12.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c4 Christian Trippe <ctrippe@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://bugs.kde.org/show_b | |ug.cgi?id=281862 --- Comment #4 from Christian Trippe <ctrippe@opensuse.org> 2011-11-10 04:11:35 UTC --- This is the following upstream issue https://bugs.kde.org/show_bug.cgi?id=281862 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c5 --- Comment #5 from Lars Müller <lmuelle@suse.com> 2011-12-06 18:27:27 CET --- If this is still the case with the released openSUSE 12.1 please update the 'Version' field to final. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c James Knott <james.knott@rogers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|RC 1 |Final -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c6 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volker3204@paradise.net.nz --- Comment #6 from Volker Kuhlmann <volker3204@paradise.net.nz> 2012-06-27 08:37:36 NZST --- The upstream issue mentioned in #c4 is correct. However applying the patch https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/da6... (as mentioned in kde #281862) which is made for 4.8 to the 4.7.2 used in oS 12.1 and recompiling kdebase4-workspace is an incomplete fix. The chooser window now opens, but only shows the local host to select. Because all keyboard input is dead from then on no other host can be entered. Essentially the remote login feature in 12.1 is broken and useless. The dead keyboard problem has existed in previous oS versions too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c7 Christian Trippe <ctrippe@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #7 from Christian Trippe <ctrippe@opensuse.org> 2014-08-01 07:54:49 UTC --- Sorry that this bug did not get solved. However openSUSE 12.1 is no longer supported. Therefore I am closing this report. If the bug is reproducable with a later version please reopen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c8 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #8 from Wolfgang Bauer <wbauer@tmo.at> 2014-08-01 08:32:56 UTC --- The originally reported issue that KDM crashes when you move the mouse over the "remote hosts" window is fixed in 13.1 at least (I think in 12.3 as well). It still doesn't accept any keyboard input though (as mentioned in comment#6). But there are several other bug reports about that, both here and upstream (see bnc#772344 f.e.), so I think this one can safely be kept closed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c9 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|KDE4 Workspace |KDE4 Workspace Resolution|WONTFIX | Product|openSUSE 12.1 |openSUSE 12.3 Target Milestone|--- |Final OS/Version|openSUSE 11.4 |openSUSE 12.3 --- Comment #9 from Volker Kuhlmann <volker3204@paradise.net.nz> 2014-08-01 21:01:26 NZST --- Well, not ever looking at a bug then closing with "obsolete product" may please product managers, and never mind the users... ;-) This is the only way to use thin client terminals (all the others suck). Suse decides to use kdm as login manager, and this functionality hasn't been working for years! Whether someone fixes a kdm crash is irrelevant to me unless the functionality, suddenly broken with version xyz, is restored. When kdm doesn't accept any keyboard input (or some of the mouse input) I don't care whether it crashes as well. It's still useless. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c10 --- Comment #10 from Wolfgang Bauer <wbauer@tmo.at> 2014-08-01 10:07:41 UTC --- (In reply to comment #9)
Well, not ever looking at a bug then closing with "obsolete product" may please product managers, and never mind the users... ;-)
First, I don't care about "pleasing product managers", as I am a volunteer. Second, this is an upstream bug/problem in KDM, and it is reported upstream. As I said, there are other bug reports about this, no real need to keep this one open as well.
This is the only way to use thin client terminals (all the others suck). Suse decides to use kdm as login manager, and this functionality hasn't been working for years!
Yes, but no-one prevents you to use a different one. And regarding "Suse decides to use kdm as login manager": that's of course only the case if you install the KDE desktop initially on a fresh install. If you choose any other option at installation time, other login managers are installed/used.
Whether someone fixes a kdm crash is irrelevant to me unless the functionality, suddenly broken with version xyz, is restored. When kdm doesn't accept any keyboard input (or some of the mouse input) I don't care whether it crashes as well. It's still useless.
Again, the keyboard issue is reported in other bug reports as well (both in this bugzilla and in KDE's bugzilla), so no need to keep this one open I'd say. Anyway, I don't mind whether this bug is open or closed. It wasn't me who closed it anyway. I just stated that it is ok to close it IMHO. That said: I have no idea whether the remote login functionality actually would work if you could enter a hostname manually. And I don't use XDMCP at all. But I suppose the "keyboard bug" (actually it seems to be a input focus issue) would have to be fixed first to check that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c11 Christian Trippe <ctrippe@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |DUPLICATE --- Comment #11 from Christian Trippe <ctrippe@opensuse.org> 2014-08-01 11:03:51 UTC --- (In reply to comment #9)
Well, not ever looking at a bug then closing with "obsolete product" may please product managers, and never mind the users... ;-)
To only restate what Wolfgang said: I don't care about "pleasing product managers", as I am a volunteer. I am even not aware of an openSUSE product manager I would have made happy by closing the bug. I just try to clean up the bug database or do you think that bugs for outdated versions help anybody? The KDE maintainers in openSUSE do not use every software they package so they depend also on the bug reporter to update their report if a bug is solved with a later release or does still exist. As the crash was fixed let's close this report as a duplicate of another report about the same issue. *** This bug has been marked as a duplicate of bug 859711 *** http://bugzilla.novell.com/show_bug.cgi?id=859711 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c12 --- Comment #12 from Volker Kuhlmann <volker3204@paradise.net.nz> 2014-08-01 23:52:49 NZST ---
As the crash was fixed let's close this report as a duplicate of another report about the same issue.
As Wolfgang and I both tried to explain, this bug report is about remote login from greeter. Most definitely NOT fixed. The crash doesn't remove any functionality when present nor adds any when absent. I can't say what internas of kdm are affected but I can say that this hasn't worked in at least opensuse 11.x, 12.x whereas it did before. XDMCP used to just work. Ok, never mind audio forwarding, but it was usable, which can't be said for VNC with major rendering errors - no good for the LAN. Happy to keep it as bug#859711. James describes my position perfectly! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c13 --- Comment #13 from Wolfgang Bauer <wbauer@tmo.at> 2014-08-01 12:12:01 UTC --- (In reply to comment #12)
The crash doesn't remove any functionality when present nor adds any when absent.
That's untrue of course. ;) If the remote hosts window would show remote hosts, you still could not select one because of the crash. So it effectively does remove the functionality as well.
XDMCP used to just work. Ok, never mind audio forwarding, but it was usable, which can't be said for VNC with major rendering errors - no good for the LAN.
I did use it in earlier versions 10.x, IIRC also some 11.x version(s). But I haven't since some years ago (at that time it _was_ still working though, even with KDM). But AFAIK this is "just" a kdm problem (at least the keyboard input problem is). XDMCP itself might work fine. Maybe try with GDM to verify? (I think GDM supports remote login via XDMCP as well) Would be interesting to know anyway whether the problem is specific to KDM or there's a general XDMCP issue (which should be reported as bug against a different component than KDE4 then of course, I suppose Xorg). And what VNC rendering errors are you talking about? I did use VNC interchangeably with XDMCP back then (on the LAN). Anyway, further details and information about the bug should be posted in other bug reports now that are still open. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c14 --- Comment #14 from Volker Kuhlmann <volker3204@paradise.net.nz> 2014-08-02 11:34:35 NZST ---
(In reply to comment #12) If the remote hosts window would show remote hosts, you still could not select one because of the crash. So it effectively does remove the functionality as well.
From looking at login managers some while back I got the distinct impression
The crash is not the only bug that removes remote login functionality, hence fixing it makes zero difference to the functionality being available, the problem being fixed and this bug being dealt with! Yes I expect it to be just a kdm problem as well. Changes that caused the crash also caused other (still to be fixed) problems. Difficult to test whether XDMCP still works if one doesn't even get as far as opening that connection... that suse always uses kdm, regardless of desktop. I may have been wrong, and it may be different now.
And what VNC rendering errors are you talking about? I did use VNC interchangeably with XDMCP back then (on the LAN).
Big bitmap block rendering errors, requiring turning off various of the VNC protocol features. Unusable UI, useless performance. Both vncviewer and krdc clients. Would like to know what clients and servers you used - thanks!
Anyway, further details and information about the bug should be posted in other bug reports now that are still open.
Other than bug 859711? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c15 --- Comment #15 from Wolfgang Bauer <wbauer@tmo.at> 2014-08-02 00:43:30 UTC --- (In reply to comment #14)
The crash is not the only bug that removes remote login functionality, hence fixing it makes zero difference to the functionality being available, the problem being fixed and this bug being dealt with!
So what? To follow your reasoning: The input focus issue and the automatic display of remote hosts have not been the only bugs that remove remote login funcionality, hence fixing them would have made zero difference to the functionality being available... (if that crash would still be present, that is) Anyway, it was KDE upstream who fixed that crash. Do you want openSUSE to revert that? :-P If you argue that way, nothing at all should be fixed here. I don't think that's what you have in mind. You have your open bug report anyway with bnc#859711. What sense does this discussion make? None at all. So that's it now for me.
Yes I expect it to be just a kdm problem as well. Changes that caused the crash also caused other (still to be fixed) problems. Difficult to test whether XDMCP still works if one doesn't even get as far as opening that connection...
As I said, you could test XDMCP by using a different display manager f.e. That would be more productive than this discussion here.
From looking at login managers some while back I got the distinct impression that suse always uses kdm, regardless of desktop. I may have been wrong, and it may be different now.
I doubt that you ever got KDM when choosing GNOME during installation or installed from the GNOME LiveCD. Btw, if there only ever was KDM on (open)SUSE, then why have there been all those display manager settings in /etc/sysconfig/? People even complained and filed bug reports for years that KDM's settings are not respected. The purpose of that was to have one configuration place for _all_ different display managers. That would not have been necessary or even reasonable if (open)SUSE always used KDM.
Big bitmap block rendering errors, requiring turning off various of the VNC protocol features. Unusable UI, useless performance. Both vncviewer and krdc clients. Would like to know what clients and servers you used - thanks!
As server whatever was installed/used by default when you enabled VNC in YaST. As client I mostly used KRDC, but also the Java client you get when you open http://host:5901 in a web browser. With both I didn't see rendering errors and never had to change any server or client settings. And it was usable, even via HTTP/java. And then of course I often used (and still use) ssh with X forwarding.
Anyway, further details and information about the bug should be posted in other bug reports now that are still open.
Other than bug 859711?
No, exactly in 859711 e.g. if it is fitting there. But you may of course also add something to an upstream bug report. And if for example you find out that there's a problem with the XDCMP _server_ part, you should open a new bug report for that though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c16 --- Comment #16 from Volker Kuhlmann <volker3204@paradise.net.nz> 2014-08-02 13:57:06 NZST --- (In reply to comment #15) I never said bugs shouldn't be fixed. I said closing problem reports when 1 out of 3 bugs are fixed doesn't do anything for the user. Kudos to the bug fixer of course, but no difference to the end user when the problem only changed colour. Read the *title* of this report!
As I said, you could test XDMCP by using a different display manager f.e.
That would test the remote host XDMCP server, but not the kdm XDMCP client, which I understand is under discussion here. But I'll do some virtualbox experiments. Thanks for your tips re VNC clients! Yes ssh X11 is very good (takes some scripting with KDE for dbus stuff) but operates at the application level. In use all the time here, but often I want the desktop and that doesn't seem to work over ssh (or at least I haven't found what programs I'd need to start) and whether that interferes with the local desktop negatively (1 panel obscuring the other e.g.). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c17 --- Comment #17 from Wolfgang Bauer <wbauer@tmo.at> 2014-08-02 10:14:54 UTC --- (In reply to comment #16)
Read the *title* of this report!
And you read the *state* of this report! This bug report has not been closed because that crash has been fixed. That's old news already. This bug report is marked as duplicate of bug#859711 now, which is still open. And you yourself stated that the other bug report perfectly describes the situation. It makes no sense to have two bug reports open about the exact same issue. There's nothing further to discuss here about this. So please stop it. And btw, the original report here states: "An XDMCP Host Window opens displaying other machines on my network that are up and willing to accept Xdmcp login. When I move the mouse over the XDMCP Host Window to select a remote host, the widow closes and I am returned to the normal login screen." So this bug report originally was about that crash that got fixed. Unfortunately since then something else broke apparently, i.e. the display/search of remote hosts.
As I said, you could test XDMCP by using a different display manager f.e.
That would test the remote host XDMCP server, but not the kdm XDMCP client, which I understand is under discussion here. But I'll do some virtualbox experiments. Well, the reason for KDM not showing any remote hosts could actually be a XDMCP server problem.
And it would provide a work around for you... ;) [QUOTE]> Thanks for your tips re VNC clients! [/QUOTE] RDP would be another option of course. Or NX. But I never tried any of those. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c18 --- Comment #18 from Wolfgang Bauer <wbauer@tmo.at> 2014-08-02 11:01:32 UTC ---
As I said, you could test XDMCP by using a different display manager f.e. PS: You don't even need a display manager for connecting to a XDCMP server. There are other clients as well.
For example, remmina has a XDMCP plugin, it's in the package "remmina-plugins-xdmcp". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c19 --- Comment #19 from Volker Kuhlmann <volker3204@paradise.net.nz> 2014-08-04 13:26:18 NZST --- After KDE's refusal to perform any XDMCP login at all I tried all the other remote desktop clients you mentioned. For one reason or another, they all sucked hamsters. As for "Unable to Remote Login from Greeter" being status: RESOLVED, that's plain nonsense. I am a user. As long as it doesn't work I don't care about blabla that only shunts bug reports around or precisely why it hasn't worked in years. But I do accept "not enough developers" as an explanation. It is extremely obvious no KDE developer has tried to set up a minimal test case of xdmcp in years. Sometimes Microsoft does work better out of the box :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugzilla.novell.com/show_bug.cgi?id=715265#c20 --- Comment #20 from Wolfgang Bauer <wbauer@tmo.at> 2014-08-04 06:25:56 UTC --- (In reply to comment #19)
After KDE's refusal to perform any XDMCP login at all I tried all the other remote desktop clients you mentioned. For one reason or another, they all sucked hamsters.
So they suck. But more interesting would be whether XDMCP worked or not. You should also be able to manually start an additional X server that connects to the remote host. Have a look here: https://wiki.ubuntu.com/xdmcp
As for "Unable to Remote Login from Greeter" being status: RESOLVED, that's plain nonsense.
A last time: This bug report has the status RESOLVED DUPLICATE, because it is a duplicate of bug#859711. What's yout problem with that? Again, you yourself stated that it is a duplicate. If you suddenly don't think it is a duplicate, feel free to reopen it. But better have a good explanation why you think it is not a duplicate. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com