[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#883062: marked as done (XDM could not be stopped)

Your message dated Wed, 22 May 2019 17:34:58 +0200
with message-id <20190522153458.h6g3zzmff3iy4kty@jwilk.net>
and subject line Re: Bug#883062: XDM could not be stopped
has caused the Debian Bug report #883062,
regarding XDM could not be stopped
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
883062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883062
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xdm
Version:

Dear maintaner(-s), I've found that XDM could not be stopped.
When I run command
   systemctl stop xdm.service
it hungs and XDM gets killed [by systemd] using SIGKILL.

Same hangup occur upon host reboot and termination.


Following piece is a system calls (trace obtained using ``strace'' utility)
from XDM:
rt_sigsuspend([], 8)                    = ? ERESTARTNOHAND (To be restarted if n
o handler) <11.870653>
--- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=1, si_uid=0} ---
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=594,
si_uid=0, si_status=SIGTERM, si_utime=2, si_stime=2} ---
--- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=1, si_uid=0} ---
rt_sigreturn({mask=[TERM]})             = 0 <0.000090>
getpid()                                = 543 <0.000030>
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1544, ...}) = 0 <0.000048>
getpid()                                = 543 <0.000017>
write(2</var/log/xdm.log>, "Tue Nov 28 20:11:23 2017 xdm inf"..., 45)
= 45 <0.000033>
write(2</var/log/xdm.log>, "Shutting down\n", 14) = 14 <0.000020>
kill(594, SIGTERM)                      = 0 <0.000019>
kill(594, SIGCONT)                      = 0 <0.000017>
kill(564, SIGTERM)                      = 0 <0.000022>
kill(564, SIGCONT)                      = 0 <0.000018>
rt_sigreturn({mask=[HUP CHLD]})         = -1 EINTR (Interrupted system
call) <0.000019>
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000017>
wait4(-1, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGTERM}], WNOHANG, NULL)
= 594 <0.000043>
stat("/etc/X11/xdm/xdm-config", {st_mode=S_IFREG|0644, st_size=1113,
...}) = 0 <0.001980>
stat("/etc/X11/xdm/Xservers", {st_mode=S_IFREG|0644, st_size=1696,
...}) = 0 <0.000755>
stat("/etc/X11/xdm/Xaccess", {st_mode=S_IFREG|0644, st_size=3401,
...}) = 0 <0.000503>
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1544, ...}) = 0 <0.000036>
getpid()                                = 543 <0.000037>
write(2</var/log/xdm.log>, "Tue Nov 28 20:11:23 2017 xdm inf"..., 45)
= 45 <0.000037>
write(2</var/log/xdm.log>, "display :0 is being disabled\n", 29) = 29 <0.000019>

Strace was attached immediately before attempt to stop XDM.
Process [564] seems to be an X server.
So, probably this is hangup is a result of bug in the X itself and not in XDM.


Following packages (excerpt from ``dpkg -l'') are installed on the host:

Complete list is in attachement.

-- 
С уважением, Дунаев Антон.
mailto: duanton@gmail.com

--- End Message ---
--- Begin Message --- 
* Anton Dunaev <duanton@gmail.com>, 2017-11-29, 13:00:

Please close


Closing as requested.

--
Jakub Wilk

--- End Message ---
Reply to: