[Bug 774386] New: no vnc login offered after vnc installation
https://bugzilla.novell.com/show_bug.cgi?id=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c0 Summary: no vnc login offered after vnc installation Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ohering@suse.com QAContact: jsrain@suse.com Found By: Outsourced Testing Blocker: --- logs in bug #774379 I did a vnc+ssh installation of 12.2-rc2. After installation 'vncviewer stein-schneider:1' does not work. nmap shows that only ssh port is open. A vnc instllation has to enable vnc per default, like it used to do that since SLES7. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfilka@suse.com AssignedTo|yast2-maintainers@suse.de |fcrozat@suse.com -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c1 --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2012-08-06 07:55:57 UTC --- by "after installation", you mean for second stage in Yast, right ? was firewall enabled in the installation ? -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c2 --- Comment #2 from Olaf Hering <ohering@suse.com> 2012-08-06 10:20:53 CEST --- I'm sure I disabled it. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c3 --- Comment #3 from Frederic Crozat <fcrozat@suse.com> 2012-08-06 08:44:37 UTC --- we had issue with 12.1 where firewall was started too early, preventing ssh installation but this should be fixed. I'll try to duplicate vnc install in a VM -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c4 --- Comment #4 from Olaf Hering <ohering@suse.com> 2012-08-06 12:07:06 CEST --- thats wha I get on another system were firewall was really disabled: Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:34994 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN tcp 0 0 :::39859 :::* LISTEN tcp 0 0 :::22 :::* LISTEN tcp 0 0 :::631 :::* LISTEN tcp 0 0 ::1:25 :::* LISTEN tcp 0 0 ::1:6010 :::* LISTEN udp 0 0 0.0.0.0:5353 0.0.0.0:* udp 0 0 0.0.0.0:39483 0.0.0.0:* udp 0 0 192.168.2.81:123 0.0.0.0:* udp 0 0 127.0.0.1:123 0.0.0.0:* udp 0 0 0.0.0.0:123 0.0.0.0:* udp 0 0 0.0.0.0:631 0.0.0.0:* udp 0 0 :::5353 :::* udp 0 0 :::51085 :::* udp 0 0 ::1:123 :::* udp 0 0 fe80::baac:6fff:fea:123 :::* udp 0 0 :::123 :::* udp 0 0 :::177 :::* -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c5 --- Comment #5 from Olaf Hering <ohering@suse.com> 2012-08-06 13:22:10 CEST --- I tried to enable 'Remote Administration (VNC)' with yast ncurses and found it was already enabled. After yast there was an xinetd process and the ports 5801/5901 were open. connect with vncviewer initially works, but the connection is dropped once the green background is drawn. So there is yet another bug, perhaps GNOME related. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c6 --- Comment #6 from Olaf Hering <ohering@suse.com> 2012-08-06 18:07:30 CEST --- I will retest once more, it seems that it happens only after initial boot. After a seond reboot xinetd starts and vncviewer can connect. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c7 --- Comment #7 from Frederic Crozat <fcrozat@suse.com> 2012-08-06 16:36:01 UTC --- Some dependencies are probably missing in YaST2-Second-Stage.service (in the After and Before sections) -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c8 --- Comment #8 from Olaf Hering <ohering@suse.com> 2012-08-06 19:49:29 CEST --- In first and second stage vncviewer works well. It happens only after second stage, not after subsequent reboots. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c9 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #9 from Frederic Crozat <fcrozat@suse.com> 2012-08-09 08:54:26 UTC --- xinetd service is being enabled by yast2 second stage but not started at that time. This was probably working when using sysvinit because Yast2 Second stage was started before all initscripts but under systemd, it won't work (since YaST2 Second Stage is a service like others) unless it is started by YaST itself. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c11 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ohering@suse.com --- Comment #11 from Jiří Suchomel <jsuchome@suse.com> 2012-08-10 06:45:18 UTC --- So, is xinetd needed only for VNC installation? Than I assume it should be stopped after it. Arvin, what do you think about this patch? Olaf, could you test it? It's for /usr/lib/YaST2/startup/Second-Stage/S08-start diff --git a/startup/Second-Stage/S08-start b/startup/Second-Stage/S08-start index 1722773..5efd268 100755 --- a/startup/Second-Stage/S08-start +++ b/startup/Second-Stage/S08-start @@ -25,7 +25,13 @@ if [ "$VNC" -eq 1 ] || [ -z "$USE_SSH" ] || [ "$USE_SSH" -eq 0 ] ; then if [ ! -z "$VNC" ] && [ "$VNC" -eq 1 ] ; then vnc_message fi + if [ -x /usr/sbin/rcxinetd ] ; then + /usr/sbin/rcxinetd start + fi startYaST2 + if [ -x /usr/sbin/rcxinetd ] ; then + /usr/sbin/rcxinetd stop + fi else -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c12 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ohering@suse.com | --- Comment #12 from Olaf Hering <ohering@suse.com> 2012-08-10 09:30:19 CEST --- (In reply to comment #11)
So, is xinetd needed only for VNC installation? Than I assume it should be stopped after it.
No, what is supposed to happen is that during a vnc installation vncviewer must be able to connect during first and second stage. This part is working fine in 12.2-rc2. But during second stage the 'Remote Administration' option is supposed to be enabled per default so that one can connect right away once installation is done. That part is partly broken because it works currently only after yet another reboot. I think the reason is, as stated in a previous comment, that systemd seems to run most of the "stuff" before second stage starts. As a result xinetd is not running anymore right after second stage, even if its appearently enabled.
Arvin, what do you think about this patch? Olaf, could you test it? It's for /usr/lib/YaST2/startup/Second-Stage/S08-start
That patch is not needed because it does not solve the issue. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c13 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ohering@suse.com --- Comment #13 from Jiří Suchomel <jsuchome@suse.com> 2012-08-10 07:45:32 UTC --- Well, the patch should start xinetd before starting YaST in second stage. I probably do not understand: when exactly does it need to be running and it is not? -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c14 --- Comment #14 from Olaf Hering <ohering@suse.com> 2012-08-10 09:59:30 CEST --- (In reply to comment #13)
Well, the patch should start xinetd before starting YaST in second stage.
I probably do not understand: when exactly does it need to be running and it is not?
Right after second stage, if 'Remote Administration' is enabled. I will double check wether this setting is really enabled during second stage. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c15 --- Comment #15 from Jiří Suchomel <jsuchome@suse.com> 2012-08-10 08:14:56 UTC --- Well, than the first part of the patch (starting of xinetd) should help. It could be also later in the sequence, like just before YaST finishing, but starting it before should not harm. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c16 --- Comment #16 from Olaf Hering <ohering@suse.com> 2012-08-10 19:59:09 CEST --- I tested it once more. During second stage vnc runs fine, one can connect and interact with yast. The 'Remote Administration' knob is enabled per default, as expected. Once yast finishes the vnc port is not accessible anymore. If I reboot and boot again into runlevel 5 then vnc connection is offered. I will try it once more with relevant parts of the patch above. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c17 --- Comment #17 from Jiří Suchomel <jsuchome@suse.com> 2012-09-20 09:32:21 UTC --- Any news? -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c18 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|ohering@suse.com | Resolution| |NORESPONSE --- Comment #18 from Jiří Suchomel <jsuchome@suse.com> 2013-01-04 12:11:28 UTC --- OK, closing as no response... -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c19 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Component|Installation |Installation Version|RC 2 |Final Resolution|NORESPONSE | AssignedTo|jsuchome@suse.com |yast2-maintainers@suse.de Product|openSUSE 12.2 |openSUSE 13.1 --- Comment #19 from Olaf Hering <ohering@suse.com> 2013-12-05 13:45:31 CET --- Since this will be relevant even for SLE12 I'm reopening this bug. It still happens with a fresh 13.1. Right after install login is only possible via serial console or ssh, when 13.1 is booted with this cmdline: linemode=1 quiet sysrq=yes panic=9 start_shell ssh=1 sshpassword=root nosshkey vnc=1 vncpassword=password linemode=1 start_shell console=ttyS0,57600 install=http://download.opensuse.org/distribution/13.1/repo/oss -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c20 --- Comment #20 from Olaf Hering <ohering@suse.com> 2013-12-05 13:49:44 CET --- This is what I get, not sure what is actually required to offer a vnc login: 1 ? /sbin/init showopts 1448 ? /usr/lib/systemd/systemd-journald 1502 ? /usr/lib/systemd/systemd-udevd 1855 ? /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation 1856 ? avahi-daemon: running [linux-3.local] 1858 ? /usr/sbin/nscd --foreground 1859 ? /usr/lib/systemd/systemd-logind 4612 ? login -- root 6270 ttyS0 \_ -bash 4769 ? /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf 5744 ? /usr/lib/postfix/master 1110 ? \_ pickup -l -t fifo -u 1111 ? \_ qmgr -l -t fifo -u 5767 ? /usr/sbin/cron -n 5842 ? /usr/sbin/cupsd -f 5981 ? /usr/lib/systemd/systemd --user 5982 ? \_ (sd-pam) 2725 ? /usr/sbin/sshd -D 6384 ? \_ sshd: root@pts/0 6386 pts/0 \_ -bash 6509 pts/0 \_ ps fax 2840 ? /usr/sbin/rsyslogd -n 3433 ? /sbin/rpcbind -w -f 3442 ? /usr/sbin/ypbind -n -no-dbus 3465 ? /usr/sbin/automount -p /var/run/automount.pid 5476 ? /sbin/dhcpcd --netconfig -L -E -HHH -c /etc/sysconfig/network/scripts/dhcpcd-hook -t 0 -h satriani enp1s0f0 6150 tty1 /sbin/agetty --noclear tty1 6220 ? /usr/bin/xdm 6223 tty7 \_ /usr/bin/X -nolisten tcp -br vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-gS9Nno 6252 ? \_ -:0 6265 ? /usr/bin/xconsole -notify -nostdin -verbose -exitOnFail -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c21 --- Comment #21 from Olaf Hering <ohering@suse.com> 2013-12-05 14:14:10 CET --- Like in 12.2, after reboot the vnc login is offered. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c Vladimir Moravec <vmoravec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmoravec@suse.com AssignedTo|yast2-maintainers@suse.de |jsuchome@suse.com -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c23 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |ohering@suse.com --- Comment #23 from Arvin Schnell <aschnell@suse.com> 2013-12-13 15:51:42 UTC --- Please provide start YaST logs (including the start log). -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c24 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|ohering@suse.com | --- Comment #24 from Olaf Hering <ohering@suse.com> 2013-12-16 19:37:14 CET --- Created an attachment (id=572001) --> (http://bugzilla.novell.com/attachment.cgi?id=572001) bug774386.tar.xz logs from installation in a hv guest. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c25 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@suse.com |yast2-maintainers@suse.de --- Comment #25 from Arvin Schnell <aschnell@suse.com> 2013-12-16 19:09:10 UTC --- As I read the report and the logs the second stage of the installation works fine so this is not a problem with the yast startup scripts. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c26 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsuchome@suse.com --- Comment #26 from Arvin Schnell <aschnell@suse.com> 2014-01-08 13:36:45 UTC --- I found some code dealing with VNC setup for the final system in copy_files_finish.rb in yast-installation. Reassigning to maintainer of yast-installation. -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsuchome@suse.com |lslezak@suse.com -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c27 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO CC| |jreidinger@suse.com InfoProvider| |ms@suse.com --- Comment #27 from Josef Reidinger <jreidinger@suse.com> 2014-02-27 14:24:23 UTC --- I am sure that problematic part is this one: https://github.com/yast/yast-installation/blob/master/startup/Second-Stage/S... I do not see reason why we must kill VNC sessions. Markus git blame told me you are author, do you know reason? -- 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=774386 https://bugzilla.novell.com/show_bug.cgi?id=774386#c28 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED CC| |ms@suse.com InfoProvider|ms@suse.com | --- Comment #28 from Marcus Schaefer <ms@suse.com> 2014-02-27 15:04:30 UTC --- It's true that I wrote the startup code several years ago when I was a member of the yast team but I'm afraid I have no yast development system anymore and thus can't give this a test
From just reading the code the cleanup stage was used to stop all installation related services. This includes ssh connections as well as vnc X-servers as well as local X-servers and so on
What I think is problematic is the killall Xvnc which would really kill all Xvnc sessions also those which are not releated to the yast installation process. At the time when I wrote it the assumption was that while inside this process there is if at all only the Xvnc server started by yast and nothing else to do this better the Xvnc startup should store its pid and the cleanup should only focus on this session -- 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