Bug#656803: libgtk-3-doc: image files in reference manual are missing
Not only images are missing. Some html files instead of code snippets have only a message: FIXME: MISSING XINCLUDE CONTENT See for example: gdk3/gdk3-Windows.html gtk3/gtk-getting-started.html gtk3/GtkApplication.html Rafal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598551: /usr/sbin/pppd: updetach option causes "Connection terminated"
How to repeat the problem: assume the following pppd command does work: pppd call foo The following command causes hangup immediately after connect: dash -c "pppd call foo updetach" Problem is caused by "always_setsid" patch. The patch is unnecessary with ppp 2.4.5 because problem which the patch is for, was fixed in original code - see differences between 2.4.4 and 2.4.5 in file pppd/main.c, function kill_my_pg(). The patch removal should correct the problem, without any negative impact. Rafal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#626939: ppp: updetach regression: hangs up immediately after IPCP's OK
This is the same problem as I wrote in bug #598551, namely, the problem is caused by "always_setsid" patch. I suggest to remove the patch. In my opinion it does not solve intended problem, only adds a new one. Rafal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598551: /usr/sbin/pppd: updetach option causes "Connection terminated"
The bug does not appear in original pppd code. It is caused by "always_setsid" patch. With this patch, setsid() function is invoked before opening modem (tty) device. If the setsid() succeeds, pppd process is losing their controlling tty and then the opened modem device becomes a controlling tty of the pppd. This causes that when the parent dies, HUP signal is sent to all children processes - in particular to the child process communicating via modem. The setsid() function fails when pppd is invoked directly from shell. It succeeds when is invoked e.g. from a shell script. If sedsid() fails, HUP signal is not sent to children when parent dies because the opened modem device does not become the controlling tty. This explains behavior described by David (Message #27). As I understand, the "always_setsid" patch was added to prevent from kill of parent processes when a signal is delivered to pppd. But, as I see in the original pppd code, the problem should not appear. How old is the patch? Maybe the problem was fixed in original code some time ago, and the patch is not needed? Rafal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
