[Bug 244311] [NEW] leftnexthop required even if left is %defaultroute
Public bug reported: Binary package hint: openswan Contrary to what is said in the manpage for ipsec.conf, quote: "leftnexthop: next-hop gateway IP address for the left participant’s connection to the public network; [...] If the value is to be overridden by the left=%defaultroute method (see above), an explicit value must not be given.", leftnexthop must be set to %defaultroute as well if the client connection to the public network is via a gateway. More precisely, with the attached ipsec.conf (slightly anonymized), after sudo ipsec auto --route L2TP-PSK-CLIENT the routing table looks like Destination Gateway Genmask Flags Metric RefUse Iface vpn.example.com * 255.255.255.255 UH0 00 eth0 192.168.2.0 * 255.255.255.0 U 0 00 eth0 link-local * 255.255.0.0 U 1000 00 eth0 default 192.168.2.1 0.0.0.0 UG0 00 eth0 Note that connections to the VPN server are incorrectly routed into the local network, not via the gateway to the public network. After adding leftnexthop=%defaultroute to /etc/ipsec.conf the first route above changes to vpn.example.com 192.168.2.1 255.255.255.255 UGH 0 00 eth0 which is the correct behaviour. This might either be a mistake in the documentation (i.e. leftnexthop is now required even if left is %defaultroute) or a bug in OpenSWAN. This is on Hardy with OpenSWAN 2.4.9. ** Affects: openswan (Ubuntu) Importance: Undecided Status: New -- leftnexthop required even if left is %defaultroute https://bugs.launchpad.net/bugs/244311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244311] Re: leftnexthop required even if left is %defaultroute
** Attachment added: "ipsec.conf file (anonymized) demonstrating the problem" http://launchpadlibrarian.net/15692598/ipsec.conf.old -- leftnexthop required even if left is %defaultroute https://bugs.launchpad.net/bugs/244311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243384] Re: Incorrect argument passing from ip-up to ip-up.local
Of course, /etc/ppp/ip-down has exactly the same problem. Find attached a patch fixing this, too. ** Attachment added: "ip-down.patch" http://launchpadlibrarian.net/15636537/ip-down.patch -- Incorrect argument passing from ip-up to ip-up.local https://bugs.launchpad.net/bugs/243384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243357] Re: /var/run/xl2tpd disappears after reboot
** Description changed: The binary (i386) package for xl2tpd contains a directory /var/run/xl2tpd/. This seems pretty futile since /var/run is cleared on each reboot, so the newly-created directory persists only for the current session. After a reboot, xl2tpd does not start anymore because this directory is missing. Instead, the init script /etc/init.d/xl2tpd should check for /var/run/xl2tpd/ and create it if it's not there. See the related issue (though for a different package) discussed in: http://ubuntuforums.org/archive/index.php/t-139923.html + + Find attached a proposed patch fixing this. ** Attachment added: "Create /var/run/xl2tpd if it doesn't exist" http://launchpadlibrarian.net/15636514/xl2tpd.patch -- /var/run/xl2tpd disappears after reboot https://bugs.launchpad.net/bugs/243357 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243384] Re: Incorrect argument passing from ip-up to ip-up.local
** Attachment added: "ip-up.patch" http://launchpadlibrarian.net/15635954/ip-up.patch -- Incorrect argument passing from ip-up to ip-up.local https://bugs.launchpad.net/bugs/243384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243384] [NEW] Incorrect argument passing from ip-up to ip-up.local
Public bug reported: Binary package hint: ppp The startup script /etc/ppp/ip-up optionally calls another startup script /etc/ppp/ip-up.local iff the latter exists and is executable. However, it incorrectly passes its command line arguments on to ip- up.local. More precisely, line 47 in version 2.4.4rel-9ubuntu2 reads: exec /etc/ppp/ip-up.local "$*" This invokes ip-up.local like /etc/ppp/ip-up.local "$1 $2 $3 $4 $5 $6" (similarly for >6 arguments). Thus ip-up.local is called with only 1 argument. Instead, line 47 should be exec /etc/ppp/ip-up.local "$@" which invokes ip-up.local like /etc/ppp/ip-up.local "$1" "$2" "$3" "$4" "$5" "$6" A corresponding patch is attached. ** Affects: ppp (Ubuntu) Importance: Undecided Status: New -- Incorrect argument passing from ip-up to ip-up.local https://bugs.launchpad.net/bugs/243384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243357] [NEW] /var/run/xl2tpd disappears after reboot
Public bug reported: The binary (i386) package for xl2tpd contains a directory /var/run/xl2tpd/. This seems pretty futile since /var/run is cleared on each reboot, so the newly-created directory persists only for the current session. After a reboot, xl2tpd does not start anymore because this directory is missing. Instead, the init script /etc/init.d/xl2tpd should check for /var/run/xl2tpd/ and create it if it's not there. See the related issue (though for a different package) discussed in: http://ubuntuforums.org/archive/index.php/t-139923.html ** Affects: xl2tpd (Ubuntu) Importance: Undecided Status: New -- /var/run/xl2tpd disappears after reboot https://bugs.launchpad.net/bugs/243357 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184996] Re: Annotation tools are broken in hardy
Today I tried xournal again with "Use XInput" deactivated (following your suggestion above) and now most things seem to work almost as on Feisty/Gutsy, except that the drawings aren't smooth as you already noted. I also checked against my Feisty installation of xournal (0.3.3) and there the "Use XInput" option is not enabled by default. In fact, the corresponding menu entry is grey/deactivated. Since I don't have a tablet PC I can't check whether it would work with the pen. So I think 90% of this bug (at least #1 and #3) could be fixed by just not making "Use XInput" the default or somehow have this depend on whether xournal runs on a tablet PC or not. Just moving away .xournal does btw. not help on my installation. What remains are the slightly square-edged drawings and the eraser problem. I can considerably improve on the latter by choosing "Tools/Eraser Options/Standard". "Delete Strokes" on the other hand leads to the very strange behaviour mentioned above under #2. -- Annotation tools are broken in hardy https://bugs.launchpad.net/bugs/184996 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184996] Annotation tools are broken in hardy
Public bug reported: Binary package hint: xournal In the most recent version of xournal (0.4.1) on Hardy, most of xournal's tools are broken. In particular: 1) Pen & highlighter tool: Drawing / highlighting only becomes visible after _releasing_ the mouse button. 2) Eraser tool: Sometime erases all of a figure drawn in one stroke. 3) Text tool: Text is always inserted at the top left corner of the page no matter where you click. Since the xournal version in Hardy is the same as in Gutsy (0.4.1-0ubuntu1) where none of these problems occur, this is most likely due to some updated library xournal depends on. ** Affects: xournal (Ubuntu) Importance: Undecided Status: New -- Annotation tools are broken in hardy https://bugs.launchpad.net/bugs/184996 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174291] Comment text in xorg.conf missing
Public bug reported: The comment lines in /etc/X11/xorg.conf are missing the file and package name on Hardy. For example, the first line in xorg.conf on Hardy is: # (xorg X Window System server configuration file) whereas on Feisty it reads: # /etc/X11/xorg.conf (xorg X Window System server configuration file) Another example are lines 6+7. On Hardy: # Edit this file with caution, and see the manual page. # (Type "man " at the shell prompt.) On Feisty: # Edit this file with caution, and see the xorg.conf(5) manual page. # (Type "man xorg.conf" at the shell prompt.) This reduces the usefulness of these comments for newcomers. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- Comment text in xorg.conf missing https://bugs.launchpad.net/bugs/174291 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174288] emacs-el doesn't depend on latest elisp sources
Public bug reported: The metapackage "emacs-el" depends on "emacs21-el" in Hardy, whereas the latest elisp source package is "emacs22-el". N.B.: The latest emacs release installed via the metapackage "emacs" is "emacs22", too, so this behaviour is inconsistent. ** Affects: emacs21 (Ubuntu) Importance: Undecided Status: New -- emacs-el doesn't depend on latest elisp sources https://bugs.launchpad.net/bugs/174288 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107117] Re: Only first session works when Desktop effects are enabled
** Attachment added: "Screenshot showing the "empty" terminal window during a faulty session" http://librarian.launchpad.net/7338341/Screenshot-1.png -- Only first session works when Desktop effects are enabled https://bugs.launchpad.net/bugs/107117 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107117] Only first session works when Desktop effects are enabled
Public bug reported: Binary package hint: compiz After the first session with desktop effects enabled has ended subsequent sessions behave strangely if they have desktop effects switched on. For example, terminal windows do not show any text (see attached screenshot), many dialog boxes are missing elements, menu items aren't highlighted if pointed to. If the X server is restarted the following session again works as usual. Also, sessions not using desktop effects do not seem to be affected in any way. This happens on an IBM ThinkPad T41p with Feisty. ** Affects: compiz (Ubuntu) Importance: Undecided Status: Unconfirmed -- Only first session works when Desktop effects are enabled https://bugs.launchpad.net/bugs/107117 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107109] No "New Login" for user with Desktop effects enabled
Public bug reported: Binary package hint: gdm When using Applications --> System Tools --> New Login to create a new login screen, users with Desktop effects enabled cannot log in. For users with Desktop effects disabled, everything works as usual. How to reproduce: 0. Enable Desktop effects for user X. 1. Log in as user Y. 2. Select Applications --> System Tools --> New Login. 3. Try to log in as user X. In this case, instead of being logged in, I get a white screen on which I can see & move the mouse pointer. The session can be exited as usual with CTRL+ALT+Backspace, returning me to the session of user X. The same thing happens if user Y initially has desktop effects switched off and switches them on during a session initiated with Applications --> System Tools --> New Login. I'm running Feisty on an IBM ThinkPad T41p with the free "Radeon" driver (xserver-xorg-video-ati, i.e. not fglrx). ** Affects: gdm (Ubuntu) Importance: Undecided Status: Unconfirmed -- No "New Login" for user with Desktop effects enabled https://bugs.launchpad.net/bugs/107109 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 19101] Re: nautilus's clever anti-hax0r detection is really dumb
Sorry for so long without notice. On my box this problem occurs with _every_ pdf file. I have no problems with e.g. jpg files or so. As an example I attach one of the files for which I verified that it doesn't open upon double-clicking (giving the cited error message instead). ** Attachment added: "Example file for bug 19101" http://librarian.launchpad.net/5804269/042.pdf -- nautilus's clever anti-hax0r detection is really dumb https://launchpad.net/bugs/19101 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76413] PDF documents can't be opened by double clicking
Public bug reported: When I double click on a PDF file (say somedoc.pdf) in Nautilus 2.16.1, instead of opening the file in Evince a dialog box pops up saying --- Cannot open ChomboDesign-1.4.pdf The filename "ChomboDesign-1.4.pdf" indicates that this file is of type "pdf document". The contents of the file indicate that the file is of type "PDF document". If you open this file, the file might present a security risk to your system. Do not open the file unless you created the file yourself, or received the file from a trusted source. To open the file, rename the file to the correct extension for "PDF document", then open the file normally. Alternatively, use the Open With menu to choose a specific application for the file. --- This happens with every PDF file. When using right click - Open with -- Open with "Document Viewer" everything works as expected. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- PDF documents can't be opened by double clicking https://launchpad.net/bugs/76413 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
